yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] fabu09:
As the image above, have set to apps only and tried to update the binaries on SuperSU but end up with this every single time
[Fire Original Android Development] zeusminos:
[MENTION=4432577]fabu09[/MENTION] how did you flash the CM image/google apps? Which fire version was installed on your tablet before being replaced by CM?
[Fire Original Android Development] fabu09:
The fire device came on Fire OS 5.1.3 and i followed instructions from:

http://www.overclockers.com/forums/...od-12-1-Android-5-1-1-on-Amazon-Fire-7-Tablet

to downgrade to 5.1.2. As per the instructions I followed and installed CM 12.1 from here the first page and gapps [ARM - 5.1 - micro]

I used the supertool from rootjunky to install flashfire once rooted on FireOS 5.1.2 and than followed the instructions for flash fire to flash the rom
[Fire Original Android Development] zeusminos:
I am using the gapps arm 5.1 pico. Did you use the supertool to take care of the rooting and install flashfire (used to flash cm and gapps)
[Fire Original Android Development] fabu09:
I used micro instead of pico, could that be the issue? (The link i followed instructed to use micro) And yea, i used the supertool for rooting and installing flash fire when i was on FireOS 5.1.2, I did think of trying to use the Supertool to root on CM12.1 but the options to root was for fireOS 5.1.2 etc. which i'm not on anymore so I didnt go forth with that.
[Fire Original Android Development] zeusminos:
I do not know the difference between the instructions that you used and the ones that are described at the top of this thread. I will recomend to compare both and you my find the difference.

Regarding the gapp version. I am not sure about the difference between the 2. I am guessing that the pico has less apps on it, but other than that I do not know
[Fire Original Android Development] GhostRider86:
Go back to start and give it another try. Sideload previous installed FireOS version, re-root with supertool, replace kingroot with SuperSU, install play store, install FlashFire from play store, install CM12.1 and OpenGapps as described in OP (attention to wipe order), go into developer options, enable root, reboot, install SuperSU from PlayStore, enjoy
[Fire Original Android Development] fabu09:
I did give both a read and compared, don't seem to have any difference from what i can see besides the OP here using flash fire from FireOS 5.1.1 and the instructions i followed used 5.1.2

I don't quite know how to side load the previous OS so i would have to go give that a read but if it's too complicated I might just live with it as i would hate to hard brick the device or something else worse
[Fire Original Android Development] DB126:
Sorry this happened. The integrated CM SU has been likely been damaged or become inaccessible. Unfortunately - in the absence of a robust, stand alone recovery environment (eg: TWRP) the only reliable option is to reload FireOS from Amazon's limited recovery environment and start over; it is the only way overwrite/refresh the system partition on an locked/unrooted device.

Keys to success when ready to reflash CM 12.1:

- use the latest version of FlashFire (currently 0.53)

- follow instructions in OP exactly; don't twiddle FlashFire options

- only flash CM 12.1 zip + GAaps nano (no SuperSU)

- double check operations sequence before flashing (wipe on top)

- after CM 12.1 initializes enable root in developer options and reboot

The excellent SuperSU root manager can be added later from the Play Store if desired. That said, it is neither necessary nor recommended. An unnecessary complication for most casual users of CM ROMs (12.x and above).
[Fire Original Android Development] fabu09:
Well my intentions to root is just so i can force move apps to SD card, tried link2SD but it requires root for some thus i'm trying to figure out the root. I may restart the process all over like you said but I just want to check 2 things, is it not possible to change amazon's recovery to TWRP or CWM or is that a whole different process? And I have no idea how to go about flashing back FireOS, any guides for that?
[Fire Original Android Development] DB126:
- not possible to boot/install a custom recovery due to locked bootloader (exception for early builds in 5.0.x series; sorry, no rollback option)

- rollback instructions w/accompanying video here

