yashsingh1/xdaforums huggingface dataset:
[Fire General] mrmazak:
You must have missed the current work do e since early this year. Am unlocked bootloader, twrp and updated lineageos.

No more flashfire. In fact with the hacked /unlocked bootloader it would make a brick.

All that aside, yes , to return to Amazon stock , yes flash the Amazon bin file with stock recovery, not fastboot.

I'm not sure which version s are safe to move back and forth from and too. But if last version was 5.3.1.0, then stay with that.
[Fire General] EtoileLabrie:
Actually I did TWRP as given on other threads. All is good. Like the clean LOS.

How do I get to stock recovery? Should I simply

Boot into recovery (Volume Down + Power at the same time)

update: this gives me TWRP.

Should I then, just go for

adb sideload firmware.bin

Many thanks

---------- Post added at 11:54 AM ---------- Previous post was at 11:27 AM ----------

Answering myself here:

from thread

https://xdaforums.com/amazon-fire/development/unlock-fire-t3899860
[Fire General] greeneyez15o:
What sudo ?
[Fire General] sd_shadow:
sudo is a program for Unix-like computer operating systems that allows users to run programs with the security privileges of another user, by default the superuser. It originally stood for "superuser do" as the older versions of sudo were designed to run commands only as the superuser. However, the later versions added support for running commands not only as the superuser but also as other (restricted) users, and thus it is also commonly expanded as "substitute user do". Although the latter case reflects its current functionality more accurately, sudo is still often called "superuser do" since it is so often used for administrative tasks.

https://en.m.wikipedia.org/wiki/Sudo
[Fire General] MattieBit:
Small problem with the script.

When i get to the sudo ./bootrom-step.sh of the instructons on my Gen 5 Amazon Fire , (Using method 2) it errors out, with the runtime error saying "RuntimeError : ERROR: Serial protocal mismach", I have no clue where to go from here.
[Fire General] Echoecho33:
Hello there. I believe you responded to a post of mine on another thread.

I am the one that screwed up my rooted Fire (5th) by deleting the Kindle app. Everything else on the device works fine.

