yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] platypoid:
Thanks for the help .

So here is what I did - flashed Lineage 12/17/17 with gapps nano and it worked . But .... I didn't have any of the google stuff like playstore , gmail, etc so I tried apk mirror to put in playstore but that didn't seem to work. So I got idea to reflash again from scratch but use gapps micro . This did not work out so well and locked me up on the Amazon screen so I had to restore 5.12 again and reroot and run through all the Supertool options like block ota, install playstore, etc. So I put in Flashfire .73 from playstore .

But this time I used Flashfire to restore backup I had made in Cyanogenmod 12/1/2016 version from before I started all this . Flashed and it went all black but left it go awhile and restarted with ADB reboot and - here I am back to pretty much where I had started at . Lot of messing around for not much gain though I learned a few new things along the way. I will just stick with Cyanogenmod - always worked fine for what I use it for.

I guess the " If it's not broke , don't fix it " should apply to me and I don't need to try out Lineage - not sure what it would have gained for me anyway .

Thanks again for the help !
[Fire Original Android Development] DB126:
Thanks for the update. I suspect a procedural error as Lineage has been a reliable install for most. If you're up for it suggest the following:

- reconfigure CM 12.1 to your liking then add FlashFire 0.73 from the Play Store

- use FlashFire to backup that config

- snag the latest Lineage 12.1 and OpenGAaps nano package (arm/5.1)

- configure FlashFire as indicated in the Lineage OP for a fresh install; do NOT wipe data partition (wipe should encompass system, dalvik and cache)

- be sure to move wipe operation to top of queue; then execute
[Fire Original Android Development] platypoid:
that is what I did - flashed Lineage and Nano and it worked and loaded. But then how do you get the play store and other google apps on it once loaded up with Lineage ? Nano was pretty bare bones .
[Fire Original Android Development] DB126:
Play Store is included in nano. If it wasn't exposed in the Lineage launcher then GApps didn't install or didn't install properly. I have seen that happen on occasion with CM based ROMs from which Lineage was derived. Usually happens when system is booted before a GAaps package is installed. Regardless, reflashing system + GAaps (same TWRP/FF session...include a system wipe) usually fixes it.
[Fire Original Android Development] ipdev:
Ran into a problem with a dirty flash. Got stuck on boot. (amazon screen)

FlashFire showed an error but, I can not get the log.

(Currently reloading fireOS. I have a 5.1.1 device, second easiest to root.)

Probably my error. ;)

Cheers and thanks for the update. :)
[Fire Original Android Development] DB126:
Interesting. If problem reoccurs please check (enable) "Mount /System Read/Write" after selecting Lineage ROM zip. Shouldn't need this but read/write access is definitely required to insure everything goes in smoothly. There is no disadvantage selecting this option when flashing custom ROMs that are not OTA capable. Leave all other FF options as-is.
[Fire Original Android Development] melvinaury:
Just write second case, stuck on Amazon Screen. I also see the error, but not take note, I remember that indicate error mounting, something..

Also, I try to had 2 users of the tab, but the second user don't had root access. How I configure for root on other users.

---------- Post added at 11:51 PM ---------- Previous post was at 11:39 PM ----------

I don't remember what version of Fire OS was on the tablet was installed before installing Lineage. What is the safe version to install to restore the tab? For what I read the safest version to install are version 5.3.1.0
[Fire Original Android Development] DB126:
Yep - if uncertain reload FireOS 5.3.1.0. Be sure to maintain network isolation (except during the first 30-60 sec of KingRoot runs) as any successfully downloaded/processed OTA update will bring FireOS to a level that can't be rooted at present.

---------- Post added at 06:17 AM ---------- Previous post was at 05:47 AM ----------

A couple folks have reported trouble loading this build via FlashFire (hangs on boot). I have not tested and won't be able to for 12-24 hours. Might want to hold off installing/updating until sorted. Might be nothing.
[Fire Original Android Development] ggow:
Unsure as to why this is happening. I tested flashing via flashfire 0.73, using flashing instructions in OP. Can someone provide any log files, so I can take a look?
[Fire Original Android Development] DB126:
Identical failure (hang at gray Amazon logo) attempting to update 20171217 via FlashFire 0.73 following OP *exactly* for updating from a previous Lineage build. Received an unmount error at FF conclusion but couldn't read the rest before screen cleared. Restoring previous build via TWRP and will retry again later today. Hopefully FF left a log behind. I did have adb access during hang (suggesting progression beyond bootloader) which should allow pulling logs on next attempt. Sorry for delay...RL calls.
[Fire Original Android Development] ggow:
I just tried flashing 3 times and it worked each time. Attached is the lastlog.

