yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] SageWilliams:
Anyone able to add another user, because I cannot find a way.
[Fire Original Android Development] drkbg:
Or maybe not enough other popular roms?
[Fire Original Android Development] DB126:
CM does have name recognition.
[Fire Original Android Development] ldeveraux:
This is what you told me too and I still don't believe it. I don't know how much Chainfire's paying you, but the newest Flashfire has major issues. [emoji6] I tried flashing multiple opengapps packages, even packages I had confirmed working months ago. I literally couldn't flash anything with the new version. I had to resort to TWRP. You can say what you will about it anyway, but it's broken for some people.
[Fire Original Android Development] DB126:
Thanks for reporting your experiences. Never said 0.30 was without issues. A bit difficult to decern what you are trying to say here. A previous post suggested 0.27 proved more sucessful but here you are saying a reversion to TWRP was necessary to complete the installation. Once GApps fails to flash it tends to resist further attempts. I do not know why this is but it is not unique to a specific version of FlashFire that I'm aware of.

ChainFire scripted the above but is having me post. Did I do ok, boss?
[Fire Original Android Development] ldeveraux:
No that's funny, it is. FF 27 has been very successful for me and others. In fact I haven't had any success with anything further. If you have, I'd love to know the magic formula. Newer versions just stop midway, maybe it has to with the "mount /system read/write" that is checked automatically now, I don't know. But whatever it is, it's new and unique to flashfire, since it won't work with old roms or gapps either.
[Fire Original Android Development] DB126:
Yeah, looks like there *may* be a problem with 0.30 as the symptoms you describe match another users experience on SlimLP which is rare. Crapped out in the middle and completely borked his device. I was quick to jump on 0.30 as it supposedly addressed some of the problems experienced with earlier versions (including 0.27) and seemed to be getting favorable reviews elsewhere. Not sure what to recommend now...although 0.27 appears to be marginally better that any of it's predecessors. Probably regret saying that when someone has a bad experience with that version.

Of course twrp is the best option if available...
[Fire Original Android Development] ldeveraux:
If the stupid BL wasn't locked, TWRP would be the easy/best solution. I had high hopes for the fixed releases of FF, but somehow, seems it's worse. :confused:
[Fire Original Android Development] DB126:
Give it time (I know; everyone hates that pacifier phrase). FF is still young, in beta and bound to have some bad iterations. Personally I don't hold out much hope for a bootloader vulnerability being identified/exploited. Amazon has a pretty good record keep that locked down. No source and code unique to Amazon devices. Not enough eyeballs/interest.
[Fire Original Android Development] booogermonkey:
IMHO what Chainfire has done and what he continues to do for our devices is amazing stuff. Beta is beta, and those are the pitfalls. Every confidence it can work as intended.....aaaand yes, I was paid for this[emoji12]
[Fire Original Android Development] Jstame:
I used .30 on two separate fire 7s to flash CM this morning. They both did exactly as your describing. Ran about halfway through then seemed to just freeze up. I only waited a few minutes before powering down and back on again figuring the first one was a goner but it was only about a minute or so after the CM boot logo started before it began loading the apps.(wheeew). I've been following the instructions in the OP to use Flashfire to install the rom but instead of flashing Gapps immediately after I use the "flash firmware package" option to flash a stock recovery img instead. Then flash Gapps once rom is up and running. Im really not sure if this affects my outcome or if I've just been lucky honestly? I'm still fairly new to this stuff but just thought if something happened to stock recovery during flash I would try to put it back. Out of the 6 fires i used flashfire to install roms on it was the only one i didnt flash this way that had to get replaced. Is it possible this has helped or did I just hit a little good luck streak?
[Fire Original Android Development] :
This isn't really a time will tell matter. The fact is that certain things work and certain things do not. Flashfire 0.30, for me, on multiple 5.1.2 (stock) Kindles, does not work properly. 0.27 works fine with these devices.

I posted my finds for those who run into the same problems and want to know how to get CM+OPENGAPPS on their 5.1.2 devices.
[Fire Original Android Development] DB126:
Thank you. Every post like yours contributes to the body of knowledge that leads toward one solution or another. That's the function of a community board. A singular event (yours, mine or anyone elses) does not lead to a decisive conclusion. Everything would be instant crapolla if we played by those rules. That said, there is mounting evidence, much of it posted in the past 12 hours, that FlashFire v0.30 has some issues. Maybe you reached that conclusion a day or two earlier. When I penned 'time will tell' the jury was still out - at least IMHO.

