yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
Xposed framework works well but xstana module likely won't due to CM navbar overlays. Suggest going with AOSP rom (eg: Nexus) if seeking full control over UI with Xposed.
[Fire Original Android Development] whodat711:
after rooting and getting cyanogenmod installed , i tried installing a theme which ended up having all apps close upon trying to open them and i figured i could do a factory reset and fix it , well i lost root and now im unsure how to regain root back because kingroot isnt working now.. any suggestions? *facepalm* fkn cm themes!!

I did do a full backup onto /sdcard/ in flashfire before flashing cyanogenmod however flashfire wont run without root either.
[Fire Original Android Development] GhostRider86:
Reboot, try re-root. Otherwise sideload installed FireOS version for a clean reinstall, but this should have been done by factory reset I guess
[Fire Original Android Development] whodat711:
guessing i could have done something else to remove the theme settings... id like to learn more about this and make my own theme. assuming that the theme i selected was borked due to it being made for a different version of CM...

and, also assuming that cyanogenmod patched kingroot's exploits... however im unsure of which file to sideload, the 5.1.2 fireOS downgrade?
[Fire Original Android Development] DB126:
Once CM 12.1 looses root it's typically game over. On devices that support booting a custom recovery (eg: TWRP) I usually need to dirty flash CM (optionally SuperSU) to regain privileged access; flashing SuperSU alone doesn't do it. That path is not available for most 5th gen Fire devices. You'll likely have to reload FireOS and start from scratch as recommended by [MENTION=7367623]GhostRider86[/MENTION]. And yeah, stay away from CM 12.1 themes. Your experience is not atypical.
[Fire Original Android Development] GhostRider86:
Flash previous installed FireOS version, never an older version. Do not try to downgrade this way, only if experienced xda-cm-amazon guys tell you to do it
[Fire Original Android Development] whodat711:
well i had 5.1.3 i believe to start with , then i had to downgrade to 5.1.2 to gain root, so unsure which to sideload..
[Fire Original Android Development] GhostRider86:
So in your case 5.1.2 was installed before FlashFire was used
[Fire Original Android Development] whodat711:
Correct, and I did a FlashFire full backup before i installed CM

so do i go back to 5.1.3 , then downgrade to 5.1.2 , then root, and back to CM? or can I go to 5.1.2 and then root and CM?
[Fire Original Android Development] GhostRider86:
Both ways should work in you case
[Fire Original Android Development] whodat711:
[root@power ../Firmware-Downgrade-to-Fire-OS-5.1.2-Supertool] # adb sideload update-kindle-global-37.5.4.2_user_542168620.bin

serving: 'update-kindle-global-37.5.4.2_user_542168620.bin' (~54%)

or should i sideload fire-OS-5.1.2-update-kindle-global-37.5.4.2_user_542168620.bin instead?? dont need another brick =\ Yall help is much appreciated!!!

**edited**

seeing as they have the same md5sum i imagine they both are the same

[root@power ../modZ/fire/fire/Firmware] # md5sum fire-OS-5.1.2-update-kindle-global-37.5.4.2_user_542168620.bin

5b0dcc957def3accff58bf33794d6d88 fire-OS-5.1.2-update-kindle-global-37.5.4.2_user_542168620.bin

[root@power ../modZ/fire/fire/Firmware] # md5sum Firmware-Downgrade-to-Fire-OS-5.1.2-Supertool/update-kindle-global-37.5.4.2_user_542168620.bin

5b0dcc957def3accff58bf33794d6d88 Firmware-Downgrade-to-Fire-OS-5.1.2-Supertool/update-kindle-global-37.5.4.2_user_542168620.bin

[root@power ../modZ/fire/fire/Firmware] #
[Fire Original Android Development] whodat711:
ok i made it back to flashfire and am about to flash CM again , this time do I want to "Inject SuperSU" ???

since I do not have CM recovery or TWRP??

how about these "EverRoot" settings....?

Enable ADB? Set usb mode to PTP+ADB. Reconnect cable once Android is up and running to trigger the authorization dialog. ??

preserve recovery? Try to prevent Android overwriting the currently installed recovery at boot. May break OTAs. ??

disable setup wizard? Attempt to force skip the setup wizard during first boot. Only works on some devices. May break OTAs. ??
[Fire Original Android Development] DB126:
No - follow flashing instructions in OP. SuperSU is neither required nor recommended for most users.
[Fire Original Android Development] GhostRider86:
... And if you want SuperSU, flash CM with FlashFire (see OP for instructions) go into developer options, enable root for apps, reboot and then install SuperSU from PlayStore
[Fire Original Android Development] whodat711:
thanks much GhostRider86!!

