Database Users

KingRoot works

I tried the OS 4.5.2 rooting from the forum and that did not work. I tried KingRoot and its works. Can someone test this on OS 4.5.3 or higher OS please
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Sent from HDX 7 OS 4.5.2 Rooted

Tried it on 4.5.4. But KingRoot showed me, that root was failed. So no luck.

Sometimes you have to tried several times the last time I fail too but the second works. I dont know what cause it
Sent from HDX 7 OS 4.5.2 Rooted

PsymH said:
Tried it on 4.5.4. But KingRoot showed me, that root was failed. So no luck.
Click to expand...
Click to collapse
From what I've heard, 4.5.4 can't be rooted. If you have a 3rd generation HDX, then you have to first downgrade to 3.2.8 and then manually update to 4.5.2.

Is this still true? Has anyone used Kingroot on 4.5.5.3? It looks like they are saying it works now...
Announcement from Kingxteam: KingRoot 4.6 has been released, she can root 5.1 well and some 6.0 devices
Will someone please confirm? I'm about to take the plunge. I'm hoping the worst that can happen is that it simply fails. I can't ADB with my HDX 3rd gen (usb port won't interface with PC) so I won't have a way back from softbrick/bootloop.

rabaker07 said:
Is this still true? Has anyone used Kingroot on 4.5.5.3? It looks like they are saying it works now...
Announcement from Kingxteam: KingRoot 4.6 has been released, she can root 5.1 well and some 6.0 devices
Will someone please confirm? I'm about to take the plunge. I'm hoping the worst that can happen is that it simply fails. I can't ADB with my HDX 3rd gen (usb port won't interface with PC) so I won't have a way back from softbrick/bootloop.
Click to expand...
Click to collapse
You obviously understand the risk and assume you tried alternate (Moto) drivers along with different cables and host ports to confirm diagnosis. Note cables/ports that work on one device may not on another - especially finicky HDX hardware.
You're probabky not going to get a high confidence response to your KingRoot question as most take the full step of unlocking. Plus age of device and waning interest. Good luck.

Yes, I realized that the only thing that can go wrong with the root attempt (kingroot or otherwise) is that it fails and you still don't have access to root. No harm no foul. The risks come in when you attempt to flash a ROM and it fails by partially loading and overwriting/erasing critical files without completing (loss of power mid flash!) or if the ROM is incompatible in some way and you are unable to flash your previous ROM. That's where bootloader recovery software comes in (TWRP and the like). So that you can access the system before loading (or failing to load) the ROM, and flash over it or flash a backup.
Moral of the story is that YES, Kingroot works on HDX 3rd Gen on 4.5.5.3. I tried it last night and it worked. I now have access to the root directory. Oh, the places you'll go!!
Sent from my Pixel 2 XL using Tapatalk

rabaker07 said:
Yes, I realized that the only thing that can go wrong with the root attempt (kingroot or otherwise) is that it fails and you still don't have access to root. No harm no foul.
Click to expand...
Click to collapse
Nope; root attempts can yield a bootloop or otherwise dysfunctional device. Glad all worked out for you.

Ouch. I didn't realize that. It always seemed very benign and I've never had it go wrong. I guess I'm used to devices that are designed to be accessible. Fortunately my HDX rooted without a hitch.

FireOS 5.3.1.1 is coming - root 5.3.1 ASAP & disable OTA !!!

I've glanced at the updates for the latest Fire HD 8 2016 model, and it has version 5.3.1.1 already available :
https://www.amazon.com/gp/help/customer/display.html?nodeId=202073860
So if history is any guide, all the other Fires will see the same update real soon now ...
Use the latest Kingroot to root FireOS 5.3.1, and disable OTA !!!
http://forum.xda-developers.com/amazon-fire/general/root-t3471289

How do I remove ota Updates?
I renamed 2 APKs now when I check for updates it reports "Failed" am I Fine?
I want to switch to CM12.1 but I am afraid to try the method for 5.1.2 someone said it is the same procedure but I am not yet srue.
and I need to pay for Super Sume I guess.
so At least can someone clear out how we disable ota updates? I don't trust PM hide method, Renamed some apk but I am not sure if it worked.

-Yami- said:
How do I remove ota Updates?
I renamed 2 APKs now when I check for updates it reports "Failed" am I Fine?
I want to switch to CM12.1 but I am afraid to try the method for 5.1.2 someone said it is the same procedure but I am not yet srue.
and I need to pay for Super Sume I guess.
so At least can someone clear out how we disable ota updates? I don't trust PM hide method, Renamed some apk but I am not sure if it worked.
Click to expand...
Click to collapse
You could use rootjunky's supertool but if it already says failed it should be fine

