yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] platypoid:
Did you go to Developers Options in the Settings and Enable Root ? If you do that you also need to reboot to get it take effect.
[Fire Original Android Development] Ace42:
From what I remember you cannot flash TWRP outright...that is why you switch to fast boot mode, and *boot* TWRP via the boot command in cmd.

It's something like fastboot boot [Directory]twrp_fire.img

You can try flashing SU with flashfire, but I prefer TWRP 2.8.7 because I'm unfamiliar with that app. I don't trust king root at all.
[Fire Original Android Development] DB126:
TWRP can not be installed on any 5th-7th gen Fire tablet as the bootloader remains locked. Early build 7" 5th gen devices could boot a suitable TWRP image from fastboot; very few devices fall into that category. Those that have a 'special' device tend to know it. For the vast majority of eligible (operative word) 5th gen devices FlashFire is the only method available for flashing content.

Prior poster offered sound guidance: enable root under developer options and reboot. If that doesn't work reloading FireOS via stock recovery and starting over is the only option if root is desired. Of course, Lineage will run just fine in an unrooted state.
[Fire Original Android Development] ext23:
Thanks, I didn't know that Root was available in Dev Options. This fixed my problem, enabled Flashfire and allowed me to flash a few packages. Adaway here I come!
[Fire Original Android Development] Ace42:
Mine are able to boot TWRP from fastboot, I figured that applied to everyone here. I have no idea what Fire OS version they were on prior to switching to custom ROMS, though they're from Nov 2015. But now I understand why FF is always mentioned instead of TWRP, thanks!

:highfive:
[Fire Original Android Development] chiwolve:
I am having issues too. Flashing from Fire version 5.1.1 and can get Lineage to load but without GAPPs. I can get GAPPs to load once Lineage is on, but will not re-flash Lineage and subsequently sticks on Amazon logo at reboot. Have not tried above yet...but will tomorrow. Anyone else have same issue and having wipe after just GAPPs install work (as suggested above)?
[Fire Original Android Development] DB126:
If your device can boot TWRP then it has the original 5.0.x bootloader which contained a 'flaw' which Amazon subsequently patched. Should you ever need to reload FireOS go for 5.0.1 and maintain absolute network isolation (WiFi off) until the issue driving reinstallation of FireOS is addressed. But there should never be a need to do that if a custom recover can be booted.

Those with bootloader (effectively FireOS) build 5.1 and above can NOT roll back to 5.0.x. Device will hard brick with no known recovery.

---------- Post added at 02:51 PM ---------- Previous post was at 02:36 PM ----------

Add a wipe task at the top of the FlashFire operations sequence that includes system (system data), data (3rd party apps), cache and dalvik partitions. Then flash the latest Lineage build with a suitably sized Open GAaps package (mini or smaller) as operations #2 and #3, respectfully. If that does not work then a more comprehensive wipe may be needed to clear out whatever remnants are blocking the installation of GAaps.

Installing GAaps after CM/Lineage has initially booted will almost always yield a less than satisfactory outcome.

Do not include SuperSU during the initial flash attempt as it adds unnecessary complexity. Lineage has it own root manager (Privacy Guard) which can be used temporarily or permanently.
[Fire Original Android Development] chiwolve:
Still no GApps. Here's what I've got:

Freshly wiped and rooted 5th Gen 7" Fire with auto update blocked

FF .73 (only one I could get to load as others have stated)

