yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] RevAtB:
SOL or G2G?

I was able to snag "refurb" 16G fire 7" on the prime day for $38, sure it has a few dead pixles but hell, what a deal.

It has taken the 5.1.4 update <UGH> I was able to get playstore on it, but of course cannot root this firmware.

Am I going to be able to downgrade to 5.1.2 and root this bad boy? or am I SOL?
[Fire Android Development] lieferant:
I ordered 2 on Prime day. One came with 5.1.1 and one with 5.1.3... dammit

Successfully rooted and installed Fire Nexus on the 5.1.1.

I'll try to downgrade the 5.1.3 to 5.1.2 and see if it works out as well.
[Fire Android Development] Blastyrant:
I've read that you can downgrade 5.1.4 to 5.1.2 and gain root. Do not downgrade below 5.1..2 or you will brick your system.

This is what I did on 5.1.3: http://xdaforums.com/showpost.php?p=67803488&postcount=4
[Fire Android Development] rickatnight11:
I successfully followed https://www.youtube.com/watch?v=RQLoH-ahjy4 to downgrade a tablet running 5.1.4 to 5.1.2, and was then able to root and flash the Fire Nexus ROM. Hurray!

I tried the same on another tablet, also on 5.1.4, but after adb sideloading the 5.1.2 bin, it never booted again. It appears to be in the same "brick" state as described in http://xdaforums.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747, but those instructions only work for people who tried to go from 5.1.1 to 5.0.1. Am I screwed with this tablet?
[Fire Android Development] DB126:
There is an inherent risk with any flash/rollback; you may have just drawn the short straw. Or possibly used the wrong file which is a common error. In either case little can be done if the device will not boot and can be coaxed into recovery mode. A warranty exchange (if relatively new) is your best option.
[Fire Android Development] thetolsonator:
Getting this error when trying to roll back to 5.1.2 through the tool provided in the OP.

Any help? Currently on 5.1.4 and have adb installed and working properly.
[Fire Android Development] Tomsgt:
did you extra the zip to your desktop
[Fire Android Development] sd_shadow:
extract/unzip
[Fire Android Development] DevilsClaw1991:
Can I use this tool to downgrade from 5.1.4 to 5.1.2?
[Fire Android Development] Tomsgt:
You can use this tool http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/Firmware firmware downgrade super tool here
[Fire Android Development] DevilsClaw1991:
Great. Thanks a lot. After downgrading how do I root the Fire with 5.1.2? Is there a supertool as well?
[Fire Android Development] Tomsgt:
Yeah the one on the op of this thread.
[Fire Android Development] DevilsClaw1991:
I f***ing love you. :victory: Thanks!!!
[Fire Android Development] dnf007:
I'm trying to downgrade as well. I'm plugged in with ABD enabled. My computer sees my kindle but when I open a terminal and run the supertool nothing happens on my kindle. What am I missing?
[Fire Android Development] shinykari:
I had this same issue--did anyone ever figure out the cause? I'm at the office and not able to sideload anything, but was able to do a Factory reset to at least get it out of the boot loop. Everything was hunky dory for about a day and a half, plugged it in last night (wall charger, not computer, w/ correct cord) and this morning it was looping.

(And here I thought I was in the clear, because Kingroot only required one reboot to root my Fire. Spoke too soon, I guess!)
[Fire Android Development] DB126:
Best guess: OTA updates not effectively blocked. Looping a common side effect of a failed FireOS/rom update. Could also be caused by Kingroot detritus (switch to SuperSU) or a silent update to Google Framework/Services/Store if installed.
[Fire Android Development] shinykari:
Thanks! Any ideas how to prevent it in the future, or do I just need to reroot and hope for success?
[Fire Android Development] patt2k:
Does it matter if I have the 16GB model of Fire tablet. It came in with 5.1.3 I remember I could downgrade 8GB model on 5.1.3 with no issues. Will roms also work on 16GB model?

thank you guys!
[Fire Android Development] dukefan6842:
I might need some help and I'm sure this info is available but I couldn't find it. I bought a new Fire 7" 5th gen, sideloaded 5.1.2, used the supertool to root/install google play/block OTA updates, it worked fine for a week. I came home from work today to find it booting to the "Optimizing system storage and applications" screen in a loop. Advice?
[Fire Android Development] DB126:
- use the FireOS OTA update blocker included with the SuperTool

