yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] Capsaicin88:
I'll be pray for it lol
[Fire Original Android Development] xenokc:
Working well for me and I did finally get root to work fine. The included camera app did not work for me at first. I downloaded Silent Camera (by Peace) and it works fine, then included cam app worked (maybe it was a reboot, not sure). Everything else looks to be working. Feels snappier than AOSP but could be the fresh install.
[Fire Original Android Development] Jrhotrod:
Well, I finally figured out a guaranteed working method to replace the built-in Lineage SU binary with SuperSU:

1. Download SuperSU 2.79 apk.

2. Ensure that root access is enabled for apps and ADB in developer options.

3. Reboot after enabling the root access

4. Install the SuperSU APK and update the Su binary with the normal option.

5. Disable root access in developer options and reboot
[Fire Original Android Development] Hallo32:
On 1/30 you can simple reenable root.
[Fire Original Android Development] ggow:
And remember to reboot after enabling root so that it can take effect.
[Fire Original Android Development] t3chwizard:
I just flashed using TWRP after wiping system and now it works
[Fire Original Android Development] DB126:
Yep - never been an issue when flashed via TWRP. Recent update and initial loss of root issues appear to be associated with FlashFire.
[Fire Original Android Development] t3chwizard:
Hmm it's telling me Android system is corrupted or something and that I need to factory reset when I boot it up.

I'm going back to the last December build since I made a TWRP backup with FlashFire.
[Fire Original Android Development] DB126:
[MENTION=5749760]ggow[/MENTION] cautioned a full wipe (including apps/data) might be needed with 2018 builds due to a change in source. I was able to dirty update but that success may not be representative.
[Fire Original Android Development] akz1x1:
Clean flash or dirty?
[Fire Original Android Development] akz1x1:
Looks like I fall to the unlucky category.

Had no luck flashing the new build on flash fire.

Got error saying unmount of /system failed. No such volume.

Mount : failed to mount /dev/block/platform/mtk-msdc.0 by name /system at /system : device or resource busy

Symlinks: some symlinks failed.

Used latest flashfire.

Now stuck at Amazon logo.

I haven't flashed stock in a long time and don't remember from which version I am coming from.

Can anyone find the link for flashing stock through adb and re flashing this rom.
[Fire Original Android Development] DB126:
FireOS can be reinstalled via the stock recovery menu; you won't be able to use ADB sideload directly. Follow the video guidance from this thread making sure to substitute build 5.3.1 for the one referenced in the video. When initializing the devices do not allow a WiFi connection as it will quickly update to an unrootable version of FireOS (anything above 5.3.1). Then use the SuperTool to root and prepare your device for a custom ROM should you choose to go that direction again. Ask questions along the way as needed.
[Fire Original Android Development] Timballist0:
Dirty flash. Everything works fine for me.
[Fire Original Android Development] prisoner1969:
What is the average battery life on this? I used to get great standby time. Now I'm getting maybe 2 days of standby time. If I have it at full charge then not use the device, it's dead a couple of days later. I used to get over a week on standby.
[Fire Original Android Development] DB126:
A week plus of standby endurance is typical on the latest and past builds. Either the battery is failing (unlikely) or you have an app/service running in the background and/or waking the device periodically. Use a monitoring tool like BBS or GSAM to track down the culprit(s).
[Fire Original Android Development] DragonFire1024:
Ok I looked and looked. I. Interested in trying other romz, older. I found a few, ressurection remix for example. So I downloaded the room, gapps, did a wipe of system, dalvik, cache, but can't get any ROMs to load. After flashing, I get stuck at Amazon screen. I am on stock now, but was just wondering what I was doing wrong.
[Fire Original Android Development] t3chwizard:
Yea, clean flash with data and system was necessary, all is working great now. Whatever ggow did the system is much faster, but it also could be due to not using app2sd much anymore. Either way I can actually play games again without lag.

[MENTION=5749760]ggow[/MENTION] if and when you decide to start winding down on this I urge you to please post some source code so that someone can continue this awesome project if need be. Just to clarify I'm not saying now, but if ever you decide to stop please release source.

---------- Post added at 08:32 PM ---------- Previous post was at 08:31 PM ----------

