yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] phpbb88:
FOR 2016(6th GEN) ON 5.3.1 AND 5.3.1.1 ONLY: Works on HD7, HD8 and HD10

You can downgrade from 5.3.2 by adb sideload the 5.3.1.1 bin file.

DO NOT downgrade from 5.3.2.1!! Hard-brick attention!!

This guide requires some ADB skills, read more from the forum, install it from here

Enable ADB and install apps from other sources in Developer Options

Download Kingoroot PC version at www.kingoapp.com or google mirror

Root your Kindle using Kingoroot, then reboot your device

Download a file explorer apk (ie. ES File Explorer) and sideload install the apk to your kindle

Download SuperSU apk at APKPure, but DON'T install it first

Download the attachment "Kingo.to.SuperSU" below then unzip and paste into your kindle, ie /sdcard/Kingo.to.SuperSU

Run ADB Shell and type

su
mount -w -o remount /system

Keep the root-accessed ADB shell open, then remove root by using Kingoroot

(If your kindle reboot at this step, you need to re-root it and try the above steps again)

In the ADB shell type

cd /sdcard/Kingo.to.SuperSU
cp ./su /system/xbin/daemonsu
chmod 0755 /system/xbin/daemonsu
daemonsu -d &

Still keep that root-accessed ADB shell opened, copy the SuperSU apk into your kindle and install it using the file explorer, DO NOT OPEN IT.

In the ADB shell type

cp ./su /system/xbin/su
chmod 0755 /system/xbin/su
rm /system/xbin/supolicy
rm /system/bin/install-recovery.sh
rm -rf /system/usr/iku
rm -rf /sdcard/Kingroot

(1 error with "No such file or directory" is okay I think)

Run SuperSU and update binary, choose the "normal" one, then it should ask you to reboot your kindle

Open up SuperSU and go to setting

Set the "Default Access" as [Grant]

Due to unknown reason, kindle cannot prompt the "Asking for root access", this step is to allow all access for all apps.

Install Root Checker and confirm you have root, run ADB shell to confirm you can su

Remove Kingolink and that Kingo battery app from kindle

Uninstall Kingo from PC via manual unins000.exe inside install directory in programs(x86)

ALL DONE! You may then want to install google play, do all the pm disable for OTA, firelauncher, and other amazon services you don't want.

References:

[Index] Amazon Fire HD 8 and HD 10 (5th Gen/2015)

[Working]Root Kindle Fire HD8 6th Gen

Tips, Tricks, and the Root!

[HOW-TO] Install Google Play Store (Fire OS 5.3.1.1) (No Root/ADB)

[Script] Replace KingoRoot with SuperSU

Credits:

@coltxL2717

@chemie99

@2ig2ag

@smokejumper76

@phpbb88 ME:cool:
[Fire HD 8 and HD 10 General] imadiamond:
Getting error at Step 11:

After entering

rm /system/bin/install-recovery.sh

getting

No such file or directory

Then when updating binaries, SuperSU says "Installation successful! Reboot your device." On reboot, says that binaries are not installed and the app closes itself. Also, when initially updating SuperSU binaries, which option is to be chosen? The first "Normal" or the second "Custom/TWRP."

Here is my full log:

shell@giza:/ $ su

root@giza:/ # mount -w -o remount /system

root@giza:/ # cd /sdcard/Kingo.to.SuperSU

root@giza:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu

root@giza:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu

root@giza:/sdcard/Kingo.to.SuperSU # daemonsu -d &

[1] 5542

root@giza:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su

[1] + Done daemonsu -d

root@giza:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su

root@giza:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy

root@giza:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh

rm: /system/bin/install-recovery.sh: No such file or directory

1|root@giza:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku

root@giza:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot

root@giza:/sdcard/Kingo.to.SuperSU # reboot
[Fire HD 8 and HD 10 General] phpbb88:
in step 10, install SuperSU but do not open it.

your log should have no problem, maybe try again from clean state? (clean 5.3.1./5.3.1.1 state)

