yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] Joshmccullough:
I seem to have lost the ability to have my tablet recognised as external storage when I connect it to my laptop, automatically connect via ADB, and on top of it all my SD card isn't writeable anymore. I'm not sure what I did; am I the only one experiencing this, does anyone have an idea how I might troubleshoot this?

I'm out of town/away from my laptop right now, figure once I get home I can try reflashing and see if that does the trick. I can't for the life of me think what I might have done.....
[Fire Original Android Development] ipdev:
Quick note. (Chainfire has been working on ff.3 issues related to failed installs.)

http://xdaforums.com/showthread.php?p=66198155

I have opengapps & SuperSU 2.8 beta installed. These were installs that would kill my fire. (5.1.1)
[Fire Original Android Development] DB126:
Although FF should not have stopped the CM install may have been successful as root access is disabled by default. Have to enable developer options and enable root from there. Not advocating you reflash as risks remain with CM/FF; just commenting.

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

Common failure - although it doesn't happen to everyone. Qs:

- what version of FlashFire

- what happened when you rebooted?

---------- Post added at 08:49 PM ---------- Previous post was at 08:45 PM ----------

This looks promising! For those interested navigate the link and scroll down to the bottom for more instructions. Keep in mind detail testing still needs to be done; go in with eyes open. If you do go for it report outcomes here and in the FF thread. Be sure to use latest CM build (first post in this thread).

---------- Post added at 08:56 PM ---------- Previous post was at 08:49 PM ----------

Nexus is a very nice ROM (pure Android) but does require a bit of work (primary through Xposed modules) if you like the customizations in CM. Nexus installs with FlashFire have been uneventful. If you can't boot twrp Nexus offers a nice alternative for FlashFire users who struggle with CM. Slim and Remix also get favorable reviews. Really depends what you like in a rom.
[Fire Original Android Development] riverstyxxx:
Flashed it again, this time I kept the zip files on the system memory and it worked.

---------- Post added at 03:56 AM ---------- Previous post was at 03:28 AM ----------

Spoke too soon: OpenGapps didn't work, it hung at the "checking rom info" status. Had to use regular Gapps 12.1 from here: http://www.teamandroid.com/gapps/
[Fire Original Android Development] ipdev:
Starting from fireOS 5.1.1