Just use the 1/30 build of Lineage it works great for me.
[Fire Original Android Development] DragonFire1024:
I like to try other things. See what other options are available in each ROM. So if I can get in different one aside from the rwo I've tried, that would be awesome.
[Fire Original Android Development] ipdev:
rr should work if you flash from fireOS. I know it fails if you flash from the lineage 0130 build. Not sure about the nexus builds.

You can flash the lineage 0130 from rr by the way. :confused:

rr is a no-go from the last nexus build.
[Fire Original Android Development] ggow:
Source code is linked in the OP.
[Fire Original Android Development] DB126:
Only two ROMs are being actively maintained for this device: Fire Nexus and Lineage 12.1. While a ROM doesn't go 'stale' sitting on shelf the surrounding environment is constantly changing as we see today with issues surrounding FlashFire. None of the now depreciated ROMs (whether they wear that tag or not) were issue free when released and carry those worts forward with only community based support. Probably best to continue such OT conversations in their respective threads.
[Fire Original Android Development] xantiux:
So, this may be complete coincidence, but out of the 7 tablets I flashed, 5 were done successfully and 2 got stuck at the Amazon logo after the flash. The two that failed were connected to the PC via the USB cable while going through the process of flashing the ROM, while the other 5 were not. I thought I'd share my experience.
[Fire Original Android Development] DB126:
Whoa - great observation! I am almost always tethered when updating via FlashFire...either to transfer files or boot TWRP as needed (one of the fortunate few with an older bootloader). May give untethered updating a try as FlashFire consistently fails on my two active devices. Seems an unlikely connection but have also seen weirder things happen.
[Fire Original Android Development] riverstyxxx:
Well this is great, I have two tablets and they're both bricks now after updating. Great work, thanks a lot.
[Fire Original Android Development] tonibm19:
You can reflash stock fireos, root and then install Lineage again...

Probably (or in my case I could)
[Fire Original Android Development] NeuromancerInc:
No need for the sarcasm
[Fire Original Android Development] nirogu325:
I wonder what's the thread's disclaimer right below the OP banner...hmm. Sarcasms like that don't fly here. Search around, there are workarounds. Good luck.
[Fire Original Android Development] DB126:
5 min of reading (starting at the top or bottom of the thread) would have surfaced important caveats that should have raised yellow flags. But those flags never turn red as FireOS can almost always be reloaded via the stock recovery menu. You should probably become familiar with the restoration process and seek clairification up front if you wish to avoid a true non-recoverable brick or a device that can not be rooted which is a prerequisite for installing custom ROMs.

I encourage you to do your homework, ask questions as needed (lots of folks here able and willing to help) and check the sarcastic attitude at the door.
[Fire Original Android Development] riverstyxxx:
This is just going from bad to worse. The Kingroot pc app doesnt work, it created temp root for one of them. The apk that comes with the supertool forces an online connection to work (which is not allowed because it would update the fireos to the latest). I tried a previous version of the pc app, didnt work either but it tried. I moved on to Kingoroot, it's doing something but who knows. FYI Kingroot detect my 5.3.1 at 5.1.1. Also tried manually replacing the supertool kingroot .apk with the latest version, same thing.

This is on two tablets. The same results.
[Fire Original Android Development] DragonFire1024:
May need to run kingroot several times, restarting after a few tries. It takes me many times sometimes when I play around. Other times it happens on the first go. Use the kingroot that comes in the supertool. Don't ever click request. Disable this apk using the adb code below, before turning on Wi-Fi and running kingroot:

adb shell pm uninstall -k --user 0 com.amazon.device.software.ota

That disables OTA.

adb shell pm clear com.amazon.device.software.ota

That clears the app data and any pending updates.
[Fire Original Android Development] riverstyxxx:
No good: Error: Unknown option: --used

edit: "success" on one. working on the other.
[Fire Original Android Development] DragonFire1024:
Sorry typo. Used = user
[Fire Original Android Development] riverstyxxx:
Alright thanks, seems to be running its course.

---------- Post added at 02:58 AM ---------- Previous post was at 02:36 AM ----------

Doing good, after 453 restarts I got one rooted.
[Fire Original Android Development] steve8x8:
I'm still at 20170928 and hesitating to jeopardize my setup, but more and more often I'm told to upgrade my Google framework.

