yashsingh1/xdaforums huggingface dataset:
[Fire General] Clat22:
I did. And I just went back to do it again to make sure. No dice.

Just to be clear. I turn it off. Then go to system recovery and scroll down to "wipe cache partition" and once that is complete I go to power down. And then once it's done powering down I boot it only by using power button. That is what I did. Just want to make sure I'm doing what you're telling me to. Appreciate your help.
[Fire General] sd_shadow:
You can try wiping data in recovery, but think you will likely need to use the adb side load option in recovery to install stock firmware.

see How to Firmware Restore or Unbrick your Amazon Fire 5th gen Tablet

[YOUTUBE]RQLoH-ahjy4[/YOUTUBE]
[Fire General] chemie99:
So if someone flashed to RR rom on 5.1.1, why do you have to restore to 5.1.1 vs failing back to 5.0.1 (which apparently bricks it)?
[Fire General] sd_shadow:
once on full stock 5.1.1, you can not downgrade to full stock 5.0.1
[Fire General] chemie99:
so I read...I was just wondering why. I mean, all of 5.1.1 is gone once you reflash?
[Fire General] sd_shadow:
there are several partitions on an android device

/system is where the stock rom is and where a custom rom is installed

so no once you install a custom rom the custom rom is no longer there.
[Fire General] hp420:
The bootloader, kernel, system, etc all have to be compatible with each other. If they aren't bad things can happen.
[Fire General] paolora999:
restart in fire os!

after having followed the procedure step-by-step, my device (with fire os 5.1.1) reboots in fire os...

any hint?
[Fire General] sd_shadow:
filenames?
[Fire General] tdcrone:
[MENTION=5019863]paolora999[/MENTION] This morning I observed that FlashFire 0.24 moves "wipe" to the last task, regardless of the creation order. This prevents anything installing. You have to long-press the wipe task and then drag it above the flash ZIP tasks.

Doing this I was able to install 1/4 CM12 with the 1/5 Micro GApps over a colleague's stock FireOS 5.1.1. Thanks to everyone!
[Fire General] paolora999:
Tonight I will follow tour advice. Thanks a lot! :)
[Fire General] CuriousTux:
I've got a problem hopefully can be fixed. I was on 5.1.1 and used rootjunkies supertool and rooted the device. I used flashfire to install cyanogenmod 12 but I don't seem to have recovery option but I can get into fastboot mode. Is there anyway to restore the device to factory or be able to use cyanogenmod 12 with gapps and playstore the correct way thanks
[Fire General] sd_shadow:
does cm12 boot?
[Fire General] CuriousTux:
cm12 boots and I can use it I just don't have playstore and google apps how can I go from there to make it a fully functional device thanks
[Fire General] sd_shadow:
have root?
[Fire General] CuriousTux:
Root yes
[Fire General] sd_shadow:
just reinstall FlashFire, and flash open gapps, no wipe,
[Fire General] sd_shadow:
www.opengapps.org
[Fire General] sd_shadow:
arm, 5.1.1, mini or smaller
[Fire General] paolora999:
Bingo! Thank you
[Fire General] sd_shadow:
Updated Post #1
[Fire General] williamvito:
Anyone make traction yet installing CM12.1 coming from SlimLP?
[Fire General] dfelicia:
Worked for me

5.11 stock, rooted -> CM 12 worked perfectly. What a HUGE improvement.

Anyone figure out a way to make the fonts smoother? I messed around with various DPI settings, but they made the icons blurry.
[Fire General] williamvito:
I am in the process of restoring the stock firmware, then re-root, then flash CM12/gapps. Did you flash the Super User zip or ever root? And did you auto-mount? Thanks in advance.
[Fire General] dfelicia:
I let FlashFire inject root - I did not use a zip. I picked nano gapps. I did automount. My full process:

- Get root via Rootjunky's Supertool

- Install FlashFire

- Full backup to SD

- D/L CM12 and GApps nano

- FlashFire w/automount and root injection (manually move Wipe to 1st task)

Dunno how long it took. I hit Flash and then went to do chores for an hour. When I came back it was ready.
[Fire General] williamvito:
followed that and it worked perfectly, thank you!

have you had any issues with moving apps to the SD card but after reboot the .android secure folder on the SD card is gone thus deleting the apps? I'll head over to the CM thread with the same question but I figured i'd ask since you're running it, no big deal of you can't answer, thanks again!
[Fire General] joshyakadamien:
Hi everyone.