Using ff .30 (With Chainfire's suggestion about AROMA)

Installed cm-12.1-20160404-UNOFFICIAL-ford.zip

(Installed fast and only took a minute or two to boot.)

-- Had to enable/disenable root, reboot twice but finally had root.

Reinstalled ff .30

Installed BETA-SuperSU-v2.71-20160331103524.zip

(I run SuperSU on everything.)

Installed open_gapps-arm-5.1-pico-20160402.zip

Logged into google & installed apps.

Sent from my KFFOWI

- I ran all off my sdcard. I ran into a few problems when I was installing from internal storage. -
[Fire Original Android Development] marrco:
root access is included in cm mod via developer options.
[Fire Original Android Development] Ghadeed:
I was able to get CM 12.1 to load but I am unable to get gapps to load. Every time I try and install via ff .30 it juts sits on mounting. Anyone figure out how to get this working?
[Fire Original Android Development] ggow:
See post 2438 for an alternative gapps

Open Gapps doesn't work with ff .30
[Fire Original Android Development] sandman512:
Ok, so went to upgrade to the latest version via TWRP and ran into a problem. Used 1 click reboot(always worked) and it said error, then it said unable to locate TWRP...img(something like that. Device went to fastboot mode and hung there. held the PWR button for 30 seconds and back to home screen. Any thoughts on this one? Thanks!
[Fire Original Android Development] sd_shadow:
upgrade?

1 click reboot for what?

there is a twrp thread

using rootjunky's super tool? there is a Thread for that as well
[Fire Original Android Development] DB126:
Err...and you retried how many times? TWRP is a stand-alone application/environment that occasionally crashes. If the problem persists download the lastest twrp image, recheck connections and post finding/questions in the appropriate thread.
[Fire Original Android Development] sd_shadow:
is this on your soho 3rd Gen Fire?
[Fire Original Android Development] sandman512:
@sd Shadow, meant to flash latest build, not upgrade. No, this is not for the SOHO device, this is for my Amazon Fire. [MENTION=5488402]Davey126[/MENTION], tried a few times to no avail. I will try the latest image.

The reason I posted it here is in case someone else was having a similar issue using Root Junkys Super Tool.

Thanks for the responses.

sandman
[Fire Original Android Development] sd_shadow:
yes but it's a super tool issue not cm12
[Fire Original Android Development] sandman512:
I didn't think of that until you pointed it out, thanks. Message posted in that forum....
[Fire Original Android Development] GhostRider86:
Tested succesfully (no mount system error)

- Reverted to stock FireOS 5.1.2 (adb sideload, wipe cache, factory reset)

- Rooted with Kingroot method (with AmazonFire5thGenSuperTool)

- Changen to SuperSU (with AmazonFire5thGenSuperTool)

- Installed Play Store (with AmazonFire5thGenSuperTool)

- Installend FlashFire 0.31 from Play Store (manual installed versions opens and closes directly, tried 0.27, 0.29, 0.30)

- Wiped, Flashed "cm-12.1-20160404-UNOFFICIAL-ford.zip" and "gapps-lp-20150314.zip" (cause OpenGapps would not work, see #2438)

- CM12.1 worked like a charme and Google Play Store as well (but it is old version)
[Fire Original Android Development] DB126:
Play Store and other components in the GAaps package should self update; no further action required (might need a few reboots).
[Fire Original Android Development] riverstyxxx:
Question: There's a significant number of play store apps that are incompatible (Amazon, Weather channel, Yelp, OKC, Postings craigslist app) with this device. Is it just because the creators of the apps never updated to 5.x.x or is this a CM problem?

Other than that, everything is running nice and I'm quite impressed with this rom.
[Fire Original Android Development] sd_shadow:
It's an google/amazon-fire issue
[Fire Original Android Development] riverstyxxx:
Seems to be. I went to apkmirror and manually installed, so far everything's fine. I think it has to do with Android System Webview, it asked me to install in order to get one working. Thanks again!
[Fire Original Android Development] AwlsomeAlex:
I can confirm that FlashFire 0.31 fixes all problems experienced with CM12.1 upgrades (can't say fresh installs for sure) and fixes GApps. However it weirdly autoticks /system read/write for CM12.1, so u might wanna make it clear that BOTH have to be ticked off in your guides. [MENTION=5749760]ggow[/MENTION] But it all works ?
[Fire Original Android Development] ipdev:
Just installed using ff .31 & fireOS 5.1.1

- Installed from sd card.

Wipe:

System data, 3rd party apps, Dalvik cache, Internal storage & Cache partition.

Flash :

cm-12.1-20160404-UNOFFICIAL-ford.zip (Nothing checked.)

open_gapps-arm-5.1-pico-20160402.zip (Mount system read/write)

BETA-SuperSU-v2.71-20160331103524.zip (Mount system read/write)

Wipe:

Dalvik cache & Cache partition.

No problems. When to Google play and installed xda app.

I still had AROMA under settings unchecked.
[Fire Original Android Development] williamvito:
Having tried all of the suggested remedies without success in the past I am wondering if anyone with the latest 4/4 has been build been able to move apps to the sd card and have them stay on the device/function after reboot without the assist of a 3rd party method? Thanks in advance.
[Fire Original Android Development] DB126:
Not for nothing but I have long stopped twiddling FlashFire options and accept the defaults where it makes sense. At one time (when CM bricks first started happening) there was speculation changing this option or that would make a difference. Time has shown that not to be the case. Some of the defaults may have changed. Never experienced FlashFire failure except with v0.30 in controlled testing.

Always great to get individual feedback but each flash represents one user, one device (usually), one data point. Don't think we can "confirm" anything just yet. Hopefully these early results reflect a positive trend for everyone.

---------- Post added at 11:46 PM ---------- Previous post was at 11:41 PM ----------

Suggest using a 3rd party app. I wrote on this topic earlier today (here). Although one tool was mentioned in particular there are several options in the Play Store. You'll do best with something that creates symlinks on a dedicated partition vs a 'hack' that relocates apps to a standard FAT partition.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 06 April 2016

- Updated CM Code

- 01 April 2016 AOSP Security Patch Level
[Fire Original Android Development] kramalot:
Is this a new problem with 0404 (I'm still on 0311 seeing no need to update) and have never had a problem moving to sdcard with any version (have to use sdfix to enable the card after every update and some earlier versions would periodically lose write access)?
[Fire Original Android Development] drofmij:
Hi Guys,

I'm new to CM and ended up using a script from rootjunky to root: http://www.rootjunky.com/amazon-fire-5th-gen-supertool/

then used flashfire 0.31 to flash CM12.1 and google apps.

Worked great on my fire starting from FireOS 5.1.2 I ended up with smooth running system :D

One thing of note: I tried a few themes (I was careful to pick ones marked cm 12.1 or cm 12/13) from app store and they ended up crashing UI if you end up in that situation reboot in safe mode and uninstall the theme causing problems

Steps from: http://www.enrepublic.com/2015/01/how-to-fix-cm-12-system-ui-crash.html

Are there any themes that have worked for you guys? or is this an issue that I can fix?

Thanks,
[Fire Original Android Development] ggow:
New laptop just arrived back from repair. Looks good in test barring BIOS issue. So some down time while I get this setup.
[Fire Original Android Development] ggow:
Just did a build of lollipop:

Without ccache: 54 minutes

With ccache: 10 minutes

Bam! :victory:
[Fire Original Android Development] ipdev:
I'm running PitchBlack (7th G-Cyan) theme.

(This is their free version)

https://www.google.com/url?sa=t&sou...IzUbBi3BLWojoPj-g&sig2=StWwt1C3DECTMOl8KSsZzg
[Fire Original Android Development] ipdev:
Installed cm-12.1-20160406-UNOFFICIAL-ford.zip

Works fine so far.

AROMA under settings checked.

(AROMA was a .30 problem and was corrected in .31)
[Fire Original Android Development] booogermonkey:
Me too[emoji110] [emoji110] [emoji110] good combo
[Fire Original Android Development] bbstucki:
Stuck on CM Mod boot animation. The little blue face is mocking me, can't even boot to stock recovery. Help!
[Fire Original Android Development] sd_shadow:
which bootloader version 5.1.1?
[Fire Original Android Development] ipdev:
Can you get into fastboot?

It has taken me up to and over a minute holding power & vol - (button next to headphone jack) to get into Amazon system recovery. Once there I side loaded fireOS - downloaded from amazon link.

(I was lucky a few times and could just unlock the kernel with fastboot and then fastboot continue.)
[Fire Original Android Development] bbstucki:
Took 10 minutes to get to recovery. I was able to update via sideload to 5.1.2. Looks good again. Thanks!
[Fire Original Android Development] DB126:
Curious - 10 min continuous button hold or were there other events? Lots of soft bricked devices following FlashFire crap outs w/CM. This may offer a solution.
[Fire Original Android Development] theechap:
Hey all, just wanted to add 2 more Flashfire data points... I updated both my Fires to the 4/6 build without any problems at all. Used Flashfire v31 with the Aroma setting unchecked. The rom was installed from internal memory and neither check box option in Flashfire was checked, just like OP.

I didn't reinstall gapps because I don't really see a reason to since they keep themselves updated already. The playstore opened fine after the update so I think all is well so far.
[Fire Original Android Development] bbstucki:
Initially, I was using the power button and up volume (the side closer to the power button) and it would briefly display it was going into fastboot mode for about 3-5 seconds, but then it would proceed to the CM boot animation. I tried that countless times with the same result. I turned it off because it seemed like it was getting really warm. It was 10 minutes later that I looked at the screen and found the tablet had booted itself into recovery mode. At that point I wasted no time getting the stock rom update.

Further investigation:

When I was resetting up the tablet with root and the Now Launcher, I tried removing the fire launcher to make the Now Launcher the default, (I did this process with my 3 kids fire tabs, so I didn't think twice about it) but it seems like 5.1.2 didn't play well and again I was stuck on the boot animation, only this time is was the flamin fire logo. Power button and up volume did absolutely nothing. I decided to try power button and all buttons (mashed the up and down volume buttons) and it took me to the stock recovery, where I ran a factory reset. Because I'm a stubborn monkey, I repeated this process with the same results,... fire boot animation freeze. This time I tried power button + volume up, power button + volume button mash.... finally I used power button + volume down (like i do with my Nexus 7) and it booted into recovery.

I had other issues while rooting and getting everything right, but I think I booted to recovery 3 more times last night and each time used power button +volume down. Everything I read online suggested the volume up button does it. but I guess my tablet is special... maybe 5.1.2 made a switch.
[Fire Original Android Development] DB126:
On 5th gen Fires the hardware buttons are unlabeled; to my knowledge Amazon has not produced a guide outlining the intended function of each button. It is dangerous to assume which buttons are 'vol-up' or 'vol-down' based on observation in a particular rom as the functions can be easily remapped/reversed. That said, the standalone button near the USB port appears to consistently behave as one would expect: power/sleep/select.

From a full power off state:

- <power> + <volume button closest to the power button> = Fastboot (2+ second hold)

- <power> + <volume button closest to 3.5mm headphone jack> = Recovery Mode (5+ second hold)

Note: Recovery Mode does not always engage on first attempt. If boot not initiated with 10 sec release both buttons and try again.
[Fire Original Android Development] andPS2:
Market Helper doesnt seem to work anymore

only Cannot send device config in Step 3

could someone offer flashable zip that changes the build.prop (in a safe

way) Hashcode always had those for his ROM's
[Fire Original Android Development] DB126:
Change it to what? Nexus 7, Moto X, Galaxy S5? Everyone wants it a little different. And it's never a perfect solution as some apps are still identified as incompatible/unavailable. Most free apps can be snagged from a trusted 3rd party (eg: APKMirror, 1Mobile) and will auto-update from the play store once installed. No good solution for paid apps beyond bad manners which I want nothing to do with.

Diddling with build.prop is dangerous (as you point out) as it can lead to an unrecoverable device - especially when modified without the assistance of a dedicated editor. Permissions are a sticking point for many.

You are welcome to use any of Hashcode's roms for this device. Wait ...
[Fire Original Android Development] bbstucki:
Great info! Thanks. I have CM now. I think my problem yesterday was my flash fire wasn't updated to the newest version. I think I was on 0.24.0 so it stalled out in the middle of flashing. Finally realized I can get it from the play store now.
[Fire Original Android Development] bbstucki:
If anyone is looking to use Google Now launcher and make it a default on this build, try installing an older version of the launcher. You can download one here:

http://www.apkmirror.com/apk/google-inc/google-now-launcher/

Now Launcher 1.3 isn't recognized for some reason so it wont show up as an option when you are trying to select it as your home launcher. I uninstalled the launcher and then installed google-now-launcher-1-1-1-1706998 from the site, which was immediately identified and I was able to select it and make it default, then I went to the play store and update it. I just don't like Trebuchet or Nova as well. :)
[Fire Original Android Development] theechap:
While this does work to get apps installed on the device, I am still not allowed to update it through the store. I have to download an updated apk and do it manually. It's a pain. If there's something I'm missing here, please let me know. :)
[Fire Original Android Development] DB126:
The relatively few apps I have sideloaded typically have a counterpart on one of my 'supported' devices; perhaps that comes into play. I also don't maintain a huge portfolio of apps.
[Fire Original Android Development] norweeg:
Is anyone else having trouble flashing an update with flashfire? I'm trying to do a fresh install and flashfire doesn't seem to be doing anything its supposed to be doing as it keeps booting to the old CM build I had before.
[Fire Original Android Development] DB126:
Flashfire version? Old and new rom build identifiers? Have you tried?

- rebooting; FlashFire requires a lot of memory (according to dev)

- moving install file to internal storage if located elsewhere?
[Fire Original Android Development] norweeg:
flashfire 0.30, flashing to most recent build from 2nd most recent build, but want to do a fresh install. Flashfire is on internal storage, the zips are on the sd card. Sorry, I'm having a world of technology problems today and I forgot to include those details.
[Fire Original Android Development] DB126:
- upgrade to FF 0.31 (0.30 is problematic)

- move zips to internal storage (eliminate variables)

- do an initial 'dirty' flash without GAaps

- leave FF defaults as set; no need to change anything

Keep in mind installing/updating CM with FlashFire can result in a brick. Seems less likely with newer builds of FF and VM but still possible. Does the update warrant the risk? Might want to wait unless you are experiencing problems with current build.
[Fire Original Android Development] theechap:
Notes on CM12.1: Things have been overall very stable. I have only been having 2 recurring issues that are annoying...

1. Sometimes the wifi won't reconnect when I turn on the tablet from sleep. It says something like Internet Connection Failure. Then I have to go to wifi settings, tap the network, and say connect. This happens randomly every couple of days.

2. I have some apps that seem to just go missing. It's as though I uninstalled them. (Their icons are still on my Nova homescreen but they are grayed out.) These apps are all installed on internal memory, so it isn't an SD card problem. I believe they are all things from Amazons appstore. I have Titanium Backup so my workaround has just been to restore the apps manually when I find out they are missing.

Besides these 2 issues (which have occurred over multiple builds), everything else has been great. Good job [MENTION=5749760]ggow[/MENTION]!
[Fire Original Android Development] DB126:
I also experience the connect issue with roughly the same frequency. Device is configured to disable WiFi while sleeping. Have a hunch the glitch occurs managing an AP switch over during wake-up.
[Fire Original Android Development] norweeg:
The build I'm currently using doesn't handle encryption properly. The external SD card becomes read-only if I encrypt the device, so I hope the current build addresses that problem. Thanks for the suggestions. I have to find an apk for flashfire 0.31
[Fire Original Android Development] DB126:
Good luck with encryption and maintaining updates. Although I can't speak to FlashFire specifically other tools that facilitate modding/flashing locked devices tend to struggle with encryption.
[Fire Original Android Development] Signor Rossi:
I tried flashing it with FlashFire 30 and it failed again, but this time it simply stuck around 80% flashing

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] kmharman:
FF v.31 and latest ROM...

Updated to FF v.31 from v.28, flashed 4/6/16 ROM over one from March, using default (read/write enabled I believe), didn't reflash Gapps, worked perfectly on 2 different tablets that shipped with 5.1.1 and were rooted with Super Tool.
[Fire Original Android Development] DB126:
Upgrade to FF 0.31; fixes midflash hang.
[Fire Original Android Development] Signor Rossi:
Thanks this helped, I thought I was on the latest version already

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] kramalot:
Very occasional loss of WiFi on mine (better to rarely) s little more frequent on wife's but still v. Infrequent. No missing apps (no Amazon appstore).

Only persistent probs have been frequent reboots while charging (fixed by a clean install) and crashes when running Netflix. No solution to that one.
[Fire Original Android Development] DB126:
Possibly related. Experience occasional lockups while viewing YouTube vids in browser, typically after 30+ min. Noted parasitic reduction in memory during playback. Have not determined if browser (Opera), CM or device is the culprit. Need to do some testing with official YouTube app. Reboot required to fix.
[Fire Original Android Development] kramalot:
Mine might be ChromeCast related as that is the only way I use Netflix. And I probably should have said reboots rather than crashes as that's what I get, spontaneous reboots. I will check men status next time I use it.
[Fire Original Android Development] nyln:
Is it at all possible to do this on the HD 8 / 10 model? I will be trying soon.
[Fire Original Android Development] DB126:
No. Enjoy the brick of you try.
[Fire Original Android Development] nyln:
I was just about to do it. Thanks. I hate amazon os :(
[Fire Original Android Development] sd_shadow:
Installing cm12.1 has been tricky on the 2015 7in Fire, there have been several bricked devices

I would be a little surprised if I booted on the HD 10 or 8, and very well could brick them

if you are interested in building CM12.1 for those devices ggow maybe could offer some insight on what changes are needed to be compatible
[Fire Original Android Development] Handsome Jack:
I just got a used Fire 7 2015. How do I know if it has been installed CM-12.1 before?

Thank you.
[Fire Original Android Development] DB126:
Don't understand what you are asking. Did it come from Amazon or a 3rd party? If Amazon it obviously has FireOS. Otherwise check under settings (about tablet). It doesn't matter if CM was previously installed.
[Fire Original Android Development] platypoid:
Flashfire .31 and CM 4-6-16 - a okay

Just flashed the zip using Flashfire .31 and newest CM 4-6-16 build over older CM version - no wipes , didn't reflash gapps - everything went according to plan no glitches.
[Fire Original Android Development] berto648:
at it again. someone get this guy a medal. thanks man! got the family kindle tabs loaded up with cyano. these are great with chrome with one tab open. anything more these puppies will start stuttering. :silly:
[Fire Original Android Development] DB126:
Give it a go w/Opera. Same engine as chrome. I know, everyone has their favorite browser. I regularly have several tabs with moderately complex content open with limited lag/stuttering. Push hard and the 1GB memory starts to reveal itself. Still not bad.
[Fire Original Android Development] Neffy27:
Recommend Lightning browser, very lightweight without the bells and whistles (still has tabs). I got it from F-Droid repository.