yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] sd_shadow:
http://xdaforums.com/showthread.php?t=3264224

[PSA] Information Regarding Firmware Version 5.1.1 A.K.A. ROOT
[Fire Original Android Development] :
i knew that u wasnt on 5.1.1 because twrp doesnt work on 5.1.1. i was in 5.1.1 and only option was flashire. but thanks anway
[Fire Original Android Development] fmc000:
Just curious: as you're already in CM, why don't you just dirty flash the new rom using twrp? Unless you can't have fastboot booting it, of course.
[Fire Original Android Development] qtotter:
Install just open gapps pico or nano or mini with FlashFire on Fire, and let it reboot. Then, install cm12.1/SuperSU/gapps with FlashFire.

Something in the install script does not always work on flashfire, and returns an error which aborts the whole install process. Somehow, installing a small variant of open gapps like pico fixes this issue. This only happens with flashfire, not with TWRP.
[Fire Original Android Development] DB126:
Poster stated he used flashfire; unlikely he has ability to boot twrp.
[Fire Original Android Development] fmc000:
That was what I meant with "Unless you can't have fastboot booting it, of course.". He did not mention explicitly the reason why he had chosen that method (and yes, I searched for all his previous posts before answering).
[Fire Original Android Development] DB126:
Curious - is there a reason one would opt for FlashFire over booting a custom recovery aside from being unaware of the latter? FlashFire seems to carry increased risk but is currently the preferred option for those unable to boot CWM, TWRP, etc on this device. Asking because when I see FlashFire I automatically assume fastboot booting is off the table.

