yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] ThatDragon:
I will post some of my experiences of how I finally managed to get this working after two very frustrating days of trying, to hopefully help some of you guys out.

First off: If you have a working custom rom installed already, think twice about updating. I wouldn't have done it if I knew what kind of work it would turn out to be.

I started out with a 5th Gen-2015 that originally came with stock firmware 5.1.2 on it. I had flashed it with some older version of Cyanogen OS a few years ago and wanted to update it to this one now.

At first I wasted time trying to get TRWP to boot using ADB, because I had forgotten that devices with 5.1.2 bootloader can't even boot that temporarily.

Then I tried flashing this ROM using Flashfire, which straight up bricked my device.

Using the Stock Recovery I wiped cache & data partition and then flashed the original Amazon 5.1.2 ROM through "apply update from ADB"

Now I had to get Root again, so I downloaded the newest version of Kingroot, only to find out that Flashfire does not work with Kingroot. To make things worse, the newer versions of Kingroot seem to be very hard to remove, while at the same time keeping root, thus making it near impossible to switch to SuperSU.

Tried using SuperSU-Me to convert from Kingroot to SuperSU, which failed.

I spent a lot of time trying around and re-flashed 5.1.2 several times during that.

The Solution was to root with the Supertool from Rootjunky, as it first installs an older version of Rootking, which is used to Root and is then automatically removed and replaced with SuperSU.

Next, I tried flashing this ROM & the newest version of GAPPS Pico using Flashfire, which was a success. However, for some reason Root was gone again.

So I had to flash Amazons 5.1.2 and obtain Root again, to be able to try again.

This time, besides using Flashfire to install this ROM & Gapps, I also used Flashfires Everoot "Inject SuperSU" option.

ROM was running fine and I had Root. However, Google Play always closed immediately each time I tried to start it. So I thought, fine, maybe GAPPS didn't install correctly, so I'll just flash them again, using Flashfire. Unfortunately Flashfire showed the exact same behaviour as Google Play, force closing instantly.

After hours of searching online, I found a post suggesting to force stop and disable the Google Play Services. After doing so, I was suddenly able to start Flashfire.

Using Flashfire, I installed GAPPS again. After doing so, Google Play finally worked properly.

Now, I also wanted to install Google Play Games, using the Google Play Store. However, it always failed to install with the Error -505.

More searching suggested downloading & installing an older version the APK manually, then updating it on the Google Play Store, which worked.

And that is why I will never attempt to update this Tablet again. Whats on it now, will stay on it until it goes to the trash.

I will also never buy a device without unlockable bootloader ever again - no matter how cheap.

