yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] switchy85:
If you have xposed you can use the module xinternalsd to do that. I have it set up to do that for all apps.
[Fire Original Android Development] marcinse:
Oh no... Just got my Kindle, hit the update button without thinking and it's now 5.1.1... Any way to downgrade or anything else I can do to install CM?
[Fire Original Android Development] Dr.TheMaster:
Not for now.. But I guess soon :)

Kindly press thanks if I helped :)
[Fire Original Android Development] miniX1:
how about update cm-12.1-20151211-UNOFFICIAL-ford.zip --> cm-12.1-20151216-UNOFFICIAL-ford.zip? it is possible to update without to lose user data and settings? something like OTA update? or i habe to flash the new version and lost everything?

maybe this question should be get to the FAQs?!
[Fire Original Android Development] blueberry.sky:
Yes, user data and settings are retained by doing a "dirty flash" but if you experience any bugs or problems after a dirty flash, then backup your apps, user data, settings & do a clean flash instead. Backup using Titanium Backup or your choice from the multitude of backup apps.

Dirty flash = wipe cache, dalvik cache and system.

Normal clean flash = wipe dalvik cache, cache, data and system. Always do this if you come from stock or another rom.
[Fire Original Android Development] BakCompat:
Well I loaded the 1216 version on one of my $35 units and have played a bit with it for the past few days. Antutu benchmark was 26474, which is decidedly low for current hardware, but certainly acceptable and reasonable for this class of hardware.

The clock app kept crashing repeatedly on me, and some searching led me to clear and delete the cache and data for that app under System Settings, which has fixed it. A few of my normal apps report as incompatible on this device in the Play Store, including: Automatic Call Recorder, Network IP Scanner, R Communications radio app, Weather Underground, and I get an error -505 trying to install Google Play Games. These are having installed open_gapps-arm-5.1-mini-20151218 so I'm wondering what I need to try instead. Any suggestions here?

I also ran a Geekbench battery test for anyone interested, and it reported a battery runtime of 08:07:40, which is pretty darned good for such a low cost device. In short, money well spent, and still looking forward to the ever increasing capabilities of future rom enhancements. Thanks to ggow and everyone else who has spent such wonderful time and effort on developing an unofficial CM rom that works so darned well.
[Fire Original Android Development] qtotter:
Actually, I use open gapps "super." Of course, it is too big to install as it is, but you can edit "installer. data" in the package to choose what to or what not to install to make it fit your own device's capacity. It is easier to remove apps from a big list than searching for missing apps/files for a mini list.
[Fire Original Android Development] GartimusPrime:
I have purchased 4 of these for my kids for Xmas. Got them in the mail and immediately installed your cm on them before wrapping, thank you so much!
[Fire Original Android Development] gad42000:
ok.. rooted.. did back up.. did factory restore.. used rootjunkys script.. went into twrp.. cm installed ok.. open gapps did not (wrong version) script stopped..

1. cm now loads but how do i install the opengapps and the supersu.?

2. Can i go back to the 5.0.0 if i want?

3. do i need to do anything to prevent it from updating?
[Fire Original Android Development] singlebyte:
I had to ADB IINSTALL GooglePlayGames to get it to work. But now, all games are working,
[Fire Original Android Development] dEris:
Read entire thread. I installed SlimLP from rooted 5.1.1. Can I flash this with FlashFire from SlimLP?
[Fire Original Android Development] ruggar:
Just wanted to drop OP a note. Thank you. Picked up two for Christmas, rooted, and flashed CM on it without any issues. Cheers.
[Fire Original Android Development] abacabie:
I don't think anyone has been able to install 12.1 with Flashfire at the moment, but I think they are working on it.
[Fire Original Android Development] dEris:
Ok. Thanks for the update.
[Fire Original Android Development] Pond-life:
Download the right version of opengapps and install it how you tried to before.

Not sure we've a rom for 5.0.0, but there's one for stock 5.0.1 on the forum, if you feel the need to go back to Fire OS.

It won't update to new stock Fire OS from here without you going back to it intentionally.
[Fire Original Android Development] gad42000:
IF you lead me to the correct version of open gaps i appreciate it. I thought i had the correct one. (opengaps stock 5.1 2015-12-19)

IM getting the message, "insufficient storage space available in system partition.. You may wish to use a smaller opengapps package or consider removing some apps using gapps-config

