yashsingh1/xdaforums huggingface dataset:
[Fire General] rmendez011:
hey i tried doing this on my kindle fire, that i bought yesterday, when I got it, it had 5.1.2 but stupid me updated it to 5.1.4, I used this forum to try and downgrade it, but after I did the ADB sideload command and flashed the file, I forgot to wipe data and cache, instead I pressed reboot system now, but now it won't turn on at all, not life, when I plug it in my PC, my beeps but nothing happens, it was at 94% battery, can anyone help?
[Fire General] yossijoe:
Sure you didn't update to 5.3.1.0?
[Fire General] rmendez011:
im positive
[Fire General] DB126:
A cache/data partition wipe is unnecessary and would not have triggered the reported symptoms if omitted. Sounds like you sideload the wrong version or the downloaded .bin file was corrupt. Return for a warranty exchange.
[Fire General] rmendez011:
the funny thing is, i downloaded the bin file from this tuttorial.
[Fire General] DB126:
Downloads can be corrupted by a single flipped bit. Always best to check the file signature (md5) on sensitive operations.
[Fire General] nabelar82:
need your help guys i got the fire hd 5 generation i rooted and make some changes then i try to restored to stock but somenthing went wrong now the fire wont boot into anything screen is black but pc found when i plug in now i cant do anything because fastboot doesnt work or dont find it i try almost everything to recover but nothing works and i am getting crazy help please
[Fire General] sd_shadow:
what firmware version was on the device?

which firmware (filename) did you use?
[Fire General] nabelar82:
was on 5.3.2 update
[Fire General] DB126:
Failed to answer 2nd question -> which firmware (filename) did you use?

If you attempted to sideload any version below FireOS 5.3.1 the device is not recoverable. Also, fastboot can not be used to recover this device or perform other common tasks (Amazon crippled it).
[Fire General] AndroidSpaceMonkey:
Black Screen (no Recovery)

Hi there, I was reinstalling Fire OS onto my Fire 7inch 5th Generation after messing around with it a little and wanting a fresh start but after sideloading the stock rom from the amazon site I'm left with a black screen and unable to enter recovery by pressing Vol & Power, I can only assume that while I was away from the tablet for a few hours it updated the OS to the latest version through OTA update and resulted in a downgrade thats messed it up.

Is there anything I can do to resolve this issue?
[Fire General] DB126:
If you can not enter stock recovery via <power>+<vol-up> the device can not be recovered. What version of FireOS did you attempt to reinstall?
[Fire General] AndroidSpaceMonkey:
Damn it!

The same FireOS that was installed when I bought it, I only purchased it yesterday as part of the blackfriday sales and it came with 5.1.1 so thats the one I attempted to install as thats what the Device page on the tablet said it had installed a few hours before this issue.
[Fire General] nabelar82:
It means I need a new a tablet
[Fire General] AndroidSpaceMonkey:
Well I was luckily enough to be able to take it back to the store and they exchanged it for another one, in the future I'll make sure that im not downgrading the OS to a earlier version that will cause this issue.

One question though, if I was to install CM 12.1 using FlashFire for example and then wish to change the ROM to another one like SlimLP 5.1.1 what would be the best course of action so not to cause another "black screen of brick"?
[Fire General] DB126:
- download rom and verify file integrity (check md5)

- grab any other required zips (see ROM OP for details)

- if necessary reinstall FlashFire

- include system/dalvik/cache as the *first* operation in FF

- (optional) wipe user data ... required going to/from FireOS

- add remaining zips and flash
[Fire General] TheGoliath:
Bricked my device

Hi Guys,

I just received a new Fire tablet, but I forgot to update my firmware so I can downgrade without bricking. So I bricked it by updating via the ADB sideload feature and now can't go into recovery, system or fastboot mode. What can I do?

Thanks to everyone who could help me solve the problem :)

- TheGoliath
[Fire General] DB126:
There are no working solutions for this type of brick. Contact Amazon for a one time courtesy exchange (if still in warranty).
[Fire General] voland34:
Getting adb connection: maybe useful to someone

Hi. Trying to customize Fire 7 5th gen to my kid for Xmas, flashed custom RR rom with fireflash; i might have done incorrectly the wipes, as it didn't seem to flash it (went very fast) and rebooted into amazon logo, stuck there since.

