yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DB126:
Given the recent emergence of FireOS 5.3.1.x in the wild need to start including a caution about not attempting a rollback if on that version or higher. No rollback, no root ... sucks.
[Fire Original Android Development] Denverfan9:
Used the flashfire method due to fire os 5.1.2 went to reinstall supersu from app store need to update binary message and supersu app wont update its self...did i loose root? If so what method to reroot? Originally used rootjunky supertool....

Thanks
[Fire Original Android Development] sd_shadow:
root is off by default, if you didn't flash supersu.zip or use Flashfire's root option

you need to enable dev options {settings/about tablet, tap build version ~7 times} and

settings/dev options/ root / apps and usb
[Fire Original Android Development] Denverfan9:
Haha did not know that was a setting though you were screwing with me....thanks bud...do you know if i need to reinstall xposed framework or just install the installer
[Fire Original Android Development] sd_shadow:
need to reinstall xposed framwork
[Fire Original Android Development] monster1612:
Thanks for this stable ROM! I flashed this onto my sister's fire that she got from Amazon for the Prime Day promo, and she's loving every bit of it! :D
[Fire Original Android Development] DevilsClaw1991:
When I first used the super tool I had 5.1.1. installed. I disabled the automtic updates so is it safe to restore to 5.1.1. or should I restore it to 5.1.4?
[Fire Original Android Development] GhostRider86:
You are lucky, restore to 5.1.1 and enjoy
[Fire Original Android Development] DevilsClaw1991:
Weeelll. I restored it to 5.1.4 by accident :( Is there a way to easily downgrade it?
[Fire Original Android Development] GhostRider86:
Dam, as far as I know there is no way...
[Fire Original Android Development] DB126:
You can rollback to 5.1.2 (rootable) but not 5.1.1 (guaranteed brick)
[Fire Original Android Development] DevilsClaw1991:
Thanks. I actually found a guide to roll it back to 5.1.2. I'm doing it right now. How do I get root access after that with the 5.1.2?
[Fire Original Android Development] DB126:
Please don't litter the forums with cross posts. Follow the guides in the index thread located in the General section.

http://xdaforums.com/amazon-fire/de...-5th-gen-supertool-root-t3272695/post67829974

http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485
[Fire Original Android Development] DevilsClaw1991:
Sorry and thanks.

Edit: I now finally have installed CM12.1. Everything works fine but when I move apps to the SD Card they are completely deleted from the device/SD card. I did start the apps after moving them so I have no idea why it deletes them after restarting. Does anyone know why?

Furthermore I'm looking for the amazon video app in the play store but can't find it. Where is it?
[Fire Original Android Development] tstack77:
I just ordered one of these little guys last night (delivered today) and was happy to see that they are still shipping 5.1.3. I made sure to pick black since that color is the only one still "In Stock". No idea what the shipped rom will be with the new inventory that comes in on the 30th, so it might be a good time to buy more now if you're considering.
[Fire Original Android Development] 4t701:
FWIW, I bought one of the refurb units listed in "good condition" for less than $30. Thing is literally brand new, seriously. It arrived with OS 5.1.1. ?
[Fire Original Android Development] ghost13:
Rom works great! 1 small issue for me. can't unmount my 32gb sandisk microsd card... any ideas?
[Fire Original Android Development] DB126:
Unmount is not supported by this rom (generic CM 12.1 issue). In most cases an unceremonious hot eject will not result in card/file corruption. If concerned power down device before popping card.
[Fire Original Android Development] GhostRider86:
It's a feature.shutdown or just remove cause no direct write
[Fire Original Android Development] ghost13:
thanks guys!
[Fire Original Android Development] Ollaz:
I seem to have issues rooting my device in order to install CM. The supertool hangs at injecting files (sometimes no files, sometimes 2-3 get passed to the device; tried from root of C:, as admin, not as admin etc.) and Kingsroot tinkers a while and then says it's unable to root my device. Any ideas? Running 5.1.2.
[Fire Original Android Development] Doggy77:
Supertool installs "Kingroot". Use this to gain root. After root is achieved the supertool tries to replace kingroot with supersu. This will only work if root achieved. This may be the explanation why "injection" does not work.

I also had some problems with kingroot. What I found out working for myself: after installation it needs WiFi connection working, so connect the fire to WiFi. Try rooting using kingroot several times. first time I try it with fire still attached via USB. After reboot (mostly at 18%) I start kingroot again it continues and sometimes it fails in the rooting process. If so, I unplugged it from the computer and tried again one or two times. One tablet came with a pre configured fire account and was not able to be rooted, neither with USB attached nor without USB cable. I wiped it using "reset to factory" in settings and began a new round of rooting which was finally successful. Not sure if the amazon account was the cause or any other data on the device.

I already rooted/flashed a total of 8 tablets and the rooting process was always the "tricky" one. Keep on trying.

Greets,

Doggy77
[Fire Original Android Development] jratt:
I believe you will have to use FlashFire and supersu if running 5.1.2 here is basically what I did but with cm

https://youtu.be/NaCBSuUuhRE

Also before I flashed I installed play services first through his supertool blocked OTA updates then updated FlashFire and supersu in Google store

Watch this

https://youtu.be/j-glxYTY8O8

This

https://youtu.be/ux-2b3X3BlI

And This

https://youtu.be/NaCBSuUuhRE

I didn't have to mess with drivers on my win 10 computer
[Fire Original Android Development] Doggy77:
Please correct me if I am wrong: installing SuperSu from Playstore does not root your device. SuperSu is just a management tool to manage the apps that want to get "root-access". In order to do this, you first have to root your device, this is what was asked and what is done with "kingroot".

For an app that wants to get root access on a device, it tries to open a command named "su". In all "stock roms" this file is not present, therefore the app can not get the root rights.

Every rooting process (kingroot, CWM/TWRP recovery, any other process) try to use any ways (e.g. security flaws, flash from custom recovery,...) to put this "su" file into the system-partition. THIS is the rooting process.

SuperSu or the built in CM-SU are just there to enable you *denying* apps from getting "su" (root access). Without these "management tools" every app could call "su" and perform administrative tasks on the device. This would be potentially dangerous, because also malware could gain this root access without you knowing it. Therefore it does not make sense to install SuperSU from Playstore an an unrooted device. Because it just *manages* the root access.

Again: please correct me if I am wrong, but this is what I understood from working with several devices (amazon and lot of other brands).

Best regards,

Doggy77
[Fire Original Android Development] jratt:
Yes I installed play store through his supertool, then I rooted and installed supersu + FlashFire, then blocked ota updates then updated supersu + FlashFire from play store then followed the instructions at the top of this thread on how to flash with FlashFire, also I believe you will need Gapps micro or smaller to flash this "if you want cm with play store". I am kind of new but it was pretty easy.
[Fire Original Android Development] DB126:
Well said; absolutely correct.
[Fire Original Android Development] mkhcb:
My device came with FireOS 5.1.1.

I was sure not to update the device and I have since rooted the device, installed the play store, and installed flashfire from the play store. I then attempted to flash CM 12.1, pico-open-gapps and xposed all in one go. It appears that gApps and xposed was installed but not CM 12.

Anyone has any suggestions on how to install CM 12? Non-play versions of Flashfire keeps crashing unless I used v 0.25. Yet, this version does not flash CM 12.1.
[Fire Original Android Development] ldeveraux:
if you're sure you followed every step for a fresh flashfire install, try the twrp install.
[Fire Original Android Development] mkhcb:
I can't use TWRP because I am on 5.1.1.... or can I?
[Fire Original Android Development] ldeveraux:
I suppose not. Are you sure to add the initial "wipe" step?
[Fire Original Android Development] mkhcb:
Yep.... and then I selected flash... it stays on FireOS 5.1.1 :(
[Fire Original Android Development] ldeveraux:
Dunno, hopefully ggow or someone more knowledgeable can chime in.
[Fire Original Android Development] mkhcb:
This trick, from a youtube comment, seems to have done it :)

---------- Post added at 10:56 PM ---------- Previous post was at 10:53 PM ----------

My biggest concern is having my device crash and having to redo everything all over again, after I restore back to default firmware.

Now that I am on CM... is there a way to get CM recovery on this thing? Is there any way to get something functional? Flashfire is amazing, assuming you can boot into your device.
[Fire Original Android Development] ldeveraux:
glad it works, I thought there was something fishy going on. No permanent recovery due to bootloader restrictions. Either use Flashfire (yes) or fastboot TWRP each time (you can't).
[Fire Original Android Development] mkhcb:
Someone needs to crack this bootloader lol.
[Fire Original Android Development] GhostRider86:
Thats why it is stated out in OP. Move wipe to top.
[Fire Original Android Development] Ollaz:
I'm trying all kinds of things (with or without the USB, on the PC app etc.) and my device does not even reboot when trying the root process. Something changed, however, because now the PC says the device is not recognized - doing a wipe right now to see what happens.

Earlier the supertool was not able to install Kingroot on the device (just hanged), but this time it actually pushed and installed the app. So I'm a step closer, I guess.
[Fire Original Android Development] jratt:
Did you enable aba on your tablet and also make sure aba drivers where installed on your computer?
[Fire Original Android Development] Ollaz:
Not sure what "aba" is but I guess you mean ADB. Of course ADB worked - otherwise the Supertool doesn't work at all. Also, the Supertool wouldnt've been able to push stuff to the tablet. Please read next time.

Anyway, I solved the issue. I reset from a factory image (5.1.2 bin, via adb sideload), then let Supertool install Kingroot. Kingroot rebooted halfway and then finished with saying that it failed. So I rebooted the tablet after the failure message and once it booted, ran Kingroot again - only this time it succeeded. And then Supertool installed superSU and Play Store, which got me FlashFire and then did as instructed. The FlashFire in the Supertool did not work for some reason, I guess it needed an update.
[Fire Original Android Development] GhostRider86:
You mean Adb ?
[Fire Original Android Development] DB126:
Well done. Update FF to v0.52 from Play Store or apkmirror; all good then.
[Fire Original Android Development] Dunard:
There is something wrong with the app video playing part. All black. Is there anyway to fix this? KINGDOM HEARTS Unchained χ and a few others that I have. The game part is fine.

Edit: I fix the video playing part on the games. To fix the broken video playing issue. Turn this on from the Developer options "Force GPU rendering: Force to use of GPU for 2d drawing." Look for the Hardware accelerated rendering. If you having a hard time finding this. I don't know if the person who made this ROM is aware of this bug or not.
[Fire Original Android Development] Dunard:
Well it look like the The Bard's Tale video is unstable. Freezes up. Maybe Amazon game app doesn't run well on a non Amazon ROM.
[Fire Original Android Development] ipdev:
http://www.amazon.com/gp/feature.html?ie=UTF8&docId=1000625601

Install Underground and log in.
[Fire Original Android Development] Weird0ne:
I can't get Google Play installed.

I tried wiping, reflash cm12.1, reflash Open GApps, but it tells me this version is in compatible because another version is already installed.
[Fire Original Android Development] GhostRider86:
Do you changed the order in FlashFire? Wipe should be the first
[Fire Original Android Development] DB126:
- CM xx.x core is a collective effort; no one person made it

- the OP applied only the mods need to support installation on this device (hardware platform)

- the situation you describe is not a 'bug"; that's why controls are provided as different apps/games/whatever need different settings on different hardware
[Fire Original Android Development] Dunard:
Bah that a bummer.

Seem to be working fine on the Resurrection Remix LP. Down to SOULCALIBUR that have a black screen completely. I had to use my Amazon FireOS 5.3.1 ROM. No problem running SOULCALIBUR on the Amazon FireOS ROM.

Like you said. Each ROM have their own settings. It a shame not all 5.1.1 and higher have the same settings or so.
[Fire Original Android Development] DB126:
For awareness. Unlikely this development will immediately (ever) affect cm 12.1 for this device but may slow/halt future builds aligned with Android 7 (Nougat) along with ongoing development/support for more obscure devices.

http://www.androidpolice.com/2016/0...s-undergoing-major-layoffs-may-pivot-to-apps/
[Fire Original Android Development] Dunard:
Oh snap. http://www.cyanogenmod.org/blog/cyanogen-inc-and-cyanogenmod
[Fire Original Android Development] BRANDENDEUCE:
Go to the kingroot website, download the program and attempt root through the pc. I had to do it this way and it worked out the first time
[Fire Original Android Development] jratt:
KINGDOM HEARTS Unchained χ works fine on mine all I have ever changed on my tablet was LCD density to 200dpi in display & lights.
[Fire Original Android Development] Dunard:
Oh ok
[Fire Original Android Development] stslimited84:
When you say refurbed units, do you mean the ones listed as "used - good" for the condition? I don't see any listed as refurbished.
[Fire Original Android Development] DB126:
Yes - sold by Amazon Warehouse. Others may or may not be 'factory' refurbished and backed by a limited warranty (return privileges).
[Fire Original Android Development] Weird0ne:
Yup did exactly that, not my first time doing a custom wipe/flash so idk why it's not working this time.
[Fire Original Android Development] GhostRider86:
And gapps is correct architecture? Arm, 5.1,nano or pico?
[Fire Original Android Development] Weird0ne:
I was doing pico, gonna try nano this time around.

Still can't get it to work for some reason.
[Fire Original Android Development] facted:
I couldn't root either and then used Amazon Fire Tablet Tool root (#6). Importantly, you must select option #2 as this method works while methods 1 and 3 do not. It doesn't look like KingRoot works anymore for us. I tried the latest mobile version from xda, the windows version, and the version in the Amazon Fire Tablet tool without success (and that's after a reformat). Good luck!
[Fire Original Android Development] stslimited84:
Are you guys using these on a daily basis? Looking to pick up a cheaper tablet for playing games, occasional kindle app reading and maybe streaming here or there. With cm 12.1 will this fit the bill?
[Fire Original Android Development] DB126:
Daily - yes

CM 12.1 - yes

Video - yes

Games - maybe; device lacks a dedicated GPU so nothing too intense.
[Fire Original Android Development] Kildimo89:
Hi

I just received this today and its running 5.1.4

Whats is my first step to getting CM12?

Do I first need to downgrade? WIf so, what version and any guide?
[Fire Original Android Development] jratt:
http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
[Fire Original Android Development] Kildimo89:
Thanks ☺

I am now on 5.1.2

For this version must I use flashfire? Is there a guide from hetre?
[Fire Original Android Development] jratt:
Yes FlashFire and supersu

Don't try to downgrade to 5.1.1 you will brick it

I used http://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695

https://youtu.be/sVv1D_LNLTg

https://youtu.be/NaCBSuUuhRE
[Fire Original Android Development] yochananmarqos:
No issues with Bard's Tale here.
[Fire Original Android Development] GhostRider86:
Which FireOS version are you on? 5.1.4? Then you need to downgrade to 5.1.2 first...
[Fire Original Android Development] facted:
Not sure anymore as I've been on cyanogenmod for a while. But regardless, option #2 did work.
[Fire Original Android Development] frankzero:
if you are on 5.1.3, update to 5.1.4, them downgrade to 5.1.2, now you can root the device
[Fire Original Android Development] DB126:
This makes no sense. Upgrading to 5.1.4 before downgrading to 5.1.2 offers no benefit over directly downgrading to (adb sideloading) 5.1.2.
[Fire Original Android Development] Kildimo89:
SON OF A *****

Went to sleep and it automatically updated itself to 5.3.1.0 ?

Let me guess I can't down grade from this safely?
[Fire Original Android Development] GhostRider86:
It seems he has solved his issue without saying it, see #3160
[Fire Original Android Development] DB126:
Yep - saw that. Was commenting on silliness of upgrading to 5.1.4 prior to downgrading to 5.1.2.
[Fire Original Android Development] jjnagy:
Had same issued one of two things fixed the issue: arm64 vs arm or pico vs micro

First time attempt installed using arm64 5.1 pico instead of the correct arm 5.1 pico version --> no Play Store and lost root

Second attempt install correct arm 5.1 version micro --> got playstore and did not lose root everything working great!

Try installing arm 5.1 micro version worked for me!
[Fire Original Android Development] Weird0ne:
Thanks for that, but I'm still having the issue of Google Play not installing, error 505.
[Fire Original Android Development] jjnagy:
Did you use micro version of gapps? I think thats what got me the playstore.
[Fire Original Android Development] Weird0ne:
I have play store, need Google games to sync my accounts gaming info.
[Fire Original Android Development] :
It looks like I'm not the only one having issues with exFAT format microSD cards but I wanted to add my experiences to the knowledgebase. My tablet can read and write to my 32GB SanDisk but the Documents file selection tool does not see it, meaning that I can't grant apps write access to the SD. Yes, I know about the top right menu. That only makes internal storage appear in the sidebar.
[Fire Original Android Development] jratt:
Google games was the only app that would not download for me so I installed it from apkmiror then updated that through play store
[Fire Original Android Development] jjnagy:
Sorry I thought you were having issues with Play Store. Have you tried getting Google games from apkmirror site? Someone(can't recall where I heard it from) had mentioned they had to get Google games from there and then upgrade from play store.
[Fire Original Android Development] ldeveraux:
You mean the post literally before yours? ;)
[Fire Original Android Development] JPDucks:
Does anyone know how I can re-root this device after upgrading to CM 12.1? I was on Fire 5.1.4, downgraded to 5.1.2, rooted, got Google play working, installed Flash Fire and flashed CM onto the device (working perfectly). I tried reinstalling SuperSu as well as Titanium and was told the device isn't rooted. Also told that by Root Checker.

I even tried using RootJunkie's SuperTool to install KingRoot but that was unable to root the device.
[Fire Original Android Development] jratt:
Go into about tablet tap build number 8 times then go to settings-->developer options then you will see a root access option
[Fire Original Android Development] JPDucks:
You're awesome, I appreciate it, and I hit thanks... My son's tablet is now setup.
[Fire Original Android Development] tintin74:
Hi guys,

I'm running this CM12 version on my Amazon Fire 5th. I'd like to have a confirmation about the chance get back to the original firmware , downgrading it to 5.1.2.

Is it risky? I can get back to the original firmware using adb sideload ?

Thank you

Tintin
[Fire Original Android Development] GhostRider86:
No risk, just adb sideload the firmware you tablet has on delivery
[Fire Original Android Development] DB126:
Generally agreed on reload/sideload risk (minimal albeit not zero) but only downgrade to 5.1.2 unless you are 100% confident your device had a different version of FireOS installed just prior to flashing CM. Attempting to reload a lower version of FireOS will usually result in a brick (there are some exceptions which I won't detail here).

As of this writing FireOS 5.1.2 is a safe bet for all if (and only if) you are currently running a custom rom and wish to return to stock.
[Fire Original Android Development] mainstang:
Does anyone else have a problem with low volume via headphones. It gets even worse if I try to use audio FX. I tried looking for a mixer file that can be edited and that is referenced in some fixes to no avail. Has anybody tried viper mod with this ROM?
[Fire Original Android Development] shiva-afk:
I am using "FolderMount" for things like that. Give it a try -> com.devasque.fmount
[Fire Original Android Development] sd_shadow:
install ES File Explorer>open ES>settings>Directory settings>Download path/backup arrow (on popup)> /storage/sdcard1>OK

when downloading select ES Download manager (you will get a popup)
[Fire Original Android Development] BigMosley:
2 examples why I love XDA, many thanks both of you. ?
[Fire Original Android Development] 4t701:
This looks pretty sweet Am I correct in my understanding that the latest cm 12.1 build can be booted *without* adb/fastboot?
[Fire Original Android Development] ggow:
- Yes it can boot standalone, just remember to flash SuperSU directly after the ROM
[Fire Original Android Development] ggow:
- I have just fixed bluetooth audio

- Bit more testing on my Motorola S10-HD...

- Then I'll do another release.

EDIT: That's enough, seems stable to me
[Fire Original Android Development] ggow:
New Build is Up - Bluetooth Audio Fixed

- Dated 02 Dec 2015

- Change log on Post #2
[Fire Original Android Development] 4t701:
Awesome! Will probably be flashing this shortly. Seems pretty stable [emoji106]

Thanks!
[Fire Original Android Development] Sid-Shrunk:
Hi, first of all thanks for your work. Will try as soon as my fire arrives. Had to return the delivered tablet cause of pixelerrors in the display. :(

So do I realy need to install Supersu? Have installed CM 12.1 on my Nexus 4 with root management via built in CM-Rootmanagement and no need to install supersu.
[Fire Original Android Development] sd_shadow:
yes, it will not even boot without it
[Fire Original Android Development] sam tyler:
Will try this version tomorrow thanks.
[Fire Original Android Development] ggow:
- Let me know if it works ok for you.
[Fire Original Android Development] ggow:
- Added note in the OP to place more emphasis on the importance of flashing SuperSU.
[Fire Original Android Development] sandman512:
Sd, to install the latest build do I still have to get the device into recovery via my pc and then flash? Thanks!
[Fire Original Android Development] sd_shadow:
Yes, you need to boot twrp with pc, then install update
[Fire Original Android Development] k4y0z:
So my kexec module seems to be partially working.

I can load a kernel into memory with kexec-tools.

When I try to boot into the new kernel with "kexec -e" I get a black screen.

After nothing appears to happen for a while the Fire reboots normally (I presume it's the watchdog kicking in).

So something is not quite right yet. :confused:

I was however able to successfully build and boot (using fastboot) a kernel form source,

this will hopefully help in debugging the issues with kexec. :)

Find a patch for the kernel-sources attached.