Wipe with 4 total checks: system data, 3rd party apps, dalvik, and cache (should I check cache and dalvik? I've tried both now)

Latest Jan 30 Lineage and Open GApps ARM Nano v5.1 flashed with nothing checked from local storage (not SD Card...should I try that?)

Again, it loaded Lineage but no GApps. When you say a more comprehensive wipe may be needed, what is your suggestion? Another added wipe? More wipe types checked? Which ones? I'm fine with wiping everything...nothing's on it. Your help and advice is much appreciated!
[Fire Original Android Development] DB126:
Well, it gets kinda wonky from here as you should not be facing this issue. It could be related to problems others have reported (self included) with recent FlashFire builds - although using an older build is no assurance of success.

Give it another whirl with 'internal storage' added to the wipe list (5 partitions checked). You will need to place the Lineage and GApps zips on a SD card as they will get zapped if located on the device.

If this also fails you may want to try Fire Nexus ROM (full) which has GApps nano integrated into the installation package.
[Fire Original Android Development] Blob Blobbed:
sweet. just installed. thx for sharing
[Fire Original Android Development] tweekde:
Battery Drain

Hello Fellas..

After sticking very long with CM-12.1 for my Fire Tablet I finally changed to Lineage.

For the update I got a brand new SD card and completely wiped the internal storage. So it is a fresh installation w/o any history data on the internal or external memory. This I have done through FlashFire as well as through TWRP.

Since I had problems with battery drain in the past, I did not Install any apps besides the recommend open gapps pico.

If I now lay the tablet down it takes about 12 hours before the battery is drained completely. This was not the case before the update and with the old CM-12.1 release.

Within the Lineage Settings Battery area I can see that the battery is getting drained by the "Android OS". This is also the most detailed information I get if I install a specific tool for battery monitoring.

I already checked my network if there is maybe constant traffic from the tablet but I cannot see anything out of the ordinary.

Do you guys have any ideas what could cause the drain? Or how I can investigate further and find out which Android OS part or process is causing this behavior?

Any hints are well appreciated.
[Fire Original Android Development] DB126:
Symptoms suggest botched install and/or incompatibility w/GAaps package. I easily get 7+ days w/30-60 min light usage per day on a device with a 2+ year old battery. Verify WiFi scanning is disabled then perform a wipe only targeting dalvik and cache partitions. If the problem persists redo clean flash with a fresh download of the latest Lineage and GAaps nano builds.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 15 March 2018

- Security patches up to March 2018 included
[Fire Original Android Development] Timballist0:
I have the exact problem. Ever since installing this rom, my battery went from lasting a week or so, to lasting maybe a day. I did a dirty flash with Flashfire, I used open gapps micro. When you say wipe dalvik and cache, I assume I can do that safely in flashfire without messing up anything else?
[Fire Original Android Development] DB126:
- cache/dalvik wipe via FlashFire should be perfectly safe; be sure only those two partitions are ticked and wipe is the only operation queued

- if dirty flash was from another ROM (FireOS, Nexus) then all bets are off as data structures do not always align
[Fire Original Android Development] nirogu325:
Privacy Guard is kinda getting on my nerves on the latest ROM release. I don't recall it being so active before. Can we somehow turn that thing off? I'm still looking everywhere. It reminds me of Window's UAC in a very bad (intrusive) way.
[Fire Original Android Development] ipdev:
I found that turning it on, reboot. Turn it off, reboot. Seems to work.

Edit. It is under Settings, Privacy.
[Fire Original Android Development] DB126:
Yep - privacy guard can be pretty dang annoying when enabled for all apps. Best to leave it disabled then toggle individual options as needed by long pressing apps of concern in the privacy guard list. Better yet, whap the 'advanced' option under the 3-dot menu to see apps grouped by permission.

I don't get all worked up over permissions on Lollipop as they are loosely enforced. If an app exhibits concerning behavior I uninstall it and look for alternatives. Blocking permissions is a fools errand unless one enjoys monitoring for conformance. Got better things to do with my life. :)
[Fire Original Android Development] ipdev:
The problem at least on my end is that I did NOT enable it and it is running regardless. Every now and then I get a Privacy Guard Notification Box but, seems I can ignore it or if need be, reboot and everything seems to run fine.

Edit. Only started with the latest build.
[Fire Original Android Development] ipdev:
My last post may have been a little confusing. I hope this may clarify it a bit.

Clean flash from FireOS 5.1.1

FlashFire-v0.72-20170913110731

FlashFire-v0.73-20170921123305

FlashFire-v0.73-20171001124337-B1

lineage-12.1-20180130-UNOFFICIAL-ford

lineage-12.1-20180315-UNOFFICIAL-ford

UPDATE-unSU-signed

SR5-SuperSU-v2.82-SR5-20171001224502

.gapps-config

open_gapps-arm-5.1-stock-20180315

No problems with the 0130 build. And the above mentioned files.

After toggling on, reboot, toggle off, reboot. I only get a stray Privacy Guard notification and I seem to be able to ignore the notification without issue. Sometimes I do need to reboot.

Not sure why Privacy Guard seems to be enabled on the 0315 build regardless of setup options but, it is for me.
[Fire Original Android Development] nirogu325:
Thing is, same as you, it never turns off. This behavior started in this March build.
[Fire Original Android Development] DB126:
Could be an upstream change or something that crept into the custom build for 5th gen Fire. [MENTION=5749760]ggow[/MENTION] might have a better read.

I have not updated to the March build yet and probably won't have time for a few days.

Could also be an interaction with SuperSU...although I tend to think not.
[Fire Original Android Development] ggow:
I'll take a look, perhaps a new build setting or something was introduced. The device setup remains the same.

Should have some time about mid week.
[Fire Original Android Development] andPS2:
there really seems to be something wrong with latest flashfire i guess i should have used the older version...

wiped cache and dalvik and flashed new version with flashfire

after reboot fire got stuck after amazon logo

second fire same procedure worked without any problems with twrp

p.s.

privacy guard really seems to be problematic as written here already

after turning it on rebooting turning it off again rebooting it still show messages beeing active

how to totally get rid of it?
[Fire Original Android Development] DB126:
Seems unrelated to the latest FlashFire build (0.73) as similar reports have floated in with older builds. Clearly a problem mounting/dismounting the system partition (where Lineage lives) according to FF logs.

I hope to spend a little time messing with the latest Lineage and FF builds for this device over the next day or two. Will surface any revelations should they occur.
[Fire Original Android Development] andPS2:
after reboot i cant unlock fire right away

i can see a message from privacy guard about system ui wanting to scan wifi

cant get to it

in advanced options of privacy guard i cant seem to set that permanently

under which category should list wifi be?

problems dont appear with dirty flashed rom ...
[Fire Original Android Development] nirogu325:
Same here. The developer will check on it mid-week.
[Fire Original Android Development] Neffy27:
Thank you for the update! Dirty flashed over Jan 30 with latest FF, no issues.
[Fire Original Android Development] Dakotalee24:
This may be a dumb question but what is the easiest way to overclock this tablet running the most recent update of LOS. And what is the highest/safest clock speed?
[Fire Original Android Development] nirogu325:
There are no custom kernels, meaning you can only toy around with stock frequencies.
[Fire Original Android Development] DB126:
So no joy installing via FF 0.73. Tried various sequences, options and components. All resulted in system partition mount/dismount issues stating either "not found" or "busy". Fortunately, could restore and reset fairly quickly using TWRP. Eventually gave up and did a simple dirty flash over Jan18 build via TWRP; all good now. Seems that is the only reliable technique for updating Lineage at present. Can't speak to Nexus.

Gut tells me this is a Lineage issue. Note Lineage partially boots before returning control to FlashFire. Seems it does something to the system partition that makes it unstable in FlashFire. As an aside, my device will not boot into Android "safe mode" when running Lineage. Hangs on the LOS boot logo. Don't know if the two are related.

As for Privacy Guard weirdness, I punted and installed SuperSU 2.82 SR5 after disabling native root manager. Problem solved.

I feel bad for the vast majority of 5th gen owners who can not boot a custom recovery (TWRP). Of course, there is a much larger community that can't root and thus enjoy the liberation that comes with custom ROMs. Whittling down to a niche community that can leverage the full capabilities of this device (ie: those rocking 5.0.x bootloaders). At least when it comes to Lineage.
[Fire Original Android Development] nirogu325:
Weird that installing SuperSU solved it for you. I always install that exact build as soon as I flash the ROM and had no such luck. The lockscreen lag provoked by the Privacy Guard (Wi-Fi from SystemUI) prompt is no more here because luckily it popped up while I was using YouTube.
[Fire Original Android Development] DB126:
Although an unlikely culprit make sure root access is disabled under developer options (with SuperSU installed).
[Fire Original Android Development] nirogu325:
That's actually a good idea. I can't try it because I have already accepted all prompts and that's why it doesn't pop up anymore.
[Fire Original Android Development] riverstyxxx:
This is the second time both installs were a fail, the other time was January. I followed the instructions and just used the latest flashfire to flash the zip and do a quick cache delete and now the tablet won't go past the Amazon screen.

On the second tablet, I uninstalled the current flashfire and put 0.58 in. It wont even load, it gets to a few screens then closes out by itself. You know I hate to say it but I think development of this rom needs to be put out to pasture, It isn't upgrading like it used to.
[Fire Original Android Development] DB126:
Not sure what the future holds but I'll share my view: if you don't have an early 5th gen device that can boot TWRP it's probably best to stick with whatever build of Lineage is on the device. Unlikely there will be any feature/functionality enhancements on an Android base released in 2014. Security patches are nice but do little for this class of device if one practices good app/network hygiene. Routine updating just isn't worth the hassle if it involves reloading FireOS and starting from scratch (IMHO).
[Fire Original Android Development] riverstyxxx:
I'm surprised. I expected to hear a "It's your fault/use something else if you don't like it/you're obviously an idiot" . No, I can't do twrp and I dont feel like going through fireos and that kingroot app that takes 87 times to work. With all this bs, I'm probably just going to buy a new samsung tablet because I gave this group nearly four months to get something working and, if it hasn't happened yet it's probably not going to.
[Fire Original Android Development] DB126:
Not sure who "this group" is but if inferring the dedicated XDA contributors (as opposed to consumers) who volunteer copious time supporting this none-too-friendly platform then it might be best if you invested in a different device. Amazon brings to the table a low price point, non-standard hardware and locked down 'underpinnings' that make customization and ongoing maintenance a significant challenge. It is amazing the primary developer has hung around this long given the ridiculous hurdles! ROM upgrades are always optional; existing builds are not time limited. There are no upfront fees or ongoing maintenance costs. You can return to FireOS at anytime.

Rootable 5th gen Fires had a nice run and will continue to serve those who are willing to put up with its idiosyncrasies. Whether that be with a custom ROM or running good old FireOS as Amazon and mother nature intended.

"This group" owes you nothing. Good luck with those Sammys.
[Fire Original Android Development] andPS2:
disabling built in supersu and flashing supersu 2.82 didnt solve the problem with

privacy guard for me -> very often when i try to unlock fire i cant cause i see the privacy screen and cant allow or always allow

there must be some kinda workaround to totally disable privacy guard?
[Fire Original Android Development] DB126:
Tough one. TTBOMI there is no master switch beyond what is shown in the UI. Normally I'd suggest full wipes and a fresh install but that seems ill advised with Flashfire. A quick surf suggest this problem is present on other platforms and Lineage builds - although certainly not a common complaint.

I'm still running Lineage because it works (in my case) and I hate change for the sake of change. That said, if it acts up I'm off to Fire Nexus. The latter is not without a few warts but I have always leaned toward AOSP+Xposed when available. Lineage is does have the advantage of ready-to-rock right out of the box; Nexus needs a few 'adds' to make it awesome. :)
[Fire Original Android Development] nirogu325:
That particular prompt is SystemUI asking for WiFi access. It popped up randomly while using YouTube. Since then no more lockscreen issues. Use your tablet normally and pay attention because it happens randomly. OP said he'd check where the issue's coming from so we should hear from him anytime soon.
[Fire Original Android Development] DB126:
One of the more annoying characteristics of Privacy Guard is you can't toggle individual 'system' permissions - even in the advanced menu. Have to perform a master reset.

