yashsingh1/xdaforums huggingface dataset:
[Fire HD 8 and HD 10 General] DragonFire1024:
I can get Kingroot to get to 70%. I've managed that several times in the last 12+ hours. It seems to be doing most of the rooting attempt on steps 3-6, however it seems like it gets to possible stable rooting path, then Kingroot stops it saying "root failed." The tablet really does put up a fight and I mean a really good one. It's gotten to a point more than a few times where I swear it was going to reboot. So far, 70% is the highest I've been able to achieve.

1. Uninstall Kingroot if you have it installed.

2. Use your favorite tool to clear cache, then memory.

3. (optional) Reboot into recovery. (Press and hold volume down and power buttons at the same time until recovery screen appears). Select "wipe cache partition."

4. Select power down/off.

5. Power on tablet.

6. Download a fresh Kingroot APK and install it, do *NOT* open it.

7. Settings > Accessibility > Scroll to bottom > Enable Kingroot.

8. Give Kingroot 'Usage Access. *SEE HERE*

9. Open Kingroot and wait for it to check for root. If not root, click "try root."

10. Root *WILL* fail. Do *NOT* tap the request button. Instead tap 'root again.'

11. Continue tapping 'root again.' over and over. If you get to 70%, and after several times it doesn't go higher, exit Kingroot.

12. Settings > Apps > Manage All Apps > clear Data of Kingroot then force stop.

13. Repeat steps 2-5 then 7-12. Each time you clear data of Kingroot, you have to re-enable it in Accessibility.

If anyone gets above 70% please post screen shot or the likes! :D
[Fire HD 8 and HD 10 General] sd_shadow:
The percentage doesn't really mean anything, it just tries different root methods untill something works, or all methods have been tried
[Fire HD 8 and HD 10 General] Horst_999:
Does this method really work?

http://androidbiits.com/root-amazon-fire-hd-8-kfgiwi-6th-gen-easily/

Thanks for your hints!

(Sorry for google translation)
[Fire HD 8 and HD 10 General] DB126:
lol - generic rooting guide. Doubt it will work.
[Fire HD 8 and HD 10 General] plitz:
I doubt that too. But why would they do so - posting a fake rooting guide? Is Kingoroot potential malicious software or spyware?
[Fire HD 8 and HD 10 General] DragonFire1024:
You clicked on their link they have a bunch of ads on their site maybe you'll click on an ad or two. That's pretty much the only reason why that link exists.
[Fire HD 8 and HD 10 General] chemie99:
Same for me. I think we managed to partly replace with supersu but now kingo wants root access but supersu is not working so you can't grant it

so...sideloading 5.3.1.1 again
[Fire HD 8 and HD 10 General] coltxL2717:
Root is persistant. That is good news. I have disabled updates I have not been able to replace KingoROOT SuperUser for SuperSU. The filesystem refuses to be mounted as R/W. I suspect it has something to do with the locked bootloader. Not having write access is preventing BusyBox from being installed. I am also not getting any root prompts on the tablet. Root is only accessible through adb. Anyone have any ideas?

Tried all the solutions already posted in this thread.
[Fire HD 8 and HD 10 General] phpbb88:
We are still trying out...

Maybe more ppl try it and could figure it out
[Fire HD 8 and HD 10 General] chemie99:
"root is persistent" is a bit of an overstatement. Kingo persists but it is not real root.

The rest of what you say is where we are. Only adb seems to access su and nothing on tablet suggests root works.

No supersu

No apps that need root

But...the only good news, is that firelauncher does seem to be killed which at least patches the jerky novalauncher
[Fire HD 8 and HD 10 General] phpbb88:
After SuperSU updates its binary, it asked me to reboot.

I can access /system by the ES File Explorer and it said the device is rooted,

however I cannot su in adb shell anymore..

I would like to keep this status, as I cannot grant root access to anything before I change to SuperSU either.
[Fire HD 8 and HD 10 General] chemie99:
I was never able to get ES file explorer to report on root...how do you do that?
[Fire HD 8 and HD 10 General] phpbb88:
I can enable "Root Explorer" in the left side menu, doesn't it means it is a rooted device?

Cause I cannot enable that option when I am not on root.
[Fire HD 8 and HD 10 General] chemie99:
What version. I am using 4.1.5.4 and don't see that option
[Fire HD 8 and HD 10 General] phpbb88:
same as yours.
[Fire HD 8 and HD 10 General] chemie99:
Thanks did not see that. Don't know if it is there or not with respect to "root".

My status

* sideloaded 5.3.1.1

