yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] ipdev:
[MENTION=5749760]ggow[/MENTION]

I am confused why ff .58 works for me.

I haven't had much time tonight to test. The results of the last few things I tried reminded me of few things.

Back in (ff v.3? days I believe) there was an issue with the AROMA option enabled and seemed to affect this device.

CM setup wizard errors. (Mostly the crashes if you try to remove it with a open_gapps config file.)

A different amazon device from awhile back (might have been firePhone ;) I don't remember) and flashing anything but, pico gapps.

My last test for tonight was from fireOS 5.1.1, SR5-SuperSU-v2.82-SR5-20171001224502, FlashFire-v0.73-20171001124337-B1.

I was a little confused when everything flashed correctly and I was hit by a CM SetUp wizard?

So FlashFire options, open_gapps, open_gapps config file or rom ?

I should have more time tomorrow night to start picking these one at a time to see if I can narrow down what actually is causing my problem.
[Fire Original Android Development] ggow:
I am in the same situation ff 0.58 works for me too. Thanks for taking a look and feedback.
[Fire Original Android Development] micgeb:
Yes, you are right.

I installed 2.8.2 supersu.
[Fire Original Android Development] cry-o-nic:
I flashed through TWRP following a factory reset. Like others I don't have the root access entry in developer options nor does anything prompt for permission. Root is generally not available. An oversight or an intended change?
[Fire Original Android Development] Hallo32:
Dirty update with flashfire 0.73 up and running fine.

Thanks [MENTION=5749760]ggow[/MENTION]
[Fire Original Android Development] mi4agent:
Sucess with flashfire 0.58

Nevertheless now root is not available. Maybe it should be pointed in #1

How can I add the SU? I am only able to use Flashfire
[Fire Original Android Development] ggow:
Root should be available. Can you see the option in developer options?
[Fire Original Android Development] mi4agent:
Hi again,

Having read about it, I checked the developer options and there is no trace of Root
[Fire Original Android Development] DB126:
There is no root option shown under developer options in the 20180128 build installed via TWRP. However, root access is available and can be toggled for individual apps under permissions. If you search for "root" in settings a 'hit' is shown under developer options but the setting/toggle is not exposed.
[Fire Original Android Development] ggow:
OK, I have found a bug in Settings App which causes the root access options not appear. Will push a new version this evening to fix that.

I'm pulling the plug on the 20180128 release. Will be removed shortly.

EDIT:

20180128 pulled due to root option bug
[Fire Original Android Development] ggow:
New Build is Up

- Dated 30 January 2018

- Fix root issue not appearing in developer options

- Flashed clean with FF 0.73 - go figure - it worked for me this time no errors
[Fire Original Android Development] tobyxx:
Works perfectly! Did a dirty flash over the Januars 28 build and everything is working and root option is back. Thank you so much!
[Fire Original Android Development] DB126:
Unfortunately, no such luck for me. FlashFire 0.73 crapped out in the usual manner with difficulty mounting/unmounting the system partition (eg: claiming /system did not exist). At one point a string flash across the screen suggesting unresolved variables in the path to /system; might be a clue for [MENTION=631273]Chainfire[/MENTION] when he returns. I was able to restore the prior build and apply 20180130 via TWRP.

I really don't think the version of FlashFire is the culprit. Something else is going on but it's hard to think what given the level at which FlashFire operates. I wonder if Lineage is doing something early in the boot sequence before FlashFire takes over.
[Fire Original Android Development] ggow:
Can you post your FF logs?
[Fire Original Android Development] skiwarz:
What did I do wrong?

Latest flashfire version (0.73 maybe?)

Wiped system,dalvik,cache,and 3rd party apps

Installed the 30jan zip file

Now I get a blank screen on boot. Nothing shows up, but the backlight turns on. I can get into fastboot and recovery though.
[Fire Original Android Development] ggow:
We're not sure what the issue is at the moment with everyone having mixed results. Need as many logs as possible etc to narrow in to the solution.
[Fire Original Android Development] mi4agent:
Hi again!

i am trapped in the previous version, because due to the bug, I cannot give root permissions to flashfire.

Any recommendation?

---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------

Something like this?

Reboot tablet to bootloader: adb shell reboot bootloader or power button + volume up

Boot recovery: fastboot boot TWRP_Fire_2.8.7.0_adb.img