tonibm19 said:
You could use rootjunky's supertool but if it already says failed it should be fine
Click to expand...
Click to collapse
thanks I'll go ahead and also apply rootjunkies supertool method, I wasnt sure if it gonna work on 5.3.1 so didn't try.
Just to make sure I am not letting it connect to internet, switching to CM12.1 will be the best.

-Yami- said:
How do I remove ota Updates?
I renamed 2 APKs now when I check for updates it reports "Failed" am I Fine?
I want to switch to CM12.1 but I am afraid to try the method for 5.1.2 someone said it is the same procedure but I am not yet srue.
and I need to pay for Super Sume I guess.
so At least can someone clear out how we disable ota updates? I don't trust PM hide method, Renamed some apk but I am not sure if it worked.
Click to expand...
Click to collapse
Really need to take a step back and review the documentation that has already been posted starting with the forum index . Tons of relevant material. The SuperTool should handle everything you need in advance of flashing a new ROM if that's your objective:
- SuperTool can disable OTAs, replace KingUser with SuperSU and perform a host of other useful tasks
- "renamed some apk" is not helpful; details matter
- don't need to pay for anything beyond the device itself
- if still worried about OTA updates turn off WiFi and keep reading on another device

Davey126 said:
Really need to take a step back and review the documentation that has already been posted starting with the forum index . Tons of relevant material. The SuperTool should handle everything you need in advance of flashing a new ROM if that's your objective:
- SuperTool can disable OTAs, replace KingUser with SuperSU and perform a host of other useful tasks
- "renamed some apk" is not helpful; details matter
- don't need to pay for anything beyond the device itself
- if still worried about OTA updates turn off WiFi and keep reading on another device
Click to expand...
Click to collapse
I am aware of supertool, I was not sure if it gonna work on 5.3.1 or not and someone said he switched using super sume so it was paid.
I renamed otaverifier.apk and devicesoftwareota.apk
I'll go ahead and use supetool thank you.
edit:
I got an option:
1 block OTA updates from Amazon 5.0.1
2 block OTA updates from Amazon on 5.1.1 and 5.1.2
so this was why I avoided this tool, not sure which one to use and not sure if it gonna brake something or not because I am on 5.3.1
I'll go ahead and read .bat file.
edit2:
found these lines
files\adb.exe shell pm hide com.amazon.otaverifier
files\adb.exe shell pm hide com.amazon.device.software.ota
files\adb.exe shell pm hide com.amazon.settings.systemupdates
Renamed those APKs.
but the tool also have this:
files\adb.exe shell su -c "rm -r /system/app/otaverifier"
files\adb.exe shell su -c "rm -r /system/priv-app/DeviceSoftwareOTA"
files\adb.exe shell su -c "rm -r /system/priv-app/SystemUpdatesUI"
so these are responsible APKs, I missed out "SystemUpdatesUI" on my first try thanks to this tool now I know what do rename.
I must be safe now I guess, it is not going to download and replace those bcz I didnt use PM-Hide.
edit:
I also cannot find any option to convert from kingroot to SuperSu in supertool.
at least not in its menu.

-Yami- said:
I am aware of supertool, I was not sure if it gonna work on 5.3.1 or not and someone said he switched using super sume so it was paid.
I renamed otaverifier.apk and devicesoftwareota.apk
I'll go ahead and use supetool thank you.
edit:
I got an option:
1 block OTA updates from Amazon 5.0.1
2 block OTA updates from Amazon on 5.1.1 and 5.1.2
so this was why I avoided this tool, not sure which one to use and not sure if it gonna brake something or not because I am on 5.3.1
I'll go ahead and read .bat file.
Click to expand...
Click to collapse
- devicesoftwareota.apk is the operative file; just make sure it does not end in .apk
- as noted in numerous recent posts follow the procedures for 5.1.2 with 5.3.1
- if you can read/interpret the .bat file then none of this should be a mystery; the SuperTool simply automates a number of relatively trivial tasks that can be performed manually if desired (taking nothing away from the SuperTool; it is a fantastic resource for a huge community of individuals who have benefited from the selfless individual who authored it; props to @tomstg, a.k.a. Root Junkie!).
- if you have a question, ask; just be sure you have done your homework first given the vast pool of resource that is already out there; no interest in repackging what has already been written; props to @sd_shadow who tirelessly collects information from contributors and and assembles guides for YOUR benefit.
- if still uncertain shelve the device for a few weeks until the dust settles given the recent (<48 hours old) discovery that 5.3.1 can be rooted

Can 5.3.1.1 be downgraded to 5.3.1.0?

Danny1976 said:
Can 5.3.1.1 be downgraded to 5.3.1.0?
Click to expand...
Click to collapse
Unknown but assume not unless posted otherwise. Only way to know is someone tries it and scores success or a brick.

