yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] revilionz:
I flashed this amazing rom & never going back to stock ever again. Thank you TS !
[Fire Original Android Development] abacabie:
I bought it from a retail store (argos) and returned it there, it did have the CM boot logo, i just made sure it didn't show when i took it back.
[Fire Original Android Development] sd_shadow:
Thanks, lots of reports that U. S Amazon doesn't seem to care, but I hadn't seen much for outside the US
[Fire Original Android Development] digmank:
Is any body else having sound issues with games? I downloaded some kids games for playing but the sound is distorted. Example is the Lego DC Mighty Micro racing game. I have tried your stock ROM and the same happens there.
[Fire Original Android Development] theechap:
I've had some issues with sound in kids games (like those by Sago). What I figured out is that it's games that I got for free through the Amazon store over the years. The versions that I actually bought from Google Play all work fine. So for now I'm just avoiding the Amazon versions.
[Fire Original Android Development] digmank:
The games work just fine on my other Verizon tablet and phones. The games are also downloaded through Google as well
[Fire Original Android Development] masafega:
Thank you all for this amazing rom!

:)
[Fire Original Android Development] Tibidee:
Since I still had problems upgrading the ROM with Flashfire 0.27 and 0.28 I used Fastboot to boot into TWRP Recovery, wiped the cache and flashed the new ROM as well as GApps. It worked! :)

One problem: I used the Google Now launcher. After flashing the new ROM, I can't use the launcher anymore. It simply doesn't appear in the list of installed launchers. A new installation doesn't help. :confused: But I can live with Trebuchet as well. :)
[Fire Original Android Development] lisztophobia:
there's nothing about amazon versions of games/apps that's buggy or broken, in & of themselves. one problem, though, is that the version numbers tend to lag behind the version numbers that are distributed through google play.

an app that's up to version 10 on google play might still be version 1 or version 5 on amazon. not sure exactly why. if it's harder or more expensive to release an app update through amazon, or maybe the app developers just don't care about the amazon version because they don't make as much money from amazon's app store (fewer customers).

the "old app version" issue can cause compatibility problems with new OS versions, new phone/tablet hardware, etc, and the amazon app store is less picky than google play about which devices are allowed to download which apps. so it's more of a try 'n' see, hit 'n' miss affair than google play. you can still get old versions of apps from amazon that will work totally fine on new devices, but there's a somewhat increased chance of finding apps that don't work right because they're too outdated.
[Fire Original Android Development] kmharman:
Play Store 963 error

I was getting the same error trying to update apps that I had moved to the SD card. After moving them back to internal storage they updated with no problem. Limits the number of apps you can install, and makes the SD card usable only for data and media storage.
[Fire Original Android Development] keithalaws:
The internal memory on this tablet is very limiting. It needs marshmallow so the internal and SD card can be unified
[Fire Original Android Development] DB126:
Not going to happen as bootloader (and thus kernel) remain locked. Stock kernel has Lollipop roots. ROMs need a compatible kernel.
[Fire Original Android Development] BransonH:
Not booting

So I recently attempted to install CM-12.1 on a 5.1.1. device and after following all of the instructions it appears that I am having a bit of a problem.

As of right now the device will not boot past the CM logo, but more importantly I am not able to get into the recovery options at all. I have held down the volume up + power button but all I see is the Amazon logo and nothing else, it just hangs there mocking me.

I have restarted with no change. Attempted to use RJ's tool to push it into recovery, no change. I have also attempted to access it via ADB but I believe that debugging was disabled as it is not showing anything when I try ADB devices.

I also reached out to Amazon directly to see if I could get the device replaced, but due to it being outside of the 90 day warranty this is not an option. So at the end of my rope here, don't know what to do.

After looking over some other threads, it seems that there may be nothing that can be done, but was hoping someone, somewhere, might have an idea. Any assistance would be appreciated.
[Fire Original Android Development] GarlicBreadFox:
Thanks a lot for the CFW, OP. Works a threat.

Haven't tested everything but will tomorrow.

Installed open_gapps-arm-5.1-pico-20160320 btw, the latest as of now.

Question though,

1. If I encounter issues with that version of OpenGapps, how would I install an older one? Should I repeat the exact flashing process (CM again + OpenGapps) FROM CM? Should I repeat the exact flashing process from FireOS? Should I repeat the same process but ONLY for OpenGapps and from CM, or...?

