yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] vassy.uk:
Hi. Thanks for this rom and support. I downgraded my fire 7 from 5.3.2.0 to 5.3.1.0 and rooted it.
[Fire Original Android Development] Mae7:
Here's my all in one guide for rooting and flashing from 5.3.1.0. to CM 12.1

My tablet was connected to Wifi but I never updated to the latest (5.3.2.0) so this guide is just for people on 5.3.1.0. Have wifi connected as from what I read Kingroot uses the internet?

Go to developer options and enable adb debugging mode (developer mode can be accessed by tapping 5 times on the version number).

Step 1:

Download the Rootjunky SuperTool from HERE

2. Extract the zip to your desktop. Go to the usb_driver folder and install the KindleDrivers and UniversalAdbDriverSetup.

3. Connect your tablet to your PC and run 1-Amazon-Fire-5th-gen.bat

4. Choose option 6 (Root your Amazon Fire 5th Gen)

5. Then option 3 (RootFire OS 5.1.2 or 5.3.1)

From here it will install Kingroot onto your tablet, where you will open the app root your phone with the app (wait a bit). After that the tool should detect the root and remove Kingroot and replace it with SuperSU. If it doesn't continue with the steps after Kingroot has been installed the power off and back on your device and it should pick up from there now using SuperSU. Update the Binary when prompted using the normal option.

Now it's Rooted, and it's time to get Flashfire installed to flash your CM 12.1 ROM.

6. Back at the start of the tool I chose option 3 to block OTA Updates.

7. Now, select option 5 (Install FlashFire App or Xposed Framework)

8. Then select option 1 (Install Flashfire App to flash files and roms), hit enter.

9. Now that it has installed the FlashFire app onto your phone, download CM 12.1 from HERE

10. And then download google apps from HERE and select ARM, 5.1 and Nano (don't select stock as your tablet doesn't have enough room)

11. Place the CM12.1 .zip and the gapps .zipp onto your phones root directory.

It's time to flash CM 12.1 (you can have the usb cable disconnected now if you want and always make sure you have over 80% battery before flashing).

12. Open the FlashFire (0.53) app

13.

- Click the Red + and choose 'Wipe'

- Ensure System data, 3rd party apps and Dalvik cache are CHECKED

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

- Navigate to and choose the latest Cyanogenmod Zip

- Accept defaults

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

- Navigate to and choose the latest Open Gapps Zip.

- Accept defaults

- Move "Wipe" to the Top of the order

- Press the big FLASH button.

(ignore the root option the app gives, CM includes root access in it's developer options)

For this part credits to ggow

14. Your phone will now reboot and start the flashing process, it may hang on the gapps installation but just wait for it.

Now once the flashing has finished you should boot into CynogenMod :)

Hope this guide helps someone as I couldn't find one that had all the steps it one place.
[Fire Original Android Development] Soulreaver1993:
I install Cm 12.1 without any issues, thanks. But how can I activate root now? (root in dev settings dont work)

EDIT: Root works after restart, sorry.
[Fire Original Android Development] Mae7:
just above the debugging list (nine options down from the top) it should say "Root Access"
[Fire Original Android Development] nickoh_lvp:
Has anyone found a workaround for the brightness bug? Im tired of restarting the device, the app brightness control doesn't work for me. Anyway, all the other features work excellent
[Fire Original Android Development] Mae7:
Not sure if it's this ROM but does anyone else have jagged edges on some icons and animations? Its like its not getting rendered to look like vector.
[Fire Original Android Development] DB126:
Nope - other than reducing memory pressure which is also a PiTA. Interesting observation: doesn't seem to happen on devices with 5.0.x bootloader/kernel. Unfortunately, no downgrade path (Instant brick).

---------- Post added at 03:21 PM ---------- Previous post was at 03:16 PM ----------