I got my Fire HD8 (6th gen/2016) and the update for 5.3.1.1 is available. Still hasnt updated, I turned it off now. I cannot root 6th gen HD8 and I dont know of any methods that prevent the OTA update without root. Help
Edit: ops, I fail at navigating the xda forum apparently. I didn't see im in the wrong section.

I guess a benefit of the having a low end device like the Fire 7" is that they receive updates later than other devices. So you are aware of problems related to rooting early.
Anyways I ordered a Fire at Amazon Germany that arrived today and was initially shipped with Firmware 5.0.1.
I wonder why they still ship out devices with such old firmware. But tht's good for us

sebr said:
I guess a benefit of the having a low end device like the Fire 7" is that they receive updates later than other devices. So you are aware of problems related to rooting early.
Anyways I ordered a Fire at Amazon Germany that arrived today and was initially shipped with Firmware 5.0.1.
I wonder why they still ship out devices with such old firmware. But tht's good for us
Click to expand...
Click to collapse
You know the drill - root and protect that bootloader before connecting to WiFi! Or take the express route and boot directly into fastboot via <power>+<vol-down>, fire up TWRP and have your way with a custom ROM. Bounce back if you need any help with procedures.

Yeah no worries CM12 already running on it. But what is different in Bootloader versions past 5.0.1? I thought the bootloader is locked anyways - regardless of what firmware version is used - and cannot be flashed.

sebr said:
Yeah no worries CM12 already running on it. But what is different in Bootloader versions past 5.0.1? I thought the bootloader is locked anyways - regardless of what firmware version is used - and cannot be flashed.
Click to expand...
Click to collapse
5.0.x bootloader allows a custom recovery (eg: twrp) to be booted from fastboot. Nothing like a true recovery to expedite flashes and recover from missteps.

Yeah.... I wasn't able to get KingRoot to work with 5.3.1.1 and now I'm on 5.3.2 and it still won't work. I just got this tablet about a week ago. I should have rooted it before I first connected to WiFi, but I received it as a gift, so I hadn't researched the process in advance and I wasn't certain that I wanted to mess with it. I usually root my devices, but I considered leaving this one unrooted... until it was too late. Sometimes, a little hesitation makes the decision for you.

ManWithCamera said:
Yeah.... I wasn't able to get KingRoot to work with 5.3.1.1 and now I'm on 5.3.2 and it still won't work. I just got this tablet about a week ago. I should have rooted it before I first connected to WiFi, but I received it as a gift, so I hadn't researched the process in advance and I wasn't certain that I wanted to mess with it. I usually root my devices, but I considered leaving this one unrooted... until it was too late. Sometimes, a little hesitation makes the decision for you.
Click to expand...
Click to collapse
First I have heard of 5.3.1.1 and 5.3.2 for 5th gen tablets. Sure you have a 7" model (first released Sept 2015) and not the latest HD8 (released 2016)?

Davey126 said:
First I have heard of 5.3.1.1 and 5.3.2 for 5th gen tablets. Sure you have a 7" model (first released Sept 2015) and not the latest HD8 (released 2016)?
Click to expand...
Click to collapse
That's probably because the smart people on here have already blocked their updates. Yes, I confirmed that a 7" tablet is what was ordered from Amazon. It also has 2015 stamped on the back and it claims to be a 5th generation tablet in the settings. It installed the 5.3.2.0 update last night at 11:18pm.

ManWithCamera said:
That's probably because the smart people on here have already blocked their updates. Yes, I confirmed that a 7" tablet is what was ordered from Amazon. It also has 2015 stamped on the back and it claims to be a 5th generation tablet in the settings. It installed the 5.3.2.0 update last night at 11:18pm.
Click to expand...
Click to collapse
So now we know: FireOS 5.3.2 is in the wild and (apparently) can not be rooted w/KingRoot at present. What isn't known is whether 5.3.2 can be rolled back to 5.3.1 without bricking. Typically someone has to sacrifice their device (accidentally or intentionally) to determine that.
I'll create a new thread with you findings later today if someone doesn't beat me to it. Thanks for sharing.

FireOS 5.3.2.1 rollbacks

FYI - early indications 5.3.2.1 -> 5.3.1.0 rollbacks are problematic.
http://forum.xda-developers.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/post70052733

Here as well
http://forum.xda-developers.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/post70061090

Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files
Attached a scatter file I found online for the MTK8127 chipset, which fire has. No idea if it's right. SP tool for some reason won't keep the com port open...

kaysond said:
Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files
Attached a scatter file I found online for the MTK8127 chipset, which fire has. No idea if it's right. SP tool for some reason won't keep the com port open...
Click to expand...
Click to collapse
scatter files haven't worked, with any firmware versions
Sent from my sailfish using XDA Labs
---------- Post added at 05:50 PM ---------- Previous post was at 05:47 PM ----------
see http://forum.xda-developers.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747
Sent from my sailfish using XDA Labs