The tablet isn't linked to a G account, it's mostly running fdroid apps, and has less than a handful apps coming from yelp store. The latter ones are the source of the trouble, obviously.

I'd appreciate any advice how to proceed from here. Dirty flash another recent gapps? Take recent gapps, extract some packages, install them? Not sure whether the risk of terminally breaking something is outweighed by the limited gain...
[Fire Original Android Development] DB126:
Assume TWRP is not an option as risks are minimal updating via that route. I successfully dirty flashed the latest 2018 build over a 2017 predecessor built from different sources.

In my experience updating Google framework/services (GApps) independent of a ROM refresh only leads to trouble on CM/LOS based ROMs regardless of approach. They really need to go in together.

Thoughts:

- backup current environment with the latest FlashFire build (details)

- copy all flashable files (ROM, GAaps, etc) to internal storage

- skip SuperSU; can be added later if absolutely needed

- untether device

- queue up FlashFire in the normal fashion

- (optional) tick 'Mount /system read/write' (personally recommend)

- hold breadth and execute

If all goes well you'll come out the other end with 20180130 and all apps/data in tact. If things go badly a reload/reroot of FireOS is the fallback.

There are claims OTA updates can be blocked on unrooted FireOS via a simple ADB command. I would still practice good network hygiene and keep the device fully isolated (WiFi off) except when connectivity is absolutely needed.
[Fire Original Android Development] Neffy27:
I just made the switch from Nexus ROM. It was starting to get too laggy. Full clean wipe and straight to latest Lineage ROM via Flashfire. Transferred some apps with Titanium Backup. Zero issues.

Thank you [MENTION=5749760]ggow[/MENTION] !
[Fire Original Android Development] isTos:
What version of Flashfire did you use? 0.53 is crashing on me upon launching.

Thanks!
[Fire Original Android Development] M.Ray:
Just for the info: I had a december-build installed and risked it to i nstall the new 30. Jan build with flashfire 0.73 with clean wipe etc. and mount system: ticked.

(Yes, i read the instruction to use an old flashfire version, i just wanted to try it)

Got the same errors as other user: Mount : failed to mount /dev/block/platform/mtk-msdc.0

Eventually the fire got stuck at Amazon boot logo.

So in the end i also had to use twrp to flash the new build and everything is running fine.
[Fire Original Android Development] ggow:
Glad you had the option of twrp as a backup. Thanks for testing. Always good to get an additional data-point.
[Fire Original Android Development] DB126:
Curious - was the device tethered in any way (charge only or to a host) while FlashFire was running? Another member reported his/her experience updating seven devices. Five went fine and were stand-alone; the two that failed were tethered.

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

Version 0.53 is time bombed (developers words); I believe 0.58 still works. If not you'll need to go with 0.73 which has worked fine for several while failing for others. Good luck.
[Fire Original Android Development] Neffy27:
Latest, I think it's .73. I just added the zips with default options. I did have to move wipe action back to top.
[Fire Original Android Development] andPS2:
i updated my 2 devices that are able to use twrp via twrp

dirty flash worked for me as well luckily

my two older devices without twrp ability are spread out in my family

gonna try soon with flashfire on them...
[Fire Original Android Development] isTos:
I ended up using FF 0.73, and the flashing process was successful, however, how do I enable root?

I went into Settings > Developer Options > Root Access. Selected Apps and ADB.

However, I still get no root.

Thanks.
[Fire Original Android Development] DB126:
Need to reboot after enabling root.
[Fire Original Android Development] akz1x1:
Okay I have finally got some access to a laptop,

Now I have sideloaded 5.3.1.0 and installed kingroot.

But kingroot requires internet access to work?

But people strictly suggest not to turn on wifi in any case.

So any help?

Edit: finally flashed the new version. It's been lying dead for past few days lol. Everything's working good.
[Fire Original Android Development] DB126:
Three options:

- use the desktop variant of KingRoot which does not require network access on the target device

- enable WiFi for the first 30-60 sec of a rooting attempt and then disable; this gives KingRoot sufficient time to download the exploit database but is too small of a Window for FireOS OTA updates to be identified/downloaded unless you are on a very fast connection

- (unproven) temporarily disable OTA updates using adb commands from this post