regarding going back, im assuming doing a restore from my backup before adding cm wont make me completely whole again?

i got back into twrp, but don't remember how i did it... how?
[Fire Original Android Development] sd_shadow:
Stock is too large use mini, micro or pico
[Fire Original Android Development] Pond-life:
Stock is very big, so not surprised it doesn't fit, most use Pico and install the ones they need from Play store after. Mini gapps may well work. You can download a smaller one or you can make the file you've got work as a smaller version by making a gapps-config.txt file like it suggests by putting one of these command words in it. e.g. PicoGapps to just do the smallest.

To see what's in each https://github.com/opengapps/opengapps/wiki/Package-Comparison

Or you can include or exclude individual apps by writing the gapps-config.txt

https://github.com/opengapps/opengapps/wiki/Advanced-Features-and-Options

As to going back, if you made a backup in twrp then yeah you can just use that to go straight back to how it was. I've used that a few times already.
[Fire Original Android Development] ggow:
- I'm still working on getting cm-12.1 to play nice with FlashFire

- I have got past the signature checking issue but there are still other problems stopping it from working

- Will make a new release when I have it sorted.
[Fire Original Android Development] mmurphmsu:
I did the same thing.
[Fire Original Android Development] duanim:
Thanks

GGOW what is max resolution that you can set on the device for YouTube because is set 480 to default
[Fire Original Android Development] gad42000:
once twrp is installed on fire, how does one access it?
[Fire Original Android Development] martinml:
You can't "install it" (the bootloader checks its validity), you just boot it on the fly when necessary. That means you need to plug the Fire to a computer and do the "fastboot boot whatever" command each time you want to boot TWRP.
[Fire Original Android Development] fmc000:
TWRP cannot be installed on fire.
[Fire Original Android Development] kramalot:
The easiest way to get started is to use rootjunkies superttool.

Find it here http://www.rootjunkysdl.com/?device=Amazon%20Fire%205th%20gen&folder=SuperTool
[Fire Original Android Development] fmc000:
This doesn't change the fact that twrp cannot be installed on fire. The bootloader is locked and therefore you can only boot twrp, provided that you are not on 5.1.1
[Fire Original Android Development] gad42000:
Im curious what is meant by bootloader locked.

before adding cm12, i was able to batch installl a bunch of stuff using abd install.. can i still do that? If i restore with twrp will i be able to?

i tried booting into abd mode and it tried installing drivers and was not able to find them.
[Fire Original Android Development] blueberry.sky:
For us, a locked bootloader just means we can not "install" twrp. The bootloader will not allow it to be installed.
[Fire Original Android Development] djklmnop:
Are you guys getting flickering on your screen? Kinda like refresh rate gone wild, giving vertical lines. It happens after a period of use. A reboot quickly fixes it though, then it would come back again after some time. I've tested this on 3 different tablets.
[Fire Original Android Development] howzitnow:
2 tabs here from the October batch... Zero screen issues. I also had 2 from the Thanksgiving batch. Both had dead (stuck?) pixels. In addition to that, one screen would go all white but I could still see ghosts of the icons underneath. Gently whacking on the back would fix it for a while then the problem would return. The 2 replacements seem fine, tho they were only on long enough to googleize and root.
[Fire Original Android Development] gad42000:
how does one install the abd drivers for cm 12?

i wanted to abd install some programs.. booted into abd mode and then when connecting couldn't find drivers.
[Fire Original Android Development] ty_ger07:
TWRP cannot be added to the Fire as a bootloader. The stock bootloader will remain on the device. This means that every time you turn it on, it will boot up with the default Fire bootloader. This means that you will only have access to the very basic stock recovery console and you can't flash ROMS or anything like that from a normal boot.

The ONLY way to access TWRP and perform a flash is to use ADB from your computer to reboot your Fire into Fastboot mode and then push the TWRP file from the computer to the Fire which will tell the Fire to boot up with it. It is only a temporary thing. Next time you turn it off, the TWRP is gone and it will boot normally with the stock bootloader. Every time you want to access TWRP, you have to boot the tablet up, make sure ADB debugging is enabled in developer options, and have your computer reboot it into fastboot mode and push the TWRP image to it to boot up into.

Booting into Fastboot mode only works as long as you have Fire version pre 5.1.1. If you have Fire version 5.1.1., you are screwed and will not be able to fastboot into TWRP. This is because Amazon fixed the security flaw which allowed Fastboot into TWRP to work prior to that version.