Great to hear you searched before responding; so many repeat questions could be answered that way if others followed the practice.
[Fire Original Android Development] funkybrunk:
I've used flashfire to update the last 5 or so builds on 2 Fords @ 5.0.1. I could use TWRP, but its nice having an un-tethered solution, and knowing I can always boot into TWRP if anything really goes wrong.
[Fire Original Android Development] DB126:
Excellent - never thought of that (d'uh). Thank you!
[Fire Original Android Development] sd_shadow:
I also have been using FlashFire, works fine, just move wipes to top of the list
[Fire Original Android Development] BR3W CITY:
Wiped and reflashed 3x, once with the old version and again with the newest build. First two flashes still had the same process.acore error. (was doing just the regular wipe). Went back and did a complete wipe (including system/internal storage/etc), flashed the newest version...seems like it took, and the error hasn't appeared in the last 12 or so hours.
[Fire Original Android Development] andPS2:
i always used flashfire (even though i could boot into TWRP)

always did dirty flash (clear cache - clear dalvik)

i only recently found out that u have to change the order for the clear

all updates worked

i prefer updating without having to connect to a computer
[Fire Original Android Development] CrazyDelta:
Anyone notice that all the icons seem to be a bit blurry ?
[Fire Original Android Development] DB126:
Characteristic of a low res/quality panel - although better than most at this price point. Possible icons could be better optimized for 160-180 dpi but that would need to come from google or app developers imo.
[Fire Original Android Development] worm9110:
Is there a way to boot into TWRP recovery from CM? I know I can use the command "fastboot boot TWRP_Fire_2.8.7.0_adb.img" from the PC but I'm trying to get around it. I know the bootloader is locked and we can't go directly to TWRP from it.

Flashfire, only has backup, restore, flash firmware package, flash zip or OTA and wipe.
[Fire Original Android Development] niphoet:
No way right now, unfortunately.
[Fire Original Android Development] :
is there anyway booting up recovery using sd card?
[Fire Original Android Development] StackOverflow13:
No, sorry pal,. same restirictions re boot image
[Fire Original Android Development] Jileo:
Thanks ggow for your work :good:

It run very nicely on my brand new Fire.
[Fire Original Android Development] Webern:
Low res doesn't mean blurry. He's probably referring stuff that's not adapting to the screen size properly, or is being interpolated due to the non-square pixels.
[Fire Original Android Development] jedpublic:
Thank you all for the responses.

I have 3 devices. While all shipped with 5.0.1, I unknowingly allowed a 5.1.1 update to occur on one of the devices. While I am comfortable booting TWRP, like funybrunk, I like being able to do things untethered. And just to confirm, there is no way to have a custom recovery on the device and the only way to use TWRP is to temporarily fastboot into it tethered to a PC, right?

Sorry if I was unclear. FireOS is no longer running on my devices. I already was successful in installing 20151222-UNOFFICIAL-ford. Nonetheless, I'll try to flash just gapps first and see what happens.

Sorry for being so brief with my issue. Normally, I'm very verbose and detailed; however, I was practicing being succinct. :D Thanks for searching my extremely limited number of posts!

To be clear, I did move Wipe to the very top and flashed ROM, SU and gapps. Looks like someone had to do it multiple times in order for it to take. While I've tried the process three times, I'm open to trying again. I'll even try just flashing gapps only first and then try the ROM again. As a last resort, I'll tether and use TWRP... ugh!
[Fire Original Android Development] DB126:
Agreed - but the panel used by this device also has characteristics that degrade the visual experience such as a larger than usual separation between outer and inner layers which is typical on budget builds. Icon clarity is no match for the same app icons on a HDX. Some of this can be mitigated by the app developer (optimizing the mdpi variant) but there is only so far you can go on a sub-720p panel with asymmetrical pixels. I was interpreting "blurry" in a very general manner and (perhaps) inappropriately associating that with low res in casual conversation.

BTW - not bashing the 2015 in any way! It is a fantastic device for the price point and one that I increasingly grab for quick tasks and ad-hoc video viewing. Still prefer the HDX or something similar for more sustained use but that kid is 3-10x the price depending on model and has its own set of limitations (no SD slot, no OTG, tough to mod/easy to brick, no root {or custom roms} on 4th gen models, etc).

---------- Post added at 04:52 PM ---------- Previous post was at 04:44 PM ----------

Unfortunately, a custom recovery can not be flashed (installed permanently) as that would require an unlocked bootloader (or some way to forge the signature).
[Fire Original Android Development] qtotter:
Sorry, I meant "on Fire", not on "on FireOS." The auto correction added "OS", and I didn't notice that. Anyway, this happens when overwriting cm12.1 over cm12.1 with FlashFire.
[Fire Original Android Development] Neffy27:
So dirty flashing or clean flashing latest CM 12.1 build with FlashFire over Dec 22 build not recommended if originated from FireOS 5.1.1 ?

Update: sorry if my question seem noobish. The previous posts made it seem that it was best to revert to stock before updating to a newer build. I did revert but double verified the FF order and flashed latest build from 22Dec. Zero issues. Than you [MENTION=5749760]ggow[/MENTION] for your work. Next paycheck, donation your way.
[Fire Original Android Development] obsidience:
I just want to say thanks ggow - works great. Only issues I've seen are that the Google Now Launcher would not work but I ended up switching to the Apex Launcher anway. I'm wondering if it was because I installed the nano gapps.

Also - setting the pixel density to 213 crispens the screen some and looks good (thanks monza1412). To switch this, open up the File Manager and then switch your access mode to "Root Access Mode" in settings. From there you can navigate to /system/build.prop and change ro.sf.lcd_density line to 213 and reboot.
[Fire Original Android Development] DB126:
Be aware changing ro.sf.lcd_density can cause issues with some settings and modules that assume a particular (or at least standard) screen density. Note a different selection of DPI values are offered under settings depending on what value is specified for ro.sf.lcd_density. Not sure of the algorithm or whether the pick lists are standardized based on value range (tend to think not). Not a big deal as you can always flip it back.

In my case I lost expanded icons on the nav bar with ro.sf.lcd_density set to 213. Took me a few minutes to figure out what happened!! Back to 160 with a splash of font enlargement (115%) for aging eyes - mmm, better. :)
[Fire Original Android Development] fmc000:
CM12.1 natively supports changing the dpi resolution without messing with the build.prop file .
[Fire Original Android Development] DB126:
True - but only a finite number of options are available via the UI. Certainly plenty for most but tinkers hate limits. :) The DPI options presented in the CM UI change depending on what value is specified in ro.sf.lcd_density.

