yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] fuzzynco:
as a workaround I used tar to backup internal

I just ran

cd /sdcard
tar cvzf /storage/sdcard1/int-sd.tgz ./

and then uploaded the tgz to windows for backup.

I backup external with a sdcard adapter and

locally run goodsync (which works kind of like rsync)

to sync whatever changed.

Winrar extracted the files to a windows directory fine.
[Fire HD 8 and HD 10 General] retyre:
I stumbled upon this. Perhaps there's hope.
[Fire HD 8 and HD 10 General] oscarcx:
Typed a few questions but got wiped out...

So I was basically asking if it's possible to:

1. Replace the status bar completely

2. Replace that dummy lock screen

3. Customize "Setting"

(with Root and Xposed and whatever we have for now)

4. Replace that shutdown confirmation dialog and have a regular one with reboot so I don't need to power it off then turn it on again.

And I tried a few Xposed modules and they work pretty well so far.

1. Greenify

2. External Link (This English translation is quite different from the original Chinese title)

3. Wechat wizard

4. Lucky Patcher

5. App settings

6. GravityBox[LP] (partially works)

7. Xprivacy

8. YouTube Background Playback

Any more interesting Xposed modules?
[Fire HD 8 and HD 10 General] bibikalka:
[MENTION=3497316]retyre[/MENTION]

5.6.0.1 OTA file is available on Amazon, I've extracted boot and system images via MTK_Extractor_V2.6.3, and in FlashFire, restored these 2 new images, then SuperSu.zip, and Xposed.zip.

Anyway, long story short, Flashfire did not like to flash SuperSu zip after restoring system.img, complained about read only. So I lost root, but re-rooted the new 5.6.0.1 using Kingoroot.

It looks like one needs to patch SuperSu into system.img, and only then upload to the device.
[Fire HD 8 and HD 10 General] retyre:
I used dd (not FlashFire) to do this, but here's the issue I encountered: After I injected SuperSU into the stock system.img, live-dumped boot.img and system_su.img, and rebooted, SuperSU was not installed properly (trying to open SuperSU resulted in the "SD card not available" problem that has been discussed on this forum). I repeated the injection after removing the SuperSU apk part, dumped the images, manually installed the SuperSU apk, and moved it to /system. No problems since.
[Fire HD 8 and HD 10 General] btonetbone:
Is the final product flashable, and anything you might be able to upload?
[Fire HD 8 and HD 10 General] bibikalka:
I've uploaded 6.6.0.1 images in here, pre-rooted:

https://xdaforums.com/showpost.php?p=74987123&postcount=2

You can either flash them in Flashfire, or dd.

So you just dd /system from a shell, and it does not crash on you as you are doing so? How do you inject SuperSu into it then, by manual commands? Or by running SuperSu, and updating binaries? And do you re-root on each failure (which you seem to have many of), since that's how your description reads?

I was attached to the FlashFire route, since after restoring stock system, I wanted to run the regular Supersu.zip. Unfortunately, for some reason, it no longer gives write access to /system in FlashFire, so I ended up with just stock in /system, without any root.

Man, if I knew which system command to replace, I'd fix FlashFire! But it's not clear whether the issue is in the kernel, or the system utils.
[Fire HD 8 and HD 10 General] retyre:
Yes, it does crash at times (as it should when doing a live restore), but it usually does so after the data has been written. There's always a risk of corruption with this approach, but works well as a quick test. On a daily driver, I would use FF.

I do not use FF to inject su. I do that manually in Ubuntu after mounting the stock system.img. As a result, root is never lost. If you preroot your system.img and overwrite the system.gz in your current FF zip, you should have rooted 5.6.0.1 after FF is done. Or you could just flash boot.img and system_su.img in sequence in FF. Make sure EverRoot is disabled.
[Fire HD 8 and HD 10 General] bibikalka:
Interesting ... FF can also write raw images (almost like dd), so are you trying to save ~5 min on FF here but risk a crash? What I found out is that if I put system.bin & boot.bin into FlashFire/Backup, and then create md5sums files (md5 system.bin > system.md5, and same for boot.bin), then FF would just pick these 2 images up no problem.