- be sure to sideload the same version of FireOS that was present prior to installing CM 12.1; downgrades are risky and will likely yield a brick
[Fire Original Android Development] fabu09:
Thanks for your help, I really appreciate it! I will give the whole process a try again and just to be sure, the device arrived on FireOS 5.1.3 and I downgraded to 5.1.2 before flashing CM, so I would have to go back to 5.1.2 right to start over right?
[Fire Original Android Development] zeusminos:
If I remembet well suppertool does not support 5.1.3 so you need to downgrade to 5.1.2
[Fire Original Android Development] DB126:
You have a choice - FireOS 5.1.2 or 5.3.1. There is no advantage to staying on 5.1.2 while 5.3.1 brings incremental improvements to the kernel that some say improve device stability. Amazon does not provide detailed change logs so it's hard to know for sure. You could also go with 5.1.3 but there really is no benefit. Be sure to keep WiFi OFF except when rooting to avoid an unwanted OTA update. Skip registering with Amazon after reinstalling FireOS. For whatever reason that seems to interfere with rooting.

That was true for awhile but recent reports indicate 5.1.3 is now vulnerable to KingRoot.
[Fire Original Android Development] fabu09:
Ok I'm getting a little confused, you said earlier that I have to go back to the FireOS I was on before I flashed CM which was 5.1.2. Based on what you just said, seems like I'm better off flashing 5.3.1 so is it safe for me to just flash that instead? Or do I have to flash back to 5.1.2 than upgrade to 5.3.1 instead of just going straight to 5.3.1 FireOS.
[Fire Original Android Development] sd_shadow:
firmware upgrades are always possible though sideload, whether on stock rom or custom, downgrading is limited
[Fire Original Android Development] bemyescape:
Stuck on Amazon loading screen

I recently purchased a Fire with version 5.3.2. After many steps trying to get CM installed, every time I boot I get stuck on the amazon loading screen. I also get an error when trying to sideload both versions 5.3.1 and 5.3.2. Here are the steps I took to get to this point:

Downgrade from 5.3.2 to 5.3.1

Install Supertool

Root with Supertool

Upgrade SuperSU binaries

Install FlashFire with Supertool

Attempt to flash CM12.1

This attempt hung at the screen with Flashfire banner at the top before it ran any code.

To resolve issue, I sideloaded 5.3.1 again and re-performed steps 1-4.

Restarted and ensured SuperSU had granted access to Flashfire

Attempted to flash CM12.1 and stock GAPPS

Phone turned off after CM flash

Reboot took me to CM setup, but WIFI would not connect

GAPPS flash seemed to fail (I noticed now that the stock version was too large and I should have used nano)

Didn't have Play Store

Didn't know how to re-install FlashFire to try Flash process again

Attempted to sideload 5.3.1 stock again (due to lack of WiFi and GAPPS) using the "Apply update from ADB" under Amazon system recovery, but it failed after about 20% with error "* failed to read comment: Invalid argument"

Attempted to sideload 5.3.2 stock using same process and received same error message.

I am still looking to get CM installed and working correctly with WiFi and with the correct GAPPS version, but if I can just get back to stock I will be happy. Can anyone tell me how to accomplish either of these?
[Fire Original Android Development] DB126:
Good question; sorry for the confusion. You can safely sideload FireOS 5.3.1 over your current CM build. My previous guidance (below) was intended to discourage a downgrade (specifically to 5.1.1 or lower) which typically yields bad outcomes. Sometimes people read about all the wonderful advantages of an earlier build and attempt a rollback without first checking if it is safe to do so. In contrast, sideloading a higher version is almost always safe recognizing it's a generally a one way ticket. Once you flash FireOS 5.3.1 there's no going back to an earlier version.

Previous guidance: "be sure to sideload the same version of FireOS that was present prior to installing CM 12.1; downgrades are risky and will likely yield a brick
[Fire Original Android Development] DB126:
- perform a factory reset and clear caches from stock recovery before attempting to sideload 5.3.1

- try a different USB cable (sounds weird; works with surprisingly freq)

- if sideload errors persist contact Amazon for a courtesy exchange
[Fire Original Android Development] fabu09:
Oh i see, I shall go back to FireOS 5.3.1 instead and than try the whole thing again. Thanks so much for your advice!
[Fire Original Android Development] Toshman:
I am unable to install der Google App "Play Games" (required to start a special Game) , other Apps are working. Is this a Issue due to my opengapps or any other suggestions?

*Edit*

