yashsingh1/xdaforums huggingface dataset:
[HTC One A9] joeatx:
hi,

please try this:

boot in to Fastboot mode, power off your device, hold volume down and power (download mode)

connect via usb and you have installed fastboot on your computer.

check if connect:

fastboot devices

my output is: HT5B3BE07005

check CID:

fastboot oem readcid

my output is: (bootloader) cid: HTC__622

check MID:

fastboot oem readmid

my output is: (bootloader) mid: 2PQ910000

first you can try to install the stock recovery, you can downlod here the recovery.zip, extract this to recovery.img and put in to your fastboot folder.

flash the recovery.img: (i hope this match for your device)

fastboot flash recovery recovery.img

after this reboot download mode, and try a factory reset

I hope that's enough, perhaps you hereby already helped:)

if not we have to get for your device a factory.zip, with included a system.img
[HTC One A9] Noc4:
HT5BLBE01245 fastboot

CID: (bootloader) cid: BS_US001

MID:(bootloader) mid: 2PQ912000

i flashed the recovery and the screen shows up with a caution sign on a phone when trying to boot into recovery mode
[HTC One A9] Noc4:
GOT IT!

found a system.img

works now

thank you to all who replied!
[HTC One A9] Noc4:
Actually, could I get the recover.img for my version of the phone?
[HTC One A9] Ollider:
Failed attempt

So, I tried to do this, but when I got to the

fastboot flash recovery recovery.img

it gives me the following error:

error: cannot load 'recovery.zip'

Although the extracted .img file is spelled right, and is in the same folder.

All of the above worked as supposed, apart from the cid code being HTC__621
[HTC One A9] alray:
https://xdaforums.com/showpost.php?p=72573893&postcount=17
[Fire General] sd_shadow:
22 May 2016

version 0.32 is considered more stable than 0.33

default settings should be fine for both new installs and updates

Root Junky Video

Amazon Fire 5th gen 7in Slim Rom install on Fire OS 5 1 1 with FlashFire App

https://youtu.be/NaCBSuUuhRE

Official Chainfire FlashFire thread

http://xdaforums.com/general/paid-software/flashfire-t3075433

Google+

https://plus.google.com/u/0/communities/116661625291346007584

Alt downloads

https://www.chainfire.eu/

https://download.chainfire.eu/956/FlashFire/FlashFire-v0.31-20160405175326.apk

http://www.apkmirror.com/apk/chainfire/flashfire/

- Fresh Installation from FlashFire 0.27

- Click the Red + and choose 'Wipe'

- Ensure System data, 3rd party apps and Dalvik cache are CHECKED

- Click the Red + button and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Cyanogenmod Zip

- Ensure Auto-mount and Mount /system read/write are UNCHECKED

- Click the Red + button again and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Open Gapps Zip.

- Ensure Auto-mount is UNCHECKED

- Ensure Mount /system read/write is CHECKED

- Move "Wipe" to the Top of the order

- Press the big FLASH button.

Upgrading from FlashFire 0.27

- Click the Red + button and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Cyanogenmod Zip

- Click the Red + button again and choose 'Flash ZIP/OTA'

- Navigate to and choose the latest Open Gapps Zip.

- Ensure Auto-mount is UNCHECKED

- Ensure Mount /system read/write is CHECKED

- Click the Red + again and choose 'Wipe'

- ONLY tick Dalvik and Cache.

- Press the big FLASH button.

Installing gapps on Stock Rom Root Required

Wiping should not be necessary.

[url]http://opengapps.org/[/URL] Arm | 5.1.1 | Micro, Nano or Pico

Instructions

Install the app

Download gapps

Open FlashFire app

Allow root access

tap red circle with + in it (bottom right)

Select Flash ZIP or OTA

browse to Gaaps.zip

I didn't check Auto-mount

Tap Check make (top right)

tap red circle with + in it (bottom right)

browse to Gapps.zip

Shouldn't need to check Auto-mount

