yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
Brick risk on this device all but disappeared with FlashFire >v0.30 (0.30 itself was a disaster). Pros/cons for sure but I do appreciate the flexibility of being able to select my preferred GAaps package (nano). Downsides include: 1) Nexus needs a basic GAaps package to function properly; and 2) invariably someone tries to flash a jumbo GAaps package and ends up with a full system partition. Neither serve as justification to bake in GAaps IMHO.

Suppose another consideration is consistency across devices if you care about that (eg: HDX Nexus has GAaps and SuperSU built in).
[Fire Original Android Development] theron1998:
How do I make my SD card actually show up in so I can make apps save to it? I have a menu like this: http://www.jrtstudio.com/iSyncr-WiFi-SD-Card-Sync-Access except it shows my internal storage not my SD card when I click show SD card if I hide again then there's nothing. How can I fix it?
[Fire Original Android Development] DB126:
Reformat the card using another host (eg: Windows). FAT32 should be fine as a starting point to verify the card can be accessed. There are various methods for storing apps on SD cards. On Lollipop the most reliable method is to use a tool like Link2SD that utilizes symbolic links. Many individuals also speak highly of Apps2SD.
[Fire Original Android Development] STrRedWolf:
First flash...

So this is my first time getting all the way to flashing CM-12.1 onto a fresh Fire 5th gen... and I don't know if I'm stuck or not. The Fire currently displays the CM bot head with a background "radar ping" radiating out. Is that normal?
[Fire Original Android Development] Vlasp:
That is normal, as long as it doesn't take more that 10 minutes. Did you get it to eventually boot, and if so, how long did it take for it to boot?
[Fire Original Android Development] STrRedWolf:
Well, it's still doing it since I last posted... um, 20 minutes now?
[Fire Original Android Development] Vlasp:
What was the last version of Amazon Fire OS you had on your device before installing this ROM?
[Fire Original Android Development] L0rdv8r:
No trouble with flashfire and this is my 3rd flash of this ROM.

Would be nice if minimal gapps w/play store, framework and play games were included. But not really critical as some people may want to keep an aosp system. It would be easier for noons, though.
[Fire Original Android Development] ggow:
- No gapps will be included in this ROM.

- From the comments, looks like FlashFire is working quite well now.
[Fire Original Android Development] STrRedWolf:
5.1.1. I was using FlashFire to flash the ROM and Micro-Gapps.
[Fire Original Android Development] STrRedWolf:
Let me be a bit more specific.

Amazon Kindle Fire 2015 with v5.1.1, rooted via RootJunky's SuperTool. Put FlashFire on it, made sure OTA updates were disabled.

Flashing was done per the instructions above... except that I threw in a "To Fastboot backup" to the SD card before the wipe.

Now it's stuck on CM booting.
[Fire Original Android Development] Vlasp:
I think you are either going to have to flash the 5.1.1 update again through fastboot, or use the new unbrick method posted in the Android Development subforum.
[Fire Original Android Development] blazinandroid1:
What are you guys doing about SuperSU. Because I just flashed this and no superuser
[Fire Original Android Development] ggow:
New Build is Up

- Dated 30 May 2016

- Fix Swipe for stock keyboard

- Added back fix for screen rotation glitch
[Fire Original Android Development] ipdev:
Complete wipe, install rom, install su, install opengapps, wipe cache and dalvik.

Works for me.
[Fire Original Android Development] yochananmarqos:
CM SuperUser is built-in. You can enable it under Developer Options. As the other user mentioned, you can also flash SuperSU if you prefer.
[Fire Original Android Development] blazinandroid1:
I finally got it to work.. I downloaded busybox from the play store and SuperSU. Opened busybox. Did a install then update SuperSU. Everything is good. Which is kinda weird how you need SuperSU to use busybox. But it worked.. thanks..
[Fire Original Android Development] theechap:
I downloaded and installed the 5/30 build but for some reason, in Settings-->About Tablet, it still says 5/28 build. I tried installing it twice (with Flashfire and clearing caches) but it still says 5/28. Does everyone else's actually say 5/30?
[Fire Original Android Development] rogersa2k:
If there was a vote I would say no, please don't bundle gapps.
[Fire Original Android Development] ldeveraux:
Looks like he forgot to change the date on the build. No big deal, mine's the same
[Fire Original Android Development] theechap:
Thanks for letting me know. Like you said, no big deal. Just wanted to make sure Flashfire was actually doing its job!
[Fire Original Android Development] DB126:
For those who stumble upon this post - if build date shows May 28th try putting device to 'sleep' via power button while in portrait mode. A brief flip to landscape before entering sleep suggests B20160528. Otherwise it is likely B20160530.
[Fire Original Android Development] ipdev:
Glad to hear. [emoji6]
[Fire Original Android Development] marrco:
FlashFire 0.50 has been released and is available on google play