Wipe dalvik cache, cache, data and system

Flash Rom

Flash Gapps
[Fire Original Android Development] DB126:
Attached. Initial failures are in the middle as log also contains results of subsequent GApps and Xposed installs. I left those as they surface interesting detail on the how the /system partition is handled. For clarity a standalone flash of Lineage also fails.
[Fire Original Android Development] DB126:
Aside from the on going FlashFire issues the 20180130 build has been quite stable. Recall I dirty flashed over 20171208 which was not advised due to different sources. In my case everything continued to work on my not-so-simple config (Xposed framework; secondary swap file in cache partition; multiple symlinks to SD card; etc). Woohoo!

While premature to draw any firm conclusions the 20180130 build also seems more responsive on wake (less cache/swap activity); also noticed this on 20180128. But it could well be a result of rebuilding dalvik vs anything native to the ROM. For now I'll enjoy my placebo. :)

As always, thanks [MENTION=5749760]ggow[/MENTION] for all your hard work on this aging platform. It would be easy to put a bow on it and walk away. At some point that will have to happen. I'm glad that day has not yet arrived.
[Fire Original Android Development] tobyxx:
I used flasfire 0.73 Pseudo-pro, only wiped dalvik and mounted system read/write. I need to say i skipped the december build due to the error reports. Log attached , don't know if it will help.
[Fire Original Android Development] ggow:
On initial look, FF is failing to mount the /cache and /system partitions quoting read-only filesystem... initially doesn't look like it's the fault of the ROM. Hopefully [MENTION=631273]Chainfire[/MENTION] will be able to help shed some light on the issue.
[Fire Original Android Development] DB126:
Yeah - almost as if FlashFire lacked root-like permissions. As an aside, I always enable the FF option 'Mount /system read/write' as it is recommended when flashing custom ROMs (more accurately, I select the 'never' option for 'Treat system as original' in settings). This would be left unticked on devices that might receive future OTA updates. Of course, I have experimented both ways...makes no difference w.r.t current failures.
[Fire Original Android Development] t3chwizard:
So [MENTION=5749760]ggow[/MENTION] the consensus right now is to not update until this is sorted out?

I am on the last December build
[Fire Original Android Development] akz1x1:
I'm also on December build, waiting till things are sorted out.

If you don't mind flashing stock and starting over in CASE things go wrong. Definitely give it a shot.

The december build is already rock solid. So I'd wait.
[Fire Original Android Development] ggow:
I would hold off for now.
[Fire Original Android Development] t3chwizard:
Will do thanks. Also a general question, can one restore FlashFire backups using TWRP?
[Fire Original Android Development] DB126:
Yes (with caveats) according to this page. That said, if your device can boot TWRP there is no reason not to install 20180130 as all of the recently discussed issues concern FlashFire, not the ROM itself.
[Fire Original Android Development] t3chwizard:
Interesting, I still prefer to flash with FlashFire anyways, it's so much more convenient than having to type fastboot commands lol.

I'll try upgrading today to see what you guys are talking about.
[Fire Original Android Development] s_k_u_ll:
I am trapped in the previous version 20180128, because due to the bug, I cannot give root permissions to flashfire.
[MENTION=297200]Davey[/MENTION] you have said that root access is available, can you explain us how to do

Many thanks
[Fire Original Android Development] t3chwizard:
[MENTION=5488402]Davey126[/MENTION] I am confused after reading all the posts. I thought it wasn't advisable to use SuperSU, but it seems now people are using it instead?
[Fire Original Android Development] DB126:
Navigate Settings -> Apps -> FlashFire -> Modify (under permissions). If root is listed you can grant access there. If not the prerequisite su binaries and/or master switch setting are not in place; you'll need to sideload FireOS and start over to regain root access.