First of all thanks for your work, i greatly appreciate it.

I accidentally updated to 5.1.1. and started to play around with Flashfire.

What i managed to do:

backup

root

remove ads

install custom rom (slim lp)

Flashfire bricked my device while installing the cm12 rom.

I saw that sd-shadow faced the same issue as well previously, which is basically the device hangs on the cyanogen boot animation.

I've red through all the material which i could find here or anywhere else.

So i know by now the issue with the wipe in flashfire...

Unfortunately it was too late...

So far my options:

attempting to create a service cable to see if that does the trick...

Most probably it will not, because with the 5.1.1. update they disabled the option to change the boot mode in fastboot, so the so called "shorting trick" as it is written here is the last resort what i have, but could not find any way to disassemble the case without any significant damage.

So my humble questions are:

Can anyone help me how can i disassemble the tab? (btw did not found any house parts for sale to replace the casing if it gets messed up. no wonder fresh product...)

Is there anything else i could try?

fastboot will not:

oem format

wipe

flash

set boot mode

as we know it... did i missed something?

So basically if i cannot force the tab to usbboot and flash it from there all i have is just a brick right? :P
[Fire General] sd_shadow:
no solution right now, best option is returning to Amazon
[Fire General] joshyakadamien:
Thank you sir.
[Fire General] danrodz:
I followed these steps exactly and it worked perfectly. Thanks!
[Fire General] devlspawn:
Mine keeps getting stuck with Flashfire at the top and blank black screen. If I reboot after several hours I get the cyanogen logo but nothing else. Is there a specific CM rom everyone is using that works?
[Fire General] sd_shadow:
any cm12.1 build in last 20 days should work
[Fire General] patt2k:
how do you guys retain root if ROOT was not selected in FlashFire? do I need to run the exploit to run again or have to do everything all over again? just for future so I know :D on CM13 of course.
[Fire General] DB126:
Several hours? You may have a hardware issue. Consider a warranty exchange/return.
[Fire General] devlspawn:
I eventually figured it out, it was the build, the most recent one didn't work, had to go to the one before that.
[Fire General] danrodz:
also, did you make sure to move the wipe action to the top of the queue manually? that is an essential step, if you skip that it will not work! i've done this to 3 kindle fires and it has worked perfectly every time. it's never taken more than 10-15 minutes although i haven't been timing it.

i would also be leery of the build/ROM i'm using, get everything flashed up and done, then you can experiment with other builds, knowing you have a solid backup to get back to.
[Fire General] mbholm:
What do you use to get a proper backup. . .I am looking for a solution for backing up, so I can get back to where I am after trying to play with a few more options?
[Fire General] DB126:
The only backup I fully trust is a nandroid from CWM/TWRP but that likely isn't an option if you can't boot those recoveries. You can snag a nandroid like backup via adb; Google for details. Also an app called Online Nandroid Backup - but it gets mixed reviews and hasn't been updated in awhile. Titanium Backup is the gold standard for many and does far more than just backups. Not sure what abilities the free version has; might have to pay up.
[Fire General] sd_shadow:
I've restored with FlashFire a couple of times, works fine
[Fire General] mbholm:
Thanks I'll try those out as I can. Unfortunately, I made the mistake of playing with a popup prompt about how to handle the USB connection (randomly told it to use charging only mode). I never expected it was possible to set something so easily that doesn't appear to have a way to undo it. I am finding lots of people have had this issue. . .and I haven't found many solutions. I did find a couple posts that seem like they should work, but they aren't working for me.

http://xdaforums.com/showpost.php?p=64921310&postcount=669

and similar action here (with a mention of the original workaround not working after 5.0.1):

http://www.random-host.com/comment/518#comment-518

I was going to post to the first thread asking for help, but I can't post there since my account is so new (I was sure I signed up before, but it appears I have only been reading previously). It appears I should be able to post there now. I have tried setting that setting and rebooting at least 5 times. . .and debugging is still disabled for me under dev options. . .if I go to Storage > ... USB connections, I get the error " USB is not connected" as mentioned in the first thread.

Seems like a logical choice. I tried to use FlashFire to only do a back before I flashed my Fire for the first time (yesterday). . .It went to the FlashFire screen and never made any progress. . .so I left it for the rest of the night hoping it would finish, but it still wasn't done in the morning (like 5 hours later). I am not sure what I did incorrectly. . .but I'll have to try again. I haven't put flashfire back on since I flashed the SlimLP ROM. I used the SuperTool to load it the first time and of course, my current dilemma of trying to get ADB back is getting in the way of doing it that way again.

I have liked Slim, but I haven't really spent much time with Android devices yet (and haven't try CM yet). . .just getting started now that I have compatible hardware (all my iOS devices are jailbroken). Unfortunately, I have found that it appears that SlimRecents (very nice on a 7" device) doesn't function in the restricted user profiles (which is my current plan for rolling this custom rom out to our kids).

Thanks for the responses!
[Fire General] DB126:
Keep working with persist.sys.usb.config to find the magical combination that works (Google is your friend). Be sure to use a proper build.prop editor rather than going at the file directly. While there are many options I like the one embedded in Kernel Adiutor. Simple/straightforward. Just be careful what you change given the current state of your device.
[Fire General] mbholm:
Thanks. I'll try that one tonight. As long as I am just adjusting that one settings. . .anything to be worried about messing up?
[Fire General] DB126:
Can't answer with confidence; just be sure to use valid values and understand the consequences of each choice.
[Fire General] starkruzr:
So, I just rooted my 5.1.1 unit and root seems to work fine, but Flashfire crashes on launch now after having launched it once, it taking a really long time to figure out whether it had root and then taking another long time to go through "enumerating partitions." It then crashed and has not launched since, after two reboots, etc.

I'd like to put CM 12.1 on this 5.1.1 Fire. Is that possible?
[Fire General] mbholm:
I had FlashFire give me trouble the first time I installed it as well. . .after trying to use it once. . .end up reinstalling it and then it started working again.
[Fire General] starkruzr:
So I got it working! Can I boot from the TWRP image after making a backup and install CM12.1?
[Fire General] mbholm:
I am really new to all this as well, but from what I read, you can not use TWRP if you are currently on 5.1.1. . .FlashFire is currently the only method working because of the locked bootloader
[Fire General] DB126:
Uncertain of your question. Potentially helpful (or not):

- you can boot a ROM from with TWRP. Simply reboot system.

- you can not install twrp on the device (locked bootloader); it must always be downloaded/launched via tether

- see this video if unfamiliar with TWRP

---------- Post added at 12:18 AM ---------- Previous post was at 12:16 AM ----------

Correct. If on 5.1.1 see this instead.
[Fire General] starkruzr:
I guess I don't understand how Flashfire works. If I can't change the recovery, how can I wipe system, wipe data, wipe cache and install another ROM?

Live booting TWRP - is this the correct way to load CM or any other ROM on 5.1.1?
[Fire General] DB126:
- watch the videos

- read the forums; everything you need to know has been posted multiple times

- FlashFire is (at present) the only option to install a custom rom on 5.1.1
[Fire General] sd_shadow:
according to chainfire

" Android is torn down and restarted in a minimalist manner for the flashing part of the app to run."

http://xdaforums.com/general/paid-software/flashfire-t3075433
[Fire General] starkruzr:
To clarify for anyone who was as confused as I was:

CM works fine on 5.1.1

It sounds in multiple threads as though you can write TWRP to the recovery partition on 5.0.1 (I have no idea if this is true) but have to fastboot boot it on 5.1.1 (this does NOT work)

You have to follow the following procedure:

Root (easiest way is probably with the toolkit in the first post of this form) -- this takes some time, over ten minutes

Install Flashfire

Flashfire will probably break the first time you install it. Reinstall it from APK or the Play Store

Download CM12.1, Nano Gapps and SuperSU, place in your internal storage or SD card

Start Flashfire and instruct it to wipe system, data, and both caches

Voila!
[Fire General] DB126:
-TWRP can not be flashed/installed/written to recovery partition on any base version as bootloader remains locked

-can boot TWRP on 5.0.1

-can use FlashFire on 5.0.1; must use it on 5.1.1

-order matters on FlashFire; make sure wipe is at the top
[Fire General] :
Thanks for writing this up :)
[Fire General] ahmedkom:
is there a away to start flashfire from fastboot or as a pc programm like odin, my fire 7 is stock in bootloop after installing cm12 went wrong
[Fire General] DB126:
Not that I'm aware of. Many users would benefit from a solution like this if it existed (which further suggests it doesn't).
[Fire General] wulfie66:
you can use fastboot to 'install' flashfire, but that's the extent, you have to run it from fireOS
[Fire General] Will_YohYoh:
use the flash fire in my lg g4 0.27 h815p with a 5.1 rom to install the root stock rom @ Marcosuper7 and only gave me reboot. I tested with version 0.24 and going great .

Enviado desde mi LG-H815 mediante Tapatalk
[Fire General] sd_shadow:
added some comments and thoughts to post #1
[Fire General] mt12345:
On RootJunky video wipe option is listed last yet he didn't brick his tablet.
[Fire General] mt12345:
Oh, wait a second. :mad:

FlashFire DOES NOT wipe system partition. Its meant to wipe data,cache, dalvik AFTER flashing.

So it flashes custom rom over existing system. :confused:

Which means people who ended up with bricked device must have messed with the system before flashing.

The safest way would be sideload amazon firmware, root it and flashfire.

Right?

:fingers-crossed:
[Fire General] mbholm:
The first time I flashed, I used .24 with slimrom and didn't move the wipes, picked automount and mount rw on both. . .and didn't have issues. . .but I figured I was lucky. . .since then I have always moved the wipes to the top and left the automount and mount rw at their defaults on 0.27. Been okay so far.
[Fire General] DB126:
Latter is the correct procedure for rom flashes.

---------- Post added at 10:06 PM ---------- Previous post was at 09:58 PM ----------

Not sure what you are driving at. Proper procedure is listed in the OP unless you are dealing with a special situation. If wipe option includes anything other than cache/dalvik/data it should be executed before subsequent zip operations.
[Fire General] mt12345:
Never mind.

I installed slimlp from stock 511 using ff v24, files on sd card.

I did it regular twrp way:

wipe everything,flash rom,gapps(automount),wipe cache,dalvik, reboot.

thanks and good luck!
[Fire General] obiismycat:
I'm having trouble when I try to open flashfire .27, it opens for a second then quits. Any body else have this issue?
[Fire General] ldeveraux:
weird, have you installed xposed? Have you granted it superuser rights yet?
[Fire General] obiismycat:
I have SuperSU installed and I granted flashfire rights. don't have xposed, do I need that to flash nexus rom onto tablet?
[Fire General] DB126:
You don't need Xposed to use FlashFire. Suggest uninstalling and reinstalling. You can get the latest version from [URL="https://plus.google.com/+Chainfire/posts/Q7YYVPwv8Fx]here[/URL]
[Fire General] ldeveraux:
No, Xposed sometimes tweaks out certain programs, was just a hunch. Yeah maybe uninstalling Flashfire, reboot, reinstall? That's a weird one. Rebooting has fixed that for me in the past. Clear cache and dalvik too if you can?
[Fire General] Kusanagi Motoko:
I flashed mine several times with CM12.1 but couldn't get gapps to work. ._.
[Fire General] sd_shadow:
Flashfire version

gapps version?
[Fire General] Kusanagi Motoko:
FlashFire 0.27 and Open GApps, both nano and pico.
[Fire General] DB126:
Preferred versions of both. Suggest flashing GAaps seperately with wipe cache/dalvik (only!) on top followed by GAaps pkg with 'mount /system read-write' checked. Should do the trick.
[Fire General] Kusanagi Motoko:
I actually tried that earlier. Did CM without GApps, then flashed the GApps package after first boot, with mount only: it went through FF but nothing on the tablet.

Tried again with 'mount /System read-write' and the GApps appeared but they crash. Rebooted and the Google initial setup screen appeared but then it kept on force-crashing until I turned wifi off and skipped that..

Tried with both CM12.1 and ResurrectionRemix (CM based so, it's the same I guess) and still nothing.

Thanks for your reply though.
[Fire General] DB126:
Interesting. There have been some bad Open GAaps builds of late. Perhaps you were 'blsssed' with one of the wonky ones. Glad you found a solution that worked and shared it with the community.
[Fire General] Kusanagi Motoko:
Nothing worked actually but I'll just keep on trying different GApps for now.

Will report if anything works. Keep up the good work and thanks for the time!
[Fire General] DB126:
Sorry - responding to multiple threads. See last few posts in the following thread for a potential solution (removing SD card): http://xdaforums.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416/page211
[Fire General] Kusanagi Motoko:
And it worked finally. Tried like 4 or 5 GApps packages until one of them worked. Whenever one of them didn't work, I just reflashed the ROM (latest build to date) and tried a different package twice, first with only auto-mount for gapps, and second with mount/system.
[Fire General] DB126:
Great! Glad you found a solution.

For future readers: there is no need to reflash ROM when flashing an add-on package like GApps or Xposed unless explicitly instructed to do so. In the case of GAaps whatever you are attempting to flash will overlay existing components in the same location. The only time you *might* need a ROM reflash are: 1) severe corruption of the original install; or 2) downsizing a previous GAaps installation. There are other ways to address both conditions but sometimes a complete wipe/reflash is just easier (albeit riskier).
[Fire General] webdoctors:
I flashed my new Fire today running 5.1.1 with CM12-1 and GApps without issue.