https://flashfire.chainfire.eu/

FlashFire v0.50: Open to the public

With this release, FlashFire leaves Google's awkward BETA program, and is available through the Play store for everyone.

This does not mean FlashFire should no longer be considered BETA or dangerous, and it definitely doesn't mean it's feature complete.

This does mean you can now leave ratings and comments. Everybody who leaves a 5 star rating might get a warm and fuzzy feeling for a second or two, so what's keeping you?

I've also created a small website for FlashFire located at http://flashfire.chainfire.eu/ , containing quite a bit of information on FlashFire usage and specifics. If you squint, it might even look like a manual.

This update works around all known issues with N Preview, and adb backup/restore functionality has also received some much needed bugfixes.

Unfortunately, I've had to revert lz4 compression back to the single threaded model, as the multi-threaded implementation will occasionally segfault during restore. I hope to find a proper fix for this soon, as this revert may reduce backup/restore performance.

Discussion, suggestions and bugreports should keep going the XDA thread as usual: http://xdaforums.com/general/paid-software/flashfire-t3075433

Changelogs

- Fix compatibility with N Preview 3 (in used libraries)

- Added 'Restore from ADB' option to 'No backups found' dialog

- NP3: Work around ART crash

- NPx: Work around 'adb restore' bug by using 'adb push' instead

- 4.2: Fix StatFs crash

- ADB: Authorize all connections

- ADB: Fix restoring not doing anything on some devices

- Force 'clear cache' option to show UI

- Include filesize in cache validation

- (Temporarily?) Switched back to single-threaded lz4 implementation due to the multi-threaded version occasionally segfaulting

- Add choice for visiting either FlashFire's website or the XDA thread when tapping the top card﻿
[Fire Original Android Development] nwdbrown:
5th Generation Fire problems

Thanks to ggow for all of his work making a custom ROM. I have taken 7 tablets and put CM12.1 on them.

I tried to work on a new round of Kindle fire 5th generations that started with 5.1.3. I did the following steps:

1) Booted into recovery and re-installed 5.1.2

2) Rooted with Kingroot from the RootJunky Supertool

3) Installed Flashfire v0.30 . However, when I open Flashfire, it immediately closes again and doesn't allow me to flash the custom ROM for the micro SD card

I'm hopefully that some expert might be able to provide me some recommendations on how to fix this problem.
[Fire Original Android Development] harise100:
Do you have SuperSU installed?

KingRoot will not work.
[Fire Original Android Development] dunas2331:
I had the same problem download the latest of flashfire version from online or the play store that worked for me
[Fire Original Android Development] nwdbrown:
I rooted with KingRoot and then replaced with SuperSU.
[Fire Original Android Development] mbholm:
From what I have seen, you might have just been rescued. . .you don't want to use v0.30. . .lot of reports of bricks. . .you want v0.32 or later.
[Fire Original Android Development] nwdbrown:
Can you tell me where to get the version v 0.50 of Flashfire (not from Play store) as I would like to sideload this apk?

Note: I updated to v0.32 of FlashFire and am still having the same problem of FlashFire loading and immediately closing on Fire OS 5.1.2 (updates disabled)
[Fire Original Android Development] zerbey:
https://flashfire.chainfire.eu/
[Fire Original Android Development] dunas2331:
http://www.apkmirror.com/apk/chainf...-release/flashfire-0-50-android-apk-download/
[Fire Original Android Development] nwdbrown:
Thanks very much. This link to FlashFire V0.5 is exactly what I needed. I am now able to flash.
[Fire Original Android Development] dunas2331:
You're welcome
[Fire Original Android Development] x13:
Just chiming in to say I got this working on Fire OS 5.1.2 rooted with Kingroot > switched to superSU, latest version of flashfire, pico gApps
[Fire Original Android Development] Webern:
I'm on the 2016-04-20 version and occasionally, when playing a game, the sound gets stuck. It sounds like it's just playing the same 0.1 second's worth of sound in a loop.
[Fire Original Android Development] boobster2:
Has anyone been able to get the Google Play Games app to install? Keep getting an (error 505)
[Fire Original Android Development] crhylove:
I didn't see the link to the new flashfire till I already started the process. How long does the flash take? Am I hosed? It's been stuck on installing..... Inside flashfire .24 for a while now....
[Fire Original Android Development] Signor Rossi:
Should not take that long.

