Database Users

[SOLVED] Questions about 6.2.2 update

I am going away, and want to run the Kindle to the latest version (6.2.2) before I go. I do not want to get the OTA update in some hotel and have to fix everything. I have a couple questions...
After installing 6.2.2, and re-root with the commands and BurritoRoot2, and install TWRP, how much more will I need to do? Is the market still there, or does that need to be reinstalled too? How about my Go Launcher and all the apps I already have installed from the market or getjar, or whereever?

Well, That was easy. The OTA update came in, so I had to find my way through this. It was actually very simple, and running BurritoRoot2. I am not rooted, and life is pretty good. Trying to get TWRP to install, but the fastboot command just hangs at waiting for device. The device is rooted, and it shows up in my device manager on my PC. Any help?

Try this thread to fastboot: http://forum.xda-developers.com/showthread.php?t=1414832

from the op of KFU:
Known Tricks
•If you end up stuck at the yellow triangle, in KF Utility select Boot Normal, wait for it to say <waiting for device> and then press and hold the power button 20 seconds until the fire turns off, then when its off turn it back on. This sometimes happens, I have yet to find a clean solution
•If you end up stuck with a yellow triangle, do not EVER unplug it. Leave it plugged in. Check the windows drivers to make sure it isnt showing as "kindle" again. Fastboot is different and can cause this.
Click to expand...
Click to collapse
and:
http://forum.xda-developers.com/showpost.php?p=20945694&postcount=506
switch bootmode to normal manually:
with adb:
adb shell su -c "idme bootmode 4000"
adb reboot
with fastboot:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
fastboot -i 0x18d1 oem idme bootmode 4000
fastboot -i 0x18d1 reboot
or
fastboot oem idme bootmode 4000
fastboot reboot

If, as you indicate, you already have TWRP installed on 6.2.1 you could always flash one of these pre-rooted versions of 6.2.2 and save yourself the effort of re-rooting and all that.
Pre-rooted stock 6.2.2
Update-Only nfx-update-kindle-6.2.2
EDIT: Oh wait... nevermind. I missed the part where you're already attempting to install TWRP.

I'm good. Thanks for all the help. By following the instructions on the link provided I was able to manually install TWRP 2.0. My upgrade is complete, so I can go back to listening and learning here.

Woke up to an unrooted Kindle. Would someone please just clarify.
I only want root and market. No TWRP or CM7. Do I just refollow the original instructions to root.

upriverpaddler said:
Woke up to an unrooted Kindle. Would someone please just clarify.
I only want root and market. No TWRP or CM7. Do I just refollow the original instructions to root.
Click to expand...
Click to collapse
yes - but the updated ones:
http://forum.xda-developers.com/showthread.php?t=1410223
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
horsegoalie said:
I'm good. Thanks for all the help. By following the instructions on the link provided I was able to manually install TWRP 2.0. My upgrade is complete, so I can go back to listening and learning here.
Click to expand...
Click to collapse
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]

I previously used the Kindle Fire Utitlity to root/install market. After my unit was updated to 6.2.2, I used BurritoRoot and verified root using Root Checker.
The 2 things that seem missing still now are contact and calendar sync. Those settings are missing from my google sync settings as well. Do I need to revert to stock and rerun the entire process?

markazali said:
I previously used the Kindle Fire Utitlity to root/install market. After my unit was updated to 6.2.2, I used BurritoRoot and verified root using Root Checker.
The 2 things that seem missing still now are contact and calendar sync. Those settings are missing from my google sync settings as well. Do I need to revert to stock and rerun the entire process?
Click to expand...
Click to collapse
fixed it: reinstalled
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk

markazali said:
fixed it: reinstalled
GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
Click to expand...
Click to collapse
I believe I am in this same boat. Was rooted, and had both of these sync adapters configured and working correctly......and now I received 6.2.2 and no longer have root.
At this point, I am not exactly sure what I need to do to regain root access so I can restore the sync adapters.

ontwowheels said:
I believe I am in this same boat. Was rooted, and had both of these sync adapters configured and working correctly......and now I received 6.2.2 and no longer have root.
At this point, I am not exactly sure what I need to do to regain root access so I can restore the sync adapters.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1410223