So i had previously adb enabled, of course, booted into stock recovery, but adb connection wasn't working anymore, so i couldnt sideload stock firmware.I tried everything in forums (reinstalling adb drivers and so) and still Fire couldn't get recognized, no adb drivers show.ed. But then i plugged my Moto g and it showed adb drivers just fine. So i plugged Fire 7 at the same time, in another usb port, and then: voilá! device got indentified; unplugged my Moto G, and it kept adb conexion with Fire so i've finally been able to sideload stock firmware and everything's working fine again.

Just sharing in case it might be useful to others in my situation.
[Fire General] faizul_emizal:
My Kindle Fire was with Fire Nexus ROM.

Try to install xposed framework zip through SuperTool

Now stuck at Fire Nexus ROM boot screen.

I still can enter stock recovery.

How to flash back Fire Nexus ROM without FireFlash?
[Fire General] DB126:
You will need to restore FireOS and start over. See below for video guidance. Be sure to restore the same version of FireOS that was on your device when Nexus was flashed. Do not attempt to downgrade; device will likely brick.

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

Edit: everything you need can be found the OP (first post in this thread).
[Fire General] faizul_emizal:
Thanks you for your reply Davey126.

I already go through the index post of Amazon Fire 7.

I also already try the video guide before post in here.

When i try to flash through adb siteload with same firmware version before Nexus nothing flash.

My firmware version before flash Nexus is 5.3.1.

I try with both windows and linux machine but still the same

I think the adb working fine and display the device id and sideload status when i run adb devices command.

Already fix can't sideload by using macbook
[Fire General] DB126:
Unfortunately I do not have any further suggestions. If FireOS can not be reloaded/sideloaded it will be difficult/impossible to recovery the device. Contact Amazon for a courtesy exchange if still under warranty.
[Fire General] amerkiller1995:
Please edit the first post, specifically the Downgrading Options part, to include information about 5.3.2.1 (not downgrade-able) and 5.3.2.0 (downgrade-able) for completeness.
[Fire General] kbza_98:
Unbrick/undo a realy bad downgrade...

Hi guys, I have a 7" fire 5th gen with fire OS 5.3.2.1, stupidly i tried to downgrade to 5.3.1.0. Now the tablet is bricked obviously, but after a whole night of forum research i found here a low level access using python's scripts that allows me to read/write directly to the mmc memory... but i need the correct files to flash.

These files would be something like "lk_5321.bin", if i'm seen this in the right way.. but my knowledge of the android file system is realy poor... can i extract these files from the 5.3.2.1 stock rom? any information will be very apreciated!

Sorry if i misspelled something, my english isn't the best.