* ran kingo

able to use adb shell su to pm disable updates and OTA

better than nothing but not root. Will sit here with working novalauncher, and maybe fully disabled OTA (will monitor over 48 hours before turning off opendns). With no OTA, I can at least take this out of the house!

Future: Hope to get supersu working with real root for apps.
[Fire HD 8 and HD 10 General] phpbb88:
omg, I saw logs in SuperSu Log, some asked for root access, but the device never prompt.

I then go to superSU setting and set the default access is "grant", then my adb shell and teminal emulator works again.

I then tried 2 of the root checkers and both said my device is rooted! It seems the device wont prompt for root access so the root checkers cannot verify the root status. However "always grant root access" is a dangerous behavior I think.
[Fire HD 8 and HD 10 General] chemie99:
I saw my logs with a bunch of red "X" for TB, and other programs where I was trying. I never found any options but maybe did not look. I am fine with no prompt, it is only me using this baby.

Now, can I figure out the steps we did again?
[Fire HD 8 and HD 10 General] vandyman:
Good idea! A list of conformed steps will make things less complicated.

Sent from my Nexus 5X
[Fire HD 8 and HD 10 General] JAS_21:
**** wish i could downgrade.
[Fire HD 8 and HD 10 General] Reuben Talbott:
me too ?
[Fire HD 8 and HD 10 General] vandyman:
Yes, that is my problem as well.

I am not sure if a reset will go back to 5.1.

Sent from my Nexus 5X
[Fire HD 8 and HD 10 General] chemie99:
well,, I re-did steps in thread #15 and this time supsersu declared that the binaries were missing. No idea why it work a different way the second time around. I actually did not get any errors messages about the daemonsu being locked, which I thought was good until my inability to duplicate what I did became apparent.
[Fire HD 8 and HD 10 General] phpbb88:
FOR 2016(6th GEN) ON 5.3.1 AND 5.3.1.1 ONLY: Works on HD8 and HD10

Confirm you are on 5.3.1. or 5.3.1.1. 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!!

0. Enable ADB and install apps from other sources in Developer Settings

1. Download Kingoroot PC version at www.kingoapp.com

2. Root your Kindle using Kingoroot, then reboot your device

3. Install ES File Explorer, download SuperSU apk for later use

4. Download the attachment below and paste into, ie /sdcard/Kingo.to.SuperSU

5. Run ADB Shell and type

su
mount -w -o remount /system

6. Keep the root-accessed ADB shell open, then remove root by using Kingoroot PC version

(Someone will get the device rebooted at this step, if it does, the root-accessed ADB shell would be closed. You need to re-root the device and try the above steps again)

7. In the ADB shell type

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

8. Still keep that ADB shell opened, then sideload the SuperSU apk and install it

9. In the ADB shell type (there may be 0-1 error, its okay, more than 2, its not)

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

10. Run SuperSU and update binary then it should ask you to reboot device.

11. Open up SuperSU and go to setting

12. Set the "Default Access" as Grant instead of "Prompt" under the "Access" section

Noted that step 12 were applied due to Kindle not prompting the "Asking for root access", it is DANGEROUS to always grant root access without asking your permission, especially we are not firmed is Kingoroot safe or not, use it as your own risk.

13. Install Root Checker and confirm you have root. Run adb shell and confirm you still have su

14. Remove Kingolink and that Kingo battery app from kindle

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

You may then want to install google play, do all the pm disable for OTA, firelauncher, and other amazon services you don't want.
[Fire HD 8 and HD 10 General] phpbb88:
I got my Kindle hard-bricked because of downgrading from 5.3.2.0 to 5.3.1.0, not showing anything when power on the device.

I then sent it back to Amazon and got a free replacement because my device is under warranty.

The device it sent to me is on 5.1.1 version so I can test this root.
[Fire HD 8 and HD 10 General] chemie99:
5.3.2 can be downgraded to 5.3.1.1 (but not 5.3.1)

5.3.2.1 can't be downgraded

---------- Post added at 11:58 PM ---------- Previous post was at 11:56 PM ----------

@phpbb88

I can't get step 10 to work this time (it did before for me). Supersu gets stuck updating. Also, now I can;t get to shell su anymore either. Thoughts?

Do you still have shell su access after all steps?

What was your workaround for when kingo PC app wants you to grant access (which you can't because their superuser app crashes)?
[Fire HD 8 and HD 10 General] phpbb88:
I did step 12 and 13 to allow all root access, ADB shell works after that. Please try those 2 steps, if that doesn't work for you, I think you need to start from the beginning (clean OS) again...

edited:

oops, i didn't notice you cannot update SuperSU's binary...please try to start from clean state...

---------- Post added at 01:21 AM ---------- Previous post was at 01:14 AM ----------

I gotta sleep, its 8AM here and I didn't sleep lol.

Let see anyone success to root their devices :)