b63 said:
http://forum.xda-developers.com/showthread.php?t=1410223
Click to expand...
Click to collapse
I am back in business.....

[Q] Kindle BOOT help stock os gone. fix????

Accidentally erased my stock OS I think. Kindle still rooted and when I turn it on it auto goes to TWRP2.0 after FFF. ADB still working. can I push and flash another ROM or the original stock OS or am I screwed. I did a factory reset instead of going to TWRP like a dork. I can see all the folders and everything from TWRP when I select to flash something.

Mount the sd card from TWRP copy the rom you want then un mount then flash the rom

when you say mount you mean by adb correct --> adb push blah blah rom to kindle unmount then flash using TWRP correct??

You can mount the sd card from within twrp

My kindle won't go into usb mode. when you plug in usb it starts normal with FFF then auto loads TWRP 2.0 how to i load the rom then?

Did you flash a rom already?

I re read your post and you just need to set the boot mode

Use KFU and get your PC to recognize the kindle then set the boot mode to normal

says activating normal (4000) at the top then nothing just the text input blinker???
is there a new KFU am using 9.2
edit after a sec kindle booted on pc to view files --->.> guess u expected that huh. will this work with the stock os software or so i need to put into another folder?

Is KFU recognizing your kindle?
I dont think you erased anything
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
In KFU set the boot mode to normal 4000

it doesn't really do anything and bootmode doesn't change it just sits there saying activating (4000). my pc did recognze my kindle and stock os finally after doing this, but i don't think KFU is.i have stock os which is labled update.zip is in there as well as MIUI. should i try flashing?

you can flash it if you want as long as you have twrp you can pretty much do anything.

sweet thank you for helping bro thought i bricked and screwed up horrible. atl east its just a little funky. next time am going to make sure am not tired or baked next time i try to fix ****. long first day at the college and four hours sleep >.<.

Hello I am having a similar problem as the original poster.
I just got a new kindle and have been playing around with it for a few days. I have had adb working for some time now with updated drivers across the board. Today I decided to apply KFU followed by TWRP. In this process my kindle bricked. This is how it proceeded
1) yellow triangle + TWRP loads but is "empty". KFU fails to recognize kindle.
2) Same as above + PC stopped recognizing kindle only listing it as "Unspecified". (Some hours later after trying various ways to reconnect adb)
3) loss of TWRP --> stuck @ the yellow triangle
Have I totally bricked out? Seems I damaged corrupted the OS or damaged my HD somehow

i asume your in fastboot mode
first fix your drivers by updating the drivers
select manually - the right one for fastboot is "android adb interface" (no composite !)
then
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot

Bricked Kindle Fire

I tried to restore my kindle fire, and apparently it's stuck at the yellow screen which keeps taking me into twrp. All my backups are gone, and I am stuck now. What do I do? I didn't have firefirefire installed on my kindle.
I have searched for the problem on this forum, but can't seem to find one that matches.

Were you running cm7? It sounds like maybe you tried to boot into recovery from whichever Rom you were on. Meaning you held the power down and chose to boot to recovery and your stuck? Anyways we need more info
Sent from my Kindle Fire using xda premium

if you have twrp installed then you have fff - it's in one installation - the yellow triangle is fff
would boot to twrp (adb commands are available)
did the restore work without failures ?
if yes then change boot mode to normal:
"adb shell idme bootmode 4000" and
"adb reboot"

Bricked
I installed miui 4 now bricked. i used twrp recovery to do this and i made a backup . first i did a factory reset then wipe cache and dalvic cache then installed miui 4 the wiped dalvik/cache again, then rebooted and now it is stuck on the yellow triangle screen with the green light on. if i turn off and try to go to recovery the orange light just stays on instead of the green i think i have completely bricked it . also computer will not recognize kindle fire. Any Ideas?
---------- Post added at 08:45 PM ---------- Previous post was at 08:33 PM ----------
i have also tried to leave plugged in use KFU to change boot to normal and recovery, and turned it off then back on and it will recognize it for the split second it takes to tell it to change boot but im still stuck at the same ****
---------- Post added at 09:10 PM ---------- Previous post was at 08:45 PM ----------
ok so i had to use the kindle fire utility but first i had to plug it in turn off, then have kfu install latest twrp again when it says waiting for device turn on and it will reinstall that and get you back to the recovery. always be sure you have a backup and use that and done