I directly installed the .apk file, that worked.
[Fire Original Android Development] Seraph08:
i know i got one of these coming tomorrow.
[Fire Original Android Development] kyledowling:
Does anyone have problems with their SD card? No Xposed, only cm + SuperSU. SD card is formatted as fat32. If I need a log just let me know.
[Fire Original Android Development] gsjkly123:
I flashed with 79% :3
[Fire Original Android Development] hooks024:
Will cyanogen Inc's decision to stop cyanogen mod affect further updates for us or are we good because it's an unofficial build? Anybody know?
[Fire Original Android Development] mattgyver:
Unofficial builds still have to be built off of a base.. any updates done from Jan 1 on would only be minor, unless he changes a lot of cm code, in which case, he really can't call it cm anymore.

Possibility of moving to LineageOS once Cyanogen himself goes forward with that OS?

Sent from my TARDIS
[Fire Original Android Development] fabu09:
So i finally gave it a go, and managed to get 5.3.1.0 running on my device, and i'm currently trying to root it but no matter how many times i'm trying to root it, it simply wont root with kingroot. Could it be possible that 'root' partition for my device is permanently damaged? Sorry if that sounds dumb but i''m not familiar with the whole android thing yet.

Any idea why all my root attempts are failing? i'm using rootjunky's super tool, also should i try to install flash fire first before rooting or does that make no difference?

EDIT: Nevermind, i managed to get it rooted. Read on another thread to factory reset and thats what i did on the recovery menu and still had to try about 2-3 times but finally rooted and succefully run CM12.1 now with updated binaries etc!

Glad i decided to give the whole process a go and now it works perfectly, thanks so much to everyone that helped me out with advice and suggestions!
[Fire Original Android Development] gsjkly123:
How do I put files on root of the kindle?

Do I put the files on the root of the actual kindle or the sd card? (and if on the root of the kindle how do I do that?) :(

---------- Post added at 07:14 AM ---------- Previous post was at 06:48 AM ----------

My GAPPS install failed(bad version) but cm12 worked so how can I get gapps now?
[Fire Original Android Development] steve8x8:
A to first Q: use "adb push file /sdcard/"

Not-so-A to last Q: The OP suggests a way to upgrade an existing install - I would (but never did yet) perform an upgrade (with the same CM version though, and the right gapps) as described in the OP here. If that fails (use flashfire 0.53!) you've got to take the long path, going back to the version of FireOS you had installed before flashing CM, opening WiFi only for KingRoot, etc full circle.
[Fire Original Android Development] DB126:
Sometimes GApps can be successfully added to a GAppsless CM install via a simple FlashFire. More often than not both CM and GAaps need to be flashed together in a single operation following a wipe of the system partition.
[Fire Original Android Development] glockman4519:
Latest build is running great. Just wanted to say thanks again. Awesome job.
[Fire Original Android Development] zeusminos:
I may skip yhis part, but is it possible to get notified if a new build is ready?
[Fire Original Android Development] DB126:
At present XDA forums do not directly support this capability. You can be notified of all new posts to a thread but not specifically new builds.
[Fire Original Android Development] zeusminos:
Can we setup a mailing list for that?
[Fire Original Android Development] DB126:
SOP is to check this thread on occasion for updates. Change log is in the first few posts. New builds incorporating the latest security tweaks come out every month or so.
[Fire Original Android Development] Marsu42:
Fyi: There's no "CM" CyanogenMod" anymore b/c the commercial parent-ish company is gone, everything left switches to the new name "LineageOS" - so someone please rename this thread [ROM][UNOFFICIAL] LOS-12.1 [32 Dec 2016] as we don't want to appear outdated, do we (that means you, Google/Amazon Android update policy)?

http://lineageos.org/Yes-this-is-us/

I dunno if this is really necessary as there's no actual development of the roms going on, only monthly-ish security updates - or is there?

Afaik all will stay just the same at ASOP 5.1 or LOS 12.1 with - and after the recent ASOP trouble I for one am happy not to use the latest build :-p. Please someone unlock the bootloader so we can get Marshmallow or even Nougat, I'd like the Vulkan api and the split screen (and a magnifying glass) :)
[Fire Original Android Development] brickedfire:
Hello!

I have tried to upgrade my FireOS 5.3.1 tablet to cm12.1 using FlashFire.

After the execution of FlashFire, I had a screen with a red bar at the top ("FlashFire") but nothing happened for a long time. I have power cycled the device and now it is stuck at the amazon bootloader logo and does not do anything.

If connected to a Windows PC, Windows reports a MTP USB device and is unable to locate drivers for it.

Is there anything I can do to recover the device?

Thank you for your help!
[Fire Original Android Development] kyledowling:
Boot into recovery and reflash fire os 5.1.2 or 5.3.1 then try it all over again. Which fire os version did you come from?
[Fire Original Android Development] brickedfire:
Thank you for the quick feedback.

coming from 5.3.1.0

I was able to get into Amazon system recovery by pressing both the power and the button on the left at the same time.

Where can I download 5.3.1.0?

(I have read that I should not downgrade to a lower version because it might brick the device)

EDIT:

FireOS is located on rootjunkysdl.com (I am not allowed to share the link because I am a new forum member)
[Fire Original Android Development] Munns86:
This question isn't specifically about this tablet / ROM but more CM 12.1 / Android 5.1 and the SD card.

Will Link2SD or the Xposed modules HandleExternalStorage allow me to download Netflix content to my SD card? If both which one do people think work better for this purpose?

Thanks!
[Fire Original Android Development] toweliechaos:
I am also running cm12 (latest) on fire 7 lollipop with a restricted profile. Under the owner's profile, the Bluetooth headphones connect and work perfectly. Under the restricted profile however, bluetooth does not even turn on, let alone connect. Is this an android or rom issue?
[Fire Original Android Development] DB126:
Lol - love reference to 32 Dec :). As for the rest naming conventions and future code base have yet to be solidified or at least publicly announced for this ROM tree. Developer will update thread title, links, etc at a time of his choosing. Lots of moving pieces that need to settle in. For now it's still CM 12.1.