---------- Post added at 07:08 PM ---------- Previous post was at 07:07 PM ----------

one last question, should i "Install SuperSU into /system" ?
[Fire Original Android Development] GhostRider86:
Don't touch SuperSU options
[Fire Original Android Development] whodat711:
hmm so i reinstalled CM and still having trouble getting supersu installed... keeps saying failed.. am i supposed to use twrp somehow?

not seeing developer options anywhere..
[Fire Original Android Development] kyledowling:
Enable cm root in developer options. After you do that, you can install SuperSU from play store or flash the zip via FlashFire.
[Fire Original Android Development] whodat711:
sorry for the noobish question but i cannot find developer option in cm

nevermind i think i find out .... enable root for apps & adb?

w00p i got it thank you guys !

any idea what themes are safe for this ROM?
[Fire Original Android Development] smokestacknj:
was just wondering. im gonna stick with this for now. thanks man
[Fire Original Android Development] DB126:
None - stick with the default theme or be prepared to reload FireOS when the bottom falls out.
[Fire Original Android Development] Marsu42:
+1 ... I discovered it's absolutely possible to shoot yourself in the foot when playing around too much esp. on a rooted device, I now know that you shouldn't enable multiple lockscreen mods at the same time and on another occasion experienced what "bootloop" means after trying too many xposed modules :-p

Fortunately, the fireos-kingroot-reflash routine works safely and is well documented, it just takes some time. And you don't want to play god with your device while on holiday w/o desktop pc access or if you really need the device for work with no interruptions.
[Fire Original Android Development] fapste:
I bought this tablet today. The online shopping company that I used to buy the product kinda scammed me by sending me a refurbished device rather then a brand new. Meaning the tablet didn't come in Amazon tablet's packaging. It didn't have fireOS installed and came installed with CM 5.1.1.

I want to stress test the tablet to see if it has any malfunctions or not. Currently the tablet is showing NULL IMEI. Is this something to be concerned about? What else should I check if the tablet is 2015 Amazon Fire 7?
[Fire Original Android Development] GhostRider86:
5.1.1 is FireOS...

No modem means no imei, this device never have one
[Fire Original Android Development] borisboing:
I've installed and used Stay Stock ( ｈｔｔｐｓ：／／ｐｌａｙ.ｇｏｏｇｌｅ.ｃｏｍ/store/apps/details?id=com.sv.staystock ) and Playful Flat ( ｈｔｔｐｓ：／／ｐｌａｙ.ｇｏｏｇｌｅ.ｃｏｍ/store/apps/details?id=com.rOse.playful ) on multiple KKFOWI running CM12.1 with absolutely no problems.
[Fire Original Android Development] GhostRider86:
NONE
[Fire Original Android Development] fapste:
How do i check if the device has any hardware issue or displat replaced with some aftermarket display?
[Fire Original Android Development] whodat711:
found a error ........ i setup a pattern unlock pin and i selected the next level up from the smallest one... then i encrypted tablet and it only displayed the smallest unlock pattern, so i was locked out.. fair warning .. had to volume down+power on and factory wipe and restart ... at least CM stayed.
[Fire Original Android Development] dberend:
Why would someone bother buying a replacement screen? I just looked on eBay $46.95 with shipping. Even in bulk there's not enough profit there.
[Fire Original Android Development] DB126:
Interesting edge case. Two improbable user actions (expanding pattern grid and encrypting device) combined. Not saying you did anything wrong but suspect the problem lies with core CM 12.1 vs the adaptation for this device. Don't look for a fix anytime soon.
[Fire Original Android Development] fapste:
It matters in third world countries because a $50 device in US costs like $150 here. That's why concerns like after market display and repaired device queries rise up. That's why I would like to know how can I check if the display or any other part of the tablet was replaced or is it exactly as the AMAZON shipped it to its original owner.
[Fire Original Android Development] DB126:
Understand the global economics. If there is coin to be made someone will figure out how to do it. That said, validating hardware integrity is your responsibility. If there are subtle holograms or other clues to identify authentic components they have not been identified in this forum (yet).
[Fire Original Android Development] GreatEmerald:
I just installed this on a new Ford device (via Flashfire, 5.1.2). It works pretty well overall, but there are two issues that I noticed: 1) The animations seem really sluggish (the menu open animation is like 3 FPS), and 2) the icons in the menu all look rather low-quality. I tried changing the DPI but it doesn't seem to make much of a difference.

