yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] pfoneguy1:
Well it is not my device and in the hands of a bigger noob than me with no custom recovery, much better off stock. For the wife it really is just fine stock rooted, but should be some way to remove my google account sign in from this device? Without a factory reset anyway, can I even do that now or will that screw up root and brick this thing?

Thanks.
[Fire Android Development] Robo-rooter:
With the Nexus rom installed, Amazon updates are no longer relevant and don't load. The Nexus rom will not update automatically, either. You have to specifically download an update and flash it with FlashFire. You can do a Nexus rom update to Nexus rom update without erasing user data or apps. So a custom rom recovery is not needed. You can always sideload the original Fire OS rom with adb if necessary and start all over again.

You can run a reset on the Fire 7 from the menu without losing root.

When I had the Fire OS rom on my Fire 7, I went into the Fire 7 setup menu and did a reset.

This will not lose root, but it will erase the Google Play Store and SuperSU.

Then I reran RootJunky's SuperTool. Run #6 root, let it install KingRoot but don't run KingRoot. After the KingRoot app icon appears on the Fire 7, hit Enter on the SuperTool on the pc to reinstall SuperSU and automatically remove the KingRoot program.

Then rerun the Google Play Store install and Nova launcher install if desired. To be on the safe side, also run the Amazon Update blocker on the SuperTool.
[Fire Android Development] TruBlaze:
[MENTION=7388653]Robo-rooter[/MENTION] Do you have any experience attempting to Root with Linux systems?
[Fire Android Development] Robo-rooter:
My Dell laptop has Linux Mint and Windows 10 installed, dual boot. I spend 99% of the time in Linux Mint the past 6 months. But when I rooted, I used Windows 10, not Linux, unfortunately.
[Fire Android Development] m00head:
This is how you do it on a regular Android device, but I'm not sure if it will work on FireOS:

https://support.google.com/nexus/answer/2840815
[Fire Android Development] c0l:
I've 5.1.2 (build date Mar 31st 2016) also but I'm calling no joy on the Supertool (except for loading playstore which is a huge bonus for me).

Sadly Kingroot is refusing to work, even tried multiple factory resets & various versions (incl Kingroot for windows 3.2)

Kingroot 4.9 (the latest) as well as 4.8.5 & 4.8.3 all fail at about 30%.

Interestingly 4.1 gets over 50%!!

Would like to try 4.2 or 4.3 if anyone has a link please? I can't find it anywere.

Guess I'll have to wait & hope the rooting tools are updated before the firmware :/

Update: found a link to previous versions here: kingroot . net/release
[Fire Android Development] gtallmadge:
Rooting with Linux is the same process as for Mac. Rooted mine easily following the guidelines in the video for using SuperTool with a Mac. I use Ubuntu 14.04.
[Fire Android Development] m00head:
Here is a link to the video you referred to:

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] TruBlaze:
I use Linux Mint 17.3 (Basically 14.04) but my device refuses to root.
[Fire Android Development] StefLeMat:
RootJunky,

I bricked my Amazon Fire 5th Gen with 5.1.1. trying to load SlimRom and now it stays in the SlimRom loading logo.

I have FastBoot access, no recovery menu/ADB. I read that latest FlashFire can restore backups thu fastboot. Is there the possibility that you add an option to your excellent SuperTool to restore a stock recovery partition or system?

If I could just load the recovery menu and enable the option to run "ADB sideload OriginalROM" me, and so many in my situation could unbrick so many tablets :)

Or better, if we could restore a backup made with FlashFire of a clean/stock tablet that would be great.

I don´t know if I´m dreaming and the fastboot on 5.1..1 won´t allow anything of this.

Thanks,
[Fire Android Development] gtallmadge:
Am I missing one of your posts? Did you specify where you are specifically having the problem. The more information you provide the easier it is to offer help.
[Fire Android Development] m00head:
Please can you provide some more details. Specifically, which version of FireOS are you currently on (this will determine the the root method you should attempt), and the point at which your device refuses to root?
[Fire Android Development] AeroPilot03:
And another one...
[Fire Android Development] Robo-rooter:
I bricked my 5.1.2 Fire 7 twice trying to load the Slim rom with FlashFire. I recovered it twice and finally successfully loaded the Nexus rom. I used RootJunky's unbrick video instructions:

How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet

https://youtu.be/RQLoH-ahjy4?list=PLaPvcEA8BA-JMmKqiaJvZM93iTyiOAWuK
[Fire Android Development] StefLeMat:
Maybe I was not totally clear about my issue, but unfortunately, I have NO access to the "Amazon System Recovery", hence I cannot select "Apply update from ADB", and I cannot run in my PC "adb sideload OriginaRom.img".