I do find it a bit ironic that those who try to provide guidance to others get saddled with criticism when things don't work out. Perhaps a better path is to stand back and watch.
[Fire Original Android Development] DB126:
Thanks for sharing. Seems FlashFire 0.30 is having issues with this device as evidenced by a slew of recent posts.

Interesting approach. I typically flash rom and GAaps separately which has worked well. It seems you add an intermediary step of (re)flashing stock recovery as a precaution (didn't know you could do that). Curious - what source do you use for the recovery image? That may be the solution to avoiding a non-accessible recovery if the CM flash goes bad.
[Fire Original Android Development] DB126:
As FYI seen a couple reports of FF 0.30 working fine with other ROMs for this device and one crap-out that completely borked the device. The latter was a special case so hard to draw definitive conclusion.

FlashFire and CM have always had a rocky relationship. I appreciate you and others have experienced favorable results with version 0.27 and hope that continues. Others have not been so fortunate with bricks and other failures reported on 0.24/0.26/0.27 and 0.30. Almost all with CM.

Current thoughts (may evolve in time):

- use of FlashFire with CM carries additional risks relative to other options

- jury is out on FlashFire; at present 0.30 does not appear to play well with CM 12.1

- FireOS 5.1.2 may introduce additional variables that play into FlashFire outcomes
[Fire Original Android Development] Neffy27:
I flash the ROM and gapps separately as well. I just switched to Nexus last night with v30. I'm afraid to try CM now whenever I get bored again. lol
[Fire Original Android Development] DB126:
As a test I attempted to flash the latest CM build (20160329) over an identical build with FF 0.30 accepting all default options. No additional actions were included. Crapped out mid-flash and hung on CM logo after restart. Stock recovery remained accessible so not a classic brick. Attempted to wipe cache from recovery menu; device hung. Repeated operation; format completed successfully this time but CM still hung on boot animation (expected). Performed a 'factory reset' and another cache flush for good measure. No change. Ultimately able to recovery device from a recent nandroid via TWRP (5.0.1 bootloader).

I have 'dirty flashed' CM with FlashFire before w/o incident (not risky for me given TWRP fallback). So yeah, FF 0.30 and CM 12.1 seem to have some issues - at least with B20160329. I still advise against flashing any variation of CM with FlashFire unless you willing to risk a brick or have an older bootloader. Those who go for it should stick to FF 0.27 with CM.
[Fire Original Android Development] booogermonkey:
I have 2 devices. 1 has the newer bootloader and I was fortunate enough to get cm working on it. Don't think I would risk it just for an update. If I did and it koffed, I definitely wouldn't complain about it. The 5.0 bootloaders are still out there tho. With amazons return policy might be a good idea to just keep trying until they send ya one.
[Fire Original Android Development] GhostRider86:
Hi,

I have two questions:

1. How do you change the date? It tells me it is set automatic, even when i turned WLAN off and the option to set the timezone automatically as well.

2. Flashfire 0.27 start, but closed directly after it. Only the version from the Play Store (0.30) stays open for me

My Issue is, that I got the mounting system error and only cm is flashed not the GApps

when flashing CM on my 5.1.2. After Powerdown and reboot CM seems to work, but Gapps are not flashed...

Back to Stock and tried again, with same result. I hoped your approach lead to my goal, but no success see my 2 questions.

Thanks in advance

Cheers
[Fire Original Android Development] DB126:
I believe (could be wrong) CM depends on Google Play Service framework to snag network time parameters. Not sure why the date option is not available when you toggle into manual mode. Might reflect a partial GAaps load. I would recycle again omitting any GAaps flash until CM is up and running. But there's always a risk with FF ....

You can sideload Google Plays services and all apps from APK Mirror. Bit of a pain but it works. You'll want 8.7.03 (2645110-236). Last three digits are important.

Side note

: you are obviously on CM because you want to be and are comfortable with potential FF issues (even w/0.27). Should that change suggest you take a peek at Nexus which is generic AOSP but can be quickly tweaked vis Xposed modules to carry the best visual/functional 'enhancements' baked into CM. GAaps and SuperSU built in. ChainFire and I share a 10% commission for every Nexus sold - be sure to mention our names at the register. :)

