Re: [Automated] Wug's Galaxy Nexus Root Toolkit v1.4 (Updated 6/5
Thanks for being so diligent in supporting and debugging your wonderful program!
First, I read the caution about backing up system data, but I assumed (perhaps incorrectly), that since I was replacing one phone with an identical new one, that including both the system and shared data would be the closest thing to a complete image transfer. If I am incorrect in that assumption, please explain to me why in an identical phone-to-phone restore, one wouldn't want to include the system area too if only as an insurance policy to make sure everything is carried over?
One strange think I noticed about my backups which may or may not be related to this problem is that the "Shared data" backup is *larger* than the backup without "Shared data" checked. This doesn't seem logical. Note the backup with both "Shared" and "System" checked is larger than both others as one would expect.
Would it be possible to document (either here or elsewhere) what exactly is included in each of the 4 possible backup permutations (no option checked, Shared only, System only, Shared+System)?
Also is there any way for me to "unpackage" the backups on my pc so I can see what is there and compare to the files on the phone (using something like rsync or even 'diff -rq'). This would help me troubleshoot the problem initially reported.
Finally, on a related note, I got BackupPC (one of my favorite incremental backup programs that pools data) to work on the droid and I would like to know what partitions I need to back up to alternatively (1) Backup user data, downloaded applications, changed system & app settings (2) Complete phone image.
(note: The advantage of BackupPC is that it can use rsync to efficiently back up the droid or multiple different droids and only one copy of each distinct file is every stored (even if they have different names or other attributes)
Your assumption is correct regarding it's logic, however in my experience with android debug bridge, and even other backup utilities; system apps on android do not always respond well when you restore system data. This could be a limitation of adb, related to device security, or perhaps some of that data is actually stored in another partition like the sd-ext.
Regarding your observation of file size.. that is entirely normal. A backup without either option checked will be the smallest, a backup with shared data checked will be larger because it has all the things a normal backup does PLUS the shared data; and lastly a backup with both shared and system data will be the largest.
As far as I know there are no utilities to unpackage .ab files, especially if you password protected it. They can only be restored in a batch process. Google invented android debug bridge and therefore invented adb backup; they haven't released any tools to do that.
To be clear, we are not "debugging my program"; what you are experiencing is not a bug. These problems are related to adb backup, and the limitations of the backup options I provided.
If want to know about partitions;
User apps and data: /data/apps & /data/data & sometimes sd-ext
System apps: /system/apps
If you want to understand how to make a complete phone image, then I would recommend looking into how CWM recovery works.
My suggestion is to use my tool to backup and restore userdata. If you want something more full featured, you will have more options once unlocked and rooted, like making nandroids, which is the best backup solution.
If you want to use your backup program that's cool too. I understand what incremental backups are, that's cool that you made that work on your android device.
{{ WugFresh }}