Select Flash

Ok

Screen will go black for second or so.

Then a lot of code will run through screen

Then you will see normal scripts for gapps install

Device will reboot
[Fire General] sd_shadow:
Changelog

29 April 2016

Added link to

http://www.apkmirror.com/apk/chainfire/flashfire/

13 May 2016: Current Version is 0.33

Unless otherwise noted, use newest version.

Files may need to be on internal storage, rather SD card.

16 April 2016

Added links to ChainFire's Blog...

Cleaned up post abit

Added instructions from CM12.1

20 March 2016

Due to so many brick devices, I recommend that those with 5.1.X bootloaders

do not install cm12.1

nexus and slim roms have caused far fewer issues

20 Feb 2016

Note:There is some risk if using on 5.1.X Bootlader

Some have reported bricking, when trying to install a rom, unclear what the cause is.

I'm still on 5.0.1 bootloader, and I am not going to update to 5.1.1

I have not seen a clear reason as to why Flashfire is bricking some and not others.

With the locked bootloader, Flashfire should not effect the stock recovery, but yet that seems to be the result in some cases.

There is not failsafe way to install any rom with Flashfire.

6 Jan 2016: Be sure that wipe option is listed first,

FlashFire places it as last task,

which will wipe system, and rom will no longer be usable.

and likely the cause of the bricking of fires with the 5.1.1 bootloader.

23 Jan 2016

Don't try to install a custom rom with a low battery

Original post #1

I was able to update SlimLP with just Flashfire

You need to accept being a tester

Install the app

Download rom, gapps...

Root Required

Open FlashFire app

Allow root access

Wipe

tap red circle with + in it (bottom right)

System Data: optional

3rd party apps like a Factory reset

Dalvik Cache: Recommended

Cache partition: Optional

Tap Check make (top right)

(continue for installing Rom)

tap red circle with + in it (bottom right)

Select Flash ZIP or OTA

browse to rom.zip

I didn't check Auto-mount

Tap Check make (top right)

tap red circle with + in it (bottom right)

browse to Gapps.zip

I didn't check Auto-mount

Tap Check-mark (top right)

Select EverRoot

Check Inject SuperSU

Tap Check-mark (Top Right)

scroll down to bottom

Select Flash

Ok

Screen will go black for second or so.

Then a lot of code will run through screen

Then you will normal scripts for rom install (gapps)

Device will reboot

When I tried to install CM12.1 over SlimLP

FlashFire got stuck installing

Maybe possible, just need to select correct settings
[Fire General] sd_shadow:
next
[Fire General] 4t701:
When it got stuck installing CM what happened..? Were you able to just reboot? Or did it corrupt the install and you had to reflash via TWRP/CM?
[Fire General] blueberry.sky:
Wonder if it will work from within FireOS 5.0.1.
[Fire General] sd_shadow:
I just forced power off, and then I booted it into fastboot mode.
[Fire General] sd_shadow:
Failed to install stock over SlimLP, just reboots to SlimLP

Could just need a different install script for stock.
[Fire General] sd_shadow:
I haven't tried installing a rom in stock yet.

In Stock 5.0.1, restore SlimLP worked, but it took a while, I thought it was stuck, ,but just left it, came back later and it was running SlimLP just as I backed up

backup was created with FlashFire, haven't tested Twrp created backup with FlashFire, but don't think it will be compatible.
[Fire General] sd_shadow:
i wonder if I just didn't wait long enough? Didn't time it, thought it was about 10 mins?