Yeah, I got the READYREADYREADYREADYREADY brick that I was expecting. Three tablets, got two of them rooted and OTA blocked, then had an emergency and the third apparently wasn't actually Off so it happily ****ed me.
There's never been a recovery from the READYREADYREADY firmware loader, I'd assume? Deciding if I should keep or toss this one. At least this ****'s cheap since we don't actually own it.

I just got an Amazon Fire and am new to this whole thing. Ultimately I'd love to root it, and install a different ROM. But in the short term, I'm just playing with installing the Play Store and turning off lock screen ads. Anyway, I just opened the package up today, and I let it update itself to 5.3.2.1 before I was aware that this might cause me trouble.
I did download the SuperTool here:
http://rootjunkysdl.com/files/?dir=SuperTool
I successfully installed the Play Store. I next tried disabling the lock screen ads, but the tool said I would need to root first. When I selected the option to do that, it asked for my FireOS version, but didn't give 5.3.2.1 as an option. So I'm afraid to go through the root process.
It sounds like downgrading to an earlier version will brick this. What about rooting it with a tool like the one I downloaded? Is that likely to cause trouble as well? Is there much I can do with this currently?

There's no known way (yet) to flash 5.3.2.1 back to something earlier, that's true (and some who got hit by a brick will confirm).
There's also no known success (yet) rooting this, but since KingRoot is evolving, there may be hope. There are multiple releases of KR around, and the cloud part (where the methods are kept) seem to be constantly changing - if you decide to keep the Fire, you may as well spend some time trying to get it rooted... KR versions 4.8.5, 4.9.2, 4.9.6 have been suggested; if you decide to use KR 5, you will have to remove it from the list of device administrators before replacing it with SuperSU - of course only if you're successful. We're all waiting for RootJunky to release a new SuperTool that will possibly automate this - ATM Nov 29 is still the latest version available...

Does the RootJunky SuperTool just use KR under the hood? I'll have to keep an eye on this. I don't mind getting my hands a bit messy on this, but I don't want to be blazing a new trail. I'm not experienced enough with it. I don't mind waiting a bit to get some hand holding.

komi_9 said:
Does the RootJunky SuperTool just use KR under the hood?
Click to expand...
Click to collapse
It does:
Code:
$ grep -ri kingroot.apk .
./1-Amazon-Fire-5th-gen.bat:files\adb.exe install -r apps\Kingroot.apk
./3-Amazon-Fire-5th-gen-linux-mac.sh: sudo $ADB install -r apps/Kingroot.apk
SuperTool is a zip file - and the "magic" is done in human-readable scripts (bat or bash). Firmware bin files are zips too. Open them in your fav archive tool, and inspect what's inside.
tl;dr: ST installs whatever you put into apps/Kingroot.apk - watch out for Spelnig when replacing the version coming with ST with another one you have dl'ed from apkmirror.

hope this works! Thanks for the good work guys

dmerillat said:
Yeah, I got the READYREADYREADYREADYREADY brick that I was expecting. Three tablets, got two of them rooted and OTA blocked, then had an emergency and the third apparently wasn't actually Off so it happily ****ed me.
There's never been a recovery from the READYREADYREADY firmware loader, I'd assume? Deciding if I should keep or toss this one. At least this ****'s cheap since we don't actually own it.
Click to expand...
Click to collapse
I'm fairly certain you can still write to the flash memory from that loader, just a matter of figuring out how. There's a python script that I think will work as long as you figure out what to write...

So..there is no way to Root or downgrade 5.3.2.1??

At this moment there isn't, sorry. But tools are not static, and there's even the chance that a future fireOS upgrade will be easier to root. You've got the choice to return your Fire while/if still on warranty or wait for better days to come.
Edit: I have read rumours that KingRoot would now be able to root 5.1.3 - this, of course, may be due to the usual number confusion (and 5.3.1 was meant).
On the other hand, the patch level of 5.3.2.1 might not include DirtyCow attacks yet:
Code:
ro.build.version.security_patch=2016-10-05
and indeed I saw RootJunky add some DC stuff to his download site... There might be something around the corner, indeed.

Confirm, even hardbrick if flash from 5.3.2.1 to 5.3.2

I just used the supertool on the same model Fire tab, on 12/27/16. Here's what I've learned:
1. Amazon will indeed remove offers/ads from the discounted Fire, without cost, if you ask.
2. Supertool uses KingRoot, as of my download date.
3. Supertool was not successful in removing ads, but did install the Play Store. It did prevent OTA updates, but the root didn't work for me, so I reloaded original firmware and of course it updated right away. Next time I would try to root after registering my Fire with Amazon.
4. It aopeared to me that the Supertool attempted a downgrade (5.1.1?) before rooting, so if downgrading will brick a device running 5.3.2.1, then I think the answer to the OP's question is "no".
related question: Knowing all the above, can I still re-try the Supertool option #1, and (re)install the Play Store and remove ads? (I bought 3 of them Amazon removed ads on 1 of them so far.))