As my attempt to use Flashfire and another ROM (in order to just download "Kindle for Android" is not currently working, I am trying to figure out what the actual file name of the Kindle (apk?) app as it originally existed on the Fire was in hopes that I can re-download it from somewhere. My searches for "Kindle for Fire" (etc) give me nothing.

So this is a three part question: 1 What is the name of that original file.

2 Where can I attempt to redownload that file

or 3 do you have any idea of what kind of other OS I can attempt to install (instead of the FireOS) in order to go back to my original plan?

Thank you for any help you can give me
[Fire General] DB126:
Do some research on the Aurora Store (it's legit) which should install/run on your device. You can install a recent build of the Android Kindle app from there. Note the Android variant does not have the same feature/functionality as the native app that ships with Fire tablets. This is by design (thanks, Amazon) but it supports basic reading capabilities.

https://f-droid.org/en/packages/com.aurora.store/
[Fire General] zz2003:
Did this and it seems to have bricked my tablet. Everything went fine. Selected reboot and the screen is all black showing nothing at all. What can I do now?
[Fire General] sd_shadow:
Most likely you used wrong firmware, but it may have been a corrupt file or bad usb connection or a number of things.

Most of the Fire(s) bootloader can now be unlocked, which part of those steps may fix your device. If you have a 5th gen (2015) device look for the "ford" bootloader unlocking thread.
[Fire General] sd_shadow:
https://xdaforums.com/amazon-fire/development/unlock-fire-t3899860
[Fire General] Dav_Daddy:
I could use a little help. I ran the battery down on my 5th gen Fire. Afterward it has bootlooped going from a black and white Amazon logo to a triangle with an "!" in it. I was uprooted stock ROM (probably the latest) but I had GApps installed.

I can get into recovery but I get a bunch of error messages like:

E:failed to mount cache (invalid argument)

I can get into adb sideload but when I try to push a stock ROM to it I get more of the above messages on the tablet while the PC just says:

Total xfer: 0.00x

I can get into fastboot is there a zip I can put on an SD card that will get me back up on stock fireOS? I really don't want to run a custom ROM or even root. All I use the thing for is as a digital dashboard on my Sim racing rig. I've become really dependant on it and am lost without it.

Thanks
[Fire General] Dav_Daddy:
Okay I made a little progress. I've got into fastboot and I can get my pc to talk to my device.

Unfortunately anything useful I try to do like:

./fastboot oem format

or

./fastboot erase cache

I get:

FAILED (remote: 'the command you input is restricted on locked hw')

I haven't been brave enough to try and reflash the stock firmware this way yet. I'm fairly sure with the locked its not going to let me.

Anybody got any ideas?
[Fire General] johnveaz:
for anyone having trouble with the drivers I highly recommend you download the one directly from amazon located here:

https://developer.amazon.com/public...etting-up-your-kindle-fire-tablet-for-testing

after installing this specific driver and going into device manager, under fire devices, I updated and selected the ADB composite driver and was finally able to get out of the boot loop I was stuck in :D
[Fire General] DB126:
Not that I am aware of; would defeat purpose of authorization. As you can't return it now keep an eye on the forums. Someone may come up with a clever solution given the number of devices in this condition.
[Fire General] cvt123:
Hi. Could you explain what you did exactly? I am a bit confused as to how updating the adb driver fixed a boot loop
[Fire General] sd_shadow:
fixing driver allows adb sideload to work, but you need to be able to boot to recovery
[Fire General] cvt123:
Ah. Gotcha. I am stuck with CM 12.1 boot logo and booting into recovery is not working (I just see recovery but not the options and it is not appearing).
[Fire General] PratNag:
I have the exact same problem stuck with the cm boot logo and cant go into recovery mode. Hoping a solution comes out soon.
[Fire General] DB126:
Solution is possible (anything is possible) but unlikely as it would likely involve a bootloader exploit which is a tough nut to crack. Even if identified it would be another high hurdle to get beyond the buttoned down bootloader currently on the (your) device.

Exercise the courtesy exchange if device is still in warranty (90 days).
[Fire General] rigels89:
Booting into recovery can yoy see the recovery logo in the left-down side of the screen? my device shows only the amazon logo!

THe 5.0.1 Fire OS has nt a locked bootloader?
[Fire General] DB126:
Bootloader can not be unlocked (yet) on any 5th Gen Fire.
[Fire General] rigels89:
How Is it possible to use Twrp recovery in 5.0.1 and not in the 5.1.1 if the Bootloader is locked in both devices ? I dont understand ! I' m a noob!!:D
[Fire General] sd_shadow:
5.0.1 allows booting unsigned recovery.img
[Fire General] blackhaya:
I had the fire os 5.0.1 build date november 13, 2015, 1:32am gmt-5, which firmware file I need to download?

user_522054520 or user_522053820?
[Fire General] sd_shadow:
either should be fine, but the 4520 is the newest 5.0.1
[Fire General] percussionking:
When you see the Amazon logo, let off the Power button but keep holding the Volume button.
[Fire General] qtotter:
http://xdaforums.com/showpost.php?p=65234773&postcount=1772

(gosh... just found it's been almost 10 years since i joined xda... time flies...)
[Fire General] FireBill:
(For those of us that can't get into recovery) if we had a stock rom with a scatter file in it we could possibly use sp tools to flash....
[Fire General] sd_shadow:
don't think anyone has gotten sp tools to work
[Fire General] Kevin JRQ:
Full brick

Hey man. I need your help. My Amazon Fire 5th gen is completely brick. I can even start in fatsboot or recovery mode. I'm desesperate. Please help me. :(:confused:
[Fire General] FireBill:
From my chats with china devices and sp tool guys it looks like having a locked bootloader is an issue. As for the devices that they use sp tools on all have unlocked bootloaders. I have the MT8127 scatter file in my possession but not going to attempt a flash with the current rom from amazon as it's missing firmware.info and MD5 files. Don't want to completely brick that already bricked device. lol That's exactly why android MTK tools won't read. So for now I leave it up to the pros.
[Fire General] sd_shadow:
no known fix
[Fire General] rigels89:
I think definitely we are hopeless to unbrick this table.nobody knows how? Amazon won

Any method to delete the cyanogen logo ? I want to try with the warranty but i cant with cm logo
[Fire General] sd_shadow:
Amazon doesn't care about the cyanogenmod logo
[Fire General] rigels89:
How do you know. Maybe in usa they dont care but in europe could be different. The warranty also .
[Fire General] DB126:
Nice - get a clue who you are challenging.
[Fire General] sd_shadow:
I would call amazon and ask
[Fire General] Samson Lau:
I did according your instruction, but it returned error. Any idea?

My device - OS 5.0.1

I tried update-kindle-37.5.2.2_user_522053820.bin & update-kindle-37.5.2.2_user_522054520.bin.

*** Seem problem come from bin files. Will download again & try again
[Fire General] sd_shadow:
just install using twrp Unbrick/Restore Stock 2015 Amazon Fire (KFFOWI/Ford) with custom recovery
[Fire General] Theta1996:
One-time replacement?

Is this one-time, no questions asked replacement available world wide? I just bricked my Fire and it's stuck in a bootloop with a locked bootloader (thanks 5.1.1, really appreciate that lockdown!) and I've been looking for a way to fix this for the last three hours.
[Fire General] DB126:
Best answer comes from the horses mouth - contact Amazon.
[Fire General] jonathanjr321:
hey my adb say devices authorized but i do not know what to do next

hey my adb say devices authorized but i do not know what to do next

---------- Post added at 07:48 PM ---------- Previous post was at 07:44 PM ----------

5.0.1 u get everything easy just supertool boot to recovery twrp and then flash anything lol

---------- Post added at 08:04 PM ---------- Previous post was at 07:48 PM ----------

hi guys i have same problem with flash fire just with amazon 5.1.1 cos is working perfect to flash anything out, thanks to sd_shadow and root junky both working hard for this tablet also I tried almost everything too I hope that we can work together to unbrick 5th gen lol. someone already replaced the tablet with amazon??? Is there anything else we can do????
[Fire General] rigels89:
Try "adb sideload update_filename.bin" if u have not tried yet.
[Fire General] jonathanjr321:
I can not boot into the recovery (5.1.1)

List of devices attached

C:\Program Files\Android\android-sdk\platform-tools>adb devices

List of devices attached

G0K0H404543202AT device

C:\Program Files\Android\android-sdk\platform-tools>adb sideload update-kindle-g

lobal-37.5.4.1_user_541112720.bin

loading: 'update-kindle-global-37.5.4.1_user_541112720.bin'

error: closed

C:\Program Files\Android\android-sdk\platform-tools>adb sideload update-kindle-g

lobal-37.5.4.1_user_541112720.bin

loading: 'update-kindle-global-37.5.4.1_user_541112720.bin'

error: closed

I can not boot into the recovery (5.1.1) :( I tried this with the kindle off.....
[Fire General] sd_shadow:
sideload only works with recovery mode
[Fire General] DB126:
Amazon will allow a one time courtesy exchange for 'bricked' devices within warranty period (90 days). Might be the best path.
[Fire General] pfoneguy1:
Are most of these bricks stemming from flashing the ROM with flashfire and not moving the wipe to the top?

On another note I wanted to flash CM12 using flashfire, but I am currently on SlimRom. I really did not want to have to revert all the way back to stock fire OS or is this the only way to do this and not brick the device? No flashing a ROM while the device is currently flashed with a custom ROM?
[Fire General] DB126:
Speculation is leaving 'wipe' at bottom (when it includes anything other than cache/dalvik options) plus using older versions of FlashFire (<0.26) are the primary culprits. Since then there have been scattered reports of difficulty moving from SlipLP -> CM. Hard to pin down root cause as user actions/options play a big part and few think to catch a screenshot of the FlashFire config before committing. Regardless of device/tool any rom switch should be treated as a 'clean' install. If using FlashFire System Data, 3rd Party apps, Dalvik and Cache should all be selected with Wipe being moved to the top just prior to hitting 'Flash'. Even then there are no guarantees. Every system update, whether done via FlashFire, OTA or TWRP (or other custom recovery), carries a certain level of risk. FlashFire is perhaps the riskiest as the tool is still in beta as evidenced by the leading zero in the version ID.
[Fire General] dmolina007:
Poor Little ME

I made the biggest mistake. So my friend gave me his kindle fire 5th gen since he knew i did not have a tablet. So the kindle os is so lame. Having flashed other devices in the past i was like cool. I can change the rom to something else. So i came across some images for recovery and boot images for the kindle fire 7 HD. not realizing they are not the same kindle fire device i destroyed the recovery image and I get boot loops of the amazon logo. I have done research on how i can possible recover from this and so far no luck. I can enter fast boot mode but cannot enter the os to enable usb debugging. If someone has any clue how I can fix this please share.

Thank You

The TabletLess Man :(
[Fire General] DB126:
As you received the device with FireOS installed/active it almost certainly self updated to v5.1.1. That limits tethered recovery options due to bootloader restrictions. If you can't bring up stock recovery via [power]+[vol-up] little can be done until someone figures out how to unlock the bootloader. Sorry for your loss.
[Fire General] kowalskicody42:
Amazon Fire 5th Gen Bricked

I had bricked my amazon fire 5th gen by installing the wrong firmware (i was on 5.1.1 when i installed slimlp and tryed to install 5.0.1) and now it wont boot :crying: ......Someone had said that I hard bricked it :p is there anyway to restore it to amazon bellini 5.1.1???? tnx - Kowalskicody42
[Fire General] DB126:
There are no (broadly communicated) unbrick solutions for an attempted 5.1.1 -> 5.0.1 downgrade. If within warranty contact Amazon for a one time courtesy exchange.
[Fire General] crashergate1:
but if u cant get into your recovery by pressing power and down button how can we restore anything?

---------- Post added at 07:47 PM ---------- Previous post was at 07:34 PM ----------

but we cant get into recovery (power and button down) has anyone else solved this beside sending the tablet back
[Fire General] DB126:
No known solution if stock recovery is missing and bootloader version > 5.0.1
[Fire General] crashergate1:
sounds like everyoneis having this problem.. any more info about it..
[Fire General] DB126:
Not everyone. Primary cause of soft-bricks when installing CM is improper use of FlashFire.

Key points:

- be sure to use the most recent version of FlashFire (0.26 or above)

- wipe option MUST be first in operations sequence; leaving it last is just asking for a brick

Also fair to say that failed flashes that also disable the recovery partition are a characteristic of CM and are rarely/never seen when flashing other roms (Nexus, SlimLP, etc) with FlashFire.
[Fire General] amlothi:
I have a slightly different issue with my 5.1.1 device. I can get into recovery, and wipe cash or do system restore. However, when I get into the system, I can only access settings and some apps via the search bar. Home button goes to black screen on CM 12.1. If I enable root and try to get to fireflash, it doesn't recognize root or request it. (It seems to need a device reboot as I had that problem on first install.) But, once I enable root in CM settings and reboot, I get stuck at CM logo.

I can get to recovery and set tablet to accept ADB sideload but it doesn't connect to PC. It says no device. I have ADB setup correctly with drivers (used it to root the device).

Any ideas?
[Fire General] DB126:
Seems like you have a partial bork of latest CM flash. My leaning would be toward restoring FireOS via ADB sideload which I realize is a challenge given you can not connect. I would continue to work this angle vs. trying to reflash a custom rom (if you eventually get root) as FlashFire may not behave predictably. If you are within warranty try for a courtesy exchange from Amazon as I question the integrity of the recovery partition. Nothing can be done about that (locked bootloader); if not whole it will likely come back to bite you.
[Fire General] amlothi:
I can connect via ADB once I get the tablet to boot, it sees the device, but it won't let me sideload. It just gives an error. I have the CM settings set to allow root through ADB, but I'm guessing I cannot sideload in this state. I have tried repeatedly and cannot get it to connect when in recovery with ADB sideload. Any suggestions on how to get it to connect?
[Fire General] DB126:
Unfortunately, no. Hopefully someone more experienced/familiar pops in. I have yet to use this feature on my 2015 Fires (all can boot twrp) beyond verifying that it exists.
[Fire General] sd_shadow:
did you verify correct drivers selected in device manager?
[Fire General] sd_shadow:
when in recovery's adb sideload mode?
[Fire General] amlothi:
That might have done it. It wasn't recognizing the drivers and I had to manually install them when it was in adb sideload mode. It appears to be loading the .bin file now.
[Fire General] BransonH:
Not to be that guy, but seriously how is it improper use of Flashfire when you follow up saying that this is not something that happens with other ROMS? I get that flashfire adds to this, but let's be real this is an issue with CM and Amazon locking the bootloader. CM may be all well and good, but it's not something that should be used currently.
[Fire General] amlothi:
Thanks Shadow! The restore to FireOS worked. Unfortunately, I grabbed the updated 5.1.2 as the instructions said to always grab the newest one. Not able to root as I did before. I'll probably send it back now and get another.
[Fire General] DB126:
There are several different failure scenarios; documenting them all in a humongous decision tree creates a long post that no one will read. Thoughts:

- flashing CM with TWRP is fine

- there are many successful CM flashes and subsequent updates with FlashFire

- that said, evidence is mounting that CM should not be installed/updated via FlashFire given the non-trivial number of unexplained failures

- CM flash failures are aggravated by the concurrent loss of access to the stock recovery partition which effectively leaves the device in a 'soft brick' state

- the recovery partition remains accessible when FlashFire operations fail with other ROMs; FireOS can be reloaded to recover the device

- there have been several theories why CM installation/update failures occur; each seemed promising at first but then proved to be no panacea

- recent updates to FlashFire (v0.26 and above) focused on improving the reliability of CM flashes on multiple device types

- the updates have reduced but not eliminates unfavorable outcomes

- this is a dynamic situation with recommendations being made based on the most current information

- the post you quoted is 11 days old; a lot has changed since then

The real issue is not CM nor Amazon locking the bootloader which is common practice and fully understandable given Amazon's business and customer support objectives. There is an interaction between CM and FlashFire that is not fully understood. The real issue IMO is the destruction of the recovery partition (more accurately access to the recovery partition) by FlashFire that differentiates failed CM flashes from other ROMs.
[Fire General] BransonH:
My point is, and will remain, that as you put it the recovery partition remains even when FlashFire fails on other ROMS then this would indicate the issue is with CM and not anything else.

Think about it for a second, if NO OTHER ROM is having this issue, no other ROM is causing the recovery partition to be overwritten or be inaccessible, if Flashfire is working on SLIM LP and Nexus with no issues, but not on CM, then how is the issue not with CM? Something that you seem to acknowledge by stating that there is growing evidence that CM should not be installed via Flashfire.

I also cannot agree that Amazon locking the bootloader should just be okay. I get why they did it, I nor anyone else can stop it, but it shouldn't be something we just say is okay. It's not. They took a open source piece of software and walled it off. And let's be honest, they did this after the device was already released, and something tells me it has to do with people finding a way to get around their ads. It is what it is, but it's not something we should encourage or be okay with.

On one final point, "a lot has changed since then?" What? What has changed? Is CM still not soft bricking devices? Is the bootloader still locked? Has anyone found a way around it? Last I checked the answers to all of these are the same as they were 11 days ago. people are still getting stuck with soft bricked devices because they think that CM is an acceptable ROM for the Fire. IMO it is not. It has been proven, multiple times at this point, to be failing and worse than that it is blocking people out from being able to fix their device via recovery . This is something that is not happening with any other ROM, as by your own admittance. This is a problem, and one that needs to be addressed, and more importantly should be the first thing that is said in the OP regarding CM (not your problem, just saying). But either way, nothing has really changed, other than more people running into this issue. The only good news with that is that there will be more invested in ensuring that this issue get's resolved. But let's all be honest, with the locked bootloader the only real resolution we have, and probably will have, is to have the device replaced. Something many of us, at this point, cannot do.
[Fire General] DB126:
Sorry for your frustrations. Your contribution (and mine) will remain for others to read/consider.
[Fire General] Mattye81:
Not charging

Hey guys, not been on since having a working version of CM12, but it now wont charge. Plug it in and all it does is loop round and round get to CM symbol turns off and starts again, can boot up fastboot and recovery, but tells me there is not enough power to perform update or factory reset. Need help as I have an upset 6 year old with no tablet.
[Fire General] sd_shadow:
try booting twrp, twrp can charge battery, fastboot mode cannot
[Fire General] DB126:
Charging functionality lives in the kernel (locked); has nothing to do with ROM or anything you can tweak. If the device won't charge when powered down then you likely have a hardware problem that can not be resolved without changing components. Contact Amazon for a replacement if still in warranty. Otherwise refurbs are available on Amazon for <$30 USD.
[Fire General] Mattye81:
Cheers for the quick reply's, after 3 days of trying to get it to charge it seems to have looped itself to a charge screen ??, will keep you posted if it doesnt turn on at 100% percent.
[Fire General] sd_shadow:
true but a custom rom can cause issues sometimes

and not want to charge correctly, especially if battery is drained very low