yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] MontysEvilTwin:
My Fire HD 10 (2017) is on OS 5.6.0.1, and is rooted (SuperSU) with Xposed plus the per app hacking module installed, to make Flashfire 0.24 work. I would like to update to OS 5.6.3.0 and am planning to do this by flashing the stock update and a modified SuperSU zip (no arm64) with Flashfire. Presumably this will overwrite Xposed? Is this the best way of updating, and will overwriting Xposed cause a bootloop or other problems? Can I flash an Xposed installer Zip with Flashfire in the same sequence?
[Fire HD 8 and HD 10 General] nikothebarber:
Can't I side load the disable Xposed framework to kill the modules. Or is it possible to load it from a SD? I tried the hardware button method but since we don't have vibration I can't get the signal when to push four times
[Fire HD 8 and HD 10 General] GuyInDogSuit:
For some reason, I have two users on my Fire, both my name, and I can't figure out how to delete one. One, I can "manage the profile," which means change the name and the picture. I can only "manage family library sharing" on the excess one, no option to delete it. If I tap on it, it just shows a spinning circle and says "Loading" forever.

EDIT: Figured it out. It was just my shared Amazon account with the Prime benefits. For some reason both accounts show up on the tablet even though I'm just signed into the main one.
[Fire HD 8 and HD 10 General] PlayDev892:
I just wanted to install exposed that's all I'm 16 and am new to this and I want to unlock my boot loader can someone help me there is a guide on here xda but it's complicated I have and Amazon Fire Hd 10 2017 Version 5.6.4.0 and I want to install twrp
[Fire HD 8 and HD 10 General] retyre:
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.
[Fire HD 8 and HD 10 General] bibikalka:
OK, thanks! I guess FF 0.24 Pro should work fine, without any time limits.

I am still not clear why Kingoroot is an issue - you just need to root once, and then you can daisy chain all updates by using a working copy of FF, each time redoing all the necessary zips, see this for details:

https://xdaforums.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594

This is handy for loading new Amazon ROMs, and preserving root.
[Fire HD 8 and HD 10 General] retyre:
Thanks. I don't think there's any difference between the Pro and the Free versions of FF at this time, so I'm not sure it will work without the date hack. If you find otherwise, please update here.

Won't Kingo be needed if the device is bricked for whatever reason (with the kind of experimentation I have been doing, this is a matter of when, not if) and adb sideload is called for?
[Fire HD 8 and HD 10 General] bibikalka:
I think FF Pro version does not have a time bomb. Indeed, you could brick if FF misbehaves, but in reality, you already got through the bulk of it, there is not much left. The other screw ups might be fixable via root access in ADB (which you should have authorized already).
[Fire HD 8 and HD 10 General] mistermojorizin:
Hey, I got FF to work as a system app. Sorry I wasn't clear in my previous posts. I did the backups after rooting and making xposed, adaway, FF system apps. Then I set everything up the way I like it and made another backup, with PAH in DATA and google play store and other google apps in SYSTEM. For this latest backup, I used the exact settings you suggested (system, boot, recovery in the RAW, and DATA with max compression) and my system was just under 1GB and the data was 4gb. I haven't tried to restore the backups back, but I think they backed up properly. The process worked as you described and ended up completing. System .img is in the system backup file.

I wanted to ask, is it OK to have PAH in the DATA backup/restore? I know you said not to put it into system because FF won't work with it in system.

---------- Post added at 02:14 PM ---------- Previous post was at 02:10 PM ----------