PS. you should choose "normal" when update binary
[Fire HD 8 and HD 10 General] citrusfizz:
Thanks for making this clear and concise guide! Well done.
[Fire HD 8 and HD 10 General] imadiamond:
Did cache wipe/format and reset to factory settings via device recovery (powering on and holding volume button.)

Went through the process again, and THOUGHT it worked, even though I got the same "No such file or directory" error. I didn't reboot on Step 12 and went into SuperSU setings to "Grant." Got Root Checker. Had root. Rebooted and opened Root Checker and had no root. So--

1) still getting same "No such file" error: how can I reset the device "clean" without that new .bin? Isn't there a way to "clean" the OS already on the device? On 5.3.1.1 On device did "wipe data/factory reset" then "wipe cache partition" and have also done them in the opposite order to make sure.

2) On step 12 do you reboot the device like SuperSu says, or do you just go straight into the settings. I was rebooting the device at this point for 3 or 4 tries. The last two times I did not and went straight into settings. Still same error of "No such file or directory." The file IS in the Kingo.to.SuperSU folder though, even downloaded and unzipped the attachment a few times.
[Fire HD 8 and HD 10 General] meikschlenther:
Could I also install a customrom after root? with one?
[Fire HD 8 and HD 10 General] JAS_21:
Not at this time... There are no ROMs as of yet, and if I'm not mistaken we would need a custom recovery and our bootloader is still locked.
[Fire HD 8 and HD 10 General] phpbb88:
Please download the official 5.3.1.1 bin, wipe cache, factory reset, then sideload the bin through recovery mode and follow the guide step by step strictly.;)

edited: please have a look at here, I somehow worked with 1 error, which is likely the "rm /system/bin/install-recovery.sh" command.
[Fire HD 8 and HD 10 General] imadiamond:
First problem was even though previously all drivers loaded and I was able to root/re-root and navigate adb.... when booting the device into recovery mode? Tablet not recognized by computer. Extremely frustrating. Read and read and read.... and finally came across something from @smokejumper76 -----answer was in Device Manager, tablet was showing up as KFGIWI with the error that drivers were not installed. Did "manually install drivers" "Search online" does not work) and chose ADB Composite Device, and now tablet is recognized in recovery mode.

Issue NOW is the process gets halfway through installation and then force closes with

E: failed to verify whole-file signature

E: signature verification failed

Man, I am ticked. What now? Been reading for the past hour++. People elsewhere are saying to change the .bin extension to .zip, but I haven't seen that here on the XDA forum.

---------- Post added at 01:48 AM ---------- Previous post was at 01:11 AM ----------

Install from ADB complete: went through. After multiple tries, did 2 things at once so not sure which one it was

1) ran cmd prompt as Administrator

2) deleted all 5.3.1.1 bin files from computer, just in case what was gotten previously was corrupt, and redownloaded fresh file onto the ADB computer, instead of the copy and paste version from another computer
[Fire HD 8 and HD 10 General] el7145:
Thanks for making this guide! Worked perfect 1st time on my hd8 2016. Used rootjunky supertool to disable ota, install nova, disable ads Lockscreen, install Google play.

Just a thought, in the guide, you state, you could get es file Explorer from Amazon appstore, which would imply you have wifi on...which could get you updated to 5.3.2.1 without you knowing? Should prolly stick to sideloading ES only until ota is disabled.

Thanks again

From the time I turned the hd8 on for 1st time, I kept wifi off until I was rooted and able to disable ota.
[Fire HD 8 and HD 10 General] ¿GotJazz?:
I hope all you guys are also donating some bux to Kingoroot (I did).

We want to keep those geniuses happy and cranking out rooting updates for the v5.3.2.x builds!
[Fire HD 8 and HD 10 General] lr1100:
Thanks so much for the guide. It was pretty easy to get through!

I have Nova Launcher running now and it is way better.