In my case the proper binaries were retained/restored along with the previous master switch setting. I would not be surprised if that's not the case for others.
[Fire Original Android Development] s_k_u_ll:
Thanks, bad news, I have followed your instructions but root is not listed under app permissions :(

There is /system/xbin/su file, but I don't know how can I do to regain root access to flashfire.
[Fire Original Android Development] DB126:
People use it out of habit or preference for the more granular UI. I am not a fan on Lollipop (Android 5.1) based ROMs in general and Lineage in particular due to spontaneous loss of root experienced by many including me. That's merely an annoyance on most devices as SuperSU can simply be reflashed to restore root. On Amazon devices (that can not boot TWRP) the fallback is sideloading FireOS and starting over. Ugh!

SuperSU 2.82 SR5 seems to have solved the problem. However, the project is all but abandoned with the departure of developer [MENTION=631273]Chainfire[/MENTION] and complete lack if engagement by CCMT (new owners). Given Lineage has an integrated, stable root solution why mess with SuperSU?

I still use SuperSU on some older devices but have decided to go with Magisk on newer builds. Unfortunately, Magisk is not an option on this device due to the locked bootloader.

At one time SuperSU (vs KingRoot or some other root method/solution) was a prerequisite to using FlashFire on FireOS. I believe that requirement is lifted in newer FlashFire builds but have not tested.

---------- Post added at 05:18 PM ---------- Previous post was at 05:11 PM ----------

You'll need to sideload FireOS (with all associated precautions) and start over. Or just live without root for awhile as Lineage runs fine without it.
[Fire Original Android Development] chris-89:
I made a clean wipe in TWRP (System, Data, dalvik, cache and also internal)

Then i flashed the rom, opengapps pico and SuperSU 2.82 SR5 from external sd.

And everything works fine here. Very smooth and stable so far.

Btw thank you very much for your work :good: [MENTION=5749760]ggow[/MENTION]
[Fire Original Android Development] s_k_u_ll:
very bad news.. I need some help, I have to use this post https://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

Is it correct?

But I don't know which FireOS version I have to sideload

many thanks
[Fire Original Android Development] t3chwizard:
DO NOT connect wifi under any circumstances in FireOS!!!!
[Fire Original Android Development] s_k_u_ll:
ok, thanks

but I don't know what FireOS version I have to sideload :(

Edit: I answered myself: https://xdaforums.com/showpost.php?p=74496406&postcount=374

As I don't remeber what FireOS I had, I should use 5.3.1 and give a try.
[Fire Original Android Development] DB126:
Correct (5.3.1). Be sure to heed guidance on maintaining network isolation while on FireOS (WiFi off!).

You will have to connect briefly during rooting attempts; your device will be vulnerable to an unwanted OTA update during those windows. If you see unusual download activity flip off WiFi immediately and reboot. It will be a nerve wracking exercise until FireOS is expunged from the device.

Ask yourself if the effort/risk is worth the benefit at this time. Lineage runs fine without root. And there's no assurance things will go smoothly on the next attempt. Might end up back in the same situation.

In your shoes I would leave it alone until there is a better understanding of what's happening with FlashFire.
[Fire Original Android Development] Hallo32:
Build: 30 January 2018

Is "ADB over network" working for you?

---------- Post added at 12:34 AM ---------- Previous post was at 12:31 AM ----------

Use kingroot for windows to eliminate the risk of an OTA update during the root process.
[Fire Original Android Development] DB126:
Unfortunately, rooting higher builds of FireOS with the desktop variant of KingRoot has been hit/miss. But reasonable to try as it eliminates risk of an unwanted OTA sneaking in. Can always switch over to app if desktop version doesn't work.
[Fire Original Android Development] Hallo32:
The desktop version worked for me for fireos version 5.3.1 yesterday after a few tries.
[Fire Original Android Development] Hallo32:
Build: 30 January 2018

* Is "ADB over network" working for you?

* Enable root seems to need a reboot to work correctly after enabling root for ADB and apps.
[Fire Original Android Development] nirogu325:
Current build flashed successfully over TWRP. This out of the box runs better than December's build. Smells like some optimization happened in the new code. I debloated even further and had 500MB free RAM before restoring user apps. After restoring and without user apps in memory, 369MB free RAM.
[Fire Original Android Development] DB126:
Agreed as noted here. Still noticeable after several days. Looks like [MENTION=5749760]ggow[/MENTION] found a winner enhanced with a touch of his own secret sauce. :)
[Fire Original Android Development] akz1x1:
New build can be safely flashed using older version of flashfire mentioned in op ... On December build rigght now
[Fire Original Android Development] DB126:
My experience was somewhat different with unfavorable outcomes regardless of FlashFire version (tried 0.52, 0.58 and 0.73). I was able to update via TWRP but most do not have that option. The developer reported FF v0.73 inexplicably worked for him with the latest build. So I don't think there is a demonstratable correlation between FF version and the success of installing this ROM. My gut leans leans elsewhere.