rallison203 said:
I just used the supertool on the same model Fire tab, on 12/27/16. Here's what I've learned:
1. Amazon will indeed remove offers/ads from the discounted Fire, without cost, if you ask.
2. Supertool uses KingRoot, as of my download date.
3. Supertool was not successful in removing ads, but did install the Play Store. It did prevent OTA updates, but the root didn't work for me, so I reloaded original firmware and of course it updated right away. Next time I would try to root after registering my Fire with Amazon.
4. It aopeared to me that the Supertool attempted a downgrade (5.1.1?) before rooting, so if downgrading will brick a device running 5.3.2.1, then I think the answer to the OP's question is "no".
related question: Knowing all the above, can I still re-try the Supertool option #1, and (re)install the Play Store and remove ads? (I bought 3 of them Amazon removed ads on 1 of them so far.))
Click to expand...
Click to collapse
- SuperTool does not attempt a FireOS rollback
- 5.1.1 refers to underlying Android build
- Amazon will (reluctantly) remove ads from ONE device registered to an account
- KingRoot works best if device is NOT registered with Amazon
- at present KingRoot is not effective against FireOS 5.3.2+

Thanks for responding, sorry for any misinformation, I'm quite a noob. So - if the supertool doesnt rollback, do you think I'd have trouble retrying the ad removal tool while running 5.3.2.1. ?

rallison203 said:
Thanks for responding, sorry for any misinformation, I'm quite a noob. So - if the supertool doesnt rollback, do you think I'd have trouble retrying the ad removal tool while running 5.3.2.1. ?
Click to expand...
Click to collapse
Don't see any significant risks with rerunning but also don't think it will be fully effective on an unrooted device.

Is this probably the best thread to follow if I want to be notified when it's possible to root 5.3.2.1?

valzi said:
Is this probably the best thread to follow if I want to be notified when it's possible to root 5.3.2.1?
Click to expand...
Click to collapse
I hope so, I'm certainly subscribed

5.3.2.1 Root

A contributor is reporting success rooting 5.3.2.1 with Kingroot. No immediate confirmation...simply reposting for visability and comment. Report your results here for community benefit.
https://forum.xda-developers.com/am...-5th-gen-supertool-root-t3272695/post70784402
Reminder: Do not attempt to rollback FireOS 5.3.2.1; you will likely be rewarded with a brick.

No success for me. I have assumed "Gave both king root and purify full access via setting" as enabling these apps in accessibility under services?
I have tried KR 4.9.2, 4.9.6, 4.9.7, 5.0.0 and 5.0.3 numerous times. Also done a factory reset and followed the steps stated to no avail.
Maybe I am just unlucky.

stonedpsycho said:
No success for me. I have assumed "Gave both king root and purify full access via setting" as enabling these apps in accessibility under services?
I have tried KR 4.9.2, 4.9.6, 4.9.7, 5.0.0 and 5.0.3 numerous times. Also done a factory reset and followed the steps stated to no avail.
Maybe I am just unlucky.
Click to expand...
Click to collapse
Not having any luck with it either.

This is just a quick overview for testing purposes. As always, there is an extreme chance of the undesired "Bricked Device". You are warned...
1. Make sure adb and fastboot drivers are enabled and working to the 5th gen Fire. Extremely important.
2. Once connection is working follow the "Super Tool" setup directions.
3. Disable ota, disable ads and install GPlay. Somethings can only be done after root.
4. Once you have Gplay setup, use Super Tool to install KingRoot.
5. When you first run KingRoot, it will advertise "Purify Battery Saver" install it.
6. Afterwards run KingRoot. It will reboot 3-5 times before applying root. This process of rooting consumed over an hour and may need to be restarted if KingRoot fails.
7. Please keep in mind it is just an overview in order to determine the steps correctly.
If necessary I will start from square one and document all my steps. After rooting, I downgraded to 5.3.1 and verified 2 roms worked (Fire Nexus and CM Fire.)
My apologies for not providing more accurate details, its just an overview.

