New answers tagged

0

First of all, be advised that Nandroid backups, in some situations aren't able to backup the "boot.img" properly, or isn't able to properly restore the "boot.img", even if it was backed up properly. When either of that happens, you're going to end up stuck like the way you are at the moment. The issue you're facing can also turn up, in case the partitioning ...


0

Most of the answers have become a bit dated so here is an update: Nandroid Manager doesn't seem to be developed any more and doesn't work reliably with the latest versions of Android anymore. But it's worth a try. In my case, about half of my apps were successfully restored and for most of the ones where "restore app + data" failed, "restore data" alone ...


0

Use adb logcat command to check system log for exceptions during the restore process. Try looking for BackupManagerService messages like these: I/BackupManagerService( 716): Reusing existing agent instance D/BackupManagerService( 716): Invoking agent to restore file fbreader.ui.xml E/BackupManagerService( 716): Unknown tar entity type: 76 ...


3

Wiping /data If you were upgrading Android versions, the OTA might not have wiped your /data partition properly, and this may cause the issues that you describe. You should first try to perform a factory reset to see if that resolves the issue. One way to do this is through Settings > Backup & reset > Factory data reset. If you can't access your ...


1

It's because the files within the com.koushikdutta.backup/files are deleted whenever 1) you uninstall helium backup or 2) phone is factory reset. If those files are missing, helium backup will fail to recognize any of your backups, even if they exist and is easily restorable. Requiring those files to exist in order to restore backups is honestly quite a ...



Top 50 recent answers are included