Hardware related. Aside from low-res panel pixels are asymmetrical (look at a circular image) yielding rendering anomalies. FireOS seems to deal with it better than custom roms. Twiddling DPI is not a solution but may make it less obvious.
[Fire Original Android Development] Munns86:
Agreed. Changing the DPI makes a big difference but it does come with other issues. The lock screen won't rotate to landscape and the nav bar will no longer be transparent in landscape if you go to a higher DPI. If just the nav bar could be fixed I would be very happy.
[Fire Original Android Development] Mae7:
Yeah loading the youtube app when met with the splash screen, the logo looks ugly as.
[Fire Original Android Development] Munns86:
The non-transparent nav bar was just too much for me to handle so I pretty much instantly changed it back to default so I didn't get a chance to test out any apps.
[Fire Original Android Development] Mae7:
You went back to FireOS? I think I would rather have the snappiness of CM and have a little bit of jaggedness in the nav bar.

Also I find the stock dpi (160 i think it is) to be the best, as any higher the text on websites started to get blurry.
[Fire Original Android Development] Munns86:
No. I went back to the default 160 DPI. For my use I preferred (mostly little games and media watching) 180.
[Fire Original Android Development] L0stinSp4ce:
Many thanks for this, I must confess I was having difficulty getting beyond KingRoot.

I used your guide to boot my Amazon Fire 7 into CynogenMod.
[Fire Original Android Development] sk4doosh:
I've also experienced this same issue, I've loaded what I need from apkmirrors and the Play Store still thinks they need updating and then generates the same 505 error. Is there going to be a permanent fix for this in the future ?
[Fire Original Android Development] DB126:
Root cause is Google's unwillingness to accommodate 'non-standard' devices. Play Store compatibility issues have plagued various Amazon tablets running custom ROMs for years and will likely continue into the foreseeable future. Problems may subside with the next Google Play Services (GAaps) update only to reemerge on subsequent releases. Amazon devices and associated custom ROMs are not only one's impacted by recent Google updates as evidenced by a simple web search.
[Fire Original Android Development] arcticathlon:
So i have 2 Fire tablets and both failed the actual FlashFire 0.53 update to CM12.1. I followed the directions and i have the right rom and gapps downloaded. When flashfire attempts to flash both files, it fails on the first CM rom and then only flashes gapps. I forget what the error said, and after that, it rebooted and i had to reroot and reinstall flashfire. this happened on both Tablets, and one was then stuck in bootloop and i reinstalled 5.3.1 and rerooted. not sure if i want to keep doing this, as there must be something i am missing. any thoughts?

i placed the CM12 rom and gapps in the internal storage and not on SD card, does the exact location matter when flashing?
[Fire Original Android Development] nujak:
Just to be sure, you are following the directions from the OP:

- Fresh Installation from FlashFire 0.50

- Click the Red + and choose 'Wipe'

- Ensure System data, 3rd party apps and Dalvik cache are CHECKED

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

- Navigate to and choose the latest Cyanogenmod Zip

- Accept defaults

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

- Navigate to and choose the latest Open Gapps Zip.

- Accept defaults

- Move "Wipe" to the Top of the order

- Press the big FLASH button.

It is important to ensure that you do these steps in the correct order, especially moving the "Wipe" action to the top .
[Fire Original Android Development] Mae7:
have you tried the steps in my post one page back?
[Fire Original Android Development] arcticathlon:
I got it to work . I screwed up the first 2 times . I never moved the wipe to the top . Its working now =)

thanks all
[Fire Original Android Development] NightCrayon:
You will need to manually update any apk 505ing on you using adb.

Find the apks for Google play games and inbox on apk mirror http://www.apkmirror.com/ use the no DPI or 160dpi apks

Once they are downloaded and copied to your adb folder (on your PC) install with this command: "adb install -r file.apk" (replace file.apk with the name of the apk you are reinstalling and do not use quotations with the command)

That should solve your 505 problems. If you aren't sure how to use adb let me know and i can provide a step by step guide.
[Fire Original Android Development] coincoinlapin:
Isn't that à MAJOR bug?? Can you explain exactly what steps you took to rename the sd please? I have the same problem here.
[Fire Original Android Development] NightCrayon:
Make sure you force stop, clear cache and data of any app you are attempting to upgrade, you can do that in settings > apps. Also try wiping data in download manager.

Make sure you upgrade Google play store, Google services and Google framework services before anything else.

Make sure you are upgrading/reinstalling through adb. installing the apk by copying it to your device and running the apk through the default package installer is not recommended and I have not tested it. Its best to use adb to reinstall google apks, I have tested this and know it works 100%.

