Exception on big backup (~6GB) about android-backup-extractor HOT 7 CLOSED

Hi,

Thanks for trying the tool out.

I've only tested with a couple of GB, IIRC, so this is new. It might be a bug in the JVM, but it's also quite close to 4GB, so I have to ask: what OS are you running this on? Additionally, you might want to try running this from the command line directly (not Eclipse), and maybe increase the heap size, although the program shouldn't need too much memory. I will check the JB code and see if there are any changes in the original code that might be relevant.

Additionally, there is also a Perl implementation (not by me), so you might want to try that out too, in case this is JVM/OS related.

http://forum.xda-developers.com/showthread.php?p=27840175#post27840175

from android-backup-extractor.

Thank you.

I'm running windows XP, with NTFS filesystem (so >4GB files are not a problem).

I tried the problem by unpacking it as it was uncompressed (forcing inCompressed = false), then inflating it with a simple C# program: I have the same problem in the same point.

So: the backup is corrupted.
Or: the AOSP implementation of java.util.zip has problems, maybe using it would solve.

Thank you.

from android-backup-extractor.

How did you create your backup? There was bug ICS that wouldn't properly compress shared storage contents (if you specified the '-shared' option), maybe that is related. The Perl tool I linked has a script that tries to fix this, but it might need some work.

from android-backup-extractor.

It was with ICS and with -shared.

Thank you.

from android-backup-extractor.

Here's the Android issue, is has some more details:

http://code.google.com/p/android/issues/detail?id=28303

from android-backup-extractor.

Thanks for this work!

FWIW I was able to unpack a 2.3GB backup.ab created via 'adb backup -noshared -all -system' on Ubuntu 12.10 (32-bit) running adb version 1.0.29 and your code compiled with the default OpenJDK package (had to delete the third parameter of the DeflaterOutputStream ctor in AndroidBackup.java, maybe due to OpenJDK?). BTW, Samsung Galaxy S2 [SGH-I727] running AT&T flavor of ICE (4.0.4).

When I ran adb with -shared I ended up with a 4.9GB backup.ab which produced the 'invalid stored block lengths' reported by neclepsio. So seems Android (your last link) is at issue.

from android-backup-extractor.

Glad it worked for you. There are no inherent limits to backup size, and the app should be reading it in batches, so not much memory is required. As for the DeflaterOutputStream parameter, it was introduced in Java 7, so if you got compiler errors your JDK version is probably still 6 .

The -shared issues has been fixed in Jelly Bean, but is quite annoying nonetheless. Fixing the broken backups is a bit tricky, but not impossible, albeit somewhat hard to do automatically.

from android-backup-extractor.