Which files are you injecting such that you know it works for sure? Can you share the exact commands that worked for you? Btw, EverRoot is nothing else but running an internal supersu.zip package within FF. It's simple to repackage FF v0.24, and put the newer supersu.zip into it from the more recent FF v0.73. Unfortunately, this may probably run into the same issue - /system is not writable. For some reason supersu.zip worked fine with 5.5, but stopped with 5.6.0.1
[Fire HD 8 and HD 10 General] kapilathi:
Is there a alternate OS available other than fire OS. No LineageOS love ?
[Fire HD 8 and HD 10 General] TheRealIntence:
No custom rom so far
[Fire HD 8 and HD 10 General] GamerOfRassilon:
I apologize for the newbie question here; I've been exclusively on iOS devices for years, so I'm still trying to wrap my mind around many fundamental aspects of Android.

So, to make sure I understand this correctly:

If I follow this guide and get a working image for both /system and /data, what does that get me? It looks like I'm able to restore after a sideloaded OS reinstall or factory reset; is that right?

In particular, if I have the system set up the way I like it (apps, settings, etc.), and I get Xposed and FlashFire working and create my sytem.img and data.img backups, does that mean I can re-load the system from the system.img and data.img and my system will be at the state it was when I did the backups? (There are a jillion apps, app settings, tweaks, login infos, etc. I have with the device, and it'd be a HUGE time-saver to have a fully restorable backup in case something goes wrong . . . but I'm not 100% sure if that's what this is getting me, and I'd hate to test it only to discover I misunderstood what this was doing, and now I need to reinstall a jillion apps.)
[Fire HD 8 and HD 10 General] retyre:
Yes, restoring a FlashFire backup of system and data will get you back to the state you were in when you made the backup. Note, however, that this requires a working install of FlashFire after a sideload of the factory update .bin. FlashFire requires Xposed in this case. The OP explains everything.
[Fire HD 8 and HD 10 General] GamerOfRassilon:
Sure! I got all that; I just wanted to make sure I was understanding the whole point of this exercise (which is, indeed, a way to get to a solidly working system with minimal effort after a system install).

I performed everything herein, and it all worked with only a few hiccups; thanks so much for your efforts.

I wanted to list a couple of bits that tripped me up, since I missed them:

Make sure SuperSU is set as a system app. (This one is mentioned a couple of times, but I still missed it.)

Make sure Xposed Installer is set as a system app, as well. (This was was easier for me to miss, IMO, since it seems like was only mentioned tangentially.)

I otherwise did everything correctly, except I didn't have SuperSU when I restored the system image (although I did have su, because of Kingo). After I restored the system.img, I just installed SuperSU with ADB, forced SuperSU to reinstall (using its option), reinstalled Xposed Installer, reinstalled Per App Hacking, set the time in Per App Hacking, restored from the backup, and it all worked out. It was even more trivial for me, because I'm using the offline Kingo rooting method.

I did have one question. I'm trying to maintain a tightly locked SuperSU using the other excellent retyre tutorial. Do you know if Xposed Installer and all its modules need to be listed separately in the eu.chainfire.supersu_preferences.xml file, or does only one or the other need to be listed?
[Fire HD 8 and HD 10 General] retyre:
Just Xposed Installer.
[Fire HD 8 and HD 10 General] lovemesomeandroidyo:
Would kill for LOS on this.... I just had the tablet delivered yesterday, and it's a pretty nice cheap tablet. Hid the useless amazon apps with Nova, installed Google Play and got other apps I needed, but for some reason, Podkicker Pro is incompatible with it. That's the only issue I'm having
[Fire HD 8 and HD 10 General] GamerOfRassilon:
Thanks so much for your help! It worked great.

I've been through the process a few times now, and — now that I have backup images I'm happy with — I can go from "Hmm, I think I want to wipe this system and restore from backup" to sideloading the OS to having a fully restored system in 39 minutes, 20 seconds:

reboot, wipe data/cache [1:39]

sideload update from adb [11:38]

reboot (and optimize system storage and applications) [16:20]

copy rooting files and root [18:20]

load system.img via adb [21:43]

reboot (and optimize system storage and applications) [27:46]

load SuperSU, install Per App Hacking via adb, reboot, active Time Machine on Per App Hacking, reboot, start FlashFire, select "restore from backup image" [31:20]

restore from data backup. [39:20]

There's only one minor question I have. At one point, I accidentally typed the wrong command. Instead of typing:

dd if=/storage/sdcard1/system.img of=/dev/block/mmcblk0p13; sync

I typed:

dd if=/storage/sdcard1/system.img of=/dev/block/mmcblck0p13; sync

(That is, "mmcblck0p13" instead of "mmcblk0p13")

When I entered the erroneous command, I got an error message:

dd: /dev/block/mmcblck0p13: No space left on device

1858185+0 records in

1858184+0 records out

951390208 bytes transferred in 16.905 secs (56278628 bytes/sec)

Did I do any damage to the tablet as a result of this erroneous command, or is there anything I should fix? (I've reinstalled the system twice since then, and it seems to be totally working fine now, so I'm guessing not, but I'd hate to think I've left any ticking time bombs for me . . .)

Thanks again for all your help; this is an excellent guide, and this backup system is a great "security blanket" so I can start making regular backups and feel reasonably safe that I can get my system back with minimal fuss, even as I make more tweaks and poke around.
[Fire HD 8 and HD 10 General] retyre:
You just wrote about 900M of data from system.img into a nonexistent partition on /dev/block. You say you have adb sideloaded twice since, so it's gone now. If you had not, going to /dev/block and doing a listing would have revealed a file with the name "mmcblck0p13" taking up 951390208 bytes. If so, you'd just delete it.

As you have probably realized, dd blindly does what it is told. Be happy you did not type in the name of an incorrect (but extant) partition, e.g., bootloader.
[Fire HD 8 and HD 10 General] GamerOfRassilon:
One more question on this topic:

If I have two Fire HD 10 (2017) tablets, and I successfully have a system and data backup from one, can I restore them to the other tablet? Or are backups somehow signed or tied to the tablets they're created on?
[Fire HD 8 and HD 10 General] bibikalka:
Not tied. Can restore with ease! I've done this bunches of times. If you are registered with Amazon, it may get briefly confused.
[Fire HD 8 and HD 10 General] GamerOfRassilon:
Thanks for your help, bibikalka! It all worked as you said it would, and now I have a complete ready-to-go "backup" tablet. (And, indeed, Amazon was REALLY confused. It took a fair bit of tinkering, but I think the "best" way to do it is to deauthorize both tablets, rename them how you want — with different names — and then reauthorize them.)
[Fire HD 8 and HD 10 General] DragonFire1024:
I have discovered an app called MyAndroidTools. You can enable and disable services, broadcasts, activities and content providers (most require root). You can even edit and modify databases. It seems to work more often to disable than enable. Nonetheless I am using it along with my debloating to get somethings working, but so far not a lot of luck.

Anyways, I am not brave enough yet to test this one. I might have found a way to disable the ADB sideload security (probably not) but haven't tried it yet.

1. Download, install and open MyAndroidTools.

2. Tap on three lines at top left and tap on Service.

3. Tap on the system tab

4. Scroll to and tap on SecuritySyncClient

5. Notice the 'SideloadEventService'?

I am wonderig if it has to do with ADB sideload. I turned the service off, rebooted and plugged my HD 10 into the PC and sideloaded an APK. So I know it doesn't do anything on that level. Anyone want to try sideloading in recovery with it disabled?

By the way...I soft bricked twice already using this app, and recovered from near misses a few times. Toggling these things will do some damage if you aren't careful.
[Fire HD 8 and HD 10 General] Flipscuba:
Wait, how do you have OGyoutube? Wasn't it discontinued/made unavailable?
[Fire HD 8 and HD 10 General] chris_dubs:
This works how come this guy didnt get kudos? thankyou sir! :good:
[Fire HD 8 and HD 10 General] chris_dubs:
Can someone edit OP for these instructions 3rd time ive done this, works flawless, i clear dalvik after reboot then reboot again.. my 2 cents
[Fire HD 8 and HD 10 General] retyre:
There's a guide linked in the OP that contains these steps: Install the arm64 .zip in Xposed Installer, delete /system/bin/app_process64_xposed, and reboot. Did that not work for you?
[Fire HD 8 and HD 10 General] chris_dubs:
No op instructions were to install per app hacking ff etc. I got bootloop multiple times and he didn't explain about renaming the file to arm64 instead of just trying the reg arm file. No offense to op at all. Still trying to get ff working to bu data but his dd script for sysimage works great. What am I missing for ff? Does it really have to be a sys. App I'm so confused. I have root browser so not a big deal but .24 or new .73 have same prob getting stuck at fire logo. Need help. Thank you though for response. Just thought this guy explained it easier for a noob on Amazon tabs like myself. I only got experience in unlocked boot loader samsung.
[Fire HD 8 and HD 10 General] retyre:
You have to follow the steps in the OP: (1) Xposed should be working with PAH activated, (2) install FF v0.24 but do not open it, (3) set the date/time in PAH's Time Machine for FF, (4) open FF, adjust its settings, and backup the partitions, and (5) endure two four-minute waits as described.