You can use the 2nd and 3rd options together for maximum protection against OTA updates.
[Fire Original Android Development] M.Ray:
Hm. I did everything as as dozen times before: Fully charged battery (so no cable connection), downloaded rom and gapps to internal memory, everything - except wifi - was off.

The only thing i changed was the Mount /system read/write option. (I think i remembered someone suggested it along this thread when updating to the new lineage base).

After the error message the opengapps package seemed to install normal, so at first i even thought everything went fine - and then it got stuck.
[Fire Original Android Development] thomas69k:
hi,

first of all good work on the rom, I'm in a pickle now, I upgraded the rom to build 20171217 and did a factory reset. unfortunately, now I just have os and apps for calculator, clock downloads, settings, and supersu. i enabled developer options - usb debugging and tried to connect to pc, unfortunately, i cannot connect adb devices is not showing anything. Tried bluetooth to transfer apk files, then realized Bluetooth won't allow apk transfers. is there a way i can transfer apk to tablet at this point. i dont see any browsers in the tablet
[Fire Original Android Development] Hallo32:
Why not to the latest build?

Are there any new devices in th device manager with the connected device?
[Fire Original Android Development] Hallo32:
vitals_collection_agent

Any ideas why this task is running and where it is called?
[Fire Original Android Development] thomas69k:
i was trying from the previous build, its not showing up in device manager, tried multiple cables, its getting charged when connecting using usb

---------- Post added at 12:30 PM ---------- Previous post was at 11:48 AM ----------

i was trying from the previous build, its not showing up in device manager, tried multiple cables, its getting charged when connecting using usb
[Fire Original Android Development] Hallo32:
On a dirty update it worked for me.
[Fire Original Android Development] thomas69k:
at this point, i don't have any options to update the version
[Fire Original Android Development] Hallo32:
You should be able to send any files to the tablet over BT, if you enable "accept all file formats".

Configuration->Bluetooth->three dots at the right side

I'm not using the english interface, don't search for the exact spellng.
[Fire Original Android Development] thomas69k:
unfortunately i have only the following items

refresh

rename this device

show received files
[Fire Original Android Development] DB126:
You likely have the conventional fallback: boot into stock recovery, reload the last version of FireOS that was on the device and then start over. Use FireOS 5.3.1 if unsure of the prior version. Be sure to maintain full network isolation (WiFi off!) until OTA updates have been blocked. Details on how to root when WiFi is disabled (hint: briefly cycle on/off) can be found throughout the Fire forum and likely within this thread. Search is your friend.
[Fire Original Android Development] Hallo32:
It seems something went wrong in your case.

Before following the way described by Davey126, I would first reset the device to factory default.
[Fire Original Android Development] shar88:
Are there other devices affected by this flashfire partition issue or is it exclusive to our Amazon Fire?
[Fire Original Android Development] DB126:
Can't say with certainty with this specific issue but FlashFire behaviors are frequently device specific.
[Fire Original Android Development] thomas69k:
unfortunately, i cannot get to sideload the apps as the system is not getting recognized by laptop, I've tried multiple systems. one of the systems is the one I used to load Android to tablet
[Fire Original Android Development] DB126:
Try a different USB cable; amazing how often this solves the problem. Make sure the device has been booted into stock recovery with the sideload option selected/activated. Then tether the device and observe how the host responds. Usually Windows selects/installs the proper drivers for this device; same for Linux. Not sure about OS X. Otherwise you may need to load drivers in advance. See this thread for additional details and video guidance. Remember: Go with FireOS 5.3.1 unless you are 100% sure of the exact prior version. Consequences of guessing can be ugly and non-reversible.
[Fire Original Android Development] thomas69k:
unfortunately, the device itself is not showing up in device manager, tried different cables, however, the device is getting charged while connected to the laptop. drivers are loaded from the supertool.
[Fire Original Android Development] DB126:
You'll need to work through the connection issue to have any hope of recovering your device. Almost certainly a driver/port/cable issue. Try rebooting both devices.

Note charging and data transfer occur over different pins/wires; the presence of one has little bearing on the other.
[Fire Original Android Development] andPS2:
today i got a message on one of me fire google play is not supported for this device

please contact your manufacturer

after pressing ok i was able to still update an playstore app