Here's a

potential

quick fix:

- access Privacy Guard; make sure WiFi is enabled/active

- toggle both switches to 'on'

- tap reset icon in upper right status bar; respond to confirmation dialog

- wait 10-30 sec; should get a prompt from Privacy Guard asking for permission to access WiFi

- respond 'yes' and tick the box that says 'remember this setting'

- toggle off Privacy Guard

Obviously you may have to repeat the above if there are other disruptive system level confirmations.
[Fire Original Android Development] nirogu325:
You did well on putting potential on bold because I tried that with reboots between and nope. Once you accept all prompts it throws at you, it doesn't bother you anymore. The single most annoying prompt is the one that mostly triggers randomly and that's the one "freezing" the lockscreen.
[Fire Original Android Development] ggow:
I have identified a couple of commits that looks to be the likely cause of the privacy guard issues.
[Fire Original Android Development] prisoner1969:
Wow. Need a pacifier? I mean really all that over a tablet that if you got it on sale cost you $35.00
[Fire Original Android Development] DB126:
OK - I'm out. :)

Interesting findings as I have yet to experience that pop-up except when self-induced. Well...it did happen after the initial LOS update which was quickly rectified by toggling Privacy Guard off, disabling root and subsequently flashing SuperSU via TWRP. I realize the last step isn't available to most but it's what I did. Regardless, installing SuperSU apparently didn't help [MENTION=3501296]andPS2[/MENTION] or [MENTION=3059141]nirogu325[/MENTION]. Strike 1.

