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.
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 ?
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?
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
How to recover data from "adb backup --twrp" archive? Been through hell and back
I have two backups I made using "adb backup --twrp" while my OnePlus one phone was in TWRP recovery 3.2.1-0 running LineageOS with a recent build (don't know exactly which one, but it was from Feb/March 2018). Each of the backups are about 6.0GB so they appear to be complete backups. I am trying to recover one app and its data (Signal/Textsecure) but the rest would be nice too. The backup files have .ab extensions. I am fairly android savvy and have been working on this for days, your help is VERY MUCH APPRECIATED! I have access to Windows and Linux.
I have tried the following:
-"adb restore filename.ab" while in TWRP recovery. It appears to restore (progress bar goes, it reports success, etc), but no apps are restored. I have tried this both with totally wiped partitions/system/data and with a fresh install of LineageOS. As far as I can tell, nothing happens. When doing a restore after a full wipe and trying to restart, TWRP warns that no OS is installed.
-Restoring using the restore menu in TWRP. Immediately upon clicking on the backup, the phone restarts and TWRP opens again. Not sure what's going on there.
-Opening the backups in Titanium Backup, Nandroid manager, and a few other apps. None of them worked. Titanium backup crashes instantly in recover from ADB, doesn't recognize the backups in nandroid recovery mode.
-Opening the .ab files in an archive manager, all of which report it isn't a valid tar archive. One time I was able to get a list of directories, and things looked pretty right, so I know at least some of the data should be there. Running variants of this command with different skip values, none of which produces a valid tar file dd if=file.ab bs=512 skip=1 of=test.tar
Questions:
- Is there a way to extract data from these backups in Linux or Windows outside of Android? From what I read, TWRP adds some stuff in the headers which makes them invalid tar files, and that doing "adb backup --twrp" is different from a regular TWRP backup.
- Why is TWRP crashing? Is there a log I can look at for this and how? Maybe i can find a way to diagnose it that way.
- Where does Signal store message data? I have a flat-file backup that may have this information depending on where it's stored.
- Can I somehow convert these backups to a different format that might be better-tolerated by TWRP or other apps?
- Any good utilities for reading a corrupted tar file? I think all this utility would need to do is skip through the junk at the start.
I use PE custom rom and I have tried to backup app data without success. Adb commands works fine but when I have restored backup, I can't find any backup app icons on my phone. What I doing wrong?
adb backup -f app.backup -all -apk -nosystem
adb restore app.backup
The sad reality is that ADB actually listens to app manifests when they request that userdata not be backed up. It'll only restore the apps themselves, even if you encrypt the backup. To backup app data these days, you need root access and an app that can handle the backup/restore procedure via root.