Either there is something wrong with abe.jar or with .ab and .tar files.
.ab were created using Helium and uploaded to dropbox, then downloaded locally
When I unpack it - resulting .tar files is wrong for some reason.
Then I get another backup .tar.gz using ultimate backup, unpacked gz to tar and tested that .tar to check if it is ok.
It was ok with /data/data structure and files in it.
When I pack it - resulting .ab has header and garbage after that. And Helium can't restore it.
What can be wrong?
They made some custom and probably more convinient way to backup using adb backup with tar files. The problem is that it is really hard to convert any backup (titanium or ultimate) for it to accept. I don't think it is bug, it is just some strange usage of adb backup. This means even if Helium creates .ab backup really it is not in that format... Or it is just unencrypted or uncompressed. And I don't have openssl and cygwin to confirm it.
---------- Post added at 01:20 AM ---------- Previous post was at 01:17 AM ----------
Yes. It looks like .ab created by Helium is just tar with ANDROID BACKUP header. Not encrypted, not compressed. Is it possible to create pack/unpack for such format?
|Thread Tools||Search this Thread|