However, Auto Rotate screen isn't working quite right. If it is in Portrait, it will flip to landscape if I turn the tablet, but then it gets stuck in landscape which is the wrong landscape that I need for my Fire cover/stand.

Anyone else experiencing this?
[Fire HD 8 and HD 10 General] imadiamond:
Dumbest question:

the root is supposed to stay after turning the tablet off and on again, right?

I say this because went through the whole process successfully. New .bin. No errors on any commands. SuperSU installed binaries and then downloaded Root Checker and verified. Then verified su in adb shell. Then did pm disable of amazon apps and services,

and then turned tablet off and back on and Root Checker says NO ROOT. Root is supposed to stay, correct??? Or is it to just get all of the Amazon items off and customize tablet. Have rooted at least 8 or 9 devices, LG, Samsung, HTC etc, and this one has been the absolute _____ .
[Fire HD 8 and HD 10 General] phpbb88:
Thanks for pointing out the mistake, cause I had disable ota update by OpenDNS method before, so I was not aware of this.
[Fire HD 8 and HD 10 General] phpbb88:
did you change the default access in SuperSU from prompt to grant? or have you disabled the OTA service?

in normal case, root will not lose till the OS updated.
[Fire HD 8 and HD 10 General] imadiamond:
Need to type exit, exit in shell to save settings?

Good question. Thanks for asking phpbb88! Definitely changed the default access. Rebooting here was one of the problems earlier since SuperSU says to reboot, then you must hit "Ok"-- and then logically, you would reboot. But instructions don't say to *ignore* and stay in SuperSU. Previously was rebooting, since Step 13 says "Open up SuperSU"... but SuperSU is already open in Step 12, so no need to open it up.

Only connected to the internet with it once, in December. Saw that everything needed an Amazon account, so have had wireless off/airplane mode ever since. Bought it with sole purpose to root.

The only thing I can think of would be not typing "exit" twice to get out of the shell. First read that instruction at the end of the pm disabling tutorial. If that's important than it needs to be added to the instructions also. Otherwise, when finished people will just power down the device or pull the USB plug. It's got to be written so that someone not knowing anything- first-time Kindle buyer like me :confused:, can do it. Here is the log.

shell@giza:/ $ su

root@giza:/ # mount -w -o remount /system

root@giza:/ # cd /sdcard/Kingo.to.SuperSU

root@giza:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/daemonsu

root@giza:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/daemonsu

root@giza:/sdcard/Kingo.to.SuperSU # daemonsu -d &

[1] 7590

root@giza:/sdcard/Kingo.to.SuperSU # cp ./su /system/xbin/su

[1] + Done daemonsu -d

root@giza:/sdcard/Kingo.to.SuperSU # chmod 0755 /system/xbin/su

root@giza:/sdcard/Kingo.to.SuperSU # rm /system/xbin/supolicy

root@giza:/sdcard/Kingo.to.SuperSU # rm /system/bin/install-recovery.sh

root@giza:/sdcard/Kingo.to.SuperSU # rm -rf /system/usr/iku

root@giza:/sdcard/Kingo.to.SuperSU # rm -rf /sdcard/Kingroot

root@giza:/sdcard/Kingo.to.SuperSU #

C:\Users\COMPUTER\AppData\Local\Android\Sdk\platform-tools>
[Fire HD 8 and HD 10 General] imadiamond:
ROOOOOOOOOOOOOOOOOTEEEDDDDDDDDDDDDDDD.

Final piece of puzzle I think it was the SuperSU I had. Didn't do any other changes. Got it from appsapk.com . FOLKS, do not use any SuperSU you get from there (or anywhere else) at least for this process. You'll end up chasing squirrels. It *might* have gone through even with the other errors etc (like phpbb88 mentioned it did for him), but the wrong SuperSU probably killed everything in the end. Go to https://apkdot.com/apk/chainfire/sup...ersu-2-79-sr3/ and get your SuperSU there: thank you for the suggestion smokejumper76. For one, immediately noticed the app logo was different. Also took longer to load the binaries. Whatever the other SuperSU apk is I'm deleting it now: don't even want to know the version.