That said I am in no way advocating messing with build.prop! Even with a proper editor it's all to easy to mess up a critical value and render the device unbootable. Depending on what recovery options are available the no-boot could turn into a soft-brick. FireOS users in particular should be wary of editing build.prop as a native factory reset will not restore default values.
[Fire Original Android Development] FireBill:
Been running CM-12.1 installed using Flashfire from 5.1.1 for 24 hours now. Had to install play games via apk mirror and the only problem I noticed today is every time I restart the tablet I loose some icons, very strange
[Fire Original Android Development] r_azo_r:
Thanks ggow. Able to install CM 12.1 on Fire 5.1.1 using FlashFire. Only place where one needs to be careful is the order of actions in FlashFire. Make sure the order is Wipe, Flash ROM, Flash Gapps , SU etc (top to bottom) on the FlashFire screen before starting the process.
[Fire Original Android Development] kramalot:
Ditto, while the higher DPI does sold a bit clearer I found it sent some apps eg. Chrome into a smaller screen mode making them behave as though on a small screen phone. I assume they do some arithmetic dividing screen size by DPI or some such. Anyway I like my tabs in chrome :) so I too am happy to suffer slightly rougher text to get a more desktop like view (eBay in mobile mode? Yuk!).
[Fire Original Android Development] sandman512:
Just want to throw this out there. On the last several builds, I have been dirty flashing(no wipe etc...)via flash fire and experienced no issues. I flash build, gapps and SU all at once.
[Fire Original Android Development] DB126:
Same - although I do like (and recommend) wiping cache and dalvik as there is no data/personization loss and it only extends first boot by a couple minutes. Seen too much weirdness on other devices/roms traceable to crusty caches. Cheap insurance IMHO.
[Fire Original Android Development] sandman512:
Davey, I'l try that next time. Thanks much.
[Fire Original Android Development] Pix12:
Why is the boot logo too big?

---------- Post added at 01:14 PM ---------- Previous post was at 01:11 PM ----------

Yeah I Tried it without dragging the things in order and it said cm12 failed to flash. So i rebooted and my fire was back on fire os because it did not wipe it. Kudos to you! :good:
[Fire Original Android Development] Neffy27:
Thank you [MENTION=688006]sandman512[/MENTION] for throwing that out there. No one replied to my post in the previous page so just went ahead and did a clean flash.

FF kept moving wipe down when I added each zip file. Something for all to keep track of.

[MENTION=5488402]Davey126[/MENTION] I've made it a habit to do that on all my devices after flashing/updating a rom, wiping cache and dalvik. Good advice.

Thanks all!
[Fire Original Android Development] DB126:
Standard CM (cyanogenmod). You can change it with something like ROM Toolbox Lite. Includes a nice database of boot logos.
[Fire Original Android Development] patt2k:
using flashfire I get error that I can't flash on top of incompaptible data something like that. I did it first: Wipe,Flash Rom.Flash gApps

any ideas what's up?
[Fire Original Android Development] sd_shadow:
checking automount?
[Fire Original Android Development] patt2k:
I didn't do I have to? and for wipe do I have to select system as well? I un selected that and now fire booted but with no launcher so I have to do factory reset from settings I guess and do it again.
[Fire Original Android Development] sd_shadow:
may work with out auto-mount, but seems more likely to work if you select it.

first option should be wipe ( Select system, 3rd party, and Dalvik cache)
[Fire Original Android Development] patt2k:
Thanks I will play around it with it more later need to charge it :)
[Fire Original Android Development] sd_shadow:
yes, don't try to install with a low battery
[Fire Original Android Development] patt2k:
Now rom is booting! amazing :D thanks :D cheap tablet turned into decent browser and some movie playback :)
[Fire Original Android Development] FireBill:
Did you have internal memory checked on the wipe?
[Fire Original Android Development] patt2k:
already is working had to select auto mount

[MENTION=4267571]sd_shadow[/MENTION]

Is there any way to root it now on CM? Did not know i needed to select root in flashfire :D I just thought enabling dev options & root access would do it. This tablet is not even for me but for someone who will do just basic browsing and some streaming.

Just wanted to install adaway basically with root access.

If not then I assume only way would be to go back to Amazon firmware and do this all over again?

Thanks!
[Fire Original Android Development] sd_shadow:
yes you need to install supersu with FlashFire at the same time as installing the rom

you could try the 5.1.1 root method, but not sure that will work

safe option is to return to Stock
[Fire Original Android Development] Sumaech:
how to/updates

Okay I'm on 5.1.1 I have flash fire and stuff, but how do I install it with flash fire. Also does it have automatic updates or do I have to re flash it every time there is a update for it.