- if the problem persists might consider moving away from FireOS (ie: install a custom rom like CM11 or Nexus)
[Fire Android Development] m00head:
Yes, downgrading and installing ROMs will also work on the 16GB model as long as it is on FireOS 5.1.4 or lower.
[Fire Android Development] DB126:
Likely an automatic update from Amazon made its way through the block. Heard this from a few others over the past week or so. Yikes! There may be a new OTA uodate method in play. Also possible Google framework silently updated causing FireOS to cough up a fir ball.

You can sideload 5.1.2 to recover your device but it's likely to do the same thing after a few days until the underlying cause is identified and a 'fix' developed.

Other option is a custom ROM which will releases your device from Amazon's control. FireOS is not a particularly good platform for Google components regardless of the reason for the recent rash of boot loops. Unhappy marriage at best.
[Fire Android Development] dukefan6842:
Thanks for the answer, I re-sideloaded 5.1.2 and am OK for now...
[Fire Android Development] J3RI3L:
Hi guys, I'm trying to downgrade my 16GB Amazon Fire "7 5th Gen Tablet Firmware 5.1.4. The problem I'm facing is that when sideloading the 5.1.2 right at 47% it stops and a message displays on the screen saying (Could not verify whole-file signature, operation aborted).

I've downloade couple of firmware files from different sources with no luck including the ones on RootJunky's website with Supertools, any ideas please?
[Fire Android Development] DB126:
Why are you cross posting? Several people are trying to help you in the other thread. Not good enough?

Aside from that annoyance note the following from another contributor (suggest reading a few posts before/after):

http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294/post67852262