---------- Post added at 02:30 PM ---------- Previous post was at 01:33 PM ----------

For giggles and grins I took the freshly restored device from above and flashed the latest Nexus build (20160329) over the latest CM build (20160329) with FF 0.30 accepting all default options. Added a wipe action (system/cache/dalvik) at the top of the operations sequence. Did NOT wipe user data. FlashFire completed successfully and Nexus booted after rebuilding caches. Nexus was slow to start as it had to contend with my existing portfolio but everything eventually fired up including several apps that require root permissions (I was prompted).

So what's the significance?

- Further evidence FlashFire 0.30 is ok with other ROMs

- Offers a viable 'dirty' migration path for those who may not feel comfortable with the current FlashFire/CM relationship

Be aware this represents a single data point and may not be representative. Others experience may vary. Switching ROMs without a comprehensive data wipe can lead to unpredictable outcomes. You've been warned!
[Fire Original Android Development] Signor Rossi:
Hi I'm having issues flashing the latest update on top of an earlier version. It stuck at 85%

Tried it twice and always fails, might be due to latest FlashFire version?

Gesendet von meinem OnePlus One
[Fire Original Android Development] booogermonkey:
That seems to be the general consensus around here. Somewhat limited to cm, maybe[emoji15]
[Fire Original Android Development] Signor Rossi:
Thanks, I might try the earlier versions of FlashFire.

Anyone tried this?

Gesendet von meinem OnePlus One
[Fire Original Android Development] DB126:
Might be. You can try v0.27 as others have had luck with it. Or stick with the current CM build for now and be thankful you don't own a brick.
[Fire Original Android Development] Signor Rossi:
Will try 0.27, should not brick it

Gesendet von meinem OnePlus One
[Fire Original Android Development] ggow:
For those losing stock recovery via FlashFire, in Developer Options there is an option named 'Update Cyanogen recovery' - ensure this is switched off.

Is this occurring only on upgrades of CM or coming from FireOS?

I am investigating why this is happening. Think it might be the recovery-from-boot.p functionality been triggered. I am putting in place a potential solution which will mean the install-recovery.sh script will be ineffective at updating the recovery partition by removing the recovery-from-boot.p file. This way SuperSU root access won't be affected either.