[MENTION=5749760]ggow[/MENTION] - may want to consider removing guidance on FF version(s) in the OP. Also note older builds will stop working at various dates due to the imbedded "time bomb" as documented in FF change log. Workaround involves setting a faux date on device which is kludge IMO
[Fire Original Android Development] s_k_u_ll:
Now I have Build: 30 January 2018

I have sideload FireOS 5.1.2 because I remembered I had that version, then I have rooted it with desktop variant of KingRoot, and finally I have flashed with latest FlashFire version without any problem.
[Fire Original Android Development] ggow:
Yes flashfire creates backups that can be flashed with twrp
[Fire Original Android Development] xantiux:
I tried flashing the latest ROM, and the tablet is stuck on the Amazon If the tablet is stuck on the Amazon logo screen, and I do not have TWRP, does that mean the tablet is garbage at this point?

Picture of the screen after the flash with flashfire, before it rebooted.

Not sure why the image isn't showing up. imgur.com/a/tlwTa
[Fire Original Android Development] DB126:
Bad news - you got bit by the FlashFire glitch discussed in recent posts. :(

Good news - you tablet can be easily revived by reloading the version of FireOS that was previously in use. If not certain of the exact version use 5.3.1 which is the safe fallback. Don't guess; using the wrong build can permanently brick your device.

You can find older builds of FireOS for 5th gen devices here. A video describing how to reload FireOS can be found here. Just be sure to use the proper build for your device...not the one mentioned in the video.

Once FireOS is reloaded it is important to maintain total network isolation (WiFi off) until rerooted and OTA blocked. Failing to take these steps will result in an immediate update to an unrootable build of FireOS (likely 5.6.0.1).
[Fire Original Android Development] ipdev:
Just a quick note.

I have had the MOST problems after sideloading fireOS via recovery.

I even had to use kingroot once to root it. I normally use Link

My only guess is sideloading in stock recovery is treated as an update regardless of what is installed. Even if that is broken.

Had to sideload fireOS again tonight so I made a new ff backup. To test this theory.

Flash from sideloaded fireOS - fail.

Flash from new ff restore backup - worked.

Here are the ff log files.

Edit: I found by using "wipe data/factory reset" and "wipe cache partition" before and after sideloading fireOS seems to help quite a bit.

Note:

I can install and use the latest builds. Problems come from trying to narrow down how. The mount errors do not seem too important, since everything still installs - Save for OpenGAPPS. Reason why it is now at the bottom of my flash list. The mounting errors do not seem to be Device, API or OS related.

Example from Nexus 7 2013 WiFi
[Fire Original Android Development] akz1x1:
So some users managed to flash the latest build from December build to Jan 30 without any hustle using FF.

Those who tried flashing...

Please answer the following questions if possible...

1. Were you successful in flashing the new version?

2. What version of flash fire did you use?

3. Were you clean flashing or dirty flashing?
[Fire Original Android Development] DB126:
- see here

- wiped system partition (technically dirty flash as data left intact)

- previously tried full wipe including Internal Storage; same outcome
[Fire Original Android Development] xantiux:
Thank you for the descriptive answer. It helped me revive my tablet. I had RootJunky's SuperTool installed on an old laptop from the very first time I rooted the tablet. I loaded the stock Fire rom (5.3.1.0), rooted it with the desktop variant of KingsRoot, loaded FlashFire 0.53, and then flashed the Jan 30 version of the Lineage rom. Thanks again!
[Fire Original Android Development] gompka:
After doing a regular flash to jan 30 with flashfire I got stuck the Amazon Logo. I had to sideload 5.1.2, reroot, and then install jan 30. Booted this time.
[Fire Original Android Development] Hallo32:
Which Flashfire version?

Which Open GApps variant?

Which files have been in the addon.d folder?

---------- Post added at 03:38 PM ---------- Previous post was at 03:33 PM ----------

1. yes

2. latest available version

3. dirty flashing

4. (gapps pico)
[Fire Original Android Development] Timballist0:
Success

I successfully installed the 2018 Jan 30th rom using Flashfire 0.73. I was on CM 12.1, the Flashfire 0.58 would always crash at "Checking for pro", maybe a Busybox problem? Throwing caution to the wind, I installed the updated Flashfire from the Play Store; that version worked. Following the first post directions, I was able to flash everything just fine.
[Fire Original Android Development] t3chwizard:
I lost root upgrading from the last December build to the 1/30 build [MENTION=5749760]ggow[/MENTION] so I can confirm I have experienced it as well
[Fire Original Android Development] Alaxmofo:
I was talking about flashing FireOS from the stock recovery by doing "apply update via adb" since I can't do "apply update via sd card".
[Fire Original Android Development] ipdev:
[MENTION=7547097]Alaxmofo[/MENTION]

Make sure adb is correctly installed on your computer and you have the correct version of fireOS downloaded for your device. (The last version of fiireOS that was installed on your device.)

Amazon system recovery <3e>

Volume up/down to move highlight;

enter button to select. (enter button is the power button by the way. ;) )