this should help someone
I unbricked my kindle. Here is how I did it.this might not work for you.
1.Download kindle fire utility
2.Unzip kindle fire utility
3.To install the driver,its easy,just plug in your kindle, when it pops up with the install wizard say pick from the location of: KindleFireUtility>drivers>kindle 4.run kindle fire utility,select 1 then select 1 again
That's it, hope it helps someone like me

[Unconfirmed] Root (maybe) for 13/14.3.2.1 Need testers

THIS CURRENTLY DOESNT WORK. DONT TRY IT. JUST LEAVE THIS THREAD AND FORGET YOU EVER SAW IT.
Disclaimer: I take no responsibility for bricked devices. I will try to help you fix it if it happens.
But it really shouldn't happen.
This should root x.3.2.1, this isn't my work, this is Gran PC's work for the kindle fire HD 2013 (kfsowi) which runs the same software as the HDX, so this theoretically should work for The HDX's.
Prerequisites: fastboot cable, adb, and a half hour of your time
How to:
•Download the old update file (13/14.4.2.1) sadly, I don't have this, but if I find it, I will post it. I think the 13.3.1.0 is on my home computer, but I can't access it right now.
•Unpack it as a zip archive
•Find the boot.img and copy it into your working/adb directory (or just c:\ on windows)
•open a terminal window
•plug the powered on kindle into the computer with the fastboot cable.
•type: "adb reboot bootloader" without the quotes. Hit enter.
•type "fastboot -i 0x1949 flash boot boot.img" hit enter. Wait
•type "fastboot reboot" hit enter.
This is the tricky part. It will go past the first boot logo, but it *should* load a black screen. Now you cab root it with the old method because what we just did is roll back the kernel to the version that the root exploit will work on.
•once you root it with the old method for 13/14.3.1.0, type "adb shell su" and hit enter. If "#" pops up in your terminal window then you have root.
HOWEVER:
•There is still only a black screen, so now that we have root, we need to roll the kernel forward to the one from 13/14.3.2.1.
•Download the latest update for your device from Amazon's update webpage.
•unpack it like we did before with the old update.
•go to the boot.img we used before from the x.3.1.0 update. Delete it if it is in your adb/working directory. (or just c:\ on windows)
•copy the new boot-prod.img to your adb/working directory (or just c:\ on windows)
•type "adb reboot bootloader" hit enter.
•type "fastboot -i 0x1949 flash boot boot.img (again, be extra sure that this is the new one) hit enter
•type "fastboot reboot"
•the kindle *should* boot up as normal and be rooted. If it isn't, tell me, and I'll try to help you.
•Optional but recommended: install SuperSU, and update binaries.
Edit: I apologize for the boot-prod.img mix up. It is just boot.img it is apparently different for the HDX than the HD.

Reserved
Sent from my Galaxy Nexus using Tapatalk

What is the old update file version number? I found one from
s3.amazonaws.com[slash]kindle-fire-updates[slash]update-kindle-13.3.1.0_user_310079820.bin
Is that the right one for Fire HDX 7?
Or if possible, please upload the boot-prod.img somewhere so we can download.

