Database Users

Been gone for a few weeks..

Playin w/ roms on my new Rezound... Anyways I noticed the wife's KF got updated to 6.2.2 and FFF/twrp got axed.. Came back lookin for an updated way to get it back quickly. From my last 30 mins or so of reading it would seem the KFU and burritoroot are like fragmented now or something. I tried KFU for twrp and it failed- then I saw there was a burritoroot v3 but it doesn't install a recovery. Just wondering if there's any automated way to get it all done again or if I'm gonna have to keep searchin for links to recoveries etc. If so, no biggie- but if there's an easy way to get twrp back obviously I'll go that route. If there's a thread on it- I must just be missing it- granted I've had a few tonight.

I rooted my 6.2.2 kindle with burritoroot3 and then used KFU to flash TWRP recovery. Make sure you have the updated run.bat found in the KFU thread before trying to flash TWRP

Yep- I found the post from stevenmirabito seconds after posting this damn thread and I've already got twrp back on.. Sorry for the wasted thread.. Still kinda wondering why BR3 hasn't been worked into a new version of KFU but I'm sure if I was really interested enough there's prob some threads on that too- hopefully no drama. Anyways- thanks BluesHawk for responding to my question.
One more thing- I'm assuming it's ok to remove the old burritoroot? Got two icons now

Once you got the burritoroot you may as well uninstall unless your sentimental :_
done and done!

Well- I didn't do perm root- so that I could keep the streaming vid working. I fig'd I'd keep it around though for temp root/unroot

Hag77 said:
Well- I didn't do perm root- so that I could keep the streaming vid working. I fig'd I'd keep it around though for temp root/unroot
Click to expand...
Click to collapse
Unnecessary... Just perm root it and be done with it.
Use OTA Rootkeeper and you will be able to view your Amazon Videos.

Oh ok cool- like I said I've been gone for a while.. Pretty sure last time I was active on these forums OTA RK was a no go for prime video.

It has been the only method that I've ever seen.
o Using OTA rootkeeper use Unroot
o Go to settings -> Applications
o find Amazon Video and force close it
Now run Amazon Video again and it will work. You can even go back and root using OTR Rootkeeper and it will still work until your reboot your device.
This works on the Stock roms... CM7 and ICS doesn't

Cool thx for the info.. Last time (6.2.1) I did perm root, installed market and other apps, FFF&twrp, then unrooted (had to manual delete su files on the device)- so OTA-RK sounds easier. Unfortunately, this is my wife's fire- so I don't get to have that much fun with it. She's way into the amazon ecosystem and likes the stock rom.. So unless ICS final just kicks complete ass- I'll prob have to buy my own to play w/ those roms.. Not even sure why I ended up putting twrp back on it really- I just can't help myself!

krelvinaz said:
It has been the only method that I've ever seen.
o Using OTA rootkeeper use Unroot
o Go to settings -> Applications
o find Amazon Video and force close it
Now run Amazon Video again and it will work. You can even go back and root using OTR Rootkeeper and it will still work until your reboot your device.
This works on the Stock roms... CM7 and ICS doesn't
Click to expand...
Click to collapse
If on CM7, you can leave rooted, use the browser to view Amazon video if you set the user agent to Linux desktop, and that works.

Fire HD 6 Root success with KingRoot APK

Hi!
Today, while doing my daily reading blogs, I found an article by El Android Libre (in spanish) of an app for rooting Android devices quickly, so I decided to try it on my own and effectively, the application success to root my Fire HD 6!. His name is KingRoot. I'm very excited, it worked, and so far I have not noticed errors in the operation of my tablet (at least, today). I could say that this is the ultimate solution to root the Fire HD 6.
WARNING: This is a Chinese application, so I can not guarantee that it 100% safe to use . IF YOU INSTALL THIS, IT IS AT YOUR OWN RISK. I AM NOT RESPONSIBLE FOR BUGS, BOOTLOOPS OR SOFTBRICKS..
Antivirus information:
If the antivirus software on your tablet shows this application as a virus, it is evident: for root you device, this app made a series of exploits to the operating system, and obviously the antivirus will display warnings before or during the process
I hope this can be useful to someone.
(Sorry for my English, I am using Google translator)
UPDATE 12-05-2015 02:01 AM
This process is not yet totally safe and we have very little information. Indeed, it is possible to root the Fire HD 6/7, but there's a very high risk of the device is unable to boot.
Unroot instructions:
Open the KingUser app
Press the Settings button (upper right corner)
Then press the "Remove Permission Root" option
Confirm and wait a few minutes.
Reboot

Yay!!! Thank you for posting this, I will try it now

great news! plz report how it goes thx.

Made a quick vid. Thanks for the info! How to Root Fire HD6: www.youtube.com/watch?v=KcQ30qcImJc