Is it just me? And are the same issues present in the nexus ROM?
[Fire Original Android Development] GhostRider86:
1) not present on my side, sounds strange

2) known issue.

Ask for nexus rom? Just give it a try on your own?
[Fire Original Android Development] GreatEmerald:
About the animation issue, [MENTION=5678269]trulyparis[/MENTION] suggested trying to change animation speed in the dev options, but that doesn't change anything.

Also, to clarify, the sluggish animation is actually only in the launcher, when opening and closing the app list (six dot button). It basically only shows three frames: the initial frame with the button just pressed, a frame with a white oval (during the transition) and the app list opened (almost the final frame of the animation). All other animations in the system and nice and snappy.

If it may give any clues, I installed gapps micro and chose the Google Now launcher, and I haven't logged into any Google account. That's literally all I have done so far.

I'm not entirely certain what would the suggested way to try it be. Flashfire is no longer there after flashing CM. If I want to try, should I reset the firmware back to FireOS 5.1.2, or just install Flashfire into CM?
[Fire Original Android Development] el_charlie:
Your probably using Google Now launcher and it sucks. Yes, the animations are slow and the icons look huge and low quality. Keep Trebuchet or use Nova launcher.

To flash another ROM, enable root access in developer options and install FlashFire.

Cheers!

Edit: you'll need to reboot the tablet after enabling root access in developer options.
[Fire Original Android Development] GhostRider86:
You are not using the stock CM launcher, you are using Google Now launcher, which use different symbol size and the animation is slow. So just stay with Trebuchet...
[Fire Original Android Development] Bioschnitzel:
my fire 7 loose the wlan-signal when its go to sleep.

Is this a problem with this rom or a general Fire 7 problem?
[Fire Original Android Development] GhostRider86:
Look in extended wlan settings for stay awake. Turn to always on.
[Fire Original Android Development] Bioschnitzel:
Default-Setting in Android is always "stay awake".

When i wake up the tablet, i can see its reconnecting with my wlan. The wlan-symbol is empty and after 2-3 seconds it shows connection.
[Fire Original Android Development] nirogu325:
It doesn't matter if you keep on the "Keep WiFi on during sleep", tablet tends to shut off network activities after a certain idle time. Surely it's a kernel feature and there's nothing to do there since there's no source hence no kernel development here to change that behavior (let's not even talk about the locked bootloader).
[Fire Original Android Development] GreatEmerald:
Ah, thanks, that indeed solves it! Initially I thought it made no difference which launcher I used, but it turns out that I also need to reboot after switching them for the changes to take effect. Yes, Trebuchet is fast and looks much better.
[Fire Original Android Development] DB126:
Nova is also a clean (AOSP like) efficient launch with additional customization options if desired. That said, Trebuchet is a fine choice if it meets your needs.
[Fire Original Android Development] ante123:
Hi everyone. I just flashed this rom after using the LP Fire Nexus ROM just to try it out. Everytime I open the kindle from sleep a dialog box that says "Unfortunately the process com.android.phone has stopped"

Is there any way to stop this dialog from popping up every 2 seconds?
[Fire Original Android Development] DB126:
Sounds like you may not have wiped the system and data (aka user apps) partitions prior to flashing CM 12.1. See OP for flashing guidance.
[Fire Original Android Development] ante123:
Fixed my problem. Went in recovery and just did a factory reset. Now CM11 is working flawlessly. Now just have to download all my apps again! :p
[Fire Original Android Development] DB126:
Yup - performing a factory reset from stock recovery is akin to wiping the data (user apps) partition. It does NOT wipe the system partition; keep that in mind if CM 12.1 gets flaky down the road.
[Fire Original Android Development] fredm77:
Solved
[Fire Original Android Development] freaky2xd:
which gapps zip should I use????
[Fire Original Android Development] Bioschnitzel:
I flashed pico, works perfect.
[Fire Original Android Development] Doggy77:
Use http://opengapps.org/ with "ARM" "Android 5.1" and "Pico" or "Nano". Bigger packs don't fit into the rom. All the missing Apps (GMail, G+,...) can be downloaded on Playstore.

Greets,

Doggy77
[Fire Original Android Development] DB126:
Excellent guidance. Also note differences between Pico and Nano; the latter includes a couple components that can not be obtained from the Play Store and thus is my preferred base on most devices.
[Fire Original Android Development] xenokc:
Any chance of a LineageOS port, which has replaced CM?
[Fire Original Android Development] ggow:
In short, yes, soon
[Fire Original Android Development] fredm77:
Thank you. I use it on my Honor 5x and will be happy to get it on Fire.

Envoyé de mon KIW-L21 en utilisant Tapatalk
[Fire Original Android Development] fuzzynco:
fireOS 5.1.2 -> CM12.1 root?

Does CM12.1 have root buikt in or do I need to install SuperSU?

thanks
[Fire Original Android Development] ipdev:
CM has built in root. You can install SuperSU if you want to. (I prefer SuperSU so that is what I use.)
[Fire Original Android Development] DB126:
If you opt for the default Superuser/Privacy manager it must be enabled under developer options as root is disabled by default.
[Fire Original Android Development] fuzzynco:
[Resolved]

Thanks
[Fire Original Android Development] akz1x1:
Hello, I'm new to Amazon Fire community.

Just flashed the rom and it works awesomely :)