Thanks,
[Fire Original Android Development] sd_shadow:
How to Use FlashFire App to install a Rom
[Fire Original Android Development] Pix12:
XPosed will not work. Can you check the picture attached?
[Fire Original Android Development] patt2k:
You have to flash xposed .zip but I never actually used flash fire so I don't know if flashing xposed will work using flash fire. Try your luck :)
[Fire Original Android Development] DB126:
Works fine but like [MENTION=1659045]patt2k[/MENTION] I have only flashed via TWRP. Be sure to grab the proper zip (sdk22-arm) and latest v3 apk from here.
[Fire Original Android Development] Pix12:
Well At least i used flash fire for cm12. and i am going to try that.

---------- Post added at 12:23 PM ---------- Previous post was at 12:18 PM ----------

You just have to press plus and choose the ZIP and proably auto-mount it (I did it just in case)
[Fire Original Android Development] Signor Rossi:
[MENTION=5749760]ggow[/MENTION]

Latest build runs fine, dirty flasged

Let us know if there is anything we should look out for

Gesendet von meinem Amazon Fire Pad mit Tapatalk @ Cyanogenmod 12.1
[Fire Original Android Development] :
always worked for me from cm/rr/slimlp using flashfire. never had any issues.

---------- Post added at 05:58 PM ---------- Previous post was at 05:53 PM ----------

hi i was wondering can internal memory be expanded using sd card instead of moving apps auto to sd card. like for ex: if i wanted to add 15gb from sd card to internal is that possible?

---------- Post added at 06:07 PM ---------- Previous post was at 05:58 PM ----------

thats good to hear, im staying away from flashfire because i had issues with it exspecially flashing cm from clean install.
[Fire Original Android Development] sandman512:
[MENTION=270365]Composer[/MENTION],. Nope,.used flashfire for the last few updates. Dirty flashed.
[Fire Original Android Development] Franzferdinan51:
What does cm 12 have that slimLP doesn't is there any real difference in the 2 I've used cm before but not cm12 so just wondering the difference's before I try and switch

Sent from my SlimLP Kindle Fire
[Fire Original Android Development] DB126:
Not much, mostly window dressing. Both are Lollipop based and receive regular updates. I wouldn't switch unless you are looking for a specific look or feature (or just like to play).
[Fire Original Android Development] Franzferdinan51:
Thanks for your quick response with all the info I needed much appreciation

Sent from my SlimLP Kindle Fire
[Fire Original Android Development] sambucca1977:
server do download latest ROM is down?
[Fire Original Android Development] ggow:
- The whole of androidfilehost seems to be down for the majority of this morning
[Fire Original Android Development] DB126:
Back up
[Fire Original Android Development] ggow:
- I'm still trying to figure out Miracast / WiFi display functionality

- I'll release another maintenance build shortly
[Fire Original Android Development] ggow:
New Build is Up

- Dated 26 Jan 2016

- Change log on Post #2
[Fire Original Android Development] Pix12:
How do I update?
[Fire Original Android Development] DB126:
Reflash using the tool of your choice (twrp or flashfire). Wipe cache and dalvik for the best experience; leave data alone unless you want to start fresh. Strongly suggest including SuperSU and a gaaps package (nano/micro/mini) with the update. Many don't and are successful. That said, most update issues can be traced to skipping one or more of the above steps. There is no downside other than additional gathering and an extra few minutes on first boot.
[Fire Original Android Development] Pix12:
Okay so I wipe cache and flash update and gapps? Will this remove my apps?
[Fire Original Android Development] DB126:
No - user apps (for the most part) live in the data partition.
[Fire Original Android Development] Pix12:
Or app data?
[Fire Original Android Development] DB126:
Dude, just flash as suggested. You won't loose anything if you only wipe cache and dalvik. If worried don't wipe anything. If still worried don't update at all.
[Fire Original Android Development] DB126:
FYI - dirty update via FireFlash over 20160112 (prewiped cache/dalvik) including nano gaaps + SuperSu 2.5.2. No issues; happy camper. :)
[Fire Original Android Development] sandman512:
Same as Davey, no issues.
[Fire Original Android Development] coopmaster:
So wait do you have to fastboot this everytime or does it just boot up as so
[Fire Original Android Development] ggow:
- Once flashed the ROM will boot standalone
[Fire Original Android Development] coopmaster:
Awesome thank you
[Fire Original Android Development] Gibbothegreat:
**Bit off topic** Any news regarding CM13 for ford?
[Fire Original Android Development] fmc000:
I'm not a dev so I may well be wrong but I very much doubt that it's even possible to use a 6.x kernel with a locked bootloader.
[Fire Original Android Development] FredBloggs13:
I'm new to the whole CM scene, I'm running the early January version without any issues, but your recent changelogs are as good as Googles! They tell us very little!