Try rebooting your device. If you still can get into recovery, flash the stock firmware and start over new

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] jaudio:
see post #3 ?
[Fire Original Android Development] sd_shadow:
yes
[Fire Original Android Development] Henil Shah:
Did anyone notice any Lag when you open the App Drawer on Google Now Launcher? Also FIFA 16 crashes and refuses to work, it used to work when Fire OS was installed. Any idea why?
[Fire Original Android Development] dunas2331:
I really love this rom. Quick question is there an auto updater like in cm 13 or do I have to check/install updates manually?
[Fire Original Android Development] ggow:
You will have to update manually.
[Fire Original Android Development] DB126:
Known problem with custom roms (any/all) on this device. TMK no resolution.

---------- Post added at 04:44 PM ---------- Previous post was at 04:41 PM ----------

Try a different launcher to validate lag problem; suggest Nova. Or revert back to stock launcher. No knowledge of FIFA crash.
[Fire Original Android Development] Y314K:
[emoji40]
[Fire Original Android Development] KhuynhThanh:
where is safe move SD card?
[Fire Original Android Development] DB126:
Not sure what you are asking.

If looking for a 'safely remove SD card' function it's not there and generally not needed if the SD card does not hold apps or transactional data. If either of the above are true powering down is the best option.
[Fire Original Android Development] martinmcu:
Has anyone else noticed Inbox is no longer working? The Play store says it is no longer compatible with my device. I have updated to the 2016-05-30 version, as well as the latest GAPPS (2016-06-07 micro). Any insight as to what changed between Inbox 1.22 (I think?) and the latest Inbox 1.24?
[Fire Original Android Development] yochananmarqos:
I downloaded it from APK Mirror and it works fine. I'm guessing the incompatibility may be the app doesn't support the device DPI.
[Fire Original Android Development] martinmcu:
Lamentably, that has failed for me. I uninstalled Inbox, and version 1.22 now crashes constantly after installing from APK Mirror.. Version 1.24 refuses to install. Any thoughts on debugging why it refuses to install? Thanks
[Fire Original Android Development] inscythe:
The lag with Google Now launcher's drawer has been there since the very beginning, I think...

I've recently switched to Smart Launcher, and I don't notice any lag with it.
[Fire Original Android Development] Henil Shah:
Hey when im playing any game or transferring huge amounts of data on my SD card, the screen freezes and the device reboots. Anything i can do?
[Fire Original Android Development] DB126:
Probably not. Inherent behavior of deadline scheduler under very heavy load. You could try switching to cfq or noop using a tool like Kernel Auditor albeit with a slight performance degradation in other use cases. Minimizing background activity and killing unnecessary tasks before game play or large transfers can sometimes help.

http://androidmodguide.blogspot.com/p/io-schedulers.html
[Fire Original Android Development] yochananmarqos:
I have 1.18 installed. I haven't tried updating it yet.
[Fire Original Android Development] martinmcu:
Hmmm, an uninstall and then a clean install of 1.24 seems to have done the trick. No idea what was going on there. I'm curious as to how you an still use 1.18, as for me, the old version stopped letting me view my messages and said that I had to upgrade... But, I have my Inbox again, so all is well! Thanks for your help!
[Fire Original Android Development] linuxnerd2194:
Busybox bug

Excellent ROM! I found an issue, however. If you try to use the busybox applets iwconfig or iw, it gives this error:

iw: applet not found

or

iwconfig: applet not found

Running as root makes no difference. I haven't found any issues with any of the other busybox applets, although I haven't tried them all by any means. Installing busybox from a Google Play app makes no difference.
[Fire Original Android Development] yochananmarqos:
I don't check my email on my Fire very often so I hadn't noticed it wasn't working. I just updated to 1.24 without issue.
[Fire Original Android Development] castlec:
Unable to Flash Rom with 5.1.2 Downgrade

I've tried flashing both this package and SlimLP with Flashfire. I just got the device yesterday and made the mistake of attaching it to wifi to play with it last night. It upgraded to 5.1.4. I have downgraded it to 5.1.2 as forums have suggested. I am able to root etc but Flashfire fails to flash the new OS.

Is this a known issue?