It'll be interesting to see what the differences are to yours.
[Fire Original Android Development] Kramar111:
[MENTION=5749760]ggow[/MENTION]

Maybe error occur when .zip on microSD
[Fire Original Android Development] ggow:
Could be, let's see what Davey126 and maybe some other guys who had the problem say.

Did you flash the update using Flashfire?
[Fire Original Android Development] Kramar111:
No, it's from previous experience.
[Fire Original Android Development] Reynald0:
I flashed the latest build using twrp, went fine;

Two things I noticed, but not exclusively of latest builds are:

- Cannot change account image with a image;

- The WiFi Network name keep the name "Unavailable".
[Fire Original Android Development] DB126:
She's a nogo w/FlashFire 0.73. Log attached. Also tried the following with same outcome:

- source image on internal storage

- mount /system read/write

- clean flash (system wipe)

Goes in fine with TWRP but looses all settings (behaves like a clean install). Bit of a head scratcher. Probably should pull the last build as fall out is a bit brutal for those w/o access to a custom recovery (identify/reload/reroot FireOS while dodging OTA updates).
[Fire Original Android Development] ggow:
December release put on hold

Your log shows a boat load of errors, it's weird because all I did for this release was apply the December Security patches.

Sorry to anyone that experienced problems with this release. I have pulled the 17 December Release. Will get it figured out and then ask for some help testing. I still can't replicate the issue here.
[Fire Original Android Development] DB126:
For giggles-n-grins tried reapplying 20170928 update from FlashFire with same result. I did

not

use FlashFire when this build was initially installed so can't say if the problem was present then. Most likely not as there were no widespread reports of problems. What's most interesting is the issue persists when /system is wiped. Next attempt will be a full device wipe; will post results shortly.
[Fire Original Android Development] ggow:
Just had a look back over the changes I made and can confirm that only the security patches were applied and nothing else.

I also checked against the Fire Nexus ROM code updates and they are a match in terms of the changes I made for security updates. Will need to think this one through a bit more.
[Fire Original Android Development] DB126:
Some progress. 20171217 installed fine over 20170928 w/FlashFire (no wipes) after ejecting SD card. That card had a dual partition for symbolic linking (ie: transparently migrating apps/data to SD card). Never presented an issue before. Obviously something has changed. Not only my config but likely others too. Reinserting SD card and rebooting after LOS update reestablished all symbolic links.

Unfortunately, running out of bandwidth to do more testing today. At least there is a solution for those stuck with no installation options after destroying their existing LOS instance. Of course that never happens as everyone makes backups ....
[Fire Original Android Development] melvinaury:
I was able to install the new update, after factory restore. I install the ROM from external sd card. Maybe it had something to donwith upgrading. I use the same file the second time without a problem.
[Fire Original Android Development] JKSurf:
No problem here with 12/17 update.
[Fire Original Android Development] DB126:
Made the call prematurely: device was unstable, some Google properties would not launch or badly lagged...just a mess. Tried dirty flashing again in TWRP w/o SD card mounted; similar result. Ultimately restored 20170928 build. Have to give more thought to whether I want to mess with this minor update. Really do not want to do a full wipe and clean install/reconfig for a few security patches. As previously stated wiping only the system/dalvik/cache partitions didn't do it. Probably have to go after Internal Storage to obliterate lingering detritus that is interfering with install scripts.
[Fire Original Android Development] ldeveraux:
I also have major problems with this build. Dirty flashed over the previous, rooted with SuperSU, keeps shutting off after a few minutes. I'm going to try to dirty flash the previous version, hopefully that will fix it?
[Fire Original Android Development] DB126:
That didn't work for me; hopefully you have better luck. Ultimately you may have to do a full rebuild either by sideloading FireOS or wiping all partitions, including Internal Storage, via FlashFire. If you go the latter route be sure to backup important personal content in advance and have all files needed for the rebuild (minimum LOS and GApps) on the SD card. Probably obvious but restated for clarity: if the FlashFire operation fails (for whatever reason) following the wipes you will need to reload/sideload FireOS and start over.
[Fire Original Android Development] ldeveraux:
I don't know for sure how long it stays on for, but doubtful it's long enough for Flashfire to work. I still have an old bootloader, so I can just boot into TWRP and do it that way.