---------- Post added at 03:36 PM ---------- Previous post was at 03:31 PM ----------

Everything needed can be found in forum index. See post #4 for recovery info. Download links also contained in the first few posts. A thread search will also yield many helpful posts.

http://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485

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

You can try both w/o financial commitment. I would go the Xposed route first if you already have the framework installed. Otherwise Link2SD or a similar app that ulilizes symbolic links will be easier to set up (eg: the unfortunately named Apps2SD app which some prefer).
[Fire Original Android Development] ggow:
Stay tuned I am monitoring the situation on new ROM base. Will let you know once decided.
[Fire Original Android Development] kyledowling:
Sweet. Download 5.3.1 from there then in Amazon recovery choose to apply update from adb then on your computer do adb sideload 5.3.1.zip (or whatever the name is. Best is to drag and drop)
[Fire Original Android Development] mbholm:
I ran into this issue as well. Didn't get any answers here. Ended up moving my boys into standard profiles, disabling the multiuser gui, restricting to only one user account and continuing to use Kidsplace to provide the usage limits.
[Fire Original Android Development] gsjkly123:
Cannot get flashfire up and running

It has no root access and even when I enable root access in developer options it doesn't detect it. Even if I try to install SuperSU the binary update fails.
[Fire Original Android Development] ajislav:
You must reboot after enabling the built-in root access.
[Fire Original Android Development] Marsu42:
Did anyone actually try both (Link2SD & Apps2SD) and can tell the difference (esp. using Android 5.1 on this device)?

They both look the same to me and as far as I have figured out both require a 2nd sd card partition to work. Ok, I have this partition set up by now, but still wonder which one of these two apps to use?
[Fire Original Android Development] zeusminos:
I use link2sd and seams like most of the guys around here too. Not sure the difference between the 2 apps at the low level.
[Fire Original Android Development] DB126:
Link2SD has worked reliably for me and several different devices so I stick with it for app relocation. The unfortunately named Apps2SD is a general purpose tool that also supports symbolic links. Both perform that role well. Although I paid for both I'm not a fan of the aggressive revenue generation model that Apps2SD uses even in the 'pro' version. Disabled some items to satisfy personal criteria. Really a matter of personal preference/tolerance.
[Fire Original Android Development] VinZz972:
Hi,

Same problem. CM12 OK. Gapps install failed.

Unable to launch FlachFire, no root access ...

EDIT : It is very simple. We can set root in developers options.