I'll just check out now; hopefully someone else can work out the issue.
[Fire Android Development] J3RI3L:
Dude chill, just asked in the Supertool Thread (which I'm using to downgrade you know).

Just trying to solve an issue here, thanks for the time. BTW I tried everything you said in the other thread and nothing yet.
[Fire Android Development] stuzer:
These tools are BA

RootJunky you're my hero. Bought this tablet for my daughter and I root pretty much every device I've ever owned and you've made it so simple and quick, even on Mac which is hard to find the process for on lots of devices. I just want to show my appreciation.:good::laugh::D
[Fire Android Development] Tomsgt:
Glad you like it. I have lots of fun creating these scripts it's a fun challenge.
[Fire Android Development] pinkshirtbadman:
[/COLOR]

I am having an issue where I am sure I am probably missing something very obvious here, but I am attempting to downgrade from 5.1.4 to 5.1.2 and have used the firmware downgrade supertool and have watched and followed the youtube video How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet from Dec '15 (sorry, new user, cant post a link)

although the supertool seems to be newer than the video since I'm looking to downgrade not to redo the firmware "upgrade"

The downgrade Supertool ran me through the steps and had me install from ADB and proceeded to give me the warnings that it would take some time and was like watching paint dry. I received no progress bar or any sort of indication it was working, however a short time later it notified me the device was now properly running 5.1.2 and I could select reboot on the device (and a further warning that the first boot would take 15 minutes)

On the device the screen still says "Now send the package you want to apply to the device with "adb sideload <filename>" and nothing happens

Eventually it tells me it has timed out waiting for the package / installation aborted.

If I restart the device it is still of course running 5.1.4

I am sure I am missing something obvious step but am at a loss as to what it may be
[Fire Android Development] stuzer:
Bootloop issue

So it's been a day and I had powered down to save battery life before finishing my setup of the new device and now I'm stuck in the bootloop optimizing software yada yada. I assume I'll have to use ADB to restore the 5.1.2 and then root all over again? Is there a way to resolve this issue for sure. I saw a few people mention it before but no one definitively confirmed that they had the solution outright.
[Fire Android Development] reeshmd23:
Ok I give up I'm on 5.1.2 how do I flash a rom, flashfire doesn't seem to work it just reboots
[Fire Android Development] fmc000:
It's been at least three days I'm trying to download the latest Super Tool and it always stops at 59,1 MB (62.002.307 bytes) . Anyone else? Maybe someone can provide a mirror?

BTW, the old release downloads just fine.
[Fire Android Development] DB126:
Best guess is you failed to block OTA updates (or used an unreliable method, eg: pm hide ...) leaving your device vulnerable to whatever Amazon decides to push. You can try to reload 5.1.2. Might work or trigger a brick if the rogue update was FireOS 5.3.x which can not be rolled back.

---------- Post added at 05:53 PM ---------- Previous post was at 05:49 PM ----------

Downloaded fine for me; linear progression; no hesitation or stalls at/around 59 MB.
[Fire Android Development] stuzer:
I did everything through the Supertool Multitool. I used the downgrade one to go from 5.1.4 and then used the regular one to root, block ads, block otas etc. I'll try it all again if I can and see if there's a difference.
[Fire Android Development] DB126:
Two additional possibilities:

- new version of Google Framework/Services which generally receive silent updates (albeit no evidence this is the problem)

- Amazon found a way to circumvent OTA blocks (also unlikely)
[Fire Android Development] schuh8:
Fire 5.3.1.0

Will any of this work on 5.3.1.0 ?

Can it be rolled back ?

Can ANYTHING be done with 5.3.1.0 ??
[Fire Android Development] sd_shadow:
maybe

no

perhaps
[Fire Android Development] Tomsgt:
At this point 5.3.1 can't be downgraded as it will brick the device. The features of this super tool may work on it or may not it's hard to say. I will update the tool as I find more working hacks for it.
[Fire Android Development] BatteriesIncluded:
I just installed Google Play Store (using the Mac script) on a Fire HD 7 4th Generation after a manual downgrade from 5.1.2.1 to 5.1.2 and the root of 5.1.2 with Kingroot. I then used Doloopers Fire HD Tools to check root and block OTA and ADS, and then used the SuperTool (thanks Jmz) to install Google Play using the Macintosh script because I wanted to avoid the TWRP method (by Bibikalka) which seems a bit risky since you are replacing the bootloaders. The MAC script had to be run twice but only because the Google Settings App did not copy over and install on the first run (not sure why). All is working well now. I was considering using the tool to install Nova Launcher but was wondering if this is necessary. Is it possible to just install a launcher (such as Apex) through the Google Play Store?
[Fire Android Development] Norapapa:
I have a Problem. I use the downgrade Supertool zip to downgrade to 5.1.2. The Version of FireOS is 5.3.1. I didnt read before that this version brick the tablet. After Reboot the Screen is Black. I have Brick the Tablet. Can i anything do? Or is the Tablet dead?
[Fire Android Development] DB126:
Permanent brick. Contact Amazon for a replacement if within 90 warranty.
[Fire Android Development] stanleyopar2000:
is this worth doing right now? hear so much about bootloops.....
[Fire Android Development] DB126:
SuperTool itself does not triggered bootloops. They are actually rather rare if following instructions and staying reasonably close to the beaten trail.
[Fire Android Development] stanleyopar2000:
I know supertool isn't. You think Amazon found a way to push OTA via another method...?
[Fire Android Development] DB126:
Likely not. But if you really want a 'belt and suspenders' defense install a custom ROM (AICP-LP, CM, Nexus, SlimLP...) and never have to worry about an Amazon OTA wrecking your day again.
[Fire Android Development] stanleyopar2000:
Came with 5.1.2. afraid I'm SOL ATM
[Fire Android Development] DB126:
No, you're not as 5.1.2 (but not 5.1.2.1 and above) can be rooted which opens the door to custom roms. 5.1.4 and below can be downgraded to 5.1.2 with minimal risk. If you are not ready for the custom rom leap you should at least use the SuperTool to root and block OTA updates as you will truly be "SOL" if your device goes to 5.3.x or above.
[Fire Android Development] beezar:
http://xdaforums.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594

Works great. I'm on 5.3.1 with a 5.0.1 bootloader, retained root, can go to TWRP, etc.
[Fire Android Development] tawengss:
my amazon fire 5th gen

-can i use this method with my updated os?...

my os version now is 5.3.1.0
[Fire Android Development] DB126:
Some features may work while others will not as 5.3.1.0 can not be rooted at present.
[Fire Android Development] eoinzy:
IS anyone else getting an error on Ubuntu saying:

"sudo: unable to execute files/./adblinux: No such file or directory"

I can't root my device now! :(
[Fire Android Development] pinkshirtbadman:
Solved

I am still having an issue with the downgrade tool trying to downgrade from 5.1.4 to 5.1.2 so I can add the google play store. I have attempted to run the downgrade supertool on two different PCs both running win 7 64 bit.

On one PC I'm given an error message "error: more than one device / emulator" (the kindle fire 5th gen is the only device plugged into the PC at all.) the supertool then stops responding saying it waiting for any device leaving me unable to do anything.

On the second PC I get to the point in the fastboot mode where it asks you to apply udate from ADB and then tells you to send the package. The supertool says it is laoding the .bin file and warns it may take 20 minutes. I get no progress bar or indication it is attempting to run on the device or on the supertool, but then within a minute or two the supertool tells me I have succesfully downgraded. The device on the otherhand still says and eventually times out. If I restart the device it is still running 5.1.4

Edit: I updated the device to 5.3.1 ad the supertool worked perfectly.

Thank you, and sorry for the hassle
[Fire Android Development] lextex:
I downgraded to 5.1.2 with the supertool, and it seemed to work just fine. Rebooted out of recovery and the screen just stayed black. Won't boot at all now.
[Fire Android Development] DB126:
You do understand 5.3.x can not be rooted (at present) or downgraded. Not really an issue if your only objective was to install the Play Store and have no interest in a custom rom to replace FireOS.
[Fire Android Development] lextex:
I was at 5.3.1 -- is that why I'm bricked after downgrading to 5.1.2?
[Fire Android Development] pinkshirtbadman:
Yes, the play store was really my only goal since the tablet is for my daughter I didn't need anything particularly fancy. Thank you very much for the heads up (and warning for anyone else )though
[Fire Android Development] Merlin8008:
Hello, sorry for newb post. My device gets stuck on adb and fastboot test and I can't get my device to show up in the supertool. I have adb and fastboot installed. I'm running 5.1.1 out of the box hasn't been connected to wifi or registered.
[Fire Android Development] DB126:
Yup - sorry for your loss. Contact Amazon for a courtesy exchange if still under warranty.

(rollback and accompanying brick risks are well documented in the forum index and numerous discussion threads)
[Fire Android Development] lextex:
I am in the process of trying to get it replaced. Only had it for a week.

Would definitely not say "well documented." It was not clear at all that I'd brick it by going back to 5.1.2 -- I was under the impression that it would only brick if you went back further than that.
[Fire Android Development] DB126:
http://xdaforums.com/amazon-fire/general/warning-downgrade-5-3-1-0-brick-device-t3422003 (thread title says it all)

http://xdaforums.com/showpost.php?p=62986665&postcount=3

http://xdaforums.com/showpost.php?p=67948062&postcount=166

These were just the easy posts I found with a 30 sec search. Many more contained within individual threads.
[Fire Android Development] sd_shadow:
http://xdaforums.com/amazon-fire/general/fireos-5-3-1-source-code-released-t3412581
[Fire Android Development] lextex:
This is from the OP:

All I'm saying is that it should probably be updated to say "don't attempt to downgrade if you're on 5.3.1.

Yes, there are warnings in other places -- but it would be nice if it were in the OP here, too.
[Fire Android Development] Tomsgt:
OP updated. I hope your happy :) :)
[Fire Android Development] DB126:
Fair point. That said, time moves on and everyone here is a volunteer contributor with limited time & resources. OP is an amazing individual who supports dozens of devices and produced countless videos that have benefited many. FireOS 5.3.x is relatively new; not surprised OP has not been updated to address this specific release.

