yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] glockman4519:
Latest update is running superbly on two of the 3 fire tabs that I have. On the 5.0.2 bootloader tablet that uses TWRP has had this ROM on it from day one and I just updated it to the latest and it is still as smooth as butter. The other I updated to the 5.1.1 and am running or flashing via Flashfire, I had RR on it at first. Then The battery ended up dying on me and that threw me into a bootloop, of coarse, so I used "rootjunky" super tool to get back to stock, then root and finally get this rom on it via Flashfire. I really think this ROM just runs better on that tablet.

Anyways, thank you so much for all of your work and to "rootjunky" for his tool and videos.
[Fire Original Android Development] njackson-uk:
Got the Kindle today, managed used rootjunky's tool and flashed cm12.1 with flashfire. I followed the instructions in the first post carefully, with the wipe at the top.

It's now stuck on the amazon logo when starting up. I've tried waiting 10 minutes, but the screen doesnt change from the initial logo. I can still boot into recovery and fastboot.

Any ideas? Or shall I just sideload 5.1.2 back on it and start again?
[Fire Original Android Development] ggow:
Your best bet is to sideload fireos and try again
[Fire Original Android Development] DB126:
Additional thoughts (after 5.1.2 reload):

- if you intend to go straight to CM don't bother registering device with Amazon as this sometimes complicates rooting w/kingroot

- be sure to replace Kinguser with SuperSU (believe the SuperTool does this by default)

- use the latest version of FlashFire (currently 0.50)

- leave all zip options at their default values (no need to twiddle mount options)

- wipe should include system, user apps/data, dalvik and cache
[Fire Original Android Development] ipdev:
Never thought about that before. Might be why I haven't problems.

(Mine were not registered to my Amazon account before flash.)
[Fire Original Android Development] ggow:
I'm updating the OP so I'll replace the old flashfire instructions with this info.

EDIT:

- Flashing instructions updated on OP

- [MENTION=5488402]Davey126[/MENTION] - would you mind checking if it's ok?
[Fire Original Android Development] DB126:
Edit:

- didn't see [MENTION=5749760]ggow[/MENTION]'s follow-up (simultaneous posts)

- revised OP looks great

- following suggestion still applies but may be awkward; perhaps just a generic note stating OP always contains most current guidance which may differ from earlier posts, videos, etc.

Previous:

Suggest including a bullet noting options in RootJunky's *excellent* videos were for early versions of FlashFire and may not apply to recent releases; guidance in OP should be followed instead.
[Fire Original Android Development] ggow:
Done :)
[Fire Original Android Development] ogpog:
I just wanted to say that I have CM12.1 with Pico OpenGApps on my KFFOWI :D

There were a couple of things that post #1 could have included to make it even easier (perhaps these things are mentioned elsewhere, or just blatantly obvious to most people).

1. How to select GApps: I had to look up the CM12.1 Android version (5.1) and arch (ARM) that I need to sleect on http://opengapps.org.

