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?
Related
Hi,
My dad just got himself a new phone and now it's my task to set him up with his apps on the new Phone.
My trouble is that I can't find a solution that back up App AND Data.
I have always had my phones rooted from Day 1 so i had an easy Titanium Backup+Restore and don't know about non-root methods.
Rooting is not really an option as my dad won't let me because he thinks it will break everything :
I searched and found Helium Backup which would be what i need, except that it only works on 4.x+
Do you know a Root-free backup&restore for the Transition from a
2.2 Motorola Defy
to a
4.0/4.1 Motorola Razr i ?
thank you in advance and thanks will follow
btw: why doesn't android simply backup all your data along with your contacts etc...?
There is a way to save your whole phone without root, you have to use adb.
Use this command:
Code:
adb backup –all -apk -shared –f c:\backup.ab
It will save all your data, apps and the internal or external storage.
Baasi said:
There is a way to save your whole phone without root, you have to use adb.
Use this command:
Code:
adb backup –all -apk -shared –f c:\backup.ab
It will save all your data, apps and the internal or external storage.
Click to expand...
Click to collapse
thanks, do you also know, how to restore them with data onto an unrooted 4.1 phone ?
something along
adb restore –all -apk -shared –f c:\backup.ab ?
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.
Hello
I own a Samsung Note 4 SM-910A. It is unlocked, (but unfortunately bootlocked because of ATT policy), unrooted and used internationally by me both at home and internationally using a variety of SIMs.
I backed up my device using adb and successfully created a backup file xxx.ab of about 3.2GB
I then updated the android baseband to ..DOI4 from ..DOI3 (the goal is to get to MM).
I wanted to make sure the backup would restore before going all the way up the update list. So i tried to restore my data.
I now find that adb will not restore my data. The only clues I have... The message in the DOS command window on my PC: “Now unlock your device and confirm the restore operation”
And a message on the phone stating that the restore has started then finished after a few seconds.
“Restore starting... Restore ending...”
Questions:
1. Is there a log file that I can read that might give me a clue as to why adb has failed? If the answer is logcat – how do I find actual failure messages in this vast logfile?
2. Are backups from different basebands, but on the same phone compatible?
Any help appreciated.
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
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?