If you are unsure on how to use adb to reinstall apks let me know and I can write a step by step guide.
[Fire Original Android Development] DB126:
Additional thoughts:

- location of zips (rom+gaaps) does not matter; internal storage will yield faster reads shaving off a few seconds

- that said, I prefer internal storage as it eliminates a potential (albeit unlikely) failure point reading from the SD card

- recommend FlashFire 0.52+ as 0.50 had some issues that were sorted in later releases

- return to FireOS after flash attempt suggest wipe operation was not included or sequenced incorrectly

- if you are confident the install procedure was followed it's possible the CM 12.1 zip is damaged; try downloading it again

- be sure to note all errors during flashing (tip: if possible video record the FlashFire install with your phone)

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

Understand the intent but this is not really necessary unless the internal installer is creating issues which is not the source of "-505" errors. Sideloading from apkmirror or another trusted source should be fine and offers the convenience of clicking the 'download complete' notification to begin installation.

Nothing against installing via adb (used it many times!). Recommend a simple sideload install first and falling back to adb install as needed. Google apps included.

---------- Post added at 08:24 PM ---------- Previous post was at 08:14 PM ----------

Believe you are referencing this item which appears to be a situation unique this the poster. The subject of app migration to secondary storage on Lollipop is not straight forward. Really depends how the app was coded, developer choices and any special provisions included with the ROM to assist with relocation. In absence of some/all of these attributes a tool that utilizes symbolic links will all but guarantee apps can be moved to secondary storage, will run from that location and will not 'vanish' when the device is rebooted. Link2SD is one such tool; there are others which can be found in the play store. Using the native Apps2SD functionality built into CM 12.1 is a crap-shoot at best (blame Google and Lollipop, not CM or the local rom developer/maintainer).
[Fire Original Android Development] ggow:
Before I look at including the December Updates, am I right in saying that Xposed Framework has been updated to work with the November security update that caused issues last month?
[Fire Original Android Development] coincoinlapin:
Thanks for your reply. I adb-shelled into the fire and indeed, in /mnt I had 2 sdcards. I was surprised to read that a simple renaming could do the trick (unfortunately, poster didn't provide the steps: I tried adb root / remounting rw but always got the message that the system was read-only). I resorted to using link2sd in the end, and it works great. Well worth its 2€. Case closed.
[Fire Original Android Development] Mae7:
Is anyone elses IMEI number Unknown after flashing this ROM? Not sure if this device even had one to begin with?
[Fire Original Android Development] Bioschnitzel:
No modem = no imei.
[Fire Original Android Development] DB126:
Yep. No issues with v87 framework.
[Fire Original Android Development] nickoh_lvp:
Sorry I insist on this topic, which is the name of the xposed module you use? Thank you
[Fire Original Android Development] DB126:
I use the screen brightness controls built into GravityBox.
[Fire Original Android Development] Mae7:
Does anyone have trouble connecting to a hotspot? My device just stays connected but has no internet access, and it only connects (no internet) when I add a static IP.
[Fire Original Android Development] Marsu42:
I have the same problem using the asop rom, but I guess I have tried one xposed module too many and even uninstalling them didn't solve the problem anymore. It's my first Android device, so I can only second to the best practice to do regular backups in case you screw something up with root access.
[Fire Original Android Development] DB126:
Had another Amazon device (different model/gen) that behaved like this on occasion. A full power down + restart fixed it including a 5-10 sec pause between. Likely won't work with this device but thought I would share the tip.
[Fire Original Android Development] nirogu325:
Yup. https://www.xda-developers.com/xda-...issues-with-googles-november-security-update/
[Fire Original Android Development] KLit75:
This is a first for me. It just lost the ability to stream videos. Youtube kept giving the"tap to retry" message. So I went through basic troubleshooting (restart, clear cache, uninstall, update etc) but nothing. THEN I tried playing netflix and it gives the unable to contact server message.

Initially I thought it was my network but then I switched both my phone and computer from 5 to 2.4 ghz and they play video fine. Any ideas?
[Fire Original Android Development] yochananmarqos:
Not sure what your computer & phone have to do with anything, but this tablet does not support 5 GHz.
[Fire Original Android Development] KLit75:
I know. I switched them to 2.4 to see if there was a problem streaming from the 2.4 ghz band. There is not a problem streaming from 2.4 ghz so it rules out network error.
[Fire Original Android Development] DB126:
Silly question that must be asked: no joy after rebooting device (including restart after full power off)?
[Fire Original Android Development] Marsu42:
Sorry to have to ask a "use the search" question, but 300+ pages of posts is too much to read through: Is there some comprehensive list of changes of cm vs. stock asop on the Fire 7"?

I'm running asop right now and would like to have cm's theming, but it would be nice to know what I'll get myself into. As both seem to be the most popular custom roms on this device, there's bound to be a post about the difference somewhere :-o ?
[Fire Original Android Development] KLit75:
Not so silly. Simplest thing first, but yes I tried both.

I'm thinking Ill just reflash the rom. I only use this tablet once in awhile and now I'm certain I messed a few things up when I tried to get Viper4android working a little while back.

The device is no longer rooted. That shouldn't effect streaming but Im pretty sure its somehow connected to my problems.

***That being said, if anyone here got viper working and remembers the details, Id appreciate it if you share. Thanks
[Fire Original Android Development] DB126:
Probably exists somewhere; Google is your friend. Short of searching 300+ billion pages might pay a visit to the CyanogenMod home page to see what they have to say.

---------- Post added at 12:45 PM ---------- Previous post was at 12:23 PM ----------

If you lost root on CM 12.1 with SuperSU 2.78 the latter may be a contributor. I spontaneously lost root 3 times with that combination; rolled back to SuperSU 2.76 (terminal build by ChainFire) and haven't had a problem since. Obviously just a single data point - YMMV.
[Fire Original Android Development] Marsu42:
Well, in case anyone wonders and happens to read this post of the gazillion of pages: I just tried cm vs asop on the Fire 7 and my verdict is ...

... the upside: cm has theming, which is nice, though a bit laggy. Plus only the most popular apps and settings are themed, most other apps seem to have custom lite/dark themes built-in which look like stock lp. Many themes seem to have moved to cm13+ by now btw. So with the (most recommended) themes I've tried, it looks a bit customized, but a bit messy, too.

... the downside: cm lacks support for the popular customization options available on xda and the like (for example GravityBox) since cm already has some of their options integrated. Thus cm is nice if you have little time and want a ready-made system - but the 3rd apps I tried with asop mostly have more options and often are still in active development.

Once I manage to screw up my system again by using too many xposed modules, I'm likely to go back to the snappier asop rom version.

Edit: I'm sure cm has other lovely features like multiuser support, but the above is my simple "I just want to have customization and run generic android apps without complications" perspective.
[Fire Original Android Development] DB126:
- GravityBox runs fine on CM 12.1 with exception to areas of functional overlap where CM takes precedence...as it should

- CM 12.1 theming support is marginal and imposes a significant performance penalty on this device (as you observed)

- Those seeking a highly customized/personalised Android experience should clearly opt for an AOSP rom like Nexus

- CM remains an excellent choice for those seeking a ready made productivity environment while exposing a few knobs & dials for those seeking something more than bare bones AOSP

Nice to have choices! Be sure to thank (via XDA) the developers/maintainers for their selfless efforts even if you opt for a different rom.
[Fire Original Android Development] ms372591:
I have tried to load the 11/22 as an update and as a fresh install and I can't get past the Amazon screen. My only option at that point is to ADB back to the Fire OS, root and load the 11/21 update with Flashfire. The 11/21 update runs fine any idea what I could be doing wrong or has anyone else had this issue with the 11/22 update. I guess I could wait for the December Security updates and see what happens.
[Fire Original Android Development] marrco:
i just run into a very similar issue running nov.21 version.

Changed to "charging only" and the bar that appears when sliding from the top [Connected as a media device] simply had disappeared, so i could no longer change it back. I tried to restart my Fire, but no luck. Going to settings/storage, triple dot in corner and selecting 'usb computer connection' fixed the issue for me.
[Fire Original Android Development] stonedpsycho:
Just want to say a massive thank you to [MENTION=5749760]ggow[/MENTION] and anyone else who has helped for this awesome rom! Its now my tablet and not Amazon's!
[Fire Original Android Development] DB126:
I experienced the same thing by simply flashing the update using FlashFire 0.53 with no wipes. This is not SOP (at least for me) but wanted to try a common update scenario. I was able to quickly recovery by booting into TWRP (device w/older bootloader), wiping system/dalvik/cache and then flashing CM+SuperSU+GAaps(nano)+Xposed. After a 5 min delay rebuilding caches the device fired right up to CM 12.1 B20161122 with all apps and data intact.

Bottom line: pre-flash wipes improve reliability but add to the complexity/duration of applying routine updates. Given the consequence of a flash failure (typically reloading FireOS for FlashFire users) I would give consideration to including a system wipe with every update. No need clear the data/user partition. Don't forget to move the wipe operation above the flash operation in FF.
[Fire Original Android Development] racketier:
Can anyone speak to how long it typically takes flashfire to install CM 12.1? When flashing I seem to get stuck on a screen with FlashFire at the top, and black screen below. I have two Fire tablets, and experienced the same on both. I finally let one sit all day while at work and CM had installed at some point before I got home.

Which is great! So this evening I tried installing CM 12.1 on the the other tablet and just let it go, but it's been well over an hour and I'm still on the same screen.

Both tablets were 5.1.3.0, rooted using the Supertool, and using the same microsd card with CM 12.1 and OpenApps Nano. and FlashFire .53.
[Fire Original Android Development] platypoid:
It didn't take anywhere near that long when I did mine . Not sure what you have happening there. Did you put the wipe up top in Flashfire like it says in the first post ?
[Fire Original Android Development] racketier:
Yep. Moved wipe to top. I used "default" Flashfire settings for CM and gapps.
[Fire Original Android Development] platypoid:
Did you put the files on the internal drive or have them on the micro SD card ?
[Fire Original Android Development] racketier:
Microsd card. The card is very old (only 1 GB) so I'm wondering if it's being finicky with that...

Going to try internal storage after I flash stock 5.3.1.0
[Fire Original Android Development] platypoid:
Why not just put the files on the internal drive ? That old card might the problem. I had a Raspberry Pi running on an old SD card and it locked up every day. I got a new high quality Samsung sd card for it and it has been running non stop for months since. They do make a difference.
[Fire Original Android Development] racketier:
Yeah, good call. I'll try that. Thanks for the suggestion. :good:
[Fire Original Android Development] DB126:
Although many have success flashing from the SD card my preference leans toward internal storage. Aside from a slight speed advantage (internal storage is 2-3 times faster than the SD card interface [regardless of SD card rating] on this device shaving a few seconds off install times times) it also removes a potential failure point from the equation. Once whatever was being installed up and running the source files can be moved to the SD card for later recovery if needed.

Assume you mean FireOS 5.3.1 not 5.1.3.0 as the latter is not rootable unless first downloaded to 5.1.2 or updated to 5.3.1. If you downgraded/upgraded there is no need to reference the original version of FireOS on the device.
[Fire Original Android Development] leotakacs:
Is there a Nougat or Marshmallow ROM available for the Amazon Fire 7" 2015 (5th Generation)?
[Fire Original Android Development] racketier:
''

Yes, sorry, 5.3.1. Good catch!
[Fire Original Android Development] GhostRider86:
Sadly no, kernel is build in device no chance with any rom on this device
[Fire Original Android Development] geozakelle:
Stuck on Splashscreen

Help please,

Please be patient, I'm new to all this........

I have rooted and flashed my fire using the flashfire app. Up to that point everything seemed to go smoothly. Now device will not reboot, it's just stuck on the Amazon splashscreen logo and I don't know what to do. Turning on and off only gets to that same point and won't progress. TIA.
[Fire Original Android Development] DB126:
You will need to reload FireOS from the stock recovery menu if that option remains available. See linked thread and video below. If stock recovery is borked (quite possible depending on what errors were made in FlashFire) contact Amazon for return/exchange options.

http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
[Fire Original Android Development] geozakelle:
OK, thanks. Managed to get back to stock. Just need to start over again.

Anyone tell me the recommended version of Open Gapps to use with this ROM?
[Fire Original Android Development] ajislav:
1) read OP

2) if in doubt flash the smallest, i.e. pico