never seen this message before

hope google isnt trying to block anything in the future...
[Fire Original Android Development] Hallo32:
Which recovery so you have TWRP or stock?

You could have meshed up the Android installation but not the stock recovery. If the fire is not detected with the stock recovery, I would have a closer look at the USB port, USB cable and the software installation on the pc/mac.
[Fire Original Android Development] AwlsomeAlex:
Bootloop

Would like to point out in both instances of Installing the LATEST Lineage OS (1/30/18) on both my tablet with an older version of Lineage OS (FF 0.73) and my tablet with AOSP (FF 0.58) will both result in a bootloop but not a Hard Brick. After many hours of research, I was able to restore them with FireOS 5.1.1. with this guide (Since that is considered the "Current Version" for both tablets) and retry the process after rooting it with this guide and flashing it as I normally would and it resulted in a successful flash (FF 0.58). The moral of the story, not the best time to be flashing. :(

EDIT 1: Both devices were being detected as 5.1.1 in the recovery log so I figured flashing them with the version theyre being detected as would work, and it did. NEVER DOWNGRADE OR YOUR DEVICE IS DONEZO!
[Fire Original Android Development] DB126:
Quick note to those unfamiliar with reloading/sideloading FireOS: in many cases downgrading below the version previously installed will result in a non-recoverable "hard brick". If uncertain of prior build go with 5.3.1 which is the highest rootable version of FireOS.

tl;dr: downgrading bootloader will brick device on reboot...guaranteed.
[Fire Original Android Development] Copro:
Thanks - trying to flash a just rooted Fire tablet with FireOS 5.3.1.0 to this LineageOS port!

Success using FF 0.58 and lineage-12.1-20180130-UNOFFICIAL-ford.zip plus open_gapps-arm-5.1-nano-20180226.zip

Enabled root in debug options

Also verified Miracast to LG tv works

But even tho I used the nano gapps there is no play store - is this contained in the nano package?
[Fire Original Android Development] AwlsomeAlex:
Theres a weird

bug?

that won't install GAPPs when you flash the ROM beforehand. Try flashing GAPPs again with the same settings (Just GAPPs) but this time wipe the Dalvik Cache and Cache Partition afterwards. Hope this helps.
[Fire Original Android Development] rozwell01:
I think I know why(maybe)

If your problem is device manager in windows, it shows as "knoxll" (or something that looks like that)with a weird triangle that looks like windows installed it wrong when amazon is adb push update, you need to change driver manually to "adb composite device".

---------- Post added at 06:22 AM ---------- Previous post was at 06:08 AM ----------

Which settings do I use for flash fire linage updates? Since they updated it(old versions mounted both options auto checked r/w system and new ones don't) when I go to update I always do it wrong now so then there goes a 1/2 hour to reload reroot, flash my restore to recover) do I want to mount these two options as r/w or no?

Thanks
[Fire Original Android Development] asad393:
Upgrade for Fire OS 5.6.0.1

Hi there guys,

I just today got my Amazon Fire 7 (5th Generation). Its running Fire OS 5.6.0.1. Any recommendation or method on how to get Lineage OS on it ?
[Fire Original Android Development] ms372591:
Any models above 5.3.1 are not able to be rooted so you will have no way of adding any custom roms.
[Fire Original Android Development] DB126:
Defaults in 0.58-0.73 are fine. If you like to turn knobs "mount /system read/write" is safe to tick; leave all other zip options alone. Be aware these settings have no impact on recent flash issues reported in this thread which remain undiagnosed.

---------- Post added at 01:19 PM ---------- Previous post was at 01:17 PM ----------

You can't; device (specifically FireOS 5.6) can not be rooted or rolled back to a rootable build. Root is a prerequisite to installing a custom ROM.
[Fire Original Android Development] melvinaury:
Only option is launcher hijack tool and sideload playstore
[Fire Original Android Development] ext23:
I don't have an unlocked bootloader and so can't boot into TWRP. (Anybody know how to do this?)

Anyway I flashed Linage from CM using FlashFire and now I don't have root access. Lineage is working fine but how can I get root access here? FWIW KingRoot doesn't seem to be working. Can I flash SU via ADB or something? Fastboot isn't an option because like I said I don't have an unlocked bootloader.