TechDad378 said:
This is just a quick overview for testing purposes. As always, there is an extreme chance of the undesired "Bricked Device". You are warned...
1. Make sure adb and fastboot drivers are enabled and working to the 5th gen Fire. Extremely important.
2. Once connection is working follow the "Super Tool" setup directions.
3. Disable ota, disable ads and install GPlay. Somethings can only be done after root.
4. Once you have Gplay setup, use Super Tool to install KingRoot.
5. When you first run KingRoot, it will advertise "Purify Battery Saver" install it.
6. Afterwards run KingRoot. It will reboot 3-5 times before applying root. This process of rooting consumed over an hour and may need to be restarted if KingRoot fails.
7. Please keep in mind it is just an overview in order to determine the steps correctly.
If necessary I will start from square one and document all my steps. After rooting, I downgraded to 5.3.1 and verified 2 roms worked (Fire Nexus and CM Fire.)
My apologies for not providing more accurate details, its just an overview.
Click to expand...
Click to collapse
Are you sure it was 5.3.2.1 you where on ? I only ask because downgrading to 5.3.1 from 5.3.2.1 should result in a brick as the boot loader used in 5.3.1 and 5.3.2 changed from on 5.3.2.1 and the anti-roll back measure amazon have should have kicked in to give you a brick.
How did you roll back ? Through ADB or placing the update file in the internal SD ?

Correct it was 5.3.2.1. While playing around with it I hit a black screen while booting. Upon reading some posts, I thought there was no return because of the version. Since the device responded via usb on pc, adb sideload worked causing downgrade to work.
Don't get me wrong this may have been just pure random luck. But hopefully my results my lead to "Fire Lineage OS".

No luck with this method. Will keep trying.

Zero Luck yet as well. Will try again. Hopefully something more reliable will come about soon.

Sorry to hear you have had no success. Will revert everything back and document each step. Once the method has been identified as successful, the information will be provided.

You still need to provide us with one of the most important tips, what version of kingroot you are using.
Thank you

TechDad378 said:
... But hopefully my results my lead to "Fire Lineage OS".
Click to expand...
Click to collapse
Quick side note: No LineageOS for this pup while the bootloader remains locked. LineageOS begins with Android 6 (Marshmallow); the current suite of Android 5 (Lollipop) ROMs is all we'll see due to FireOS 5 kernel restrictions. Unless Amazon releases and back ports FireOS 6 to older devices. Highly unlikely IMHO ... economics don't square.

If someone succeeds, could they try to post the kmPlugins.zip from their downloads folder? If we can get that from a successful root, then we could probably skip all the repeated failures and just get KingRoot to use that method immediately.

What ever happened to the guy that had rooted it? I knew he was bs.

Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
Hmm...
Interesting response.
With a full time job and a family, this is a hobby I do for fun in my spare time. Most mods are done with patience and diligence.
Recommending following command,
C:/yourself/ adb sideload patience.zip
---------- Post added at 03:20 AM ---------- Previous post was at 03:09 AM ----------
Davey126 said:
Quick side note: No LineageOS for this pup while the bootloader remains locked. LineageOS begins with Android 6 (Marshmallow); the current suite of Android 5 (Lollipop) ROMs is all we'll see due to FireOS 5 kernel restrictions. Unless Amazon releases and back ports FireOS 6 to older devices. Highly unlikely IMHO ... economics don't square.
Click to expand...
Click to collapse
Point taken. Just hoping LineageOS will be as widespread.
As for the root, I reverted back to original. Trying to recreate the environment which allowed success.

Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
Nice. If you bothered to read his post history you might think differently. Well presented/documented with all the appropriate caveats.

Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
What a shame that people can't be considerate online anymore.

@TechDad378 Could you verify what supertool version you are using . I'm trying to figure what version of gapps got installed, and can you recall if you installed any apps from playstore like chrome ?
I don't have a tablet with 5.3.2.1 but it occoured to me that kingroot may have found a backdoor to root in playstore or another installed app. I've tested on a tablet with previously unrootable 5.1.4 and the difference in root behaviour pre/post play store installion is very noticable. The tablet reboots several time during root with playstore installed , it only rebooted once without it installed.
Ive not managed to root it yet but kingroot now stuck on verifing root status, it previouly detected it as unrooted, something has changed
My router is blocking OTA so going keep playing with this

5.1.4 Rooted !!!!!
Mr McBoatface said:
@TechDad378 Could you verify what supertool version you are using . I'm trying to figure what version of gapps got installed, and can you recall if you installed any apps from playstore like chrome ?
I don't have a tablet with 5.3.2.1 but it occoured to me that kingroot may have found a backdoor to root in playstore or another installed app. I've tested on a tablet with previously unrootable 5.1.4 and the difference in root behaviour pre/post play store installion is very noticable. The tablet reboots several time during root with playstore installed , it only rebooted once without it installed.
Ive not managed to root it yet but kingroot now stuck on verifing root status, it previouly detected it as unrooted, something has changed
My router is blocking OTA so going keep playing with this
Click to expand...
Click to collapse
Well it may not be the news most visiting this thread are looking for but I've rooted the previously unrootable 5.1.4 !!!!
I played around with various play store installations as suggested in my post above looking for a back door to root. 3 hours and got no where. Decided to downgrade to 5.1.2 and use supertools to root it the tablet. For the life of my I couldn't root this rootable OS..... six attempts failed each with multipul reboots. Then I read up a bit more and use kingroot 4.8.2 as suggested in this thread - https://forum.xda-developers.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300. This time 5.1.2 Rooted first time one reboot using Kingroot. I had always thought the Kingroot edition used didn't really matter that the files it used came from the online database. This result put that assumption into doubt.
Decided to go back to 5.1.4 and retry using the kingroot as above....... Didn't work. Not being someone who gives up easy i tried the impressively long-named "NewKingrootV5.0.1_C165_B377_xda_release_protected_2016_12_22_20161222120332_105243_signed.apk" from here https://forum.xda-developers.com/devdb/project/?id=9793#downloads
Rooted first time !!! It did reboot a few times, I had to manually restart the root process each time it rebooted but it picked off at the % point where it rebooted.
Moral of the story never give up and try some kingroot versions from the xda links above
Going to reset the device and confirm it's repeatable.