2. Where to place the two zip files on the device so that FlashFire can find them. I used adb to push them to /storage/emulated/legacy and then used adb shell with su to move them into /data/media/0/Download (because I could not adb push to /data/media/0/Download due to permission denied.

But, all things considered, being able to do this is fantastic. This morning, I was running stock 5.1.4 and now I am running CM12.1.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 14 June 2016

- June 2016 AOSP Security Patch Level

- Added CIFS Support (Instructions TBD)

- Switch to using lastest update-kindle-37.5.4.4_user_544271020 binaries and boot.img

EDIT:

- I'll put the guide for setting up CIFS in a thread within the general section of this forum.

EDIT:

- Guide for CIFS shares is here

- Also added Question 5 on FAQ linking to the Guide.
[Fire Original Android Development] njackson-uk:
Tahnks Davey and Ggow, reloaded 5.1.2 and then went throigh the process again. Now got cm12 on the device. Excellent for £50!
[Fire Original Android Development] glockman4519:
Dude, this is just too cool. I just took the time to update my 5.0.2 tablet to your last update a couple days ago and now this,? Can't wait to get this updated again. I just love this tablet and the funny thing is I got it when they were only like $35.00 (got 3 of them) so this running your build is a hell of a tablet for that price.
[Fire Original Android Development] erickrocks1126:
I also got mine when they were on sale for $35; bought to tinker with and flash ROMs like this. With custom ROMs basically making this a Nexus tablet with extra ROM capability built in, and at $35, this sure is one heck of a deal! Only wish they had a 16GB version at the time when they went on sale.
[Fire Original Android Development] DB126:
JFYI - in the US Amazon is currently running a promotion knocking $10 off both 8GB and 16GB models. Will likely end this weekend (see post date for timings).
[Fire Original Android Development] false_chicken:
Current FlashFire Insturctions

Hey guys. I just purchased a kindle fire and am awaiting for it to arrive. In the post it was mentioned that the video for installing using the old flashfire is no longer valid. How do I get flashfire installed currently? It says it requires root so I assume I will need to root the device first? If so what is the latest way of doing that? I am just afraid of following some old instructions and bricking the device. Thanks!
[Fire Original Android Development] ggow:
- Install FlashFire 0.50 as would any older FlashFire version

- Then follow the instructions on the OP
[Fire Original Android Development] samijam:
EDIT: I think you might have to downgrade to 5.1.2 first by downloading the 5.1.2 firmware and installing it from recovery via adb sideload.

Which video? I followed an older video for SuperTool. It was mostly the same, but the tool has been updated. It has the following options:

Install Google Play Store

Root Device

Block OTA Updates

Remove Lock Screen Ads

Nova Launcher Install

FlashFire App Install

Xposed Framework Install

If you want to install CM 12.1, then you will want to root using this tool followed by FlashFire app install(will install version 0.50). Then follow instructions in OP to install CM 12.1
[Fire Original Android Development] false_chicken:
Ok awesome! Thanks!
[Fire Original Android Development] erickrocks1126:
Thanks! Yeah I saw that and was thinking of getting a 16GB version.
[Fire Original Android Development] glockman4519:
That is good to know. Thanks for the heads up
[Fire Original Android Development] exesse:
Hey!

Thank you ggow for the awesome ROM, using it for couple days now and pretty happy about it!

Raised AnTuTu score from 20302 (Stock firmware) to 26801 (CM 12.1).

If someone is ineterested I wrote two step-by-step manual's:

how to Downgrade to 5.1.2 firmware (Ubuntu)

how to install corectly CM 12.1
[Fire Original Android Development] DB126:
CM guide is nicely done; didn't look at the other. Suggestion: leave all FlashFire zip options at their default values. There is no need to alter the developers selections nor tick 'auto-mount' for GAaps.
[Fire Original Android Development] exesse:
Thank you for your note!

I did two attempts to flash rom. First one was with default mount flash options and OpenGAps-mini package. And as result play store wasn't installed. On the second try i tickle auto-mount and use OpenGAps-pico version and everything was in perfect working condition. So not sure issue was in the type of package or auto-mount.
[Fire Original Android Development] DB126:
Interesting observation. Pico & Mini are both smaller GAaps packages and should have flashed fine. On the second attempt was Pico the only zip included in FlashFire's operations queue or did you reflash CM 12.1 concurrently?
[Fire Original Android Development] exesse:
I tried to root cm 12.1 on that first time so i'll be able to flash again, but it doesn't happend. So i adb restored to fire os 5.1.2, rooted and then flashed again cm 12.1, pico and supersu.
[Fire Original Android Development] DB126:
Hum - sounds like there may have been other issues on the first flash attempt.

Note CM 12.1 is already rooted when installed although the integrated root manager is not enabled by default (under developer options). SuperSU is an alternative root manager that overrides the integrated tool.
[Fire Original Android Development] exesse:
I just wanted to minimize risks on the second attemp and flashed supersu in case if something went wrong.
[Fire Original Android Development] DB126:
Understood. SuperSU is preferred by many (self included). However, it does not increase/decrease flash risk. Glad your device is working well and you took the time to document experiences.
[Fire Original Android Development] exesse:
Hope my experience could help someone [emoji4]
[Fire Original Android Development] prazola:
Last build is laggy on my dire and overheating while whatching netflix video until it reboots...and more battery drain.

D/OpenGLRenderer( 3954): Use EGL_SWAP_BEHAVIOR_PRESERVED: true
D/Atlas ( 3954): Validating map...
I/OpenGLRenderer( 3954): Initialized EGL, version 1.4
D/OpenGLRenderer( 3954): Enabling debug mode 0
E/[EGL-ERROR]( 3954): egl_image* _egl_create_image_ANDROID_native_buffer(egl_display*, egl_context*, EGLClientBuffer, EGLint*, void*):593: CHUN try create image with crop 0,0,0,0
E/ ( 3954): CHUN map external image rgb 768 x 768
I/MaliEGL ( 3954): [Mali]window_type=1, is_framebuffer=0, errnum = 0
I/MaliEGL ( 3954): [Mali]surface->num_buffers=4, surface->num_frames=3, win_min_undequeued=1
I/MaliEGL ( 3954): [Mali]max_allowed_dequeued_buffers=3
I/Timeline( 3954): Timeline: Activity_idle id: android.os.BinderProxy@21621662 time:808128
I/MaliEGL ( 3954): [Mali]window_type=1, is_framebuffer=0, errnum = 0
I/MaliEGL ( 3954): [Mali]surface->num_buffers=4, surface->num_frames=3, win_min_undequeued=1
I/MaliEGL ( 3954): [Mali]max_allowed_dequeued_buffers=3
W/InputEventReceiver( 3954): Attempted to finish an input event but the input event receiver has already been disposed.
I/MaliEGL ( 3954): [Mali]window_type=1, is_framebuffer=0, errnum = 0
I/MaliEGL ( 3954): [Mali]surface->num_buffers=4, surface->num_frames=3, win_min_undequeued=1
I/MaliEGL ( 3954): [Mali]max_allowed_dequeued_buffers=3
W/InputEventReceiver( 3954): Attempted to finish an input event but the input event receiver has already been disposed.
[Fire Original Android Development] DB126:
No problem here. B20160614 responsive; Netflix stable with no device heating; battery consumption normal. Look for a rogue background app/process/service. If issue persists do a full CM flush-&-fill, possibly preserving user apps/data (although better to reinstall those too).
[Fire Original Android Development] Sumaech:
I want to update my rom, but the upgrade instructions are not super clear...

Upgrading from FlashFire 0.50

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

- Navigate to and choose the latest Cyanogenmod Zip

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

- Navigate to and choose the latest Open Gapps Zip.

- Accept defaults

- Click the Red + again and choose 'Wipe'

- ONLY tick Dalvik and Cache.

- Press the big FLASH button.

Do I need to change the order at all?

What about "mount /system read/write" Do I leave that checked or no?

On wipe what options do I choose besides dalvik cache? (cache partition, or no)

Please respond soon.

Thanks,
[Fire Original Android Development] GhostRider86:
Instructions are pretty clear. Default options, no need to change order, wipe cache and dalvik cache
[Fire Original Android Development] Cicciux95:
Hi, I've tried to flash the rom with flashfire, but at the end of the installation I have FireOS, why? It's like a factory reset without flashing the new rom
[Fire Original Android Development] GhostRider86:
Did you wiped it?
[Fire Original Android Development] Cicciux95:
Yes, i wiped dalvin, system and 3rd apps and the first time also cache partition. I selected the rom from internal storage the first time and from sd card the second time. I didn't flash gapps, is that the problem?
[Fire Original Android Development] Hinazooke:
Hey, I am having a wierd issue with my SD card.

When my tablet calculates if I have enough space to download something, it reads everything on my SD card as being located on my internal storage. This is especially weird, because when the calculations come through, it shows (in storage settings) that i've only used about 1GB on the kindles internal storage. What gives? It can tell that i'm not running out of space, so why is it glitching out like this?

Also side note there is no button to eject SD card safely.
[Fire Original Android Development] GhostRider86:
No gapps mean no gapps, nothing to do with cm. Do you have a log?
[Fire Original Android Development] Cicciux95:
ok, I didn't move wipe on the top of the list :D
[Fire Original Android Development] GhostRider86:
No need to eject sd card, no apps or data access. If you want to change sd card, shutdown for be super safe

---------- Post added at 10:29 PM ---------- Previous post was at 10:29 PM ----------

Ok than its clear☺
[Fire Original Android Development] Hinazooke:
Ok what? I realize the not being able to eject SD card issue isn't that big of a deal, i just brought it up for meantionings sake. Can we please focus on the fact that there is almost

zero

SD card compatibility in my system right now? Not trying to sound like a smartass, but I am a little angry because no matter what i try I cant fix this issue.
[Fire Original Android Development] GhostRider86:
Read from #2682.

#2689 seems to be interesting for you
[Fire Original Android Development] Hinazooke:
Thanks. That's the exact same issue I am having. Sadly, he stopped responding after receiving a few suggestions on how to fix his problem, and none of the suggestions given to him work for me.
[Fire Original Android Development] Sumaech:
When you mean "wipe cache" do you mean cache partition ?
[Fire Original Android Development] DB126:
Yep.

JFYI - you may find the following thread helpful, especially the video overview of FlashFire in the first post. Note some of the screens and options may differ slightly from the current recommended version of FlashFire (0.50). Be sure to follow the guidance in the first post of this thread regarding options specific to cm-12.1.

http://xdaforums.com/amazon-fire/general/how-to-flashfire-app-to-install-rom-t3269839
[Fire Original Android Development] cjeee:
Im using the most recent build can't access my SD card either. Theres only an option to format the SD card and it doesn't show the free space left on it or anything. I can't even access it with a file explorer. Unpon removing the SD card, the option to erase the SD card gets grayed out. So it knows theres an SD card, but it just wont mount it
[Fire Original Android Development] DB126:
I experienced no issues with installed 32GB SD card before/after flashing the most recent CM build. Check the card format in another device. Should be vfat although other formats will also work (eg: ext4) and may be required by some utilities. Many cards come formatted as fat32 which isn't as broadly compatible.

There are many apps for servicing SD cards. I like diskinfo for viewing existing partition detail; you'll need to use something else to change formats and perform other maintenance.

Also try a cold restart - preferably with SD card removed. One fully booted reinsert the card and see if it is recognized.
[Fire Original Android Development] cjeee:
It was working just fine with stock 5.1.1 though,and I had it working on this latest build once. Had to restart and not oit won't mount it, and its not damaged or anything either
[Fire Original Android Development] DB126:
Yep - happens, especially on pre-formatted and/or inexpensive cards. Suggest copying contents to another device and then reformatting. Usually fixes compatibility issues - permanently on better cards.
[Fire Original Android Development] cjeee:
Ill try it and let you know what happens, thanks
[Fire Original Android Development] cjeee:
Its been exFAT the whole time. The sd card was working fine on the official Frimware as well as other devices. Once I flashed this verson with FlashFire it caused these issues. I followed the directions perfectly as well. Ive also done multiple factory resets and the issue still remains.
[Fire Original Android Development] false_chicken:
Hey guys. I installed this on my new Fire 7 and it seems to work great! But I am having problems with getting root in the new CM install. I see in the OP that "built in root access" is a thing but I cannot su in the terminal and the SuperUser app will not let me change its setting. Its always disabled. Any suggestions? I am probably missing something. I at first thought that I simply didn't have root anymore but kingroot always fails at 16% when running it in CM. Also the SuperUser app always reports to me that its out of date but doesn't offer me a way to update it. Thanks.

EDIT: I found the Root Access setting in Developer Options and changed it to Apps and ADB and this is reflected in the settings for SuperUser but I can never seem to get a root shell (#). It always just says changes to "255|shell@ford" and idk what that means but I am not permitted to load any modules it seems so I assume I am not root.

EDIT 2: Updated the SU binary from the one in the CIFS tutorial and it works now :). Thanks anyway.
[Fire Original Android Development] ggow:
To use built in root you have to enable in developer options then reboot for the change to take effect.
[Fire Original Android Development] false_chicken:
Yeah I think I might have just did the reboot automatically in FlashFire after flashing the latest SU and assumed it was the newer SU but was actually the result of the reboot. Thanks.
[Fire Original Android Development] DB126:
Grabbed a fresh 32GB card, formatted exFAT (Win 10) and experienced the same problem. Device recognizes card is present but can/will not read it and only offers erase as an option which formats the card vFAT.

A search reveals reoccurring issues with exFAT support on newer CM builds. Microsoft exerts control over exFAT and CM may be caught up in licensing issues. Many 3rd party tools do not support exFAT for this reason. The apparent regression may in fact be intentional.

Your options include using a different format or going with a different rom. If Google paid the licensing fees then Nexus should work. Don't know about the others.

[MENTION=5749760]ggow[/MENTION] - for awareness.
[Fire Original Android Development] jrk190:
This might be frowned upon, but what are the chances of getting CM13? I don't know if the mtk sources or kernel will work, but it'd be super nice to see this tablet remain up to date!
[Fire Original Android Development] DB126:
Although not mine to answer I'd guess chances are slim to none unless the bootloader is cracked (kernel incompatibility) or Amazon releases a MM based version of FireOS.
[Fire Original Android Development] cedricbr:
Hi just flashed my fire tbalet to the latest CM 12.1 (14 june) and i discovered that i don't have root anymore. I already activated the developer options and activated root. After a reboot flashfire keeps telling me that i'm not root.

Can somebody help me?
[Fire Original Android Development] batatok:
Hey there.

I had the same issue. Did you install SuperSu (i.e. via Playstore)? If it still doesn't work for you, you could use the Supertool to aquire root again. I did that with Resurrection Remix. Worked then. Hope it works for you.
[Fire Original Android Development] DB126:
Tough one lacking an obvious explanation. Likely remediation is a reload of FireOS via the stock recovery menu. The lack of a true recovery environment is a killer.
[Fire Original Android Development] rudolfm:
Try setting root to "Apps only" in the developer options.. This actually got root working in my Kindle Fire HD with CM 12.1. I have no idea why this helped.
[Fire Original Android Development] bigpapa007:
Hi, i would like to know if i would see a real life performance diference if i update to the 2016-06-14 having right now the 2015-12-16 build.

I want to know if doing all the steps again to flash new version is worth it.

Thanks.
[Fire Original Android Development] DB126:
Short answer - no. That said, it is trivial to flash a later build of the same rom. 5-10 min using FlashFire. See OP for instructions.
[Fire Original Android Development] ldeveraux:
if you're already on an older version of this Rom, all you have to do to upgrade is use flashfire. Only takes a few minutes, there's no reason not to...
[Fire Original Android Development] castlec:
The issue I was experiencing was definitely due to two things

1) The wipe was in the wrong order. FlashFire was always putting wipe after flash. If I long tap and dragged it up, it would do the wipe first

2) FlashFire doesn't set the R/W options on flash correctly for all packages
[Fire Original Android Development] GhostRider86:
That's described in the first post...
[Fire Original Android Development] DB126:
Wait...when does current guidance from the rom dev/maintainer trump a 6 month old video (still outstanding) along with tons of related posts in this thread and the index outlining the proper use of FlashFire. Just say'in... :)

At least read the OP (err...that would be the first post) before attempting to flash crap.
[Fire Original Android Development] atroph:
Is the weather widget that is part of cLock depreciated?

Yahoo weather never seems to update and open weather seems to be about 10+ degrees off.
[Fire Original Android Development] Doggy77:
Yes, the cyanogen widget "cLock" does not work anymore. Try the app "Chronus" from playstore instead. The free variant works fine for me on several devices.

Greets, doggy77
[Fire Original Android Development] TheLoonyRebel:
I haven't used CM 12.1 on my Fire tablet since I believe February or so. Has the random reboot issue especially while doing app updates been fixed?
[Fire Original Android Development] DB126:
Don't believe this was a widespread problem but there have been no recent reports of spontaneous reboots; suggest updating as see what happens. If issue persists do a fully system/data wipe and reload CM or another custom ROM.