Thanks to the ROM Author for trying to provide an updated OS for this device anyways.
[Fire Original Android Development] scooter1979:
For anyone stuck at this point (trying to set the date back to run FlashFire), I HIGHLY suggest using your phone or another tablet that you can easily set the date back via standard system settings. Purchase Pro that way (it's only a few bucks, well worth the price), then FF on your Fire will check for the purchase, see it, update, and run properly.

Coming from 5.3.1, the only issue I had was the GApps didn't seem to take on my initial FF flash from FireOS to Lineage. The OS loaded fine, but once in Lineage, I had to use FF to reflash GApps. Fortunately, I had the FF v58 apk already on my SD, so I could install from there. Everything was pretty much gold after that.

Thanks to everyone for their help.

---------- Post added at 01:39 PM ---------- Previous post was at 01:24 PM ----------

I had the same issue... Play Books installed fine, as did a couple other Play apps, but Games kept with the error.

I don't know if this was the real reason or not, but I registered my "unauthorized" device on Google's Developer ID page (due to their recent efforts to block services on what they consider bootleg OS's or whatever), waited a few, rebooted, then Games installed with no problem.

I would suggest, whether you're initially having problems with Play Services or not, registration of the device. Download Device ID, and use that to pull your GSF number to put in on the site. That'll (hopefully) avoid any future issues with Play.
[Fire Original Android Development] DB126:
Google Play Games

Google Play Games usually can not be installed directly from the Play Store on 'uncertified' devices. Been that way for years. Simply download/sideload from from APK Mirror (here).
[Fire Original Android Development] DragonFire1024:
My 8.9 worked fine with just installing the app from APK mirror. You still won't be able to update it via the play store either, but it does work.
[Fire Original Android Development] david_ker:
[MENTION=5749760]ggow[/MENTION], I've been using your ROMs on my Fire from day #1. Thank you! Did you push the sources somewhere? I can't find them in either your Bitbucket or Github account, where else could I look?

I'd like to rebuild with another patch included. Thanks
[Fire Original Android Development] ggow:
The sources are linked on the OP of this thread.
[Fire Original Android Development] DB126:
Keep in mind recent SuperSU builds (2.8x) have been problematic (bootloop) on certain devices - especially those running Lollipop based ROMs. Probably do not want to accept any Play Store updates for awhile. 2.82 SR1 is looking pretty good but isn't available outside the beta channel.

FWIW - I have lost some confidence in SuperSU given the latest debocal and the need for ChainFire to step in to clean up the mess. Pretty happy with the native root manager in this ROM and its predecessors. Sticking with that for now.
[Fire Original Android Development] t3chwizard:
Posted before refreshing page, please delete this post reply I made.

---------- Post added at 11:58 PM ---------- Previous post was at 11:45 PM ----------

I accidentally replied before seeing your reply asking what the benefits of using SuperSU were instead of the native SU. I suspect being that this ROM has backported security patches messing with the SU binary may weaken the security [MENTION=5749760]ggow[/MENTION] intended on providing with these patches, but I could be mistaken. This aside, SuperSU is closed source whereas Lineage isn't which is much more reassuring.
[Fire Original Android Development] eric93se:
ggow, can we please have a version without any gapps like traditional LOS. :)
[Fire Original Android Development] DB126:
This ROM does not include a GAaps package.
[Fire Original Android Development] eric93se:
thanks! So let me tell you what I did and hopfully you can see what went wrong.

Went from the old CM12.1 and used the latest flashify and installed, ROM + SU + OpenGapps Pico. Realized I didn't need/want Gapps, so I flashed again without The Gapps package and for some reason I still got Gapps after reboot. Things I did, check automount and check mount system for both ROM and SU. Also when SU was running I let it install the startup script to preserve root after flashing in the future.

Used the standard wipe options. So why did Gapps survive the flash?

---------- Post added at 01:05 AM ---------- Previous post was at 12:54 AM ----------

Can I add "cache partition" to flashify when wiping?

---------- Post added at 01:17 AM ---------- Previous post was at 01:05 AM ----------

Ok flashed again, included 'cache partiion' and the other systemless root partitions (I know there should be nothing there). I only flashed the ROM and there is no Gapps this time, I did not flash SuperSU but it did survive.
[Fire Original Android Development] DB126:
Interesting outcome; I would not have expected the previous GAaps install to survive a system partition wipe. Thanks for sharing.
[Fire Original Android Development] nirogu325:
Edit: Never mind.
[Fire Original Android Development] joienguyen:
I am on Fire OS 5.4.0.0 (Fire 7 5th generation), thus how do I install this Lineage OS rom?

- I have not known how I install twrp yet?

- Do I need to root my Fire?

- Or where do I get & how do I use Flashfire? Whether I have to root my Fire before?

Thank you!
[Fire Original Android Development] DB126:
You can't:

- a custom recovery can not be installed or booted on FireOS 5.1.x or above

- FireOS 5.4 can not be rooted at present

- one of the above is a prerequisite for the installation of a custom ROM

- FireOS 5.4.x.x can not be downgraded to a rootable version

- however, you can install the Google Play Store, remove access/visability to most preinstalled, block ads and take several other steps to improve the UX
[Fire Original Android Development] joienguyen:
Thank your replying.

Could you help me explaining a thing mentioned in the #1 of this thread:

By your quote, I understand that I can not root & install recovery rom.

But whether I can use Flashfire to install custom rom?

(Okie, can't use Flashfire because of requiring root before)

1 more thing, please help me:

I have just read another thread: https://xdaforums.com/amazon-fire/orig-development/twrp-recovery-t3242548

In the #1 he guided to install temporary recovery but it is in 2015

He notices that:

Do you know about this way? It's useful, isn't it?

Fire OS drains the battery very quickly, as a result I need to find anyway to install other rom.

Thank you.
[Fire Original Android Development] rwbonesy:
can't do custom recovery on newer firmware versions as i understand it
[Fire Original Android Development] DB126:
- a custom ROM can not be booted except with FireOS 5.0.x

- at present there is NO method to root or install a custom ROM on this device with FireOS 5.4

- you can remove most pre-installed apps which will help with battery drain

- see thread index for additional info/links: https://xdaforums.com/amazon-fire/general/index-amazon-fire-2015-t3210485

https://xdaforums.com/amazon-fire/general/amazon-fire-utility-tool-bloat-removal-t3641151
[Fire Original Android Development] t3chwizard:
If anyone wants to get a bit more bang for their buck with performance I've found using that "L Speed" tool helps a bit if you tinker around with it.
[Fire Original Android Development] Jrhotrod:
L Speed may seem like one of those scam Chinese apps, but actually made a noticeable difference with my old Sammy phone. Haven't tried it on this device, but now that you remind me, I'll install it and report back.
[Fire Original Android Development] DB126:
L Speed is a good starting point if unfamiliar with the various underlying mods (some are pretty exotic) and/or do not want to apply them yourself. I have this tool installed on a handful of devices primarly for ease of use. L Speed is also 'systemless' meaning all changes can be reverted with a simple reboot.

Like any tweaking app/tool what you change can have a significant impact on device performance and stability, both positive and negative. Tweak with care.
[Fire Original Android Development] t3chwizard:
I think it actually started here on XDA if I am not mistaken, so there's that too.
[Fire Original Android Development] t3chwizard:
The deep sleep on this ROM is incredible. It only lost like 5% when letting it sit without charge overnight for 8+ hours.
[Fire Original Android Development] Jrhotrod:
I only lose 5% over the span of 5 days. Quite incredible indeed.
[Fire Original Android Development] DB126:
Yep - Lineage is fussy about that. I have not found a solution but also have not looked hard as I use other methods/tools to disable apps. There are a ton of utilities in the Play Store that can facilitate this action (also known as freezing). If uncertain where to start give CCleaner a whirl.
[Fire Original Android Development] ipdev:
[MENTION=6051741]stkpxl[/MENTION]

Try force stop then disable. (Sometimes I had to clear app data also.)
[Fire Original Android Development] david_ker:
Ok, I was confused because the device on your Bitbucket files haven't changed since late 2016 (and I didn't find anything regarding Privacy Guard in those commits in March '18). So you're rebuilding LineageOS from the amami tree as-is plus the 2016 device files?
[Fire Original Android Development] ggow:
You need to select the cm-12.1 branch I think. The master branch is older

I'm not at home so can't check.
[Fire Original Android Development] zXiC:
With FlashFire, I've done all the steps and pushed Flash. All I get is a prompt that I accept then "Loading..." for over 15 minutes. This can't be right can it? How long does Loading take?
[Fire Original Android Development] DB126:
The loading portion normally takes only a few seconds. Obviously something isn't working. Flashfire is memory intensive; try clearing out background tasks before starting the app.
[Fire Original Android Development] zXiC:
I've cleared all the background tasks and nothing has changed. I really don't understand how this can happen.

I'm using the March 25 Lineage version with ARM 5.1 Nano from Fire OS 5.1.1 on FlashFire 0.58 and I tried the newest version too. Is there anything else to do?
[Fire Original Android Development] DB126:
In your shoes I would reload FireOS 5.1.1 and start over.
[Fire Original Android Development] zXiC:
Thanks, that worked!
[Fire Original Android Development] zXiC:
Is the a reason why my tablet lost Root? It's enabled in Dev options and seemed to work at the start but not anymore.

It's still enabled for Apps and ADB but Root Checker and anything that needs root confirms it's off. What can I do to turn it on?
[Fire Original Android Development] DB126:
Generally a reboot will fix it. If not you can try flashing SuperSU 2.82 SR5 (here) which works well on this platform. That said, better to stick with the integrated root solution if possible; one less thing to go wrong.
[Fire Original Android Development] zXiC:
How can I flash that when FlashFire needs root?

Unfortunately reboots don't work. Worse, 3/4 tablets had this issue. This sure is troublesome, is this something that happens often or am I just very unlucky?
[Fire Original Android Development] ipdev:
Kinda common in cm/Lineage roms using built in su.

Normally rebooting or toggling root access off then back on solves it. (Disable then Apps and ADB)

May have to reboot in-between toggling off and on, or reboot after toggling back on. Seems to depend on device and build.

If the common reboot/toggling dance doesn't work then the easiest would be to start fresh from fireOS again.

As for unlucky, I wish you had that market cornered ;)

Since you mentioned having some issues, and if you do reflash fireOS again, try these steps.

wipe cache partition

wipe data/factory reset

apply update from ADB

wipe cache partition

wipe data/factory reset

reboot system now

I know it seems redundant but, that is safest way of reloading fireOS that works for me.

When I skip the wipes I drag the same errors into fireOS that I am trying to get away from. No /sdcard or no keyboard, for example. :eek:

If you decide to go with SuperSu, make sure to put it in the flash list before GApps.
[Fire Original Android Development] ggow:
New Build is Up

- 04 May 2018

- Security patches up to April 2018 included
[Fire Original Android Development] dyonissos:
Charging issues

Not sure if this is the right topic but i have a charging problem on a 5th gen Fire tablet (ford) running on CM12.1 (20161122).

I don't know if it's related or not, but my daughter puked on it about a week ago. After that, it won't charge after CM boots up. The outlet, charger, cables are all fine. The tablet gets power when powered off, but i guess it doesn't support offline charging. As soon as it has enough power to boot up, it automatically powers on. Once CM boots up, it doesn't charge, and the battery discharge from 1% until it powers down and the cycle repeats on and on.

Do you guys have any idea what's causing this behavior? Is it software related somehow? I would upgrade it to lineage, but i need some battery in the first place.

Thank you!
[Fire Original Android Development] DB126:
Absolutely not software related. Most likely device is charging at very low rate that is below the power consumed when awake (screen on). Good chance the integrated USB port has some debris from recent, err, events that is preventing a good connection. Some of that 'goo' may have penetrated to the interior with similar electrical effects. Other less likely culprits are the cable and/or charger. Swap with known good substitutes to rule those out.

Worse case put a drop of rubbing alcohol on the end of the cable and gently insert/withdraw from port. Power should be off during this procedure; cable not plugged in to charger. Repeat until everything looks clean. Make sure everything is dry before testing. If still no joy internal damage is likely. Good luck.
[Fire Original Android Development] DB126:
No problem updating via TWRP. But that's to be expected. Those using FlashFire should proceed with caution (status quo).

For awareness, the following post is from the author of FlashFire. Interpret it as you wish. Given the enormous complexities of FlashFire my take is it will not be maintained.

https://plus.google.com/+Chainfire/posts/ZVDG2SnmgM5

Related: https://www.xda-developers.com/chainfire-ending-development-root-apps/
[Fire Original Android Development] ipdev:
I can not say for sure on updating. I can guess though.

Clean flash from fireOS via FlashFire 0.73 worked fine.
[Fire Original Android Development] DB126:
Yep - that path has been fairly reliable based on posted reports. Might be an interesting exercise to see if a FlashFire data (only) partition backup can be successfully restored after rebuilding from FireOS. Might be the long way to a 'dirty' update.
[Fire Original Android Development] eric93se:
Just wanted to report a successful flash of the May ROM (despite all the warnings lol :) ). Tablet had the december 2017 ROM loaded. Fully charged the tablet, set SElinux to permissive, rolled the tablets internal clock to a 2017 date, installed latest FireFlash, closed all other programs running, turned off wifi, selected the full wipe and both caches, selected the rom to flash and ticked both options, also flashed xposed installer (worked). Flash process was surprisingly fast, only a couple minutes. Thank you all for your efforts, this still a good little tablet!