Hopefully I'll have some time to get into it more this week and include the fix into the next release.
[Fire Original Android Development] booogermonkey:
So cool to be on an active thread again[emoji5]
[Fire Original Android Development] DB126:
Both - as evidenced in this post (I can cite others if needed that don't involve my devices)

---------- Post added at 03:49 PM ---------- Previous post was at 03:43 PM ----------

If you can find your way clear to include a minimal GAaps package (as is done w/Nexus) that will save a boatload of headaches for many attempting to install/update via FlashFire. Or perhaps two builds, one with GAaps and one without. Just a thought ...
[Fire Original Android Development] ggow:
I thought about including gapps, but I'm not sure I am allowed to include them in a cm ROM. If anyone knows any different then please let me know.
[Fire Original Android Development] Signor Rossi:
Installed the latest update using FlashFire 0.29

But with errors

Gesendet von meinem OnePlus One
[Fire Original Android Development] ipdev:
I had no luck with opengapps. (Shame since it is what I run on everything else.)

Found this version, MDPI_miniGAPPS-5.1.1-20160401-signed.zip, not sure were I got it but it works. (Google search.)

(If the one who made this gapps reads this, Danke! Works great!)

Edit

- Spoke to soon. Google error after restore.

Restored prior backup (no gapps)

installed MDPI via ff .30

Now working great again. (No errors yet)
[Fire Original Android Development] KYJoe:
Has CM 12.1 matured at all or is it the same as it was in the first post?

I currently have Nexus ROM installed and having problems with games Beeping/clicking/Making weird noises....is CM12 any better??

Does CM12 offer anything that would automatically install apps/games to sd card instead of moving/copying them with link2sd or app2sd ?
[Fire Original Android Development] DB126:
- AFAIK all custom roms experience some audio issues (anomalies) on this device; only FireOS is 'clean'

- Not sure I understand maturity question as all issues are shown closed as of late Jan 2016. Something in particular?

- Believe link2sd/ap2sd are still required with CM 12.1
[Fire Original Android Development] AwlsomeAlex:
Would like to report that FlashFire v0.30 failed to update CM12.1 to a more recent version, with it complaining:

mount: failed to mount /dev/block/platform/mtk-msdc.0/by-name/system at /system: Device or resource busy

unmount of /system failed; no such volume

script succeeded: result was []

Then GApps Pico was installing, but hanged on:

- Gathering device & ROM information

I tried to do this with FlashFire v0.27 but it wouldn't load and kept crashing, so I used v0.30 with both options UNCHECKED for the CM12.1 and one option (/system read/write) CHECKED for GApps.

Its been at the GApps for 15 minutes and i'm a bit stuck. WHAT DO I DO NOW? (FlashFire is still running. HELP!)

UPDATE #1: Got into CM12.1 after Hard Resetting data intact. I'm gonna fool around with FlashFire v0.30 to see if I can get it to install the newest update...... (Weirdly I got "Android is Upgrading" after the reset.

Update #2: The Device successfully updated to CM12.1 3/30/16, its just GApps failed, so the problem is something with GApps. Gonna play around with that.

Update #3: Tried both (Auto-Mount) and (/system read/write) but still hung on Gathering Device & ROM information. :/ Tried just (Auto-Mount) but still hung on Gathering (Instead of just saying ( - Mounting ) it said ( - Mounting /system) if that's helpful...... Finally just tried neither and it still failed. Said ( /system) again, but always hangs on Gathering. :/ I recommend going to the last known working GApps (Was Pico 2-29-16 for me) and use FlashFire v0.27 until this is all sorted out. :( But the CM12.1 update does work, just not GApps.

Update #4: Gonna get the lastlog and last_kmsg and will post it here and on the FlashFire Forums, hopefully thats gonna help someone. :(

---------- Post added at 01:57 AM ---------- Previous post was at 01:53 AM ----------

Same Error I Had.
[Fire Original Android Development] sandman512:
Quick question, flashfire did not seem to be working on my device. I go to open it and it shuts immediately. V.27
[Fire Original Android Development] Jstame:
Reboot and hope for the best. Had the same screen but CM worked for me after I turned it of then back on.

---------- Post added at 02:03 AM ---------- Previous post was at 02:02 AM ----------

Delete and reinstall...
[Fire Original Android Development] AwlsomeAlex:
It actually Updated, GApps is the problem. :)
[Fire Original Android Development] DB126:
I have seen this reported elsewhere with no resolution. You might want to wait for the next release (>0.30) to see if it more stable ... both when launching and flashing CM. Other versions are available here. Appears v0.28 was the first 'public' release. No experience with it.

You likely know the current cautions regarding FlashFire (any version) and CM 12.1 for this device: use at your own risk.
[Fire Original Android Development] Jstame:
I downgraded Flashfire to v.29 and had to flash a nano package of gapps to get it to work. V.29 seemed to work smoothly on one of my fires that I use that I test that version on. Be aware it's still very risky using Flashfire with CM currently.
[Fire Original Android Development] AwlsomeAlex:
I'll try that with Pico until it is fixed for v0.30. Thanks!
[Fire Original Android Development] DB126:
Restore (access to) Stock Recovery

A big shoutout to [MENTION=7230143]Jstame[/MENTION] for sharing this info!

Edit: Please see [MENTION=7230143]Jstame[/MENTION]'s excellent guide here. Also note a recent CM build update (here) may reduce/eliminate recovery related issues.

I have not tested yet as all my devices have functioning recoveries. Ideal candidates:

- a bootable device that does not have a functioning stock recovery

- someone willing to include as an additional operation in a standard CM install/upgrade (via FlashFire)

I am not sure if this actually replaces the stock recovery or simply enables access to the existing partition contents. I was under the impression the recovery partition could not be altered on a device with a locked bootloader.

Also possible this approach would work with Flashify (also untested).

[MENTION=7230143]Jstame[/MENTION]'s PM (excerpt):

