yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] DB126:
Experiences vary widely; look back through the thread for commentary. If no joy reload FireOS via stock recovery and skip Amazon registration in restart. The algorithm KingRoot uses to find a root solution that works with the target device appears unsophisticated. Supposedly identical devices/configs can take very different paths. Good luck.
[Fire Android Development] Thelgow:
Hey guys, I havent had to root anything in a while so I just want to minimize my bricking chances.

The wife picked up 2x Fire 5th gens and both are on v 5.1.3, but already have a noticed 5.1.4 is ready to install.

So I believe I can use the Supertool to downgrade to 5.1.2, then root it?

How do I go about putting CM or something more normal on it than FireOS?
[Fire Android Development] gtallmadge:
Do not downgrade...you will brick the tablet. SuperTool works with 5.1.3, read the forums. As to what you put on it, again read the forums.
[Fire Android Development] sd_shadow:
5.1.3 and 5.1.4 can be downgraded to 5.1.2

but both should also be rootable now with kingroot
[Fire Android Development] tkr9000:
So as an update, yes i was finally able to get SuperSu installed however the SuperTool gives me this message (View attachment 3932662). As well as opening SuperSu gives the message "The SU Binary needs to be updated. Continue?" however according to the video tutorial it's NOT supposed to give that message. Do i go ahead with the update anyways or did KingRoot/SuperTool mess something up?
[Fire Android Development] DB126:
This is partially correct:

- SuperTool does work on 5.1.3 but capabilities are limited w/o root

- Last I knew KingRoot was ineffective on FireOS 5.1.2.1-5.1.4

- FireOS 5.1.2 can be safely sideloaded on a device running 5.1.3

- KingRoot works on 5.1.2 (also 5.0.x and 5.3.1)

- Downgrading below 5.1.2 will result in a brick

- Alternatively, allow device to auto-update to 5.3.1 which is rootable

---------- Post added at 02:07 PM ---------- Previous post was at 01:51 PM ----------

It appears device is not rooted. Suggest rebooting and then using a root check app to verify root status. App linked below for convenience; there are many others.

http://www.apkmirror.com/apk/jrummy-apps-inc/root-check/
[Fire Android Development] Thelgow:
This is part of the reason I'm finding these threads confusing as there is a lot of mixed info. I was able to downgrade the 5.1.3 fine to 5.1.2. The 2nd one sadly kicked off the 5.1.4 update on its own and was in the process of downloading 5.3.1 when I got to it.

Right now both are on 5.1.2, rooted, ota blocked.

So at least for now I have OTA blocked and can breath for a bit.

I plan to do fireflash next and then cm12.1.

Then I can have my 2013 Nexus back and try and fix it.
[Fire Android Development] DB126:
The forum index is an excellent resource that often gets overlooked.

http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485
[Fire Android Development] gtallmadge:
My fault, I misread your original post and responded with the incorrect information. I apologize. I meant 5.3.1 will now work with SuperTool. You already know and followed the correct advice to downgrade 5.1.3 to 5.1.2. Again, I am sorry for posting the incorrect information and seeding any confusion. My experience with SuperTool and 5.3.1 was great so if the tablet does update before you use it, it will be fine to use SuperTool.
[Fire Android Development] Thelgow:
Not a problem, I made the same mistake. I saw all the warnings for 5.3.1 and thought damn, I got 5.3.1... no wait, 5.1.3, ungh.

And reread everything to make sure. But some threads are a bit like facebook with the chronology all over the place.
[Fire Android Development] DB126:
Hey - we're all human and make mistakes. Reasons vary but usually the poster is simply trying to help another member of the community based on their understanding of the question/situation. What's important this we all keep helping each other and (gently) correct errors when encountered.
[Fire Android Development] blackwrx02:
Is there any hope for rooting Kindle with 5.3.2.0 on it? I was going to root it tonight when I got home. Came home to find that it had updated itself tonight from 5.0x. Incredible timing. Thanks amazon....
[Fire Android Development] DB126:
Please don't cross post. Against forum (XDA) rules and annoys the residents. Answered in other thread.

If blessed with a 5.0.x build WiFi should have been off (ie: network isolation) until rooted and OTA blocked. Tough break but not a complete disaster.
[Fire Android Development] julianporter5:
I have a couple of questions:

1) I want to Root and block OTA just to keep my options open for a custom ROM at a later date, but not now.

Should I be worried about leftovers from Kingroot/Purify if I am leaving the original ROM on the device?