Thanks the opener of this thread coltxL2717, without him we were still waiting for kingroot. LMAO
[Fire HD 8 and HD 10 General] chemie99:
OK. I sideloaded 5.3.1.1 for the third time and followed your steps.

I would add the following for others:

For 2016 only: Confirmed working on HD8 and HD10 with correct versions (see below)

Step 0: Enable ADB and install apps from other sources. Confirm you are on 5.3.1.1 or earlier. Do not downgrade from 5.3.2.1. You can downgrade from 5.3.2 to 5.3.1.1 (but not to 5.3.1)

Step 2B: reboot

Step 14: remove kingolink and that kingo battery app from kindle

Step 15: uninstall kingo from PC via manual unins000.exe inside install directory in programs(x86)

Step 16: Install Root Checker and confirm you have root. Run adb shell and confirm you still have su

Step 17: Install google play etc. Update supersu and let it update and reboot.

Step 18: Do all the pm disables for OTA, firelauncher (if desired) and other amazon services you don;t want

Confirming I can still shell su now

(I have no idea how I got it to work, then you followed my lead on the kingo uninstall, then I could not duplicate it again. I think it was that I did not bother with any of the step1 commands. They almost all fail but there were a few that must be important. The only ones that worked were:

rm /system/xbin/supolicy

rm /system/bin/install-recovery.sh

rm -rf /system/usr/iku

if anyone wants to try just those to avoid all the other typing.

I can confirm Titanium Backup is now happy with root access. This is what I wanted.

pm disable launcher and OTA

have TB

have link2SD to run apps off SD

Thanks all. Hope others can use this too.

Edit:

I still on opendns settings; will wait 48 hours to make sure the pm disables hold

Only thing not working is widgets in nova launcher...thoughts?
[Fire HD 8 and HD 10 General] :
You win the Internet. I knew it would only be a matter of time. Since 5.3.1.1 works, should 5.3.1.0 work also? I'm slowly building up the nerve to attempt this myself.
[Fire HD 8 and HD 10 General] chemie99:
No promises but normally is works for lower versions. I had 5.3.1.1 bin in case of bad things which was good since I had to reload it 3 times during all the testing we did. Do you have 5.3.1 just in case? Worst case is you get the 5.3.1.1 off this site and move up one increment as we know 5.3.1.1 works and I don't see a problem with you flashing that if you fail terribly.
[Fire HD 8 and HD 10 General] :
Unfortunately not. Somewhere on one of the other threads someone had made mention of there not being a 5.3.1.0 flash bin in existence. Do you know what version Alexa support is added? I was hoping to avoid it.
[Fire HD 8 and HD 10 General] coltxL2717:
Can confirm phpbb88's instructions worked. Too bad about the prompt. Happy to finally be able to use my tablet.
[Fire HD 8 and HD 10 General] :
Your language and attitude make me want to try this.... :) You also win the Internet.
[Fire HD 8 and HD 10 General] phpbb88:
I am using HD8 2016, so I think HD10 also works.

Do you confirm if we only apply those 3 command would works? If so then I can edit my instruction above.

rm /system/xbin/supolicy
rm /system/bin/install-recovery.sh
rm -rf /system/usr/iku

For the OTA issue, I had do the following things

adb shell
pm hide com.amazon.otaverifier
pm disable com.amazon.otaverifier
pm hide com.amazon.device.software.ota
pm disable com.amazon.device.software.ota
pm hide com.amazon.settings.systemupdates
pm disable com.amazon.settings.systemupdates

Navigate to /system/priv-app/DeviceSoftwareOTA/ and rename DeviceSoftwareOTA.apk to something else, ie. DeviceSoftwareOTA.apk_

I tried rebooting the device, after that I still cannot access the system update section in settings.

But I do not have the guts to disable the opendns :laugh:

---------- Post added at 09:30 AM ---------- Previous post was at 08:51 AM ----------

I think you can at least try the kingoroot first, if it doesn't work, then sideload to 5.3.1.1

I think it is okay to "upgrade" from 5.3.1 to 5.3.1.1, usually downgrade bricks.
[Fire HD 8 and HD 10 General] chemie99:
I can't confirm those work without redoing which after three flashes, I do not want to do. However, they were the only ones that did not come back with an error message. Hopefully someone else can try those three to confirm. I know that you need some commands from Step1. My second failure I was getting a "you do not have permission to access" message when I tried to run. The first time, when I got supersu to work, I was able to run Step 1., so I think we do need some of the commands.

