So I recently came back to using ADB to backup my device and it worked perfectly with my HTC Desire 816, I mean the back up is all working and restore installs the apps and restores the app data's correctly.
But however on my ASUS Zenfone 3 it doesn't work when it comes to restoring, no errors but this is how it goes. So the backup worked it prompt the screen on my phone and I did the backup my device thingy, the .ab file us at a reasonable size around 8GB, but when I restore it prompts the screen as well and I click restore data then it takes a reasonable time as well around 5~10 minutes, and when I go to my app drawer nothing freaking shows up!!! I tried restarting my device and it doesn't show up, I've tried restoring again but it's the same!! PLEASE HELP ~~~~
The commands I use [same for both device]
Backup:
adb backup -apk -all -nosystem -f "mydirectory.ab"
Restore:
adb restore mydirectory.ab
Related
Hi there,
I had been on Android 5.0.1 and HATED it. It has so many issues with it that I decided to go back to 4.4.4 using fastboot.
I backed up my device using ADB beforehand, and then loaded the KitKat OS. Once I'd done I tried to restore my backup, and for some reason it won't let me because it's a different android version...
I used the command "adb backup -apk -shared -all -f c:\users\user\filename.ab" when backing up.
Has anyone got a way round this, or am I going to have to go back to 5.0.1, restore the backup, copy as much as I can to my computer without that backup method, then sideload back to 4.4.4 again? That's so long winded!
TY
droidsmanmk2 said:
Hi there,
I had been on Android 5.0.1 and HATED it. It has so many issues with it that I decided to go back to 4.4.4 using fastboot.
I backed up my device using ADB beforehand, and then loaded the KitKat OS. Once I'd done I tried to restore my backup, and for some reason it won't let me because it's a different android version...
I used the command "adb backup -apk -shared -all -f c:\users\user\filename.ab" when backing up.
Has anyone got a way round this, or am I going to have to go back to 5.0.1, restore the backup, copy as much as I can to my computer without that backup method, then sideload back to 4.4.4 again? That's so long winded!
TY
Click to expand...
Click to collapse
BUMP?
I guess I'll have to just take off all my photos, videos, app backups and music off bit by bit, then go back to 4.4.4 and copy them back over.
Ahh well.
Hi,
I have a droid turbo 2, and have all the backup and restore settings checked. I've had my phone connected overnight several times, but it seems to have barely backed up even the most basic stock apps. The Google Drive files are so small that I question whether anything is backed up (see attached pic). What am I doing wrong? Is there a way force a backup via brute force?
Anyone?
Is using adb to perform your backup possible? If so there are many guides on setting adb up then once you have a recognised device issue "adb backup -all -apk -system backup.ab. you could use the -shared or -noshared depending on if you want to backup internal storage. Then when you want to restore issue "adb restore backup.ab" thats the only fix I can suggest without more info.
I took a Nandroid backup of my OnePlus One shortly before it was sent to a watery grave. I got the Oneplus Three to replace it and I installed Titanium (I have the Pro version) in the hopes that I could restore my important information from my Nandroid. Now I know that Nandroid is a full image of the phone and so restoring everything is unwise as I'm on a different phone and OS. But I'd like to get back my app data in addition to the multiple app profiles I set up in Titanium.
Now Titanium WILL find the Nandroid backup I dragged over to the internal SD and it'll extract a list of the apps available to restore and whatnot. I can check them off and hit the restore button. A loading screen will come up that'll be stuck on 0% for a while and then after some time it'll immediately jump to 100% and tell me the batch backup completed. However, upon inspecting the app drawer nothing has changed. The only app I successfully restored was GasBuddy.
I DO have USB Debugging enabled and I have disabled "Mount Namespace Separation" in SuperSu.
bump
I used to use TitaniumBackup to transfer apps and data from one Android phone to another when both devices are rooted. Recently I got a phone which currently does not have root access, so TitaniumBackup would not be useful. Most apps are not an issue, but I have trouble transferring a few apps and their data.
I was thinking to use adb to backup each app+data separately on the old phone (and then to restore it in the new phone), and tried the following command on the old (and rooted) phone:
adb backup -f <appname>.ab -apk <app_package_name>
but I got the following message:
Now unlock your device and confirm the backup operation.
The strange thing is that there is nothing there for me to accept when I unlock the phone or when I keep the phone unlocked.
Also when backing up all apps via "adb backup -apk -shared -all -f all.ab", I still get the same message: Now unlock your device and confirm the backup operation. And this happens on two computers I have tried so far. Very weird.
I just tried another phone, and had no problem with the adb backup command (I did see the confirmation request on the phone). So the problem seems to be with this particular phone (LG G2 with root).
Any suggestions as to how to handle the transfer? Any better alternatives to transfer a few apps+data from one phone to another?
I have used ADB to backup data and apps on all of my devices for a couple of years. It is very reliable and the backups for individual app can be restored across devices without issue. It is preferable to using Titanium Backup, especially since that program is no longer reliable since the inception of A12. It is especially handy when the device is not rooted. But until recently, it always worked whether the device is rooted or unrooted. Today, while preparing to install the latest A12 update on my T870, I attempted do a backup of my favorite game, it would go through the motions and create the backup file. However, I knew immediately that the file was not correct because it was only 1K in size. The same game on my phone creates a 500 Mb file. My tablet was rooted using the Magisk/boot.img method but that hasn't made a difference in the past on any device. I wasn't overly concerned because I tested restoring the phone version of the backup to my tablet and it worked just fine. I went ahead and did a clean install of the latest A12 update, debloated my tablet and restored my backups via. ADB. everything is copacetic. The only difference is I did not root my tablet this time. I suspect if I do I will have the same issue. Not a big deal since rooting holds much less importance for me than it once did.
Command used to backup - adb backup -apk com.crossword.bible.cookies.find.english -f com.crossword.bible.cookies.find.english.adb
Restore command - adb restore com.crossword.bible.cookies.find.english.adb
Same commands used in both the successful and unsuccessful backups.
Thoughts anybody?