Mineturtle33 said:
Disclaimer: I take no responsibility for bricked devices. I will try to help you fix it if it happens.
But it really shouldn't happen.
This should root x.3.2.1, this isn't my work, this is Gram_PC's work for the kindle fire HD 2013 (kfsowi) which runs the same software as the HDX, so this theoretically should work for The HDX's.
Prerequisites: fastboot cable, adb, and a half hour of your time
How to:
•Download the old update file (13/14.4.2.1) sadly, I don't have this, but if I find it, I will post it. I think the 13.3.1.0 is on my home computer, but I can't access it right now.
•Unpack it as a zip archive
•Find the boot-prod.img and copy it into your working/adb directory (or just c:\ on windows)
•open a terminal window
•plug the powered on kindle into the computer with the fastboot cable.
•type: "adb reboot bootloader" without the quotes. Hit enter.
•type "fastboot -i 0x1949 flash boot boot-prod.img" hit enter. Wait
•type "fastboot reboot" hit enter.
This is the tricky part. It will go past the first boot logo, but it *should* load a black screen. Now you cab root it with the old method because what we just did is roll back the kernel to the version that the root exploit will work on.
•once you root it with the old method for 13/14.3.1.0, type "adb shell su" and hit enter. If "#" pops up in your terminal window then you have root.
HOWEVER:
•There is still only a black screen, so now that we have root, we need to roll the kernel forward to the one from 13/14.3.2.1.
•Download the latest update for your device from Amazon's update webpage.
•unpack it like we did before with the old update.
•go to the boot-prod.img we used before from the x.3.1.0 update. Delete it if it is in your adb/working directory. (or just c:\ on windows)
•copy the new boot-prod.img to your adb/working directory (or just c:\ on windows)
•type "adb reboot bootloader" hit enter.
•type "fastboot -i 0x1949 flash boot boot-prod.img (again, be extra sure that this is the new one) hit enter
•type "fastboot reboot"
•the kindle *should* boot up as normal and be rooted. If it isn't, tell me, and I'll try to help you.
•Optional but recommended: install SuperSU, and update binaries.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I have the files needed but I can't find that boot-prod.img file, I have a boot.img and prod_cert_swap.sed in there on the 13.3.1.0 on the new one

mech_supernova said:
I have the files needed but I can't find that boot-prod.img file, I have a boot.img and prod_cert_swap.sed in there on the 13.3.1.0 on the new one
Click to expand...
Click to collapse
The Fire HD's update-kindle-11.3.1.0_user_310084920.bin contains boot-prod.img but the HDX's doesn't. (Also inside their 11.3.2.1 new update files, but not HDX's 13.3.2.1)
1. Not sure using HD's boot-prod.img would work or brick the HDX?
2. Or using HDX's boot.img directly would work?
Someone with better unbricking experience than mine should try it out.

I will attempt this, If someone can get me the link to download the previous update...

plasticarmyman said:
I will attempt this, If someone can get me the link to download the previous update...
Click to expand...
Click to collapse
Fire Kindle HDX's old update (contains only boot.img, no boot-prod.img):
s3.amazonaws.com[slash]kindle-fire-updates[slash]update-kindle-13.3.1.0_user_310079820.bin
Fire Kindle HD's old update (contains both boot.img and boot-prod.img):
s3.amazonaws.com[slash]kindle-fire-updates[slash]update-kindle-11.3.1.0_user_310084920.bin

the link for the 8.9" is https://s3.amazonaws.com/kindle-fire-updates/update-kindle-14.3.1.0_user_310079820.bin
i'm downloading it right now
EDIT: Downloaded and extracted....i have a boot.img should i try and flash that? @Mineturtle33

Mineturtle33 said:
Disclaimer: I take no responsibility for bricked devices. I will try to help you fix it if it happens.
But it really shouldn't happen.
This should root x.3.2.1, this isn't my work, this is Gram_PC's work for the kindle fire HD 2013 (kfsowi) which runs the same software as the HDX, so this theoretically should work for The HDX's.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Have you checked boot_prod against dkernel boot image in the HDX? IDK for certain, but I thought the 2013 HD was more akin to the HD 8.9 in terms of hardware, with the OMAP platform & the uboot based bootloader, (both of which are much easier to work with as there is a lot more documentation & reference). Aside from that, AFAIK, you cannot flash anything (signed or unsigned) via fastboot on the HDX, at least not with a locked bootloader. At any ratee, I am certain you can flash the older firmware using update, but you must alter the older version to reflect a newer version AND retain the signature. I have had limited success with this though, as it seeks some of the changes in the latest update alter the misc partition & make some changes in the trusted zone. These changes mean that even rolling back will cause some issues that can be a real pain. Location awareness is one. Connectivity is another. The you also have issue of audio not restoring locally whenever a headset or BT device is used. The same also hppens with video when switching back & forth from the device to a wireless display device.
EDIT: Yep. The new HD is indeed OMAP + uboot. This isn't going to work. Again, I am nearly 100% you cannot flash via fastboot period. If you could though, you may have a similar route via the initial boot.img, aka dkernel.img, but at that point, theere'd be no need anyway, since you'd have the keys or the required access via an unlocked bootloader.