Have questions about ADB, Fastboot, and TWRP? This should help out a lot:

https://www.youtube.com/watch?v=4dwguHoxTvo

Definitely a great start at least.
[Fire Original Android Development] fmc000:
This previous post is mostly correct; however, TWRP is not a bootloader but a custom recovery. The bootloader is another software which resides in a different partition on the phone. The security flaw that allows pre-5.1.1 installations to boot twrp is within the bootloader.
[Fire Original Android Development] su6ur6an:
Would someone be willing to share simplified steps to build this properly from source?
[Fire Original Android Development] ggow:
Update about FlashFire

- I now have a version of CM-12.1 which is flashable from FlashFire

- I tested it by Flashing a Sanitised version of FireOS 5.1.1 + SuperSU via TWRP

- Then install FlashFire

- Then Setup a Wipe and install .zip from FlashFire and it worked fine

- There were numerous problems why it wasn't working

- I'll will update the thread with a new version shortly
[Fire Original Android Development] ggow:
New Build is Up

- Dated 22 Dec 2015

- Change log on Post #2

- See this post to see how I tested going from FireOS_5.1.1 to CM-12.1
[Fire Original Android Development] thechosenone43:
Any needs to update to 22-12 build when I'm on your 16-12 build that is really smooth and stable for me? Thanks for effort and happy holidays ?
[Fire Original Android Development] ggow:
- If you're happy with the build you currently have then no need to update

- The main thing in the new build is installation fixes
[Fire Original Android Development] funkybrunk:
Playing around with Flashfire for the first time... (making backup now). Safe to dirty flash from 12/16 using FF? I'd presume yes, and can follow up otherwise.
[Fire Original Android Development] ggow:
- Should work fine

- Let me know how you get on
[Fire Original Android Development] codepilot:
Hello ggow,

I just figured out this morning that CM 12.1 is not possible to install the usual way if FireOS 5.1.1 is installed, and now you gave me this evening the solution - perfect!

The steps I've done:

SuperSU as described here

Install FlashFire as apk from here (done by

adb install flashfire-0.24.apk

)

Downloaded your CM 12.1 file from the first post in this thread

Copied it with

adb push cm-12.1-20151222-UNOFFICIAL-ford.zip /mnt/sdcard/

on the device

FlashFire => Setup wipe and flash the ZIP-file (also checked the boot-flag on!)

Everything works so far. THANK YOU FOR YOUR EFFORTS!!!
[Fire Original Android Development] funkybrunk:
Upgrade went well, but I don't think FF liked my opengapps package (no google services installed). I'll try a different package to see if it remedies the situation. I probably shouldn't have wiped system before flashing.

Edit: It didnt like the latest micro package either. Is there an issue with opengapps compatibility with FF? Restoring my backup now.
[Fire Original Android Development] je66b:
stupid question but does this block_based_OTA mean that we can now download updates you make to the rom OTA? I dont believe thats how it works but I figured I'd ask anyway cause thatd be awesome.
[Fire Original Android Development] ggow:
- Like a lot of people here I am just learning really how to use FlashFire and what it's limitations are etc.

- So in answer to your question, I don't think there are any issues but no 100% sure either.
[Fire Original Android Development] ggow:
- No BLOCK_BASED update refers to a way of Flashing the ROM file to EMMC

- BLOCK_BASED flashing means the same result will be achieved as if flashing system.img via fastboot

- It also seems to be quicker and therefore probably more efficient than the Non BLOCK_BASED flash
[Fire Original Android Development] funkybrunk:
Cool. After restoring the backup (FF did this perfectly). I attempted another dirty flash, this time, no issues.

When Dirty Flashing with Flashfire

- BACKUP FIRST! (either via TWRP or FF. It does not appear that FF backups are compatible with TWRP, so TWRP would be safest if you have the fastboot boot ability)

- DO NOT wipe System, or you're gonna have a bad time.
[Fire Original Android Development] codepilot:
OK - does that mean that there is not chance to get gapps running now?

I don't have a backup :silly: ...
[Fire Original Android Development] funkybrunk:
Can't say for sure. After wiping system, gapps wouldn't take either time I tried to flash. Maybe a clean flash is needed if starting with a clean system partition.
[Fire Original Android Development] codepilot:
Yep I tried to install the gapps via FF, with a message "no space left on device" - but this can't be the reason.