Not sure why the master reset technique didn't work. Figured once you had accepted the initial WiFi access prompt it would suppress subsequent annoyances. Apparently there are multiple scenarios each of which require a definitive response (if I'm interpreting [MENTION=3059141]nirogu325[/MENTION]'s comments correctly). Strike 2.

Here's hoping the lead [MENTION=5749760]ggow[/MENTION] is pursuing pans out (likely a home run!).
[Fire Original Android Development] nirogu325:
Lmao it's good to pinpoint and look for possible solutions, it's part of what this forum is after all.
[Fire Original Android Development] andPS2:
the one freezing the lockscreen i cant get to turn off

with the reset i allowed both google and system to scan wifi

youtube doesnt trigger any screens for me

i'll just wait for ggow to find something ;)

problem only occured on fresh rom with dirty flash (with twrp) didn't arrise
[Fire Original Android Development] nirogu325:
Yeah, it happened randomly for me while using YouTube but the magic word is randomly. Guess I was sort of lucky.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 25 March 2018

- Fix privacy guard issue

- NOTE: I had to replicate the issue on a different tablet, the one I develop on with TWRP access did not show the issue.
[Fire Original Android Development] dood6017:
Is there a chance that this Fire will get Android 6/7?
[Fire Original Android Development] DB126:
Unlikely on 5th/7th gen hardware. 8th gen may come with FireOS v6 which is based on Android 6.01 or 7.1 depending on build. Whether those devices will be rootable (prerequisite to custom ROM) is an open question.
[Fire Original Android Development] Hallo32:
[MENTION=5749760]ggow[/MENTION]

