yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] ozlo:
Any tips for getting link2SD to work properly with this ROM? I have a mSD card from an old tablet which already has an ext2 partition on it, yet link2SD doesn't seem to recognize the partition exists on this device.

Also, can Xposed be installed on here without too many conflicts? I know in some previous CM ROMs it would cause problems.
[Fire Original Android Development] masafega:
I move apps to sd with app menu without link2SD

Tapatalk
[Fire Original Android Development] marrco:
I just received a new fire. This time i really got lucky, 5.0.1 so i just fastbooted twrp and then wiped system and data before installing CM and opengapps. Using a gapps-config.txt to exclude a few useless modules (this is not a phone) i was able to install via otg the full package. And doing so i'm quite confident there are no amazon ota apk left.

I see the first sticky post still suggests flashing supersu. It's not needed, root access is already included in cm12.1. So for me it was like:

Fresh Installation from TWRP

- From your recovery perform DATA and SYSTEM wipe

- Flash the ROM File

- Flash Open Gapps - Use stock with gapps-config.txt to exclude useless modules

- wipe cache and dalvik

- Reboot and enable root from developer options

Upgrading from TWRP

- Flash the ROM File

- Flash Open Gapps - Use stock with gapps-config.txt to exclude useless modules

- wipe cache and dalvik

- Reboot

ymmv
[Fire Original Android Development] ggow:
Missed it last time, OP updated to reflect this - Thanks :)
[Fire Original Android Development] DB126:
I have not experienced conflicts with Xposed and this CM12 build. Obviously the functionality of some modules will be compromised due to CM customizations, eg: UI tweaks in GravityBox. That said most GB tweaks work fine. Note Xposed installation procedure differs on Android 5.0 and above; see here.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 29 March 2016

- Updated CM Code

- Switch to using lastest update-kindle-global-37.5.4.2_user_542168620 binaries and boot.img

- Full change log on Post #2
[Fire Original Android Development] pythoner:
Thank you very much for the Time you put into this. The only reason i bought a Fire was because there is a Cyanogenmod ROM available. You made this Device Useable.

:good::good::good:
[Fire Original Android Development] oliman99:
BT Low Energy implemented?

I've tried the CM 12.1 Rom - as well as SlimLP - with Anki Overdrive. Both work fine until the track should be scanned (so installing the app and in the app selecting a car is working). But when the track should be scanned the cars do not start moving. According to Anki Support this is the case when the device does not support BT 4.0 Low Energy. According to the device specs BT 4.0 LE should be supported by the device itself.

If the Rom is missing this feature (do you think this could the case?), is there a possibility that a future version will support it?

If there's any chance I'd like to avoid switching back to Amazons original firmware.
[Fire Original Android Development] DB126:
As an experiment I updated to latest build via FlashFire (NOT recommended) preceded by a wipe action (cache+dalvik) and accepting all FlashFire defaults without modification. No issues - all apps/data remained intact; stock recovery remains accessible. I could have also updated via TWRP which served as a backup recovery method if FlashFire borked the device. Also worth noting SuperSU v2.65 was installed/active prior to updating.

My experience serves as a single data point and does not suggest other update attempts via FlashFire will have similar outcomes. If your current CM install is working well and you do not have a TWRP fallback option I suggest skipping this update until the FlashFire/CM interaction is fully understood.
[Fire Original Android Development] ggow:
I'll look into BT LE support in the ROM. If the device supports it then it should be possible to get it working.

EDIT: I'll try and enable it for the next build
[Fire Original Android Development] sandman512:
[MENTION=5749760]ggow[/MENTION], Thanks for all the help, How can i go about having my PC see the device so I can easily transfer files over? Looking to put GAPPS on my new device that i just unlocked. Thanks again!
[Fire Original Android Development] sd_shadow:
unlocked? there is no unlocking KFFOWI
[Fire Original Android Development] hkjr:
Damn it. Applied a theme and killed my system UI, what are my choices? Locked
[Fire Original Android Development] DB126:
Sure you are posting in the correct forum? Recent post history suggest you have an HD device (also noted a recent device mixup in the HDX forums). Please see this page and/or the first two posts in this thread to help identify your device and the associated XDA forum. If you do have a 2015 5th Gen Fire use this post for help in getting the right drivers installed.

