Related
I don't know if I'm the only one having this issue, but I'd figure I'd lay out my findings for everyone to see if we can get to the bottom of it. Since the EB01 leak was released, I've noticed that after a while my installed apps will not remember their preferences anymore, think everytime is the first run, etc...
First time I flashed EB01 was using ROM Manager and an old "green" version of CWM. After the first instance of these issues cropping up, I went back DI01 using a FULL Odin restore (rom, kernel, radio, novinand, etc, w/ re-partitioning), then flashed to an EB01+CWM+Root package using Odin instead of CWM. Again, after a day or two, apps started forgetting their preferences. I then got a new phone as a warranty replacement, went from EA28 to EB01 using Odin: still having the same issues.
The only thing I noticed out of place (I'm no developer) in a logcat trace is:
Code:
Line 745: E/ApplicationContext(31797): Couldn't rename file /dbdata/databases/com.speedsoftware.rootexplorer/shared_prefs/com.speedsoftware.rootexplorer_preferences.xml to backup file /dbdata/databases/com.speedsoftware.rootexplorer/shared_prefs/com.speedsoftware.rootexplorer_preferences.xml.bak
Line 745: E/ApplicationContext(31797): Couldn't rename file /dbdata/databases/com.speedsoftware.rootexplorer/shared_prefs/com.speedsoftware.rootexplorer_preferences.xml to backup file /dbdata/databases/com.speedsoftware.rootexplorer/shared_prefs/com.speedsoftware.rootexplorer_preferences.xml.bak
Line 745: E/ApplicationContext(31797): Couldn't rename file /dbdata/databases/com.speedsoftware.rootexplorer/shared_prefs/com.speedsoftware.rootexplorer_preferences.xml to backup file /dbdata/databases/com.speedsoftware.rootexplorer/shared_prefs/com.speedsoftware.rootexplorer_preferences.xml.bak
Line 745: E/ApplicationContext(31797): Couldn't rename file /dbdata/databases/com.speedsoftware.rootexplorer/shared_prefs/com.speedsoftware.rootexplorer_preferences.xml to backup file /dbdata/databases/com.speedsoftware.rootexplorer/shared_prefs/com.speedsoftware.rootexplorer_preferences.xml.bak
Just a few other things I've noticed
*System application do not seem to be affected
*/dbdata/databases/ is full if entries for apps that are no longer installed. I don't know if that is normal or if they are supposed to be cleared out when an app is removed.
*deleting the entry in /dbdata/databases/ for a particular app seems to force it re-create the entry, allowing it save it's preferences.....until they change again.
*reading from dbdata seems to work fine, just writing isn't working.
*only certain apps seem to act up. The first ones to show signs of issues are usually Tapatalk, Root Explorer, & Titanium Backup. Apps like Dropbox and Facebook don't seem to be affected this time around.
I question weather this a corruption due to the installation method (outdated CWM) or a bug in EB01 itself and only folks who add/delete apps frequently like myself are more prone to notice it.
Thoughts?
First, this shouldn't be posted here. This has nothing to do with Development, so it should have gone in the General forum.
Next, have you tried to do a factory reset after the issue pops up and try again? I realize that you did the full Odin wipe, but did you try wiping data anyway? Also, are you on Voodoo or no-voodoo?
1. Apologies, I figured since this was an issue with software under development and is likely a code issue, that it belongs here more than anywhere.
2. Yes, many wipes of data & cache partitions, restores to DI01, etc. The full restore & re-formatting was a last resort. Plus, it's doing the same thing with an entirely new device.
3. Non-voodoo
What I would suggest is reset your phone and reset your data restoring, AKA clearing it from google's servers the best way to do that is reflash a froyo rom, wipe all the cache's and then when it asks you to login with your google account skip that step and then login using Settings->Accounts & Sync add your google account And then in Settings->Privacy Uncheck Backup my data and Automatic Restore. There is a chance there is a app or a setting being pulled from google that could be screwing it up, you could also try formating your SD card.
You mentioned Titanium Backup. It has an "Auto-sync TB settings" is supposed to auto restore it's settings from the SD card after a wipe. Maybe you have a setting in there that is causing an auto-restore to happen of the data from some of your apps.
And definitely check to make sure that you don't have Automatic Restore checked in Settings->Privacy. The best way to do this is just like jazzyjames mentioned. After a wipe, don't log into Google on the first boot, but first go in and uncheck the auto restore. Then you can log into your Google account.
It happens to those who use voodoo, but it was worse with 2.2 for some reason.
I fixed it using and all in one odin 2.2 version. It'll repartition the file system and restore your dbdata.
Done problem solved...
I found the Google Auto-Restore was enabled, so I disabled it to clear everything and did a factory wipe and re-did everything with pretty much every automated backup or sync service turned off.
We'll see how things go.
Hello,
I literally installed the Facebook app from Google Play on my Nexus 4 hours ago and then my phone literally went blank. Eventually my phone was turned off as there was no more battery. I charged it and powered it but it no longer boots (it has been stuck at the X screen for hours). Is it possible to backup my files despite this so I can try to reinstall a custom ROM/unroot my Nexus 4?
I spent some time searching the forums and couldn't find the answer, so any response would be helpful and appreciated. Thanks.
One of the suggestions here might help you as well:
http://forum.xda-developers.com/nexus-4/help/access-device-computer-cracked-screen-t2885335
Do let know if it doesn't!
oopsy said:
Hello,
I literally installed the Facebook app from Google Play on my Nexus 4 hours ago and then my phone literally went blank. Eventually my phone was turned off as there was no more battery. I charged it and powered it but it no longer boots (it has been stuck at the X screen for hours). Is it possible to backup my files despite this so I can try to reinstall a custom ROM/unroot my Nexus 4?
I spent some time searching the forums and couldn't find the answer, so any response would be helpful and appreciated. Thanks.
Click to expand...
Click to collapse
Maybe, it depends if you can boot into recovery and have a custom recovery
Sent from my Nexus 5 using XDA Free mobile app
SirHat said:
One of the suggestions here might help you as well:
http://forum.xda-developers.com/nexus-4/help/access-device-computer-cracked-screen-t2885335
Do let know if it doesn't!
Click to expand...
Click to collapse
Thanks I'm actually trying something from here.
jd1639 said:
Maybe, it depends if you can boot into recovery and have a custom recovery
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I can. I am running on TWRP v2.3.2.3 but I don't think I can access the files through ADB as I did not set it to Development Mode (ever). It seems I can actually back it up through TWRP, but my concern is I don't know how to extract it out of my phone because once I reinstall JB everything will be wiped right?
Once I reinstall a JB version that means everything will be erased. Does anyone how to keep that backup from TWRP if you can't take it out from your phone? It appears my version doesn't seem to have Nandroid.
Also, does anyone know if it's "System" that stores all the contacts/text messages?
I want to backup my Data folder too but I only have 900mb free space left on my phone (I have the 8gb version) and my Data file is about 1.5gb. I don't remember if I have anything valuable in my Data file that I need to recover, so just to be sure, does anyone know if I can explore my "Data" folder to remove content to make it smaller so I can back it up? Thanks.
ADB via recovery should be the way to go then.
Did you try something as an ADB file manager?
See: https://github.com/sole/aafm for example.
This should allow you to copy the files to your PC without having to backing them up first on the device itself.
An alternative way would be to connect to the (ADB) shell, delete some useless files.. like music and stuff you already have (or package music as one archive - download - delete) etc. Till you have enough to package the data directory in one go. If done right the archive should preserve file permissions which is an extra plus I guess.
The way I try to make sure I don't have a problem like this is:
- Letting TitaniumBackup backup all important applications + data every night @ 4 AM when it's charging (while I am sleeping).
- Use FolderSync to sync the new backups to a server I have running. Could also be cloud of course. (Only on Wifi and while charging)
Good luck!
If you can boot into recovery it might be possible to pull data there.
Also, if you know which ROM was installed, you can try just flashing the system partition of respective ROM. It might not fix your issue but might allow you to boot and backup your data prior to completely resetting everything.
I've had something similar once. Tried all kind of solutions via recovery/fastboot/adb and only flashing a clean system image allowed me to recover important data. The phone was unusable still (constant FC's) but it allowed me to establish an adb connection and pull all data I didn't want to lose.
Sent from my Nexus 4 using XDA Free mobile app
Problem Solved, didn't follow any of the suggestions. Thanks though.
If you can, please do put your solution here so other people with a similar problem can use search and find the solution. Thanks!
SirHat said:
If you can, please do put your solution here so other people with a similar problem can use search and find the solution. Thanks!
Click to expand...
Click to collapse
To be honest, I actually didn't. I decided to perform a reset and lose my data (and reinstall my ROM) as I didn't have the patience to experiment and figure it out. I just don't have time for that.
So I ran into an issue with my locked-bootloader, unrooted MXPE 2015. I am running stock Marshmallow. I will note that I don't think this is really a bootloop, it seems to boot for a few seconds before a crash/reboot. I am able to boot into recovery, and am even able to trigger a safe-mode boot during the few seconds of uptime, where the safe-mode boot does not crash/reboot. I also suspect a Factory Reset will fully resolve the issue, unless the factory image got corrupted somehow... I do apologize, this is a long post.
I was essentially trying to make a backup to do a factory reset. Long story short, I was trying to use an app called Easy Backup that consolidates sms, mms, call logs, and that I had used in the past without issue. However this time that was not the case. I have a 16 GB version with an SD card, but have used ~8.5 GB of the internal free ~9.8 GB (I can't remember the exact numbers) and I constantly run into low storage situations with app caches and install sizes when doing updates. Normally clearing all app cache data is enough to get the downloads to go through.
So I go to run this backup app (with the default storage directory set on my external SD card) to have it uploaded to Google Drive, and after it gets close to finishing, I get errors about running out of storage, and then a cascade of apps crashing, and then a reboot. After the reboot, I check my Drive folder and see that the file never uploaded; the storage seems to have cleared up, but I clear my cache and the backup app's storage just in case (though it had already pretty much cleared back to the 8.5 GB used from before). I also notice some oddities like random settings suddenly having changed in certain apps. But I stupidly think no harm has been done, so maybe retrying after clearing up Cache space will work. So I tried to get the backup to run again after verifying the upload and storage location options (SD Card -not internal - and G Drive), but the same storage and crashing thing happens. It "finishes" the backup, and after a few seconds of the phone hanging and lagging, it reboots again. This time after the reboot I notice that apps are missing from my Nova Launcher home screen (but still in my app drawer), and go to restore a backup of Nova, except the overview and home buttons don't do anything, and then see that the notification shade can't be pulled to open the settings toggles. Then it suddenly reboots again. And now, unless I boot into safe mode, I get a few seconds of of it sitting at the home screen before the phone reboots. This same nav button and settings shade behavior are persistent in safe mode.
I guess my question is whether or not there is a way to pull off my SMS, MMS, Call log data (maybe in ADB?) while in safe mode. I have been trying to uninstall extraneous apps in Safe Mode to see if I can break the rebooting cycle, but no luck thus far.
On another note, should I go ahead and do a factory reset or should I contact Moto first (I have a Moto Care policy, though I've heard horror stories). I have never had this issue with this app before,
Any other recommendations and tips? It almost seems like the app tries to cache on my internal storage before moving to the destination folder, and in a low storage situation it seems to have corrupted something in the actual OS as well as my other apps.
Thank you, I appreciate your time!
If memory serves, apps like Easy Backup may store things on external storage or upload to the cloud, but use app cache space as temporary working space, thus most likely causing your storage issue. Erasing app cache likely wiped that out, and your are correct that a factory reset will likely clear up this issue.
Moto care doesn't care if an app messed up your system, and they won't help you with it other than to walk you through a factory reset first before sending the device in for replacement, as I suspect a factory reset will clear your issues up.
Have you tried clearing the cache partition in recovery?
Recovering your data will be impossible if you can't get it booted long enough to enable ADB and copy the files off.
If you can get if booted, I suggest using SMS Backup & Restore over your existing backup tool for this type of data... I have used it successfully for many years without issues (except when they accidentally had it set by default to delete all but the last 2 backup file on Google Drive, geesh, that sucked, but that isn't an issue anymore).
acejavelin said:
If memory serves, apps like Easy Backup may store things on external storage or upload to the cloud, but use app cache space as temporary working space, thus most likely causing your storage issue. Erasing app cache likely wiped that out, and your are correct that a factory reset will likely clear up this issue.
Moto care doesn't care if an app messed up your system, and they won't help you with it other than to walk you through a factory reset first before sending the device in for replacement, as I suspect a factory reset will clear your issues up.
Have you tried clearing the cache partition in recovery?
Recovering your data will be impossible if you can't get it booted long enough to enable ADB and copy the files off.
If you can get if booted, I suggest using SMS Backup & Restore over your existing backup tool for this type of data... I have used it successfully for many years without issues (except when they accidentally had it set by default to delete all but the last 2 backup file on Google Drive, geesh, that sucked, but that isn't an issue anymore).
Click to expand...
Click to collapse
Yes, I did try cleaning the cache partition, but to no avail. Ironically because I was messing with ROMs on my old 2013 moto x, I'm currently using that with CM 13. When I get back from work tonight I'll see about ADB, I think I may have set it up on it in the past, however I may have deactivated it. And yeah, I think I may have used that tool in the past, so I'll have to give it another look!
I thought that the Moto Care route may not be worth it, but I thought that I might as well check. If a reset doesn't solve things, I'll take another look. Thanks for the help, really appreciate it!
acejavelin said:
If memory serves, apps like Easy Backup may store things on external storage or upload to the cloud, but use app cache space as temporary working space, thus most likely causing your storage issue. Erasing app cache likely wiped that out, and your are correct that a factory reset will likely clear up this issue.
Moto care doesn't care if an app messed up your system, and they won't help you with it other than to walk you through a factory reset first before sending the device in for replacement, as I suspect a factory reset will clear your issues up.
Have you tried clearing the cache partition in recovery?
Recovering your data will be impossible if you can't get it booted long enough to enable ADB and copy the files off.
If you can get if booted, I suggest using SMS Backup & Restore over your existing backup tool for this type of data... I have used it successfully for many years without issues (except when they accidentally had it set by default to delete all but the last 2 backup file on Google Drive, geesh, that sucked, but that isn't an issue anymore).
Click to expand...
Click to collapse
So I did get in and take another look, however developer options just shows "Developer permissions not available for this user." So I think i may be hosed. I'll give it another go and see what I can try to salvage from booting into safe mode again. Thank you for the help and recommendations, this willteach me not to be using something like SMS backup instead (and consistently, haha).
jtflynnz said:
So I did get in and take another look, however developer options just shows "Developer permissions not available for this user." So I think i may be hosed. I'll give it another go and see what I can try to salvage from booting into safe mode again. Thank you for the help and recommendations, this willteach me not to be using something like SMS backup instead (and consistently, haha).
Click to expand...
Click to collapse
Sounds like you are in a Guest user account, can you switch users?
acejavelin said:
Sounds like you are in a Guest user account, can you switch users?
Click to expand...
Click to collapse
So I looked at that, and it says I am logged into my account. Photos below:
So coincidentally, I just got it connected to my wifi while in safe mode, and it hasn't crashed/rebooted since that (it still was doing that prior). I can get into the play store, so I am going to try to get my sms/call logs/mms. Home and overview buttons are still broken, and the notification shade is still borked. So No ADB backup, but at least I have most things on my SD card and was on MM, so the app backups should help get restarted. Once I get everything checked/backed-up that I can, I'll try a factory reeset, and failing that a call to moto care *cringes*.
Thanks for the help everyone! I learned my lesson on small-storage phones...
jtflynnz said:
So I looked at that, and it says I am logged into my account. Photos below:
So coincidentally, I just got it connected to my wifi while in safe mode, and it hasn't crashed/rebooted since that (it still was doing that prior). I can get into the play store, so I am going to try to get my sms/call logs/mms. Home and overview buttons are still broken, and the notification shade is still borked. So No ADB backup, but at least I have most things on my SD card and was on MM, so the app backups should help get restarted. Once I get everything checked/backed-up that I can, I'll try a factory reeset, and failing that a call to moto care *cringes*.
Thanks for the help everyone! I learned my lesson on small-storage phones...
Click to expand...
Click to collapse
Do you have a corporate account on the device that is a Device Administrator? That is the only other thing I can think of that could cause something like that.
acejavelin said:
Do you have a corporate account on the device that is a Device Administrator? That is the only other thing I can think of that could cause something like that.
Click to expand...
Click to collapse
No, nothing like that. It's my own personal device with no work emails, and in fact I had previously used USB debugging to backup pictures when my SD Card got corrupted. All of this weirdness occured after the failed backups, and just speculating it honestly seems like when the app ran out of room it just kept going and started overwriting random bits (ie the Nova Launcher settings/ homescreen), and might be why the Navigation buttons/Notification shade are broken. But that's just me spit-balling , so really there might be no telling what happened.
jtflynnz said:
No, nothing like that. It's my own personal device with no work emails, and in fact I had previously used USB debugging to backup pictures when my SD Card got corrupted. All of this weirdness occured after the failed backups, and just speculating it honestly seems like when the app ran out of room it just kept going and started overwriting random bits (ie the Nova Launcher settings/ homescreen), and might be why the Navigation buttons/Notification shade are broken. But that's just me spit-balling , so really there might be no telling what happened.
Click to expand...
Click to collapse
Well... Try to get off what you can, then factory reset, I imagine things will improve greatly.
I just had an issue similar to this... phone (1575) would reboot (continuous reboot) after about 30-45 seconds every time (reminded me of TV show Lost where you had only a certain amount of time before you had to reset)... enough to uninstall a GPS app I was tinkering with a few hours prior... enough to delete cache... enough to reboot into recover to wipe cache partition... about 4 reboots to finally download a Google app update (which in the end said it couldn't successfully install) etc. Sometimes powering off would reboot instead (and after a while could not reboot into safe mode, just a normal reboot) so the few times I had the phone off, I took out/reset the SIM and SD card. What seemed to solve it was taking out the SD card (formatted as External, but was always a pain -- a week or so ago it "disappeared" and had to reformat the SD card (just downloaded stuff)) and when I powered it up this morning, no more reboots. Of course for now, no more added storage But saved me a full factory reset.
I assume this is possible. Usually I would do this with TWRP (which you can do), but this method does not require root necessarily.
I want a backup I can restore in case things go sideways.
I managed to do this. Here are the basic instructions.
Have developer options available, select USB debugging. On PC, install minimal adb and fastboot, install essential drivers. Connect phone to PC, select transfer files MTP under USB connected options in notifications. If USB debugging prompt prompts up on phone, check alway allow and ok.
Run cmd.exe as admin and navigate to you ADB install directory. Type "adb root" if rooted or just "adb" if not. ADB should start.
Type adb backup -system -apk -shared -all -f C:\filenameyouchoose.ab
On the phone, type a password for encryption if wanted and touch Back Up My Data.
Presto, now all that's left is to wait. The -apk is to back up apps and -shared is to backup internal SD card data. Change those if you don't want that data backed up.
The command to restore the backup is adb restore C:\filenameyouchoose.ab
Full XDA guide here: https://forum.xda-developers.com/galaxy-nexus/general/guide-phone-backup-unlock-root-t1420351
Thanks! I'm attempting this procedure for the first time. I am at the place where I am supposed to enter a password to encrypt my backup. The "Back Up My Data" button does nothing. I've tapped all over and around it. The "Do Not Backup" button works just fine and it cancels the operation instantly. My adb session ends. If I tap all over the "Back Up My Data" eventually the operation times out. What could I possibly be doing wrong? Has anyone ever seen this behavior before? (It's super hard to troubleshoot problems with no feedback or error codes.)
I set a desktop backup password in developer options. It still wouldn't go. Then I rebooted and it worked after a fresh boot. Not sure why. I hope that is helpful to someone.
Grep_The_Truth said:
Thanks! I'm attempting this procedure for the first time. I am at the place where I am supposed to enter a password to encrypt my backup. The "Back Up My Data" button does nothing. I've tapped all over and around it. The "Do Not Backup" button works just fine and it cancels the operation instantly. My adb session ends. If I tap all over the "Back Up My Data" eventually the operation times out. What could I possibly be doing wrong? Has anyone ever seen this behavior before? (It's super hard to troubleshoot problems with no feedback or error codes.)
Click to expand...
Click to collapse
Oh, while I was typing out the message, seems you already solved it.
Previous message: I had similar issue when I was trying to install apps using apk(s) files. It turned out to be the app Twilight app which didn't allow me to click install button except cancel: "The prompt for screen overlay detected is presented when an installed application is allowed to Draw over other apps is running in the background" See if your issue has something to do with an app.
Charkatak said:
...It turned out to be the app Twilight app...
Click to expand...
Click to collapse
Brilliant! That was it. Jolly good show, sir!
File size of backup
Just wondering if anyone gets vastly different file sizes when they do a complete backup? The first time i tried this i got a backup file of about 600mb. I did it again with a different file name to the same folder and it was double the size. The third time i tried it was back to the original smaller size. My fear is that this is not a reliable means for complete backup. Is there any way of seeing whats inside this backup?
I have stumbled upon this command and my question is, is this as powerful as a nandroid backup? Since we don't have permanent TWRP (Yet?), I feel really unsafe while messing with the phone (The whole A/B thing which I still need to get used to doesn't help either) and considering the times nandroid backup saved my device I could really use something equally powerful to fall back on.
I tried the ADB backup and it took a while and generated a ~10GB file for me, but restoring to a new phone didn't work. No errors or anything, it just went real fast and didn't seem to do anything. I didn't care to try to investigate it because I just needed to get my new phone up and send the broken one back.
I ended up using TWRP from the boot partition (obviously not backing up boot), then installing twrp on boot on the new phone and restoring the system and data, next copying the sdcard contents to the computer using adb pull and adb push onto the new phone, finally flashing the correct boot.img, and I was back up and running on a replacement phone right where I left off on the old one. ...
One caveat is if your old phone is on a different firmware you have to update the new phone to match before all this.
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?