reboot system now

apply update from ADB <- Select this option.

wipe data/factory reset

wipe cache partition

reboot to bootloader

power down

view recovery logs

On your computer run :

adb sideload update-kindle-global-xx.x.x.x_user_xxxxxxxxx.bin

(Use the appropriate named update.bin for your device.)

If you need more help check out this thread.

https://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

Cheers. :)
[Fire Original Android Development] TheZoker:
So this rom does not support the 2016 version, right?
[Fire Original Android Development] DB126:
There is no 2016 version of this device. Regardless, applicability at present is limited to *rooted* 5th gen (2105) Fire.
[Fire Original Android Development] xenokc:
Everything running fine but most apps don't recognize root. It shows on developer options that root is on for both apps and adb. Suggestions?
[Fire Original Android Development] DB126:
- have you rebooted since enabling root?

- any attempt to install another root manager (eg: SuperSU)? That can muck things up.
[Fire Original Android Development] monster1612:
Try disabling root through developer options, then toggle it back to "apps and ADB" and reboot afterwards. I've had that issue with other CM/LOS builds on other devices, and toggling it usually solves the problem.
[Fire Original Android Development] xenokc:
Hmm, I did attempt to install another root manager. Guess I'll start from scratch with a full wipe.
[Fire Original Android Development] xenokc:
Just did a full wipe re-install and still no root after enabling in Developer settings.

edit: OK I did an adb shell from terminal then did su and it worked, Then apps now able to get root access. Curious.
[Fire Original Android Development] Alaxmofo:
So it successfully work flashing lineage from slimlp, just follow what it says in fresh install with fireos or rom using flashfire. And make sure you have everything on internal storage instead of sdcard or it will throw errors?. (It happened to me).

Still no success with adb though, must be that my files aren't installed right.
[Fire Original Android Development] DB126:
No, native LOS root manager works fine. Sounds like a procedural error either during reinstall (system wipe) or when enabled (make selection and reboot).

What app(s) are indicating root isn't available? Have you validated with a root checker app or trusted utility?
[Fire Original Android Development] t3chwizard:
Is this ROM awesome? I'm considering switching from Fire Nexus?

---------- Post added at 05:32 AM ---------- Previous post was at 05:31 AM ----------

This is so cool. You are porting security patches and making this awesome device even more awesome!!! Thank you
[Fire Original Android Development] DB126:
Err...it's a ROM and does what ROMs do. If you enjoy a few built-in UI customizations then you might like LOS vs Nexus which is pure AOSP and makes an excellent platform for unlimited personalization and functional enhancement. I'm running LineageOS 12.1 on one device; no issues to date.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 02 August 2017

- Fixed sdcard write issue

- Fixed odd screen rotation glitch on power off

- ROM status updated to "stable"

- Enjoy :D
[Fire Original Android Development] t3chwizard:
You da real MVP :D

---------- Post added at 01:33 PM ---------- Previous post was at 01:29 PM ----------

Will be giving this a try then. Fire Nexus is somewhat dated and lacking in customizations as you stated. Over a year later and I'm still loving my Amazon Fire 7 (5th gen) due to the awesome support from everyone in this community. You guys rock!!!! It also helps that I got mine very soon after release so it has the bootloader than can load TWRP, but it is still an awesome device nevertheless.
[Fire Original Android Development] Capsaicin88:
will there be a way to root v.5.3.3.0?
[Fire Original Android Development] DB126:
Got a crystal ball? Me neither.

Don't get your hopes up. Been a big push over past 12-15 months to clean up sloppy code that lead to exploitable root vulnerabilities. Seems to be working.