---------- Post added at 10:54 PM ---------- Previous post was at 10:47 PM ----------

Can you get into stock recovery (power down and then restart holding <left-vol>+<power> for several seconds? If so you can sideload FireOS. See here. Of course if you can still get into CM there may be a less dramatic approach. Above guidance assumes a completely hosed rom.
[Fire Original Android Development] hkjr:
Thanks for the quick response. Yes, I can get into stock recover. Technically, I can get into CM, but not past the system ui prompt. And, of course, my daughter let the battery get down to 20%, lol
[Fire Original Android Development] DB126:
First order of business is to charge the battery; don't want the pup to go dead during a recovery operation. Then follow the video to restore FireOS. You'll likely loose everything on the device. Assuming you will be restoring 5.11. Be sure to keep WiFi off until you have rerooted and blocked OTA updates. Note the OTA block in some tools has not been 100% effective. If your device updates to 5.12 you'll have a tougher time rooting and may not be able to install a custom rom without jumping through additional hoops.

Once your device is recovered and rooted give serious consideration to Nexus or SlimLP if using FlashFire. If you been following recent posts you know there is an unresolved issue w/FlashFire that can leave your device in an unrecoverable condition when flashing CM. Does not happen to everyone but you don't want to be that guy (dad) with a permanently borked device.

Good luck; got some work ahead.
[Fire Original Android Development] hkjr:
Charging at the moment. I figure she'll lose everything... she's 10, will be pissed that all her Minecraft worlds will be toast. I was at 5.11 and that's the img I had saved. Had to do this once before, early on. I was thinking Nexus and should have when it came out. I got lucky with CM and knew better to try a new theme... Thanks for the info.
[Fire Original Android Development] marrco:
works fine, just updated mine. Thanks.

i guess boot.img is just a new boot logo, but what are the update-kindle-global-37.5.4.2_user_542168620 binaries used for?

---------- Post added at 08:40 AM ---------- Previous post was at 08:36 AM ----------

btw, in OP before first twrp install a Factory Reset is suggested. If memory helps factory reset means data+cache, so no system is wiped. But before installing a different rom a complete system wipe is often recommended to get a clean install. I did that end everything was fine, with more space available to install opengapps.

with pico gapps: Post Install Free Space (KB) | 644155

so there's plenty of space to install stock gapps with gapps-config.txt to exclude a few modules
[Fire Original Android Development] sandman512:
[MENTION=5488402]Davey126[/MENTION] sorry wrong forum ,please delete. Thanks.
[Fire Original Android Development] ggow:
New build will be out shortly which should enable BT LE support. Will you be able to test and let me know whether its working as I don't have any devices to test with.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 30 March 2016

- Enable Bluetooth Low Energy Support (needs testing)
[Fire Original Android Development] oliman99:
Thanks a lot for your fast support. I've downloaded two apps (BLE Checker and Bluetooth Low Energy Checker) and both tell me that LE is working fine.

Nevertheless my Anki cars do not start scanning the track using my fire tablet. Obviously there's another problem with my/our devices. I'm interested whether it works with Amazons firmware, or if there's a HW limitation. If I put Fire OS on my tablet can I switch back to your ROM 'easily' (sorry for this question but I haven't been following this forum for one or two months now)?
[Fire Original Android Development] hkjr:
So all went well, until I got home and saw my daughter playing Minecraft... which, was surprising. I thought I'd lose everything when I went back to 5.11. Kicker was, she proceeded to tell me that she connected to wifi and then updated whatever popped up... I'm stuck on 5.12 lmfao... The best part - she's happy she has her game but unhappy that she has to look at all the Amazon clutter...

What are these additonal hoops?
[Fire Original Android Development] DB126:
You'll need to reroot via Kingroot (or possibly one of the toolkits) which leaves behind clutter that does not play well with FlashFire. You will need to get rid of that mess and replace with SuperSU, either via manual process (said to be easy; have no personal experience) or a paid app call Super-Sume available in the Play Store. Only then can you flash a custom rom which has yet to be widely done starting from 5.1.2. Presumably the latest version of FlashFire plays nice with 5.1.2. TBD.

---------- Post added at 03:10 AM ---------- Previous post was at 02:49 AM ----------