Thanks
[Fire Original Android Development] TheLoonyRebel:
LineageOS is just a continuation of CM. So I would think that shouldn't effect our current stuff being still on CM12.1 here.
[Fire Original Android Development] melvinaury:
Bingo..We depend on Amazon for the moment. When there is a way to unlock the bootloader, then we can go up to a much updated version of Android...
[Fire Original Android Development] adodson927:
Rooted and flashed CM 12 with Nano GAPPS. Works great. Only issue is Direct TV Now streaming service is giving me error message 40. After doing some research I found that DTN doesn't work on rooted devices. A workaround for other devices as been using Magisk and PHH superuser with hide enabled for the app. I am not familiar with Magisk and I don't even know if it would be compatible with CM12. Anyone else ran into this issue or have some insight on how to get this to work? I have tried to turn off root in Dev Options but that didn't work. I'm locked in for 3 months of service so I can get my 4th gen apple tv for free. After that will probably go back to PSVUE.
[Fire Original Android Development] DB126:
Don't count on a bootloader unlock for this device. Amazon effectively sealed the silly exposures that permitted universal unlocks on 3rd gen and below. No unlocks for 4th, 5th or 6th gen devices to date.
[Fire Original Android Development] tonibm19:
Kexec could be the key, but it doesn't seem to get any attention.
[Fire Original Android Development] James.Harking:
F2FS and Link2SD

Hi all,

Can anyone confirm if you can use an F2FS partition with link2SD with the kernel the fire uses? I am not sure if this would perform better than using ext3 with the Kindle Fire. Do you guys turn off journaling to prolong the life of the micro sdcard?

Cheers!
[Fire Original Android Development] DB126:
Link2SD FAQ indicates F2FS is supported. Should be easy to confirm if kernel support is present. I don't mess with journal toggling as smaller SD cards are a commodity and I keep higher IO apps/data on internal storage.
[Fire Original Android Development] James.Harking:
Hi Davey,

I realise F2FS is supported by link2sd. To check if F2FS is supported by the kernel of the Fire 7would you recommend just to format an SD card and put it in to the reader to check if the disk can be read? Regarding journaling I have read in the past it is worth switching this off, I understand that SD cards are commodities but I would not like to continously have to be creating new partitions on a system that is still being used. Have you or others reading this had to replace cards due to wear out of the flash?

Many thanks and best regards,

James
[Fire Original Android Development] st0nedpenguin:
There's an Xposed module called RootCloak that might be worth a shot.
[Fire Original Android Development] DB126:
- to test a F2FS formated card insert and use for a suitable period to confirm operations on CM 12.1 work as expected: restart/reboot/sleep device (card reliably recognized?), explore with your favorite tools, migrate a few test apps with Link2SD, etc.

- I have not heard of SD cards 'failing' due to excessive journaling. Most cards are not exceptionally robust and should never be used for important data w/o regular backups. A minor performance bump might be realized on slow cards.
[Fire Original Android Development] bp2008:
Thanks so much. Your guide was perfect; only problem is I had to spend several hours running Kingroot 4.9.6 over and over and over again before it worked. I'm not even kidding. I must have run it 50 times, and even did a factory reset in the middle to make sure it was 100% clean. I did do something differently that last time. I stopped all the apps in the settings list except the settings app itself, kingroot, and the keyboard entry which can't be stopped. Then I started the rooting process. Some content management service kept opening back up and I stopped it every time it came up. It may have all been coincidence, but that time the root succeeded. I also took out the SD card shortly before it worked; possibly that was involved as well.
[Fire Original Android Development] gbil:
Ha, imagine my surprise when I managed to root one Fire within 8 tries and another one - bought at the same time just different colour - took me more that 30 times and in between I flashed it twice with the stock ROM, changed 3-4 Kingroot versions.

I still haven't figured out what make it work, I think it was something totally random.
[Fire Original Android Development] Shanye:
OK - so l have CM up and running. It works pretty well, but I can't find the button to turn off the keyboard sounds. Everything else can be made quiet though. Any ideas anyone?
[Fire Original Android Development] GhostRider86:
See instructions in OP and third post with FAQs...
[Fire Original Android Development] Shanye:
Doh! Why didn't I see that earlier? Now I look like some one who can't read! Thanks
[Fire Original Android Development] GhostRider86:
No worries☺
[Fire Original Android Development] DB126:
It's great you made an effort to look before posting! We all miss stuff from time to time. Happy New Year, mate.
[Fire Original Android Development] smokestacknj:
Just got this setup on my new fire So much faster than stock fire os. Was thinking of installing xposed. Has anyone tried out the xstana module on this rom? Would love to customize the nav icons.