yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] retyre:
In general, it will help if you explain what the problem (with the steps in the OP) is. Here's what I have seen thus far: "I don't know why the latest xposed_installer(3.1.4) didn't working correct in my HD 10" and "I got really stuck trying to install Xposed framework." What exactly have you tried and what's the error message?

Why are you downloading the wrong data package (xposed-v89-sdk22-arm) to begin with? You should be using the drop-down arrow in the installer to download xposed-v89-sdk22-arm64, after which you should install it and delete app_process64_xposed from /system/bin before rebooting.

If you think downloading the wrong package and changing its name can trick the installer, you must have a really low opinion of Xposed. The filename of the .zip has nothing to do with installing the framework. What the installer installs is governed by what's inside xposed-v89-sdk22-arm64.zip\META-INF\com\google\android.
[Fire HD 8 and HD 10 General] JJ2017:
Hi, I downloaded 'XposedInstaller_3.1.5.apk' from the Xposed page you link in the OP, made it a system app using Link2SD, opened it and clicked download 'V89' (that was the only variant offered), got error as reported by kirin-h (ARM SHOULD BE ARM64) - there was no option to download 'xposed-v89-sdk22-arm64' - so I followed the procedure by kirin-h and that worked. Great OP by the way - everything else has worked just fine :good:
[Fire HD 8 and HD 10 General] DragonFire1024:
I've finally got it! Found a way to mod the SystemUI without making it crash and burn on reboot. This process looks like it also does at least two things.

1) appears to keep the signature intact.

2) System UI keeps all it's original info, ie original install date, etc while marking the APK as UPDATED.

I haven't tried to see if it will trick a non rooted tablet via package installer yet.
[Fire HD 8 and HD 10 General] DragonFire1024:
ROM update: some progress has been made. I've gathered everything needed to get a ROM up and running. Looks like I can port over most of the system from the Fire 7 ROM. The tests I've been doing show Many of the components are compatible to the HD 10. Im pretty sure I have all I need. It's just a matter of tweaking some things which I think I'll be done with later today. If so, I'll be able to perform the first flash to the HD 10 :D
[Fire HD 8 and HD 10 General] ThisCrimsonDiscordia:
On the edge of my seat, keep us posted!
[Fire HD 8 and HD 10 General] retyre:
Two updates:

-- If you only care about FlashFire and don't want Xposed, here's a quick-and-dirty non-Xposed way to get FlashFire working (say, after an adb sideload and SuperSU): Change the date using busybox:

busybox date -s "201509221745"

Changing the system date has implications beyond FF, so this is just a quick fix to get FF working to do a restore, after which you should look to PAH as the permanent solution.

-- [MENTION=6680544]bibikalka[/MENTION] I have been able to get FlashFire v0.53 (there are many posts on the FF thread about things breaking post-v0.53) to load on the 2017 Fire HD by overwriting the v0.53 libflashfire.so with that from v0.24. Backup and restore work as expected and FF v0.53 pulls up many more partitions than does v0.24, but flashing .zip files just hangs w/o rebooting.
[Fire HD 8 and HD 10 General] bibikalka:
OK! I kept trying flashing zips with the replaced library in newer FF versions, but not the images. Is there any real benefit to using a hacked v0.53 version vs the v0.24?
[Fire HD 8 and HD 10 General] GamerOfRassilon:
This guide has been indispensable to me; thanks again for your efforts.

However, I did have one question about the /system partition. For the most part I have not been using FlashFire to generate my /system partitions, relying instead on the dd if=... of=...p options. However, if I have a working version of FlashFire, can I use FlashFire's backup and restore of /system ?

The use case I would envision is similar to:

Tablet is working as I intend it (and I've got FlashFire working).

I make a backup of /system and /data using FlashFire.

I screw up the system somehow (probably by messing with an Amazon file I shouldn't have), and now something doesn't work (like Kindle, Alexa, Shop at Amazon, etc.) . . . but FlashFire still works.

I restore /system via FlashFire.

Voila! I'm back to where I was.

Would that work, without jumping through the hoops of extracting system.img from system.gz?
[Fire HD 8 and HD 10 General] retyre:
Yes, you can (and should) use FF to backup and restore /system as a raw image. Read the very bottom of the OP to understand the risk of doing a live restore using dd.

I suggested the use of dd early on because of the need to install Xposed and PAH to get FF working. If you use busybox to set the date back, there's no need to install Xposed to get FF working. In such a case, you should use FF (rather than dd) to restore /system.
[Fire HD 8 and HD 10 General] retyre:
Not that I can see. It identifies many more partitions than does v0.24, but restoring bootloader-type partitions using FF is a big risk. There are some cosmetic benefits (e.g., more detail in backup progress), but it would great to get zip flashing working. IIRC, you wrote about FF v0.24 not understanding newer update scripts.
[Fire HD 8 and HD 10 General] MontysEvilTwin:
Once you have Flashfire v 0.24 working on your tablet if you pay for the pro upgrade it will still work if you then change to the correct date. Even the latest version of Flashfire (v 0.73) is time-bombed out now. I found out when I needed it to flash an Amazon Fire 7 (2015). Annoyingly, you can only buy the pro upgrade from within the working app. I did not know about the busybox hack mentioned above; so I had to install FF 0.73 my old Amazon Fire HD 7 (Amazon Tate), which is now running an unofficial Lineage OS ROM, and change the date to late March 2018 using the menu 'date an time' options. You can then open the app and pay for the pro upgrade. After doing this, if you install from Google Play to the Fire 7 tablet the app then opens and works correctly. On the Fire HD 10 you can only install FF 0.24 from an apk file and it only works if you change the date first (I did this with the exposed module) before opening.
[Fire HD 8 and HD 10 General] GamerOfRassilon:
This statement filled me with hope, but — to offer my findings — this didn't work on the HD10. (That is, I still needed to have the date changed in some fashion to make it work.) I've paid for the Pro upgrade (I believe in supporting the creators and all that), but deactivating the Per App Hacking in the Xposed module caused it to not open. (I tried to install it from Google Play Store and hoped to downgrade to FF 0.24, but that totally didn't work, to the point where I had to re-flash the system and reload from backups.)

Now, it's possible there's some strange synergy between the Google Play Store and this working; I have it installed as a /system app (using Link2SD), and self-signed (using ZipSigner) so it doesn't show up on Google Play; I uninstalled before trying to install the Google Play Store version, but it's possible something got messed up.

So, tl;dr — Even with the Pro version, FF may not work on the HD10 without a date-changing method.

(And if that's what the last sentence of the post I replied to is trying to say, I apologize.)
[Fire HD 8 and HD 10 General] retyre:
That's what I understood from that post. As written in that post, every version of FF is time-bombed at this time. Outside of the time hack (using busybox or PAH in Xposed), I believe the only version of FF that works at this time is v0.73 Pro. (I haven't verified this, please correct me if I'm wrong.) Of course, v0.73 is not of much use to users of the 2017 HD 10.

To recap, for the 2017 HD 10:

-- FF needs a time-bomb workaround. Two options here: busybox or Xposed+PAH. If you are recovering from a brick and have a backup of /system and /data, the former approach is quicker (a dd of a system.img with FF and Xposed already baked in might be another option here, but it comes with the risk of data corruption).

-- The last version of FF that works with the time hack and no other requirement is v0.24.

-- The last fully-functional version of FF that works with the time hack and an injection of the libflashfire.so from v0.24 is v0.51. This version picks up many more partitions than does v0.24.
[Fire HD 8 and HD 10 General] GamerOfRassilon:
Can you offer any more insight to that, please? Are those extra partitions worth backing up? Is there any downside to upgrading to v0.51? (Normally I'd just try to upgrade it myself, but tweaking with FlashFire always seems perilous, since — if it doesn't work and I don't get some version of FF working — I'm really stuck until I do a to-the-bones re-flashing.)
[Fire HD 8 and HD 10 General] retyre:
Of course, the partitions are worth backing up. Restore is where the risk is. Many of the new partitions are bootloader-type; I would not use FF to restore such partitions.

I have not seen any downside to v0.51 -- yet. In fact, it's able to flash update .zip files that v0.24 could not (e.g., the 5.6.1.0 update .zip). Careful when you do this; delete the bootloader images from the update or edit updater-binary before you flash.

FF is just an app; I am surprised a borked install of FF necessitated an adb sideload. Were you not able to reinstall v0.24 and use PAH? Or just overwrite base.apk in eu.chainfire.flash/?
[Fire HD 8 and HD 10 General] retyre:
1. The reason is in there. If you look carefully, you will notice that I wrote v0.53 isn't able to flash .zip files; v0.51 is. You will have to _uncheck_ two options (this isn't just a problem with v0.51): Emulate framebuffer in Settings and Mount /system read/write (after you choose the update file). If this second setting solves your problem (FF not rebooting), you may not need step (2) below.

2. Edit the _apk_ before you install. Use APK Editor Pro. The dev is now giving it away for free. Extract libflashfire.so from v0.24, choose the file-replacement option in APK Editor Pro, browse to /lib/armeabi-v7a/ in v0.51.apk and replace the file.

3. Open the update .bin in 7-Zip and delete the images folder. Next, edit updater-script in /META-INF/com/google/android/ to remove all the references to the bootloader images (just retain system, boot, and recovery).

4. See (1) above.
[Fire HD 8 and HD 10 General] MontysEvilTwin:
To clarify, all versions of Flashfire are timebombed now. Retyre is probably correct that the only version still working without some form of date modification is 0.73, with a pro licence (I have only checked 0.24 and 0.73). If you don't have a pro licence already though you will have to change the date to no later than March 31st 2018 to launch FF 0.73 and purchase the pro upgrade through Google Play. Once you have done this, it will still work with the correct date. FF 0.24 needs date modification to run (e.g. by setting the date to September 29th 2015 with the PAH Xposed module). Once open, FF 0.24 will still work temporarily if you turn off the date change in the PAH module: rebooting or quitting FF will stop it opening though. If you really don't want Xposed, the Busybox date change method described in post #111 works, but again this will not survive a reboot as the tablet corrects the date and time when it does so, presumably by connecting to an Amazon server.
[Fire HD 8 and HD 10 General] GamerOfRassilon:
I see; I missed the conversational thread and the jump between v0.51 and v0.53 at some point.

Otherwise, all of this info worked great; thank you! I have edited v0.51 FlashFire, and successfully backed up and restored my system partition as a test.

I did have one oddity with FlashFire; for some reason, it wouldn't recognize root access with SuperSU set to "prompt," even with <string name="config_eu.chainfire.flash_access">grant</string> in SuperSU's eu.chainfire.supersu_preferences.xml , even though FlashFire was listed in SuperSU's "Apps" list. (Even a reboot didn't work.) However, I eventually got it to work fine by tweaking it in SuperSU's menu; IIRC, I switched it from "Grant" to "Prompt" in SuperSU and then back to "Grant," and it started working again. I checked eu.chainfire.supersu_preferences.xml again and the config line was the same in there, so I don't know what changed . . . maybe SuperSU was just somehow getting confused by one of the previous installed versions of FF and needed to be kicked? ¯\_(ツ)_/¯ It's working now.

Thanks again!
[Fire HD 8 and HD 10 General] bibikalka:
Did you try to flash zip files in sequence with v0.51? First 5.6.1.0 zip (modified), then SuperSu zip, and even Xposed zip. If v0.51 flashes zips, I don't see why daisy chaining would not work. Btw, there is no point backing up bootloaders via FF, you can just dd, or use the update zips from Amazon. I used to dd-overwrite bootloaders on a live system all the time - never was a big issue, since bootloaders are not being read at all once the system boots up.

Btw, I've used apktool to change the library, then it needs signing, that's slightly trickier.

C:\extra\android\apktool>apktool_2.3.1.jar d ff_v0.51.apk

Now you replace libflashfire.so library from v0.24 once apk has been unpacked, and proceed to rebuild apk :

C:\extra\android\apktool>apktool_2.3.1.jar b ff_v0.51
C:\extra\android\apktool>sign.jar ff_v0.51\dist\ff_v0.51.apk
[Fire HD 8 and HD 10 General] GamerOfRassilon:
By the way, I tried to do this today, and it didn't work.

I did a fresh sideload of 5.6.0.1, then tried to do an update to 5.6.1.0 using a modified .bin of 5.6.1.0:

Open the 5.6.1.0 update in 7-Zip

Delete the /images folder

Update /META-INF/com/google/android/updater-script (see below)

Close updater-script

Confirm when 7-Zip asked if I wanted to overwrite updater-script

load FlashFire

Ensure Settings -> Emulate framebuffer is unchecked

Select "Flash ZIP or OTA"

Select the modified .bin

Make sure "Mount /system read/write" is unchecked

Tap "Flash"

An error pops up — "Warning: It has been detected that you may be trying to flash a block-level OTA, but your /system, /vendor, or /oem partition has been modified. This will likely cause the flash to fail!"

Tap "Ignore"

It reboots chugs for a while, eventually getting to the "FlashFire" screen . . .

. . . but then it quits very quickly, and boots back to my screen, where it's confirmed that it has not updated.

FWIW, this is the modified updater-script:

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);

I'd love to do an update with a modified .bin. Can you tell me where I went wrong, please?
[Fire HD 8 and HD 10 General] retyre:
Did it print the "Patching system image unconditionally..." message? If it quit without flashing, it's likely a version issue. Did you update the v0.51 .apk the way I described?

Do a quick test with a smaller .zip. For example, move busybox from /system/xbin and flash the busybox .zip in FF. Upon reboot, check whether busybox is back in /system/xbin.
[Fire HD 8 and HD 10 General] bibikalka:
So herein lies the issue - it appears that in the newer FireOS FF cannot put the system into rw mode ... It used to work in 5.5.0.0, where I could reflash SuperSu 2.82 , but now all I get is "system read only".

[MENTION=3497316]retyre[/MENTION] - did you succeed to flash any zip via FF which involves writing extra files to /system (such as busybox or SuperSu)? The FireOS update itself uses the block mode, so it's accessing things differently. Same with restore, which dd's things into the partition, without mounting it rw.
[Fire HD 8 and HD 10 General] retyre:
Yes. No issues here with flashing .zip files (incl. the 5.6.1.0 update .zip after removing the bootloader files). I have not been able to inject SuperSU in FF immediately following the 5.6.1.0 update (daisy-chained), but flashing .zip files with a SuperSU-rooted /system works as advertised.

Are you using v0.24 or something newer?
[Fire HD 8 and HD 10 General] endleesss:
I'm not clear on how to install xposed. after following the instructions, tablet is stuck on FIRE boot screen.

After installing the xposed installer apk, Where am I suppose to use the framework file: xposed-v89-sdk22-arm64.zip ?
[Fire HD 8 and HD 10 General] retyre:
After installing the Xposed framework, did you delete app_process64_xposed from /system/bin before rebooting? If you did not, connect the device to your PC (while it's stuck on the Fire boot screen), {adb shell, su, mount -w -o remount /system, cd /system/bin, rm app_process64_xposed}, and reboot.

The primary use of the installer is to manage the Xposed modules. It can also be used to install the framework, but that ship may have sailed in your case.

The order of your questions suggests you have solved your first problem ("tablet is stuck on FIRE boot screen"). Is that correct?
[Fire HD 8 and HD 10 General] endleesss:
No, I'm stuck at Fire boot screen. I did delete app_process64_xposed then reboot .
[Fire HD 8 and HD 10 General] DragonFire1024:
How long has it been there? Mine will sometimes take 2-3 mins to pass the boot screen and another 6 or 7 mins once at the optimizing screen. For both, sometimes longer. Depends how good of a root you have I suppose. This only happens to me once and I think it was with the official Xposed apk. I've used dvddandroid since.
[Fire HD 8 and HD 10 General] endleesss:
I'm having a problem with an xposed module, tablet is flashing walpaper over and over again. so i want to remove it with adb, or disable xposed.

with these, i can see a list

adb shell

cat /data/data/de.robv.android.xposed.installer/conf/modules.list

/data/app/com.e_vertise.dopa.phab7-1/base.apk

/data/app/com.aviraxp.adblocker.continued-1/base.apk

/data/app/com.gzplanet.xposed.xperianavbarbuttons-1/base.apk

/data/app/ma.wanam.youtubeadaway-1/base.apk

i don't know what command to use to remove com.gzplanet.xposed.xperianavbarbuttons-1/base.apk

I also don't know what command to use to disable xposed

Thanks
[Fire HD 8 and HD 10 General] retyre:
To uninstall the module:

adb uninstall com.gzplanet.xposed.xperianavbarbuttons

To temporarily disable Xposed:

adb shell
su
touch /data/data/de.robv.android.xposed.installer/conf/disabled
reboot

and uninstall the offending module.
[Fire HD 8 and HD 10 General] endleesss:
Xposed Install Guide Fire HD 10

I had problems installing xposed, finally figured it out, here's what i did. hopefully it can help someone else.

1. Download xposed installer: https://xdaforums.com/xposed/material-design-xposed-installer-t3137758.

File name: XposedInstaller_by_dvdandroid_25_12_17.apk

2. Download xposed framework: https://dl-xda.xposed.info/framework/sdk22/arm64/xposed-v89-sdk22-arm64.zip

Save the file in your device.

3. Install xposed in device from step 1

4. Run xposed app on device. Tap official.

5. Tap xposed-v89-sdk22-arm. It will expand, tap xposed-v89-sdk22-arm64.

6. Tap Install/Update

7. Are you sure pop up, Tap OK

8. Look at the path where it downloaded the file, it's basically sdcard/Xposedinstaller.

9. DON"T click on the pop up cancel or ok.

10. go to the download location sdcard/Xposedinstaller via switch app button, then file explorer app

11. Copy the framework zip file from step 2 into the sdcard/Xposedinstaller folder, and over write the file.

12. Go back to Xposed installler, click OK on the Are you sure pop up window

13. Watch the Xposed window till error msg shows up.

14. Go to /system/bin/ and delete the file: "app_process64_xposed"

10. Reboot
[Fire HD 8 and HD 10 General] retyre:
The file downloaded in step 7 should be identical to the one in step 2. Check the hashes.
[Fire HD 8 and HD 10 General] endleesss:
File name downloaded is the same. The location is different than OP
[Fire HD 8 and HD 10 General] Fathor:
Does this Tutorial also works with a 5th Gen HD 10 and 5.6.1.0 Fire OS?
[Fire HD 8 and HD 10 General] DragonFire1024:
Hello. Can someone with an HD 10 please reboot to recovery and go into fastboot mode type:

fastboot help

and take a few pictures of your screen with all the options listed? I need to be proven wrong about something and the only way to do that is to see the screen on a device not of my own. I'm probably getting excited over nothing though.
[Fire HD 8 and HD 10 General] JJ2017:
Hi, Is this any use?

It's from Fire 10HD (7th Gen) rooted and with Xposed installed as per retyre's post.

Cheers.
[Fire HD 8 and HD 10 General] DragonFire1024:
Thanks. Just wanted to make sure I was seeing the same things. Haven't looked at that menu in a while. I thought I was seeing things.
[Fire HD 8 and HD 10 General] huffmybrd:
anhybody else running into issues with {LP}gravitybox not opening?
[Fire HD 8 and HD 10 General] DragonFire1024:
Running just fine for me.
[Fire HD 8 and HD 10 General] huffmybrd:
grrrr, ive tried uninstalling and reinstalling a bunch of times with no luck
[Fire HD 8 and HD 10 General] DragonFire1024:
Did you make sure to change the setting in superSu from 'prompt' to 'grant' for root access?
[Fire HD 8 and HD 10 General] huffmybrd:
Yepp, that was one of the first things i did
[Fire HD 8 and HD 10 General] DragonFire1024:
I would uninstall it, clear cache in recovery and in storage settings, look in data/app and make sure there are no folders left for it when you are done clearing those things. Won't hurt to uninstall and reinstall Xposed. If you still have problems, I'll have to scratch my head a bit and say beats me. Haven't had an issue yet and I don't believe there's been a recent update to the module.
[Fire HD 8 and HD 10 General] huffmybrd:
seems its a head scratcher then lol. did everything ya said with still no luck. but bootmanager opens fine so theres gotta be something weird with gravitybox itself
[Fire HD 8 and HD 10 General] DragonFire1024:
Actually there was a recent update to the module a few days ago. It could be a developers mistake , but I'm not sure. I would suggest using an older version if possible. I'll see if I can contact the developer.
[Fire HD 8 and HD 10 General] huffmybrd:
seems that fixed it! the newest version (5.5.0) wasnt working so i tried the one before that and everythings all good!!!

quick question though. is it safe to adjust the QS toggles? im just trying to get rid of a few cuz my kiddo will never use em lol
[Fire HD 8 and HD 10 General] DragonFire1024:
Pretty much none of the quick setting toggles on GravityBox will work for this device or any Amazon tablet for that matter. About the best you can do is toggle some of the status bar icons like Wi-Fi, the battery icon, clock settings, you can use ultimate notification settings to shut off system user interface notifications, which will also limit the amount of icons to appear in the status bar, but because Amazon doesn't use the standard Android status bar or quick settings, none of the standard QS options will work. However it is a good note to add that GravityBox is great for the navigation bar especially if you are looking for an app to substitute long pressing the home button to bring up Google Assistant. Works absolutely perfect. You can also customize the navigation bar colors...at least the keys anyways.

Edit: if Amazon did use a standard Android quick settings or quick tiles, they can be edited and removed via secure settings. A good example of this is the Galaxy S7. without secure settings removing icons from status bar or the Quick Settings bar with ultimately put the device in a never ending boot loop. It just so happens the only way to edit those settings is through a secure settings application.
[Fire HD 8 and HD 10 General] DragonFire1024:
I've gotten a hold of the developer. So if you can explain the issue in detail, that would be awesome.