2) I can use the Windows or Mac version of Supertool. Seeing the comments about versions and file name issues, which one is likely to give me least problems?
[Fire Android Development] DB126:
Given source and reported behaviors (which likely contain a healthy dose of FUD mixed with fact) I would not leave either on a device longer than necessary. SuperTool automatically removes KingRoot detritus and installs SuperSU with no apparent side effects. What's not to like?

On a personal note I used a recent stand alone version of KingRoot (skipped Purify and other suggestions) on a stubborn but stable, non-Amazon device. Has never been the same since. Play Store busted, downloads busted, unable fully uninstall KingRoot or transition to another root manager (SuperSU). It's a mess. This is a low-end gadget with no custom roms or capability to reload stock. Probably end up in the dust bin. Admittedly a single data point but left a bad taste.
[Fire Android Development] rainer303:
Kingroot.apk could not exchanged with supersu

Hello,

sorry, i am new in rooting with supertool.

I downloaded the latest supertool an I tried to root my Fire 7 with Version 5.1.3. First I made a downgrade to 5.1.2. Success.

I startet the supertool and try to root. When it's installed Kingroot i got the error "invalid Kingroot.apk".

I found out that there is no Kingroot.apk in the folder of Supertool. I downloaded the latest Kingroot.apk from the internet and renamed it in "Kingroot.apk".

Than Supertool install Kingroot and I got root on my Fire device.

But than Supertool wants to exchange Kingroot with supersu. That fails. It cannot uninstall Kingroot.

Do I have a wrong Version of Kingroot?

Best regard (and sorry for my bad englisch :rolleyes:)

Rainer
[Fire Android Development] DB126:
Most likely downloaded the a recent version of KingRoot (v5.x) which can not be uninstalled with the SuperTool. Try uninstalling/unrooting with the option from within KingRoot. If successful download KingRoot v4.9.x and try again. Note SuperSU is a FlashFire prerequisite which itself is a prerequisite for installing a custom rom.

If KingRoot will not uninstall you will need to reload FireOS 5.1.2 or 5.3.1 via the stock recovery menu.
[Fire Android Development] skypirate123:
FireOS 5.1.2 here~ (perhaps 5.1.2.1 is causing these issues? How can I check?)

I've also been running into issues uninstalling 4.9 KingRoot via SuperTool then getting 2.78-SR4 SuperSU installed. It won't complete any of those actions.

Have tried to manually complete the process however upon verifying the root on Root Checker I get:

Stage 3 - Root User Account: Error pops up.

Error stderr: ... Connection to ui timed out, stdout: nuell, exit_value: 0

This error on Root Checker did not occur with KingRoot installed so a bit miffed where to go from here so I can get FlashFire working then install a custom rom.
[Fire Android Development] DB126:
Most expeditious path is to sideload FireOS 5.1.2 via the stock recovery menu. There is not an easy mechanism to distinguish 5.1.2.1 from 5.1.2. Even if you have 'vanilla' 5.1.2 the issues you are experiencing point to a FireOS reload as the remedy.
[Fire Android Development] hoverman1992:
So last night, I bought a fire 7 5th gen with 5.3.1 out of the box. I was able to use supertool to root it successfully. I then flashed CM 12.1 and gapps. However, the Gapps version I downloaded was the wrong one so it caused some problems, and I couldn't flash again. I sideloaded 5.3.2 and returned it to the store, exchanged for a new one also on 5.3.1. ADB is enabled on the device and allowed for my computer. The drivers are good on Win 10. Now when I launch supertool, it says "cannot find the specified path". Any idea on what to do?

EDIT: Nevermind! I don't know what was different, but this last time I launched the supertool, it finally worked. Rooted and on my way to CM 12.1.

2nd EDIT: Just want to point out that the apk file name for flashfire is wrong. Supertool looking for flashfire-v0.53.apk, however the file in the folder is missing the v.
[Fire Android Development] rainer303:
Hello,

I have try to uninstall Kingroot from Kingroot itself without success. So I begin once again with installing 5.1.2 via sideload. Before that, I made a wipe.

After installing 5.1.2 I downloaded a 4.9.6 Kingroot Version and renamed it in Kingroot.apk.

I use the supertool and try to root it with Kingroot. Kingroot is installed and when it try to root my device it reboot sometimes. After a while I got root access.

But supertool cannot uninstall Kingroot.