phpbb88, I see you added the answer to my question about which option to pick in SuperSU (Normal) to the instructions. Thanks! Would also suggest 1) to add a note NOT to reboot even though SuperSU asks to, since in the next line you say "Open SuperSU" but it's already open and 2) the link for the proper SuperSU in the credits at the end, or the file even.

This was Christmas gift for my gf... now she can use it. Was planning on getting a HD10 for myself, but it's been so long that unfortunately now it might ship with newer software. Might buy one from a retail store as they will have older stock, and the return will be a quick walk-in if it's got 5.3.+.+ .
[Fire HD 8 and HD 10 General] phpbb88:
Glad to hear that you can finally root your fire.

In fact, I never typed exit twice in adb shell, I just close it...lol

1) After SuperSU updates its binary, I followed the reboot, still success to root my device.

2) I am using the SuperSU apk download from apkpure linked above, why don't you download it in the first try...?

I went to appsapk.com and have a look of the SuperSU, it is totally a different app.
[Fire HD 8 and HD 10 General] asherm2:
Thanks for the Guide finally got root!
[Fire HD 8 and HD 10 General] asherm2:
I had the exact same problem over and over finally tried this:

change this: rm /system/bin/install-recovery.sh

To this: rm install-recovery.sh :p
[Fire HD 8 and HD 10 General] phpbb88:
rm install-recovery.sh

typing this command is pointless...

you are just deleting a file which you previously copied to your kindle. ROFL
[Fire HD 8 and HD 10 General] asherm2:
roflmao well it worked bro

i have root failed until i did that guess i'm just dumb lucky
[Fire HD 8 and HD 10 General] ramencup:
got through step 3, rebooted, now stuck in a boot loop. first time i've had a device do this -- any suggestions?
[Fire HD 8 and HD 10 General] phpbb88:
at least its not a hard brick

sideload the 5.3.1.1 bin to have a fresh start
[Fire HD 8 and HD 10 General] ramencup:
Thanks, had actually just finished this. I'm good to go now.
[Fire HD 8 and HD 10 General] Novalis31:
Can't wait to be able to root 5.3.2.1. So sick of this os.
[Fire HD 8 and HD 10 General] Quick-Study:
5.3.1.1 | Successful root

Thanks to all for figuring this out!

If anyone gets stuck at step 9 and has an issue with ADB not finding the folder check the path to your SD card by using ES File Explorer.

I had to change "cd /sdcard/Kingo.to.SuperSU" to "cd /storage/sdcard1/Kingo.to.SuperSU" and "rm -rf /sdcard/Kingroot" to "rm -rf /storage/sdcard1/Kingroot".

I have verified root but have yet to connect the device to the internet. Do Amazon updates need to be disabled?
[Fire HD 8 and HD 10 General] vandyman:
https://xdaforums.com/hd8-hd10/development/tips-tricks-root-t3310569
[Fire HD 8 and HD 10 General] critofur:
Tech support offered to send me a replacement tablet with 5.3.1.1 OS on it because I complained about the 5.3.2 update. I told them I didn't want the tablet if I couldn't root it and it was ridiculous that they would try to prevent a customer from rooting their OWN tablet, should be illegal.

So, should I get the replacement? If I follow these steps su works and remains working after a reboot?
[Fire HD 8 and HD 10 General] ¿GotJazz?:
Amazon can't guarantee that they will be sending you a v5.3.1.x HD8-6G. They will send you whatever they have in stock, and it could come with a more recent build if Amazon now is building tablets with v5.3.2.x.

The sooner you request and get your replacement, the better.
[Fire HD 8 and HD 10 General] critofur:
My customer service agent said that he could specify to send 5.3.1.x and would request that the developers address my concern about not being able to unlock the boot loader. He also said that he completely agreed that the customer should have full control over their own device [root access] after I explained that I wanted to setup Greenify to prevent my kids games from running in the background and popping up annoying notifications, and that I wanted finer control over app permissions. He also suggested that since I was using the google play store to run a game not available through Amazon that it would be more convenient for me to use a different Android device which came with the Google Play store and just get a refund for my Fire HD.
[Fire HD 8 and HD 10 General] greenrosed:
Bizarro world

