yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] Veon11:
The download doesn't seem to work, it always stops with an error at 99%... Another link? Or anyone willing to share it.

Thanks!

---------- Post added at 10:09 AM ---------- Previous post was at 09:42 AM ----------

Nope, it worked after a while! Sorry!
[Fire Android Development] steve8x8:
Has anyone ever tried to backup an existing Stock ROM setup using FlashFire, and possibly restore it?

This might avoid the long and crooked path via reinstall-root-customize, should something unforeseen happen that makes the system misbehave (of course, only to the point that FF could still be started), or to return to a previous ROM from a custom one...
[Fire Android Development] sd_shadow:
I haven't tried for awhile, but earlier versions of FlashFire didn't support FireOS installation
[Fire Android Development] Sinalco33:
I have already the aosp 5.1.1 rom on my fire tablet, but i cant get root access. Either with the supertool (error while uploading Files in the fastboot mode) or with kingroot or kingoroot. What elso can i do? :(
[Fire Android Development] DB126:
Assume you are referencing Fire Nexus which comes pre-rooted. However, you may have messed that up trying to run KingRoot. Install SuperSU from the Play Store and reboot. If that doesn't yield root then you will likely need to reload FireOS (same version you had before) and start over.
[Fire Android Development] neilc300:
Fire tab 5th gen

Has anyone successfully rooted this device or been able to downgrade from fire os 5.4.0.1? Did not see anything mentioned past 5.3 versions. Thanks in advance for any input
[Fire Android Development] DragonFire1024:
There are several threads in this forum discussing the matter that doesn't require a search. Just need to look at the most recent ones in the first two sections. There is no root for 5.4.0.0 or 5.4.0.1. if you have a Fire 7, 7th Gen, you can downgrade from 5.4.0.1 back to 5.4.0.0 which means you can also downgrade from 5.4.0.0 to 5.3.2.1, but none lower.
[Fire Android Development] DoubleL03:
I was just wondering if anyone could help me out. I am on 5.3.1.0

What will the Super Tool alow me to do?

Thank you in advance for your help..
[Fire Android Development] steve8x8:
Provided you have turned off your WiFi, and deregistered the tablet from Amazon, the SuperTool can help you root the device, install Google infrastructure, and disable ads. There's a batch script coming with the ST, it won't harm to study it ;)

Keeping WiFi off, and under strict control for the rooting process, is crucial, otherwise you'll end up with 5.4.0.1 from where there's no known way back.
[Fire Android Development] DragonFire1024:
I wonder why the OTA happens on the Fire 7 and HD 8, but not the 8.9. I wonder why Amazon hasn't updated the 8.9s at all.
[Fire Android Development] DB126:
Different generations; level of adoption; challenges distributing OTA; etc.
[Fire Android Development] havikx:
Hey guys, I was messing around with the launcher. I factory reset and now I don't have a launcher? I'm on 531. I can't get into settings to enable and. How screwed am i?
[Fire Android Development] DB126:
You will need to reload ('sideload') FireOS 5.3.1 from stock recovery. Be sure to keep device off WiFi until rooted and OTA updates blocked. Consider installing a custom ROM which offers a far richer experience on this device.
[Fire Android Development] havikx:
That was the plan. Luckily I'm remembered adb once I got back Into it. Been a while. Now on nexus Rom. Recommend anything else to mod from here? Not too much of a backing here and I haven't really kept up on the modding scene.
[Fire Android Development] DB126:
Consider Xposed Framework and modules like Gravitybox if seeking additional UI flexibility on Nexus (AOSP). L Speed (available in Play Store) has additional knobs and dials for those inclined to tweak. Greenify makes a nice add to quiet background activity. Alternatively, try Lineage 12.1 which strikes a nice balance between AOSP and useful tunings.
[Fire Android Development] thezman007:
Rats

Sooo... since it just updated to 5.6.0.0 I suppose I can't root, or use a custom ROM? Is that correct?
[Fire Android Development] ytsejam1138:
You are correct, sir.
[Fire Android Development] evodon84:
How can I get into fastboot if the tool isn't working? Running 5.1.1. I get the error below in the supertool.

error: more than one device/emulator