First rule of modding is recognizing a comment/guide is only current the moment it is posted...and may still be 100% wrong. Research and collaborate everything. Ask if unsure. In general rollbacks are risky and should always trigger a 'yellow flag' response. Consider yourself wiser for the experience.
[Fire Android Development] asmad:
Well said!

The OP is truly a giant amongst men for his work on these devices. Without his hard work and commitment this device would at best be a mediocre tablet.

Remember it's not a paid job, but something done for free in his spare time and every update has taken considerable time to create and test.

Enjoy the result and try to help others on the forum with your own results and experiences. If you have a problem or a question people are very quick to help where they can.
[Fire Android Development] Tomsgt:
Like a breath of fresh air. Thanks guys
[Fire Android Development] lextex:
I appreciate you updating the OP, and for all of your work on the Supertool in general!

As for Amazon -- they're replacing the tablet. Before bricking it, i was at least able to get the Play Store loaded, so I'll learn to live with those lock screen ads. :)
[Fire Android Development] robbygizzle:
Amazon Fire 5th Gen after attempting to load a theme, took ota update to 5.3.1

First off, I just want to thank everyone for all the info, tools, and advice through out this thread and others! Especially Tomsgt, sd_shadow, and Davey126. Pulled a lot of info from your post! I had an issue I thought warranted a post. I purchased 2 Kindle Fire HD 7's 5th gens. on prime day both delivered with 5.3.1. One of the tablets had very little issue with and had it rooted with Kingroot and Supertool running CM12 with very little issues. The other one took kingroot at least 7-8 attempts to finally get, but got it done. My problem came while loading apps etc. I followed the CM themes engine to Play store and tried to load a colored theme as tabs are for my kids. Did due diligence, read and identified appropriate versions and compatabilities before attempting. In my experiences they are fairly safe if you've read and ID'd devices, versions and Launchers etc. Rebooted and the device went into what appeared to be a ROM loop as opposed to boot loop. Had clearly booted and CM wallpaper displayed but never loaded beyond that, just occasionally a flash which I assumed was the ROM trying to reload. Tried rebooting and wiping cache and rebooting etc. which I didn't have much hope for. Under ADB device now showed unauthorized so I decided to start over and sideloaded 5.1.2, then Supertool and blocked updates Google play etc. Had difficulty again with Kingroot and finally put it down and went to bed. When I went to resume in morning I had notification that it had been updated at 05:30. Checked version 5.3.1. SUCK! I have seen a couple of post of others taking update while thinking they were blocked. I am pretty methodical and would definitely not be posting anything if I wasn't fairly sure OTA was blocked. My recommendation to others would be to disable the wifi if stopping work on tablet for any period of time. I should have known better. That being said, and lacking any evidence to the contrary I am assuming it was operator error. Wanted to post my thanks for all the help and figured I should put it out there in case something was up. Thanks again!
[Fire Android Development] DB126:
There a a couple different ways to block Amazon OTA updates. One involves disabling components via 'pm hide...' which is non-durable and easily reversible. The other entails renaming one or more files which is both time proven and permanent. I have not dug into the various tools commonly used to block updates on this device to see which approach(s) are being used.