So how to start with a *clean* system partition? I can't use TWRP because I've unfortunatelly updated FireOS to 5.1.1 previously, so no way to get this installed, and bricking the device as one did in this thread is not an option.
[Fire Original Android Development] ggow:
- I have cm-12.1 without gapps

- I'll try to install via FlashFire now and let you know what happens
[Fire Original Android Development] funkybrunk:
Please note that my experience is dirty flashing from the 12/16 build to 12/22 using Flashfire. I installed CM before amazon blocked the fastboot boot functionality in the 5.1.1 update. Please refer to ggow's install steps coming from Amazon 5.1.1.

Edit: and you'll want to grab a new gapps package, micro or smaller.
[Fire Original Android Development] codepilot:
Yeah, thank you! That was the solution. I first downloaded the stock package of the gapps, but the nano package now works.

I flashed this also with FlashFire, and everything worked. Thanks to you all, I'm now happy with the device! :p

What about updates on the CM? Will they come automatically, or do I need to fireflash these again?
[Fire Original Android Development] Vlasp:
Quite interesting, seeing that it has 2 USB ports, so I can charge my phone also. I really need a backup battery for my phone, I am using a Battery, connected to an Arduino, which outputs 5V, which can charge my devices.
[Fire Original Android Development] Harry44:
Taking pictures doesn't work on any camera apps but video camera seems to work
[Fire Original Android Development] a1yet:
removed by me
[Fire Original Android Development] :
The tablet slows down during GFX intensive tasks e.g badly written GIF players e.g Reddit clients and certain games e.g Clash Of Clans. And the old style YouTube videos too. The ones that are embedded in apps, not the new HTML5 type ones. Could you look into this?
[Fire Original Android Development] Awesomeslayerg:
Nevermind i got it i missed a step..

Cant wait for the next release when most of the things are more stable. Cant believe we now have cynogenmod on this device!!

Also im wondering if you can now flash custom kernels yet or no
[Fire Original Android Development] diegocr:
Here rom is stable, somethings don't works.

For custom kernels need unlocked bootloader.
[Fire Original Android Development] csolanol:
Hi all,

are data stats (Settings->Data Usage) working in this rom and are they real?.

Ty.
[Fire Original Android Development] kylemaguire:
This tablet doesn't have a cellular connection, so only your wifi usage should be shown.
[Fire Original Android Development] csolanol:
I know it's WiFi only. I ask for the stats, are real?.

I attach mines. It isn't cm, just my testing SlimLP.

Enviado desde mi KFFOWI mediante Tapatalk
[Fire Original Android Development] Unjustified Dev:
The power_profile.xml is missing from the tree. It can be obtained by decompiling stock framework-res.apk and pulling it from framework-res/res/xml . It should be placed in overlay/frameworks/base/core/res/res/xml/power_profile.xml of device tree.
[Fire Original Android Development] patt2k:
Wow no way and this tablet will be on sale for 35$ on BF. One question does this mean no longer need tethered boot mean that you don't need to fastboot to boot CM 12.1? and guys imagine this with CM 13 and SD+internal as storage. This could be killer cheap tablet. For basic things!
[Fire Original Android Development] sd_shadow:
Correct
[Fire Original Android Development] csolanol:
Tu ver y much!

Enviado desde mi Nexus 5 mediante Tapatalk
[Fire Original Android Development] blueberry.sky:
But we can't boot a different kernel as long as the bootloader is locked. So will CM 13 be possible? Maybe if amazon puts out a 6.0 Marshmallow based fire OS update. I'm presuming we can then use the kernel from that?
[Fire Original Android Development] theophile2:
It may be possible to run Marshmallow on a kernel build for Lollipop. Heck, there's a Lollipop ROM for the Xoom that runs kernel 2.6.39, the version that shipped with Honeycomb!
[Fire Original Android Development] blueberry.sky:
Damn, that's awesome. I was worried that this tablet would be limited to just following Fire OS updates.

So what limitations are likely from being locked into the amazon kernel?
[Fire Original Android Development] csolanol:
Sadly It didn't work. Built it after clobber and tried dirty and clean flashing [emoji30]