Are these stability type changes and is there a need to update?

Any help appreciated!
[Fire Original Android Development] ggow:
- Wow, really?

- I'm speechless right now
[Fire Original Android Development] nickhaven:
Audio issues in some games still persist after the update.
[Fire Original Android Development] ps2lover:
how to install root and install TWRP ?
[Fire Original Android Development] blueberry.sky:
See the root & recovery threads.

Amazon Fire 5th Gen 2015 Root

twrp-recovery

recovery-cyanogen-recovery-2015-11-04
[Fire Original Android Development] sd_shadow:
don't need to root before installing cm12.1

cannot install twrp, only temp boot twrp
[Fire Original Android Development] theophile2:
I noticed that ambient light detection in Lux does not seem to work on CM 12.1 although it did on the Amazon firmware. I don't think the Fire has an ambient light detector so I believe Lux was using the front camera to measure the light levels. Maybe this is related to the camera bug?
[Fire Original Android Development] sandman512:
Ok, little help needed. Flashed into recovery, wiped data/factory reset. Went to FLASH ROM and then noticed there is NO option to flash anything. Screen says FASTBOOT Mode. Please help. Thanks.
[Fire Original Android Development] sd_shadow:
You watched the video?

[YOUTUBE]4dwguHoxTvo[/YOUTUBE]
[Fire Original Android Development] sandman512:
SD, I did not, I attempted to follow the directions in the OP.

Am I screwed?
[Fire Original Android Development] sd_shadow:
You need to copy files to tablet/sd card

and boot twrp

---------- Post added at 09:16 PM ---------- Previous post was at 09:16 PM ----------

Not even close
[Fire Original Android Development] sandman512:
Thanks, I have the files on my SD card, I booted (Power and Volume) and it just says fast boot.
[Fire Original Android Development] sd_shadow:
Yes, in Fastboot mode, you need to boot TWRP with

fastboot boot TWRP_Fire_2.8.7.0.img

see http://xdaforums.com/amazon-fire/orig-development/twrp-recovery-t3242548
[Fire Original Android Development] sandman512:
Strange, device just rebooted as new
[Fire Original Android Development] sd_shadow:
yes, likely a time limit for fastboot mode

---------- Post added at 09:39 PM ---------- Previous post was at 09:38 PM ----------

watch the cm12.1 video
[Fire Original Android Development] sandman512:
Ok, following video and I think I'm good. Whew. Thanks.

PS: For some reason, thought I could flash from recovery by Power and Volume down.

While I got you, I'm flashing fire-open-gapps-arm 5.1-pico, should this be ok?

Thanks again!!!
[Fire Original Android Development] sd_shadow:
that is fine, but I would just download newest from opengapps.org

there was an issue with gapps but it has been fixed

choose arm/5.1/pico
[Fire Original Android Development] Pyrb:
Thanks ggow, works great!

I do seem to have some wifi issues sometimes. After some time the system is not able to connect to the Internet, even though wifi is still connected. Disconnect and reconnect solves the issue. Does anybody experience something like this? Didn't have this on FireOS.
[Fire Original Android Development] Joshmccullough:
Hey all, quick SD card question here....I did a search and didn't find an answer, apologies if it's there and I just didn't see it.

How do we install apps to the SD card by default, so as to save the minuscule internal storage? The only phone I've had with an SD card option was my Evo 4G, and there were scripts to make the SD card really work well as the default app/data storage. Thanks!
[Fire Original Android Development] nowseewhatudid:
Can we try something like this just a thought I used it before but scared to tinker to most with my tabby http://xdaforums.com/showthread.php?t=2346389
[Fire Original Android Development] julianpaul:
I can't even see my sd card. Does CM have an issue reading exFat ?

Edit: TWRP sees the exFat sd card and installs CM etc just fine. It's only CM that can't see the sdcard.
[Fire Original Android Development] sandman512:
Thanks Sd, I am up and running. I thought that you can boot straight into recovery from the device itself(like a phone). Once I was booted in via my PC, i was good. Thanks again.
[Fire Original Android Development] sd_shadow:
That's the difference between flashing/installing the custom recovery and booting recovery which is temporary. Most locked bootloaders do not allow flashing of custom recoveries.

Sometimes a bootstrap is used to hijack the boot process, allowing a custom recovery to be used, but no one has posted a method to do that yet.