Just a thought, in the guide, you state, you could get es file Explorer from Amazon appstore, which would imply you have wifi on...which could get you updated to 5.3.2.1 without you knowing? Should prolly stick to sideloading ES only until ota is disabled.

Thanks again

From the time I turned the hd8 on for 1st time, I kept wifi off until I was rooted and able to disable ota.[/QUOTE]

You were correct to implement this strategy, I did the opposite and failed.
[Fire HD 8 and HD 10 General] domino6789:
My fire hd 8 Hard Brick

Hi everyone, before read this post I have tried downgrade OS ver 5.3.2.1 to ver 5.3.1.1 and my device hard-brick.:crying:

please help me. if any someone have the ways fix it.

Thanks all,
[Fire HD 8 and HD 10 General] vandyman:
Can you use ADB?
[Fire HD 8 and HD 10 General] domino6789:
yes. I can. but adb can't connect with device.

Thanks you.
[Fire HD 8 and HD 10 General] Vysarat:
Does anyone know if this method will work for 5th Gen tablets?

I have a 5th Gen HD 10 running 5.3.2.0. I want to try downgrading to 5.3.1.1, but all the instructions I see here only mention 6th Gen tablets.
[Fire HD 8 and HD 10 General] JAS_21:
If you contact Amazon, tell them it won't boot. They will send you a replacement. I did this and my replacement came with 5.3.1.1 installed. I was then able to root.

Edit: you may or may not get a rootable version installed. Boot up and don't connect to wifi, and check what version you have.
[Fire HD 8 and HD 10 General] domino6789:
Thanks you for reply. Amazon replace for you new device ? and I need send Device error to amazon ? Thank you again
[Fire HD 8 and HD 10 General] JAS_21:
Just tell them it won't boot. They will try to have you reset it. It won't work since you bricked it. Then they will offer to send you a replacement. Do not tell them you tried downgrading it.
[Fire HD 8 and HD 10 General] el7145:
Just an additional tip...

I went a little too crazy with TitaniumBackup uninstalling some critical system apps causing my rooted fire to go wonky. I proceeded to flash the original 5.3.1.1 firmware, which went fairly smooth, until I booted into Android. I didn't realize I had to do a factory reset before flashing the bin file. When I booted into Android, I realized that my WiFi was on and connected. Amazon was happily downloading the update...thankfully I caught it in time before it finished downloading. I then factory reset, and went back through the root guide (wifi off) and it was as smooth as the 1st time I rooted.

So if you ever have to reinstall the firmware, you MUST factory reset 1st or risk getting the Amazon update upon booting. I'm assuming this is common knowledge for most people but it wasn't for me as I incorrectly assumed flashing the bin file would format everything.
[Fire HD 8 and HD 10 General] Novalis31:
I'm about ready to brick mine on purpose and shake the dice on the OS they send on replacement tablet. Being stuck with 5.3.2.1 really sucks. Stock runs so slow, and this 8HD would run so much smoother without all this crap installed.
[Fire HD 8 and HD 10 General] tenazrael:
Isn't there a tutorial that explains how to setup your wireless router to block Amazon updates automatically? :confused:
[Fire HD 8 and HD 10 General] MyCephei:
You have to add this to the blacklist of your router.

amzdigitaldownloads.edgesuite.net

amzdigital-a.akamaihd.net

amzdigitaldownloads.edgesuite.net

softwareupdates.amazon.com