Edit: Realized I also had Bluestacks running which was causing the error....
[Fire Android Development] madagascaradam:
Sooo... I got the Kindle for my kid last year at Christmas-time, thinking we'd see how the "FreeTime Unlimited" goes for the free year it comes with. Turns out it's an OK service, not great, and now it's expiring. I always figured I'd convert the OS to regular android when the FreeTime Unlimited was done (because Fire OS really doesn't seem to be a friendly OS and the limitations are terrible). But now I see that his Fire had updated itself to 5.6.0.0 in the meantime.

Is it true that I literally can't do anything with it now and I'm stuck with the terrible Fire OS? Please let me know if there's anything I can do! I've rooted several android phones, converted them to Lineage or ASOP Extended, etc., different options, so I'm familiar with rooting and flashing roms and the general process. Is it not possible to just wipe the system and clean flash to an older OS so that I can use whatever tools there are in order to convert this thing to a legitimate Android device?

Please help! Not only is Free Time not effective for us anymore (since we no longer have regular internet service in the country we live in), but overall it just really limits what our son has access to, defeating the point of getting him this kindle fire. If there's anything I can do to convert it to an actual android tablet, PLEASE let me know! Thanks!
[Fire Android Development] ktmom:
No, you can not downgrade enough to be able to root/flash custom ROM. The bootloader is the issue. Amazon has a vested interest in preventing their low prices devices from being turned into returned tablets.

You should be able to install google play store, and have more choices in apps. I also use a launcher interceptor to "switch" launchers so I can control what is presented on the home screen.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Fire Android Development] madagascaradam:
Haha, I like that quote! And yeah, better judgment next time!

So, I have already installed the Google Play Store on my profile, which accomplishes a lot (for me). I thought it would let me give access to more apps to my kid's profile though, and it did not! :( So I'm getting the FreeTime Unlimited canceled as I'm writing this. But how do I get my kid access to the Google Play Store apps and things like that? I think I saw someone else write on here in the last few pages that maybe they could only install Google Play Store access on one account on their kindle fire, but not multiple accounts. Let me know if you know about that.

Also, where do you get the launcher interceptor to switch launchers? That sounds like a decent-enough start anyway. Fire OS really sucks. That's why I haven't messed with my son's tablet much at all since he got it and am only too late realizing I'm too late to switch to regular android. (Thus, your quote above.)
[Fire Android Development] ktmom:
Pardon my acting like a mod, but I don't think this is a good thread for an ongoing discussing about these issues. There is currently an ongoing discussion [in the play store thread I linked before] about multiple profiles and the related problems. I use this launcher hijacker.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Fire Android Development] Bratzilla:
Quick question - I've just gotten a hold of the Fire 7" 5th gen that is still running version 5.0.0. If I am planning to install a custom ROM (as I am not interested in using FireOS), should I run this tool first?

Sorry if this has been addressed elsewhere. I searched and read through a LOT of information that had me somewhat confused, so I just want to get clarification. Thanks!
[Fire Android Development] madagascaradam:
Thanks for the link on the launcher hijacker. It's definitely added a LOT of functionality that was missing in FireOS. Not quite as smooth as if FireOS wasn't beneath it at all, and a few challenges on similar apps between amazon store and play store, nonetheless, with it I can do most everything I want. Thanks a lot for the input!
[Fire Android Development] ktmom:
I think it will help to read through the [Index]Amazon Fire 7" - 5th Gen-2015 by sd_shadow thread. Read through everything, but esp. post #4.

"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers
[Fire Android Development] brubakes:
Same thing here. I picked it up just because it was an on sale from a marked down from a refurb price and figured eh, what the heck. Oh well, locked into the crap fire OS I guess.
[Fire Android Development] jamoosh:
Hi everybody. Thanks OP and everybody else here for your work and contributions here. I have a quick question, if anybody can answer or point me in the right direction. I have a Fire 2015 device that was previously rooted using the SuperTool. At some point an update slipped through to Fire OS 5.3.3.0. Can this version of Fire OS be rooted at all and/or a custom ROM be installed, and if not, can it be rolled back to a previous version without bricking the Fire. If anybody can point me in the right direction, I'd greatly appreciate it. Thanks again.
[Fire Android Development] platypoid:
Take a look at third post on this topic

