May I inquire why you were using FF v0.24 ? What's wrong with the newer FF versions? Do they not work?
What's the reason to save an img for /system, instead of just reloading everything upon getting root?
Correct. I tried _every_ version of FF from v0.73 on down, and this is the one that worked. The more recent ones (v0.53+) don't even try to load; the earlier versions try to load but fail. Chainfire did mention in a post somewhere that v0.26 was a major update. Obviously, not the right kind of major for the 2017 HD 10.
When it comes to restoring /data, I trust FF more than TiBu or Backup+ (familiarity and better automation). To be able to do that, however, I need a working FF. For FF v0.24 to work, I need the PAH module in Xposed to trick the FF time bomb. If I have Xposed and FF installed in /system, I can just dd restore that image instead of manually installing Xposed, waiting a long time for it to load after reboot, installing FF, etc. With my current solution, I just need to install PAH after a dd /system restore (because FF doesn't like PAH in /system), and then use FF to restore /data.
Given the amount of time I have spent tuning this, I am now able to get my entire setup (custom /system and /data) up and running from a fresh adb sideload update.bin in less than 30 minutes.
I worry a lot about having to depend on Kingo to root because it's not an offline operation. Blocking updates puts Amz out of the picture, but Kingo needs Internet access to fetch its world-class scripts. I have tried all sorts of URL snooping and redirecting to capture Kingo's scripts/exploits, but without success.
Last edited: