Database Users

[Guide Finder] Root, Upgrade, Back to Stock + More

These guides are for 2014 Fire HD 6 and 7. Don't use for any 2015 model. If your device has a micro-SD slot, it's 2015.
All root/upgrade guides install Gapps
Credit: Guides for rooting OS above 4.5.3 rely on powerpoint45's instructions for downgrading to 4.5.3 to obtain root. Thanks @[COLOR="Black"]powerpoint45[/COLOR]!
Basic Root and Upgrade
UPGRADE - Upgrade guides link back to root instructions, so you can just begin here.​
Upgrade to Lollipop
- [TUT] Install [FireOS 5.1.2, Feb 26, 2016, "blue shade"], ROOT & GAPPS http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Upgrade to OS 4.5.5
- [How to] Upgrade to 4.5.5 (or other 4.5.x) with root in TWRP: http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
- [How to] Upgrade to 4.5.4 and keep TWRP and root: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-4-5-4-twrp-root-t3141648
ROOT​
Root, install TWRP, and upgrade
-[ROOT, v2.0] + FireOS 4.5.4 + fully working latest GAPPS http://forum.xda-developers.com/fire-hd/general/root-v2-0-fireos-4-5-4-gapps-t3150613
Video Root and Upgrade to Lollipop
Step-by-step video guide to root and upgrade to Lollipop
- OS 5.0 + ROOT + GAPPS + Play Store VIDEO TUTORIALhttp://forum.xda-developers.com/fire-hd/general/os-5-0-root-gapps-play-store-video-t3238734
Return to Stock
[How to] Restore full stock FireOS; http://forum.xda-developers.com/fire-hd/general/how-to-restore-stock-fireos-t3164267
Obsolete
Detailed Root and Upgrade to Lollipop (for never-rooted devices)
Step-by-step "newbie friendly" guide to root and upgrade to Lollipop
- [Root] OS 4, 5.0.n and Install Lollipop & Gapps ("Newbie Friendly") http://forum.xda-developers.com/fir...lipop-os-5-t3172408/post62188341#post62188341
Out of date as of 3/3/16
- [ROOT] With working PlayStore Google Apps + Custom Launcher + superSU http://forum.xda-developers.com/fire-hd/general/root-supersu-stable-appstore-custom-t3113311
Install ADB Drivers for Windows
Illustrated - Run ADB in normal and sideload mode from any folder location
- [GUIDE] Install Windows ADB Drivers for Fire HDs ("Newbie Friendly"): http://forum.xda-developers.com/fire-hd/general/guide-install-windows-adb-drivers-fire-t3189000
Video
- Install ADB USB Drivers for Fire HD 6/7 (normal & sideload mode) (Windows): https://www.youtube.com/watch?v=CyJlmTtLsIg
Other Good Stuff
Temporarily Install TWRP on Rooted OS 5: http://forum.xda-developers.com/showpost.php?p=62011272&postcount=2
Links to Stock ROM Update bins
Fire HD ROM links : http://forum.xda-developers.com/fire-hd/general/fire-hd-rom-links-t3173102
Lollipop Info, Issues, Tips/Tricks and Workarounds
[Discussion] Lollipop on Fire HD : http://forum.xda-developers.com/fire-hd/general/qa-lollipop-fire-hd-t3167532
Disable OTA, Amazon Launcher, Appstore and More
[How To] Disable System Apps and Services (includes OTA): http://forum.xda-developers.com/fire-hd/general/how-to-disable-apps-services-includes-t3165348
Use a Script to Disable/Enable Sys Apps, and Switch Launchers with One Tap:
[FireOS 5.x + ROOT] Quickly switch to Amazon UI and back: http://forum.xda-developers.com/fire-hd/general/fireos-4-5-x-root-quickly-switch-to-t3145613
Get Wallpaper on OS 4 Custom Launcher
[HOW TO] Get Wallpaper on Custom Launcher: http://forum.xda-developers.com/fire-hd/general/how-to-wallpaper-custom-launcher-t3123009

:fingers-crossed:

Another where's root guide question, another nudge

Gapps tutorial for Hd6/7
DoLooper said:
Another where's root guide question, another nudge
Click to expand...
Click to collapse
It will be a great help someone can compile a guide about how to install gapps on hd 6 or 7 running 5.2.X. there are lot of confusion about which xpose and gapps and in which order should flash to get them working. (specially who are already on 5.2.x without gapps)

Nudge

I changed the title and added a bunch more guides. Post if I got something wrong or left out something you think is helpful. thx.

Added @powerpoint45's new video guide

DoLooper said:
Added @powerpoint45's new video guide
Click to expand...
Click to collapse
Coolio

:angel:

:fingers-crossed:

Hi everyone,
I have the Kindle Fire HD 6 4th Gen currently on the developer preview Fire OS 5.0.1..... Is there any way to get this rooted????
I've tried Kingroot v4.90 but no luck....

Pardon the dumb question, but from reading the guides here, my conclusion is: there is no way to directly root 5.1.2.1 and install playstore / gapps. One must do either
1) regress to 4.5.3 / root / upgrade to 5.1.2.1 + gapps + xposed
or
2) sideload 5.1.2 factory image and flash that, root it, then install gapps and xposed (and update disabler) <<--- probably recommended
Did I understand that correctly?
I am familiar with bootloader / gapps / roms / Xposed and all that. I play with my Nexus 7 / Moto X stuff all the time. Fire HD is primarily an e-reader, but would be nice to have Playstore on it too.

Is there a way to root a Fire HD 7 4th gen 5.3.1.0?

[How To] Upgrade Rooted JULY Developers Preview to Official 5.2.2 Release

[EDIT Oct. 25] Here's what I did--cleaned up and corrected for bootloaders--to install the official 5.2.2 update (build date September, 2015) on myrooted tablet running Developers Preview, build date July, 2015.This is only for those who rooted and installed the dev preview before the upgrade/downgrade troubles. It let's you keep all your stuff.
Few important things:
If you don't reset/wipe in TWRP you can keep most of your stuff, including homescreen layout, play store and all apps. However . . .
Google framework, account manager, contact sync and calendar sync get deleted with the update.
I didn't flash Gapps and got bogus insufficient space error [130 Mb free] when I tried later. Restoring framework fixed everything, but it may be best to flash new Gapps (although that can cause problems when update doesn't completely wipe /system, like this one). Up to you.
Oct 26 Update: Based on reported "insufficient space" flashing Gapps--plus testing and researching contacts and calendar--I suggest not flashing Gapps but simply backing up Google services framework before you upgrade and restoring it after. The other google system apps that get deleted don't seem to be needed; if you want to sync Google contacts & calendar on the Fire you can add your google account(s) in Settings, same as on any Android. If you don't want Amazon's stock calendar or contacts, get another from the Play Store. I've updated the instructions to reflect this.
.
HDXposed module is no longer needed for working Play Store.
Xposed Framework: The update doesn't support the version we used with the July dev preview. You must either flash the latest version or flash the uninstaller if you don't want Xposed anymore.
Stock launcher now = com.amazon.firelauncher
Home key now defaults to stock launcher until you pm disable it. (No prompt anymore)
Backup Google Services Framework.
Turn off wifi (airplane mode) and plug in.
Download the zips:
* September 5.2.2 update (thanks @Hariiiii !) and rename extension from bin to zip.
update-kindle-full_ariel-20.5.2.2_user_522053520.bin: https://mega.nz/#!ZI1wTL6L!xbDNDvaJjLUWwqe8J9awAs4xNQvxreXCmZ1I6cWTLVA
* Latest Xposed Installer or Uninstaller from here: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
Installer = Xposed-v74-sdk22-arm-by-romracer-20150911.zip
Uninstaller = xposed-uninstaller-20150911-arm64.zip
* Gapps (if using)
tk_gapps-modular-pico-5.1.1-20150920-signed.zip: http://forum.xda-developers.com/android/software/tk-gapps-t3116347
* 5.2.0_stock_recovery_only.zip
Attached to bibikalka's lollipop post: http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
Get latest SuperSU apk (?) Don't know if it's required, but I installed it.
- SuperSU 2.52 Beta: http://www.apkmirror.com/apk/chainfire/supersu/supersu-2-52-android-apk-download/
Follow Step 1 of @bibikalka's guide to temporarily install TWRP and while in TWRP:
a. Flash the update
b. Flash Xposed (installer or uninstaller)
c. Flash 5.2.0_stock_recovery_only.zip
d. Choose boot to recovery and install SuperSU when TWRP prompts you.
Confirm you're in recovery, then boot to system and press Exit at "Welcome to Fire OS 5!"
In OS, see if SuperSU is still managing root access. If it's not or you want to update, install the new SuperSU apk and update binaries.
(Wait to reboot unless you can't get su access at next step.)
Block OTA:
a. Disable dcp or otaverifier (whichever you prefer)
b. Rename system/priv-app/devicesoftwareota/devicesoftwareota.apk extension to apk_
Restore Google Services Framework and reboot.
Turn on wifi and sign in to playstore.

Thanks for the guide!

deleted

putridfoetus said:
Will this work if my tablet is running the september 5.2.2 and never rooted? Just downgrade to 4.5.3 and go from there?
Or can I just install twrp to flash xposed and get supersu, then reflash the stock recovery?
Click to expand...
Click to collapse
As far as I understand from my experience of going from unrooted september 5.2.2 to rooted 4.5.3 to rooted september 5.2.2, it should work fine if you go via that route.

putridfoetus said:
Will this work if my tablet is running the september 5.2.2 and never rooted? Just downgrade to 4.5.3 and go from there?
Or can I just install twrp to flash xposed and get supersu, then reflash the stock recovery?
Click to expand...
Click to collapse
This is only for rooted tablets. Follow the steps Hariiiii describes here. There are guides for what he did.

[How To] Upgrade Rooted Developers Preview to Official 5.2.2 Release
Finally i follow the turorial and i forgive flash 5.2.0 recovery and gapps and it works then i flash twrp again by adb and i did wipes and flash update, gapps, xposed and 5.2.0 recovery and i hard bricked my fire. Why?
I order a replacement. What i have to do to have fire os 5 final with root, play store and other launcher?
Thanks

You got bricked because you used a tutorial to root that said at the top, don't use/on hold. Maybe we'll have a new method when you get your replacement.

Could we possibly get a video tutorial on how to do this?
(May be easier for some.)

Ooh, I don't do video and doubt anyone will for this, but that would be kind. You can pm me with questions.

I'll see if I can do a video. However, can you add to the guide how to get to the rooted preview at the start of the guide. I bricked my kindle going from 5.0 or so to 4.5.3 up again to get here and bricked. Probably my bad but it would help if you provide some initial steps for those who just got their tablets. Btw my replacement comes in tomorrow do I'll see what I can do for the video if possible.

Nice guide!
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too

bibikalka said:
Nice guide!
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too
Click to expand...
Click to collapse
Hdxposed is not necessary

cm11noob10 said:
I'll see if I can do a video. However, can you add to the guide how to get to the rooted preview at the start of the guide. I bricked my kindle going from 5.0 or so to 4.5.3 up again to get here and bricked. Probably my bad but it would help if you provide some initial steps for those who just got their tablets. Btw my replacement comes in tomorrow do I'll see what I can do for the video if possible.
Click to expand...
Click to collapse
Think we have some confusion. I'll need to make this clearer: This guide is only for people who already have the rooted developer preview--people who did the downgrade/upgrade using the July build. There is no longer a way to use the developer preview to gain root; the latest version (September) ends up causing bricks, as you learned the hard way. Fortunately, it looks like the official 5.2.2 update that Amazon is now OTA distributing can be successfully used in the downgrade/upgrade operation. I'm sure guides for that will be out soon.

Then I'll look for a guide on that and go from there.
Thx for the replies.

bibikalka said:
I wonder if HDXposed is still needed to keep the PlayStore working. The clarity on installing GAPPS is kind of missing too
Click to expand...
Click to collapse
Good feedback, thanks. HDXposed is indeed not needed, which of course means Xposed isn't required. If you don't install the new Xposed, though, I suspect the old, non-working one will stay on system even with factory reset. Your thoughts?
(Edit: NVM. Yes, they'll still have old Xposed, so will need new.)
Yeah, Gapps <sigh> It's such a personal thing. (Thinking about how to handle.)

DoLooper said:
You got bricked because you used a tutorial to root that said at the top, don't use/on hold. Maybe we'll have a new method when you get your replacement.
Click to expand...
Click to collapse
But my first time i update and i didn't flash 5.2.0 recovery and work perfectly and i haved root. This mean that it isn't necessary flash 5.2.0 recovery?
Enviado desde mi SM-N910F mediante Tapatalk

davigar said:
Finally i follow the turorial and i forgive flash 5.2.0 recovery and gapps and it works then i flash twrp again by adb and i did wipes and flash update, gapps, xposed and 5.2.0 recovery and i hard bricked my fire. Why?
Click to expand...
Click to collapse
I'm looking into this again. When you flashed "5.2.0 recovery" which zip did you use, 5.2.0_stock_recovery_only.zip or 5.2.0_stock_recovery_uboot.zip? Thanks.

I flashed 5.2.0_stock_recovery_uboot.zip

davigar, you got the developer preview in order to downgrade to OS 4.5.3 and root, is that right? If not, what OS were you on and how did you install it?
EDIT: @davigar Wait a minute--did you not root? Did you just use this tutorial to install the update and that's when you forgot recovery? This will make a difference. Thanks.

I upgrade my kindle to developer preview then i downgrade to 4.5.3, root and upgrade it to 5.2.2 developer with gapps. I followed the newbie friendly tutorial when i bought it. Sorry for my english [emoji16]
Enviado desde mi SM-N910F mediante Tapatalk

FireOS 5.3.2 has arrived

FYI - it has been reported FireOS 5.3.2 is being distributed via OTA update (here). The same individual indicated Kingroot was ineffective suggesting this build is not rootable at present. Also unknown is whether a rollback to FireOS 5.3.1 is possible. Suggest not trying a rollback unless you are comfortable sacrificing the device. Those on a lower versions of FireOS should consider blocking OTA updates via SuperTool (here) if you wish to preserve the option to root.
Edit: see following post by @zippy411. Appears a rollback to FireOS 5.3.1 (rootable) is viable.

Davey126 said:
FYI - it has been reported FireOS 5.3.2 is being distributed via OTA update (here). The same individual indicated Kingroot was ineffective suggesting this build is not rootable at present. Also unknown is whether a rollback to FireOS 5.3.1 is possible. Suggest not trying a rollback unless you are comfortable sacrificing the device. Those on a lower versions of FireOS should consider blocking OTA updates via SuperTool (here) if you wish to preserve the option to root.
Click to expand...
Click to collapse
I decided to offer up my tablet for testing. One of the two kindle fires I was going to root updated itself to 5.3.2 as soon as it was turned on. I am going to attempt to restore it back to 5.3.1.0
I followed the instructions in this youtube video.
https://www.youtube.com/watch?v=RQLoH-ahjy4
I used this as my source for the firmware. I downloaded 5.3.1.0
http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3
I had some trouble getting the kindle recognized in usb debug mode even after installing correct drivers and attempting to manually update the drivers the usual way but was successful using this method in Windows 7 Pro 64-bit.
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select show all devices
select Amazon.com
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
It now states I am running FireOS 5.3.1.0
I am now going to root this device using the latest supertool and install the fire nexus rom.
I successfully rooted it and installed the fire nexus rom.
I found that Kingroot 4.9.6 151 works best instead of the kingroot included in supertool. run kingroot and then the supertool process like normal to replace kingroot with supersu.
I also had to install flashfire manually versus the one included in supertool.
good luck all!

great news that we can downgrade without issue.
P.S: Maybe my HD 10 5.3.1.0 will never see the light of getting root as Fire 7" as Amazon is pushing another update already

Did you try to rip the Alexa voice assistant APK(s) out and try them on other ROMs at all? I'd be very interested in being able to do this. Since my Fire was on 5.0.1 when I switched it to CM, I don't want to have to lose being able to use TWRP in order to get the files myself (via upgrade, root, and then stuck with flashfire).

Orbiting234 said:
Did you try to rip the Alexa voice assistant APK(s) out and try them on other ROMs at all? I'd be very interested in being able to do this. Since my Fire was on 5.0.1 when I switched it to CM, I don't want to have to lose being able to use TWRP in order to get the files myself (via upgrade, root, and then stuck with flashfire).
Click to expand...
Click to collapse
Quite likely you can retain 5.0.1 bootloader while 'upgrading' to FireOS 5.4.x (when released) using the time proven procedure in this thread yielding the best of both worlds. Backup your existing CM install in TWRP so you can revert back after grabbing the Alexa components. You could do the same with the FireOS build and toggle between the two (awkwardly) via TWRP backup/restore. Can do the same thing with recent FlashFire builds although I would always retain a true nandroid (ie: twrp backup) of CM as a fallback.

zippy411 said:
I decided to offer up my tablet for testing. One of the two kindle fires I was going to root updated itself to 5.3.2 as soon as it was turned on. I am going to attempt to restore it back to 5.3.1.0
I followed the instructions in this youtube video.
https://www.youtube.com/watch?v=RQLoH-ahjy4
I used this as my source for the firmware. I downloaded 5.3.1.0
http://forum.xda-developers.com/showpost.php?p=62986665&postcount=3
I had some trouble getting the kindle recognized in usb debug mode even after installing correct drivers and attempting to manually update the drivers the usual way but was successful using this method in Windows 7 Pro 64-bit.
Open device manager Settings>Devices>Device Manager
Connect Kindle Fire
Enable USB debugging
(If Kindle is not listed as Android>Android Composite ADB interface)
select Other Devices>Fire
Right Click>Update Driver Software
Browse my computer for Driver Software
Let me pick from a list of drivers on my computer
select show all devices
select Amazon.com
select Android or Android Phone (or ADB Interface or Android Device)
Select Android Composite ADB interface
or Android Composite ADB interface
It now states I am running FireOS 5.3.1.0
I am now going to root this device using the latest supertool and install the fire nexus rom.
I successfully rooted it and installed the fire nexus rom.
I found that Kingroot 4.9.6 151 works best instead of the kingroot included in supertool. run kingroot and then the supertool process like normal to replace kingroot with supersu.
I also had to install flashfire manually versus the one included in supertool.
good luck all!
Click to expand...
Click to collapse
I just followed your lead and it worked!!!
I had 5.3.2.0 on my Kindle Fire 7" Gen 5 tablet.
I booted the tablet into recovery (adb reboot recovery) and then used the "adb sideload" command to flash the 5.3.1.0 firmware.
The latest Kingroot did not work, so I downloaded the version you suggested 4.9.6 (from http://www.apkmirror.com/apk/kingro...-release/kingroot-4-9-6-android-apk-download/)
That version did successfully root the device!
Now I'm playing with FlashFire. If all goes well, I'll be running CM12.1 soon!
Update: CM12.1 is installed and running great!

ManWithCamera said:
I just followed your lead and it worked!!!
I had 5.3.2.0 on my Kindle Fire 7" Gen 5 tablet.
I booted the tablet into recovery (adb reboot recovery) and then used the "adb sideload" command to flash the 5.3.1.0 firmware.
The latest Kingroot did not work, so I downloaded the version you suggested 4.9.6 (from http://www.apkmirror.com/apk/kingro...-release/kingroot-4-9-6-android-apk-download/)
That version did successfully root the device!
Now I'm playing with FlashFire. If all goes well, I'll be running CM12.1 soon!
Update: CM12.1 is installed and running great!
Click to expand...
Click to collapse
Will it be possible on 6th gen as well?
I can't quite understand the difference between the two software-wise.

Apart of the NEW Alexa, does anyone here has noticed something NEW or any improvements with the latest FireOS 5.3.2 update?

Can we root it after the update with dirty cow?

just4u32 said:
Will it be possible on 6th gen as well?
I can't quite understand the difference between the two software-wise.
Click to expand...
Click to collapse
Hi - this forum is for 5th gen Fire (released fall 2015); you'll want to ask you question here. While 5th and 6th gen devices often run similar builds of FireOS there are some differences attributable to hardware variations and software release cycles. What works on one type of device may or may not on others. Rollbacks can be especially dangerous as bootloaders/kernels generally differ across device types. A failed rollback attempt typically yields a bricked device with no recovery options. In short, I would not generalize across device types.

Reuben Talbott said:
Can we root it after the update with dirty cow?
Click to expand...
Click to collapse
To my knowledge there is no indication Dirty Cow has any meaningful relevance on this device. Although the underlying vulnerability may exist there is no evidence it has been successfully exploited on FireOS.

OK I thanks

Reuben Talbott said:
Can we root it after the update with dirty cow?
Click to expand...
Click to collapse
I tried rooting it with Dirty Cow after the update to 5.3.2.0, but was unsuccessful. The device would reboot while it was attempting the exploit. Flashing back to 5.3.1.0 made it rootable again (via Kingroot version 4.9.6).

5.3.2 > 5.3.1 downgrade IS possible
Good Afternoon,
I recent purchased a Kindle Fire 7 (11/11/16) and it was upgraded to 5.3.2. I was able to downgrade the OS to 5.3.1 using the ADB sideload method and then root using Kingroot (11/18/16). Be sure to block OTA updates once completed. Have not seen any issues yet and will report if i do.
Good Luck everyone.

ManWithCamera said:
I tried rooting it with Dirty Cow after the update to 5.3.2.0, but was unsuccessful. The device would reboot while it was attempting the exploit. Flashing back to 5.3.1.0 made it rootable again (via Kingroot version 4.9.6).
Click to expand...
Click to collapse
Thanks

Tried to disable lockscreen ads using adb (com.amazon.kindle.kso), but when I touch the special offers icon on lockscreen, I get a window that says Selected Offers. Is there another package that I should be disabling? I'm on Fire OS 5.3.2.

Hello, i have the latest Fire 7".
If i rollback from 5.3.2 to 5.3.1.0 and i use Kingroot, only root, can I go to back to stock software if I have to give it to Amazon assistance?
Onlye root, not recovery modded or other rom.
Thanks
p.s.: not use slang with me, thanks

Palux said:
Hello, i have the latest Fire 7".
If i rollback from 5.3.2 to 5.3.1.0 and i use Kingroot, only root, can I go to back to stock software if I have to give it to Amazon assistance?
Click to expand...
Click to collapse
Yes - 5.3.1 can be reloaded again if pure stock is desired. However, this is not generally required for warranty exchanges (the only type of hardware assistance Amazon provides) as they do not perform a detailed inspection of returned devices.

Hey there, I followed the instructions as provided and everything seemed to work fine but now I am stuck and not sure if I should reboot it.
1. Downgraded from 5.3.2 to 5.3.1 -> worked
2. Install Kingroot with "AmazonFire5thGenSuperTool" and Root the device -> worked
3. Install FlashFire with "AmazonFire5thGenSuperTool"-> that did not work. I got the message that the APK is invalid.
4. Install Google Play Store
5. Install FlashFire from Google Play Store -> was that ok?!
6. Configure it as described in this thread which was linked. CM12 + Gapps Nano
I was confused because the instructions are a little bit different regarding the checkboxes compared to the other thread but I followed those instructions.
Device rebooted, and now I am seeing an Amazon Logo on the Screen since about 1,5h. It does not reboot or anything, it just shows the Amazon Logo
Should I reboot it or is it actually flashing right now since hours?
br

Arret said:
Hey there, I followed the instructions as provided and everything seemed to work fine but now I am stuck and not sure if I should reboot it.
1. Downgraded from 5.3.2 to 5.3.1 -> worked
2. Install Kingroot with "AmazonFire5thGenSuperTool" and Root the device -> worked
3. Install FlashFire with "AmazonFire5thGenSuperTool"-> that did not work. I got the message that the APK is invalid.
4. Install Google Play Store
5. Install FlashFire from Google Play Store -> was that ok?!
6. Configure it as described in this thread which was linked. CM12 + Gapps Nano
I was confused because the instructions are a little bit different regarding the checkboxes compared to the other thread but I followed those instructions.
Device rebooted, and now I am seeing an Amazon Logo on the Screen since about 1,5h. It does not reboot or anything, it just shows the Amazon Logo
Should I reboot it or is it actually flashing right now since hours?
Click to expand...
Click to collapse
Something went wrong; the Amazon Logo should display for <30 sec. You will need to reload FireOS 5.3.1 from the stock recovery menu and start over. Guidance here, here. Once recovered post back for further assistance loading CM 12.1.

Steps to install stock 4.5.5.3 rom after deleting recovery in twrp

Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.

Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.

treysky54 said:
Wanted to add a few more clear details...
Device: Fire HDX 7" Thor
Came w/ 4.5.5.2 (never updated to 4.5.5.3)
Wanting ROOT.
No stock backup in TWRP (accidently wiped)
Running AOSPExtended 7.1.2 w/ gapps Pico
Tried multiple 1-click root methods (pc and apk versions)
Installed older rom at one point (lineage11 android 4.4.4) in hope root can be made on kitkat in case nougat was the issue.
Can I still get root from any method at my current state WITHOUT reverting back to stock fireos?
Notice that I do own a second hdx 7" that I've used kingroot on BEFORE wiping anything lol and it rooted just fine. But not this one after the rom(s) install. I guess I just don't know where to go after failing to get root post-twrp/rom.
Click to expand...
Click to collapse
Why can't you just flash SuperSu or Magisk via twrp?

Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm

treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.

gwardsc65 said:
Why can't you just flash SuperSu or Magisk via twrp?
Click to expand...
Click to collapse
gwardsc65 said:
This should be easy, unless I'm missing something.. Worst case get into twrp recovery and flash Asop or whatever custom rom, Gaaps, and SuperSu or Magisk ALL in the same session. Wipe cache and reboot.
Click to expand...
Click to collapse
Sorry mate, not the way it works on this device (3rd gen HDX). Bootloader must be unlocked to obtain root on any custom ROM based on Android 5+. There are no (reasonable) workarounds or exceptions.
treysky54 said:
Hi, the times I've done that, ended with a reboot into the Kindle logo (gray, not the gold). I left it for ages it seems with no change. So I would reboot back. Thought: don't tell me I needed to adb at that stage... never thought about it because it wasn't showing fastboot. Hmmm
Click to expand...
Click to collapse
Expected symptom when attempting to secure root on a bootloader locked HDX.

Ahhh... so it somehow got locked back and need to redo the procedure?

treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
No need to restore stock. Use MTP in TWRP to transfer (push) a KitKat based custom ROM zip to device, install and then go through bootloader unlock procedure. Suggest using Fire Nexus as the interim ROM as it is self contained with GApps and SuperSU built in.
https://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931
---------- Post added at 03:38 AM ---------- Previous post was at 03:37 AM ----------
treysky54 said:
Ahhh... so it somehow got locked back and need to redo the procedure?
Click to expand...
Click to collapse
That's what the symptoms suggest. What makes you believe the device was properly unlocked sometime in the past?

treysky54 said:
Unless I'm wrong, these are the steps to reinstall 4.5.5.3 fireos back into the hdx 7" thor after stock recovery was wiped in twrp.
1) Download fireos 4.5.5.3 last version from amazon official site.
2) Rename .bin to .zip
3) Put into root (sdcard) on fire
4) Boot into twrp recovery, install said zip
5) Done??? (I assume the one zip will install to the 3 partitions (.img) on the fire?
My story:
I followed the instructions, unlocked my bootloader, and installed custom rom. No problem. Problem is, I didn't make a stock fireos backup first. The real kicker, I advanced wiped everything in twrp before the custom rom. Now it seems I have nothing but twrp and my custom rom.
NOT ACTUALLY WANTING STOCK OS BACK, but I didn't root at the time of the custom rom install. I didn't care about root at the time, just the custom rom. But now I DO want root, but kingroot etc won't work now. I assume it only works with the stock install? Because I'm now on aospextended, it appears I'm on a Kindle Fire 7" on android 7.1.2
Any suggestions on how to simply get root now at the current condition my hdx is in now? Thanks alot, been coming here for a long time. I'm usually the type to just "try and see" and not really ask many questions, but man I don't wanna brick this and I know how touchy these can be.
Click to expand...
Click to collapse
Can I do it without TWRP????

8HD 2018 (karnak): How to re-install stock rom but keeping TWRP?

I have already unlocked my 8hd (karnak) 2018 and flashed TWRP. It is now running Lineage OS 14.1.
I have 2 queries:
1. How can I re-install FireOS but keeping the device unlocked with TWRP recovery mode?
2. Where to download an older version FireOS which is rootable by mtk-su? (I want to remove some Amazon stuff as a Root user)

drdtyc said:
I have already unlocked my 8hd (karnak) 2018 and flashed TWRP. It is now running Lineage OS 14.1.
I have 2 queries:
1. How can I re-install FireOS but keeping the device unlocked with TWRP recovery mode?
2. Where to download an older version FireOS which is rootable by mtk-su? (I want to remove some Amazon stuff as a Root user)
Click to expand...
Click to collapse
As long as you have the latest version of TWRP for Karnak (3.3.1-0) you should just be able to flash the standard Amazon software 'update' (change '.bin' extension to '.zip'). You may have to wipe system and data first if changing OS. Don't wipe 'internal storage' if you want to keep your files (pictures, downloads etc.). One time I flashed a standard Amazon software package my recovery was overwritten, but if you have an mtk-su vulnerable version it is easy to redo the unlock with no opening of the tablet required.
The last build of OS 6.3.0.1 (mtk-su vulnerable) can be downloaded by clicking on this link: https://fireos-tablet-src.s3.amazonaws.com/qGCnGoVclGgaVdoLm9521w9byK/update-kindle-NS6301_user_1638_0001309042308.bin.

MontysEvilTwin said:
As long as you have the latest version of TWRP for Karnak (3.3.1-0) you should just be able to flash the standard Amazon software 'update' (change '.bin' extension to '.zip'). You may have to wipe system and data first if changing OS. Don't wipe 'internal storage' if you want to keep your files (pictures, downloads etc.). One time I flashed a standard Amazon software package my recovery was overwritten, but if you have an mtk-su vulnerable version it is easy to redo the unlock with no opening of the tablet required.
The last build of OS 6.3.0.1 (mtk-su vulnerable) can be downloaded by clicking on this link: https://fireos-tablet-src.s3.amazonaws.com/qGCnGoVclGgaVdoLm9521w9byK/update-kindle-NS6301_user_1638_0001309042308.bin.
Click to expand...
Click to collapse
Thank you very much.
May I also ask where to download an older version of FireOS (with mtk-su vulnerability) for Fire 7 (Austin) 2017 which is also unlocked with TWRP recovery mode?

drdtyc said:
Thank you very much.
May I also ask where to download an older version of FireOS (with mtk-su vulnerability) for Fire 7 (Austin) 2017 which is also unlocked with TWRP recovery mode?
Click to expand...
Click to collapse
The Fire 7 (7th generation, Austin) is not vulnerable to mtk-su. The shorting method is the only way to unlock this model.

MontysEvilTwin said:
The Fire 7 (7th generation, Austin) is not vulnerable to mtk-su. The shorting method is the only way to unlock this model.
Click to expand...
Click to collapse
I have already unlocked my Fire 7 Austin using the shorting method and flashed the Fire-Nexus rom on it. Very happy with the slick response under Fire-Nexus. I can use Open Camera apk which works fine using the back camera. The only slack is that the front camera for taking selfies does not work. Thus I am tempted to revert to FireOS and trim down the Amazon stuff as a Root user with the help of mtk-su.

drdtyc said:
I have already unlocked my Fire 7 Austin using the shorting method and flashed the Fire-Nexus rom on it. Very happy with the slick response under Fire-Nexus. I can use Open Camera apk which works fine using the back camera. The only slack is that the front camera for taking selfies does not work. Thus I am tempted to revert to FireOS and trim down the Amazon stuff as a Root user with the help of mtk-su.
Click to expand...
Click to collapse
MTK-SU is a temp root and doesnt allow for system changes. You would be better off flashing magisk for root usage. You can download the latest from amazon flash it, and flash magisk.

drdtyc said:
I have already unlocked my Fire 7 Austin using the shorting method and flashed the Fire-Nexus rom on it. Very happy with the slick response under Fire-Nexus. I can use Open Camera apk which works fine using the back camera. The only slack is that the front camera for taking selfies does not work. Thus I am tempted to revert to FireOS and trim down the Amazon stuff as a Root user with the help of mtk-su.
Click to expand...
Click to collapse
Best of luck finding a version of Fire OS for Austin that is vulnerable to mtk-su.
If you don't want root access permanently on this tablet you could install SuperSU or Magisk, remove whatever Amazon bloat you want and then unroot. Your only other option is to manually rename or delete any unwanted system apps using the TWRP file manager while in recovery mode.