https://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485
[Fire Android Development] DB126:
FireOS 5.3.3.0 is a oddball release that is rarely seen in the wild (at least on the 5th gen Fire). Unfortunately, since it follows 5.3.2.1 I'm fairly confident with the following:

- no root

- no rollbacks to rootable build (attempting to do so will brick device)

- no custom ROMs

- Play Store can be installed

- alternate launcher can be installed

- debloat scripts are supported
[Fire Android Development] hochichi667:
Best way to flash settings?

I have a strange problem with my Amazon Fire 5th gen, which worked fine for a long time after using Rootjunky's tool to root the device, put on CM, etc. Somehow or other something got corrupted and there's no way to turn on USB debugging. Even when disconnected from USB, in the settings it says it's still in charging mode. I've tried a variety of things, but would now simply like to back up my photos, etc., and 'flash' it back to how it was after I rooted the device. In other words, something like a factory reset but not. I'd like to keep CM.

What's the best way to do this? Thanks.
[Fire Android Development] DB126:
There is a fix for this but I don't recall the details. Will try to find related posts in the next day or two and respond here.
[Fire Android Development] Mervingio:
Yes few games that's my son plays simply says please disconnect from USB PC and others few simply not run [emoji15] [emoji55]
[Fire Android Development] hochichi667:
Thanks in advance if you're able. I've been hunting through the forums and the help sites without any luck.
[Fire Android Development] DB126:
Try this:

- install a terminal program from the Play Store

- launch and issue the following command: setprop persist.sys.usb.config mtp,ptp,adb
[Fire Android Development] hochichi667:
"No command 'setprop' found. "

Will try another terminal program.

---------- Post added at 05:47 PM ---------- Previous post was at 05:38 PM ----------

I'll be damned. That brought back the Android debugging option. (No longer grayed out.) However, when I run 'adb devices' on Ubuntu, still nothing shows. Killed and restarted server: same. Also, when I go on the Fire: settings - storage, then the upper right menu and hit 'USB computer connection', the same as before it comes up with 'USB is now disconnected'.

Can't seem to get this device to simply show up either on Ubuntu or on a Win 7 machine.
[Fire Android Development] DB126:
Have you tried a different USB cable? Many folks sluff that suggestion off as fishing until they actually do ... and it works. USB cable quality is all over the map regardless if where sourced. The one include with 5th gen devices was no gem; most of mine landed in the waste bin after being tested.

Also look for pin damage if you are not having any luck with different cables and host platforms. Ports aren't the most robust on this device; pretty much what you would expect on a 'value' oriented gizmo.
[Fire Android Development] hochichi667:
Good advice but in this case, I've tried three USB cables across two computers with 3 OSs (laptop w Win 7, PC with Win 10/Ubuntu). For some reason, I can't get any of these to trigger a driver discovery. Plugging, unplugging, device reboot, etc.: nothing. But this wasn't always the case. Was able to plug it into a PC access the file system a couple years ago. So I think it's software related on the Kindle device.
[Fire Android Development] DB126:
Could be, but a hardware flaw is equally likely IMHO. Here's an easy test. Boot into RECOVERY MODE and then select the option to 'reboot to bootloader' (can also boot directly to the bootloader if you know how). Once there tether and check Windows device manager. If nothing shows up it's likely a hardware or communications fault. However, if you receive some indication Windows noticed something was connected then the problem under FireOS is probably software related as you suggest. The fastboot test isn't perfect but works most of the time.
[Fire Android Development] hochichi667:
Tried the test. Went into recovery mode, selected 'reboot to bootloader', plugged it in as it went into fastboot mode. Windows 7's installing driver bubble window popped up, and it installed Windows ADB Fastboot (or somesuch driver). Which I then found in Device Manager as 'Android Bootloader Interface'.

So that much works. Advice on where to go from here?

---------- Post added at 10:14 AM ---------- Previous post was at 09:37 AM ----------

A couple of updates. Used Rootjunky's tool to try and test the ADB and fastboot drivers following your advice to put it in recovery mode. While the ADB device didn't show up as listed, the fastboot driver did. So I rebooted the PC, and went through the occasional MT65xx preloader failing to install. This time I was watching device manager, and rebooted the device, and while the device was booting into fastboot, I saw the Android ADB composite device actually fully load into device manager under 'Fire devices'.

