yashsingh1/xdaforums huggingface dataset:
[Fire General] DB126:
Options:

- install FlashFire on CM 12.1 and attempt to reflash GAaps

-as above but flash CM and GAaps at the same time (recommended)

- reload FireOS from then stock recovery menu and start over

For the first option make sure both FlashFire pop-up options are ticked. Otherwise accept all defaults; twiddling options is the fastest path to failed flash. All flashable zips should be located in internal storage, not on the sd card. Can move/delete them later if desired.

Installing GAaps after CM has booted/initialized does not always work. Arm/5.1/nano is the recommended GAaps build. 6.0 will not work.

FlashFire can be obtained from here:

http://www.apkmirror.com/apk/chainfire/flashfire/

---------- Post added at 01:40 PM ---------- Previous post was at 01:27 PM ----------

This technique (ie: booting into twrp to install ROM) only works for early device builds with an exploitable 5.0.x bootloader. Reliable way to bring up stock recovery:

- untether device

- power off (long press power button if hung/looping)

- press <power>+<vol-up> buttons together for 3-5 seconds

- if nothing happens release both buttons and try again

Note: volume-up is the button closest to the head-set jack.
[Fire General] tydell:
Is cm12.1 is rooted after flashing with FlahFire?
[Fire General] DB126:
Yes - root toggle is under developer options located at the bottom of the settings menu. If you do not see developer options tap on build number (under settings->about) 7-8 times to enable.
[Fire General] tydell:
Thanks a lot, now I see it. I rooted successfully my Amazon Fire 7 and flashed it with cm12.1, enabled dev options but didn't saw this toggle :)
[Fire General] critofur:
Root working on Fire HD 8 2016 (6th Generation)?
[Fire General] DB126:
Wrong forum; ask here: http://xdaforums.com/hd8-hd10

tl;dr - no
[Fire General] critofur:
Sorry, I thought this thread was for any of the various Amazon Kindle Fire tablets.
[Fire General] DB126:
OK - can see your point given the generic title (thank Amazon for giving the 5th gen Fire such a generic name).

Anyhow, as you probably gathered no root exploits for the 6th gen HD8. Kinda frustrating as that would be a nice platform for custom ROMs.
[Fire General] chemie99:
I have 5.3.1 and I am running the Supertool. It installs Kingroot and I try to run but Kingroot wants internet access. I have wireless off to stop any Amazon fireware updates. How to use Kingroot without turning on wireless?

(also Kingroot says "KFFOWI System 5.1.1) while it is looking for internet access).

Note I did replace the Supertool supplied Kingroot with the lastest 5.0 from this site.
[Fire General] sd_shadow:
You can run the pc version, and keep wifi off

or

turn on wifi and run kingroot, it will take a little time for update to download, and prompt to install

there should be plenty of time to root and stop the update

dont worry about what version kingroot thinks is on the tablet
[Fire General] chemie99:
I was paranoid so I kept unplugging router during each reboot. It rooted after 5 tries.

However, now I am having issues with Supertool replacing Kingroot - see attached.

(Yes, I had fixed the "v" file naming issue first)

It is failing with those errors on this call:

"files\adb.exe shell su -c "sh /sdcard/mrw/root.sh""

EDIT: I was running Kingroot 5.0 but it seems that is bad (in terms of removing it after) so I uninstalled it, and ran using 4.85 and that eventually worked (after first reboot, Kingroot reported it could not root at all. Ran again and then had success after 1 reboot). Uninstall then seemed to work as intended (did have a "Failure [DELETE_FAILED_INTERNAL_ERROR]" but rest looked good)
[Fire General] bijubiju007:
Hello,

Below is how I got it working:

1. Used supertool from rootjunkie to install kingroot.

2. Once kingroot was installed, I ran kingroot a few times to root (it fails the first couple of times or so, but eventually roots). Also needs wifi connection.

3. Once kingroot said that the root was completed, I uninstalled kingroot from the device using the apps menu in settings.

4. Disabled OTA updates using supertool.

5. Used supertool again to side load google play store, once complete, sign in to google play store and install super su.

6. Once super su is installed open and configure it.

7. install flash fire from PlayStore, I think the current version is 0.53.

8. Open the flash fire app and grant root access when prompted by super su.

9. Follow the steps mentioned in this thread CM 12.1 for Fire 7" 2015 under - Fresh Installation from FlashFire 0.50. Make sure that you move the Wipe step to the top of the order, else the install will fail.

Hope this helps.
[Fire General] chemie99:
I am still having issues and not sure if it is root related.

I ran supertool to switch from Kingroot to SuperSu after root.

I installed flashfire, and then : wipe, RR ROM, Supersu, GAPPS install.

However, google play won't install updates to gapps. I get "error 505" and update fails (Android System Webview, Maps, Photos etc)

I had no issues with last year's Fire 7 so I am wondering if this is root related? I updated Supersu both in playstore and via settings/system/SuperSU right after the flash was done....

Tired to force stop/clear cache on a bunch of google apps but that did not help.

I then went back to 5.3.1 via recovery, and followed steps from [MENTION=4480820]bijubiju007[/MENTION] but the googleplay failed, so I sideloaded supersu instead, but then supersu failed to update itself. I then ran supertool and it got supersu in there (all be it 2.46 vs 2.78). With root again, I redid the whole flash as before but still have the google play errors with the "Android System Webview" failing to update)