(Amazon replacement waranty is the last option, cause i'm realy realy far from where the tablet was bought, and here not even exist amazon services :P)

Thanks for advance!
[Fire General] JoBByZ:
I've got your same problem, but I think that the only way to unbrick its is to bring the tablet at Amazon...
[Fire General] sd_shadow:
doesn't work see

http://xdaforums.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747/
[Fire General] alzabir:
I did same thing as you did and tried to use the Python script and even the Linux ISO of [MENTION=4469251]powerpoint45[/MENTION], My device got handshaked, but while reading/writing there was type mismatch error. The solution was for downgrading of 5.1.1 to 5.0.1. Does not seem to work with 5.3.2.1 to 5.3.1.0.

I am also too far away from Amazon service for returning it, We may have to wait for updated Python script or something like that

If anyone has any new solution, please provide

Regards
[Fire General] seth.dean02:
My fire doesn't boot into recovery?
[Fire General] sd_shadow:
Nothing can be done about that, except keep trying
[Fire General] steve8x8:
It is not possible to flash fireOS 5.1.1 over 5.1.2 (well, it is, but the outcome is undesirable).

If you're lucky you may install 5.1.2 (e.g using the supertool that was made for that).

The general rule: etch the last fireOS version into the back cover, and if you have to go back, always use that version.

Never try to roll back to a previous version unless that's explicitly documented to work - there are only a few cases.

P.S. Your usage of "Android" vs "Amazon OS" is confusing, in particular due to overlapping version number ranges. FireOS is an Android flavor, and as such also an incarnation of "Lollipop". (If you were using CM or Nexus or whichever custom ROM, please name that.)
[Fire General] DB126:
Annoying crosspost; answered here (and above).
[Fire General] anatoliy@forex.ua:
I using CM-12.1 for Amazon Fire 7" 2015 Tablet

https://xdaforums.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416
[Fire General] DB126:
From this post it's game over. Device is bricked; no known recovery. Dust bin or sell it for parts.
[Fire General] Mr McBoatface:
If you're in the US there is an eBay seller that is selling "defective" SV98LN (fire 7 ) mothereboards. The boards themselves are functioning 100% but serial numbers are blocked by amazon so can't register with them. They are cheap, I've been reliably informed a 7 dollar best offer could be accepted on them :) shipping outside of the US would add significantly to the cost of these so may not be worth it useless you like getting your hands dirty . There are several fire 7 "working" with broke screens going cheap too on eBay.

The fire 7 looks easy enough to open and switching out the boards should be very easy. The motherboards are most likely on an old fire OS that can manually upgraded to latest rootable fire OS. I fancy having a crack at this myself, I've a bid on a fire 7 with a broke USB port...

Im not posting ebay links here as not sure if it's against any site rules .... I'm not affiliated with the seller. Shouldn't be hard to find on eBay if you go looking.
[Fire General] davidasdf:
Kindle fire 7 5th was downgraded from 5.3.1 to 5.1.2, but it became a brick.

I have kindle fire 7 5th.

Kindle fire 7 5th was downgraded from 5.3.1 to 5.1.2, but it became a brick.

The current state is not booting, and only black screen is displayed continuously. However, if you connect to a PC, you will get periodic connection and dropping symptoms.

If you know how to recover, please help.
[Fire General] sd_shadow:
If it cannot be booted to recovery, there is no fix
[Fire General] DeLonge:
is it safe to downgrade from 5.1.3 to 5.1.2?
[Fire General] sd_shadow:
yes, fairly safe
[Fire General] Mr McBoatface:
Yeah it's safe enough to do but you could try root 5.1.3 with the Kingroot linked to and mentioned in my posts below.

https://xdaforums.com/showpost.php?p=70853398&postcount=18

https://xdaforums.com/showpost.php?p=70853958&postcount=20

5.1.4 was unrootable until i tired that , you might have luck with 5.1.3
[Fire General] DeLonge:
Thanks for the info. Confirmed, I'm able to root directly from 5.1.3
[Fire General] ieatabiscuit:
Ok, so I found out the hard way that my fire updated to 5.3.2.1 without me knowing about it. I downgraded to root it, and it's now a paperweight. I can't use the current method to unbrick from that point as it blocks read/write via ADB once I get a handshake. Anyone have any experience using JTAG to get any progress made?
[Fire General] BeeWall:
For now, there is no way to recover. Exchange it if it's still under warranty, if not, set it down and wait for someone to think of something.
[Fire General] ieatabiscuit:
That's what I figured, just wanted to see if there was any news. It's going back in a drawer for a few months, and I'll check back and hope.
[Fire General] risk_arg:
New Kindle Fire 5.3.2.1

I have a Kindle Fire 5.3.2.1 version that is fully functional. So I want to know if booting the tablet in rescue mode and put and old image of kindle for rooting and then change it for other room will be possible, or will brick the tablet.

Thanks.
[Fire General] BeeWall:
It will brick.
[Fire General] countthesaints:
Oops, wish I would have seen this before I decided to attempt to downgrade. Looks like I'll be waiting for my replacement device now.
[Fire General] kelvinsin:
I met the same nightmare by downgrade the firmware from 5.3.2.1 with adp sideload and now its bricked. Oh gosh...may i know any method can recover from bricked?
[Fire General] Mr McBoatface:
No recovery method. If in warranty return to Amazon.
[Fire General] Chewieez:
My Kindle Fire 7" has been running fine but today entered a soft brick, I believe after trying to convert a apk to a system file.

My problem is I do not remember what firmware I am on. I think I'm on 5.1.2. I have had the tablet rooted, but still running FireOS and use Nova. Is there a way I can confirm the firmware via adb? I can only connect via adb sideload mode in the bootloader. I tried using adb in fastboot mode but it won't work. Adb sideload seems to be the only thing that works. I'm leary to restore using 5.1.2 firmware in case I was no on that firmware before.

One idea I have is to upgrade my firmware to 5.3.1. Can I do that using the same method as a restore? I have downloaded the 5.3.1 firmware. Do I just adb sideload it and let it run? Then keep wifi off and run the SuperTool to root and block OTA?

Thank you!!
[Fire General] sd_shadow:
as long as it wasn't higher than 5.1.4

5.1.2 is fine

if unsure use 5.3.1
[Fire General] GEORGEGeek:
i'm bricked unauthorised device can't go after amazon logo no power volume down not working what to do was on 5.3.2.1 new fire tablet 1 day old :@ tried to flash cm12 as in video now even while turned off connecting with usb says mtp usb device this device can not start
[Fire General] DB126:
Device is permanently bricked; no known recovery. Contact Amazon for an exchange if still under warranty.
[Fire General] CLWhit:
Never mind - didn't read far enough in the thread! I'll order a replacement.
[Fire General] lh94:
Unbricking 5.1.1?

Is there a way to unbrick OS 5.1.1? There's no way to access recovery mode so I'm hoping someone can provide a method for this.
[Fire General] DB126:
How did it become bricked? Actually a retorical question as there is no known method to unbrick a 5th gen Ford if stock recovery is inaccessible.
[Fire General] WilliamTheKingAS:
They said when I tried returning it that it was out of the 90 day warranty. I just want another tablet. Help
[Fire General] sd_shadow:
There is nothing to be done.
[Fire General] SirTurbo:
I have a 5thGen, at which i killed the stock recovery by trying to install TWRP. Cant boot to recovery anymore: Not to TWRP maybe because of locked bootloader. Not to stock because it was overwritten by TWRP.

At the moment it is NOT bricked, the custom rom still boots. But for the future i would like to have a recovery again...

May i get the stock recovery from somewhere so that i can flash it by a temp TWRP, just like i flashed the working rom?

Thanks.
[Fire General] sd_shadow:
sure if we had a signed copy of recovery.img, which we don't have

edit: see you got it fixed

lucky you had 5.0.1 bootloader
[Fire General] SirTurbo:
yup, some times i have luck:)