cm-12.1-20160311-UNOFFICIAL-ford

open_gapps-arm-5.1-micro-20160320

Using the flashfire app that comes with superTool. I used the tool to do a wipe and than install of the 3 zips (the 3rd zip is for superUser).
[Fire General] drag0micr0:
What were the steps you used?
[Fire General] 1storm976:
I tried to wipe , and flash slim rom and it didnt... i have fire os 5.1.2 rooted when i tryed to flash it did say something about a im trying to flash a block level ota .. how can i fix that?

thx
[Fire General] DB126:
Irrelevant on this device - just click through it.
[Fire General] 1storm976:
Well I did give it a go all it did was reset my tablet back to factory after it Rebooted and supposedly installed it

Thx
[Fire General] DB126:
What version of FlashFire? Should be using v.031 (latest) or v0.27 which appear to be the most reliable. The behavior you noted has been seen before; not sure of root cause.
[Fire General] 1storm976:
V24 and 31 the newest has more options to Wipe but I keep it at system , delvac in Cache. I tried to install cm12 and that didn't work either and this is a rooted fire OS 5.1.2, I really would rootjunkey super cool but I did not block the OTA update I'm not sure why exactly is not installing

Thx
[Fire General] DB126:
Did you swapout Kinguser for SuperSU? Reports of FlashFire not playing nice with the former. Believe recent versions of RootJunky's Supertool has an option to automate this. Wipes should be confined to those you listed and be positioned (obviously) before the ROM flash. Also, confine flash to rom only; do GAaps later.
[Fire General] 1storm976:
Yes I replace root King with SuperSU no problems there I did try different versions of Flashfire did wipes without a problem but it's not installing the ROM . With slim ROM it says it's a block level Ota. Cm12 it just don't install.
[Fire General] DB126:
Given two different roms fail to install with different FlashFire versions and SuperSU isn't complaining the focus shifts to integrity of your existing FireOS install. Unless someone has a better idea you may need to reload using the stock recovery menu. Bit of a pain but a useful exercise as it is the primary (only) recovery method when flashes go bad with no twrp access. After reloading FireOS you'll need to reregister, reroot, etc.

I don't suggest this path lightly - but don't see a better option.
[Fire General] 1storm976:
Well when I read the install log it said that the OTA signature was not correct or something of that nature.. think the ROM is based on 5.1.1 and it don't match up some how.. thx guess no flashing slim rom on 5.1.2 fire tablet..???
[Fire General] DB126:
FireOS version should be irrelevant to the success of flashing any ROM provided both are from the same Android branch. OTA should also not matter. Have no idea why SlimLP is not flashing on your device. Have you tried Nexus which is known to work with the latest version of FireOS?
[Fire General] Sulinjr:
Hi when you say Nexus, are you talking about a variant of Android OS or does Nexus refer to another method of flashing SlimLP?
[Fire General] DB126:
There are at least 4 custom roms for this device: CM 12.1, Fire Nexus, Resurrection Remix, and SlimLP. You can read about them in Fire Original Android Development section.

http://xdaforums.com/amazon-fire/ORIG-DEVELOPMENT
[Fire General] m00head:
That link doesn't work for me. Try this one instead:

http://xdaforums.com/amazon-fire/orig-development
[Fire General] Sulinjr:
Oh wow I was only aware of CM12 and SlimLP. Which is the best in your opinion? And has anyone figured out a way to flash 5.1.2? I had issues every time I tried to flash CM12 and SlimLP with FlashFire.
[Fire General] DB126:
There is no best. Try Nexus as a problem determination step. Be sure to use the latest version of FlashFire (>0.30) and leave all FF options at their default.
[Fire General] Sulinjr:
Thanks but you don't have a preference? I use CM12 on my other tablet, mainly for Xposed functionality, OS stability, and performance. Which do you use?

I will give flashing CM12 another shot with your recommendations. Also I read somewhere that I should just flash Gapps afterwards? So just wipe, flash CM12, flash SuperSU; then boot up and flash Gapps and Xposed. Correct?

Also thanks for taking your time to help out here.