Just a small request, Is there any chances for adding Kcal color tuning support to the kernel.?

(I don't know whether is it possible for mtk cpus, Still it's a small req.)

It'd make our dull looking display great.

Thanks
[Fire Original Android Development] GhostRider86:
Kernel is stock amazon kernel and is locked, no chance
[Fire Original Android Development] dctan:
Issue encounters

Brought this tablet during Christmas sale, after flashing to CM 12.1 and used for a while I got the following issues:

1. When I charge the tablet @ off mode, the tablet will go into cyanogen os, is this a norm? I have no issue of other phones I own, they will on when charging and will not go straight to OS…..

2. Have anyone install xposed framework/installer? After installation is not working, the flashfire itself also not working too. I have to uninstall the xposed in order to have flashfire work again.

3. I would like to buy chromecast 2 to mirror to my led tv, Is this compatible to this tablet (CM12.1)? Beside chromecast any other compatible device used for mirroring with led tv.

Anyone encounter above issues, please advice…..
[Fire Original Android Development] DB126:
#1 - Kernel issue; device behaves the same with all ROMs

#2 - Xposed Framework works fine for me; verify you have correct build (zip)

#3 - Chromecast mirroring does not work reliably; search thread for details
[Fire Original Android Development] akz1x1:
Do you know any alternatives that can do the same?(just missing the saturation and contrast adjustment)

Just wanted to calibrate the display a bit.

It'd be perfect after that.
[Fire Original Android Development] yomiguy:
Excuse me, which is the correct build of Xposed for this Rom?

I'm going to flash CM and I would like to use xposed with it.

Thanks. :good:
[Fire Original Android Development] DB126:
Latest SDK22 (Lollipop) build: https://xdaforums.com/showpost.php?p=58828974&postcount=1
[Fire Original Android Development] yomiguy:
Thanks a lot mate!! I'll try then ;)
[Fire Original Android Development] DB126:
Please don't cross post - answered in CM 12.1 thread: https://xdaforums.com/amazon-fire/orig-development/rom-cm-12-1-2015-11-15-t3249416

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

Possible (albeit unlikely) with Xposed modules. Drop green to 95% in CM 12.1 color calibration; fixes the most egregious display issues given budget panel.
[Fire Original Android Development] freaky2xd:
flashing now :)

I had to reorder the tablet because I downgraded from 5.3.2.1 to 5.0.1 :/
[Fire Original Android Development] ggow:
LineageOS??

The reason I have been holding off on the port is that the 12.1 branch of LineageOS to-date has not had much love. So for the moment at least, there is no advantage in moving to this new codebase.

I'll keep an eye on it and if things start to look more promising then I'll let you know.
[Fire Original Android Development] Y314K:
Thanks for all the 7" tablet love. We know even the other Rom flavors depend on your continuing work.

I've been trying to find any version of all the Rom's that I can miracast/screen cast to my FireTV1's on FireOS 5. No matter what settings I try. The tablet never sees the FireTV. I can see my neighbor's TV's but not my FireTV.

Let me know if there is a specific version or way to try it. Or if I can help with testing a solution.

Thanks again.
[Fire Original Android Development] Mr.BungIe:
I don't know about the firetv specifically, but try to download the localcast app off of playstore. It's working for casting to my chromecast, and I believe it sees my firestick as well, but I don't use it in that room.
[Fire Original Android Development] Y314K:
Does it do actual screen casting or just media casting. I need a screen casting option to screen a specific app & sound to the screen. Most apps I found related to Chromecast only sent media links over.
[Fire Original Android Development] Mr.BungIe:
Ah! I believe it's just media. But, checkout out. It's a pretty full featured app.
[Fire Original Android Development] phoenix061987:
hi,

first off thank you so much for all your work!

I have encountered problems when I put in 32 GB & 128 GB microsd cards formatted as exfat and/or fat32. The tablet recognizes them, reads them, all seems fine until it just unmounts randomly them saying card was removed unexpectedly. Any advise?

Cheers
[Fire Original Android Development] kozovod:
The tablet does not start after flashing CM-12.1

Good afternoon.

Help solve the problem.

Amazon tablet "Amazon Fire 7 2015" 5.3.1.0

Installed firmware - [ROM][AOSP] Fire Nexus ROM - LMY49J [24 NOV 2016]

Many times the error "*Launcher3 has stopped*" and "Google" :(

I decided to flash the firmware "cm-12.1-20161122-UNOFFICIAL-ford.zip"

Installed "flashfire-0.53.apk" (I flash this version before of "NEXUS ROM")

I downloaded "cm-12.1-20161122-UNOFFICIAL-ford.zip" and "open_gapps-arm-5.1-pico-20170111.zip"

Run the program "flashfire-0.53"

Chose "WIPE" System data, 3rd party APPS, Dalvik cache and Cache partition are CHECHKED

Chose "Flash ZIP / OTA" from SD card "cm-12.1-20161122-UNOFFICIAL-ford.zip" - WARNING! I NOT CHECKED AUTO MOUNT!!!

Chose "Flash ZIP / OTA" from SD card "open_gapps-arm-5.1-pico-20170111.zip" - WARNING! I NOT CHECKED AUTO MOUNT!!!

Move up "WIPE"

FLASH.

Began installation of firmware.

Running Tablet - the logo "amazon" a very long time. I waited 30 minutes. The tablet does not start.

The tablet can be enters into recovery and bootloader mode.

How do I restore the tablet?

Thank you
[Fire Original Android Development] kyledowling:
Go into bootloader mode then apply update from adb. Go to your computer and do "adb sideload NAMEOFAMAZONZIP.zip"
[Fire Original Android Development] DB126:
Possible hardware problem given similar behavior with different cards and underlying formats.

---------- Post added at 02:07 PM ---------- Previous post was at 02:04 PM ----------

https://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
[Fire Original Android Development] akz1x1:
Is ARISE Sound mod compatible with rom?

Can I flash it using flashfire
[Fire Original Android Development] DB126:
Unlikely anyone can answer this question unless they have prior experience with this package on this device. Check for general compatibility with CM 12.1 before attempting. Be prepared to recover device via stock recovery (FireOS reload) if it fails to boot after flashing ARISE. Taking a backup in FlashFire not a bad idea if you have important personal data.
[Fire Original Android Development] JelloB:
Just an fyi, I also bricked my tablet coming from the Fire Nexus ROM. I couldn't get the device to be recognized by my computer with adb. Since it was only 10 days old I exchanged it and started fresh with CM12.1.

I'm not sure if this was something I did or failed to do but the CM12.1 install failed and bricked my device coming from Nexus using Flashfire.
[Fire Original Android Development] Mr McBoatface:
If you can boot to Amazon recovery it's not a "brick" , adb side loading from recovery isn't hard. If a tablet isn't recognised by a PC while it's in recovery it's most likely a driver issue (it can in rare cases be a hardware or usb cable issue). I found Amazon's official drivers work best , no need to disable driver signature on Windows 10.

As for the failed ROM flash I've had similar experiences but noted it happened directly after freshly installing flash fire and granting it privilege under #SU and then flashing. When I installed flashfire , granted it privilege, rebooted the tablet and then flashed a ROM I never had any problems. I've flashed and reflashed six Amazon fires , mine and family ones, and it's a relatively safe process in some ways better than having to flash a custom recovery. IMHO the dangerous part is the downgrading of stock roms to editions where root has been confirmed.
[Fire Original Android Development] JelloB:
Thank you for the information. I had previously working drivers on my computer but after the flash fail I could not get the computer to recognize my device. I tried several different diver installs to no avail. It's more than likely that somebody else (you for instance) could have rescued my tablet. If I hadn't had the easy exchange option that I did, I might have eventually solved it too.
[Fire Original Android Development] shar88:
I love this rom, and for the value, this tablet.

One question, I got the brightness level down as low as it can go, and the built in android 'LiveDisplay' as well as twilight to dim the backlight at night, but even with all three of these this tablet is still like a search light (lighthouse) at night. I assume this is just because of cheap hardware/light bleed but is there any way to dim the light even more?