If anyone is looking later on for the image which saved "my" tablet an find this posts: i took stock-recovery.img out of AmazonFire5thGenSuperTool.
[Fire General] Hallo32:
[MENTION=4267571]sd_shadow[/MENTION]

Are there any information, that the fastboot boot command is still working with a signed recovery.img?
[Fire General] DB126:
Assume you are referring to the fastboot parameter that permits booting to a custom recovery environment. If accurate it works with bootloader builds 5.0.x; nothing above that.

To the best of my knowledge stock recovery can not be flashed independent of the bootloader as the latter remains locked.
[Fire General] Alaxmofo:
Can I get instructions for doing this restore to fireos on Linux? I have a raspberry pi 3 with raspbian on it but, adb won't detect the tablet in stock recovery. I had fireos 5.1.1 and went to slimlp.
[Fire General] DB126:
I am not aware of any formal write-up or video specific to Linux. Watch the Mac and PC restoration (reload/sideload) videos in linked the OP. Procedure will be very similar on Linux.
[Fire General] billswild00:
Followed the instructions to the letter and somehow ended up bricked. I have no idea how. The entire process went exactly like RootJunky's video showed. How could I have ended up bricked when I did everything like it said?
[Fire General] sd_shadow:
Unfortunately bricking happens sometimes, for no apparent reason.

Likely causes

wrong firmware version (which resulted in a failed downgrading of firmware)

bad downloaded firmware/ corrupt file

bad usb connection (device port, cable or pc port)

some other flash error on device or pc

there are so many different things that can go wrong
[Fire General] billswild00:
Thanks for the quick response. Bad USB connection is the only likely answer as I verified that I was on 5.1.1 and that I downloaded 5.1.1 and I even verified the MD5. Frustrating.
[Fire General] sd_shadow:
How did you verify 5.1.1?
[Fire General] billswild00:
My root checker app.
[Fire General] DB126:
5.1.1 reported by your root checker app was almost certainly the underlying version of Android, not the version of FireOS. Sideloading FireOS 5.1.1 to a device that had FireOS (bootloader) >5.1.1 will result in an unrecoverable brick. Contact Amazon for a courtesy exchange if still in warranty.
[Fire General] sd_shadow:
Agreed, root checker app doesn't know anything about FireOS, its checking Android version, which isn't helpful in this case.
[Fire General] billswild00:
Aww man. Rookie mistake after all that research and careful planning! Now I'm really kicking myself. I know it's water under the bridge now but for the future, how would I have checked the version? Because I was rooted, it wasn't allowing me into the software update section of the settings.
[Fire General] DragonFire1024:
Once rooted, so far as i know, system updates aka OTA are disabled. So you wouldn't be able to do system updates through settings. I am not rooted and have disabled the OTA packages. When I go to system updates and tap the check updates, it tells me it failed. Win.
[Fire General] sd_shadow:
https://xdaforums.com/amazon-fire/development/identify-bootloader-version-t3424634
[Fire General] DB126:
The act of rooting (obtaining root permissions) does not block OTA updates. The method used to accomplish the latter on Amazon devices determines if the current FireOS build is displayed when checking for updates via settings. Most OTA blocking tools, including the most popular ones on this forum, take a shotgun approach which are hard to reverse and carry side effects. The inability to display the current FireOS build is one of them.