GSLEON3 said:
Have you checked boot_prod against dkernel boot image in the HDX? IDK for certain, but I thought the 2013 HD was more akin to the HD 8.9 in terms of hardware, with the OMAP platform & the uboot based bootloader, (both of which are much easier to work with as there is a lot more documentation & reference). Aside from that, AFAIK, you cannot flash anything (signed or unsigned) via fastboot on the HDX, at least not with a locked bootloader. At any ratee, I am certain you can flash the older firmware using update, but you must alter the older version to reflect a newer version AND retain the signature. I have had limited success with this though, as it seeks some of the changes in the latest update alter the misc partition & make some changes in the trusted zone. These changes mean that even rolling back will cause some issues that can be a real pain. Location awareness is one. Connectivity is another. The you also have issue of audio not restoring locally whenever a headset or BT device is used. The same also hppens with video when switching back & forth from the device to a wireless display device.
EDIT: Yep. The new HD is indeed OMAP + uboot. This isn't going to work. Again, I am nearly 100% you cannot flash via fastboot period. If you could though, you may have a similar route via the initial boot.img, aka dkernel.img, but at that point, theere'd be no need anyway, since you'd have the keys or the required access via an unlocked bootloader.
Click to expand...
Click to collapse
At least on the HD you can flash anything with fastboot -- but if it is unsigned, it will fail to boot up (or sometimes actually just refuse to flash it). If it's properly signed, it should boot up.
I don't have an HDX to test with, but it seems to me like flashing the boot.img from an old update *may* work -- while you might not see anything on screen/some hardware may not work, you should be able to connect through adb and use the same old exploit -- and then revert to the newer kernel to get everything functional again. Again, I have not tested this so I cannot confirm it works, and I am assuming that fastboot would work. It is possible that it does not work as GSLEON3 described.
Similarly, you may have some success making a stripped down system.img that contains a su binary and flashing it, like I have done on the HD (again, no clue whether this will work on the HDX or not)

Gran PC said:
At least on the HD you can flash anything with fastboot -- but if it is unsigned, it will fail to boot up (or sometimes actually just refuse to flash it). If it's properly signed, it should boot up.
I don't have an HDX to test with, but it seems to me like flashing the boot.img from an old update *may* work -- while you might not see anything on screen/some hardware may not work, you should be able to connect through adb and use the same old exploit -- and then revert to the newer kernel to get everything functional again. Again, I have not tested this so I cannot confirm it works, and I am assuming that fastboot would work. It is possible that it does not work as GSLEON3 described.
Similarly, you may have some success making a stripped down system.img that contains a su binary and flashing it, like I have done on the HD (again, no clue whether this will work on the HDX or not)
Click to expand...
Click to collapse
So this won't work?
Sent from my Galaxy Nexus using Tapatalk

Mineturtle33 said:
So this won't work?
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
It *may* work if you use boot.img and not boot-prod.img (which doesnt exist), but it's probably not going to work.

I'll update the op.
Sent from my 2013 Kindle Fire HD

This thing is quickly reminding me of the lgF6 and L9 phones.
Sent from my SGH-T999 using Tapatalk

I tried to flash boot.img from the 14.3.1.0 bin file (Fire HDX 8.9) and unfortunately it didn't work. Attached is a screen capture of the command line output.

Here is the BIN file straight from amazon website couple of months ago, the 13.3.1 "update".
https://www.dropbox.com/s/98f9yxbmekwtxi2/update-kindle-13.3.1.0_user_310079820.bin
Also, I entered fastboot mode, but without a factory reset cable, my kindle displays KINDLE [fastboot]
and READY
but as soon as I attempt to flash boot.img file it says waiting for device...
Should I try with fastboot cable?
With it all that happens is the screen goes black, but I can hear it working, and it does indeed run out of battery.This is from previous experience of trying to unbrick it.