[UI] FlashFire - © 2015 - Chainfire
[UI]
[UI] Installing [/mnt/media_rw/sdcard1/flash/cm-12.1-20160530-UNOFFICIAL-ford.zip]...
[UI]
[OUT] Archive: /mnt/media_rw/sdcard1/flash/cm-12.1-20160530-UNOFFICIAL-ford.zip
[OUT] inflating: META-INF/com/google/android/update-binary
[OUT] inflating: META-INF/com/google/android/updater-script
[OUT] minzip: Extracted 3 file(s)
[OUT] about to run program [/tmp/install/bin/backuptool.sh] with 2 args
[OUT] Running FireOS; skipping backup script...
[OUT] about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
[ERR] grep: /tmp/recovery.log: No such file or directory
[OUT] You have an installed system that isn't signed with this build's key, aborting...
[OUT] run_program: child exited with status 124
[OUT] script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
[UI] Can't install this package on top of incompatible data. Please try another package or run a factory reset
[OUT] ui_print

Thanks!
[Fire Original Android Development] Niddu85:
Hi guys, I have a problem with the tablet with the latest CM 12.1 version (30 May 2016), but also with a previous one (20 April 2016) and the latest OpenGApps.

I cannot install some of the apps of the Play Store because i got the message "Your device isn't compatible with this version"

An example is Google Inbox.

I also noticed that some apps are not installed with the latest version available.

Eg. Ebay, which i can install it without problem from the play store, if i check the version of the app is really old compared with the latest avaialble on the Store (on the tablet i got version 2.x.x.x instead of 5.x.x.x available )

does anybody have a solution to this?
[Fire Original Android Development] ajislav:
Read the thread. You are not the first to have this problem.

The solution is to sideload the APK.
[Fire Original Android Development] Niddu85:
Yes i know this allows to install apps, but I was thinking a more technical solution to solve the issue not a work around
[Fire Original Android Development] TruBlaze:
After installing, I don't seem to have root anymore...
[Fire Original Android Development] MisterSteve:
Most apps that utilized GPS will show up in the Play store as incompatible because the Fire doesn't have a GPS. As others have said, go to APKMirror and sideload.
[Fire Original Android Development] DB126:
The more "technical solution" you seek involves twiddling parameters in build.prop to masquerade your device as a different model. Rarely works well. Plenty of info online as it's a common problem with custom roms. Or just sideload and call it a day.

If you value auto-updates and a flashy interface consider an alternative marketplace like 1Mobile for apps that won't load via the Play store. Watch out for crapware; lots of similarly named clones that carry an interesting payload.

---------- Post added at 10:08 PM ---------- Previous post was at 10:01 PM ----------

http://lmgtfy.com/?q=Enable+root+on+cm+12.1#
[Fire Original Android Development] GhostRider86:
After installing what? This rom has root build in, you need to enable it under developer options...
[Fire Original Android Development] drkbg:
Does anyone else have Bluetooth audio lag?
[Fire Original Android Development] elbastardo1:
On video playback, yes. BT audio always has lag, unless BOTH devices have BT 4.0
[Fire Original Android Development] Signor Rossi:
Read first post to understand which boxes to tick in FlashFire

Gesendet von meinem OnePlus One
[Fire Original Android Development] DB126:
Seems this is an old post but worth clearing up a few details:

- recommend using latest version of FlashFire (currently 0.50)

- leave all flash options at default vslues; no need to change anything

- if changing roms add wipe operation above flash operation; include system, user data/apps dalvik and cache; do not wipe internal storage
[Fire Original Android Development] castlec:
Pretty sure I've done exactly as you've described. I end up with the above error and a wiped device with the same rom. I wouldn't be horribly surprised if I'm screwing up the check boxes since I haven't found a tutorial flashing a new rom on the fire with flash fire 0.5 but I also tried 0.24 following RootJunky's video tutorial.

Are you able to point me to a reference?

Oh, twrp..... how I miss thee.
[Fire Original Android Development] DB126:
Yep - life without twrp sucks. Thoughts:

- did you replace Kinguser with SuperSU after rooting?

- leave all FlashFire 0.50 defaults alone (ignore OP; outdated info)

- if all else fails reload 5.1.2 and start over; don't register w/Amazon
[Fire Original Android Development] castlec:
SuperTool flashes SuperSU as its rooting protocol and then removes KingRoot.

I'll try it again with defaults only.

It's Flash Zip or OTA not Flash Firmware Package for both the rom and gapps, correct?

Thanks for the suggestions.
[Fire Original Android Development] DB126:
Correct. If it fails again you'll probably need to reload FireOS 5.1.2. This is often the quickest and most reliable path when FlashFire acts up.
[Fire Original Android Development] drkbg:
Does this mean that device is unusable with Bluetooth speaker to play videos? I experience 3-4 seconds delay...
[Fire Original Android Development] Signor Rossi:
True, but I used it the other Day to go from 5.1.2 to CM without an issue using those settings.

Anyway thanks for clearing things up.

Gesendet von meinem OnePlus One
[Fire Original Android Development] ldeveraux:
The best way I've found to flash any zip is to uncheck everything in flashfire. Except for the rom, in that case I mount the /system and read/write. This has worked for me for months now without any issues at all.
[Fire Original Android Development] DB126:
FlashFire is a powerful enabler that is getting better with every release. But it can still behave erratically - at least on this device. There is likely a logical explanation when things go wrong despite appearing to follow exactly the same procedure. Obviously something is different, whether it be by the users hand or a nuance introduced 'behind the curtain'.

While pealing back the onion to discover root cause has its rewards it is often easier, faster and more reliable to simply reload FireOS and start from scratch.

Some claim that twiddling FlashFire options improves outcomes. Much of this stems from early videos and personal success stories that are not repeatable. I encourage a careful read of the FlashFire home page (below) and associated guidance under the hamburger menu. IMO the default choices in more recent releases of FF are appropriate. Funny how the developer seems to get it right.

https://flashfire.chainfire.eu/
[Fire Original Android Development] TruBlaze:
Is anyone else having a problem with sound? I can hardly hear any sort of media except for music
[Fire Original Android Development] castlec:
Sideload of fire-OS-5.1.2-update-kindle-global-37.5.4.2_user_542168620.bin pulled from RootJunky's site stops at 94%. It seems to be finishing the flash successfully but it never says 100%. Reflashing 5.1.2 has not changed the behavior I'm experiencing.

Looking at the FF logs again, it kind of seems like the wipe isn't happening until after the failed flash of the ROM.

Before posting, I decided to try a few more things out. I went looking for another location of the 5.1.2 bin and noticed RootJunky had versions of SlimLP and CM12.1 saved on his file repo. I pulled those to try to flash. I moved them to my sdcard and then set SlimLP to flash via FF. It did not set R/W mount so I set it myself. I then added a wipe and dragged it above the flash. It went.

So in the end of it, I have no idea what was causing the problem flashing nor what fixed it. :confused:

I'm wondering if, now that I'm on an AOSP rom, if I won't have issues with it anymore or if I have to follow some particular incantation still.

As I learn more, I'll report back. If there is further insight from the group, please share.

Thanks all.

__________________________________

Looking at the successful log leads me to believe I was having some issue with the wipe order.

UI] FlashFire - © 2015-2016 - Chainfire
[UI]
[UI] Wiping...
[UI]
[UI] Installing [/mnt/media_rw/sdcard1/flash/Slim-ford-5.1.1.build.2.2b-20151210.zip]...
[UI]
[OUT] Archive: /mnt/media_rw/sdcard1/flash/Slim-ford-5.1.1.build.2.2b-20151210.zip

[UI] FlashFire - © 2015-2016 - Chainfire
[UI]
[UI] Installing [/mnt/media_rw/sdcard1/flash/cm-12.1-20160530-UNOFFICIAL-ford.zip]...
[UI]
[OUT] Archive: /mnt/media_rw/sdcard1/flash/cm-12.1-20160530-UNOFFICIAL-ford.zip
[OUT] inflating: META-INF/com/google/android/update-binary
[OUT] inflating: META-INF/com/google/android/updater-script
[OUT] minzip: Extracted 3 file(s)
[OUT] about to run program [/tmp/install/bin/backuptool.sh] with 2 args
[OUT] Running FireOS; skipping backup script...
[OUT] about to run program [/tmp/install/bin/otasigcheck.sh] with 1 args
[ERR] grep: /tmp/recovery.log: No such file or directory
[OUT] You have an installed system that isn't signed with this build's key, aborting...
[OUT] run_program: child exited with status 124
[OUT] script aborted: Can't install this package on top of incompatible data. Please try another package or run a factory reset
[UI] Can't install this package on top of incompatible data. Please try another package or run a factory reset
[OUT] ui_print
[UI]
[UI] Wiping...