Consequently (and off topic), can we install other launchers on top of FireOS yet? I'm not terribly thrilled with my device's performance under any of the custom ROMS on XDA...
[Fire Original Android Development] DB126:
There's a thread in the general section that addresses installing an alternative launcher (usually Nova) on FireOS which mostly works but is not a 100% clean solution.

If displeased with overall performance on Lineage/Nexus you will likey find FireOS revolting which runs far more background processes on this limited resource device. There are various tweaks to improve memory management but none are 1-click solutions.

FWIW - my 'tuned' Fire (currently on LOS) is fairly responsive and rarely lags under modest workloads. Push a little harder and things go to hell pretty quickly. Nature of a budget device where everything is a compromise. Overall better than anything else in the price range if purchased on promotion.
[Fire Original Android Development] ggow:
So, I spent a little time today which was fruitless:

Still cannot replicate the issue seen by some flashing the 17 DEC build, It looks more likely to be an issue outside the ROM build. The root cause of being stuck at the amazon logo is the flashing of the ROM, failing.

[MENTION=5488402]Davey126[/MENTION], when you have a free moment, for the FlashFire application only - try wiping application info, data, cache and delete any config info for Flashfire (don't know if there is any such thing) from the internal/microsd storage and retry the dirty flash process?
[Fire Original Android Development] Deuces:
I clean flashed the 12-17 version through TWRP a couple days ago and have had no problems
[Fire Original Android Development] DB126:
[MENTION=5749760]ggow[/MENTION] - thanks for your ongoing efforts and having to deal with the unfortunate distractions associated with what should have been a non-eventful build. For now let's just assume it's my device as more voices are chiming in indicating a successful update. Particularly with clean flashes.

Time is at a premium ATM with the pending holidays and other irons in the fire. Preparation for a semi-dirty refresh in FlashFire (obliterate everything except '/data') is rather time consuming if done correctly which means no ADB/TWRP access. I already have more than a few hours investing in this iteration as I'm sure you do as well. Hopefully additional data points from the community will provide a guiding light.

N.B. Gut feel suggests orphaned/redundant symbolic links and/or mount points are the root cause of FlashFire failures on my device. I attempted a manual clean-up but the data (.d scripts) reside in areas that I don't often travel. I will likely do a complete rebuild in TWRP which is time efficient compared to FlashFire.
[Fire Original Android Development] ipdev:
I am inclined to agree.

Keep in mind I kinda do things my own way but, it's been working for me. ;) Like I said in my prior post, probably a fault on my end. Be it hardware or procedure. I was not looking to blame the last build or start a war on flashing errors. I honestly just wanted to say thank you for all the resent updates. :)

As mentioned, after I got stuck, I sideloaded fireOS. (Took longer than I remember. - Normally I just restore my original rooted fireOS backup with ff.)

I rooted, installed flashfire and tried again. Wow at lease it booted. Very broken but at least somewhat usable. (No root, SuperSU did NOT install.) No lock screen, no developer options, (list goes on.)

ADB was enabled, so I could use adb to boot into recovery.

(Somewhere along the way I lost the hardware key combo again. Only get fastboot with power and volume keys. Wish we had fastboot oem recovery on this device.)

Sideloaded fireOS again.

The story repeats a few times, different setup, files, etc.. So I'll just skip to the end.

I found a screenshot from the 928 build and used the exact same setup and files. This time it booted fine and seems to be no problems. (Until you look at the lastlog. WOW how did this even boot?) WiFi gave me a few issues but, a reboot fix that.

This was the last time I did a clean install, using my ff backup, and have only dirty flashed from there. (Looks like I m ay have done another clean install in November, not sure though.)

This problem may have existed, for me at least, and gone unnoticed. Since everything seemed to be working I never looked at the log files. (If they were the same from then to now? :confused: )

Traditional I only look at log files if I have a problem, su updates, major updates, or files I'm not quite sure on. Laziness on my part. :p

I applaud all who are willing to help, as it seems I may not be the only one with this problem. (Big thanks to [MENTION=5488402]Davey126[/MENTION] for all you have found.)

Cheers. :) (And a little early Merry Christmas )