Thoughts/Suggestions?
[Fire General] bijubiju007:
I used open Gapps for arm, 5.1 nano when flashing CM 12.1 just check if you have downloaded the right version based on the RR OS and correct architecture.
[Fire General] chemie99:
I had the right ones. I gave up. After re-flashing 3 times, going back to stock 5.3.1, and another flash, it was still broken. I then did the obvious and sideloaded the darn webview which seemed to work. I don't know if the failures will come back which is too bad since this one is going to an 78 year old who will not be able to do anything in the way of troubleshooting with me over the phone. Worst case, I guess google play apps will stay unupdatabled.
[Fire General] bijubiju007:
Let's hope for the best k good luck :)
[Fire General] Luminair:
Device is stuck on "verify root status" after failing to root 3 times. I rebooted after each failure and am using Kingroot installed via AmazonFifthGenSuperTool. Any ideas? I'm concerned since the device states that it has 5.3.2.0 ready to install. It is currently on 5.3.1.0

Edit: after restoring, the first reboot after a failed root attempt also resulted in getting stuck at Verify Root Status. Should I just send this back?
[Fire General] indslycon:
I tried to follow the instructions using the version of KingRoot from post #36 but had no joy with SuperSuMe. However I installed RootChecker and that confirmed I had root access, the problem was that SuperSuMe wasn't requesting it, it was just hanging.

Anyway I eventually used the script in this guide http://missingtricks.net/replace-kingroot-kinguser-with-supersu-superuser-android-guide/ which gave me a working SuperSu, from which I could install FlashFire and then the Nexus ROM. Rather than install a terminal emulator I just pushed the uncompressed files to /sdcard and opened up an adb shell to run it. I recall a few errors but it got me a working SuperSu and Kingroot was removed.

Hope this helps anyone in the same situation.
[Fire General] DB126:
FYI - 5th gen 'SuperTool' offers a simple one-click solution that does not carry the potential brick risk of SuperSuMe and other home brewed solutions. Relevant commands can be extracted from the batch file for those who prefer a more 'hands-on' approach.

http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
[Fire General] indslycon:
I didn't realise it supported 5.3.1, my bad.
[Fire General] wenston:
My tablet has 5.3.1.0, will supertool work with this as well?
[Fire General] TNL4LyfeYT:
5.3.2?

Will it work with 5.3.2?
[Fire General] DB126:
5.3.1.x - yes

5.3.2.0 - no (must downgrade to 5.3.1)

5.3.2.1 - no (no rollback option...brick)

See forum index and other threads for further info as these questions along with downgrade and rooting instructions have been well covered.
[Fire General] kwanbis:
I'm worried because kingroot requires internet on, and I'm at 5.3.1.0... I don't want to upgrade to the latest version! Any ideas?
[Fire General] DB126:
Unless you have a very fast network connection KingRoot will finish before an OTA update fully downloads. Rebooting will discard the partial download. Kill WiFi after securing root and proceed with remaining steps.
[Fire General] theabsinthehare:
I created a thread detailing how to block Amazon updates without root: http://xdaforums.com/amazon-fire/general/block-ota-updates-root-t3496802
[Fire General] snoerme:
Hi!

I tried rooting my fire 7 v5.3.1 with no luck so far:

I was able to install the kingroot.apk (4.9.7) with supertool, but it didn't complete the rooting prozess for several times. It always stopped at 70% and told me there was no root for my device.

I sideloaded kingroot 5.01. This completed the rooting.. erm.. it said it succesfully rooted, but it seems it actually didn't. There's no Su binary. And root checker also says (surprise!) That the device is not rooted.

Any hints?
[Fire General] DB126:
- KingRoot 5.x is problematic as you discovered; difficult to fully remove too

- reload FireOS via the stock recovery menu for a fresh start

- when device restarts do not register with Amazon

- retry rooting with various versions of KingRoot in the 4.x series; users have reported success with 4.85, 4.92 and 4.96

- Kingroot is a necessary evil that is highly unpredictable but eventually gets the job done; just keep trying tossing in an occasional reboot as needed.
[Fire General] snoerme:
finally got it working :)

I used Kingroot 4.9.6.

I guess the problem was the bandwith limitations I set to prevent FireOS from updating via OTA.

First I only allowed 100 kb/s up and downstream. This way Kingroot didn't complain about missing internet connection BUT DID NOT succesfully root. I tryed for more than 15 times.

After I allowed unlimited upload and 500 kb/s download Kingroot did it's job with two attemps.

<3 cm :)
[Fire General] DB126:
Appreciate the notes. For future reference there is misplaced concern about an OTA update sneaking in during KingRoot execution. In the absence of an unusually speedy network connection the frequent reboots that occur during KingRoot runs effectively purge any partial FireOS downloads. I have yet to hear of a device that received/processed an unwanted OTA update while KR was going about its business. Most occur sometime after as folks forget to disable WiFi before blocking OTA updates or flashing a custom ROM.
[Fire General] snoerme:
I actually had the case, that the OTA update was installed while I was trying to root with kingroot.

After a crash caused by the Kingroot app the fire tab bootet 5.3.2.1.

Had to send back my device to get an new one.
[Fire General] DB126:
Can appreciate the extra caution given your experience! Need to keep an eye on that. Possible the FireOS 5.3.2.1 update is smaller than previous Amazon OTAs increasing the chance of a download completing between KingRoot reboot cycles. Also possible KR was responding slowly during your earlier attempts extending the interval between reboots.
[Fire General] iteek:
I have a Amazon Fire HD8 6th gen, runnin 5.3.1.1, will this work?
[Fire General] DB126:
You'll need to give it a try; this forum/thread is for 5th gen Fire owners.
[Fire General] sd_shadow:
https://xdaforums.com/hd8-hd10/general/complete-guide-root-hd7-8-106th-gen-t3545411
[Fire General] ksums:
Your summary is superb!

Your summary is superb! I rooted mine yesterday and flashed customs rom as well. One remark which I would like to propose for my fellow novices attempting the same task -- if you are on a Mac, and in need of a light ADB/Fastboot tool installed, check this link out. This would take care of one prerequisite.

"http://www.androidpolice.com/2017/01/05/google-makes-adb-fastboot-platform-tools-available-without-full-sdk-android-studio-download/"
[Fire General] DB126:
[MENTION=6674393]ksums[/MENTION] - nice find; thanks for posting!

[MENTION=4267571]sd_shadow[/MENTION] - this would appear to be an excellent alternative to Minimal ADB and Fastboot - especially for those on non-windows platforms. Might be worth noting in Index/FAQ pages.
[Fire General] hovenkampsi:
Followed this and was very successful installing custom ROM to my son's new amazon tablet that arrived tonight. Big thanks!!
[Fire General] MrTinkyWinky:
Much appreciated! I successfully rooted my Fire from 5.3.1 and installed CM12.1 and a Gapps package.

I do have a question. The 5.1 Nano package from Gapps does not include Google Play Games, which is necessary for some games on the Google Play store. When I try to download+install it from the Play store, I get a -505 error. Other Google apps like Gmail, Docs and Sheet installed fine, but I can't install Google Play Games. Is there a way I could install it "manually"?
[Fire General] DB126:
Grab a copy from APKMirror: http://www.apkmirror.com/apk/google-inc/google-play-games/
[Fire General] MrTinkyWinky:
Perfect! Thank you
[Fire General] Cloven123:
Just followed these instructions and loaded CM 12.1 but there's no Google Play Store. I'm fairly new to this, could someone give me a hand? Thanks
[Fire General] DB126:
Likely forgot to Flash GAaps. If unfamiliar with that term or where to aquire suggest flashing Nexus ROM instead which includes GAaps.

https://xdaforums.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714
[Fire General] Cloven123:
I'm going to apologise in advance for the noob speak, literally have only just started dabbling in to this.

How do I go about reflashing another ROM? I've tried plugging the tablet back in to the laptop and it isn't showing up.

edit: It's showing up now but when I install supersu it says the binaries can't be updated and Fireflash says device isn't rooted
[Fire General] sd_shadow:
Please don't cross post

https://xdaforums.com/showpost.php?p=73756603&postcount=1250
[Fire General] ultrasoul:
Any reason we can't load lineageos
[Fire General] savvytechwinner:
locked botloader and no root
[Fire General] DB126:
- wrong forum for Fire HD devices which have different root solutions depending on generation and model

- relative to the devices addressed in THIS forum:

>> 5th gen (2015 Ford) running FireOS 5.3.1 and below can be rooted

>> 7th gen (2017 Austin) can not be rooted
[Fire General] N0t_Just1n:
Root Report

I decided to test it out and this is what I've gotten so far. I used kingroot 4.9.6.

Kingroot does successfully root the device. When I first launched kingroot and clicked root it made it about 30%ish and rebooted. After about the third or fourth time I tried it and it successfully rooted.

IMAGE #1

After rooting I am stuck with the kingroot application. I attempted to replace kingroot with SuperSu but have had no luck. The first thing I tried was the Super SuMe application which does not recognize that kingroot is installed.

IMAGE #2

Then I tried using the Kingroot to SuperSU script but still no luck. It can't seem to find the kingroot files it needs to remove. It does successfully install SuperSu but the binary update always fails even after reboot.

IMAGE #3

This has been my experience so far. It is also worth noting that flashfire (both version .50 and .52) close right after opening for me right now.

IMAGES: imgur*com/a/LFK6r

Replace star with period to view images as I cannot post links because I am a new user. Sorry for the inconvenience.
[Fire General] DB126:
Hum...lots of errors. Can you verify device is actually rooted? Try sideloading ES File Explorer (here) and enabling root capability under 'tools'. Does it stick?

Also noted Super SuMe app identifying underlying OS as FireOS 5.1.1. Surprised about that ....
[Fire General] N0t_Just1n:
I definitely have root access. ES File Explorer seems to be working in root mode and Material Terminal works in Su mode.

Super SuMe is identifying the Android OS as 5.1.1 which is what FireOS 5.3.1.0 is built on top of I believe. 5.1.1 does not refer to the FireOS version. I could be wrong but I'm pretty sure that's what it means.

I think Super SeMe is only compatible with Kingroot 4.9.0 and down, but I'm not sure if 4.9.0 can root 5.3.1.0.

imgur*com/a/9brf5

Replace star with period to view images as I cannot post links because I am a new user. Sorry for the inconvenience.
[Fire General] DB126:
Yep - good call on Android 5.1.1; makes far more sense. Pretty sure Kingroot 4.9.0 can not root FireOS 5.3.x. So we may be in a holding pattern until someone identifies a way to reliably remove KingUser. It's a tenacious suite of cruft that will actively reset efforts to uninstall (at least while retaining root) and/or replace with another root manager such as SuperSU. At present all my 5th Gen fires have exploitable bootloaders so I'm not able to do much realistic experimenting (nor really interested in returning to FireOS). In the interim you can do some Google searches and test various published approaches for banishing Kinguser.

No custom ROMs for the moment but root is better than nothing. Don't forget to block OTA updates at your earliest opportunity.

---------- Post added at 04:23 PM ---------- Previous post was at 03:48 PM ----------

Give FlashFire 0.53 (here) a shot making sure to remove older versions and reboot if it fails to open. Surprised 0.52 closes immediately after launch as it is not known to exhibit this behavior. If FF 0.53 does the same thing makes you wonder if something changed in FireOS or (more likely) Kinguser.
[Fire General] -Yami-:
So question how [MENTION=7710797]DoctorDark_[/MENTION] managed to get CM on his device and replaced Kingroot?

We need some information Doc.

I need to change Rom because some weird issues are around my device (such as power off doesnt work), but Don't really want to sideload 5.3.1 all over again.
[Fire General] N0t_Just1n:
Thank you, Flashfire 0.53 opens and stays open. But Flashfire requires SuperSU or CM SU binaries to flash which fails to update because kingroot is installed.

---------- Post added at 08:40 PM ---------- Previous post was at 08:34 PM ----------

He stated that he used Super SuME to convert kingroot to superSU, but Super SuMe says there is no kingroot on my device. I'm very interested to know, [MENTION=7710797]DoctorDark_[/MENTION] exactly what version of kingroot did you use.
[Fire General] DB126:
[MENTION=249875]Yami[/MENTION] - have you tried either Super-Sume or the SuperTool to transition to SuperSU? At present we have conflicting data points indicating it does and does not work. That does not mean one party is correct and the other is wrong. Anyone involved in modding knows app/device/user peculiarities can play a big role in outcomes. Plus the afterthought "oh yeah, and I just ...." quip that provides the essential clue that gets things working! :)
[Fire General] DoctorDark_:
I had just used the latest version from the kingroot website. Although I did notice that sometimes the website gave you the app with a "crown" logo. And other times it gave you the app with a "Lightning bolt" logo. ( I used the "crown" one)

