yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] m00head:
FireOS 5.0.1, 5.1.1 or 5.1.2: Use the SuperTool in the OP and carefully choose the correct options corresponding to the exact version you have.

FireOS 5.1.2.1 or 5.1.3: Download version 5.1.2 from this link and downgrade to it using the apply update from ADB option in stock recovery, then use the SuperTool as above:

https://kindle-fire-updates.s3.amaz...ate-kindle-global-37.5.4.2_user_542168620.bin

The source of the above link is the following page, which I expect they will update to version 5.1.3 soon:

http://www.amazon.com/gp/help/customer/display.html?nodeId=201830180

Do not attempt to downgrade from 5.1.2 to 5.1.1 or from 5.1.1 to 5.0.1 - doing so will brick your device.
[Fire Android Development] GoughGhan:
Thanks, that works for me, I was actually looking at downgrading it to 5.1.2 if it came with either of the other 2, and yeah I read up on the bricking from people trying 5.1.2 to 5.1.1, that suuucks. Your reply just sets in stone what I was thinking about doing. I just wanted to avoid it lol. Thanks again!

I actually used the tool before when my buddy got the Fire 5th gen in January so good thing is I'm already familiar with it :)
[Fire Android Development] m00head:
You will need to root the device first if you want to block ads and OTA updates, but afterwards is it possible to un-root the device using the 'Full Unroot' option in the SuperSU settings before uninstalling SuperSU altogether. The ads and OTA updates will remain blocked if you do this, and it is recommended to un-root the device if it is intended to be used on a day-to-day basis by a non-technical person.
[Fire Android Development] GambitK:
So I rooted my fire a couple of days ago. Blocked OTA updates and removed ads.

Today the tablet starts and shows the lock screen for about 5 seconds, then shows the "fire" words on screen for about 35 seconds and then goes back to the lock screen again and repeats this process.

What's the problem? I can't get inside to check.
[Fire Android Development] Fishman_:
Not sure about this comment.

I was able to root tablet with initial 5.1.2 by supertool. Second device was OTA to 5.1.3. After I downgraded it to 5.1.2 I was not able to root it anymore. (not by old kingroot (481,482), not by new kingroot 485, not by windows version 32).

It is very well mentioned on main post that downgrade from 5.1.x to 5.0.x will cause brick. However it was not so clear to me about downgrade from 5.1.2 to 5.1.1. (could someone make it bold and post on a main post?)
[Fire Android Development] DB126:
Bold post: downgrading from 5.1.2 to 5.1.1 will yield a hard brick. Questions?
[Fire Android Development] GambitK:
Ok, so if I disconnect the Wifi the tablet goes back to working. As soon as it has internet starts rebooting, when it reboots it begins the "optimization of applications" process, goes to the lock screen and keeps rebooting.

I think the blocking of the OTA updates is not working 100% and it is finding the update and when it tries to install it fails, so it tries again and again.

What can I do to try and fix this?
[Fire Android Development] m00head:
How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet by Rootjunky

https://www.youtube.com/watch?v=RQLoH-ahjy4

Ignore the first part about Cyanogenmod, the steps in this video can be done regardless of the ROM you currently have installed.
[Fire Android Development] GambitK:
The thing is, if I disable wifi or move away from my access point(so no internet), the tablet works perfectly.
[Fire Android Development] lambda9876:
Same thing is happening to my Fire. If wifi is turned off, tablet works fine. If wifi is turned on, the tablet immediately enters re-boot, and keeps re-booting, but the instant that I turn off wifi, the tablet works again.

I'm on 5.1.2, rooted, OTA updates blocked, nova launcher, removed ads --all using rootjunky's supertool.

I re-installed 5.1.2 via adb sideload and went through the motions of blocking ads, blocking OTA updates, and installing nova launcher. The tablet works fine for a few days after that, and then the problem with the re-booting starts all over again. I'm using the tablet with wifi turned off for now.

Please help.
[Fire Android Development] ipdev:
You are correct.

I flashed the wrong version to my 8" by mistake and now have a brick.

(That's why you shouldn't flash when you are tired.)
[Fire Android Development] Y314K:
I would recommend not to use this tool on HD10's & HD8's. Other then making sure ADB is working correctly aka Option 1. Even if an option seem to have worked on one of the other tablets. I would only use this tool for HD7's. There are manual ways of doing the same on the HD10 & HD8 thread. The FW might be similar but still different.
[Fire Android Development] ipdev:
I agree. Works great with my 7.

Most options worked with my 8. (Before I killed it by a dumb mistake. - Not related to this tool.)

The only big difference I can tell is that my 7(ford) has a unlocked kernel. My 8(thebes) did not.
[Fire Android Development] snark.shark:
5th Gen with 5.1.2 on it--ADB (from a Windows 10 PC) already working since I had Google Play store installed via a previous version of the Supertool. I decided to finally try and root it (with the most recent Supertool) before the next OS update (I understand a 5.1.2.1 or something like that is coming).

Anyway... it didn't go well. Not as badly as it could have, since I didn't brick... but not well.

ABD was already working as I said. I went to Option 6 (to root the device) then Option 3 on the submenu (telling the script I was using 5.1.2). The whole FASTBOOT stage worked. Then Kingroot seemed to install okay (there was a popup telling me that access to install it was blocked, but it included an option to install it anyway and I did that). The problem was at the next stage. SuperSU wouldn't install. properly. Or rather I again got an error on the Fire with a similar option to overide and install it anyway and the SuperSU icon shows up anyway (and the script deletes all of the Kingroot stuff too, which it sounds like it's supposed to). But the SuperSU doesn't seem to actually WORK even though the overall interface/icon is present. The script has all kinds of errors about certain files being missing, and clicking on SuperSU itself on the Fire opens it and presents the error "There is no SU binary installed, and SuperSU cannot install it. This is a problem!"

Any suggestions?

P.S. - Just double confirmation it didn't work--Flashfire, via it's own install routine--wrote itself onto the device just fine. But when you run it you get the error "Root access could not be acquired. Are you rooted?"
[Fire Android Development] ipdev:
http://xdaforums.com/showthread.php?p=64344114

This worked for my 5.1.1 (ford)

Sent from my SM-T330

http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

Running 5.1.1 (memphis)
[Fire Android Development] m00head:
You didn't say if you actually ran the KingRoot app - just installing it is not enough. This video has a step-by-step guide to using the SuperTool with FireOS 5.1.2, including how to root:

How to root the Amazon Fire 5th gen 7in on Fire OS 5 1 2 SuperTool Mac linux and Windows by Rootjunky

https://www.youtube.com/watch?v=LfxfZkI_l4I
[Fire Android Development] m00head:
Over on the Amazon FireOS 5.1.2.1 has arrived... thread, [MENTION=5698045]GambitK[/MENTION] was able to root after downgrading from 5.1.2.1 to 5.1.2:
[Fire Android Development] DB126:
Ford kernel remains locked. A bootloader vulnerability allowed TWRP to be booted on some early builds but there was no 'unlock' involved.
[Fire Android Development] snark.shark:
I did run it, yes. Sorry for leaving that out. I DID appear to be rooted. SuperSU just wouldn't install properly. It's baffling.

Is there any harm in trying the whole procedure a second time? Will the remnants from the first install mess up the second run?
[Fire Android Development] Robo-rooter:
There is no problem with running RootJunky's SuperTool root option #6 multiple times. I have 3 Fire 7's with firmware 5.1.2. I ran the root option #6 several times on them before I installed roms on them. No harm is done. (For instance, after a factory reset on the Fire OS, I reran SuperJunky's SuperTool #6 to put SuperSU back on the Fire 7.)

You do have to keep running KingRoot multiple times until you get root. Some have had to run KingRoot 10 times, with multiple reboots to get a successful root. Each time KingRoot is run, it reaches a higer percentage, finally reaching 100%.

During the KingRoot tries, don't touch the SuperTool on your PC, just allow the Fire 7 to run KingRoot and reboot itself. Then restart KingRoot, if necessary, on the Fire 7.

After KingRoot reports successful root, THEN press Enter on the SuperTool on your pc to proceed with KingRoot removal and SuperSu install. There are a couple of steps during the SuperSu install you have to respond to, such as picking NORMAL install.
[Fire Android Development] Fishman_:
After downgrading from 5.1.3 to 5.1.2 I was NOT able to root it. I tried each method like 20 times, different versions of kingroot, windows version of kingroot.
[Fire Android Development] GambitK:
After I downgraded, I used kingroot 4.8.2 because 4.8.5 didin't work. It took two tries.

So far I haven't been able to figure out why the tablet starts rebooting itself after getting internet connection. I have almost given up and installing a custom rom.
[Fire Android Development] TruBlaze:
Always fails at ~30%

Should I attempt to format the device?
[Fire Android Development] Robo-rooter:
One of my 5.1.2 Fire 7's gave a little more trouble than the others. I did a factory reset and after that it rooted.