ferrouskid, it might be that you don't have your drivers set up correctly. When in fastboot your kindle should show up in device manager on windows as an Android Boot loader interface device.
I didn't use a factory cable, just a cable I have spare. I got a response from fastboot mode but flashing boot.img failed because the hardware/bootloader is locked down. See the attached screen capture on post #15.
Sent from my KFAPWI using XDA Premium 4 mobile app
---------- Post added at 09:06 PM ---------- Previous post was at 08:59 PM ----------
I should add please look past the first 6 lines of the screen capture on post #15. I typed the command in wrong the first time.
Sent from my KFAPWI using XDA Premium 4 mobile app

ggow said:
ferrouskid, it might be that you don't have your drivers set up correctly. When in fastboot your kindle should show up in device manager on windows as an Android Boot loader interface device.
I didn't use a factory cable, just a cable I have spare. I got a response from fastboot mode but flashing boot.img failed because the hardware/bootloader is locked down. See the attached screen capture on post #15.
Sent from my KFAPWI using XDA Premium 4 mobile app
---------- Post added at 09:06 PM ---------- Previous post was at 08:59 PM ----------
I should add please look past the first 6 lines of the screen capture on post #15. I typed the command in wrong the first time.
Sent from my KFAPWI using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You're the first person I've seen who has gotten their computer to recognize the HDX in fastboot. I have tried multiple times and also always get waiting for device no matter what I do.

I forgot fast boot can't flash images >900 mb. Hmmm.

Mineturtle33 said:
I forgot fast boot can't flash images >900 mb. Hmmm.
Click to expand...
Click to collapse
It probably won't let you flash any image at all anyways. Else I could just make a reduced system image (the one I made for the HD 7 is 69 MB) that would give you root access.

[2017] Root Kindle Fire HD 6 4th gen tutorial