So I went into an ADB window (platform-tools-latest-windows, shift right click in window), did an ADB devices - and it actually showed the device there as unauthorized.

Problem is, as soon as you boot the device up normally, all that goes out the window. No sign of a driver in Device Manager, no sign of a device under ADB.
[Fire Android Development] DB126:
The "unauthorized" response when the device is in fastboot mode is expected.

Suspect you are running rooted FireOS. Fastest solution is to reload (sideload) the version that is currently on your device. You will have to maintain network isolation (WiFi off!) while rerooting and restore all apps, settings and personal data. Kinda a PiTA.

Other option is to go for a custom ROM.
[Fire Android Development] hochichi667:
Yes, the device was rooted and is currently running CM 12.1-20151216-UNOFFICIAL-ford. Android version 5.1.1.

Any decent How-To guide you can refer me to for this process?
[Fire Android Development] DB126:
Time to update to LineageOS 12.1 which is the direct descendant to CyanogenMod (CM) which was discontinued in 2016. It's pretty easy to cut over; I'll reply back here in a day or two if you haven't found your way.

Do you know by chance if your device can boot TWRP? Did you need to use FlashFire when CM was first installed?
[Fire Android Development] hochichi667:
There's a TWRP folder on the microSD card. And as far as I can recall, I didn't use FlashFire. Could be wrong. I think the whole process was done around the end of 2015.
[Fire Android Development] DB126:
Good. Hold off a day or two. Upgrading should be relatively painless with good prospects for maintaining your existing app portfolio, data, settings, etc. Plus full fallback capability should something go wrong.
[Fire Android Development] hochichi667:
OK. Will keeps my eyes on this thread for when you have time to post. Thanks.
[Fire Android Development] hochichi667:
UPDATE: I used TWRP recovery mode and flashed to the latest March 2018 Lineage OS per your suggestion. So far working great. Plugged into both the Win 7 machine and the Ubuntu machine: file explorer opened up instantly. No problems.

Thanks for all your help. May get back on here if there's a snafu, but if not - cheers.
[Fire Android Development] DB126:
Excellent! Pretty darn easy with a custom recovery (TWRP). Glad everything turned out well including restoring tethered access.

[Sorry for the delay in responding; was behind the wheel for nearly 12 hours with little opportunity to check electronic correspondence.]
[Fire Android Development] Winf2005:
Hi Experts,

If I would buy today a new Amazon Fire. Would this be rootable or not?

Thank you
[Fire Android Development] DB126:
Highly unlikely unless you win the lottery and receive old stock (mid-2015 to mid-2016 vintage).
[Fire Android Development] DragonFire1024:
Or get a HD 10. Rootable out of the box.
[Fire Android Development] lehmancurtis:
I have a Kindle Ford that was running 5.6. it's never been rooted but I had added the necessary software to have Google play store natively. My problem is that I was using to read, laid it down to leave the room, and when I returned it was (and has since been) blank with no sign of life. It tries to show up in Windows 10 but as an unrecognized USB device.
[Fire Android Development] DB126:
While not assured symptoms mirror the case where FireOS attempts to update but fails to complete. Best option IMHO is to long press power (up to 30 sec.) to see if you can coax a response from the device. If no joy repeat holding both power and one of the volume keys. Assuming FireOS will not boot your goal is to reach stock recovery where you can sideload FireOS 5.6.x.x. Unfortunately, this will only work of the bootloader remains viable. If that was somehow damaged the device is toast.
[Fire Android Development] lehmancurtis:
Thank you for the quick and informative response. I will try those things.
[Fire Android Development] Traace:
Hi, I just found a fire tab 2015 7". It was still boxed but now running on firmware 5.6.1.0, is there any way to root it? Want to flash cm12.1 :)
[Fire Android Development] DB126:
Nope. By allowing it to self-update any hope of rooting or installing a custom ROM was destroyed. Those options are only available if FireOS is at version 5.3.2.0 or below. You can not downgrade below 5.4.0.0; device will brick.
[Fire Android Development] Fridget:
Hello. My tablet is running 5.3.2.1. Is it possible to install a custom ROM on that version or downgrading it to a lower version yet?
[Fire Android Development] DB126:
No.
[Fire Android Development] Fridget:
Thanks for responding Q.Q
[Fire Android Development] Shehroz 007:
how to root amazon fire 7 (7 generation tablet)
[Fire Android Development] DB126:
You can't.
[Fire Android Development] Shehroz 007:
Why..?
[Fire Android Development] platypoid:
Because some of the older firmwares had the ability to root via various means. The new firmwares have closed those loopholes and there is no way to do it now - or to go back to older firmwares.
[Fire Android Development] lehmancurtis:
Does that mean that the only way would be to replace essential hardware such as cpu and/or chipset?
[Fire Android Development] platypoid:
I am not following you - no matter what chip it has in it , there is code . If the code and bootloader is all locked up tight there is no way to get into the root and change things . No magic can happen other than what was originally put in there without being able to unlock it.
[Fire Android Development] lehmancurtis:
What hardware stores the code? If it were replaced with compatible and unlockable hardware it would essentially free it up for new code wouldn't it (at least in theory)?
[Fire Android Development] DB126:
Doesn't work that way. Aside from the theoretical folly it makes no sense given the feature set and price point of this value oriented gizmo. A fully unlockable 2nd or 5th gen Fire is far more versatile.
[Fire Android Development] dataslanger:
Did I brick my Fire? Amazon Fire SV98LN

