ybk

as indicated above, the helium backup is completely useless if google ade backup is working. only one case I had to use helium backup - an early android where system backup hasn't yet worked properly.

I did not touch helium backup and will remove it because, according to author it does not work on Motorola phones and it does indeed fails on mine. Anyway, I got a file with login credentials out and that was all I ever needed from backup process. abe.jar unpack followed by tar worked flawlessly. Helium author, who almost never responds to any support requests to any of his products, can do whatever he wants, but without me using his abandoned products. You showed me a trivial solution, many tha...

I erased and reinstalled application then adb backup -noapk -system -f file.adb com.freedompop.phone was successful. You are right that Helium is no longer needed.

what exact backup command did you use and what phone/version?

ALLOW_BACKUP is set for com.freedompop.phone

Although this discussion went way far from initial topic, I would like to add the following. adb backup -all -shared -system -keyvalue -f file.adb indeed works but application I am interested in is not included in resulting archive, that is why having working Helium backup extractor would be very beneficial.

Correct. adb backup returns empty backup, 549 for encrypted and 41 for non ecrypted. I just tried the same on a recent Motorola with android v6 with the same results.

adb itsef is connected and working just fine, how do you think I got Helium backup file out?