Attached.

lastlogs - Maybe someone will notice something. (First clean flash and duplicate 928build flash)

ff screenshot from original 928 build flash (I flash from external SD card.)

filelist - May attach latter.
[Fire Original Android Development] ldeveraux:
In the end, I had to wipe and clean install to get it working. I went ahead and installed the September build, though I really should have done the latest.
[Fire Original Android Development] DB126:
FWIW - Log shows some of the same mount errors that I encountered which will be fatal for almost any flash operation regardless of the tool used. Unlike TWRP FlashFire continues on which probably isn't the best choice unless preceded by successful wipes which could leave the device in an unbootable state.

It's a curiosity why FF claims the "Device or resource is busy" which it should not be. FF only has a pre/forced mount option for the /system partition; errors are occurring on all partitions including /cache and /data. I wonder if glitch was introduced with FF 0.7x that is only now becoming apparent. Or it may be related to the way partitions are remounted by some 'optimization' tools such as L Speed. Those methods could be preventing FF from carrying out its own mounts.
[Fire Original Android Development] ggow:
Now that you have a clean setup you could try flashing the 17 DEC build.

I have been dirty flashing a ton load of dev and release builds and not experienced this.

I have my tablet on the new build is is still rock solid.
[Fire Original Android Development] ldeveraux:
Yeah I could try that, though I have restored my apps from TB already. I don't know how that might affect it. I've got the time though ;)

EDIT: Dirty flashed the December build after restoring my apps. Wifi checks in and out constantly making it difficult to use. Everything powers on correctly, etc but I don't know about this...
[Fire Original Android Development] el_charlie:
I need some help.

I can't install this ROM. I did the clean install process and ended in amazon logo.

I sideloaded FireOS 5.1.1 again and restarted the process and ended with only the ROM Flashed. No gapps.

Did the procedure again from within LOS and amazon logo again.

Any tips?

EDIT:

It was a gapps-config issue. The latest gapps are bigger and there wasn't enough space on system.

However, I must inform that trying to do a clean install from within the latest lineage OS results in a soft brick. Flashfire does the wipe but can't install the rom's zip because it can't mount /system. Interesting enough, the gapps package does install correctly but, because there's no ROM, the tablet doesn't boot.

Cheers!

EDIT2: MERRY CHRISTMAS!!!!!!
[Fire Original Android Development] razers7t8:
Can you make a lineage ROM for the 2017 fire HD 10? We have root for it now.
[Fire Original Android Development] ggow:
I haven't got that device, so not able to investigate this.
[Fire Original Android Development] DB126:
FWIW - I experienced something similar although root cause remains undiagnosed and could well be a device config issue (ie: my fault). Interesting you also had this happen.
[Fire Original Android Development] el_charlie:
Yeah, I did all the steps in OP for a clean flash and got the same error doing the procedure on CM12.1 and then on this build (dec 02) because I wanted to reflash everything. On both cases, the LOS zip failed to install immediately and the gapps zip installed fine.
[Fire Original Android Development] ipdev:
Delete.

Edit:

Not sure if anyone mentioned this command before. Once I found this device supported the command, it helped me a lot in testing. :D

fastboot oem reboot-recovery

Not sure if it works past fireOS 5.1.1 (bootloader) version: 0.5
[Fire Original Android Development] ggow:
Turns out someone is already maintaining an up to date security patch lineage-12.1 rom. The next release of the ROM for Amazon Fire will be rebased on this:

https://xdaforums.com/sony-xperia-z...neageos-12-1-z1c-current-sec-patches-t3614936

This will ease the burden and enable me to focus on fixes and general maintenance for the future.
[Fire Original Android Development] DB126:
Can't speak for others but for me this is some of the best news of the day on XDA. Not for any specific deliverable but for the reduction of time/effort on your part. Without [MENTION=5749760]ggow[/MENTION] several Amazon Fire devices across multiple generations would have far fewer (in some cases no) custom ROMs and associated support. Anything that helps to maximize "real life" is a winner in my book.
[Fire Original Android Development] Khaeroth:
Hi, I flashed my kindle from the Nexus rom to this flawlessly.