I've been using a LG V521 tablet, you should all check it out, it's cheap and the screen is excellent, the only draw back is the cameras are total junk. Also since it has a sim card there is no way to turn off that from running in the background within LOS, so I have to manually remove a lot of programs. If I don't the battery will last only ~2days, with the SIM radios stopped it can last all week! GPS works great on this tablet.

---------- Post added at 03:46 PM ---------- Previous post was at 03:44 PM ----------

Also just to mention the cores appear to be under better control. XTD kernel Aduitor (v6) only shows 4 cores but they are plugging and dropping down to 2 cores, so I suspect battery life will be better?
[Fire Original Android Development] DB126:
None of the stock kernel governors support unicore. Not sure if that's a SOC limitation or lack of kernel sophistication.

V521 is a nice rig. Also partial to 3rd gen Amazon HDX which shares many of the same characteristics at a lower price point.
[Fire Original Android Development] DragonFire1024:
Love my 8.9. probably the best of all my Amazon devices. However the HD 10 is quickly making it's way to being tied.
[Fire Original Android Development] Neffy27:
Anybody randomly encounter their root disabled under dev options and USB debugging is now greyed out.
[Fire Original Android Development] Neffy27:
Also, just dirty flashed May build from March 25 build with FF Pro .73, no issues. On my last post, a reboot made privacy root return. USB debugging toggle is still greyed out and not functioning.
[Fire Original Android Development] jeanett:
Hello, I need a little help here. Please, I have a Amazon Kindle Fire 7th tablet with linage (it was installed a long time ago). The case was reading the wikipedia and my screen is black. I think this brick is some way to make my tablet work. again.