The only function have access to in my tablet is Fastboot.
[Fire Android Development] sd_shadow:
then boot twrp and install stock in twrp

Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
[Fire Android Development] TruBlaze:
I am using KingRoot 4.8.2, and it is always "failing" at 30% (On FireOS 5.1.2). Should I attempt to use an older version or forget about rooting altogether?
[Fire Android Development] m00head:
I was able to root FireOS 5.1.2 using the version of KingRoot that is included with the SuperTool.

Did you try the following suggestion by [MENTION=7388653]Robo-rooter[/MENTION]?

How to Factory Reset the Amazon Fire 5th gen 7in tablet by Rootjunky

https://www.youtube.com/watch?v=ZkNArXhJF8M

Also, the following video demonstrates KingRoot being used. You may have to run it many times, fully closing it each time either by doing a reboot or by swiping it away in the 'Recents' list before running KingRoot again:

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] TruBlaze:
I tried that the previous day, same result both times.
[Fire Android Development] m00head:
Did you downgrade from FireOS 5.1.3 to 5.1.2 at any point?
[Fire Android Development] TruBlaze:
I never got updated to 5.1.3
[Fire Android Development] lambda9876:
I downloaded the latest version of flashfire v0.32 and the latest release of ggow's nexus rom. After installing flashfire, I carefully followed rootjunky's youtube video "Amazon Fire 5th gen AOSP Nexus rom install with Flash Fire app" on how to flash the nexus rom.

Follow his instructions and there shouldn't be any problem.
[Fire Android Development] Robo-rooter:
You might try side loading 5.1.2 through adb, even though that's what's on it now.. A little more radical than a factory reset, but it might work to prompt the Fire 7 to root. Here is a link to a video showing the process.

How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet

https://youtu.be/RQLoH-ahjy4?list=PLaPvcEA8BA-JMmKqiaJvZM93iTyiOAWuK

DO NOT try to side load 5.1.1 or 5.0.1 on a Fire 7 with 5.1.2 or you will permanently brick it.
[Fire Android Development] xda_peteb:
Worked successfully on my Kindle Fire running FireOS 5.1.2

Had to dnload the USB windows drivers from Amazon to install and get my Windows laptop talking to the Fire, then everything was plain sailing.

Follow the Youtube guide carefully, it works.

Big thanks to rootjunky and all who developed this tool....
[Fire Android Development] Tomsgt:
glad it worked for you. hopefully i will be looking into fire os 5.1.2.1 and above soon
[Fire Android Development] pappasasquatch:
Bricked Fire 5.1.1 and 5.1.2

I have 2 bricked Fires. The first was a new 5.1.1 upgraded to 5.1.2, the second was a used 5.1.1. Both bricked when I tried to use Flashfire. RootJunky's video used 24apk and I downloaded 30apk. I bricked the first one because I didn't follow directions fully. I wiped, then went back to load, instead of wipe+Rom+Gapps all in one action. Don't know what went wrong with the second one, but 30apk has different choices than 24 and I must have guessed wrong. I unbricked the first one with Soupkit, and am currently trying to unbrick the second. Not ready to try to reflash ROMs yet.
[Fire Android Development] TruBlaze:
Though unrelated to the thread, does anyone have any Idea how to get ADB 1.0.32 onto a Debian-based machine?
[Fire Android Development] gtallmadge:
This link should help: http://www.linuxslaves.com/2015/07/install-android-tools-adb-fastboot-on-ubuntu-linux.html
[Fire Android Development] Robo-rooter:
Slightly off topic, but...

I just used RootJunky's Amazon Fire 5th Gen SuperTool (April 6, 2016 version), JUST AS IT IS, to root my Tracfone LG L22C Power. With only a couple of mouse clicks.

Even if you are already rooted with KingRoot, you can use this tool to uninstall KingRoot and install SuperSU. (Just run the tool, let it re-install KingRoot, don't run KingRoot but hit Enter on the SuperTool to then uninstall KingRoot and install SuperSU).

Tracfone LG L22C Power info:

Model Number: LGL22C

Android version: 5.0.1

Kernel version: 3.10.49

Build number: LRX21Y

Software version: L22CV10a

The SuperTool batch file script rooted the phone with KingRoot and then uninstalled KingRoot and installed SuperSu.

I have since installed ES File Manager, Titanium Backup, Link2sd on the phone. Root is totally working. Rooted with only a couple of clicks!

Just enable Developer options on LG L22C (by tapping phone Build Number 7 to 10 times [Settings, About Phone, Software info, Build Number (tap 7 to 10 times)]), enable USB debugging on L22C in the Developer options settings.

Connect L22C to Windows 10 with a USB data cable (I used the USB 2.0 port). When screen message on the L22C mentions MTP mode, tap that and change to PTP mode on the phone.

Install RootJunky's SuperTool to the Windows 10 desktop.

Run RootJunky's SuperTool (Amazon-Fire-5th-gen.bat) You may have to read the instructions on the pages below and install adb drivers. Pick option #6 Root. Choose Option #3: version 5.1.2.

Press enter and KingRoot will be installed on the phone from the SuperTool. (approve any messages that appear on phone screen) Now don't touch the PC SuperTool until the phone is rooted.

Open KingRoot on the phone and run it. You may have to run KingRoot several times and the phone may reboot. Just keep running KingRoot until the LG L22C is rooted. After KingRoot reaches 100%, then press ENTER on the PC.

The SuperTool will now uninstall KingRoot and install SuperSU on the phone.

Choose NORMAL SuperSU install on the phone when prompted. When SuperSU is installed, reboot the phone. Disconnect data cable.

After reboot the LG L22C Power is rooted. There will be a request by SuperSU to upgrade. Approve it. You can now install Titanium Backup, Link2sd, ES File Manager, etc. Your phone is rooted. As easy as that. THANKS ROOTJUNKY!!!

Info and links to Download RootJunky's SuperTool at these pages:

Amazon Fire 5th Gen [SuperTool] Root, Google play install, block ota updates and more

http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695

"AmazonFire5thGenSuperTool.zip" 2016-04-06 version

http://rootjunkysdl.com/files/?dir=SuperTool
[Fire Android Development] pvsgh:
Used this tool to root the Fire, worked perfectly. Great job mate :good:
[Fire Android Development] Tomsgt:
yeah i have used the tool to root many other device as well by using the root option then select the fire os 5.1.2 option. basically if you can root with kingroot you can root your device with this option in the Supertool :)
[Fire Android Development] TruBlaze:
Since the version provided nor its updates work on my fire, should I just give up on this?

(Note: I already have ADB enabled)
[Fire Android Development] pfoneguy1:
First thing I did, but all it offers is to register with Amazon?

[MENTION=4246643]Tomsgt[/MENTION] how to remove google account on the 5th Gen? I can remove it from google list of devices, but then I get a constant notification in the notification bar and pop up to re sign in to my google play account with no way to clear it?
[Fire Android Development] Tomsgt:
you would have to uninstall all the google play store apps there are 4 of them. or just firmware restore the device
[Fire Android Development] pfoneguy1:
Thanks for the quick reply., much appreciated.
[Fire Android Development] rorytmeadows:
Hey folks, quick question. I bought mine in December, waiting for development to perfect (as usual, thanks to awesome people like OP). Am I good to run this on stock before connecting to Wifi or should I update first then run with OP?
[Fire Android Development] sd_shadow:
depends on what you want, there are several options in the Supertool
[Fire Android Development] DB126:
If you intend to root or install a custom rom I would suggest not allowing your device to connect/update as higher levels of FireOS have been increasingly difficult to root/mod. If you suspect your device has FireOS 5.0.1 give serious consideration to going straight to a custom rom w/o booting FireOS.
[Fire Android Development] ipdev:
Do not connect to WiFi. Check version, you will not be upgraded if offline.

root (If possible offline) delete any updates and block ota.