If you originally used FlashFire to install CM then your bootloader likely will not allow the use of TWRP to flash custom roms. Unfortunately, flashing CM with Flashfire is somewhat unreliable and in some cases can render your device unusable with no recovery option. Think carefully about jumping back to FireOS if must use FlashFire to reinstall CM.
[Fire Original Android Development] oliman99:
I installed CM 12.1 via TWRP, so is it safe then?
[Fire Original Android Development] ggow:
- It is safe to sideload fire OS 5.0.1.

- Don't use the newer versions of stock firmware or you'll lose twrp support

- also don't let you tablet auto update when on fireos
[Fire Original Android Development] ndg_2000:
Removed by me
[Fire Original Android Development] acdop100:
Hey,

First I want to thank you for all of your work on this project. The Fire tablet is my first android device and you've made it so much easier!

Second, I was wondering if you could outline a little bit how you started working on this? I am interested in playing with a cm13 port for this tablet and I am so confused on where to start with this device (already having looked at the official CM guide and looking around the web...). Where did you start? Did you just take a CM build and just customize it for the Fire tablet? If you have a thread on this already a link would be great. :good:

Thank you so much!
[Fire Original Android Development] sd_shadow:
CM13 will not work with stock kernel
[Fire Original Android Development] acdop100:
Oh, can you explain this to me? I am new to this kind of stuff (perhaps I shouldn't be messing with it anyways) but I thought it would be interesting to play with nonetheless. I'm guessing that the amazon kernel(?) is not normally compatible? If so, then how is the 12.1 kernel compatible? Or is it just a matter of cm13 just dropping support for this kernel?

Thanks!
[Fire Original Android Development] sd_shadow:
ggow has said that the stock kernel (which cannot be changed) is not compatible with Marshmallow
[Fire Original Android Development] marrco:
FlashFire v0.30 Released

WHAT'S NEW

2016.03.31 - v0.30 - BETA

- Exclude TitaniumBackup folder from internal storage backup as well

- Add location (internal storage, sd card, USB drive, ...) to backup listing

- Improve compatibility with StickMount-based USB mounts

- Fix a number of issues that could cause reboot while switching to flash mode

- Fix display brightness on some devices

- Framebuffer emulation for AROMA Installer (pretends to be a debugger, hijacks graphics calls)

- Fix bug where cache partition could lose data

- Complete refactor of flash mode code

- Improve Samsung CSC handling

- Fix bug where internal storage mounting could fail if external (sdcard/usb) storage present

- Update embedded SuperSU to v2.71
[Fire Original Android Development] oliman99:
Hmm, according to these reviews Overdrive seems to work with FireOS.

I guess I give it a try on the weekend.
[Fire Original Android Development] ggow:
Could you send me a logcat launching and while trying to use Overdrive?
[Fire Original Android Development] grodave:
Hello,

After the installion of cm12 and gaps . how many free spaces you have available '?

Thanks

Envoyé de mon KFFOWI en utilisant Tapatalk
[Fire Original Android Development] DB126:
Around 5.5 GB. Number will be about the same regardless of which ROM you flash.
[Fire Original Android Development] grodave:
Thanks , so the installation of cm12 take 2 go ?

Envoyé de mon KFFOWI en utilisant Tapatalk
[Fire Original Android Development] DB126:
Yes - if by TWRP

No - if by FlashFire (works for some, others have bad outcomes)
[Fire Original Android Development] ldeveraux:
Had my first soft brick installing this ROM last night. Not sure if it was flashfire update or the new ROM, bit it froze while flashing. Had to TWRP it back to health.

Which less me to ask: what's the easy fix for the play store error RH-01, where it can't connect? Tried clearing caches, reflashing opengapps pico old and latest version. What a pain!
[Fire Original Android Development] DB126:
Likely neither - it's a poorly understood interaction between FlashFire, CM 12.1 and this device that's the problem. Freezes during flashing can be triggered by lack of memory. Reboot device before launching FlashFire and limit the number/size of items included in the operations sequence. Suggest flashing rom first and then adding a modest GAaps package (Nano) after rom is up and running.

If you are starting fresh might consider Nexus over CM as it's generally easier to flash and update. Although less of a concern for you given twrp fallback.
[Fire Original Android Development] ldeveraux:
I've been dirty flashing since the initial release and never had a problem. I'm assuming it's Flashfire that did it; they updated twice in 2 days :p

If I can't restore my way back to working, I might try out Nexus, assuming I can still flash Xposed...
[Fire Original Android Development] DB126:
Unlikely FlashFire alone is the culprit; soft bricks with CM flashes have been a nemesis since day one and seem to occur at random. Just a matter of time...

Nexus is the ideal platform for Xposed as it's far closer to AOSP than CM. Some tweaks (modules) don't work with CM - although nothing bad happens either.
[Fire Original Android Development] :
As of April 2, 2016, how to install CM+OPENGAPPS on a 5.1.2 kindle:

Get root (root junkie kingroot method).

Install Flashfire 0.27 (0.30 sucks)

Set date to prior to June 1 2015

I copied my CM and OPENGAPPS image to internal storage and removed my sd card.

In flashfire, make the top step wipe the first three checkboxes + cache (5th checkbox)

Second step install CM image zip (everything unchecked)

Third step install Opengapps (I chose Pico) zip (2nd item checked)

Done. Flashfire 0.30 refused to install any opengapps package.
[Fire Original Android Development] sd_shadow:
I recommend that anyone with system version 5.1.x, not install CM12.1, the risk of bricking is too high
[Fire Original Android Development] DB126:
FlashFire 0.27 (and all prior/later) releases have reported issues flashing Open GAaps on various device types. Also a problem (albeit less frequent) flashing from a 'true' recovery environment like TWRP. There is some weirdness in recent Open GAaps packages and/or underlying Google components that is causing this. In many cases the framework goes in ok by key apps get left at the curb. Glad v0.27 worked for you but don't believe it has anything to do with FlashFire version. Time will tell.
[Fire Original Android Development] Jstame:
Curious how many of the hard bricks can 100% confirm that they were able to enter recovery just prior to installing CM with Flashfire?
[Fire Original Android Development] Neffy27:
You keep posting that over and over yet if you go through this thread, there have only been very few users reporting bricks. I have flashed many times between Nexus and CM, to include each update. No issues after I moved files to internal storage. The instructions in OP are pretty safe I'll would say.
[Fire Original Android Development] sd_shadow:
most of the brick posts are not in this thread, but in the Q&A forum

---------- Post added at 08:25 PM ---------- Previous post was at 08:18 PM ----------

very few people try to boot recovery, before it's needed

but still doesn't explain the situation with almost no complaints of bricking with the other roms
[Fire Original Android Development] Jstame:
I understand that there may be an issue with installing CM with Flashfire but its possible that its a combo of the install failing then not having the recovery to fall back on. One attempt to flash a custom recovery anytime before hand and recovery mode is toast.
[Fire Original Android Development] DB126:
Yikes - release the hounds!!

I am also in the camp of nail-bitting/worry-wart/chicken-little conservatives that have seen how bricks unfold over many weeks/versions/users and believe there is sufficient risks with the CM/FlashFire pairing

on this device

to steer new comers toward a different ROM (several fine choices) until root cause can be identified. User error as the sole cause has all but been ruled out. Veterans and others comfortable with the risk can go in with eyes open. It's only a recommendation.

Personal testimonials are interesting but largely irrelevant in the big picure. Hitting the windshield is never fun no matter how many successful unrestrained trips you take.

Like this guy [here here] who fortunately had a fallback.

[MENTION=7230143]Jstame[/MENTION] - there is absolutely no evidence of recovery partitions spontaneously becoming inaccessible prior to using FlashFire with a CM 12.1 image.
[Fire Original Android Development] Jstame:
Wow okay not what I said at all but can't argue with the evidence.... Or lack of as you so kindly pointed out
[Fire Original Android Development] DB126:
While the numbers aren't huge a fair number of users have used stock recovery to restore their device (typically sideloading FireOS) following other types of failures. Only after a CM flash attempt via FlashFire have there been reports of recovery access problems. Not Nexus, Remix, Slim or any operations involving FireOS (eg: mod attempts gone wrong). It's possible there are other dead/inaccessible recoveries that have yet to be discovered. Have not come to my attention but the forums are a busy place. Could have missed a few reports.
[Fire Original Android Development] Gibbothegreat:
I have it rooted and twrp is installed but when booting into recovery I get the amazon's internal recovery instead of twrp. Reinstalled twrp again but still getting internal recovery.
[Fire Original Android Development] kylemaguire:
You can't flash a custom recovery. You have to fastboot one every time.
[Fire Original Android Development] Gibbothegreat:
Got it thanks very much :good:

---------- Post added at 02:14 PM ---------- Previous post was at 02:00 PM ----------

Having problems installing Google play games app getting the 505 error, any ideas?
[Fire Original Android Development] csolanol:
Download it from apkmirror.com and install it.

Enviado desde mi KFFOWI mediante Tapatalk
[Fire Original Android Development] :
Logcat is for app outout. You should not find device crashes there.

http://xdaforums.com/showthread.php?t=1520508

One other thing, a developer can output an error and the app or device can continue normally. You need to learn what to look for - stack traces for instance look different in the logs so you can totally look for them.
[Fire Original Android Development] sam tyler:
Just installed this tonight. had a problem with the G-apps(was getting errors in twrp) re-download G-apps and all working now. not bad as I only bought the device a few hours ago! do you know if partition works on the recovery? as the ram does get eaten fast.also can xposed be installed or will it cause problems with this ROM? Thanks for the ROM, hope you keep it going.
[Fire Original Android Development] ggow:
- haven't tried the partition feature on twrp so can't say

- I personally avoid Xposed on CM roms

- I find that Xposed works best on AOSP based ROMs
[Fire Original Android Development] flex420:
any plans to make a cm13 rom [MENTION=5749760]ggow[/MENTION] ? :)
[Fire Original Android Development] ears1991:
thanks a lot for this, makes it an awesome device for £35!