updates.amazon.com
[Fire HD 8 and HD 10 General] el7145:
youve missed my point entirely...i assumed flashing the stock bin would erase my saved settings (including wireless), thus i wasnt worried about needing to block amazon updates. Had i done a factory data reset 1st, i couldve kept wifi off until i manually blocked the updates via rootjunkys supertool.
[Fire HD 8 and HD 10 General] tenazrael:
I apologize. Making a bunch of assumptions right now before I try to go down this road. I currently have the fire hd8 (6th gen) at 5.3.2 and plugged it in to charge a few days ago and didn't realize the damn thing would turn on mid charging but luckily I saw it and turned off wifi when the download of the 5.3.2.1 update was at like 97%.

I was actually trying to search how hard it would be to actually open the fire hd 8, remove and replace the ROM chip that contains the locked bootloader and install a new one similar to what you could with the ROM chip on a motherboard. No dice. Wish I went into computer/electrical engineering.
[Fire HD 8 and HD 10 General] RawisTheGameHhH:
does anyone know what a brand new fire hd 8 ships with or is it really hit and miss?
[Fire HD 8 and HD 10 General] ShapeShifter499:
Might not be the best idea, I just did this and was disappointed to get back a tablet with the latest OS on it. All that hassle, shipping it in, waiting 5 days for a replacement. I hope 5.3.2.1 is rooted soon or even better a unlock is found and we can run LineageOS or some custom stuff.
[Fire HD 8 and HD 10 General] Novalis31:
That just saddens me deeply...
[Fire HD 8 and HD 10 General] toroxda:
Thanks for the guide. My Fire HD 8 is now rooted and SuperSU.

I was having problem at step 8 that Kingoroot kept failing. To be honest I don't know what I did that finally make it work but I did re-root (step 3), toggle "enable ADB", Revoke USB debugging authorizations" , etc. several times.

For reference, I got the Fire HD 8 yesterday and it has 5.3.1.0.
[Fire HD 8 and HD 10 General] ttcontributor:
"8. Keep the root-accessed ADB shell open, then remove root by using Kingoroot

(If your kindle reboot at this step, you need to re-root it and try the above steps again)"

Doing this, I got 'SuperSU: There is no SU binary installed, and SuperSU cannot install it. This is a problem!

If you just....'

Should I keep the Kingoroot root to get it working?

EDIT: At last got it working after a few more tries. Now it's time for Xposed!
[Fire HD 8 and HD 10 General] Pegasusleos4:
How do i root my kindle fire hd 6th generation running os 5.3.2.1 since you said do not downgrade from this os?
[Fire HD 8 and HD 10 General] JAS_21:
5.3.2.1 cannot be rooted at this time.
[Fire HD 8 and HD 10 General] GuitarrassDeAmor:
So does somebody like me who has been waiting for root (and apparently his device keeps upgrading? I'm on 5.3.2.1 and bought it months ago), do I just leave it off and wait?
[Fire HD 8 and HD 10 General] vandyman:
There is no way to root 5.3.2.1 right now.

I suggest that you read some of the threads for the Fire HD so you can gain some knowledge.

If you do not understand what you are up against, you are asking for a bricked device.

Sent from my Nexus 5X
[Fire HD 8 and HD 10 General] GuitarrassDeAmor:
You didn't understand my question.

I've been waiting for device to be rooted for a while and it is. My firmware is above what can be rooted currently, I am aware of that. So my question was do I just turn it off and leave it so it cannot auto update while a new root comes? Can I disable auto updates and/or is 5.3.2.1 rootable?
[Fire HD 8 and HD 10 General] vandyman:
You can block the updates.

There is a thread that shows different ways to block the updates, so you can can still use your Fire...

Sent from my Nexus 5X
[Fire HD 8 and HD 10 General] GuitarrassDeAmor:
Thanks I will look for that. To be honest I've used the device once since the initial setup/paying around, I had been waiting for root of some kind.
[Fire HD 8 and HD 10 General] ttcontributor:
After removing root, the file 'daemonsu' also got removed from : /system/xbin/daemonsu

then this command is not working: cp ./su /system/xbin/daemonsu

What should I do?

UPDATED: My bad, the extracted zip created double directory of Kingo.to.SuperSU

Now working fine with root.