(This is the reason my backup 7" is still on 5.0.1 - Still has never been connected to WiFi)

Sent from my SM-T330
[Fire Android Development] Robo-rooter:
I used RootJunky's SuperTool to root my Lenovo Tab 2 A8-50F tablet. Now it's running AdAway, Link2sd, Titanium Backup, ES File Manager, etc.

The SuperTool installed KingRoot (ver 4.8.2), rooted the tablet and then uninstalled KingRoot and installed SuperSU. I had to run KingRoot 3 times and the tablet rebooted once during the process.

Here is how I did it:

http://xdaforums.com/showpost.php?p=66559609&postcount=4514
[Fire Android Development] DB126:
It is likely a 5.1.2.1/5.1.3 OTA triggered the bootloop. Can't speak to the effectiveness of the OTA blocking mechanism(s) in the latest version of SuperTool; earlier releases had some issues. Option 'B' is your best path to recovery. Option 'A' is unlikely to help as the poorly named 'Factory Reset' only clears the data partition; it does not touch System were the problem resides. Option 'C' really a variation of 'B' and a personal choice. Installing a custom ROM is the best path to stability, but I assume you have rejected that option as it was not one of your alternatives. Been around FireOS for a bit and watched many OTA battles play out with bad outcomes. Cat and mouse game at best unless you are comfortable tweaking components on your own and are willing to invest time to get it right. Good luck.
[Fire Android Development] snark.shark:
Is a Custom Rom even still an option when all I have is ADB access? If it is I suppose I may consider it, but I got the impression you needed to initiate those from inside Flashfire (which means already having a working FireOS up and running). Did I misunderstand that part?
[Fire Android Development] DB126:
- long press the power button until device shuts off

- press/hold vol button closest to the headset jack, the press/hold power

- continue holding for ~10 sec until Amazon logo appears (release keys). Do you eventually get to the recovery menu?

- if nothing happens release both keys and repeat second step (occasionally fails on first attempt)

If stock recovery is still bootable then you can sideload FireOS 5.1.2, root, block OTA, install FlashFire and move forward with a custom ROM. WiFi should remain off to prevent an unintended OTA. No need to register you device w/Amazon. You may have to enable WiFi for short periods during the rooting process.

If stock recovery is not available then your only immediate choice is to request a one-time courtesy exchange from Amazon. At some point root cause of this type of bootloop may be better understood offering an opportunity to correct via ADB. Not there yet.
[Fire Android Development] GambitK:
You can do Factory Reset and it will solve it. I did it last night. You will have to root again. Some people have reported that the problem comes back after a couple of days.
[Fire Android Development] Robo-rooter:
I would either use the Fire OS tablet stock or root it and add a custom rom. Halfway measures just seem to be asking for repeated problems.
[Fire Android Development] snark.shark:
Hmm. Good info, thanks (thanks to everyone who's responded actually).

You had a rooted 5.1.2? (vs. another OS build)

Also, is it a push of the next OS upgrade "breaking" it again those few days later? As I said, last time I had the Supertool OTA upgrade block installed, and it's only a hunch that this somehow wasn't working and that the next OS rev is what broke me. Does that mesh with what you've heard or concluded?

I am seriously considering a custom rom now, but am not 100% decided on it yet. So just getting back up (but properly blocked from new OS updates) would be the path of least resistance in the short term though. If the OTA block is broken, that actually pushed me more towards the custom rom I guess.

---------- Post added at 03:59 PM ---------- Previous post was at 03:48 PM ----------

The "stock" in this case meaning the last rev. (it looks like that's 5.1.2.1? Or is it 5.1.3? I'm confused on that)? That would mean giving up on root, then right? I'm not totally opposed to that, because I used the darn thing with just Google Play and no root ever since Christmas up till a few days ago, but the reason I finally gave in and rooted was people (here actually) warning that as time went on it seemed like it was getting more likely with each rev. that rooting might stop being possible. Meaning I had to do it now, while it was working (albeit with a lot of steps and rerunning of Kingroot). I guess again that probably pushes me to a custom rom too.

If I do pick a custom rom, what becomes the upgrade path FROM that custom rom to future revs though? If the thing is still booting, it seems easy---I'm sure you can load new roms from inside a working OS. But if the custom romed Fire breaks? Does that Power/Vol Down recovery menu still work? (in which case I assume you'd have to reload an official Fire OS via ADB, turn off your wifi, and reload the custom rom again)

Oh, just out of curiosity, the one I keep seeing people refer to is the Nexus Rom. How the heck does that work with the Fire 5th Gen anyway? Isn't the hardware totally different?
[Fire Android Development] Robo-rooter:
I'm saying people should either use the Fire tablet as it comes from Amazon, or root it and install a custom rom. Trying to modify the Fire OS by adding the Google store and trying to block updates just seems to be asking for headaches.

I rooted my Fire 7's and installed the Nexus rom on all of them. It's a nice little knock around 5.1 Lollipop tablet. My wife is using one and my sister is using another. I set one up to monitor our front porch security camera.

The Nexus rom makes the Fire 7 a totally generic 5.1.1 android Lollipop tablet. The setup menu looks exactly like the 5.1 android menu on my Lenovo Tab 2 A8-50F tablet. I loaded the Nova launcher on the Nexus rom Fire 7 and my Lenovo tablet and they both look and operate exactly the same.

The author of the Nexus rom has released a couple of upgrades. You just load those and flash them with Flashfire. Loading an upgrade rom doesn't disturb your apps or data.

If you ever wanted to go back to the Fire OS rom, you could sideload it by going into the adb menu with the vol / power keys.

After all, it's a $50 tablet (that you can buy any day on Amazon for $30 refurbished). So I really wouldn't worry about future upgrades. Use it and enjoy it today for what you can make of it today.
[Fire Android Development] Chyron8472:
I tried using RootJunky's SuperTool to root my Fire 7, but when it tries to get KingRoot it fails with an INSTALL_FAILED_VERSION_DOWNGRADE error.
[Fire Android Development] m00head:
Uninstall the existing version of KingRoot on your device, then try again.
[Fire Android Development] GambitK:
I have two Fire 7 and on one of them I installed the Nexus rom and Slimrom and they are both great. The only problem is the sound bug in some games, that's why I haven't installed it in both.
[Fire Android Development] Chyron8472:
Got Kingroot uninstalled finally. Turns out SuperTool is using KingRoot 4.8.2. Latest version is 4.9.

Both of them fail to root my Fire 7 (FireOS 4.1.2).
[Fire Android Development] Robo-rooter:
I rooted my 3 Fire 7 with firmware 5.1.2 using the SuperTool with 4.8.2 KingRoot. You have to keep running KingRoot. If the tablet reboots, start KingRoot again. Some have had success in rooting after 10 tries. With each try, KingRoot seems to reach a higher percentage. Keep trying.
[Fire Android Development] asmad:
Which Rom has the sound bug? Nexus or Slim?
[Fire Android Development] GambitK:
Both roms, some games sound like a machine gun. The sound seems kinda "stuck" playing a specific effect. Rebooting sometimes makes it so that they sound good but after a little bit it comes back again.
[Fire Android Development] asmad:
Thanks for the info. Good to know these things before flashing.
[Fire Android Development] baggerbodo:
If you can´t root 5.1.2 and stuck in kingroot at 30% so you need to sideload original amazon 5.1.2 bin. After this kingroot will success after a few try.
[Fire Android Development] DB126:
tl;dr - you will do better with short/concise posts vs rambling monologs with multiple imbedded questions. Hopefully you are learning (gaining confidence) reading through this and other threads in the Fire forums.
[Fire Android Development] Robo-rooter:
When I mentioned "stock rom" on the Fire 7 tablet, I meant the original Fire OS menu system that comes with the tablet. When you install a "custom rom" like Nexus, the Amazon updates are no longer loaded (either automatically or manually.) When a custom rom is loaded, Amazon updates no longer work on the tablet. That's a good thing.

If you want to go back to the original Fire OS rom, you can. Then Amazon updates would work again.

The writer of the custom roms have made a few updates, they usually do at least until all of the major bugs are addressed. You can load custom rom updates without erasing your current apps or data on your current custom rom.

The custom rom "Nexus" is created to LOOK like the Google Nexus, but it is designed to work on the Fire 7 hardware. It looks EXACTLY like a generic Android 5.1 Lollipop menu system. To this you can add launchers. The Nova launcher is one that works well on the Fire 7 tablet with a Nexus rom.

One good thing about the Nexus rom, as designed, it's not loaded up with a bunch of pre-installed apps. It only has about 8 or 10 pre-installed apps. Just enough to get the Google Play store working. It doesn't even come with a pre-installed camera app. This lets you choose what YOU want or need. Right after loading the Nexus rom, there is about 5gb of free internal space on the Fire 7 tablet. Being rooted, you can link apps to the SD card for even more storage space.
[Fire Android Development] Chyron8472:
Yep. Sideloaded FireOS 5.1.2, and KingRoot worked first shot out of the box.

Then I had some issues getting SlimLP to install, but leaving the .zips' default settings in FlashFire alone was, I think, what got SlimLP working.
[Fire Android Development] nysom16:
My kindle just came in today and when updated from 5.1.1 it said the update was for 5.1.2. However, when you click on the version name I realized that 5.1.2.1 was installed which is unable to be rooted as of now. I followed these instructions to downgrade like you alluded to. Make sure you use this file in recovery if it says you're on version 5.1.2. Once I downgraded I was able to root with Kingroot on the 3rd try.
[Fire Android Development] snark.shark:
You mean after the last time I had a problem and had people keep telling me I wasn't giving enough info?

Okay, I suppose I'll have to find something in the middle then.
[Fire Android Development] DB126:
Relevant (operative word) detail is good. Don't need a story.