yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] Chyron8472:
I was on 5.1.2 already, so I didn't need to downgrade. In a different thread they speculated that the Fire 5th Gen's OTA from 5.1.1 to 5.1.2 confuses Kingroot somehow maybe, and that sideloading a clean 5.1.2 image fixes that.
[Fire Android Development] snark.shark:
It only comes off as "a story" because I edited revisions into the same post. If that was putting people off, I guess I'll have to spread it out in multiple posts instead.
[Fire Android Development] nysom16:
If you updated since the new update came out and didn't check the build version its hard to tell. I'm saying that if you updated in the last few days your build version would read 5.1.2 while it is really 5.1.2.1
[Fire Android Development] kywildcat:
Do i have to re-enable updates to manually update firmware? Will the tool do that for me?
[Fire Android Development] snark.shark:
Okay, finally got around to trying to fix the rooted 5.12 5th Gen device I mentioned here that got into that endless booting loop. Discovered that the situation was not quite what I'd thought.

Even before I'd gotten a chance to try and restore from the Recovery Menu, it booted successfully. The caveat is that my Wifi was off. The unit still appeared to be properly rooted.

The kicker is that the moment I put my Wifi on and it detected it, the animated Fire logo came up (it just jumped to it right from the middle of doing something else). It was stuck there until I held down the power key, then I went into the same endless looping of "Optimizing system storage and applications" I noted the other day.

In the worst case I now know I can do an ADB restore, and/or put a custom ROM on or a bunch of other options, but since I vaguely recall reading at some point about a similar problem to this (but I don't remember the details) I'm wondering if there's instead simply a way to fix this specific behavior/problem.

Pardon me if this description is too long. I was told the other day I'm boring people. :)
[Fire Android Development] DB126:
You can either re-enable OTA updates with the SuperTool or sideload higher versions of FireOS via the stock recovery menu. Make sure you understand the implications. You will likely loose root after updating and may not be able to reroot.

---------- Post added at 09:23 PM ---------- Previous post was at 09:11 PM ----------

Given you do not know what else has been compromised I would reload 5.1.2 to provide a 'clean' foundation for further tweaks and/or flashing a custom ROM with Flashfire. I know of no fix for the WiFi boot loop although suspect it is related to a botched attempt to block OTA updates.
[Fire Android Development] kywildcat:
thanks, just updating to 5.1.1, I'll have reroot
[Fire Android Development] DB126:
If your device is currently on 5.0.1 and you have any thoughts of installing a custom rom in the future you may want to take a different approach to the 5.0.1- >5.1.1 update. 5.0.1 is somewhat magical it supports 'special' commands that simplifies installing a custom rom. There's no going back once you upgrade FireOS using the standard method. Magical powers are gone; midnight for Cinderella.

Downside of the alternative upgrade method is it is a bit technical and involves a few more steps. Post back if you are interested in going this route.
[Fire Android Development] kywildcat:
Thanks, and yes I'm interested for sure. Only upgrading because I have some connection issues, heard google services and amazon might conflict and cause my issue. My 5.1.1 tablet has 0 connection issues. I'm going to try freezing all amazon crap first and see if that helps
[Fire Android Development] DB126:
Procedure is detailed in this thread (post #1). Take a peek and post back any questions.

http://xdaforums.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594/page14
[Fire Android Development] snark.shark:
I have a feeling I know what caused the problem/was compromised after looking at it again. I wound up picking the option in the Recovery Menu to wipe my data. Then, immediately after, I hooked my USB cable back up (Wifi off the whole time), and re-ran the whole rooting routine (including all of the optionals, like OTA blocking) from the start again. Paying much closer attention this time.

When you run a lot of these routines you get pop up messages for approval on the Kindle end. They don't stay up very long though. It seems I must have looked away the first time I did this and missed one of them going on and back off the screen somewhere in the process. The rooting clearly did work, even that first time, but the OTA part must be where I missed an approval. It must have then tried to OTA update, and that's what toasted me and put me into that bootloop/wifi detection crisis.

It's only been a few days though, so I guess only time will tell (it took a few days to break last time).

Worst case I will do the whole thing again and abandon FireOS totally. Best case, I'm properly rooted and blocked this time and only have to worry about alternate OS installs if I get fed up with the FireOS performance (I'm not really). I actually heavily use my Fire for gaming, so the sound issues people have described on the custom ROMS are an issue for me.
[Fire Android Development] DB126:
Good info - thanks for the follow-up. Despite the bad press FireOS is a reasonable skin of Android for the target audience. The performance issues are largely the result of copious Amazon services that load at boot and consume resources even when not used. Most of those can be safely disabled on a rooted device yielding a rom that is as responsive as other skins. If it works for you no reason to change. Sideloading apps is a way around Amazon store limitations. If you prefer automatic app updates considering an alternate app store such as 1Mobile.
[Fire Android Development] StefLeMat:
I´m afraid that I´m on 5.1.1, and it won´t allow me to boot TWRP boot image, right?
[Fire Android Development] DB126:
Correct. No rollback option. You'll need to use FlashFire for now.
[Fire Android Development] Christ_Gj:
Hello !!

I wanna know if I can downgrade my tablet now i think Im running OS 5.1.2.1 Current Version Build 37.5.4.2_user_542169020

I try to root the device but fails at 30% using king root.

Does anybody try to downgrade 5.1.2.1 to 5.1.2 ????

I brick 1 device i dont want to do the same :(

Thanks :)
[Fire Android Development] sd_shadow:
yes, see index

[Index]Amazon Fire 7" - 5th Gen-2015
[Fire Android Development] jco23:
Yes, I did. Follow shadows post/index.

Basically, all I did was sideload 5.1.2, then apply the root batch file from root junky. Did not lose data.
[Fire Android Development] Kodtiz3D:
Trying to root with KingRoot while using this script and it fails every single time, am I doing something wrong?
[Fire Android Development] sd_shadow:
Maybe, which system version?
[Fire Android Development] Kodtiz3D:
Says I have Fire OS 5.1.2. Stops rooting at 30%.
[Fire Android Development] sd_shadow:
That's the system version

did it updated from 5.1.1?
[Fire Android Development] DB126:
Several possibilities:

- device running FireOS 5.1.2.1 or 5.1.3

- device received OTA update bringing it to FireOS 5.1.2

- didn't wait long enough or try enough times (unlikely)

Regardless, you will need to reload a 'clean' copy of FireOS 5.1.2 (that version; no other) which can then be rooted w/Kingroot. Believe there is a how-to posted somewhere in the forum. Grab 5.1.2 from RootJunky's site vs downloading from Amazon as the latter may be 5.1.2.1 or some other unrootable build.
[Fire Android Development] Kodtiz3D:
Yes. Yes it did.

---------- Post added at 02:15 PM ---------- Previous post was at 02:12 PM ----------

Will do. Thanks for your help and also [MENTION=4267571]sd_shadow[/MENTION]
[Fire Android Development] sd_shadow:
you need to reinstall 5.1.2 via stock recovery's adb sideload

http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
[Fire Android Development] jokesonme:
Reinstalling 5.1.2 myself here. Had the same issue bought this for my mom and it updated to 5.1.2 from 5.1.1. and my root was failing at 30% over and over and over and over. Will update after this finishes and let everyone know if it worked!
[Fire Android Development] zerbey:
Did you try the desktop version of KingRoot? I failed in the same spot over and over then finally succeed on the second try with the desktop version. Also, do it from a clean factory reset state.
[Fire Android Development] Tomsgt:
OP updated
[Fire Android Development] sd_shadow:
also

if device updated from 5.1.1 to 5.1.2

rooting will fail (at 30%)

restoring 5.1.2 in recovery with adb sideload

rooting can then be successful
[Fire Android Development] DB126:
If not already changed recommend (strongly) the version of FlashFire installed by the SuperTool be updated. Some posters report the ST installs v0.30 which has several nasty behaviors in addition to sharing its predecessors tendency to destroy access to the stock recovery partition on this device. v0.31 addressed both areas. Suggest going with v0.32 which has proven stable/reliable on this device. It is also the (production) version posted to the Play Store as of this posting.
[Fire Android Development] Amazonfire123123:
When I turn on 'Amazon-fire-5th-gen.bat' It automatically shut off. I tried several times but it still doesn't work. I checked adb .....
[Fire Android Development] gad42000:
help.. my table it locked on the screen.. loading fire . please wait.

its rooted fffrom 500

any ideas?
[Fire Android Development] DB126:
Details? FireOS version? What were you doing just prior? Tool used to root?
[Fire Android Development] gad42000:
My fire was successfully rooted months ago. From 5.0.0 tool used to root was rootjunky.

it is regular fire software with updates disabled. Updates were disabled with root junky and renaming file.

Last I remember is I was watching videos on it with bs player.

remember charging it and turning it off.

Message now states.

Fire is starting. Please wait.

Any ideas?
[Fire Android Development] Tomsgt:
extract the tool to c drive on your desktop and try again
[Fire Android Development] RusTachio:
I too had the issue with KingRoot failing at 30%. I did an adb sideload for the stock 5.1.2 and then re-ran the super tool. Everything is rooted and I am happy!
[Fire Android Development] gad42000:
I turned the network off and it booted after a few minutes.

Will try tomorrow with the network on.
[Fire Android Development] Noleafclover1337:
play store issue

Need some help if possible. Amazon fire 7 2015 - successfully rooted and went through the steps in the supertool to install nova launcher / superSU /play store.

However, whenever I open the play store, I am presented with a "authentication is required" error that is persistent. So.. I can't access the play store. Tried rebooting / uninstalling and reinstalling play store / restoring and re-rooting without any luck. Any suggestions? Thanks in advance!
[Fire Android Development] asmad:
Have you tried installing a different Play Store. Apk
[Fire Android Development] Noleafclover1337:
Not yet. Good Idea, will look into that tonight. Thanks!
[Fire Android Development] Kodtiz3D:
I'm unaware of how to actually sideload a .bin recovery file, my PC isn't the definition of fast and runs Vista. So...
[Fire Android Development] sd_shadow:
click the link above, thread has written instructions and link to a video

---------- Post added at 10:50 PM ---------- Previous post was at 10:49 PM ----------

Vista will be fine
[Fire Android Development] Kodtiz3D:
Tried to get latest USB drivers (Because Vista) from Rootjunky's site and Windows says that the exact folder location doesn't contain 32-bit drivers.
[Fire Android Development] sd_shadow:
Download kindle_fire_usb_driver.zip from Amazon site

Connecting Your Fire Tablet for Testing or XDA

extract files

run KindleDrivers.exe

Then manually select drivers

Open device manager Settings>Devices>Device Manager

Connect Kindle Fire

Enable USB debugging

(If Kindle is not listed as Android>Android Composite ADB interface)

select Other Devices>Fire

Right Click>Update Driver Software

Browse my computer for Driver Software

Let me pick from a list of drivers on my computer

select Android or Android Phone (or ADB Interface or Android Device)

Select Android Composite ADB interface for Stock rom or recovery/adb sideload

Select Android ADB interface for Fastboot mode

or Android Composite ADB interface

next

you may have to reboot pc
[Fire Android Development] Kodtiz3D:
Thanks, will do.
[Fire Android Development] Kodtiz3D:
Well, now I have root but I can't put widgets on the Nova Launcher, and that it needs to be a system app. How do I make it a system app? And yes, laugh at my noobish-ness.
[Fire Android Development] brchickery:
I had to wipe and sideload update-kindle-global-37.5.4.2_user_542168620.bin to get the tool to work. After that I was able to run the tool a few times and it finally worked.

Thanks!
[Fire Android Development] Robo-rooter:
If you are using the Nova launcher with the original Fire OS, you can't add widgets. It just goes to the Fire OS settings screen when trying to add a widget in the Nova launcher, instead of popping up a confirmation window to add the widget within the Nova launcher. I tried making the Nova launcher a system app within the Fire OS using Titanium Backup, but it still couldn't add widgets, even though the Nova launcher had been made a system app.

The only way I could finally add widgets in the Nova launcher was by getting rid of the Fire OS original rom and loading the Nexus rom. I have done this on 3 Fire 7 (5th generation) tablets (that had 5.1.2 firmware). All work great. I used FlashFire v.031 and the 20160420 Nexus rom. Search the xda site for the Nexus rom/Fire tablet thread.

The Nexus rom gets rid of all the Amazon stuff and loads a generic Android 5.1.1 Lollipop OS. It looks exactly like the Android lollipop 5.1 menus on my Lenovo Tab2 A8-50 tablet. It works just as fast as my Lenovo tablet also, once you get rid of all of the Amazon bloat from the Fire 7 tablet. The Nova launcher can be installed after loading the Nexus rom. It allows you to add widgets. However, the Nova launcher does not support live wallpaper.
[Fire Android Development] DoLooper:
Launcher has to be installed to /system/priv-app with perm changes for widgets. I believe the SuperTool will do this. So, you could uninstall the Nova you got, then reinstall with the Nova option in SuperTool.
[Fire Android Development] ShanMan14:
I installed the 5.1.2 .bin file, was able to use KingRoot to root it. I installed Nova (after editing the Suptertool .bat files) but I really want to run a custom ROM. I went through this with another Fire and I'm running CM12 on it. This newer one, every time I attempt to run a custom recovery via adb it fails.

Flashfire says, "Root access could be acquired".

What am I doing wrong?
[Fire Android Development] Kodtiz3D:
Well now it's booting up and going to the lock screen and booting once more, and that repeated until my Fire ran out of battery.
[Fire Android Development] hadlock:
Ok so the current root method is (I think?)

ROOT -

Downgrade/sideload to firmware v5.1.2 - http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

Download Supertool/Setup ADB - http://xdaforums.com/amazon-fire/de...rtool-root-t3272695/post64351795#post64351795

Run Supertool/Kingroot

UPGRADE -

Install Cyanogenmod 12.1 (i.e. Android 'L' or 5.1.x) firmware (no Amazon) http://xdaforums.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416

Thanks to everyone in the whole ecosystem that makes this work properly. Amazing.
[Fire Android Development] wulfie66:
if you're on 5.1.1, then there is no need to update, just root it
[Fire Android Development] Afrodelix:
Please help with GEN5 Device Drivers!!

guys guys guys I need some help. I have problem installing my Kindle Fire Gen5 5.1.2 into my device manager.

Fire is recognized in any mode, inclucing ADB mode when system is loaded. Problem occurs when I go into stock recovery and try to do ADB sideload, my device is being recognized as KEFOWI and cannot install any drivers for this.
[Fire Android Development] CAL7:
Deleted.
[Fire Android Development] asmad:
Why not install a custom rom. Then all the Amazon stuff will be completely gone.
[Fire Android Development] CAL7:
Would love to. Tell me if I'm wrong, but I believe only the Fire HD 7 has a custom recovery and ROMs. Mine is the Fire HD 10.
[Fire Android Development] asmad:
Wrong forum then. This thread is for the 7" tab.
[Fire Android Development] ironia.:
supertool works also on 16 gb version??

tnx
[Fire Android Development] SnoopyDH:
Yes Supertool will work on 16GB version. You can also install a custom ROM like nexus
[Fire Android Development] blazinandroid1:
I did the root tool. Asked me to install kingroot. Open the kingroot app on the tablet. Got a fail. 5.1.2. Anyone else having this problem. I reboot the device twice and tryed it again.. its a no go..
[Fire Android Development] DB126:
Likely have 5.1.2.1 which can not be rooted. Need to sideload 'pure' 5.1.2. Look back through thread or see below:

http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485/post62986665
[Fire Android Development] kgiff:
I started my rooting journey at about 9am my time. After much research I assumed it wouldn't take this long. it is now 5:30pm my time, I have factory reset at least 4 different times and i still cannot get Kingroot to root my device. I am officially at a stand still. I have also checked and I am running fire OS 5.1.2

---------- Post added at 01:06 AM ---------- Previous post was at 12:31 AM ----------

edit: I guess the 5th factory reset did the trick.... weird.
[Fire Android Development] geminiknight409:
Where would one look to see progress of perhaps a MM 6.0 for this "tablet"? I am a noobish, but have successfully flashed 3 KFFOWI.
[Fire Android Development] DB126:
Won't happen with locked bootloader. So far no success in unlocking.
[Fire Android Development] sd_shadow:
if Amazon updates stock kernel to 6.0 compatible maybe

but that likely won't happen for another 6 months or more.
[Fire Android Development] geminiknight409:
Thanks for that.
[Fire Android Development] bvbull200:
I'm at a standstill. I can't get this thing to root. I am trying RootJunky's method and when I get to the point that I have to run KingRoot, it gets to 29% and then fails. I have side-loaded the recommended firmware (in case I had 5.1.2.1) and it did something as KingRoot started getting further before failing, but it did not solve my problem.

Are there any suggestions for other How-To's I can try or other methods to get this thing rooted?

All input is greatly appreciated.
[Fire Android Development] sd_shadow:
factory reset and/or

re install 5.1.2 again
[Fire Android Development] bvbull200:
I'm on my 6th factory reset and 4th reload of 5.1.2. Are there other root methods available? RootJunky/KingRoot does not appear to actually work.
[Fire Android Development] BRANDENDEUCE:
Try the desktop version of kingroot. I had to do it that way
[Fire Android Development] bvbull200:
How could you tell what you are doing?
[Fire Android Development] Heroxgxdeal:
Thanks pretty easy follow the steps. I recently bought this tablet when it was on sell for $40 it came with Fire OS 5 1 3 installed. So I downgraded(To 5 1 2) first the follow steps to root and all the other good stuff in video/texts. Thank you again. :)
[Fire Android Development] bvbull200:
I've updated the drivers (the supertool verified that ADB and fastboot drivers are correct), I've downgraded to 5.1.2 on 5 different occasions, I've done numerous factory resets, and nothing I do gets me passed the step where I'm supposed to run Kingroot from my device. Right as it hits 30% it fails. Every. Single. Time.

It was recommended to try the desktop version of Kingroot, but it is in Chinese and I don't know what in the hell I'm clicking, so that is out.

Are there any other root methods available? The one from this thread clearly doesn't work for the Fire that Amazon is now shipping and the tutorial is invalid given that it just turns over the task of rooting to an app that doesn't work (no mention of Kingroot in the PC version of the tutorial). All I heard was how easy the Fire is to root, so I gave it a shot. Damn thing doesn't work, though. Out of ideas from my end.
[Fire Android Development] DoLooper:
Are you sure you have OS 5.1.2 installed (build date in device settings=Februrary)? The update file ends in 542168620.bin?

OS 5.1.2.1 (unrootable March build 542169020) and OS 5.1.2 are both displayed as "5.1.2" in settings.
[Fire Android Development] platypoid:
Not sure if this may be an issue for you but when I first started trying to root mine the tool said all my drivers were okay but process would fail at fastboot. I finally did two things that fixed my problems - had more than one adb on computer and updated Andoid SDK - and also had HTC program on computer which I uninstalled - I think that one was interfering with the process. Everything worked after that.

Good Luck !
[Fire Android Development] DB126:
Understand the frustration but the problem likely lies at your end; the tutorial is not "invalid". Try a different host, see how others handled the desktop version of Kingroot, review the method(s) you are using to sideload 5.1.2 and the versions reported before/after downgrading. The failure at 30% is indicative of retaining 5.1.2.1 or 5.1.3. Yes, it possible you are the unfortunate recipient of a newer build of FireOS that can't be rooted or downgraded. So far no one else is reporting that.
[Fire Android Development] djensk:
I'm trying to sideload 5.1.2 and getting "failed to verify whole-file signature" The rootjunky side doesn't provide md5sum (says file size exceeds threshold or something) but this is the md5 of the file I downloaded:

md5sum update-kindle-global-37.5.4.2_user_542168620.bin

5b0dcc957def3accff58bf33794d6d88 update-kindle-global-37.5.4.2_user_542168620.bin

any other places to get the file?
[Fire Android Development] fmc000:
In your PMs :D
[Fire Android Development] djensk:
Downloaded and has the same md5sum as what I got from rootjunky so maybe it is my device is having issues (or I suppose more likely I'm having issues, ha) I'm doing:

1) Boot into recovery mode

2) Select apply update from ADB

3) ' adb sideload path/to/5.1.2.bin from my mac

---------- Post added at 07:39 PM ---------- Previous post was at 06:59 PM ----------

I tried a factory reset. When booted up I see 5.1.2 build date march 31 (versus previously it said sometime in april for the build date) so not sure what is going on. Kingroot continues to not work (and it reports I have 5.1.1 so probaly using the wrong stragy anyway) so guessing I didn't actually get the 5.1.2 sideloaded and it is still really 5.1.2.1 or whatever. Gah.

---------- Post added at 08:10 PM ---------- Previous post was at 07:39 PM ----------

Ok looks like my issue is that the 5th gen hd 8 doesn't like the global update files, I needed the 5.1.2 for the hd 8 https://kindle-fire-updates.s3.amaz...Htn/update-kindle-32.5.4.2_user_542168620.bin md5: 7e82caf7ac0679630fcb245cb79acb15 Found in http://xdaforums.com/hd8-hd10/general/index-amazon-fire-hd-8-hd-10-5th-gen-t3214218
[Fire Android Development] DB126:
Why is this conversation taking place here? 5th gen Fire (7") and HD 8 are completely different devices.
[Fire Android Development] djensk:
Power of google search got me here, presumable with the thread title being 5th gen. I'm now in the fire hd 8 area. Wish this was all just in a wiki vs threads. Anyway sorry for posting in the wrong place.