Thanks for the work.

Any idea why ADB over wireless network is not working on the fire?
[Fire Original Android Development] andPS2:
thanks for the new version [MENTION=5749760]ggow[/MENTION]

dirty flashed with twrp

after resetting the settings under privacy guard no more hassles!
[Fire Original Android Development] ggow:
Will take a look before the next update. No idea for the moment, never tried to use it myself
[Fire Original Android Development] t3chwizard:
I am on the January 30 build,

Should I stick with this build until these issues are sorted out?
[Fire Original Android Development] ggow:
I've fixed the privacy guard issues, however there is still something still going on invoĺving flashfire. It's really up to you to update or not. Personally I would stick with the build you are on unless you are one of the luck ones that can use twrp.
[Fire Original Android Development] Ma4x:
Can i go from an pretty old cyanogenmod version to LineageOS with twrp?
[Fire Original Android Development] ggow:
As you have TWRP access I see no harm in trying. Take a backup in case you want to go back.

If it doesn't work, then you will need to do a clean installation.
[Fire Original Android Development] t3chwizard:
Anyone have any idea how to make this ROM deep sleep? I tried DisableService but I'm not sure if it really did anything. It seemed to be fine back in August I could be mistaken though.
[Fire Original Android Development] DB126:
Huh? My devices "deep sleep" just fine. 10-14 days on standby which is invoked minutes after screen off. Same behavior with all builds of this ROM since inception. Install a monitoring tool like BBS or GSAM to help identify app/components that are keeping the device awake. If no joy do a clean install.

Sidenote: Google Play Service has been know to invoke spontaneous insomnia in various devices for unknown reasons. Try clearing storage under settings->apps->Google Play Services followed by a reboot.
[Fire Original Android Development] nirogu325:
User can also go to Privacy Guard and turn off Google Play Service's Keep Awake toggle. Helps a lot.
[Fire Original Android Development] t3chwizard:
I solved it with DS battery saver and greenify along with DisableService I think.
[Fire Original Android Development] DB126:
Greenify is truly excellent for its simplicity, effectiveness (especially when augmented with Xposed) and reputation. DisableService is also a fine tool but note it has been superseded by My Android Tools (same developer). I would have serious reservations about retaining DS Battery Saver.