A couple quick footnotes on your original post:

- Suspect your two devices initially arrived with FireOS 5.1.3, not 5.3.1. If it were the latter you would not have been able to root or install a custom rom.

- There is no "HD" in the device name; it is simply an 'Amazon Fire' or '5th gen Fire'. The HD nomenclature was only used on 2nd-4th gen 7" devices.
[Fire Android Development] lexgladium:
Hi all,

I'm new to this process, and am trying to downgrade and root a 5.1.3 fire (from Prime Day). I did a forum search, but don't see anyone with exactly the same issue. I can access the tablet, and can get a serial number post in a command prompt; however, when I get to the second stage of the "Firmware-Downgrade-to-Fire-OS-5.2.1-Supertool" program, it returns "error: no devices found" after "loading: 'update-kindle-global-37.5.4.2_user_542168620.bin."

It continues with stating that the downgrade is complete and that the machine will reboot, but this doesn't happen. The tablet remains waiting with the yellow text for an adb sideload for a few minutes, then times out waiting for the package and aborts.

Any advice?
[Fire Android Development] DB126:
Host driver issue (presumably Windows). See forum index, in particular post #4. Driver issues are a constant source of frustration on Windows; you'll have to fight your way through.

http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485/page1
[Fire Android Development] lexgladium:
That they are... Thanks for getting back to me so quickly Davey126!

I reinstalled the most recent USB drivers for my motherboard, but still ran into a problem with the KFFOWI driver. Tried using every one of the 6+ root/SDK/driver packages I DLed as a source of drivers for Win 7's "Select driver from disk." What finally helped was a tip from acme000 (http://xdaforums.com/kindle-fire-hd/7-inch-help/kffowi-issue-t3420782), right clicking it and selecting Fire Device, then Android composite ADB interface in the next window.

Hopefully this helps anyone else who comes across that error.:good: