Database Users

[THOR .3.2.5] Root formerly working, now no access

Used towelroot v2 a while back, and root was working. Recently, I started having problems with root, so I downloaded towelroot v3 and still had problems. Root checker sees that su is installed in /bin/ and /xbin/ but has no root access. The SU prompt never shows up for any app. Upon opening SuperSU, it asks to update the binary. However, it will always fail.
Does anyone know what I can do from here?

Factory reset & using HDX tool for next step ...
I think you would to try using HDX tool to root with this version for HDX 7".
Good luck!
http://forum.xda-developers.com/showthread.php?t=2665683

tudt949 said:
I think you would to try using HDX tool to root with this version for HDX 7".
Good luck!
http://forum.xda-developers.com/showthread.php?t=2665683
Click to expand...
Click to collapse
Thanks, but I tried that already and it just directed me to use a different version of towelroot (which I did), same result. I don't understand, I WAS rooted until recently.

When I had this problem - the solution that worked for me was to find a newer version of SuperSU. The version in the store was the same as what was already installed. Go to Chainfire (the creator of SuperSU) web site (http://download.chainfire.eu/396/SuperSU/), download the latest, install and see if that fixes it for you. No promises - but this is what fixed this problem for me. Good luck.
tudt949 said:
I think you would to try using HDX tool to root with this version for HDX 7".
Good luck!
http://forum.xda-developers.com/showthread.php?t=2665683
Click to expand...
Click to collapse

can i root my 13.3.2.5 with Towelroot ??? i fear it will be bricked

I wanted to ask the same thing. Do we have confirmed accounts of the HDX tool http://forum.xda-developers.com/showthread.php?t=2665683&page=18 working with towelroot on an HDX 7" with 13.3.2.5? I really appreciate what they've done with it and it worked flawlessly for me up to 13.3.2.4. But I haven't seen confirmed reports of it for the most recent version that's running on the Thor.

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 4.5.5.2 is out; breaks root; how to block OTA updates

As of this posting two contributors running FireOS 4.5.5.1 reported being upgraded to 4.5.5.2 which breaks root and various side-loaded apps including Google Play Store. It is not known if 4.5.5.2 can be rooted and/or Safestrap v4 compatibility. Those running rooted FireOS v4 should block OTA updates to protect from unsolicited Amazon distributions.
How to disable OTA updates (source):
- Get a file explorer which has root access (I used ES File Explorer because it was already in the Amazon App Store but every other file explorer should work too)
- Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk
- Just rename DeviceSoftwareOTA.apk to whatever you like (Important: After renaming the file mustn't end with .apk)
- Profit! You can now access the internet freely without the fear of evil amazon updates
Edit: OTA updates on FireOS v4.x can also be blocked using the technique described in this post.

Davey126 said:
As of this posting two contributors running FireOS 4.5.5.1 reported being upgraded to 4.5.5.2 which breaks root and various side-loaded apps including Google Play Store. It is not known if 4.5.5.2 can be rooted and/or Safestrap v4 compatibility. Those running rooted FireOS v4 should block OTA updates to protect from unsolicited Amazon distributions.
How to disable OTA updates (source):
- Get a file explorer which has root access (I used ES File Explorer because it was already in the Amazon App Store but every other file explorer should work too)
- Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk
- Just rename DeviceSoftwareOTA.apk to whatever you like (Important: After renaming the file mustn't end with .apk)
- Profit! You can now access the internet freely without the fear of evil amazon updates
Click to expand...
Click to collapse
Which Users? and which apps? Just Google Apps? or are there many that some of us might be using atm ?

DBCAB said:
Which Users? and which apps? Just Google Apps? or are there many that some of us might be using atm ?
Click to expand...
Click to collapse
Ref: http://forum.xda-developers.com/kin...oot-how-to-install-google-play-store-t3339865
Relax - just block OTA updates and put yourself in the driver's seat. Then you get to decide if/when to upgrade, not Amazon.

Davey126 said:
Ref: http://forum.xda-developers.com/kin...oot-how-to-install-google-play-store-t3339865
Relax - just block OTA updates and put yourself in the driver's seat. Then you get to decide if/when to upgrade, not Amazon.
Click to expand...
Click to collapse
Yes I know how to block ota and all but was wondering if the update even exists and what it does , my mother has a stock kindle never rooted etc and hasn't received anything yet, cant find any info on it but ty for reply , and yeah i like being able to control my device , we all should be able to anyway without modifications, we paid for the device should be able do whatever we want.

I am from germany and got the update last tuesday

Kingroot not work on 4.5.5.2
Hi all,
I am new on the forum and very unlucky!
Yesterday my Kindle Fire HDX 8.9" 3rd gen was upgraded to 4.5.5.2 and I decided to try another way to enjoy my Kindle.
I red this forum and decided to install the Nexus ROM.
First pass was to root the device with Kingroot but it doesn't work (ended with error "ROOT FAILED - no strategy now")
So I think that the new version of firmware 4.5.5.2 CAN'T be rooted directly with Kingroot 4.9.6.
Bye
Davey126 said:
As of this posting two contributors running FireOS 4.5.5.1 reported being upgraded to 4.5.5.2 which breaks root and various side-loaded apps including Google Play Store. It is not known if 4.5.5.2 can be rooted and/or Safestrap v4 compatibility. Those running rooted FireOS v4 should block OTA updates to protect from unsolicited Amazon distributions.
Click to expand...
Click to collapse

Tried and retired kingroot 8x. Did not work. What are some other things I can try?

AzizA MeelaS said:
Tried and retired kingroot 8x. Did not work. What are some other things I can try?
Click to expand...
Click to collapse
4.5.5.2 is not rootable at present. Keep trying Kingroot from time to time.

Too late to block OTA! My Kindle Fire 7 HDX 3rd gen updated automatically to 4.5.5.2 and Google Service stops working and could not open Google Play Store, keeps crashing it. Could not login Google account, can't see Google Photos.
Kingroot 4.9.6 failed to root.
Hope can be fixed soon.

mxnerd said:
Too late to block OTA! My Kindle Fire 7 HDX 3rd gen updated automatically to 4.5.5.2 and Google Service stops working and could not open Google Play Store, keeps crashing it. Could not login Google account, can't see Google Photos.
Kingroot 4.9.6 failed to root.
Hope can be fixed soon.
Click to expand...
Click to collapse
At present the only solution is a risky downgrade to 3.2.8 followed by a controlled upgrade to 4.5.5.1. Instructions must be carefully followed to avoid bricking; all personal apps/data will be lost. Consider waiting for a root exploit which could happen tomorrow or never.

Any updates to root 4.5.5.2?

aaronkatrini said:
Any updates to root 4.5.5.2?
Click to expand...
Click to collapse
Best option is to try Kingroot from time to time. The community will only know if someone reports success.

is this bad
I rooted on 4.5.5.1, blocked updates then turned system off. I turned it on in the morning to find it has reset itself. I looked for the update file in /system/priv-app, but it wasn't there. Is this bad?

Android Rom Guy said:
I rooted on 4.5.5.1, blocked updates then turned system off. I turned it on in the morning to find it has reset itself. I looked for the update file in /system/priv-app, but it wasn't there. Is this bad?
Click to expand...
Click to collapse
Obvious questions:
- what version of FireOS does it show now?
- still rooted?

i accidentally update to 4.5.5.2 too from a rooted 4.5.5.1
i'am so frustrate right now as there is no way to root this damn 4.5.5.2 version

n.fajira said:
i accidentally update to 4.5.5.2 too from a rooted 4.5.5.1
i'am so frustrate right now as there is no way to root this damn 4.5.5.2 version
Click to expand...
Click to collapse
You can rollback to 3.2.8 and then upgrade back to 4.5.5.1, root and block OTA updates to prevent recurrence. Also possible to unlock the boot loader which opens the door to all custom roms for this device. Note 3.2.8 rollback carries a risk (permanent brick) if not executed properly. A summary of the procedure can be found here. Make sure you fully understand before attempting. Guessing 50% of those who start end up bricking their device by simply not following instructions.

Davey126 said:
You can rollback to 3.2.8 and then upgrade back to 4.5.5.1, root and block OTA updates to prevent recurrence. Also possible to unlock the boot loader which opens the door to all custom roms for this device. Note 3.2.8 rollback carries a risk (permanent brick) if not executed properly. A summary of the procedure can be found here. Make sure you fully understand before attempting. Guessing 50% of those who start end up bricking their device by simply not following instructions.
Click to expand...
Click to collapse
i'am sorry i forgot to mention my device version is Kindle fire HD 7 soho. i know i suppose to be in other thread. anyway, you think i can follow the steps you mention above?

n.fajira said:
i'am sorry i forgot to mention my device version is Kindle fire HD 7 soho. i know i suppose to be in other thread. anyway, you think i can follow the steps you mention above?
Click to expand...
Click to collapse
Likely not. The specially crafted 3.2.8 rollback image was captured during a brief period when Amazon honored downgrade requests. It is device dependent and would probably brick a HD 7.

Davey126 said:
Obvious questions:
- what version of FireOS does it show now?
- still rooted?
Click to expand...
Click to collapse
Version- 4.5.5.1
Still Have Root after rooting on 31/06/16 with Bigfoot 4.5.0

Android Rom Guy said:
Version- 4.5.5.1
Still Have Root after rooting on 31/06/16 with Bigfoot 4.5.0
Click to expand...
Click to collapse
Suspect reset was random given many days have passed without further consequence.

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.

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