Here's the link to the stock recovery for the Fire 7. I lost recovery trying to flash twrp on a couple fires before I knew less then the little I know now. Searched every where for a solution and found nothing at all. I'd imagine a lot of people that have lost access to recovery don't even realize it. I didn't know until I tried to sideload stock firmware after i deleted a bit too much from the system. Finally after bit of playing with Flashfire I learned how to flash a recovery image. Ended up making a backup of a working recovery from one of my other fires then I used Flashfire to flash it on the devices that lost access. Rebooted to recovery and it was good to go. After seeing the bricks with CM via Flashfire I figured it can't hurt adding it to the actions after the Rom. Fixed 2 stock recoveries this way and had 5 successful installs of CM on 5 diff fires even after Flashfire hung on 2 Flashes.

Related post -> here

{link removed - see [MENTION=7230143]Jstame[/MENTION]'s guide referenced above}
[Fire Original Android Development] GhostRider86:
The time change in FireOS is the issue, not in CM. Sorry for not pointing out this before.

I'll try to sideload the GApps as you suggested, because CM is working properly.
[Fire Original Android Development] ggow:
This will be fixed in the new release today.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 04 April 2016

- Updated CM Code

- Prevent recovery been overwritten: Modify build system to prevent recovery-resource.dat and recovery-from-boot.p from been generated. This needs testing preferably by people with the ability to boot TWRP.

- Fixed failure to mount /system partition error due to change in build system
[Fire Original Android Development] sandman512:
Thanks Davey, funny though, it was working fine and then all the sudden stopped. FWIW, I have been updating CM each time via FF with no issues. [MENTION=5749760]ggow[/MENTION], what is the best way to upgrade to the latest build? Thanks!
[Fire Original Android Development] ggow:
- Always prefer TWRP

- But if you can't boot TWRP then I would suggest trying v0.29 or v0.30 of FlashFire
[Fire Original Android Development] ldeveraux:
I think cm isn't skewed to include it as per their deal with Google. Imho, doesn't apply to you, since you aren't a cm employee. [emoji6] I don't see the big deal including it...
[Fire Original Android Development] DB126:
Possible Amazon removed manual date/time options from FireOS. Don't have a copy loaded at present to check.
[Fire Original Android Development] norweeg:
I've seen reports on this thread that encryption works, but every time I encrypt my device, I lose the ability to move any data to the external SD card. I can still access data and apps already on the card at the time of encryption, but those apps will no longer receive updates, nor can I move any more data to the external storage. Is that normal? Is anyone else having this issue? If only CM13 were available and ported to this device so I wouldn't have this problem because it's really killing me right now!
[Fire Original Android Development] DB126:
Hum. While a security wonk I rarely post-encrypt portable devices preferring to protect key apps and their respective data repositories. Not to say whole device encryption is bad - just a bit immature. That is changing quickly in the mainstream market. Apple is doing it right as are newer Android builds/devices.

Sorry to digress - no direct experience with the problem you are experiencing.

Unlikely CM13 or any Android 6.x variation will come to this device as the bootloader remains locked. Custom ROMs still utilize the stock kernel which is Lollipop based.
[Fire Original Android Development] DB126:
Success!! Performed the same steps as outlined here but used B20160404. FlashFire executed to completion and the updated ROM booted w/o incident. Recovery remained intact.

Thoughts:

- first successful flash of CM 12.1 using FlashFire 0.30. Yea!

- never lost access to stock recovery - even when flashes ended badly. So probably not a good test of that.

- one device, one data point, one user. Caution still advised using FlashFire to update CM (for now).

- 5.0.1 bootloader and accompanying recovery; shouldn't matter but noted for completeness.
[Fire Original Android Development] riverstyxxx:
Didnt work for me via Flashfire. Followed all the settings and instructions, it got stuck at the cm install and went nowhere for about 45 minutes, eventually rebooted and cm mod started but there was no root access so, reverted back to 5.1.2. Don't recommend this.
[Fire Original Android Development] blueandhack:
Me too. It also stop on flashfire, and I waited for 30 mins . I have no idea for that.
[Fire Original Android Development] riverstyxxx:
It got as far as format, that went ok, then installing cg gave some very wierd error messages about mounting and errors. Only reason I think is because I installed it from sd-card. I just install fire nexus, took no more than 5 minutes, works good and it includes gapps pre-installed. Did you load the zip images from sd-card or system memory? If the former, then try system memory and see if works.