Also, prior to rooting, I had factory reset my tablet and it was not registered.
[Fire General] -Yami-:
No I did not try,

For super sume I've to pay and for the supertool one I really don't want to mess something up.

As I mentioned earlier some stuff are already messed up with my Tablet after rooting somehow when I disabled OTA. (at first I wasnt even able to enter "Settings" now only "Shut Down Device" doesnt work sometimes and works sometimes.

so I don't want to mess it up even more and then have to adb sideload 5.3.1 again and in case of an hard brick, well I cannot send it back to Amazon.

if Bootloader was unlocked, I would have done everything already and submited information.

I used many other devices and bricking them was not an issue but this one, I am really afraid to touch :)

I played with / Fixed many Nvidia Tegras, Samsungs and LGs.

(if I am not remembering wrongly, I had to re-create partitions and then find and flash everything factory puts in to an LG G3 it was totaly bricked but well,

there was fastboot and I was able to flash everything back in.)

So actually this forums (Fire forums) made me a little bit afraid of the Fire, so I try not to play with Fire :p.

edit.

to add, I have the lightning bolt Kingroot on my device.

I may try super sume after all, I'll wait for a while.
[Fire General] WaywardOne:
What is the date on the app you used? The latest version with the crown logo I have is 09_18, called "NewKingrootV4.9.6_C151_B321_en_release_2016_09_18_105203.apk". That one seems like the normal Kingroot app, with the package name "com.kingroot.kinguser", size 14.38Mb, while the newest version I have is 09_30, with the lightning bolt logo, called "NewKingrootV4.9.6_C151_B329_en_release_2016_09_30.apk", package name "com.cafeteam.installer", size 16.20Mb. Perhaps that's why it's not working for me? It seems different from the normal kingroot experience I'm used to as well, especially since it doesn't let me attempt to root my device more than twice before removing the try again button.
[Fire General] -Yami-:
Doc can you upload the APK (kingroot) you used here?

also now I have to figure out how to unroot, Uninstalling kingroot probably works but not sure.

and then get the one you used.

and I have a question

if bootloader is locked and preloader checks for ROM, how do we install CM12.1 using FlashFire?

This method is a method I've never seen on any other device.
[Fire General] DB126:
Understand your concerns. 5th gen Fires are fairly forgiving relative to some other Amazon devices which are easy to bork and nearly impossible to recover (notably locked 3rd/4th gen HDX). Sideloading FireOS pretty reliable. You may have to go that route at some point given what *may* be over aggressive attempts to block OTA update capability. Only one app needs to be renamed: DeviceSoftwareOTA.apk

Realize you have extensive experience with unlocked devices (as do I). Dealing with a locked device isn't so scary once you recognize what is and is not dangerous.

If you're going to try to banish Kinguser I would try the SuperTool first before resorting to Super-sume. The latter is a fine utility ... but why pay?
[Fire General] -Yami-:
if I can use 5.3.1 provided in (5.1.2 to 5.3.1 and keep root) thread to sideload if something goes wrong, I'll give supertool a try.

Btw shut down function works right after I turn the device on, but doesn't work after I use it for a while.

I try to figure out what and why, I amy got infected by something and that prevents me to shutdown.

I am really fine on Android Lollipop and Kinda Like Amazon's Interface but for my sake of mental health, I want that CyanogenMod (even tho I got sick of it because I have it on every device I have, from samsung to lg to Advent to Motorola)

edit:

figured it out, it doesnt shut down if I enter settings so it is probably related to my removal of OTA apks.
[Fire General] DoctorDark_:
Sorry, I already deleted my kingroot apk as I thought there was no use for it :( Perhaps try using an old version of supersume?
[Fire General] -Yami-:
I installed Flashfire through Supertool but it didnt replaced Kingroot nor mentioned anything about it.

I am not sure which menu I should enter.

I said "Install Flashfire for Intalling Roms" (option one)

and it has version .50 and shuts of immediately.

if Flashfire recoginized Kingroot everything would be easier... there must be a reason it doesnt.
[Fire General] wtfjajaja:
http://king.myapp.com/myapp/kdown/i...151_B304_office_release_2016_09_22_105003.apk

use this version of kingroot