Hi,
This is my first post here but I have gotten so much help I wanted to give back. I have been working on rooting my Kindle fire HD 6 over the last couple days and after searching multiple tutorials I have successfully rooted with these steps.
To begin:
1. You MUST backup any data on your device before starting this process
2. Download all the files from here and Fire OS 5.4.0.0 here
3. Get your downgrade here
3. Follow the instructions below (modified from user @marathonjon reply here https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950/page54)
Here we go for the install:
1. Enable ADB on your device and set up ADB on your computer
2. Download 4.5.3 firmware (you should already have it from the download above)
3. Connect device to computer and run "adb reboot recovery" (assuming you have adb enabled on your tablet)
4. Use volume keys and power button to navigate to "Apply update from ADB"
5. From computer type "adb sideload update-kindle-20.4.5.3_user_453011120.bin" (the files need to be added to the same folder your terminal is currently running or you can specify the file path)
6. From tablet select "wipe data/factory reset" (this is why we did the backup earlier)
7. From tablet select "reboot system"
8. Complete setup (do not connect to a wifi network yet, this is very important!)
9. Disable OTA updates ( adb shell ; pm block com.amazon.dcp or "Debloater"), I used the above jmz Kindle fire tools to disable the OTA, just sideload it and you are good to go.
10. Sideload Kingroot & let it root (this can take a while, just let it go)
11. Flash openrecovery-twrp-2.8.6.0-ariel.img TWRP image via Flashify (backup stock recovery first, again very important!!) (you will need to sideload the included Flashify APK)
12. Download all files above and place them in the Download directory of your kindle
13. Boot into TWRP, flash 4.5.3_twrp_recovery_full_ariel_string.zip. (use adb reboot recovery for this)
14. Do factory reset using the default TWRP wipe settings
15. Flash FireOS 5.4.0.0 (rename *bin to *zip so that TWRP can recognize it)
16. Flash 5.5.2_1534_stock_recovery_uboot.zip, this will put the required 5.3.1 bootloader back(PLEASE MAKE SURE TO DO THIS STEP!!)
17. DO NOT REBOOT YET! If you do you will probably lose root!
18. Flash Supersu.zip (included in the download
19. Clear cache/dalvik in TWRP
20. Reboot to recovery: adb reboot recovery. This will be stock recovery now because TWRP doesn’t boot with 5.x bootloaders.
21. Reboot to FireOS (could take ~15 minutes, it might seem like it is stuck in a boot loop but it will go)
The above instructions served me well, as with all posts on this site PLEASE USE AT YOUR OWN RISK! And post any questions below

I just followed your tutorial and it worked for me... Amazon has FireOS 5.4.0.1 for the update file now and it still worked following your steps. Thank you!

Could I keep root without updating to 5.4?
---------- Post added at 06:42 AM ---------- Previous post was at 06:26 AM ----------
Also Kingroot fails. Was the exploit is uses patched?

Bricked Device(unbricked it with DoLooper tutorial) improvising,Step 9 says sideload JMZ Tools how do you do that without connection? only way i can think is es explorer which you have to have connection to install

Any news on this? Thinking of attempting

I attempted this to downgrade from rooted 5.12 to 4.53 so that I could install twrp and get to the latest load.
I am stuck on step 8. After I flashed 4.5.3 and wiped, I attempted to sideload kingroot and the jmz utility but they did not install. I imagined that it failed because they are from unknown sources and that setting is disabled once 4.5.3 is loaded. So I rebooted with wifi off, attempted to adb reboot recovery, and I got to a recovery menu with 2 options, none of which are adb sideload.
How can I proceed? If I enable wifi to download kingroot, it will attempt to update, correct?
EDIT - I enabled wifi to download kingroot apk since I can't sideload it, and surely enough an update to 4.5.5 downloaded. Damn.
RE-EDIT--I just caught my initial mistake. I used the command adb sideload for kingroot and jmz instead of adb install. Another damn. I am downloading kingroot and rooting while the update to 4.5.5 awaits installation, which I won't do.

It boot me into kids edition...?

jcarcinogen said:
I just followed your tutorial and it worked for me... Amazon has FireOS 5.4.0.1 for the update file now and it still worked following your steps. Thank you!
Click to expand...
Click to collapse
Glad to hear! I have had a blast with a rooted kindle, including installing google and using root required apps.

demoncamber said:
Any news on this? Thinking of attempting
Click to expand...
Click to collapse
It worked great for me, considering that that the tablet cost me $60 brand new I took the risk. It is up to you whether this is something that you want.

I have a kindle fire hd 7 4th gen, running 5.6.0.1. Will this work for me?

Will this work for my hd 7 4th gen running fire os 5.6.0.1?
@marathonjon
@RobbotCC
@jcarcinogen
Please I really want to get root to install a android rom or cyanagen mod.

RobbotCC said:
Hi,
This is my first post here but I have gotten so much help I wanted to give back. I have been working on rooting my Kindle fire HD 6 over the last couple days and after searching multiple tutorials I have successfully rooted with these steps.
To begin:
1. You MUST backup any data on your device before starting this process
2. Download all the files from here and Fire OS 5.4.0.0 here
3. Get your downgrade here
3. Follow the instructions below (modified from user @marathonjon reply here https://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950/page54)
Here we go for the install:
1. Enable ADB on your device and set up ADB on your computer
2. Download 4.5.3 firmware (you should already have it from the download above)
3. Connect device to computer and run "adb reboot recovery" (assuming you have adb enabled on your tablet)
4. Use volume keys and power button to navigate to "Apply update from ADB"
5. From computer type "adb sideload update-kindle-20.4.5.3_user_453011120.bin" (the files need to be added to the same folder your terminal is currently running or you can specify the file path)
6. From tablet select "wipe data/factory reset" (this is why we did the backup earlier)
7. From tablet select "reboot system"
8. Complete setup (do not connect to a wifi network yet, this is very important!)
9. Disable OTA updates ( adb shell ; pm block com.amazon.dcp or "Debloater"), I used the above jmz Kindle fire tools to disable the OTA, just sideload it and you are good to go.
10. Sideload Kingroot & let it root (this can take a while, just let it go)
11. Flash openrecovery-twrp-2.8.6.0-ariel.img TWRP image via Flashify (backup stock recovery first, again very important!!) (you will need to sideload the included Flashify APK)
12. Download all files above and place them in the Download directory of your kindle
13. Boot into TWRP, flash 4.5.3_twrp_recovery_full_ariel_string.zip. (use adb reboot recovery for this)
14. Do factory reset using the default TWRP wipe settings
15. Flash FireOS 5.4.0.0 (rename *bin to *zip so that TWRP can recognize it)
16. Flash 5.5.2_1534_stock_recovery_uboot.zip, this will put the required 5.3.1 bootloader back(PLEASE MAKE SURE TO DO THIS STEP!!)
17. DO NOT REBOOT YET! If you do you will probably lose root!
18. Flash Supersu.zip (included in the download
19. Clear cache/dalvik in TWRP
20. Reboot to recovery: adb reboot recovery. This will be stock recovery now because TWRP doesn’t boot with 5.x bootloaders.
21. Reboot to FireOS (could take ~15 minutes, it might seem like it is stuck in a boot loop but it will go)
The above instructions served me well, as with all posts on this site PLEASE USE AT YOUR OWN RISK! And post any questions below
Click to expand...
Click to collapse
Does this work on the Fire OS 5.6.0.1 that was sent out this year?

Provided said:
I have a kindle fire hd 7 4th gen, running 5.6.0.1. Will this work for me?
Click to expand...
Click to collapse
IDK, it has been awhile since I ran this and I have not stayed up to date on the latest firmware. As always you can try it at your own risk and post any questions here. I will do my best to answer.
I do not recommend trying this if you rely on the tablet for anything, things can go wrong and you could lose everything including the tablet.
Have Fun!

On step 15, does it have to be 5.4.0.0? I'm having trouble finding a download for it since the link in OP leads to 5.6.0.1
edit: found a link (https://forum.xda-developers.com/hd8-hd10/general/fire-hd-8-2017-downgrade-to-5-4-0-0-5-6-t3719639) but it's for FIre HD 8. Will that work or does it need to be specifically for the HD 6?
edit2: nevermind, didn't look hard enough, found it here https://forum.xda-developers.com/fire-hd/general/fire-hd-rom-links-t3173102

liebherk said:
On step 15, does it have to be 5.4.0.0? I'm having trouble finding a download for it since the link in OP leads to 5.6.0.1
Click to expand...
Click to collapse
Yes, that is the latest version that is still root-able I believe.

Still works with update 5.6.1.0
Still works thanks alot!

Yup, worked for me as well. Thanks @RobbotCC from another CMH kindle newbie

Stuck on step #13
My KF HD 6 gen 4 shows it is running OS 4.5.3. I can boot into TWRP. ADB sees my device. I need to add ".\adb" before ADB commands.
The problem I'm having is that I cannot flash the TWRP 4.5.3 recovery. When I have the TWRP launcher showing and type " .\adb reboot recovery" the system reboots right into the TWRP launcher. When I power off then on, it boots right into the Fire OS. I never see the system recovery screen, so I can't flash the recovery zip file.
Help? Any ideas would be greatly appreciated.
Thanks.

LeoDaQ said:
My KF HD 6 gen 4 shows it is running OS 4.5.3. I can boot into TWRP. ADB sees my device. I need to add ".\adb" before ADB commands.
The problem I'm having is that I cannot flash the TWRP 4.5.3 recovery. When I have the TWRP launcher showing and type " .\adb reboot recovery" the system reboots right into the TWRP launcher. When I power off then on, it boots right into the Fire OS. I never see the system recovery screen, so I can't flash the recovery zip file.
Help? Any ideas would be greatly appreciated.
Thanks.
Click to expand...
Click to collapse
Flash the recovery file using twrp?
The whole process worked for me on my kf hd 7 Ariel now I have rooted 5.6.1.0.

Provided said:
Flash the recovery file using twrp?
The whole process worked for me on my kf hd 7 Ariel now I have rooted 5.6.1.0.
Click to expand...
Click to collapse
did you use the same files in the first thread? for hd 7 ? or should we download specific downgrade file?