I downloaded the first (the oldest one) version of the LineageOS by accident and I want to update, now, it seems I'm not a root user so FlashFire doesn't work.

I checked the developer options and I checked the root one but it doesn't seem to work. How do I root now?

I tried to download SuperSU and even use the Amazon SuperTool but it doesnt work, I guess it only works with the stock rom.

Any help?
[Fire Original Android Development] DB126:
You need to reboot after enabling root under developer options. If that fails (it should not) you can try installing SuperSU from the Play Store. However, that approach is unlikely to work without the flashable companion component which you obviously can't install w/o Flashify. Bit of a catch 22. In that case you'll need to sideload FireOS (same version that was on the device prior to installing Nexus) and start over.
[Fire Original Android Development] Khaeroth:
Thanks for your reply!

Let me see if I get it right... I have to enter in the recovery mode, then to "apply update from ADB" and push the Amazon stock rom through it?

I just read that the bootloader is locked on the Fire 5.1.1 and above. Won't I brick my device?

The SuperSU says "binary occupied" when I open it, btw.
[Fire Original Android Development] DB126:
Don't confuse the underlying Android build (5.1.1) with FireOS version. If you do not recall the FireOS version previously installed go with 5.3.1 to avoid a potential brick. Also be sure to maintain network isolation (WiFi OFF!) except for ~15-30 sec at the start of each KingRoot run as FireOS will attempt to update itself almost immediately. If successful you will permanently loose the ability to root the tablet and/or install a custom ROM.

FWIW - the "binary occupied" message is symptomatic of leftover SuperSU components...likely from the prior install of Nexus. It's a tough nut to crack even for those who have an unlocked bootloader and/or bootable custom recovery. Often a full device wipe is needed to resolve the problem. In your case sideloading FireOS will effectively wipe the device.
[Fire Original Android Development] Khaeroth:
I always had 5.1.1 and never went beyond it; so it's safe to install by sideload the FireOS 5.1.1?

Sorry I'm kinda confused.
[Fire Original Android Development] DB126:
If you know for sure that FireOS (not Android) never advanced past version 5.1.1 then yes - you can safely sideload FireOS 5.1.1. If not 100% certain go with 5.3.1.
[Fire Original Android Development] Khaeroth:
I'm 99% sure I had 5.1.1.

I did buy the device on december 2015 and I blocked the OTA updates since day 1.

But just to be sure, there is no way to unbrick, right?

Or what if I sideload to FireOS and I'm still can't be a root user?

Also, what happens if I wipe the data from the recovery?

Thanks for your replies!
[Fire Original Android Development] DB126:
Your call on the version of FireOS that gets sideloaded. Just know some rollbacks are invalid and will brick the device (non-recoverable). I believe previous posts covered the bases.

You can try to wipe data from the stock recovery menu but that is unlikely to resolve the root issue you are experiencing. But there is no harm in doing so and it won't put you in a worse place (in terms of app/data retention) than sideloading FireOS.
[Fire Original Android Development] el_charlie:
This should be a tip for new users: they should keep their original and rootable FireOS build in hand to roll back in case things go wrong. I know that there are no new users with a rootable FireOS but that should be a great tip nonetheless.

I have my 5.1.1 build at hand and it's awesome because with the SuperTool I can root it with SuperSU without any network connection (I don't even bother setting up my Wi-Fi). This way I installed the latest Lineage .zip.

Going back to the issue of not mounting /system to flash a new build, do we need to uncheck the automount option in Flashfire?

Cheers!
[Fire Original Android Development] DB126:
Good tip.

As for FlashFire 'Auto-mount' should NEVER be checked on this device. The option 'Mount /system read/write' is optional; I opt to check it. Unfortunately, it did not make a difference for the issue you reference when I experienced something similar with the latest build. YMMV.
[Fire Original Android Development] DragonFire1024:
Could be something to do with FlashFire, related to some 5.1.1 devices. I have a Galaxy J1 on 5.1.1 that won't work with the latest version.