Working nicely so far, only thing odd is the display seems squished, e.g. circles arent perfectly round, anyone else have this?
[Fire Original Android Development] Tobb555:
When I tried to install xposed it stayed at the Cid boot screen forever. I do have it installed on my phone which is also cm12.1 so its probably since this rom is still in development.
[Fire Original Android Development] sam tyler:
Thanks for both reply's, I just ask as I have been on the MTK phone craze for a while and there are not many CM roms for these(unless you can build one yourself and find everything you need) phones. But it's good to be using a CM ROM again!!
[Fire Original Android Development] blueberry.sky:
http://xdaforums.com/amazon-fire/help/screen-resolution-stretching-t3239083

It seems the actual pixels in the screen aren't perfectly square.
[Fire Original Android Development] GloriousDJ:
I think this is an interesting idea but no one seemed to comment on if it was possible to do something like this... so could we maybe insert new modules on the existing kernel without breaking the signing?
[Fire Original Android Development] grizzbud:
Have you found a solution to this issue? I am encountering the same thing right now.
[Fire Original Android Development] Ace42:
"SDXC" works. I tried two cards, one 32GB (Transcend SDHC UHS-I/U3), the other 64GB (Sony SDXC UHS-I).

Have you tried formatting the card from a PC?
[Fire Original Android Development] parkerlreed:
First boot not working for anybody else? I booted TWRP and formatted all the partitions. Then I went to sideload the cm 12.1 and pico gapps zips but the computer kept saying the USB device wasn't initializing. So then I booted the Clockworkmod recovery and USb worked. Proceeded to sideload both zips and then after rebooting it just stayed on the boot animation. I even left it as I went to sleep and it was STILL running after I woke up.

I have just tried formatting everything in Clockworkmod and sideloading. Still waiting to see if this boot works.
[Fire Original Android Development] sd_shadow:
don't sideload just place zips on sd card, Boot twrp, factory reset, and install zips

if it takes longer than 10 minutes, didn't install correctly

watch the video
[Fire Original Android Development] parkerlreed:
Thanks. In my tired state I forgot to flash SuperSU. It boots!
[Fire Original Android Development] sam tyler:
Been using this ROM over the weekend now, the only problems I have found is 1) the sd card and 2) the keyboard. I fixed the sd card problem (it would let read my sd card, but I could not write to it.)I fixed it by using nextApp SDFIX from play store and 'I think' it was a problem with the device, not the ROM. the other problem is a strange one,when I use the XDA free app I can login with the keyboard but after that the keyboard no longer types in the search box. I've used the keyboard that came with the rom, touch pal, and google keyboard. but no joy with any of them. other apps are not affected. Including browser which is fine to. I would like some help on this please if possible. I know this ROM does have a few bugs as it is new, and I should expect them,but the keyboard problem is a weird one.any advice? thanks.