Edit: in reference to the install
[Fire General] pbailey212:
I tried to use flash fire to create a backup of my modified stock from, and it ran some script, then went to a blank screen with flash fire on the top. It stayed like that for about 30 minutes before it rebooted, and there was no backup file. I thought I would try it. I would like to see if I can flash cm12.1 on stock. It was a $35 tablet, I don't mind trying stupid stuff with it.
[Fire General] Pond-life:
Blimey that's a long wait. Totally sure it didn't back it up anywhere, seems odd given how long it took?
[Fire General] pbailey212:
I got it to back up and restore on stock, now to try to install cm12, worst case scenario, I have to hook it up to my computer and install it through adb and twrp
[Fire General] 4t701:
I dirty flashed CM latest build, gapps.zip, and superSU.zip yesterday. Everything worked perfectly. It only took like a minute to flash all 3 of those zips. No frozen screen or unresponsiveness. No issues with the new CM install or gapps.

Only things I did different from you [MENTION=4267571]sd_shadow[/MENTION] was I only wiped dalvik cache and cache partition, I did check 'automount' feature on all 3 of my .zips, and I didn't use the EverRoot to inject superSU into system (as I preferred to just flash the superSU.zip)
[Fire General] pbailey212:
Installing cm12 on stock didn't work. It stuck on the blank flas fire screen for over an hour, so I turned it off a d on and got stuck on the Cm boot screen. Oh weel. It was worth a shot
[Fire General] 4t701:
Did you guys use the 'automount' feature or no?
[Fire General] 4t701:
So I tried to flash SlimLP over my CM install...

-I wiped dalvik and cache partition.

-flashed SlimLP, checked 'automount'

-flashed my gapps.zip, checked 'automount'

-flashed SuperSU.zip, checked 'automount'

-FLASHED

-system reboots but hangs at boot animation forever like [MENTION=3947168]pbailey212[/MENTION]

So it appears FlashFire is only really useful if you are just using it to update your current CM or SlipLP install (or to flash xposed.zip or your gapps). Doesn't look like it can be used to flash a different ROM from what you are already on. Oh well, it's still pretty useful. Just wish it woulda worked for flashing a different ROM. That or our BL get unlocked so TWRP could be installed. If that ever happens this would be the perfect budget tablet. [emoji41]
[Fire General] Pond-life:
Well sd-shadow did get it to flash from CM to Slim in the second post on the thread, maybe you needed to wipe more as he did.

---------- Post added at 06:04 PM ---------- Previous post was at 06:00 PM ----------

Installing slim on stock did work. And restoring my stock back up after realising I really didn't like slim gapps.
[Fire General] 4t701:
Oh, yeah...I completely missed [MENTION=4267571]sd_shadow[/MENTION]s' post (#2) And yeah I didn't wipe system apps so I guess that's probably why it didn't work for me. Was gonna try that later after I had made a proper backup.
[Fire General] pbailey212:
I think my problem was I installed open gapps normal, I should have done pico. The normal is too large to fit in the system partition. I bet that's why it hung up on the flash fire screen. Its the same thing that happened when I tried to create a backup in the eternal storage
[Fire General] blueberry.sky:
So with FlashFire it is possible to flash custom roms without access to the fastboot boot command. If we can get root in 5.1.1 then we are back in business! Safestrap of course would be much better, safer.
[Fire General] Herox:
I think I might hold off. Today my kindle decided to reboot itself and then get caught in a boot loop optimizing apps. No clue whey. I reformatted and pushed 5.1.2 again and its all good again, but if it happens again I will try to switch OS for sure.
[Fire General] nashmarkt:
Fire 7" with 5.1.2 Rooted and installed Flashfire 0.50. Flashfire just opens and closes. Any ideas how to fix that?
[Fire General] DB126:
- upgrade to the latest release (here) ... 0.51 as of this posting

- reboot and try again
[Fire General] antennae:
Are we good on 0.51? Or should I just use old reliable 0.32?
[Fire General] daniel3016:
I had the same problem yesterday I installed the play store with the supertool and installed it from there. The foresaid incompatible but there was an update option I downloaded and updated and it worked. Cm 12 on it npw. I have done about 4-5 of them this way. Thanks root junky and everyone else involved!
[Fire General] DB126:
FlashFire 0.51+ is both stable and preferable to 0.32.
[Fire General] antennae:
Thanks for confirming. 0.52 dropped just before I attempted, I can confirm this version is working as well.
[Fire General] bojkoio:
Hi every one!