Model # SV98LN

I just (stupidly?) un-"bricked" my fail-to-load (but attempted to boot!) Kindle with a previous root on it to the latest firmware for unbricking from the Amazon website - 5.6.1.0 I believe w/ update-kindle-37.6.0.5_user_605485120.bin - via ADB sideload. After boot and setup, things were running fine and I blocked a firmware update by shutting it off and restarting it as, after a boot up, it still claimed an update was available but wasn't trying to force a download.

Anyway, I heard that this version couldn't be rooted so I grabbed fire-OS-5.1.2-update-kindle-global-37.5.4.2_user_542168620.bin and adb sideloaded that. Now it won't boot, show charge indications, let me load recover, nothing. Just a completely dead Fire - although, to be fair, the device was doing the exact same thing to me a while back after a failed root attempt and, after a period of time, it just started working out of the blue (I **** you not- by working, I mean allowing me to get into recovery).

Did I brick this thing or what?
[Fire Android Development] DB126:
Full brick; no known recovery (same for virtually every Amazon device). Unlike previous experience invalid FireOS rollback attempt corrupted the bootloader. Sell/save for parts.
[Fire Android Development] McMannes:
Dear friends, i am using 5th generation 7" tablet. And device's system is 5.6.2.0. Can i root my device? İf it's possible, how can i do this? Thanks.
[Fire Android Development] DB126:
Nope. Stuck with FireOS.
[Fire Android Development] Tomsgt:
it any of you are that interested in the commands just rename the .bat extension of the supertool to .txt and look at the commands that i coded
[Fire Android Development] jhebert121:
I think something bad may have happened >_<. I ran the script, installed the ADB tools successfully, and my device was identified. Then when the fastboot test started I got as far as "press any key... if your device doesn't reboot then close script and run driver install option again...". Right when the first fatboot test started my device turned off, and now I get nothing but a black screen. I have tried pressing the power button and holding it but I get no response. The device is at work, and I will be receptive to try any suggestions tomorrow. From the sounds of it how bad does one think this Fire is screwed up?
[Fire Android Development] blueberry.sky:
And if someone doesn't want root they should be able to just unroot from within the SuperSU app then uninstall SuperSU, no?
[Fire Android Development] pappasmurfsharem:
I dont think this tool has the ability to brick your device.

What version were you on? 5.0.1 or 5.1.1

How was the charge before you started?

Most usb ports only provide 500mA of current and dont have the juice to charge or keep the tablet powered on
[Fire Android Development] jhebert121:
5.1.1 freshly updated oob

It was fully charged, I had just moved the usb from the wall charger to the computer.
[Fire Android Development] pappasmurfsharem:
Which option did you run right before it went dark?
[Fire Android Development] jhebert121:
I had just pushed space bar after the adb test completed successfully. The fastboot test had just started when the screen went black. This was option 1 from the main menu then option 2 from the install/test adb menu.
[Fire Android Development] pappasmurfsharem:
Not sure, that couldn't have borked your device.

Have you already tried holding volume down + power and/or volume up + power for like 30 seconds?