2. I don't see SuperSU installed, does it mean I lost root and have to re-root? And in any case should I install SuperSU myself? Can I use RootJunky's multi tool to re-root and get SuperSU, no issues?
[Fire Original Android Development] Dread This Day:
Your Fire is a paperweight. If you scroll up you'll see I JUST went though this. Luckily I was within my warranty time, and when my replacement came, it was on 5.0.1. I am sorry for your loss my friend, there is not yet anything that you can do. Flash fire is dangerous.
[Fire Original Android Development] BransonH:
Yeah, this is what I was afraid of. My question then is, if Flashfire is so dangerous then why even have the steps on the OP to use it? Especially considering so many appear to be having this issue. Just saying, maybe they want to make it clear that it is not stable when it comes to using this ROM on 5.1.1. or above. Just a thought.
[Fire Original Android Development] DB126:
Yep - FlashFire and CM is an unstable mix, at least on this device. Using the latest versions of both (especially FlashFire) and careful attention to detail can reduce but not eliminate the risk. While there are many successful outcomes you are taking a chance flashing CM via FlashFire without a fallback like TWRP which is not an option for most.

There are copious warnings throughout this thread and other threads in the 2015 Fire forum. There are an inherent risk with any system flash, regardless of tool or technique. That said, using FlashFire with CM is particularly dangerous given the ability to enter stock recovery is often destroyed when things go wrong. This does not happen flashing other ROMs like Nexus and SlimLP.

It is up to the thread author to post additional cautions regarding potential risks of FlashFire in the OP.
[Fire Original Android Development] GarlicBreadFox:
[MENTION=5488402]Davey126[/MENTION] could you maybe help me out with the questions above?
[Fire Original Android Development] sd_shadow:
1 I would reinstall rom and gapps if trying an older gapps version

2 cm12 has its own superuser built in

CM12's root access is disabled by default.

A couple of options to upgrade root

a. settings>about tablet >tap on build number 7+ times, to enable Dev options>go back to Settings>Developer options>Root access>Apps and ADB
then reboot

or

b. Install BETA-SuperSU-v2.49.zip in TWRP or FlashFire
[Fire Original Android Development] GarlicBreadFox:
Alright thanks a lot [MENTION=4267571]sd_shadow[/MENTION]. I have two questions left then if you don't mind

1. To reinstall CM+OpenGapps, should I do the whole, back to stock FireOS, then CM or just CM inside CM straight away (I went back to Stock when I had Nexus, in order to try CM).

2. Do you reckon it's better to just leave the built-in root or should I go for SuperSU?
[Fire Original Android Development] drkbg:
One thing I don't get.

If CM has built-in root manager why in the instructions in the first post in the TWRP part there is SuperSU install.

Can they co-exist?
[Fire Original Android Development] DB126:
See [MENTION=4267571]sd_shadow[/MENTION] responses. Further comments:

- Installing/updating CM 12.1 via FlashFire carries risks including a spontaneous hard brick with no access to recovery. To date no definitive explanation why this occurs. Using the latest version of FlashFire and carefully following directions helps. But failures continue to occur. Best advise is to limit the number of flashes until a solution is found. Note this does not apply to updates made via TWRP which is not an option for you. You might want to consider one of the other roms (eg: Nexus or SlimLP) that do not exhibit this behavior with FlashFire. You will need to reload FireOS 5.1.1 via stock recovery if you go this route (switching ROMs via FlashFire is not recommended).

- Consider the merits of Open GAaps nano vs pico (you can see package descriptions on the Open GAaps site). Given the above I do not recommend flashing nano if you already have pico installed.
[Fire Original Android Development] sd_shadow:
Depends on which bootloader version, I'm no longer recommending cm12 if you have the 5.1.1 bootloader, been too many bricked Fires

flash back to stock, and try the nexus or slim rom

if you have the 5.0.1 Bootloader doesn't matter

built in superuser if fine, mostly a user preference

---------- Post added at 06:34 PM ---------- Previous post was at 06:31 PM ----------

supersu will override the built-in superuser
[Fire Original Android Development] DB126:
Yes. Some prefer the additional flexibility afforded by SuperSU along with interface consistency when switching between ROMs. That said, the integrated root manager in CM works fine and does not need to be augmented by SuperSU.
[Fire Original Android Development] drkbg:
What does KFFOWI mean? I see that my device model is that.
[Fire Original Android Development] sd_shadow:
Amazon model number for the 2015 7in Fire