Tell me please, can I use FlashFire and install CM12.1 into my Kindle 7 with 5.3.2.1 without root device?
[Fire General] sd_shadow:
no FlashFire requires root, SuperSU to be precise
[Fire General] BossmanFU:
Has anyone figured out how to root 5.3.2.1 yet without PC? I've tried kingroot a dozen or so times with no luck
[Fire General] DB126:
As of now FireOS 5.3.2.1 can not be rooted or downgraded - with or without a PC.
[Fire General] BossmanFU:
Im sure someone will figure it out eventually lol
[Fire General] TechDad378:
I searched for a while and was only able to root 5.3.2.1 by downgrading to 5.3.1.0. Meaning a PC is needed. Once rooted ROMs, gapps can be added through flashfire.. The process is a little tedious but can be done.
[Fire General] DB126:
Others have consistently reported hard bricks downgrading FireOS 5.3.2.1 to any lower version. However, 5.3.2 (sans '.1' suffix) can successfully be rolled back to 5.3.1.0. Are you sure device had 5.3.2.1 and not 5.3.2?
[Fire General] TechDad378:
The device came preloaded with 5.3.1.0. After setting the device up for first time use, it automatically downloaded to the latest software (5.3.2.1), then it installed update while not in use.

I verified the current version before downgrade to be 5.3.2.1 within system updates.

Any thing I can provide with the downgrade process, please let me know.

Fyi... The biggest problem is KingRoot during the root process. But it can be rooted with a lot of patience.
[Fire General] DB126:
Appreciate the detail. Still going to advise against 5.3.2.1 -> 5.3.1.0 rollbacks given number of previous bricks. That said, your experience offers a point of light in an otherwise gloomy landscape for those recently updated to 5.3.2.1.
[Fire General] TechDad378:
With that said, would it be beneficial to create a tutorial from my experience?
[Fire General] DB126:
Not yet. I still believe your experience was an anomaly/outlier. A tutorial would imply the 5.3.2.10 -> 5.3.1.0 rollback procedure is reasonably safe which is in stark contrast to what others have reported. The alternative outcome is a hard brick with no known recovery.
[Fire General] TechDad378:
Understood! I just dislike locked bootloader. A locked one implies the device is not yours. Any information I can provide which leads to a custom recovery would be great.
[Fire General] DB126:
Unlocking the bootloader, custom kernels and/or bootable custom recoveries are a long shot IMHO. Rather fortunate to secure basic root as some Amazon devices haven't even seen that.
[Fire General] mainstang:
This is probably a dumb question but is there a way to wipe the internal sd card completely while flashing a custom rom via flash fire. I need to debloat some left over app files.
[Fire General] DB126:
Select internal storage as one of the wipe options. Note the wipe action must be positioned above any flash operations and all files used for flashing must be located on the external SD card. If the flash fails you will need to sideload FireOS to recover the tablet.
[Fire General] Samwest1:
"Checking for pro" and closes

OK, maybe someone can help me figure out if I'm messing up , or if flashfire won't work anymore on 5.1.2.

So I rooted my fire 7 2015 , downgraded from 5.1.4 to 5.1.2. Added playstore ,Used supertool to root with kingroot ,gained root,then supertool removed Kingroot and installed SuperSU. Then i used supertool to install flashfire. Flashfire installed, gained root, then did a few partition related checks, then said " checking for pro" , and closes. And no matter how may times I install, it is the same outcome, I can't use flashfire, because when it checks for pro, it then closes. I have Installed every version of flashfire I've located online from v50 to v73, same results every time, some hang as few seconds longer, but then close at the checking for pro . I've downloaded newest version from chainfire, also from play store. No luck.

Can someone tell me if I've missed something, or is flashfire no longer an option for the fire 7 5th gen. On 5.1.2