Enviado desde mi Nexus 5 mediante Tapatalk
[Fire Original Android Development] Awesomeslayerg:
The full screen mode is a little buggy whenever i try playing youtube videos and play it in full screen mode.
[Fire Original Android Development] kudoz83:
Out of curiosity... has anyone tried USB Host functionality? Keyboard? USB drive?
[Fire Original Android Development] Awesomeslayerg:
They work Sd_shadow has a thread on that i think
[Fire Original Android Development] gad42000:
Im sorry for being so dense but I cant figure out how to install programs via adb in cm12.

Is there a place to turn on adb debugging? I cant find it.

I have adjusted rootjunkys script to the files i wanted to install via adb.

If I simply connect it, it does nothing.

If I start it in fastboot mode, it still does nothing.

If I pick the adb option from startup it tries to install drivers but finds nothing.

Any help is appreciated. thanks
[Fire Original Android Development] ggow:
- For updates to CM you just download the new ROM, flash and reboot :)

- Also I can confirm flashing todays openGapps nano worked for me via FlashFire
[Fire Original Android Development] codepilot:
yep, me too. okay so changes and settings remain when I don't wipe any partition and do the update?

Sounds OK for me. I think I have to use xda-developers more frequently now, too many non-stock devices in my use now ;)
[Fire Original Android Development] ggow:
- Yes all your data will remain intact when updating the ROM
[Fire Original Android Development] MAGICMAN516:
I got them when using my browser (I use UC Browser) in between pages it would flicker off and on as you described. And yes it does come back after reboots after a while. Very strange. I haven't tried the 12.22.15 update yet but I'll bet it's still there.
[Fire Original Android Development] ggow:
- Which stock version of FireOS were you running before installing CM-12.1?

- I'm just wondering whether it's related to the bootloader version in any way?
[Fire Original Android Development] ty_ger07:
I do not understand your question at all. What are you trying to do? Which app are you trying to install?

You don't need ADB to install an app. If it is just an APK, enable "install from unknown sources" in the settings -> developer options. Then, download the APK from a website online or copy over USB from your computer using standard media device transfer (no ADB needed) and then click the APK file in your file manager app and select install.
[Fire Original Android Development] MAGICMAN516:
It came with 5.0.1.
[Fire Original Android Development] ggow:
- I think mine came with 5.0.0

- When it arrived I switched in on - put it in air-plane mode checked it worked

- Had an initial play with various bits and had it in a drawer for ages until root was available

- I didn't let it upgrade.

- If we can can get some more data on this might be able draw a conclusion to this - maybe a separate thread in the general section for people experiencing the problem might be good
[Fire Original Android Development] Tibedabeeto:
Just got my Fire tablets and it had 5.1.1, just did the root method, and used flashfire to install CM12.1, Nano Gapps, and SU. Everything seemed to run perfectly.

My only question is, if amazon comes out with another update after 5.1.1 will it still get pushed automatically even though cm 12.1 is installed?
[Fire Original Android Development] abacabie:
No, as long as your not using stock fire os your fine.
[Fire Original Android Development] dureaux32:
Coming from early December build to 12/22 flashed fine and for those wondering, pico gapps has been the way to go- so far no issues across multiple flashes/builds

Also, for those Instagram users who enjoy the tablet real estate, you're going to have to side load the apk and other apps that are "not compatible with this version"

Is it just me, or is this build slightly slower than the earlier ones? probably a problem on my end, but feel things are a bit more "sticky" and latent than build I was coming from, I'll sit with it more tonight and tomorrow and decide for sure

Absolutely no complaints though thank you Devs so much! Happy holidays

-D
[Fire Original Android Development] sandman512:
[MENTION=5749760]ggow[/MENTION], Thanks!

Just want to make sure, just flash the latest, flash Su and then good to go?
[Fire Original Android Development] ggow:
- Yes, that'll work just fine :)
[Fire Original Android Development] NeeKoNeeKo:
Hi,

Noob question here.

I booted into TRWP using fastboot , i took a backup, wiped all caches and had copied the following files to sd card :

SuperSU-v2.46.zip

open_gapps-arm-5.1-pico-20151219.zip

2015-11-04-cm-12-recovery.img

I go to install - images

select the image and it will prompt me for boot or recovery

If i install into boot, it will get stuck in a loop rebooting

If I install into recovery and reboot, fire os loads??

What am I doing wrong?
[Fire Original Android Development] ty_ger07:
https://youtu.be/4dwguHoxTvo?t=9m15s

Do not click "Images...". That is your first mistake.