see Fire Index: Which Amazon (Kindle) Fire Do I have?
[Fire Original Android Development] drkbg:
Yeah, I get that... Just wondering If it stays for something meaningful. (Google doesn't help much)
[Fire Original Android Development] GarlicBreadFox:
Alright [MENTION=4267571]sd_shadow[/MENTION] and [MENTION=5488402]Davey126[/MENTION] thanks.

Guess I'm back to the Nexus ROM now that I got the hang of it...

Will post a question in the pertinent topic.

Kindle Fire Freshly Optimized Worlwide International?
[Fire Original Android Development] yochananmarqos:
SuperSU will overwrite CM's su binary.
[Fire Original Android Development] sd_shadow:
In my Fire index I have posted all the Fire model numbers, if you crack the code, let us know.
[Fire Original Android Development] atayal:
i used pico
[Fire Original Android Development] sd_shadow:
pretty sure

XXXWI = WIFi only

XXXWA = WAN (3 or 4G)
[Fire Original Android Development] drkbg:
I guess KF stands for kindle fire...

So just a few letters to decode...
[Fire Original Android Development] sd_shadow:
KFxxxx = Kindle Fire

xxFOxx = Codename (FO = Ford)

xxxxWI = WIFi only

xxxxWA = WAN (3 or 4G)
[Fire Original Android Development] forenmoderator:
I flashed another Fire 5 Gen. bought one week ago with FlashFire. I've been ignoring all the warnings and and after that it got stuck onto the CM-Logo. Damn! But in the End I tried the following, which helped me:

Copy CM Rom and OpenGApps to sd card

Start Fire in Fastboot-Mode (hold Volume up and Power on)

Start RootJunkys SuperTool

Select "Boot device to TWRP Recovery for ADB fire os 5.0.1 or below"

This worked! And Kindle boots up to TWRP

From there, click Wipe and choose ROM and GApps from your sd Card

Click on Flash

After flashing, click wipe

Reboot.

Works!

/edit: the original recoverymode is gone anyway!

Give it a try. I guess I'm not the only Person where this could work.
[Fire Original Android Development] glockman4519:
I just flashed the latest build and am very happy with my tablet. With this rom on it makes this tablet as nice as some of my $150.00 plus tablets.

The only issue that I had was with gapps. I used open gapps build 20160319 and it would boot all the way to system and set it up but it wouldn't let me go through the set up because of multiple Google faults. After using Rootjunkies tool 3 times on the 3rd time I use an older set of gapps "20160216 nano" that I happen to have on the SD card and it booted and set up perfectly.

I will be keeping this gapps zip for future use now unless a newer one is confirmed working.

I love this rom and it has turned this nice Fire into an great little android tablet. By the way, this Fire was the only one of the bunch that I purchased, that I did not allow to update to 511. It is still on 5.0.1.. Good...

"Chance Favors the Prepared"
[Fire Original Android Development] DB126:
Guessing your device bootloader is v5.0.1 which permits booting twrp. v5.1.1 and above do not allow booting twrp.
[Fire Original Android Development] Doggy77:
Is there any chance to find out which bootloader is installed when CM is installed?

And does the recovery to current Stock Amazon by stock recovery-options also replace the bootloader?

Best regards,

Markus "Doggy77" Seifert
[Fire Original Android Development] DB126:
There is no direct method to query the bootloader version directly. By launching twrp you have indirectly confirmed it is below v5.1.1. The bootloader remains locked and is not changed by flashing a custom rom. It can be modified (upgraded) via Amazon's OTA update process along with the kernel and stock recovery.
[Fire Original Android Development] AwlsomeAlex:
Stagefright Vulnerability

I expect that a fix for the new vulnerability of Stagefright will be fixed and patched for the CM Build yes?
[Fire Original Android Development] sd_shadow:
there isn't a new vulnerability
[Fire Original Android Development] DB126:
Ignore the media bluster. Yes, a theoretical extension of previous exploits could, with the just right magical brew of circumstances, lead to further compromises. Note that an attacker has to know something about the device and software running on it. How many Fords are running CM, and of that minute fraction how many contain sensitive information that would warrant special attention from a 'bad guy'? If you are running the NSA or carrying nuclear codes and have an Android device you might think twice about how/where you use it. Everyone else can sleep easy.
[Fire Original Android Development] masafega:
Thanks for this great rom, only a question...

The problem is only when i flash from original to cm or also upgrading cm?

Thanks

Tapatalk
[Fire Original Android Development] DB126:
Both - assuming "the problem" is in reference to bad outcomes installing/updating CM via FlashFire.
[Fire Original Android Development] snappy65:
Having a few problems with dropouts , Bluetooth seems to be interfering with WIFI, anyone else find this, thanks for custom rom, great effort.
[Fire Original Android Development] masafega:
Thanks, fortunately they came with 5.0.1 ?

KFFOWI Tapatalk
[Fire Original Android Development] Neffy27:
Are Slim Gapps compatible to use with this ROM?
[Fire Original Android Development] DB126:
Most GAaps packages should work; I recommend Open GAaps nano. The Play Store is suppose to come along for the ride but it often gets left at the curb. Simply side load from a trusted source like APKMirror after flashing nano. Once the Play Store is installed/active you can add individual Google properties as needed.

Avoid flashing large GAaps packages that include every conceivable Google app along with the kitchen sink. The system partition is a snug 1.2 GB on this device. Easy to fill and tough to correct when filled short of a wipe/reflash.
[Fire Original Android Development] ldeveraux:
Anyone try the new flashfire build released today? It's supposed to fix problems with bad flashes, maybe it helps us with this CM12?
[Fire Original Android Development] DB126:
I looked through the change log but didn't see anything specific to CM or the type of failures that are most common with this rom/device combo. There are a number of general improvements that may improve overall reliability. I'll likely upgrade to v0.29 w/o reservation.
[Fire Original Android Development] marrco:
it looks like the bug freezing /system has been solved. If memory helps a user reported the error causing the fire to brick started with an unable to unmount system message.

2016.03.22 - v0.29 - BETA

- Fix some compatibility issues with N Preview

- Fix app_process causing a reboot during startup

- Fix bug which could cause flashing /system to freeze

- Improve partition detection size accuracy

- Reduce app startup time

- Reduce time taken to switch to flash mode

- Add option to format /cache (wipe action)

- Improve external sdcard compatibility

- Improve adopted storage compatibility

- Improve USB drive compatibility

- Add additional OTA paths for NVidia

- Improve partition platform detection

- Add support for backing up internal storage (excludes FlashFire, TWRP and CWM backups)

- Fix error when opening bootloader image not wrapped in an archive

- Add setting to enable flashing primary and secondary bootloaders (automatically disabled)

- EverRoot: "Enable ADB" no longer enabled by default
[Fire Original Android Development] Dread This Day:
On testing, my Bluetooth won't connect to my soundbar, that my phone can connect to with no problem.

Does not seem to interfere with WiFi.

That was me, on 5.1.1 dirty flashing an upgrade of this ROM. Thankfully my replacement Fire came with 5.0.1 and I do not have to worry about that any more. That issue isn't so much with it freezing on /system, the issue is with it making the stock recovery inaccessible to sideload FireOS to unbrick the damage. IF YOU'RE ON 5.1.1 LIMIT YOUR FLASHES WITH FLASH FIRE! Until you KNOW the kinks are worked out, if you already have this ROM flashed, just leave it be. No update is worth a brick, just be patient.
[Fire Original Android Development] DB126:
Well said.

Note the issue with breaking recovery access appears specific to the FF/CM combo and has not been seen with other roms. Flash failures do occur for various reasons but the recovery partition remains accessible allowing the device to be recovered.
[Fire Original Android Development] marrco:
I know that sometimes recovery is not available powering the fire with vol - pressed. But with 5.1.1 you should be able to access fastboot pressing power and vol + and then type

fastboot.exe oem reboot-recovery

Did you try that? Could you get to fastboot at least, to read partition info?

> No update is worth a brick, just be patient.

Issue with my fire is a grey pixel, so before asking for a replacement i want to be sure that all issues are fixed. I don't want to risk to get a new fire and the brick it.
[Fire Original Android Development] DB126:
Fastboot is accessed via <power>+<vol-up>

Stock recovery is accessed via <power>+<vol-down> (long press 5-10 sec)

"oem reboot-recovery" does not work for the type of failure being discussed. If it were that easy device recovery following a borked CM flash would be possible.
[Fire Original Android Development] eoraptor:
So I have a question... on both Stock Fire OS and SlimLP my USB accessories (keyboard, mice, etc) Work, but in CM 12 they don't... Does anyone have a workaround or ideas as to why? Swiftkey is nice, but on those occasions when I have to do serious work via my fire (such as when my laptop is down for a reinstall) it would be nice to plug my little USB set into it to type on.
[Fire Original Android Development] ajislav:
You should capture a logcat and dmesg under CM (and Slim) and post it here.. Then ggow can have a look
[Fire Original Android Development] DB126:
On my device a wired USB keyboard and GPS receiver work fine via inexpensive OTG adapter. CM build 20160228 flashed via TWRP. Both devices attach/detach silently. Don't think it's the ROM. Possibly an artifact of flashing multiple ROMs or FlashFire weirdness. Might try reverting back to stock and the reflashing CM if that's your preference. Nexus is another option.
[Fire Original Android Development] Its_Ima:
otg on cm 12

When you flash cm 12 do you get otg support

---------- Post added at 06:33 AM ---------- Previous post was at 06:01 AM ----------

When you flash cm 12 do you get otg support and does it make your device slower?
[Fire Original Android Development] ldeveraux:
Yes,otg Is supported, why would it make anything slower?
[Fire Original Android Development] masafega:
There is a way to change device id for Google Play?

I tried this guide but the device name remains KFFOWI and many apps are incompatible...

Thanks

Tapatalk Amazon Fire 7
[Fire Original Android Development] Neffy27:
I used market helper to change it.
[Fire Original Android Development] masafega:
Market helper change the name of device but app remain always incompatibile

Tapatalk Amazon Fire 7
[Fire Original Android Development] booogermonkey:
What I do is just find the apk elsewhere, and install it. A lot easier than trying to trick Google play
[Fire Original Android Development] masafega:
you're right and for upgrades ?

Tapatalk Amazon Fire 7
[Fire Original Android Development] robnitro:
Hi, so has anyone got ibss ,ad-hoc WiFi working?

I see my ad hoc WiFi, correct info, but it doesn't connect. I tried wep off, wep on and some adhoc apps, like at zt switcher. The slim ROM, resurrection both won't even show the adhoc WiFi, so I read that its a cm feature. just can't connect!
[Fire Original Android Development] booogermonkey:
Same thing. If an app works how you want it to, not a lot of reason to upgrade it all the time, right[emoji12]
[Fire Original Android Development] ipdev:
I use apk extractor (download from google play) and copy it from another device that is supported by the app. This way I know what version I get and that it's up to date. (Benefit of having multiple brand devices.)

I have downloaded from apk mirrors before but you are never quite sure what you will get. (Sometimes the app is 2 or 3 versions out of date.)
[Fire Original Android Development] kramalot:
In many cases (all that I have tried, which I admit is not many) the app will update normally.
[Fire Original Android Development] DB126:
There are various guides floating around, some more aggressive than others, regarding the number and type of build.prop tweaks. I have yet to see one that is both safe and effective. Messing with this file brings risks including rendering your device unbootable. You'll need to do some poking around to find one that suits your needs.

Alternatively, download apps of interest from a trusted source like Apkmirror or 1Mobile. Once installed they should auto update from the Play Store regardless of how they were originally installed.
[Fire Original Android Development] masafega:
Thanks Davey, i have tried but no auto update ?

Tapatalk Amazon Fire 7
[Fire Original Android Development] Its_Ima:
Is there controller support for the otg feature.
[Fire Original Android Development] DB126:
Not sure what you are asking; OTG works great with this rom (keyboards, GPS receivers, storage, etc).
[Fire Original Android Development] Its_Ima:
Will it work with Xbox 360 wireless receiver?
[Fire Original Android Development] DB126:
Aah. No direct experience or ability to test. Sorry...
[Fire Original Android Development] Neffy27:
What device did you try? I changed to Asus Nexus 7 and have no compatibility issues.
[Fire Original Android Development] Its_Ima:
I tried flashing it using flashfire it keeps giving me this error, cant install this package on top of incompatible data. Anyone know how to fix this?

---------- Post added at 02:37 PM ---------- Previous post was at 02:12 PM ----------

Never mind I was doing the instructions wrong it works now.