However, it is the bootloader build that matters when deciding which versions of FireOS are safe to reload/sideload. [MENTION=4267571]sd_shadow[/MENTION] posted link to the relevant thread.
[Fire General] billswild00:
Curses. I should have verified my bootloader version instead of the Android version before flashing. How dumb do I have to be. :eek: I guess I'm learning from the mistake which is all you can do. Thank you for all of the helpful responses.
[Fire General] DB126:
Not "dumb" at all - just ignorant (not a derogatory reference!). Most of us are ignorant about the vast majority the world that we live it with small points of light distinguishing various individuals. There is no shame in making a error; only a new learning opportunity and another small point of light.
[Fire General] midnight102:
i am stuck on 6% help
[Fire General] midnight102:
I am stuck at 6% and I waited 30mins to complete
[Fire General] sd_shadow:
Did you check device manager, to see if its still using the correct driver
[Fire General] midnight102:
what am looking I for?

---------- Post added at 09:37 PM ---------- Previous post was at 09:18 PM ----------

Nevermind read your first post I tried to manually install the driver but I don't see Android device only ADB device

---------- Post added at 09:41 PM ---------- Previous post was at 09:37 PM ----------

It shows up as universal serial bus device
[Fire General] skyla20:
Hi guys, i have pretty much wiped my amazon fire tablet 7 5th generation accidentally through twrp. All i have on screen is the white amazon logo and nothing else loads up. I can enter recovery mode and fastboot mode however, when i enter recovery mode and choose the apply update from adb nothing happens and the file on my pc is not found. I have attached a picture of what comes up on my screen.

Is it possible to restore the factory operating system from the pc? I have tried to follow the rootjunkys tutorial however, i cannot get it to find the .bin file on my pc.

Any help would be appreciated.
[Fire General] DragonFire1024:
In your recovery screen wipe cache, then factory reset. Power down then power on. Restart could take 10 minutes, sometimes a bit more or less. You have to wait for the optimizing applications screen appears. Should boot thereafter...presumably.
[Fire General] sd_shadow:
See

Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
[Fire General] sd_shadow:
Yes, so select the correct driver
[Fire General] skyla20:
I tried it however, it never worked. I just remembered and forgot to say i rooted the device and wiped the amazon os to put nova on through the supertool. However, once it was installed i tried to factory remove nova and install amazon os again from the supertool because nova made my screen constantly blink. From there it went all haywire. Sorry guys im a newbie when it comes to this.

---------- Post added at 07:45 PM ---------- Previous post was at 07:43 PM ----------

I will give this ago and get back to you.
[Fire General] skyla20:
I tried this, however, its really confusing and there are additional links that take you to other pages and I ended up getting lost, to be honest.
[Fire General] skyla20:
I have managed to restore the stock firmware back to 5.1.1 through adb sideload.

1. Restore the stock firmware back to 5.1.1 through adb sideload.

2. I downloaded and installed the 'adb-setup 1.4.3 exe file found on this forum – Click ‘Y’ to all options that are on the blue screen.

3. I then downloaded the 5.1.1 firmware from root junky. My fire was previously on this firmware before it became unusable. http://rootjunkysdl.com/files/?dir=Amazon Fire 5th gen/Firmware

4. Once installed I connected my fire tablet 7 5th generation to my windows laptop powered into recovery.

5. Wipe data/factory reset.

6. Wipe cache partition.

7. I then selected the ‘apply update with adb’ option in recovery mode on the amazon fire 7 tablet 5th gen.

8. Using my windows laptop, I opened the Windows command prompt (CMD) (commands are recognised after running adb-setup 1.4.3).

9. Once opened I used the following command ‘adb devices’, this was to see if my fire was recognised and it was within the command prompt.

10. I then typed ‘adb sideload’ and dragged the 5.1.1 firmware into the command prompt next to where I had typed 'adb sideload' in the command prompt and hit enter.

11. My amazon fire then was installing the package and it took about 10 minutes. Exit from CMD and then hit reboot device on the fire tablet.

I'm not sure if this process will work to downgrade from 5.4.0.0 to 5.1.1. It would be great if it did so that you could root 5.1.1, block OTA updates on the tablet, and remove amazon os to install nova launcher.