So I uninstall Kingroot and SuperSu (it was installed by the supertool). I download Kingroot Version 4.9.2. And after some reboots I got root. But then I got the same messages in Supertool:

Failure [DELETE_FAILED_INTERNAL_ERROR]

Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]

rm: /data/data/com.cafeteam.user: No such file or directory

... and many more.

On my tablet I got the message that SuperSu need an binary update . If I press OK, I got a message to update with twrp/cwm or normal. I choose normal (was it ok?). After a while a message occurred that an other superuser application is installed and I can uninstall them. But it fails.

What I am doing wrong?

Make it sense to upgrade via sideload vom 5.1.2 to 5.3.1 and try again?

I hope we (or you... because I am a noob) can solve the problem. The device should be a christmas gift to my daughter :D.

EDIT: With Kingroot V4.85 i had success. SuperSu is on my fire and Kingroot is uninstalled. Now I am going to install CM12

Best regard's

Rainer
[Fire Android Development] skypirate123:
Sideloading 5.1.2 using the downgrade tool from RootJunky. Can't even get Kingroot to successfully root after 10 or so tries...

EDIT: Noticed the Kingroot v4.85 being successful. Huzzah that worked after 3/4 tries. Then actually got SuperSU to update. Finally!

Onto FlashFire and... CM12 I guess :D
[Fire Android Development] DB126:
KingRoot 5.x.x aggressively resists efforts to uninstall while retaining root permissions. Even when supposedly uninstalled disruptive traces are left behind. It would seem some of those behaviors exist in 4.9.x builds as well.

I have seen reports stating 4.9.x (4.9.6 in particular) did not work with FireOS 5.3.x while others don't have a problem. Hard to draw conclusions.

Glad KingRoot 4.8.5 worked for you both! :)
[Fire Android Development] chemie99:
I can confirm. I tried with 5.0 and it would not get removed by Supertool. Uninstalled and re-run with 4.85 and it worked.
[Fire Android Development] phamine:
Can I use this tool to root if the firmware version is 5.3.2.0?

Edit: Found a solution below to downgrade the firmware. The supertool worked and rooted without a hitch.

http://xdaforums.com/showpost.php?p=69657622&postcount=2
[Fire Android Development] singlebyte:
*Bug Report*

Apologies if this has already been reported. Bought a Fire Tablet today for the $33 deal and wanted to get home and quickly root it. When I ran option [5] to install flashify the system failed. Looking at the batch file shows there is a "V" in the file name to flash (but no V on the actual file). Simply removing the "V" from the batch command resolved the failed flash. (I also tried the [9] update)
[Fire Android Development] DB126:
Problem has been reported on numerous occasions as a quick thread search would have shown ( :) ). Several easy to workarounds as you already know. Tool author will like address in a future release.
[Fire Android Development] JBDegriz:
Just received my new kindle fire 7 and set it up unfortunately it updated to fire os 5.3.2. All I want to do for now is remove the lock screen ads, looking through the script it seems you have to root the kindle now before you can do this. Is there no way of removing those annoying ads without rooting? In the old version of supertool (fire os 5.1.1) you could do a temporary root, which I used on my old kindle, is there no way of doing a temporary root with the latest fire os?
[Fire Android Development] Tomsgt:
I figured out the problem with Kingroot 5.0 and why it will not remove Kingroot and install supersu. Basically this version of kingroot installs itself as a device Admin and you have to turn this off after rooting and before continuing the script to remove it and replace with kingroot. To turn off kingroot admin just go into settings then security and device administrator then uncheck kingroot and continue with the removal and replacement of supersu. I am working on updating the script to add this step :) also looking into 5.3.2 :)
[Fire Android Development] chemie99:
That is good to hear...hopefully if we get Kingroot 5.x to root my HD8-2016, your fix will allow a clean uninstall and replacement!

Now....just need that HD8 root....
[Fire Android Development] blacknwhite77:
Thanks for everyone who made this process easy and took the time responding to questions on the thread.

I am new to Android and just bought Fire 7" Gen 5. Used the supertool to complete the rooting.

This is what I did:

1. Downgraded the firmware from 5.1.3 to 5.1.2.

2. Disabled OTA updates

3. Root using Kingroot and installed su.

4. Installed fireflash

5. Used fireflash to flash to a custom Rom (CM12).

6. Enabled user root and rooted again with kingroot and installed su again.

All good now, however, I see online that people recommend having a recovery tool, specifically CWM/TWRP.

I understand that CM12 comes with it's own recovery that is unstable, I already disabled updating the recovery within CM12 but can't find any pointers online on how to install/flash a reputable recovery tool (CWM/TWRP).

Any help is highly appreciated.
[Fire Android Development] DB126:
- can not use a traditional custom recovery with 5.1.2 bootloader (none)

- FlashFire is the only option at present

For the benefit of future readers there is NO NEED TO USE KINGROOT ON CM. ROM comes pre-rooted; simply enable under 'developer options' and reboot. If desired SuperSU (optional) can be installed from Play Store *after* rebooting.

KingRoot is not a benign tool altruistically developed by a bunch of good guys with no ulterior motivation. It is a necessary evil for rooting FireOS and other stubborn ROMs. Do some Googling before welcoming this PoS into the family after installing a custom rom.
[Fire Android Development] blacknwhite77:
Thanks for your reply.

A couple of questions:

1. I am on Mac, is there an alternative for me to be able to boot a custom recovery tool? (Fireboot is a Windows app).

2. Without using a custom recovery tool what are my options to create a Nandroid back up?

3. Without doing Nandroid back up what is another less elaborate or same as Nandroid back up I could do for the device without custom recovery tool on CM12.1?
[Fire Android Development] DB126:
- FlashFire app ... not Fireboot (whatever that is)

- host is irrelevant; no custom recoveries (period, full stop)

- FlashFire has backup options but should not be confused with true nandroid

- above applies to all roms for this device

Footnote: early production 5th gen devices had a vulnerability that permitted booting custom a recovery from Fastboot. Amazon quickly plugged that hole. There is no downgrade path to a vulnerable bootloader; device will brick.
[Fire Android Development] blacknwhite77:
I meant fastboot not Fireboot. My bad.

So you are saying I can use flashfire to boot into a custom recovery without harming the ROM (wiping data...etc)? And then I could do a Nandroid back up?

Also, is the backup using flashfire comparable to a Nandroid backup? Meaning if things got missed up on the device I could restore it back along with it being rooted/all installed apps and ROM?
[Fire Android Development] DB126:
Please reread previous posts; nandroid is not an option.
[Fire Android Development] lensdigital:
Can't root second time

Successfully rooted my 5.3.1.0 tablet via SuperTool (via Kingroot). Everything was good, but then I bricked it wile trying to setup SlimLP. No biggie, restored it via adb to 5.3.1.0 image I got from Root Junky (fire-OS-5.3.1-update-kindle-global-37.5.5.2_user_552153420.bin).

But at this point it refuses to root again... Kingroot tries to root and fails. I'm doing exactly same steps as before. :confused:

Only thing I can think of is that there's something not quite right with .bin image I downloaded, or maybe KingRoot exploit was removed on remote servers?
[Fire Android Development] platypoid:
Many have said it may take several tries to get Kingroot to work for root. I had to restart my fire several times and retry Kingroot to get it to root - and it only did it when I had wifi access. I had that turned off at first because I was afraid of an amazon auto update which you can't disable until you root. Anyway Kingroot finally did it , and amazon update did download but did not install and I was able to complete everything else , remove kingroot and that other program it had put on, and install CM 12.1

good luck
[Fire Android Development] lensdigital:
WOW, I just tried it (for second day) and it worked!!! Thanks! :)

Yes I realized that WiFi needs to not only be on, but after Kingroot reboots tablet it might take a minute to reconnect and you unlock tablet root will fail. So I wait a minute or two after it rebooted and then Kingroot continues (unsuccessfully so far)...
[Fire Android Development] :
Using the latest version w/ matching SHA hashes results in crashes for me... anyone know what's up? The tablet is on FireOS 5.1.2... and this is how far I get before it hangs for a moment before crashing.
[Fire Android Development] platypoid:
Try opening a CMD window and type in adb devices and see if it hangs up there too.
[Fire Android Development] DB126:
- KingRoot must have network access to work

- other thoughts: http://xdaforums.com/amazon-fire/general/tut-fire-os-5-3-1-running-cm-12-1-t3482573/post69905111
[Fire Android Development] amerkiller1995:
Had an issue with the SuperTool failing to replace KingRoot with SuperSu after successful root but didn't manage to grab a screenshot. Rooted another tablet today and here is the error I encountered.
[Fire Android Development] Tomsgt:
I figured out the problem with Kingroot 5.0 and why it will not remove Kingroot and install supersu. Basically this version of kingroot installs itself as a device Admin and you have to turn this off after rooting and before continuing the script to remove it and replace with kingroot. To turn off kingroot admin just go into settings then security and device administrator then uncheck kingroot and continue with the removal and replacement of supersu. I am working on updating the script to add this step also looking into 5.3.
[Fire Android Development] Miiick3y:
Hi, i can't root my Fire, it keeps failing at 27% in Root King.

I'm on 5.3.1.0 what can i do ?

Thanks
[Fire Android Development] DB126:
Please search for related material before posting: http://xdaforums.com/amazon-fire/de...-5th-gen-supertool-root-t3272695/post69905362
[Fire Android Development] rainer303:
Stucks at "patching system image unconditionally"

Hello,

I have a big problem. I tried to downgrade from 5.1.3 to 5.1.2 with the tool "Firmware downgrade to fire os 5.1.2 supertool".

Now since 1 hour it stucks on "Patching system image unconditionally" at 47%.

What can I do?

Is it save to plug off the usb cable from my pc and reboot the device? Any other ideas?

Best regards

Rainer

Edit: I have risked it. I put out the USB Cable and the device turned into Stock Recovery. I try it once again. In about 10 minutes i put 5.1.2 on the decive. Anyway, something went wrong at the first time. So now there is 5.1.2 on the tablet. Now I'm going to root ...

Thank you for reading.
[Fire Android Development] iRub1Out:
Kingroot keeps trying and trying - but never actually roots the tablet on 5.3.1

I have tried rebooting it, reflashing 5.3.1, and other suggestions. Upon opening Kingroot it says root is unavailable, and no matter how many times I run it, it doesnt work.

---------- Post added at 04:23 PM ---------- Previous post was at 04:18 PM ----------

That didn't help at all. Kingroot has network access, mine also keeps failing around 27%, even after reading "other thoughts" - none of which worked.
[Fire Android Development] DB126:
Sorry to hear that. Many (hundreds, perhaps thousands) have travelled down the same road of adversity and ultimately were rewarded. Keep trying. You may have to get creative and try different versions of KimgRoot as suggested.

Remember everything you are doing is a 'hack' and not a commercial offering backed by copious corporate resources. Amazon ain't gonna make it easy.

If joy remains elusive try a factory reset followed by reloading (sideloading) FireOS 5.3.1 for a fresh start. Do not register during initialization or load any apps. Immediately load/run the SuperTool and attempt to root.

Good luck!
[Fire Android Development] iRub1Out:
Thats exactly what I did, factory reset, tried reflashing the stock 5.3.1 image - but Kingroot, versions 4.9.6 and 5.X dont seem to work, I tried the other 3 versions mentioned in another thread to no avail.
[Fire Android Development] DB126:
There's also a Windows desktop version which requires a USB tether and a bit of intuition as the interface is in Chinese. Not that difficult to figure out which button (singular) to tap once the program launches. Available here.

As noted others have climbed this hill. Sometimes rooting is easy, other times a battle of patience. Amazon has a 30 day 'no questions asked' return policy if nothing seems to work.
[Fire Android Development] toronado:
does KingRoot need internet to work?

Got my new Fire. Powered it on and skipped setup and skipped WiFi setup so it's offline. (Enabled developer mode and USB debugging mode.)

Got KingRoot installed on the Fire via SuperTool.

Ran KingRoot and clicked "Try It"

King root shows "Network Error" "unable to get root strategy from cloud"

Do I need to setup WiFi on the Fire for KingRoot to work?
[Fire Android Development] steve8x8:
Indeed, KingRoot already told you so.

This also possibly explains why some attempts work, others take longer ("the cloud" seems to be somewhat inhomogeneous in this respect).

What I haven't figured out yet myself, how to protect the device from receiving the OTA again, it seems to be a matter of speed (the operator's, not the network's). Perhaps there's a DNS trick? (I'm rather uneasy with that part.)
[Fire Android Development] toronado:
Success

I enabled the WiFi connection on my Fire and let KingRoot do its thing. After many many attempts and reboots it finally rooted the Fire!

Somehow I managed to avoid receiving any pushed OTA stuff during the process. And I used SuperTool to disable future OTA updates once the device was rooted and SU installed (and removed KingRoot and "Purify" or whatever it's called). So hopefully, I'm good until I get a custom ROM installed and running.

During the rooting attempts, on the reboots KingRoot would return to that screen again that said "network error, no connection to cloud etc" even though WiFi was already enabled. Pressing the "back" button would usually clear that screen and continue with the rooting attempts.