Things I have tried:

Remove the battery cable for a few seconds and reconnect it (No results)

Press for a time button of power (Without results)

Keep pressing power button and low volume (without result)

at all times the screen is black, when connecting to the pc you hear a sound but it does nothing else thanks for my English because I speak Spanish
[Fire Original Android Development] DB126:
I capitulated a few months ago and started including SuperSU 2.82 SR5 with each flash. So far no issues.

---------- Post added at 02:33 AM ---------- Previous post was at 02:32 AM ----------

Sounds like a hardware failure.
[Fire Original Android Development] jeanett:
Hi, thank you for answer me,

I do not think the hardware is broken because when I connect the tablet to windows / windows it makes a hardware detection sound and says it is in com 4 conected but the tablet does not turn on the screen and the windows explorer not shows the tablet. Is as if it were in mode brick

there is some way to get out of brick mode the tablet previously had linage fuincionando thanks
[Fire Original Android Development] ipdev:
I have noticed that updates, recently on some devices, may leave "Developer options" enabled but not active. Make sure Developer options are turned on.
[Fire Original Android Development] ipdev:
[MENTION=8568839]jeanett[/MENTION]

I have a fire 8 in the same condition. In my case it is a HARD BRICK.
[Fire Original Android Development] DB126:
A hardware detection indication is largely unrelated to device recoverability
[Fire Original Android Development] srnoth:
[MENTION=5749760]ggow[/MENTION] I know there have been a lot of people complaining about all the trouble they get into running these monthly updates through Flashfire. Just wanted to take the time to say that for those of us who can use the TWRP method, these are greatly appreciated and work perfectly every time. No problems usually = no need to post in this thread lol. Thank you for keeping my crappy $40 tablet still relevant and secure!
[Fire Original Android Development] L551:
So, attempted to install via Flashfire, and ended up stuck at the Amazon logo. I successfully sideloaded the 5.3.1 FireOS back on to get me out of the loop, but now I need to re-root so I can use Flashfire again. How the heck do you root this thing now?

I've tried the PC kingroot but after a few attempts, it just says there's no root available and won't try any more.

Edit2: Kingroot finally worked, but now I need to replace Kingroot with SuperSU for Flashfire to work. Actually, I need to do that AND change the system date/time to get around the timebomb. I also cannot connect to the internet, as then the tablet will download the unrootable OS and update automatically. How can I do this WITHOUT any wifi for the tablet? Supersu-me seems to be used in the past but it's ONLY on the play store now, so that's no-go.
[Fire Original Android Development] luk2009:
https://youtu.be/dh8ndFo8vYQ

Look at this video, maybe can help you
[Fire Original Android Development] L551:
I have 5.3.1, not 5.1.3.
[Fire Original Android Development] luk2009:
Look at the 6:16 minute and if you have patience, see how it installs supersu a little earlier. I think supertool works with version 5.3.1
[Fire Original Android Development] DragonFire1024:
I can confirm it does indeed work on 5.3.1.
[Fire Original Android Development] L551:
I tried the super tool, but it failed to install SuperSU. It got as far as deleting Kingroot but then the tool just had a bunch of errors and froze. Now I have to start again but the Kingroot app it installs wants an internet connection. If I do, it'll update FireOS. How do I do this without internet?