If you see the Fire logo (instead of a blank screen) after flashing in FF, you have not followed the instructions to the letter. In general, it would help to post everything you have tried (in sequence).
[Fire HD 8 and HD 10 General] chris_dubs:
ok understood, i got xposed working great, ive dl .24 ff not opened, rooted, bb pro etc, so where can i get this pah app? ive looked and searched... can you help me attain the apk?
[Fire HD 8 and HD 10 General] retyre:
Sure? Type Per App Hacking in Goog and what's the first hit that comes up?
[Fire HD 8 and HD 10 General] cool400:
Seems I bricked my HD 10/KFSUWI :(

When trying to install Xposed as mentioned in the OP, I got the process64-error.

Because I hadn't installed a file explorer, I then tried to install ES file explorer and Solid explorer, but neither over Google Play nor over Amazon Appstore it worked. Installation of all explorer-apps I tried failed.

I then tried to reboot my rooted HD 10 (I'm on 5.6.0.1) and now I'm stuck on the "fire"-screen without any progress.

What should I do now? Do you guys have any ideas?

BTW, it seems I can connect to it via "adb shell", but file-system is read-only :(

Are there any commands I could try?

EDIT: Unbricked it successfully using the Unbrick-Thread here! Never mind - next try ;)
[Fire HD 8 and HD 10 General] chris_dubs:
So I found an easier way to backup restore. I can only get system data and cache partitions....... but all at once. Had no issues at all. I created a control switch in Kernel Adiutor to disable SeLinux temporarily (says disabled but i assume its just permissive). I did the offline rooting method with with SuperSU, Busy Box, Xposed, no Flash Fire, but not that any of that besides the rooting matters. ai forgot aaai purchased the full version of TWRP Manager a while back and with selinux disabled it will do Live Backups directly from the OS with the phone on. Ill try to upload screenshots. 1.98 Gigs total with compression enabled. I think it cost me $5 a year ago or so. IMO way safer than FF and worth the few bucks. Until somebody can get the bootloader problem fixed? I think this is my personal recovery option...

---------- Post added at 04:12 PM ---------- Previous post was at 04:05 PM ----------

Heres a link to a thread for a fella that developed his own live backup program thats free. He has a version for the hd otter2 so maybe somebody could tinker with it and get it working on our never tablets. https://xdaforums.com/showthread.php?t=1620255
[Fire HD 8 and HD 10 General] retyre:
Does TWRP Manager have a "Live Restore" option? We don't have a custom recovery ...
[Fire HD 8 and HD 10 General] chris_dubs:
I havent tried yet, good question ill try it.
[Fire HD 8 and HD 10 General] sga999:
retyre, as you know, I had to restore a couple of weeks ago due to problems created while trying offline Kingo root. I have a couple of questions about this xposed/flashfire process.

1. When doing the dd to restore system.img, the tablet rebooted and was stuck on the Fire logo. You mentioned this in the OP, so I wasn't surprised. And it did work when reissuing the dd command. But I was curious about whether you know why this step "fails" in this way?

2. In one paragraph, you mentioned making SuperSU, Xposed, and FlashFire system apps before backing up with dd. In the next paragraph, you mentioned methods (e.g. link2sd) to make FlashFire a system app, and another way to do it for SuperSU. You don't mention Xposed, so I assume you meant that we could use link2sd. However, with having to install the PAH module (since it must not be a system app) and reboot, and I think I had to reboot to get Xposed to work anyway, is there really any advantage in including Xposed in the dd file?

3. When you mentioned creating a system.img with dd, you said "make sure you copy the backup off the tablet after it's done". It seems like we only need to do this if sdcard is wiped. Does that only occur when we pick the recovery option to wipe? I know adb sideload of a bin file doesn't wipe sdcard. I assume settings - Device Options - Reset to Factory Defaults wipes sdcard. Are there any other ways sdcard gets wiped?

Thanks so much for this excellent procedure.
[Fire HD 8 and HD 10 General] retyre:
1. dd dumps the backup system.img to a mounted /system. This is generally not recommended because of the risk of data corruption as files may be in use and/or modified while being (over)written. In all my tests, I have had the greatest success when dding the same version (e.g., dding a modified 5.6.0.1 system.img while in a pristine 5.6.0.1 Kingo-rooted system; call this "symmetric" dd), presumably because that's when the changes are minimal. That might also explain why it works on the second attempt after an asymmetric dd (because the first try has already dumped the problem file(s)). One could look at the logs to see what's crashing (probably SystemUI or something framework-related because root-shell access is intact, but that's just a guess).

ETA: In light of (1) above, here's my recommended approach:

-- adb sideload 5.6.0.1 update.bin

-- Root with (offline) Kingo

-- dd super_awesome_system_5.6.0.1_backup.img to mmcblk0p13 (repeat if it fails the first time)

-- Get FF v0.24 working with PAH in Xposed

-- Use FF to restore /system (from super_awesome_system_5.6.0.1_backup.img) and /data from backup

2. Yes if you're referring to the framework; no if you're referring to the installer. Given the hoops one has to jump through to install the Xposed framework (arm vs. arm64 confusion), why would one want to do that more than once?

3. Bootloader unlock, but that's not relevant here. That suggestion was primarily a fallback in the event of a careless wipe.
[Fire HD 8 and HD 10 General] DragonFire1024:
In regards to number 3, I've had the internal storage (/sdcard) wiped when trying to root one time and only once...I was running a dirtycow script on my HD 8. It of course didn't root it, so far as I could tell. But the script did run and complete...this was almost 2 years ago though. It seems the HD 10 is rooted via dirty cow too. I try to logcat the process and I don't know if it logs it. Every time I do it (and given the modifications I have been making, it's often) the logs freeze right at the moment of exploitation.

In regards to SuperSU and FlashFire being system apps, FlashFire has failed every time I place it into /system or /system/priv-app. It would open briefly and force close. Should I install it via ADB push or copy it from storage to /system/xxx and issue the proper permission? I know if pushing via ADB the permissions are automatically set.
[Fire HD 8 and HD 10 General] retyre:
That sounds like a time-bomb issue. Do you have Xposed working with the Per App Hacking module containing the proper date-time (in Time Machine) for FF?
[Fire HD 8 and HD 10 General] DragonFire1024:
I do indeed.
[Fire HD 8 and HD 10 General] sga999:
About the xposed framework, once the .zip is installed, isn't it already part of system? I mean, If it has already been installed and then the dd backup is done, isn't that enough to have it installed when restoring the system.img later? If it's not enough, what step needs to be done? (I did think you meant that the installer needed to be made a system app. I did not do that, and I think you're agreeing with that).

On a different topic, for Dragon1024 issue about FlashFire, I've only used link2sd. I haven't copied the file directly. Could that be making a difference? I have not had any problem with FF v0.24 with PAH module.
[Fire HD 8 and HD 10 General] retyre:
Yes, the framework files will be in /system. The goal is to have all the FF prereqs in system.img. That includes Xposed Installer. As you wrote, this is not required (using that argument, FF need not be a system app either; you could just install it like you would Xposed Installer), but it's one less thing to worry about.

DragonFire1024: If you don't want to use Link2SD, just move /data/app/eu.chainfire.flash to /system/priv-app/eu.chainfire.flash and set the correct permissions (755 for directories and 644 for files).
[Fire HD 8 and HD 10 General] DragonFire1024:
so I had this happen twice, where I had to flash stock back to the tablet. I do a factory wipe from recovery and wipe cache. I select ADB sideload and load the firmware. It finishes and I then do another wipe on it before rebooting. If that's wrong, please tell me so. Anyway tonight I did like I did ad went to root again and Kingo tells me it's apparently 'removing root.' I thought all that wiping and the flash removes root?
[Fire HD 8 and HD 10 General] retyre:
Wiping does not unroot (it doesn't touch /system); adb sideloading update.bin will. If the adb sideload completed successfully and Kingo is trying to remove root after the first boot, this is a Kingo problem. If you can, grab the Kingo files from /data/local/tmp and try the offline rooting method.
[Fire HD 8 and HD 10 General] JJ2017:
Yep, Thanks for this - I got really stuck trying to install Xposed framework too! :good: