I have a rooted phone (CM6.1) and just had the misfortune to drop it. The scree didn't shatter, but when I turn on the display, the only thing I can see is a bunch of vertical lines.
I tried calling myself, and can answer the call by swiping my finger across the "Accept" (Call).
I want to know if anyone knows if I can do a full backup of my phone using adb or another tool. Anyone have a suggestion?
Tl;dr: I can't access my phone through the screen and need to do a full backup via USB. How?
Well, you can pull anything you want via ADB, but here's something that might be even more useful:
adb reboot recovery (to get into recovery). After it's in recovery, go into adb shell and run:
nandroid-mobile.sh backup
Hands free nandroid!
nandroid-mobile.sh --help will list out all available options if you want. A couple that might be of interest:
- Include -e and -a if you want it to capture your ext (if applicable) and .android_secure folders on your SD.
- Since you'll be using this on a new device, you don't want to restore the wimax partition. Therefore, you could exclude it from the backup with -nowimax.
Also, I'm not sure what kind of issues you can have with a nandroid restore from another device. But maybe you can restore it to the new device, use Titanium to backup what you need, and then wipe and restore with Titanium. Or maybe it's just fine to restore the nandroid. Haven't needed to try yet.
Thank you so much!
Hello everyone, I'm desperately seeking for your help and hope you can give me some advice. So far, I could not relate to any of the similar topics and I'm not sure how to continue.
Problem:
The display of my Nexus 4 is broken and I want to make a nandroid backup before sending it in for repair. The screen still works but the touch function won't. Thus, I am unable to fully start the device since I cannot unlock the phone. My Nexus was rooted with the Nexus 4 Toolkit and runs on CM10. CWM is installed. Operation system of my computer: Win 7 64bit
Privious attemps:
As far as I experienced it, I'm not able to use ADB as I cannot completely start my phone due to the security pattern that I can't bypass since I have no touch function. At least the Toolkit tells me so, that ADB is not possible. Furthermore, it does not allow a backup via fastboot. Hence, I entered recovery mode and did a full backup with CWM, which is supposed to be saved in the folder CWM/backup. However, when accessing my phone via usb, there is not such a subfolder in CWM and I cannot get the backup file on my computer. The file is definitely there, since I can choose it within the restore options of CWM.
Any hints for me? Ist there a possibility for a nandroid backup without ADB? or Can I somehow access the folders of CWM where the backup is saved and transfer it via usb? or Else?
Thanks!!!!!!!!!!
Try looking for a folder called clockworkmod and search there it should be in a sub folder labeled backups. Also you can try screencast, I've only heard of it never used it but is supposed view your phone on pc Like a virtual decice
Sent from my SGH-T959V using xda app-developers app
adb should work in recovery.
use the command
adb pull /sdcard/
sexun said:
Hence, I entered recovery mode and did a full backup with CWM, which is supposed to be saved in the folder CWM/backup.
Click to expand...
Click to collapse
Backups are saved in /data/media/clockworkmod/backup
I've always used /mnt/shell/emulated/clockworkmod/
Hi all, been trying to solve this problem for a while, can't seem to figure it out.
Yesterday, when my phone died and I charged and turned it back on, the recents and home buttons wouldn't work, in addition to my notifications not showing and the quick settings drawer not coming down. This seems to be a problem others have ran into. Here's what I've tried so far:
clearing dalvik cache and regular cache
updating my ROM (I use AICP)
restoring an old backup of AICP
starting my phone in safe mode (all errors persist)
using ADB to attempt to get into the SetupWizardTestActivity as advised here
The error I get from this:
Code:
adb shell am start -n com.google.android.setupwizard/.SetupWizardTestActivity
Starting: Intent { cmp=com.google.android.setupwizard/.SetupWizardTestActivity }
java.lang.SecurityException: Permission Denial: starting Intent { flg=0x10000000 cmp=com.google.android.setupwizard/.SetupWizardTestActivity } from null (pid=12048, uid=2000) not exported from uid 10072
at android.os.Parcel.readException(Parcel.java:1684)
at android.os.Parcel.readException(Parcel.java:1637)
at android.app.ActivityManagerProxy.startActivityAsUser(ActivityManagerNative.java:3160)
at com.android.commands.am.Am.runStart(Am.java:643)
at com.android.commands.am.Am.onRun(Am.java:394)
at com.android.internal.os.BaseCommand.run(BaseCommand.java:51)
at com.android.commands.am.Am.main(Am.java:124)
at com.android.internal.os.RuntimeInit.nativeFinishInit(Native Method)
at com.android.internal.os.RuntimeInit.main(RuntimeInit.java:264)
I also tried switching from my user to a Guest user, but it won't allow me to go into the Users. At this point, I decided to take a backup on my laptop and factory reset, but after plugging my phone into my laptop, I realized I can't change the USB connection type from charging to mass storage (or whatever it is) to access the files on my laptop since I can't see notifications. This lead me to Developer Options, where I get the message "Developer options are not available for this user."
So then I tried to make an activity in Nova for the SetupTestActivity as detailed here, but the closest thing I can find in there is under Settings about activating the cellular service, and when I try to use that I just get "Permission denied" error.
After all of this, I looked into backing up my device via ADB using this command:
Code:
adb backup -apk -shared -all
It tells me to unlock my device to confirm the backup operation, but there is nothing shown on my device indicating a confirmation.
Then I went into my file manager (I use Xplore) and it indicates that my device is not rooted. I don't know how that could've happened, although I have not tried re-rooting it to see if that helps. Any suggestions or do I just have to do a factory reset and lose all my data?
markgnarza said:
... Any suggestions or do I just have to do a factory reset and lose all my data?
Click to expand...
Click to collapse
Why not use TWRP to create a newer backup? You can also use TWRP's MTP to move anything off the phone you want. Then flash a full Google image with flash-all.bat. You can try it without the -w switch first if you like. I doubt it's a hardware issue, but stranger things have happened, and returning to stock briefly will let you know right away.
v12xke said:
Why not use TWRP to create a newer backup? You can also use TWRP's MTP to move anything off the phone you want. Then flash a full Google image with flash-all.bat. You can try it without the -w switch first if you like. I doubt it's a hardware issue, but stranger things have happened, and returning to stock briefly will let you know right away.
Click to expand...
Click to collapse
I ended up uploading my Titanium backups/other files I wanted to keep to Google Drive and factory resetting, but now the setup wizard keeps crashing. Think I'm gonna try a full wipe and flash of AICP again to see if that does it.
markgnarza said:
I ended up uploading my Titanium backups/other files I wanted to keep to Google Drive and factory resetting, but now the setup wizard keeps crashing. Think I'm gonna try a full wipe and flash of AICP again to see if that does it.
Click to expand...
Click to collapse
Okay, hope that works for ya. Nowadays with Google backup for market apps and TiBu for everything else, it doesn't take long (less than one hour) to completely wipe, clean install, and restore everything back the way it was. Especially if you have a good internet connection. I use my Solid Explorer to zip the TiBu folder into a single file and transfer that off to my PC. Try that next time and see if it saves you some time. My TiBu zip files are well over 1GB, so I don't u/l them to the cloud. Curious if you have TWRP why you did not have MTP file transfer from recovery to laptop?
v12xke said:
Okay, hope that works for ya. Nowadays with Google backup for market apps and TiBu for everything else, it doesn't take long (less than one hour) to completely wipe, clean install, and restore everything back the way it was. Especially if you have a good internet connection. I use my Solid Explorer to zip the TiBu folder into a single file and transfer that off to my PC. Try that next time and see if it saves you some time. My TiBu zip files are well over 1GB, so I don't u/l them to the cloud. Curious if you have TWRP why you did not have MTP file transfer from recovery to laptop?
Click to expand...
Click to collapse
It worked! And all my Titanium backups + photos are still intact on my phone? Seems strange to me. I hadn't thought of zipping my TiBu folder, good idea!
As for using TWRP to transfer to laptop, I'm not sure how that process works! I'll look around in TWRP once I'm done restoring everything to see what you mean, good to keep in mind for the future. Thanks for the help!
My honor got the same problem... I know they were working but now they don't.. what should i do??
From what I understand, the Snapdragon S8+'s bootloader is still locked, other than for the Chinese and Hong Kong variants, so there is no chance of a custom recovery currently. This said, I am trying to find a decent backup solution for my Sprint S8+.
I am trying to create a backup using "adb backup -apk -shared -all -system -f test.ab". I can get the backup to run, but it only creates a 40-80mb file. When I restore the backup, nothing changes on my phone.
Can someone please clarify what is going on here? If you guys need more information to help, please let me know. Thanks!
Works for my S8 snapdragon. My backup files are in the 1.6 GB size. Make sure you are running cmd.exe as administrator and wait until it finishes. It may take 15 to 20 minutes to complete.
gschroer said:
Works for my S8 snapdragon. My backup files are in the 1.6 GB size. Make sure you are running cmd.exe as administrator and wait until it finishes. It may take 15 to 20 minutes to complete.
Click to expand...
Click to collapse
Even if I use an elevated (Administrator) command prompt, the backup takes about one minute to complete. I have added a few apps to my phone, since I last posted. The size is up to 174mb now, but there is no way it takes 15+ minutes.
I am connected via USB 3.0. Are you using wifi? Do you have any idea the size of a backup on a newly reset phone? I still think something is off here.
With -apk aren't copies of the APKs supposed to be saved with the backup? Are they saved as separate files? I do not see any with mine.
DawgY said:
Even if I use an elevated (Administrator) command prompt, the backup takes about one minute to complete. I have added a few apps to my phone, since I last posted. The size is up to 174mb now, but there is no way it takes 15+ minutes.
I am connected via USB 3.0. Are you using wifi? Do you have any idea the size of a backup on a newly reset phone? I still think something is off here.
With -apk aren't copies of the APKs supposed to be saved with the backup? Are they saved as separate files? I do not see any with mine.
Click to expand...
Click to collapse
I'm using an usb 2.0 connection. The 1.5 GB size is for an unlocked, no bloat, phone with about 10 added user apps. Your backup should be at least 1.0 GB.
Yes the -apk switch should backup your apps. The app files can be extracted, the backup file is a compressed TAR file using a Java Deflater. You can search on-line on how to extract from the .ab file..
gschroer said:
I'm using an usb 2.0 connection. The 1.5 GB size is for an unlocked, no bloat, phone with about 10 added user apps. Your backup should be at least 1.0 GB.
Yes the -apk switch should backup your apps. The app files can be extracted, the backup file is a compressed TAR file using a Java Deflater. You can search on-line on how to extract from the .ab file..
Click to expand...
Click to collapse
I have looked in to all of that, because I wanted to verify the contents of my backups to make sure they are completing properly. However, this still does not provide a solution to the small size. I have a stock Sprint S8+ and am using an up-to-date version of "platform-tools" downloaded via sdkmanager.
I'm not sure what else to try at this point. Can you think of anything that would lead to a smaller size? I can see the toast messages on my phone, so I can tell when the backup begins and ends. I'm honestly out of options.
By the way, what do you mean by "unlocked"? I am accustomed to that term being used for an unlocked bootloader, although I did not think that was currently possible with the S8+. I am not rooted, so from what I understand, "adb backup" cannot access system files. If you are rooted, I guess this could account for the size difference. Again, I'm grasping at straws here...
DawgY said:
I'm not sure what else to try at this point. Can you think of anything that would lead to a smaller size? I can see the toast messages on my phone, so I can tell when the backup begins and ends. I'm honestly out of options.
By the way, what do you mean by "unlocked"? I am accustomed to that term being used for an unlocked bootloader, although I did not think that was currently possible with the S8+. I am not rooted, so from what I understand, "adb backup" cannot access system files. If you are rooted, I guess this could account for the size difference. Again, I'm grasping at straws here...
Click to expand...
Click to collapse
"Unlocked" being carrier unlocked, so no carrier bloatware to make the backup larger. After running the ADB backup command my phone gives me an option to encrypt the backup, which I' not providing a password to encrypt. On the phone screen it starts showing the apk's one at a time that it is backing up. It only shows about five apk's before the screen blanks out. Guess it could be the sprint firmware preventing the backup. Maybe post on the sprint forum to see if anybody is using ADB to backup their phone.
gschroer said:
"Unlocked" being carrier unlocked, so no carrier bloatware to make the backup larger. After running the ADB backup command my phone gives me an option to encrypt the backup, which I' not providing a password to encrypt. On the phone screen it starts showing the apk's one at a time that it is backing up. It only shows about five apk's before the screen blanks out. Guess it could be the sprint firmware preventing the backup. Maybe post on the sprint forum to see if anybody is using ADB to backup their phone.
Click to expand...
Click to collapse
Yes. I have heard that different ROMs can mess with this process. I will follow your suggestion. Thank you for the help, gschroer!
Hi,
First post, so be gentle. I searched the forum and found quite a few posts about a boot looping S5 but most referring to custom ROMs - my phone started doing this on its own. Running marshmallow 6.0.1. Its almost 3 years old, and up until now has never caused problems. It was charging when this first happened, and it could have updated (I have no way of knowing what update though).
First thing I tried was a new battery, I charged it up with the phone off, but it still wouldn't boot.
The problem:
-It either hangs on the startup splash screen ("Samsung GALAXY S5") and can only be turned off by pulling the battery (sometimes), or.. it restarts on the same screen (mostly).
-If I leave it for 10 minutes without a battery, it goes further, getting to the point where it asks for the password, but then freezes at this point at restarts.
-I can get into recovery (vol up + home + power buttons) and have cleared the cache. It never hangs or freezes whilst in recovery.
-Whilst I had enabled developer options (used for debugging bluetooth problems once) I have NOT enabled USB debugging - so it seems ADB push/pull to recover user data won't work.
I don't really want to do a factory reset as google hasn't backed up everything, so I'm stuck. Does TWRP or clockworkmod go into the recovery partition (sparing user data)? Or do these only work after a factory reset? I have read a fair bit about Odin, Kies, and firmware updates, but as I don't know what the problem is, I have no idea where to start - I was hoping there are some kind of debug logs on the phone that could at least point to the cause, but of course I cannot access it. The fact it doesn't crash/hang/restart in recovery leads me to believe it isn't a hardware problem - but the fact this happened suddenly without me changing anything is suspicious. Ideas?
If you have an SD card inserted remove it - a corrupt SD can cause bootloops
If it boots without sd card transfer what you need from it to a pc either via USB card reader or via USB cable whilst in twrp
Once done format sd card & transfer files back - note only transfer back personal files eg pics music etc & not the android folder or any app data
If it still bootloops your only choice maybe a factory reset
You can flash twrp at any time - it will not erase userdata unless you goto the wipe section & do it yourself
You can create a backup & extract it on a pc but remember twrp backups do not backup personal files like pics music docs
You can however mount internal storage & transfer what ever files you want to pc
If all else fails flash stock firmware via odin
TheFixItMan said:
If you have an SD card inserted remove it - a corrupt SD can cause bootloops
If it boots without sd card transfer what you need from it to a pc either via USB card reader or via USB cable whilst in twrp
Once done format sd card & transfer files back - note only transfer back personal files eg pics music etc & not the android folder or any app data
Click to expand...
Click to collapse
Sadly, it stil does it without the SD - forgot to mention I tried that too.
TheFixItMan said:
You can flash twrp at any time - it will not erase userdata unless you goto the wipe section & do it yourself
You can create a backup & extract it on a pc but remember twrp backups do not backup personal files like pics music docs
You can however mount internal storage & transfer what ever files you want to pc
If all else fails flash stock firmware via odin
Click to expand...
Click to collapse
Ahh, this is what I was hoping. So twrp, goes onto the recovery partition? I did read (here: hxxps://twrp.me/faq/backupexclusions.html ), as you mentioned, that TWRP doesn't back up internal storage automagically. Even if done manually, as long as I can transfer the files to PC, I'll be happy. Thankfully, it's only one folder of photos that I google didn't back up, but I might as well grab everything.
I may post back with questions, thanks for the reply!
Right, I keep reading that "USB debugging" must be enabled when installing TWRP, or doing almost anything. But I don't have this enabled, and I can't enable it since I don't have access to the phones system. Is this required to install TWRP? I know it is required to use ADB which I believe is used to flash the TWRP. If this is the case, it looks like a dead end. I did find one link claiming to enable USB debugging from a recovery, but the instructions are incomplete, and it also mentions performing a factory reset first - which kind of defeats the point.
BuriedCode said:
Right, I keep reading that "USB debugging" must be enabled when installing TWRP, or doing almost anything. But I don't have this enabled, and I can't enable it since I don't have access to the phones system. Is this required to install TWRP? I know it is required to use ADB which I believe is used to flash the TWRP. If this is the case, it looks like a dead end. I did find one link claiming to enable USB debugging from a recovery, but the instructions are incomplete, and it also mentions performing a factory reset first - which kind of defeats the point.
Click to expand...
Click to collapse
On the g900f all you have to do is the following
Install Samsung USB drivers https://developer.samsung.com/galaxy/others/android-usb-driver-for-windows
Put phone into download mode (hold Vol down home & power button) & connect to pc
Push Vol up to start connection
Open odin https://forum.xda-developers.com/attachment.php?attachmentid=4431749&d=1519672710
Place twrp.tar in the AP section & flash
https://dl.twrp.me/klte/
As soon as the phone restarts enter recovery - hold Vol up home power button
If the phone starts to boot before entering recovery you will need to flash it again - once you have entered twrp once it will stick
Once again, thank you for the clear instructions. I Successfully got TWRP on my phone, and it appears on the PC so I could see the file structure in explorer (!). Progress.
I went to copy two photos as a test - MPT/USB transfers have always been unreliable for me anyway - and the phone froze. I only noticed when the touch screen became unresponsive and the clock wasn't updating. So this could well be the original problem - a hardware issue that causes the phone to freeze when it does anything remotely taxing. Or.. it could be the MPT transfer.
Either way, I had to pull the battery and it seems the TWRP didn't take as when I tried to boot into recovery, it had the stock recovery menu. So at least I'm not going backwards, nothing is broken.
Now I know how to get TWRP on there, and to boot back into recovery right away, and I know that it works. Next up is getting it on there and leaving it for 10 minutes to see if it crashes/freezes. If its OK, then I'll have to look for another way to pull files off. Can one use ADB with TWRP? If its enabled then I could use "pull" to get the files off and hopefully quicker (or at least more reliably) than ****ty MPT. Ideally I'd like to just pull everything off so I can decide what to add back later after a fresh reset.
Thank you once again for your advice!
Replying to my own post. It still can crash (screen has random colours on it and it freezes) but rarely whilst in TWRP. I was able to use adb and pull off all my camera photos that weren't backed up, and with the "-a" option, keep the file attributes.
Also solved the MPT problem - if anyone has the same issue or cares - using USB 3.0 sockets on my PC and only at the back rather than the sockets on the front (which are awful quality anyway). It's sitll onyl USB 2.0 but I guess the socket is higher quality.
Last question which I may make another thread for: How can I back up contacts, internet bookmarks, SMS and "memos" from a Samsung S5? I read that TWRP does not back these up, so I would need the location of the directory where these are stored. My google fu yielded somewhat vague answers from stackexchange, but no exact directories. If TWRP includes these in backup great, if not I would like to know if there is any kind of work around. MMS messages probably aren't that important, but contacts and memos really are. If I find any answers, I'll post back for others. Cheers!
Right, I realise people either know this, or don't care, but I did say I would post with anything I've found. I couldn't find the answers googling, so I was digging around in the file browser in TWRP.
- Almost everything in data/media - which isnt' backed up by TWRP - is exposed to MPT. I say almost everything, because some isn't, but I backed up the entire folder anyway with adb pull. This is the "internal SDcard" people mention in forums (internal memory partition, not an actual card). Simply copying from windows explorer grabs the files, but not with the correct directory structure. Best to use adb pull with the -a option to keep file attributes.
- Samsung memos, bookmarks (from the samsung internet browser), and contacts are not stored in /data/media. Rather these are in data/data. in the following places (absolute directories):
- memos: data/data/com.samsung.android.app.memo/databases/memo.db
- bookmarks: data/data/com.sec.android.app.sbrowser/databases/SBrowser.db
- contacts: data/data/com.android.providers.contacts/databases/contacts2.db
It seems TWRP does not back these up -I could be wrong though. Samsung's own utilities probably do but I have never used them. I don't know if google stores these either since I haven't used its backups to check.
I am still unclear of exactly what TWRO backup backs up. I understand that the /media folder is not included (downloads, photos, music etc..) but are app settings in data/data included?
BuriedCode said:
Right, I realise people either know this, or don't care, but I did say I would post with anything I've found. I couldn't find the answers googling, so I was digging around in the file browser in TWRP.
- Almost everything in data/media - which isnt' backed up by TWRP - is exposed to MPT. I say almost everything, because some isn't, but I backed up the entire folder anyway with adb pull. This is the "internal SDcard" people mention in forums (internal memory partition, not an actual card). Simply copying from windows explorer grabs the files, but not with the correct directory structure. Best to use adb pull with the -a option to keep file attributes.
- Samsung memos, bookmarks (from the samsung internet browser), and contacts are not stored in /data/media. Rather these are in data/data. in the following places (absolute directories):
- memos: data/data/com.samsung.android.app.memo/databases/memo.db
- bookmarks: data/data/com.sec.android.app.sbrowser/databases/SBrowser.db
- contacts: data/data/com.android.providers.contacts/databases/contacts2.db
It seems TWRP does not back these up -I could be wrong though. Samsung's own utilities probably do but I have never used them. I don't know if google stores these either since I haven't used its backups to check.
I am still unclear of exactly what TWRO backup backs up. I understand that the /media folder is not included (downloads, photos, music etc..) but are app settings in data/data included?
Click to expand...
Click to collapse
All app data is backed up in a twrp backup
If you were to restore a twrp backup your phone would be in exactly the same position as when the backup was created including app settings & data
The common partitions it will backup are system data cache & boot (kernel) - it can also backup (if included in the twrp.fstab) modem/efs & other partitions
The only things a twrp backup doesn't backup is personal files eg downloads music pictures documents etc
You can make a twrp backup & extract it on a pc - I'm sure there are guides which explain how to do this
TheFixItMan said:
All app data is backed up in a twrp backup
If you were to restore a twrp backup your phone would be in exactly the same position as when the backup was created including app settings & data
The common partitions it will backup are system data cache & boot (kernel) - it can also backup (if included in the twrp.fstab) modem/efs & other partitions
The only things a twrp backup doesn't backup is personal files eg downloads music pictures documents etc
You can make a twrp backup & extract it on a pc - I'm sure there are guides which explain how to do this
Click to expand...
Click to collapse
Excellent. Well I've manually (well, same directory structure) backed up pretty much everything I could think of anyway so even if the phone goes south, the media files are safe. I'll do a TWRP backup on my PC as well (just for easy restoring if I need to) I'm assuming this can only be done via adb? as the UI only gives options for internal or SDcard storage - which is another option.
I have some more questions as I am not sure how to proceed. Yes, everything is (or can be) backed up. But the phone still freezes which may or may not be a hardware issue. So I am stuck deciding:
1) looking for logs to attempt to diagnose the problem. Probably won't get me anywhere. logcat doesn't seem to work.
2) Just performing a factory reset from TWRP. Unsure exactly what this resets. Firmware? OS? wipes all apps?
3) Using Odin to flash stock firmware (I only have one large md5 file from updato.com for use with "AP"). Does this wipe apps and data? (I'm not including media files here).
In some forums people claim that user data (as in apps and app data) isn't wiped by using ODIN to update the firmware, others say it wipes absolutely everything. Whilst I have back ups I'd obviously prefer it to keep the apps and their data, assuming they aren't the cause of the problem. Apologies for so many questions, I probably don't need to know all the details, but I'm curious and cautious.
BuriedCode said:
Excellent. Well I've manually (well, same directory structure) backed up pretty much everything I could think of anyway so even if the phone goes south, the media files are safe. I'll do a TWRP backup on my PC as well (just for easy restoring if I need to) I'm assuming this can only be done via adb? as the UI only gives options for internal or SDcard storage - which is another option.
I have some more questions as I am not sure how to proceed. Yes, everything is (or can be) backed up. But the phone still freezes which may or may not be a hardware issue. So I am stuck deciding:
1) looking for logs to attempt to diagnose the problem. Probably won't get me anywhere. logcat doesn't seem to work.
2) Just performing a factory reset from TWRP. Unsure exactly what this resets. Firmware? OS? wipes all apps?
3) Using Odin to flash stock firmware (I only have one large md5 file from updato.com for use with "AP"). Does this wipe apps and data? (I'm not including media files here).
In some forums people claim that user data (as in apps and app data) isn't wiped by using ODIN to update the firmware, others say it wipes absolutely everything. Whilst I have back ups I'd obviously prefer it to keep the apps and their data, assuming they aren't the cause of the problem. Apologies for so many questions, I probably don't need to know all the details, but I'm curious and cautious.
Click to expand...
Click to collapse
Odin firmware images (unless custom made) do not wipe user data apps & settings however unless it's the same firmware as already on the phone it will most likely bootloop until you do a factory reset in stock recovery
This will erase all app data & settings but not internal storage unless the device was encrypted in which case all internal storage will be erased
For twrp if you want to flash a custom rom
If encrypted format data (option on right of wipe menu) This will erase all internal storage - then restart to recovery
Then once encryption removed or not encrypted to begin with
Wipe system (previous rom)
Wipe data (app data settings)
Wipe cache
Flash rom
Flash gapps
Flash root (optional)
Restart
So it looks like a firmware flash with ODIN is the way to go. As I've loaded on TWRP I can no longer see the firmware version that was on the stock recovery screen to check if I have the right image downloaded. Is there a way to see the firmware version from TWRP? I tried
Code:
adb shell getprop
Which had [ro.boot.bootloader]: [G900FXXU1CRH1] that I'm guessing is the firmware version, although the hit on sammobile doesn't mention the carrier (vodafone). If I search by region and carrier, I get a different version.
Update: Just tried to backup to a blank SD micro. It freezes and restarts 2% into it every time. Tried:
Code:
adb backup " -all -noshared -f "C:\phone backup.ab" "
And it said "now unlock your device to confirm action" but TWRP gave no such dialog. At this rate I can't actually do a proper backup of anything. Is there another way? I don't have enough space on internal storage. I guess I could try USB storage (USB memory stick with adapter).
BuriedCode said:
So it looks like a firmware flash with ODIN is the way to go. As I've loaded on TWRP I can no longer see the firmware version that was on the stock recovery screen to check if I have the right image downloaded. Is there a way to see the firmware version from TWRP? I tried
Code:
adb shell getprop
Which had [ro.boot.bootloader]: [G900FXXU1CRH1] that I'm guessing is the firmware version, although the hit on sammobile doesn't mention the carrier (vodafone). If I search by region and carrier, I get a different version.
Update: Just tried to backup to a blank SD micro. It freezes and restarts 2% into it every time. Tried:
Code:
adb backup " -all -noshared -f "C:\phone backup.ab" "
And it said "now unlock your device to confirm action" but TWRP gave no such dialog. At this rate I can't actually do a proper backup of anything. Is there another way? I don't have enough space on internal storage. I guess I could try USB storage (USB memory stick with adapter).
Click to expand...
Click to collapse
Just backup to internal storage or SD card & transfer to pc
Backup is stored in eg sdcard/twrp
The firmware you need is
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/BTU/download/G900FXXU1CRH1/233034/
Free downloads on sammobile will be back on Monday or find an alternative site
TheFixItMan said:
Just backup to internal storage or SD card & transfer to pc
Backup is stored in eg sdcard/twrp
The firmware you need is
https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/BTU/download/G900FXXU1CRH1/233034/
Free downloads on sammobile will be back on Monday or find an alternative site
Click to expand...
Click to collapse
I can't backup to SD card because it freezes at 2%. And using "adb backup " -f "C:\mybackup.ab" --twrp boot system data" " asks me to unlock my device - but TWRP doesn't show anything. On top of all that, it seems sammobile is under maintainance so I cannot download that firmware file until Monday Probably a good thing as it gives me a couple of days to keep trying to back up. Right now it gets into TWRP from recovery boot about one in 6 times. I'm out of idea's.
You can probably tell the frustration is real. Right now, I cannot use adb or twrp to backup onto internal storage (no space), the SDcard (crashes 2% into it, even with a blank SD card). It doesn't seem to crash whilst in TWRP, and I managed to pull the media folder off use "adb pull" so it seems it doesn't crash when using ADB commands.
So my only option before attempting to flash firmware is to make a backup via adb. However, I cannot get this to work at all. "adb backup --twrp" prompts me to unlock my phone, but the phone just displays the TWRP menu still. "adb backup -f "c:\backADB.ab" -noshared --twrp system boot data" tells me "adb: unable to open file c:\backADB.ab". Using simply "adb backup" puts me in the backup menu in TWRP, but then I can only change storage to internal or SDcard.
So either we can't yet backup to PC via adb and the TWRP documentation is out of date, or bugged. I'm on windows so I don't know if that makes it impossible - I just want to be able to get a backup on my PC's harddrive(s). Am I missing something with ADB?
Edit: it seems to now attempt to back up with "adb backup -f "c:\mybackup" --twrp system boot data" however.. this starts to back up and crashes at... 2%.
Just flashed the linked firmware with Odin after managing to get my apps backed up with my samsung account (the phone didn't crash for 15 minutes!). It cycled through "installing system update" restarting several times before hanging on the startup screen. I then pulled the battery, booted into stock recovery performed a factory reset (TWRP was gone). Now it is back in bootloop.
I installed TWRP again to use the file browser and my data has indeed been wiped (RIP). So what now? I could just let it boot loop and hope that it somehow gets back into android - it did that before, maybe one in 15 times. But I've done pretty much everything that has been recommended.
Rather than leave this thread hanging, I might as well post progress. After many *many* reboots interrupting the phone updating apps, it seems stable. It still occasionally crashes, but I can now make it crash and restart on demand by trying to install snapchat. It downloads it successfully and about a minute of "installing" the phone restarts, and reboots about 15 times before finally booting properly. I installed several other apps, none of which restarted the phone.
So, I'm going to get a new phone, and it seems that most things are backed up (please note, samsung doesn't back up contacts, shealth data, or splanner data despite claiming they do so). But I am curious as to what this problem could be. I have no experience debugging phone problems, and I realize it could be many things, but is there a way of checking the phones RAM (unlikely) or internal memory (flash, = more likely) for corruption? I may run a stress test to check if its power, CPU, or hover heating. If it passes that then it has to be memory usage.
Update: Today it only lasts a few minutes before it restarts. This is without any app updates - although I cannot be sure because I don't know whats going on in the background. This happens with, or without the SD card, and with both the new and old battery. I don't know where to start debugging. Any pointers?