Did you try it with FF 0.24 PRO or latest FF Pro. I tried FF 0.24 Pro and it didn't seem to want to open without PAH time settings.
[Fire HD 8 and HD 10 General] bibikalka:
Yes, 0.24 Pro bombs right away, not even a log ... Did they leave the time bomb in it? I intended to flash SuperSu.zip to get the proper 64-bit version of 'su', but got sidetracked. Will work on this a bit later.
[Fire HD 8 and HD 10 General] retyre:
4G for /data appears a bit high (if it's compressed).

Yes, it's fine to have PAH in /data. The old version will be overwritten during restore.

I think old versions of FF (Pro or not) are deactivated once new ones are released. Using FF is going to require PAH (hence, Xposed), so putting much of that in /system before the raw dump is a good idea.
[Fire HD 8 and HD 10 General] mistermojorizin:
In FF, when you add a backup action for /data, before selecting it and adding it you see the size of your partitions. My /data partition is 16gb uncompressed (pretty sure that is including the interal /sdcard partition which is 9.8 gb and is part of the data partition at /data/media/0). So I thought 4.28 gb compressed wasn't bad. What are your numbers here?

I can confirm, latest FF Pro opens without BAH time machine. But, I'm not sure if it actually works to make backups.
[Fire HD 8 and HD 10 General] retyre:
My /data backup is 1.6G (one chunk of 1G and another of 0.6G). You probably have many more apps installed, but an exact 4G backup looks iffy.

The problem is not just about FF opening. The latest version does. However, it doesn't work. When you click on Flash, it can't even get past the Fire logo. We need a version that both opens and works to backup/restore, which v0.24 is (with PAH).
[Fire HD 8 and HD 10 General] mistermojorizin:
it wasn't exactly 4, it was 4.28gb, sorry I was just rounding. But could you do me a favor,please: go into FF, Actions, plus sign, normal, and tell me how many GB /data says? of course you don't have to add the action, but I would just like to know what your *uncompressed* /data is at?
[Fire HD 8 and HD 10 General] retyre:
It's 14G (out of a total size of 27G). But like yours, most of it is in /data/media/0. Is your backup split into 1G chunks?
[Fire HD 8 and HD 10 General] mistermojorizin:
yes it is in chuncks, but only a few of them are 1gb. Maybe Flashfire doesn't actually backup the media/0 partition? do you know what the size of your sdcard or media/0 is? I want to try and compare the non sd part of data to mine.
[Fire HD 8 and HD 10 General] retyre:
My /data/media/0 is 12G, so the rest of /data is about 2.5G (FF rounds size to the nearest G).

I know FF does not backup /sdcard.
[Fire HD 8 and HD 10 General] kirin-h:
I don't know why the latest xposed_installer(3.1.4) didn't working correct in my HD 10

YOUR DEVICES-ARM SHOULD BE ARM64 .

So I can't install xposed.

Here is my solution:

1.download wrong data-package but not install

2.download arm64 data-package xposed-v89-sdk22-arm64.zip

3.rename xposed-v89-sdk22-arm64.zip as xposed-v89-sdk22-arm.zip

4.copy xposed-v89-sdk22-arm.zip to Android/data/de.robv.android.xposed.installer/cache/downloads/framework COVER the wrong data-package

5.open xposed_installer and install

6.now you should see a little console window popped up displaying that there was an error finding "app_process64". This is normal

7.Navigate to /system/bin/ and delete the file: "app_process64_xposed"

8.reboot and you will see xposed is working.
[Fire HD 8 and HD 10 General] bibikalka:
Great info!!! You should copy&paste this to your post #1. Especially regarding wait times - it can be very lonely while waiting for the device to respond :D

Now, I tried to be very clever - and re-flash SuperSu.zip ( SuperSU-v2.79-201612051815.zip ) as to get "properly flashed root". And ... Ended up with a bootloop with "Fire" logo , can get a shell, but no root :(

But no fear, recovery sideloading, and my much improved rooting guide to rescue !!! I even found the same FireOS version as my tablet has, 5.5.0.0 (link)

Update: added the Flash Fire log file that I pulled via "adb pull /sdcard/FlashFire/lastlog" while it was bootlooping.
[Fire HD 8 and HD 10 General] mistermojorizin:
I can confirm that restoring system and data partitions with FlashFire went flawlessly, saved me some trouble when i jacked stuff up, but could still boot up and load flashfire. Awesome! We just need to figure out how to make FF load the backup/restore processes faster and not sit there for 10 minutes doing nothing.

Unfortunately, using the dd command above did not work. I got the system file from inside the system backup zip and renamed it to system.img and pushed it to my sd card. got a root shell, mounted system rw, and ran the dd command above. Nothing happened. No output in ADB, just cursor went down to a blank line. I twas the same backup that I could restore in FF, so I know the backup was good.

I tried googling around a bit and read about someone saying you have run adb "from inside the device" .....but i didn't mess with it further. So my Fire is working great right now, but I had to do a FF restore, and couldn't do a dd restore. Have you, or anyone, done the dd restore of the system? Am I missing anything?
[Fire HD 8 and HD 10 General] retyre:
Writing a 1.6G file takes time (that's the blank line where you think nothing's happening). IIRC, the writing takes about 3 minutes, after which you should be back to the root prompt. Reboot from there.
[Fire HD 8 and HD 10 General] retyre:
Done. Everything's now in the mile-long OP.
[Fire HD 8 and HD 10 General] bibikalka:
[MENTION=3497316]retyre[/MENTION]

After my SuperSu induced bootloop, I've re-rooted a sideloaded FireOS 5.5.0.0, and tried Flash Fire 0.24 on something a lot more benign - Busybox zip. This zip worked fine - so zip flashing functionality in FF v0.24 is OK.

Now, if we could only find a SuperSu zip version which would flash OK in FF - then we could daisy chain all zips on top of the update, as I was doing for Fire 7:

https://xdaforums.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594

But without TWRP recovery, testing SuperSu zips to see which ones would work fine is a time wasting proposition. We should test if somehow the device can boot an unsigned recovery - long shot, but who knows ...
[Fire HD 8 and HD 10 General] retyre:
Thanks for checking FF's flashing ability on this device.

I was about ready to flash an unsigned recovery a few days ago, but stopped short. I guessed there's no way the bootloader will allow that. I might still try it (it helps that I have a test device on which to try these things).

A few days ago, I created my own update .bin with injected SuperSU (by unpacking and repacking the system.new.dat from the 5.6.0.0 update .bin using the corresponding file_contexts and system_transfer_list, and then signing the update) and tried to adb sideload it, but it failed as expected. The bootloader will not let anything pass through without verifying the signature.
[Fire HD 8 and HD 10 General] oscarcx:
Great work. I didn't back up though, knew it could be risky but just went through the tutorial because I was lazy and fortunately it worked:D

Just need to be patient when the tablet restarted and went through the optimization process.

Any suggestions for some useful xposed modules?

Update 1: Some features of Gravity box works. Xprivacy works but there's a error box popping up each time I launch the app.
[Fire HD 8 and HD 10 General] bibikalka:
[MENTION=3497316]retyre[/MENTION]

I noticed a few interesting things in my FF log in (/sdcard/FlashFire/lastlog). Could you check yours and tell me what these lines say? I want to know if the various versions (lk,pl,tee) changed from Fire 5.5.0.0. to 5.6.0.0. When sideloading an older FireOS, it often bricks when these version numbers are smaller than what got recorded in the MTK fuses:

[ro.boot.lk_version]: [0x0002]
[ro.boot.pl_version]: [0x0004]
[ro.boot.tee_version]: [0x0105]
[ro.build.version.fireos]: [5.3.5.1]
[ro.build.version.incremental]: [40.5.9.1_user_591450020]
[ro.build.version.name]: [Fire OS 5.3.5.1 (591450020)]
[ro.build.version.number]: [591450020]
[ro.build.version.release]: [5.1.1]
[ro.build.version.sdk]: [22]
[ro.build.version.security_patch]: [2017-08-01]
[Fire HD 8 and HD 10 General] retyre:
[ro.boot.lk_version]: [0x0002]
[ro.boot.pl_version]: [0x0004]
[ro.boot.tee_version]: [0x0105]
[ro.build.version.fireos]: [5.3.6.0]
[ro.build.version.incremental]: [40.5.9.5_user_595457320]
[ro.build.version.name]: [Fire OS 5.3.6.0 (595457320)]
[ro.build.version.number]: [595457320]
[ro.build.version.release]: [5.1.1]
[ro.build.version.sdk]: [22]
[ro.build.version.security_patch]: [2017-08-01]

Doesn't look any different (but for the build, of course). During some of my early testing, I did roll back from 5.6.0.0 to 5.5.0.0 just to see whether the rooting process was any easier or harder (no difference). I did notice one irritant with 5.4.1.0 and 5.5.0.0 that has been fixed in 5.6.0.0: the device name at the top-left of the status bar is gone. To me, that alone is reason enough to update!
[Fire HD 8 and HD 10 General] bibikalka:
It's good to know that downgrading here works! I ran md5sums, and got this

C:\extra\android\firehd10_2017\firehd10_2017_update-kindle-40.5.9.1_user_591450020\images>md5sums *

[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\extra\android\firehd10_2017\firehd10_2017_update-kindle-40.5.9.1_user_591450020\images\]
lk.bin 0b280c1af3bda4b2643c68731cd8f6d1
preloader.bin 81ff1e3a7bc45d172d5e3d8f8e71e179
preloader.hdr0 b3975c00c38ac79623faeb6dc8444dd7
preloader.hdr1 61518d1df14ee4d7ca0bdccb2c506ea4
tz.img 02cc58fd73faf4c2d2f0266966f929f3

C:\extra\android\firehd10_2017\firehd10_2017_update-kindle-40.5.9.5_user_595457320\images>md5sums *

[Path] / filename MD5 sum
-------------------------------------------------------------------------------
[C:\extra\android\firehd10_2017\firehd10_2017_update-kindle-40.5.9.5_user_595457
320\images\]
lk.bin 0b280c1af3bda4b2643c68731cd8f6d1
preloader.bin 81ff1e3a7bc45d172d5e3d8f8e71e179
preloader.hdr0 b3975c00c38ac79623faeb6dc8444dd7
preloader.hdr1 61518d1df14ee4d7ca0bdccb2c506ea4
tz.img 646069b642940fc95a3bc691bc02f1ed

So the only difference is TEE1 (tz.img), but I guess they kept the same version number! Once those version #'s update, there will be a flood of bricks :(

P.S. I think I figured out how to update system from an Amazon binary, and get SuperSu installed and all that. But need to test first.
[Fire HD 8 and HD 10 General] retyre:
... that does not require the use of Kingo to root? If so, please post here. In my case, every tweaked update .bin fails at around 47% (thanks to signature verification).
[Fire HD 8 and HD 10 General] bibikalka:
Flashable SuperSu 2.82 zip :

[MENTION=3497316]retyre[/MENTION]

I made some minor progress today, and was able to flash a SuperSu zip in FlashFire correctly. It only took me 2 adb sideloads to get here :D

On the down side, I was unable to flash Amazon OTA via FlashFire - v0.24 does not seem to understand the commands as is in the updater-script.

Anyway, I am posting my modified SuperSu zip here in case you'd like to use it : https://xdaforums.com/hd8-hd10/gene...7-root-box-t3726443/post74987123#post74987123

P.S. I also filed failure reports in FlashFire thread https://xdaforums.com/general/paid-software/flashfire-t3075433/post75043836#post75043836 and SuperSu thread https://xdaforums.com/apps/supersu/...78-release-t3452703/post75043768#post75043768

We will see if anybody responds ...
[Fire HD 8 and HD 10 General] mistermojorizin:
So u just flah that file in our working flashfire? Anything else special u had to do to avoid problems?

Can you see if sdmaid will freeze apps for you? I'm not interested I getting sdmaid working, but it gives an error abot lib.so being 32 bit. So I am looking at it as	a benchmark to make sure root works with all apps.

Edit: just saw your other post about having to still have 32bit libs to get it to flash. What is the advantage of flashing if over the su then?
[Fire HD 8 and HD 10 General] bibikalka:
The advantage is that it actually works now :D It may become useful in the future - in case one wants to update SuperSu in FlashFire.

The tablet's OS is a mix between 32 & 64 bits. It'll probably get addressed by Amazon at some point in the future, so it's futile to try to optimize for this.

By the way, you could try to flash first the official SuperSu 2.82 (which would run as arm64), and then my zip right after (as armv7) in the same Flash Fire session (2 zips at once). The 1st flash will leave some 64-bit libraries behind, while the 2nd should make sure it works again. This could also bootloop, so you'll need to sideload a bin file again.
[Fire HD 8 and HD 10 General] mistermojorizin:
I do see the development value of this, but I'm confused. Is your "su" now a 64 bit su? did you happen to try out sdmaid's root featurs (like freezing an app)?

CPUZ reports that the tablet has a 64bit cpu, but a 32bit instruction set. So I'd guess the OS itself is 32, or at least it runs in 32 mode.

what is the flashing procedure that you used? The one that didn't cause a bootloop?
[Fire HD 8 and HD 10 General] bibikalka:
Reporting on my current progress. I've edited build.prop to have device report 'armeabi-v7a' instead of arm64, but it did not really help to run FF 0.73 : post

Because the currently working FF v0.24 came out before Lollipop, and does not support Lollipop update commands, we won't be able to use Amazon OTAs as is, to update things in this relatively simple way:

https://xdaforums.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594

Instead, one will have to unpack the update file elsewhere (using tools like sdat2img), and then flash it via FF v0.24 writing the raw system partition image onto the device. Here is the update file in question:

block_image_update("/dev/block/platform/mtk-msdc.0/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");

Another possibility is that Amazon actually takes effort to make future FireOS updates into a proper arm64 Lollipop.

Anyway, I've poured a few hours into this, got far enough. Will be waiting on new developments from now on!
[Fire HD 8 and HD 10 General] mistermojorizin:
I've spent a bit of time tonight getting multi window on this thing. I used a modified version of xhalo floating window for lollipop and a sidebar for multiwindow app. All of the files and instructions are here if anyone's interested: https://www.youtube.com/watch?v=ocq_k283EQE

I've also got a few other xposed modules: activity force new task, app settings, gravity box, lockscreen disabler, minmin guard, native clipboard, pandora patcher, swype row and swype tweaks, unrestricted get tasks

I have a quick question re FlashFire. Is it OK to add the actions to backup system and backup data together in sequencer, then hit flash? I found this way, you only have to wait for the thing to load once, and then it does the flashing pretty quickly. Versus doing them one at a time and waiting for the FF interface to load twice.
[Fire HD 8 and HD 10 General] oscarcx:
Just a quick question, will the lockscreen disabler disable the amazon lockscreen only or completely disable the lockscreen function? Is there any chance that I can have an alternative lockscreen instead of the original one?
[Fire HD 8 and HD 10 General] mistermojorizin:
in my case, i only see the lockscreen upon a reboot. so i guess the function isn't completely disabled. i don't know more than that, but from what i could tell, the lockscreen is baked pretty deep into the fireos.
[Fire HD 8 and HD 10 General] freaky2xd:
Flashing ZIP files with FF works!

All Cores Enabled

+ wiping cache and dalvik before flashing

takes some time though

5 minutes black screen

then a few seconds LOADING with /system/blablabla list

then black screen again for 3 minutes

then the actual wiping and flashing takes place

first boot after wiping and flashing takes some time as well

optimizing application blablabla 10 min
[Fire HD 8 and HD 10 General] retyre:
Yes, you can. (I'm assuming you're doing a raw backup of /system first and then a file-based backup of /data; there's no need for two actions otherwise.)
[Fire HD 8 and HD 10 General] mistermojorizin:
Does it make a difference if you backup system or data first, as long as you do system add raw and data add normal?
[Fire HD 8 and HD 10 General] retyre:
No difference.
[Fire HD 8 and HD 10 General] mistermojorizin:
what are some things that are useful to flash on the fire hd?
[Fire HD 8 and HD 10 General] freaky2xd:
well I always use sound mods on my Android devices...

I flashed this on on my Fire HD 10: https://xdaforums.com/android/general/mod-experience-sound-t3681780

there's other stuff as well like Sony Apps Enabler

or other mods
[Fire HD 8 and HD 10 General] fuzzynco:
Flashfire 0.24, Supersu 2.79 & HD10 5.6.0.0

It's missing backup internal sdcard which the current one supports.

The current workaround does do what is intended, It successfully

backs up /system to external sdcard. Once the ftp to windows is finished

I'll run the backup of /data. :victory:

(We are guessing the current one depends on things changed in

later SDKs then 22 5.1.1? )

Can anyone confirm the backup data function still skips the

/data/media (/sdcard) directory? I'm working on an ftp

to windows directory (for backup) using Goodsync, for backing

up /sdcard. :good:

Since we now have a working root, is it possible to port a real

Android (5.1.1 sdk 22) to it similar to what was done for the

rootable fire 7 5th gens? :fingers-crossed:

Thanks all.
[Fire HD 8 and HD 10 General] bibikalka:
I kept working to make updater-script from OTA work in FF v0.24. Here is my trimmed version

getprop("ro.product.device") == "suez" || abort("This package is for \"suez\" devices; this is a \"" + getprop("ro.product.device") + "\".");
show_progress(0.750000, 0);
ui_print("Patching system image unconditionally...");
block_image_update("/dev/block/platform/mtk-msdc.0/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
show_progress(0.050000, 5);
package_extract_file("boot.img", "/dev/block/platform/mtk-msdc.0/by-name/boot");
show_progress(0.200000, 10);
package_extract_file("META-INF/com/amazon/android/target.blocklist", "/cache/recovery/last_blocklist");
set_metadata("/cache/recovery/last_blocklist", "uid", 0, "gid", 0, "mode", 0444, "capabilities", 0x0);

Anyway, not much luck. I even substituted an ancient update-binary from around the days when FF v0.24 came out (taken from FireHD7 2014 OTA), still no luck.

So the only way for future OTAs to be applied is to unpack them elsewhere, and dd a raw system image to /system partion, followed up by SuperSu zip.