You did more than me on OTA so I will add those others to the list. Like you, I am waiting on opendns for a few more days.

Edit: I get "block" as unrecognized command; I use disable

---------- Post added at 01:28 PM ---------- Previous post was at 01:14 PM ----------

I think Alexa was 5.3.2
[Fire HD 8 and HD 10 General] phpbb88:
I just type it without checking the real one so I may be

wrong. I've edited the command above :D
[Fire HD 8 and HD 10 General] vandyman:
I brought my HD8 in November 2016 and I am sure it came with 5.3.1.1.

So if I do a factory reset, it should go back to 5.3.1.1 correct?
[Fire HD 8 and HD 10 General] just lou:
No. You'll still be on whatever version is installed.
[Fire HD 8 and HD 10 General] vandyman:
Thanks. I guess I am stuck on 5.3.2 for now.

Alexa is a beatch for not letting me root my Fire...
[Fire HD 8 and HD 10 General] phpbb88:
I think 5.3.2 can downgrade to 5.3.1.1? I tried once from 5.3.2.1 to 5.3.1.1 and hard-bricked.

Please be careful and read more about the recent threads that talk about downgrading.

If your device still in warranty, give it a try, Amazon will fix this. lol
[Fire HD 8 and HD 10 General] :
Cool beans...that makes me feel better to try this. I think I'll do it later tonight. I'll triple check the steps and updates pertaining to the 2016 hd 8 model and see how everything goes and if I mess up, I'll upgrade to .1 . And follow steps to disable ota, etc.. Yeah I don't really care for that echo/Alexa stuff.
[Fire HD 8 and HD 10 General] imitationman:
When I remove root at step 6, Kingoroot PC reboots my Kindle and then I lose my ADB shell with root and can't continue. Am I missing something?
[Fire HD 8 and HD 10 General] chemie99:
This did not happen to me. Weird.
[Fire HD 8 and HD 10 General] :
Just to get it out of the way, what version Fire OS are you on?
[Fire HD 8 and HD 10 General] krazyhand:
This thread really upsets me. my fire came with 5.3.1.1 earlier this month and updated to 5.3.2.1 all on its own so now I'm stuck and can't downgrade or root. Hopefully some power user figures something out for those of us who got totally jaded by unwanted OTA updates. Can someone link me to the thread that shows how to block them?
[Fire HD 8 and HD 10 General] imitationman:
I'm on 5.3.1.1.

I'm going to try a few more times to see if I get a different result.

---------- Post added at 12:24 PM ---------- Previous post was at 12:11 PM ----------

I found this here: https://xdaforums.com/hd8-hd10/help/blocking-hd8-2016-updates-t3525223

Most seem to be using option 4: http://www.aftvnews.com/how-to-bloc...-the-amazon-fire-tv-or-fire-tv-stick/#opendns

I went with Option 3 on my ASA and I've successfully blocked OTA's by only denying access to the 2 fqdn's, amzdigital-a.akamaihd.net and amzdigitaldownloads.edgesuite.net.
[Fire HD 8 and HD 10 General] krazyhand:
Thanks friend I'll be checking back daily with hopes for 5.3.2.1 root ?
[Fire HD 8 and HD 10 General] imranh101:
Worked great. First time doing KingoRoot uninstall my tablet did auto-restart, I just started the process over and the second time KingoRoot uninstall DID NOT restart tablet and all seems to be working. I picked up the tablet today, seems like I got lucky on timing :)
[Fire HD 8 and HD 10 General] phpbb88:
did you followed [MENTION=7164512]chemie99[/MENTION] 's step2B (reboot device when it is rooted?)

---------- Post added at 01:51 AM ---------- Previous post was at 01:50 AM ----------

did you followed [MENTION=7164512]chemie99[/MENTION] 's step2B (reboot device when it is rooted?)

Seems like there is difference if booted or not?
[Fire HD 8 and HD 10 General] imranh101:
Yes, I did follow that step! Hope it somehow helps you get yours done :)
[Fire HD 8 and HD 10 General] phpbb88:
how about the first time? is it because you did not reboot the device so that Kingoroot rebooted for you?

Cause I want to clear out the instruction, thanks.
[Fire HD 8 and HD 10 General] imranh101:
I believe I did restart the tablet after both times, strangely. But 100% sure it did work the second time, when I am 100% sure I did reboot the tablet!
[Fire HD 8 and HD 10 General] phpbb88:
Thanks for your information :)

I remembered that I did not reboot the device and it was okay to go to the next step.

it seems reboot randomly. weird

---------- Post added at 01:58 AM ---------- Previous post was at 01:57 AM ----------

FYI. you can try it again, cause someone had the same result as you and he successed on the second try.

---------- Post added at 02:09 AM ---------- Previous post was at 01:58 AM ----------

added extra info on the instruction
[Fire HD 8 and HD 10 General] imitationman:
I think that was my initial problem. Once I manually rebooted at 2B, it didn't force a reboot later. But I still haven't successfully rooted yet. I've restored my HD6 back to the 5.3.1.1 bin twice and started over but when I've gotten to step 10+ and upgraded/installed the SuperSU binaries, it works, but I don't have root outside of the adb shell. And then I reboot to make sure, and yep - no root. It's like I'm stuck with the results in posts #10-30 today.

I've been skipping the commands in Step 9 that didn't appear to work. I'm about to start my another attempt a fresh image and this time I'll run all the commands and see if it makes a difference.
[Fire HD 8 and HD 10 General] phpbb88:
if the supersu's update do not success, there should be some steps above fail.

lets see if u type the command all will success rooting your device
[Fire HD 8 and HD 10 General] imitationman:
OK - I'm an idiot. :silly:

I kept reading Step 12 about the SuperSU prompt change incorrectly and thought I was supposed to change it from 'Grant' to 'Prompt' and not the other way around - because it is mentioned that 'Grant' is less secure. I saw the picture and just thought 'this is what I don't want it to look like when I'm done'. Gah!

The commands that don't work in Step 9 can be skipped. I still have root after a reboot following your's and chemie99's steps. Thanks for putting this together.
[Fire HD 8 and HD 10 General] fyrfterjr:
When I rooted my Fire 7 and attempted to use Nova widgets, they didn't work for that either. Must be something buried in the os itself. I ended up using the stock firelauncher instead.
[Fire HD 8 and HD 10 General] phpbb88:
is it because the ”setting” apk of the fire os missing something, so that widgets dont work?
[Fire HD 8 and HD 10 General] phpbb88:
On step3, just download the SuperSU in apkpure.com or www.apkmirror.com, no need to install it first.

On step8, put the SuperSU apk in the tablet, and use ES File Explorer to install it.

Moreover, just a little remind the code should be typed sentence by sentence, do not copy and paste all the code.

---------- Post added at 11:46 AM ---------- Previous post was at 11:43 AM ----------

keep the 5.3.1.1 bin, when fail it is better to start from fresh, for the kingoroot software, keep it untill you confirm you have successfully root your device, then you can uninstall it.
[Fire HD 8 and HD 10 General] :
I'll try it again. I got too tired last night. Also, is it possible to reapply this .bin to the same OS version? It won't let you apply it via dragging the .bin file to the fire device and then going to system update to apply manually, it says its on the same version. So just wondering if there is a way to bypass that and have it still reflash if need be.

Other than that, will factory reset and try again.

** Ok this is where I'm at:

For step 3: I just "adb install es-file-explorer-4-1-6.apk" from a 2nd command prompt window..And I just downloaded supersu.apk and not put in tablet yet.

I goto steps 4, 5. 6, on step 5, I remove root

In my # ADB Shell I issue "

cd /sdcard/Kingo.to.SuperSU

cp ./su /system/xbin/daemonsu

chmod 0755 /system/xbin/daemonsu

daemonsu -d &

No errors.

Step 8: I use es file explorer to navigate to /download where I put supersu.apk and install it..but do not open it

Then I issue:

rm /system/xbin/supolicy

rm /system/bin/install-recovery.sh

rm -rf /system/usr/iku

No Errors

Now: When I open superSU, I immediately get error There is no SU Binary installed and supersu cannot install. It doesn't even ask me to update binaries. I could be wrong, but those 3 remove commands "rm" make it so I cannot install binaries for supersu. I'm following the directions I think to the letter.

All commands are issued one at a time.
[Fire HD 8 and HD 10 General] phpbb88:
will that be the cause that u only factory reset but not sideloading the bin file in recovery mode?

go to recovery mode by holding power and volume down button together when turning on device, then you should clear cache, and then factory reset, after that adb sideload the bin file.

If you followed the steps above, it should work. So weired

---------- Post added at 08:37 PM ---------- Previous post was at 08:36 PM ----------

also u can paste the adb shell log here to see if anything messed or missed