Mr McBoatface said:
Well it may not be the news most visiting this thread are looking for but I've rooted the previously unrootable 5.1.4 !!!!
I played around with various play store installations as suggested in my post above looking for a back door to root. 3 hours and got no where. Decided to downgrade to 5.1.2 and use supertools to root it the tablet. For the life of my I couldn't root this rootable OS..... six attempts failed each with multipul reboots. Then I read up a bit more and use kingroot 4.8.2 as suggested in this thread - https://forum.xda-developers.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300. This time 5.1.2 Rooted first time one reboot using Kingroot. I had always thought the Kingroot edition used didn't really matter that the files it used came from the online database. This result put that assumption into doubt.
Decided to go back to 5.1.4 and retry using the kingroot as above....... Didn't work. Not being someone who gives up easy i tried the impressively long-named "NewKingrootV5.0.1_C165_B377_xda_release_protected_2016_12_22_20161222120332_105243_signed.apk" from here https://forum.xda-developers.com/devdb/project/?id=9793#downloads
Rooted first time !!! It did reboot a few times, I had to manually restart the root process each time it rebooted but it picked off at the % point where it rebooted.
Moral of the story never give up and try some kingroot versions from the xda links above
Going to reset the device and confirm it's repeatable.
Click to expand...
Click to collapse
Nice! While you can downgrade 5.1.4, this mean it may be possible to root without using a PC to downgrade first. I'm going to try on 5.3.2.1, and see how it works.
Sent from my Amazon Fire using XDA Labs

Repeated root on 5.1.4, replace the kingroot in supertools with the "NewKingrootV5.0.1_C165_B377_xda_release_protected _2016_12_22_20161222120332_105243_signed.apk" version and ran the script.
It needed 2 attempts this time but it rooted. The supertools script removed it and replaced with supersu.
See attached video in zip to confirm

Kingoroot

Kingoroot works! Not kingroot. Find thread to remove kingouser and replace with SuperSU.

jerryspring said:
Kingoroot works! Not kingroot. Find thread to remove kingouser and replace with SuperSU.
Click to expand...
Click to collapse
Yep, on some FireOS builds. Unfortunately, tends to leave a ton of untrustworthy crud behind. Better to unlock bootloader and go with a custom ROM.

DB126 said:
Yep, on some FireOS builds. Unfortunately, tends to leave a ton of untrustworthy crud behind. Better to unlock bootloader and go with a custom ROM.
Click to expand...
Click to collapse
I got chains supersu running, but I can't rid the kingo superuser app. Ugh.

DB126 said:
Yep, on some FireOS builds. Unfortunately, tends to leave a ton of untrustworthy crud behind. Better to unlock bootloader and go with a custom ROM.
Click to expand...
Click to collapse
Could I go into file explorer and delete in /system the kingosupersu app?

jerryspring said:
I got chains supersu running, but I can't rid the kingo superuser app. Ugh.
Click to expand...
Click to collapse
jerryspring said:
Could I go into file explorer and delete in /system the kingosupersu app?
Click to expand...
Click to collapse
Probably...but do so at your own risk. Welcome to the wonderful world of kingo crap.

DB126 said:
Probably...but do so at your own risk. Welcome to the wonderful world of kingo crap.
Click to expand...
Click to collapse
I'm afraid of bricking the Kindle by doing the bootloader unlocked. This isn't my device and I'm doing it for a friend

jerryspring said:
I'm afraid of bricking the Kindle by doing the bootloader unlocked. This isn't my device and I'm doing it for a friend
Click to expand...
Click to collapse
You can't brick unlocking the bootloader. You *can* soft brick rooting with a locked bootloader as there is no recovery path if s##t happens. BTW, You can't simply reload FireOS via stock recovery which is crippled. Welcome to the gang plank which you stepped into by using KingOroot.

