Android native backup function is frustrating

Android native backup function is frustrating

By PC connection, you can transfer a full backup from one to the next Android Smartphone; at least in theory. Until we can present a perfect tutorial, here we list the most common faults for a failed backup of ADB.

The best backup apps for Android
Android app data secure with and without root
I can write often enough, that the backup system for Android is a disaster. While Apple users on new devices even enter your Apple ID and then completes their facility for all apps, we start Android users with every new device completely from scratch. We need to reconfigure every single app, chat histories are gone, forget old SMS.

At least the installation effort for apps should belong to thanks to a command in the command line program Android Debug Bridge (adb) the past. In theory, he backs up your apps and app data and packaged them so that you can completely transfer the backup on the new smartphone. He is as follows:

ADB backup-f FullBackup.ab apk-all

What sounds simple and efficient is, in practice is prone to errors and quickly ensures frustration. I needed about ten times, until I was able to recover at least some app configurations. But the majority remained on the old device and had to again on the new zero restores are.

smartphone Android usb pc 2
On the Mac, the backup is a bit less broken. / © ANDROIDPIT
Problem number 1: Windows
If your a Windows system; have at best a Windows 7 system, is less than 50 percent the probability of a functioning backup via ADB. Only with luck you can find working drivers and get the ADB tools up and running - consider that you need to create two Smartphone. If you are yet in a position to transfer command line commands to your Smartphone, you are a bit closer the goal. A tiny bit. Go to our guide:

Install ADB drivers and ADB tools in Windows
Error number 2: Incorrect parameters
Okay, good. Somehow you got ADB running. That's half the battle, right? Well no. The ADB tools are the next hurdle. The outdated set of white on black commands should ensure that your apps and their data, as well as your whole directories in the emulated sdcard directory from the old will be transferred to the new smartphone. So start on the old device by you typing the above mentioned command.

ADB backup-f FullBackup.ab apk-all

With the-f and the following file path, it determines where the backup will be written. With apk, you add the installation files of the apps. -all specifies that all of the apps are backed up. Furthermore, there is still the parameters - shared and nosystem, with which her includes the user directory and exclude system apps. In particular the latter parameter to avoid errors in some cases.

Warning: Some apps backup your app data in the internal file system, others in the shared. So you have to on the time-consuming variant with-shared-setting the parameters, you want to really save all app settings. Unfortunately, hence a lot is transferred filth, more used by any app.

ADB driver installer windows 10
For people with plenty of time: ADB on Windows. / © ANDROIDPIT
Problem number 3: Encryption
As soon as your backup starts, a message appears on your Smartphone. This prompts you to set a password. New Android devices you no longer has no password, since the device encryption requires also an encryption of backups. Taps so anything a and clicks "Save data".

ADB backup restore de
This dialogue is more harassment than help. / © ANDROIDPIT
An app IDs now appear under the beam, on which you have typed your thought out password. The real progress of this operation will never to see her. When this is over, the backup window will disappear, and for a few seconds, the bubble will appear at the bottom of "Backup completed successfully". That you look at this very moment on the screen, is however highly unlikely.

It now closes the new smartphone, you can play on the same backup from the command line.

ADB restore FullBackup.ab

A similar dialogue will also indicate the new smartphone you previously saw when you create the backup. Again, you need to enter just made-up encryption password. The writing backup restore on the lower right edge should be now visible. Here I failed for the first time.

What you're supposed to do? Removes the screen lock, because thus the encryption requirement of the backups is repealed. Now you can the backup step without E

Tweet