---------- Post added at 09:39 AM ---------- Previous post was at 09:36 AM ----------

Is flashfire broken. Mine closes every time I open it when it checks for pro user. Did I do something wrong. Sorry if I posted twice. i went into detail of my problem and posted , but it's not showing up
[Fire General] DB126:
Read the last handful of posts in this thread.
[Fire General] Meep70:
In order to get Flashfire to work, one must purchase a license. In order to purchase a license, one must be in the Flashfire app. That seems to pose a problem unless one is observant and reads Chainfire's web page about Flashfire.

It worked for me. Your mileage may vary.

Edited to add:

The moral of the story is that if you find a program useful, show some love by paying for it.
[Fire General] tech3475:
So there's no alternative to flashfire at this point?

I'm not against paying if I have to but since Flashfire is discontinued I'd rather look at something else if there is one for locked bootloaders.
[Fire General] DB126:
No alternatives. Paying for FlashFire Pro is no panacea as it only addresses the 'time bomb launch failure. Flashing issues persist if updating a custom ROM from a custom ROM; must start with FireOS.
[Fire General] Pond-life:
I think it's a bit risky without the fastboot to twrp fallback. If you get a situation where the rom won't boot properly you might not be able to run the flashfire app to remedy it.
[Fire General] 4t701:
It would definitely be risky but if they get root then it is possible.
[Fire General] blueberry.sky:
Yea, it would be risky. Too risky to advise random people to go that route. But still! Guess it shows how much I think of amazon's OS. :laugh: Easily willing to take the risk just to get the hell away from it.
[Fire General] 4t701:
It probably won't be long before they figure out a way to boot TWRP now...most people will probably just wait until then.
[Fire General] 4t701:
I just successfully flashed Resurrection Remix Rom from CM12.1 using FlashFire.

-Did a FULL wipe

-Flashed RR ROM, my SuperSU.zip, and my Gapps.zip

-checked 'automount' on all roms/.zips

-left EverRoot disabled

-FLASHED!

-took like 6-7 minutes to fully wipe, flash, and boot up RR.

Btw this rom looks pretty sweet. Check it:

http://xdaforums.com/showthread.php?t=3272599
[Fire General] KennBr:
I followed these directions exactly. For whatever reason it took a bit longer for me, but it worked just as advertised.

He mentions a restore method in that video too in case it messes up, but I didn't watch it since everything went fine.
[Fire General] besweeet:
When flashing a ROM via this method, are you able to install ROM updates without it failing to boot pr something else?
[Fire General] sd_shadow:
yes you can update
[Fire General] besweeet:
Then there shouldn't be any long-term problems by using this method?
[Fire General] jbraney:
CM12.1 on 5.1.1

Any specific instructions for installing CM12.1 on 5.1.1? For any who don't know, it has been updated so that it can now officially be installed via flashfire...
[Fire General] Pond-life:
Only specific I have is don't choose Stock sized Gapps as it's too big to fit in there so fails to install.
[Fire General] kilbZ:
Installed SlimLP over FireOS 5.1.1

Working great so far.
[Fire General] esco_three:
So, I installed CM12 (via FlashFire) WITH stock Gapps before reading this . The ROM installed just fine but I've lost root access and have no Gapps. How can I get them back? I've been reading thru the forums but can't find an answer yet. Thanks!
[Fire General] sd_shadow:
settings /developer options /root... /check apps and adb
[Fire General] Pond-life:
Had someone say that didn't work for them and another that it did. :confused:
[Fire General] sd_shadow:
Likely need to adb sideload stock in Stock recovery, and start over
[Fire General] gyokujo:
Installed CM12.1 22122015 over FireOS 5.1.1

Working great :D.
[Fire General] Pond-life:
Try using supertool to push the SuperSU stuff again
[Fire General] esco_three:
I was able to push it thru with SuperTool. Thanks!
[Fire General] nyquil0520:
CM12 5.1.1 fire os install using Flashfire