You do this by powering off the Fire 7. Then booting the Fire 7 while holding down the Power and Volume-Down (left side of Vol button) buttons. Don't release the buttons until the "Amazon system recovery" menu appears.

-While holding down the Power and Vol-Down buttons, first the "Amazon" logo appears, then the "Amazon system recovery" menu appears. Using the Volume keys, I highlighted "wipe data/factory reset" then I pressed the Power button to perform the task.

-Then using the Volume keys, I highlighted "wipe cache partition" and then I pressed the Power button to perform the task.

-Finally with "reboot system now" highlighted, I pressed the Power button to reboot the system.

The Fire logo appeared for a few minutes (a bar may appear and a message about updating software might appear). It may take up to 10 minutes to boot.

-Then the Fire 7 Setup screen finally appears. I selected the language and then I connected the Fire to my Wifi (Kingroot needs an internet connection in order to root the Fire using RootJunky's SuperTool). I skipped the portion of the Fire setup that registers the Fire with Amazon.

Go to SETTINGS, DEVICE OPTIONS on the Fire 7.

Tap on the SERIAL NUMBER field 7 to 10 times.

This opens a new field below titled, DEVELOPER OPTIONS. Click on Developer Options. Make sure ENABLE ADB is turned on (switch is to the right and orange color, rather than off and grayed out).

Now the Fire 7 should be ready to run RootJunky's SuperTool again.
[Fire Android Development] TruBlaze:
I tried this...

4.8.2: Fails at 31%

4.8.5: Fails At 29%

Does this mean my Fire is unrootable? ?
[Fire Android Development] Robo-rooter:
I don't know. I rooted mine a couple of weeks ago, before 5.1.2.1 firmware was released. Make sure your Fire 7 does not have 5.1.2.1. That version has not been reported to have a successful root. If you do have 5.1.2.1 you can roll it back by side loading 5.1.2 with adb. People have reported rolling back 5.1.2.1 to 5.1.2 and then successfully rooting.

DO NOT, REPEAT, DO NOT attempt to roll 5.1.2 to 5.1.1 or 5.01 or the Fire 7 will be permanently bricked.

THE ONLY SAFE ROLLBACKS REPORTED SO FAR: 5.1.3 to 5.1.2 or 5.1.2.1 to 5.1.2.

5.1.3 rolled to 5.1.2 REPORTED OK TO DO.

5.1.3 rolled to 5.1.1 or to 5.0.1 MAKES A PERMANENT BRICK. DON'T TRY IT.

5.1.2.1 rolled to 5.1.2 REPORTED OK TO DO.

5.1.2.1 rolled to 5.1.1 or to 5.0.1 MAKES A PERMANENT BRICK. DON'T TRY IT.

5.1.2 to 5.1.1 or to 5.0.1 MAKES A PERMANENT BRICK. DON'T TRY IT.

5.1.1 to 5.0.1 MAKES A PERMANENT BRICK. DON'T TRY IT.
[Fire Android Development] snark.shark:
Argh. Okay, took like 7 runs for me.

Then it asks about Optimization inside Kingroot. I said yes. Should I not have?

Anyway got SU on it and working after that. Ran the OTA block and everything seemed okay--I believe there may have been a reboot around then too. But now I'm in deep. I ran the Ad screen block stage, then rebooted, and now I'm stuck at the Fire loading graphic (the orange animated one). It just sits there forever. Nothing at the bottom of the screen either, so it's literally stuck.

EDIT - Power/Vol Down got me out of that, thankfully. The NEXT boot attempt I get "Optimizing System Storage and Applications" (I never entered any recovery screens).

EDIT 2 - Whew, it worked. That was scary though. I hadn't even known about the Power-Vol trick until I checked here, so the idea of getting stuck on that Fire loading graphic wasn't nice.
[Fire Android Development] Robo-rooter:
You can let KingRoot optimize or not. It will install Purifty if allowed to. Just uninstall Purify later, after SuperSU has removed KingRoot.

The "Optimizing System Storage and Applications" with the "Fire" graphic logo during boot doesn't cause any harm IF you have blocked updates with RootJunky's SuperTool. Just let it run until it boots into the Fire OS lock screen. It might take 5 or 10 minutes.

Personally I would get rid of the Fire OS rom and install the Nexus rom. It is very easy to install, even on Fire 7 with 5.1.2. As long as the Fire 7 is rooted, installing the Nexus rom is really easy. After going to the Nexus rom you don't have to worry about Amazon updates causing trouble any more.

The Nexus rom turns the Fire 7 into a generic Android 5.1.1 tablet. It is very lean and bloat free. After installing the Nexus rom, before adding other apps, I had 5gb of free internal space. Then by loading Link2sd, I installed over 100 apps, linked them to the sd card and still had 3.5gb internal storage free.
[Fire Android Development] snark.shark:
Thanks for the help so far, folks. It's been frustrating but educational.

Hey is there a decent Flashfire tutorial out there? At the very least I want to use it to make a backup to my SD card, but the interface is certainly a bit quirky. Its clear you have to use that Plus button, choose Backup, and then define the parameters (making sure you change the storage location, at the very least) and clicking on the checkmark to confirm. Then, counterintuitively it seems like the activation is actually the button called "Flash"... even if it's actually a backup you're doing. Then it goes to black, runs some scripts, and a RED banner appears at the top of the screen (I think it just says "FlashFire"--but it's literally just a big long red rectangle and isn't touch sensitive to any input, and nothing seems to be running elsewhere.

Am I missing something obvious? I had to reboot when I was sure nothing was happening.
[Fire Android Development] Robo-rooter:
The backup option in FlashFire v0.32 is brand new, I believe. I have not used it yet. I have used FlashFire to flash the Nexus rom onto 3 Fire 7's. Just follow the instructions on the first page of this thread (below link) for flashing the Nexus rom with FlashFire..

flashing the Nexus rom with FlashFire.

http://xdaforums.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714

Here is a link to how I flashed my Fire 7 with the Nexus rom. But now the current Nexus rom is version 20164020. Use FlashFire version 30, 31 or 32.

http://xdaforums.com/showpost.php?p=66267730&postcount=346

-Download the newest Nexus ROM (20160420) from this link:

lp-fire-nexus-rom-ford-20160420.zip

https://www.androidfilehost.com/?fid=24499762636004259

-Download FlashFire v0.32 from one of these locations:

https://plus.google.com/+Chainfire/posts/JQ5iDpM5AZJ

https://play.google.com/apps/testing/eu.chainfire.flash

https://download.chainfire.eu/957/Fl...0420152035.apk
[Fire Android Development] pfoneguy1:
The wife some how messed up the Fire with SlimRom so I reverted back to stock and then just did all the following using the super tool

. ADB driver install and test

2. Install Google play store plus remove ads on some fire os versions

3. block ota updates

6. root amazon Fire 5th gen on android 5.1.1 and below

7. replace stock fire launcher with Nova launcher

8. remove lock screen ads on fire os 5.1.1

So I used my Google account to set it up, so how do I now remove my google account and add the wife's account? I can't find any google account setting to add /delete an account?

I searched the thread and this was asked a couple x with no apparent answer.

Thanks
[Fire Android Development] snark.shark:
Isn't it squirreled away somewhere under the Google Settings (the little blue gear icon)? Which I think you only get after the Play store addition... so you should have it now.

I'm actually asking, not telling, because I seem to recall actually being prompted when I used a Google Play enabled game, and one of the options was to add a different account. So you might try that too--deliberately add/install a game which tries to connect to Google Play. Or if you have one on already that does, poke around in the game menus to find the option to log out and back in to Play. How this manifests in using an email reader, or YouTube, or one of those kind of uses I don't know. I've only been using one Google account on my device for YouTube (so far) and use a different device totally for my email.

EDIT - Oh wait. Try this. It's a WEIRD suggestion, but I feel it should work.

Install the YouTube app, if you don't already have it, from the Google Play store. The bonifide full interface YouTube app from Play, not the stupid browser based one from the Amazon store.

Inside the YouTube App, near the top, there is a little icon that looks like a person's head and shoulders. Click on that. Your Account info comes up. On mine at least, since I'm already logged in, I see my picture for my YouTube ID, my username, and there's a little downward facing arrow next to the username. Press on that little down arrow. A popup appears "Accounts" and includes a little PLUS sign on it's right side. That leads you into dialogues to add an account. My presumption is that this adds it systemwide and not just to YouTube. If I'm wrong about that, all it's cost you is a little time, I think. The handoff IS to full-screen prompts about account details so... that seems "right" to me.
[Fire Android Development] pfoneguy1:
Thanks for the info,

I want to just clear the association with the device on the device.

I was able to clear the account by going to my google devices and removing the device from the list. But....... the device itself is still wanting to use my initial google sign in and on top of that I now have a notification at the top and the drop down "account action required" with my g-mail address that I can find no way to clear?

I hate this POS tablet, was not worth the $40 and should have sent it back when I had the chance! My $50 Freedom Pop G Tab walks all over this tablet and I get free 200/500/500 service to boot.
[Fire Android Development] Pond-life:
If it didn't wipe the system I'm amazed it had room for Gapps, Amazon packed that pretty tight
[Fire Android Development] SalemGDU:
ADMIN?

I didnt need to do anything special it just WORKED for me.>..:D
[Fire Android Development] revdirty:
If i would rather use a google now launcher instead of Nova, can i just replace the nova apk in the folder with the google now launcher apk and swap out the nova apk name with the google one?

With the bat file that is..

or since im rooted can i use some app in the play store to do this without script
[Fire Android Development] blueberry.sky:
Be aware that google now launcher is buggy in FireOS, it's recommended that you keep a 2nd launcher installed / available so that you don't get stuck if google now dies on you.
[Fire Android Development] revdirty:
Yeah i figured that would be the case, i just added the apk to the Priv-apps folder and it gave me the option to switch .. so i have both there just in case
[Fire Android Development] Pond-life:
So best installing now laucher from store after doing the nova and setting it default
[Fire Android Development] revdirty:
what i did was after running the script and getting nova, i DL GNL from the play store but when i went to open it , it told me to goto setting/home to change defaults but of course that doesnt exist in the FireOS so i used and apk extractor to extrack the GNL apk and then a root file manager to move the aforementioned apk to the system/Priv-apps folder where the Nova apk was . Rebooted and then when i unlocked and hit the home button , it finally prompted me to choose which launcher i wanted to use . Keep in mind, im super amateur-ish at this and this probably isn't the best way to go about this, but it worked for me
[Fire Android Development] julianpaul:
I didn't mention this before but I had issues running the previous supertool from a long path. It works fine when run say from the root of a drive.
[Fire Android Development] klsystem1:
I want only to use Menu 8 for changing my launcher. Do I need to root (menu 7) before ? or 1 too ?

Thanks,
[Fire Android Development] Pond-life:
Depends if you have the drivers already sorted as to whether you need 1, you shouldn't need 7 as 8 uses the temp root method anyway.
[Fire Android Development] Tomsgt:
nope root isnt needed to use option 8. but it does get temp root in doing the process.
[Fire Android Development] killa78:
When I try to root, it says error, device not recognised and fails to push any files. Anybody got an idea of how to fix it?
[Fire Android Development] pappasmurfsharem:
Send a screenshot of your CMD Prompt, also which options did you select?
[Fire Android Development] omarblu:
HELP. I cannot install the drivers. im running a windows 8.1 64bit laptop & my fire is running 5.1.1
[Fire Android Development] Killeravocado:
I had the same issue when I tried rooting originally. Luckily, I found this tutorial.

http://www.isunshare.com/windows-8/...gnature-enforcement-in-windows-8-and-8.1.html
[Fire Android Development] Breach:
I did 2, and 8. Both worked.

A set up a second adult account on the tablet afterwards. Nova launcher is working fine, but there is no Playstore in the second account. If I go back to the first account, it's there. I restarted to see if that did anything. Nope. No playstore in the second account.

It's a bug you might want to look into, but for now I just removed the secondary account.
[Fire Android Development] muellerman:
Thank you very much for your 1-click-tool! Works perfectly for me on new Amazon fire tablet 2015 with 5.1.1. Thank you for your work!!!!!!!!!
[Fire Android Development] killa78:
It's working now, I think it was a problem with the older script programme I was using!

---------- Post added at 09:43 PM ---------- Previous post was at 09:24 PM ----------

Actually, another question - How do I know that the Fire has been Rooted?

I went through this tutorial and Installed Google Play, removed Ads, blocked OTA updates and first went through the Root option.

However, when I try to use Root Explorer on ES explorer, it won't let me? In the directory, SuperSU.zip is there though
[Fire Android Development] Tomsgt:
do you have supersu app installed?
[Fire Android Development] killa78:
Nope.
[Fire Android Development] Robo-rooter:
Load the Nexus rom and the Fire 7 turns into a really nice tablet. It's twice as fast as my Dell Venue 8 3830 android tablet and as fast as my Lenovo Tab2 A8-50F tablet. It's a real dog with the Android Fire OS rom however. The Nexus rom gives you a generic, quad core, android 5.1.1 tablet.

Amazon Fire 5th gen AOSP Nexus rom install with Flash Fire app

https://youtu.be/QZjD4ME4wlI