at last my hd6 is rooted now thx

Trying it on my HD7 now. Are we forced to use the king superuser or can we switch to superSu after?

skyhopper88 said:
Trying it on my HD7 now. Are we forced to use the king superuser or can we switch to superSu after?
Click to expand...
Click to collapse
The SU binary will be saved in the /system/bin folder after rooting the Fire HD 6, so I think that while this binary is not deleted you can use any other app for root management like SuperSu.

Suh-weeeet! Can confirm, works on HD7!

Confirmed, my HD6 (well, my mother's HD6) is now rooted :3

I seem to have lost root on reboot though
Or maybe it's because I un-installed the app?
Now to figure out how to get the Play Store working...

dmillerw said:
I seem to have lost root on reboot though
Or maybe it's because I un-installed the app?
Click to expand...
Click to collapse
I restarted my Fire several times throughout the day and still root.
What is the app you've uninstalled?
Here is a screenshot of Root Checker on my tablet right now.

Yeah, it's because I uninstalled KingRoot. Need to get SuperSU in here... somehow

dmillerw said:
Yeah, it's because I uninstalled KingRoot. Need to get SuperSU in here... somehow
Click to expand...
Click to collapse
Well, I try sideload SuperSu directly on my Fire but when I open it, the app ask me to update the su binaries, and a few seconds later shows me an error...
Any suggestions?

Has anyone successfully installed the Google Play Store?

Unfortunately, no. Android root stuff isn't something I'm too familiar with. I think we've still got a long way to go...

So what does the development road look like from here? Do we need a custom recovery before any roms start coming?
Thanks for this, I am excited to get home and play with my tablet!

argrr101 said:
So what does the development road look like from here? Do we need a custom recovery before any roms start coming?
Thanks for this, I am excited to get home and play with my tablet!
Click to expand...
Click to collapse
That's my understanding

argrr101 said:
So what does the development road look like from here? Do we need a custom recovery before any roms start coming?
Thanks for this, I am excited to get home and play with my tablet!
Click to expand...
Click to collapse
merlise said:
Has anyone successfully installed the Google Play Store?
Click to expand...
Click to collapse
dmillerw said:
Unfortunately, no. Android root stuff isn't something I'm too familiar with. I think we've still got a long way to go...
Click to expand...
Click to collapse
It seems you need to install an advanced recovery. The recovery that is built into our Fire does not allow flash apps, only allows to make a factory rese ...
The problem is that if you installed a wrong recovery, can bricking the system. Not sure if CWM Recovery works here.

andersonsalas said:
It seems you need to install an advanced recovery. The recovery that is built into our Fire does not allow flash apps, only allows to make a factory rese ...
The problem is that if you installed a wrong recovery, can bricking the system. Not sure if CWM Recovery works here.
Click to expand...
Click to collapse
I'm wondering how similar this Kindle is to the previous version software wise. Maybe some of the older methods will work now we have root?

This is the situation right now:
It is now possible to root the Fire HD 6 (and 7, as I'm reading)
The root is persistent while you don't uninstall the KingRoot app.
For now, you can not install the SuperSU app (throws an error)
Installing System Tuner Pro gives you the ability to uninstall system applications, review the logs of the kernel, modify the file build.prop, among other things (Other apps can also be used for do this...).
It is not possible (for now) install Gapps until to find an advanced recovery that it works with this tablet. Despite this, you can install some Google apps like YouTube, Google, and Google Search taking an alternative way. Read this thread for more information:
(Yes, there is still road ahead ...)

Amazon has posted the Fire 5.1.1 update for 4th gen Fire Tablets!

OMG!
Amazon has finally posted the Fire 5.1.1 updates!!!
http://www.amazon.com/gp/help/custom...e_sb_swupdates
WOO HOO!

i only just found out this morning that they finally created a successful root for the last update (figures). I woke up and found my kindle with an Android tablet look to this update. How long til this can be rooted? Or does anyone think that the computer downgrade method will still work?

Well, it seems Fire OS 5.1.1 is already rootable with Kingroot, as I just did so successfully not five minutes after upgrading

what version of kingroot would work? i am using a kidle fire hd 6 (4th gen) and ive tried the latest i could find (4.8) and someone suggested i try 4.0, yet both failed multiple times. Oh, and my brother is somehow non-upgraded and is still at 4.5.5 yet i cant root his either.

WaywardOne said:
Well, it seems Fire OS 5.1.1 is already rootable with Kingroot, as I just did so successfully not five minutes after upgrading
Click to expand...
Click to collapse
I am going to update to this version today. Can you please provide me link to detailed steps (video if possible) for me to root and install GAPPs.
Thanks

It's quite simple really, I just downloaded the latest apk from the official website, kingroot.net, and ran it. As for GAPPs, however, I'm not sure which method to use just yet.

But I did too and it failed. I'm using a kindle fire hd 6 (4th gen) and kingroot is proving to be ineffective on all versions available and any competitor rooting systems. All claim it's not vulnerable to root and it fails every time. Sometimes it even reboots, but when I open kingroot, it claims it failed.
Update: just tried it again, failed again. Says it cannot root and that there is no root strategy available. Why am I not able to root?
Update 3minutes later: HFS it worked!!! Idk why it worked now, but thank you!

WaywardOne said:
It's quite simple really, I just downloaded the latest apk from the official website, kingroot.net, and ran it. As for GAPPs, however, I'm not sure which method to use just yet.
Click to expand...
Click to collapse
I used the latest apk from kingroot.net and it failed at %25.
Somehow I able to install google services & playstore without root using this
https://www.youtube.com/watch?v=MgeXdR92Sx0
edit: after reboot and try few more times finally it rooted. Once it pass 25% mark it goes very fast. Yay!!

5.3.1 ROOT! :)

Kingroot now roots 5.3.1!
If you are having trouble installng cm 12.1, try the supertool or @wtfjajaja's instructions.
wtfjajaja said:
try it a few times, i encountered the same problems as well
here's what i did
1. factory reset through recovery
2. root with kingroot, (it worked for me after 2 to 3 tries)
3. installed supersu-me 6.7
4. update su binary
it's important here! don't restart yet, my device bricked few times here
5. install flashfire 0.53
6. follow the steps to install cm12.1 under flashfire from here
7. enjoy
Click to expand...
Click to collapse
Supertool: http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
Bricked?: http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

Fingers crossed! I can't wait to start flashing roms!

If you're root then maybe you can use flashfire to flash a rom just like 5.1.2

tonibm19 said:
If you're root then maybe you can use flashfire to flash a rom just like 5.1.2
Click to expand...
Click to collapse
Flashfire needs supersu
or Cmsu to work.

hooks024 said:
Flashfire needs supersu
or Cmsu to work.
Click to expand...
Click to collapse
Try rootjunky's supertool after rooting to see if it can install it.

.
tonibm19 said:
Try rootjunky's supertool after rooting to see if it can install it.
Click to expand...
Click to collapse
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1

DoctorDark_ said:
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1
Click to expand...
Click to collapse
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.

marvelous news!!!

DoctorDark_ said:
Kingroot now roots 5.3.1! Hopefully someone can quickly push out a toolkit.
Click to expand...
Click to collapse
Would you add the 5.3.1 version in the title ???

tonibm19 said:
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.
Click to expand...
Click to collapse
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.

Nice I will try it out.

Good chance the latest versions of Kingroot (always evolving) will also work for those on FireOS 5.1.2.1-5.1.4. Worth a try before attempting a rollback to 5.1.2.

I couldn't get super sume to work.

not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)

ttcontributor said:
not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)
Click to expand...
Click to collapse
Not good - earlier builds of Kingroot froze around 29% before crapping out. Make sure you have the latest Kingroot app. Also try a factory reset (warning: you will loose personal apps/data) and do not register with Amazon during subsequent device initialization. This proved effective for some in the past. Recognize the community is still learning; expect some failures along the way.

Davey126 said:
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.
Click to expand...
Click to collapse
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.

-Yami- said:
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.
Click to expand...
Click to collapse
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.

Davey126 said:
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.
Click to expand...
Click to collapse
Come check my browser, I've read every single thread on the forums man, the thing is 5.1.2 is not same as 5.3.1 and device has locked bootloader and anti-rollback.
So it is not like my Motorola with unlocked bootloader, I am not sure if I always can save the device and also I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
So I had to make it clear everything works for 5.1.2 also will work for 5.3.1
Now I have to convert kingroot to supersu somehow (can't find the option under supertool like you mentioned.)
Your approach was a little bit harsh on me m8
It doesn't say "What can be done on 5.1.2 also can be done on 5.3.1" anywhere, it says the opposite everywhere.
So someone had to clear it out. Thank you for your help, It really helped me a lot.

-Yami- said:
Come check my browser, I've read every single thread on the forums man...
Click to expand...
Click to collapse
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
-Yami- said:
I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
Click to expand...
Click to collapse
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu

Davey126 said:
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu
Click to expand...
Click to collapse
The reason that I cannot return device to amazon is, shipment will cost more than the actual device from here to amazon, and I got it as a gift.
and Thanks so I missed out the part that Supertool automates the conversion when I click install Flashfire, thank you.
Now after this post everybody jumping right onto 5.3.1 root gonna know it, and the guy on first page have used Super Sume, so he probably would use
Supertool if he knew.

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