DB126 said:
You can't brick unlocking the bootloader. You *can* soft brick rooting with a locked bootloader as there is no recovery path if s##t happens. BTW, You can't simply reload FireOS via stock recovery which is crippled. Welcome to the gang plank which you stepped into by using KingOroot.
Click to expand...
Click to collapse
Yea. I knkw. Haha

DB126 said:
You can't brick unlocking the bootloader. You *can* soft brick rooting with a locked bootloader as there is no recovery path if s##t happens. BTW, You can't simply reload FireOS via stock recovery which is crippled. Welcome to the gang plank which you stepped into by using KingOroot.
Click to expand...
Click to collapse
I read that o.p . Idk where to even begin how to unlock the bootloader.

jerryspring said:
I read that o.p . Idk where to even begin how to unlock the bootloader.
Click to expand...
Click to collapse
Sounds like you're in over your head. If the device is working say a blessing and move on.

DB126 said:
Sounds like you're in over your head. If the device is working say a blessing and move on.
Click to expand...
Click to collapse
There is no tutorial. I am not new to rooting and etc.

jerryspring said:
There is no tutorial. I am not new to rooting and etc.
Click to expand...
Click to collapse
Sure. But as you noted HDX devices are rather fragile (easy to soft brick; hard to recover) unless unlocked. That was the point of my prior post. If you are not comfortable with the terminology, which is definitely on the more advanced side, and your friend's device is still working it would probably be best to walk away before something bad happens.

DB126 said:
Sure. But as you noted HDX devices are rather fragile (easy to soft brick; hard to recover) unless unlocked. That was the point of my prior post. If you are not comfortable with the terminology, which is definitely on the more advanced side, and your friend's device is still working it would probably be best to walk away before something bad happens.
Click to expand...
Click to collapse
I am comfy with the terminology. My point is, there is no tutorial on unlocking bootloader. Unless it's a easy command of fastboot OEM unlock.

jerryspring said:
I am comfy with the terminology. My point is, there is no tutorial on unlocking bootloader. Unless it's a easy command of fastboot OEM unlock.
Click to expand...
Click to collapse
These are the two main unlock threads aimed at the general user community. First points to a series of documents that is essentially a tutorial. Second is a 1-click 'do it all' utility provided you have access to a Linux or OS X (Mac) host.
https://forum.xda-developers.com/kindle-fire-hdx/general/how-to-root-unlock-hdx-noobies-t3916167
https://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014

DorisSheh said:
Google released Android 10 — the first Android version to shed its letter and be known simply by a number, with no dessert-themed moniker attached — in September of 2019.
Unlike Pie, Android 10 also includes the traditional Android three-button navigation system as an option on all phones. However, if users who want to block ads or extend the battery life try hard to root their Android. KingoRoot on Windows (PC Version) and KingoRoot APK can easily and efficiently root your Android with both root apk and PC root software.
Steps of Rooting Android 10.0 with KingoRoot APK
While before you root your Android 10.0 you need to prepare your mobile for rooting. Device powered on and keep it enough battery. WiFi recommanded. The following steps will guide you to root your Android 10.
Step 1: Free download KingoRoot APK
The download will be automatically started to your Android. Find it in "Download" on your Android phone.If Chrome has warned you about KingoRoot.apk, click OK to proceed.
Root Android 10.0 device with KingoRoot APK
Step 2: Install the KingoRoot APK and install the apk file. *Note: you may receive this install block message. Take the following steps:
Install Blocked: Settings > Security > Unknown sources > Check the box and allow.
Root Android 10.0 device with KingoRoot
Harmful App: Settings > Security > Verify apps > Uncheck it
Step 3: Click"One Click Root" to use the KingoRoot APK. Make sure the network is stable.
Step 4: Result: success or fail.
You may want to try it several times because KingoRoot.apk will only download one script at a time. After doing all above, if KingoRoot APK still failed to root your Android 10.0 devices, hope you have a try on KingoRoot on Windows (PC Version), which has a much higher success rate for technical reasons.
How to Jailbreak Android 10.0 With KinoRoot PC Root
Preparation:
Device powered on.
Enough battery Level of your Phone (above 50%).
Internet connection necessary.
USB Cable (the original one recommended).
Backup everything in your device.
Step 1: Free download and install KingoRoot PC software.
Turn to KingoRoot official website: www.kingoapp.com and download the software for windows. So Internet connection is necessary. After download is complete, install the Kingo ROOT.
Step 2: Double click the desktop icon of Kingo Root and launch it. Kingoroot is 100% safe.
Step 3: Plug your Android device into your computer via USB cable and enable the USB Debugging mode.
Step 4: Click "ROOT" to Begin Rooting
Step 5: Getting the root result. Hope your mobile Running 10.0 can be successfully rooted by the root app of KingoRoot.
Click to expand...
Click to collapse
What is this crap? Totally irrelevant to this device or available ROMs.
Troll elsewhere.