abe makes not valid tar archives.

[MasterQ]

Hello,
i have tried to use your software for extracting an android backup file without password. But tar is telling me that the archive has no valid header. I'm using this command to extract:

java -jar extract/android-backup-extractor-20130526-bin/abe.jar unpack com.hz.game.cd.ab test.tar

output:
Strong AES encryption enabled
Magic: ANDROID BACKUP
Version: 1
Compressed: 1
Algorithm: none
119296 bytes read

The backup is created with Helium.
I did not get why the first line says "Strong AES encryption enabled" because the file locks very much as clear text, and i really did not use a password, but i'm not sure what helium is making with the file.
If you with i could send you the file via mail.

Thanks for your work.

Regards

MasterQ

[dragomerlin]

Hello, and sorry for the delay. Unfortunately, helium backups have a different format than standard adb backups. However, "adb restore" should work properly.

It says "Strong AES encryption enabled" because you have the "Oracle Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 7" installed. But I agree that should say allowed instead of enabled.

You can see that even if the tar is just not encrypted, the flag "Compressed: 1" was set at time of archive creating, which is helium thing. I've made a specific application for helium, however as I said extracted data is not valid a lot of times because is "encoded" differently:
https://sourceforge.net/projects/heliumbackupextractor/

[dragomerlin]

FIXED. Now says enabled instead of allowed.