Can you provide the steps taken that allowed you the ability to flash CM12? If it works will more than happy to give you a good review, post a video tutorial and give you credit for it. I just want to happily use CM, I never really had a device capable of using CM except for this Kindle Fire 5th Gen [rooted] using nova launcher no OS at the moment because I much rather have CM over Slim Lp.

Ps. Did you flash over Slim Lp and did you auto mount, wipe and what drivers for the gapps did you use.
[Fire General] gyokujo:
I followed step by step on first post, but checked Auto-mount (like he did in demo video), and using micro gapps
[Fire General] DrunkUncas:
I downloaded the flashfire apk from the website. No tester update. http://flashfireapk.com/FlashFire-Download.html v0.24

Hit the plus, wiped, and installed Slim over whatever was left after I rooted an hour ago. Didn't hit the automount check.

Rebooted. Installed micro gapps.

Couldn't have gone smoother.
[Fire General] cpome7:
Zips not showing

Hi.

I've seen this problem mentioned a few times, but nobody seems to have a addressed it yet. I have a Kindle Fire 5th Gen, 5.1.1, it's rooted, I have FlashFire installed. When I attempt to use FlashFire to install a rom - CM or slim - I navigate to the zip location and the files are not showing up. There appears to be nothing in the folder. I've tried placing the zip files on local and external storage, in folders and in the root directory. Nothing. The zip files are visible in ES File Explorer.

Can anyone shed any light on this for me? Many thanks in advance.

Mike
[Fire General] sd_shadow:
i suspect that the SD cards file system is partially corrupt, could reformat card, backup files on pc first.
[Fire General] theholycow01:
Recent versions of Android have something akin to the infamous User Access Control from Windows Vista regarding an app's access to SD cards. Apps are sandboxed in their own directory unless they have the OS prompt the user for permission. I have not encountered it until I got my Fire, and I don't fully understand it. It seems inconsistent to me -- for example, ES File Explorer didn't need to prompt me (or I don't remember it).

Perhaps you missed or didn't get the prompt for FlashFire. (Or I could be completely off-base and FlashFire uses the same trick as ES File Explorer.)
[Fire General] Pond-life:
As a thought this was recommended for some sd card issues on the Fire. Maybe worth a try.

https://play.google.com/store/apps/details?id=nextapp.sdfix
[Fire General] KennBr:
Has anyone had any success actually using a restore? Attempting to right now and it's just stalled on the "FlashFire" screen
[Fire General] hobojester:
If you're asking about restoring back to stock ROM doing a 'forced' factory reset back to FireOS by holding down the power and vol-down button, yes, I've done that several times.
[Fire General] Clat22:
SlimLP stuck on boot

So I'm totally new to this... I successfully got slim installed on my Amazon Fire 2015. Left on vacation - came home and now it is stuck on the boot screen. It boots up and says Amazon in white and then the SlimLP logo starts and it just stays there. Do I have to do some sort of tethered boot to get it to work again? Can you point me in the right direction? Thanks all
[Fire General] sd_shadow:
Was it on 5.1.1 stock?
[Fire General] Clat22:
It was the prior version but it received an OTA update to 5.1.1 so... Yes?
[Fire General] sd_shadow:
SlimLP was working?
[Fire General] Clat22:
Yes. It was working fine. But after it powered down and I turned it back on... It just shows the animated logo over and over
[Fire General] sd_shadow:
try booting in to Stock recovery and wipe cache
[Fire General] Clat22:
Ok. Thanks for the info. Should I just do this through the supertool? Is that how you boot to stock recovery ?
[Fire General] sd_shadow:
power off, Hold volume down button, power on

if you get fastboot mode,

power off, Hold volume up button, and power on.
[Fire General] Clat22:
Unfortunately it's still just spinning away. For about 5 mins now. It's the S spinning with a multicolor ring.
[Fire General] sd_shadow:
did you power off?