yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] DragonFire1024:
Unzip the tool. Extract the mrw folder and place a copy of it on your internal storage. Open a root shell after a successful root:

adb shell
su
sh /sdcard/mrw/root.sh

Make sure to accept any on screen permissions it asks.
[Fire Original Android Development] l3ullseye:
Cannot connect to PC in windows 10, it only shows USB charging no MTP, my Android Phone does connect to MTP with no problem

Thanks in advanced
[Fire Original Android Development] platypoid:
Try going to Device Manager and see what it says when you plug it in . I think there is driver file in Supertool so check that out .

https://xdaforums.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695

It has been awhile since I have done it but I know there was a folder with Amazon driver for this somewhere and after installing that Windows finds it no problem.
[Fire Original Android Development] l3ullseye:
It doesn't even appear in Device Manager :confused:
[Fire Original Android Development] Joe_bar68:
Hi, I would like to install the Lineage on my new Fire with FireOS 5.6.0.0 :( Someone can help me Flashfire requires root, but I do not find how to do it on my fire.

Thank you
[Fire Original Android Development] ggow:
New Build is Up

- Dated 02 June 2018

- ASB May 2018 patches (sec. string 2018-05-05)

- Android System Webview updated to M66

- Privacy Browser updated to version 2.9

- Use Cloudflare DNS 1.1.1.1 as default fallback (instead of Google's 8.8.8.8)
[Fire Original Android Development] platypoid:
You can only root some of the older versions of Fire - I don't think it is possible with yours. There are lists of the versions you can do on the forums so do a search in this topic or some of the others for a list.

Look in first two topics here

https://xdaforums.com/amazon-fire/help
[Fire Original Android Development] Joe_bar68:
Thanks, unfortunately it is the same information that I found around :(
[Fire Original Android Development] cybermcm:
I recently tried to install Magisk v16.0 instead of SuperSU (clean install Lineage 20180602) -> ended in a bootloop -> is this expected? Switched back to SuperSU which working fine...
[Fire Original Android Development] ggow:
Magisk needs to modify the boot.img and so this cannot work here on any ROM, because the bootloader is still locked.
[Fire Original Android Development] cybermcm:
Thanks, I didn't know that...
[Fire Original Android Development] cybermcm:
Another question (I'm not sure if this is related to this specific rom)...

I did a clean install via TWRP, then OpenGapps, SuperSU and xPosed. After that Link2SD to use my SDCard for Apps. Then restore from TitaniumBackup (only user apps). Everything works fine, except an error message after booting finishes: "There's an internal problem with your device, and it may be unstable until you factory data reset." Is this problem maybe related to my test with Magisk (which didn't work)? I read a few posts that with this error I've to edit /system/build.prop and /vendor/build.prop but I have no /vendor/build.prop file...

Can anyone point me to possible solution? sorry if this isn't related to this ROM, I'm not sure
[Fire Original Android Development] Neffy27:
Installed from previous build with FF Pro v73. No issues.
[Fire Original Android Development] wzhang5460:
Hi, I know in the description it says solely for Fire 2015 7''. Does anyone know if this will work with newer devices such as 2017 Fire 8''? I didn't see anything on the Lineage website regarding it.
[Fire Original Android Development] nirogu325:
What you see is what you get. You won't see it in LOS website because this is an unofficial build solely for the Fire 7.
[Fire Original Android Development] DB126:
In addition 7th gen Fire 7 and HD 8 can not be rooted (or bootloader unlocked) which is a prerequisite for installing a custom ROM.
[Fire Original Android Development] DB126:
Although posted in the Nexus thread I actually run with this on LOS at present. Helps mitigate wake lag due to swap (zram) thrashing.

https://xdaforums.com/amazon-fire/orig-development/rom-fire-nexus-rom-lmy49f-t3300714/post76745625
[Fire Original Android Development] riverstyxxx:
New build is up, oh great. They call this thing flashfire because this project is going down in flames. Don't update or you will regret it with several hours of wasted time.
[Fire Original Android Development] Ace42:
There's nothing wrong with the ROM. If you have problems with flashfire take it up with the developer, Ggow isn't the maintainer for FF. Therefore you can't expect them to guarantee full support.

Issues mostly (if not only) popup when flashfire comes into play. Those that can use twrp are doing just fine, so don't blame the project.

You can try using an older version of FF and change your kindle to an earlier date. Also, you don't have to update. Literally no one is forcing you to.
[Fire Original Android Development] srnoth:
And this is the craziness why we need to keep saying thank you [MENTION=5749760]ggow[/MENTION] .

I really hope this guy it trying to be humorous - for those of us who can update without issue, these updates are priceless. Keeps my silly $50 tablet relevant!

It's like people are being forced at gunpoint to update every time a new build is out :rolleyes::confused::laugh:
[Fire Original Android Development] nirogu325:
Been pretty silent lately but that's because my laptop broke so I cannot update the way I do with the journaling mods (for that I require TWRP and to boot that I need a computer). Still rooting for [MENTION=5749760]ggow[/MENTION] !
[Fire Original Android Development] DB126:
Guy is a perpetual crank. Just look at posts from Feb 13th, Mar 23rd and Apr 11th. No doubt had some bad experiences with this device when FlashFire started acting up. Now damaged goods. Take it from a penguin. :rolleyes:

As for updating Lineage builds, I suggest those who can not boot twrp either stay put or start fresh from FireOS. Updating Lineage from Lineage via FlashFire is a crap shoot with a high chance of unfavorable outcomes.

p.s. [MENTION=5749760]ggow[/MENTION] rocks!
[Fire Original Android Development] riverstyxxx:
You are aware that you contradicted yourself by calling me a "crank" while also agreeing that updating doesn't work, right? Nice pengy, real nice.
[Fire Original Android Development] srnoth:
Updating works just fine if you have TWRP access. Updating via a 3rd party app doesn't work well. Why are you bashing the ROM/Dev?

Go shout at Amazon (for locking your bootloader) or Flashfire (no longer under development).
[Fire Original Android Development] nirogu325:
I agree. There's simply no constructive criticism coming from that user.
[Fire Original Android Development] DB126:
No contradiction - attitude matters. Have a great day. :)
[Fire Original Android Development] DragonFire1024:
There are plenty of versions of this ROM that install flawlessly. For those having trouble, these updates are more for security patches. Since you need root to have this ROM, and have it with the ROM, I'm not sure why some are so insisted to update. Aside from security patches, what other benefits are there? If you don't have any issues with the ROM, there should be no real need to update.
[Fire Original Android Development] DB126:
Really nothing to do with ROM build/version; FlashFire (no longer developed/supported) is the primary bad boy among all the moving parts. I do agree with sentiment regarding incremental updates. If all is well leave it alone.
[Fire Original Android Development] ldeveraux:
But the XDA community are crazy obsessives. I MUST UPDATE!!! :p
[Fire Original Android Development] DragonFire1024:
I have had FF pro for sometime now. Usually the only time I experience issues related to the cluster FF is now in, is when I'm on stock on my HD 10 and have NOT flashed gapps. It seems to me, the best option is just to buy pro and the issues pretty much disappear when the play store is properly installed.
[Fire Original Android Development] DB126:
Special situation largely unrelated to the most common issues faced by members with the device relevant to THIS forum (rooted 5th gen Fire with bootloader build 5.11-5.3.1) when attempting to update a custom ROM such as Lineage 12.1 (THIS thread), Fire Nexus, etc. Purchasing the PRO version gets around the date-centric timebomb but adds no functionality or ability to deal with random system partition lockouts which is the crux of the problem.
[Fire Original Android Development] DragonFire1024:
I'm just saying. Buying pro helps a lot in my experience with it since this all happened.
[Fire Original Android Development] DB126:
I see no cause/effect relationship other than avoiding the date issue. However, serendipitous events continue to hold factual value in the eyes of many.

We'll agree to disagree on this one. Moving on ....

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

FWIW - flawless update via TWRP following the (my) usual best practice:

- backed up boot/data/system partitions

- wiped same partitions; left data partition untouched

- flashed latest Lineage, GApps (nano), SuperSu (2.82 SR5) and Xposed Framework zips

Longest delay entailed dalvik rebuild due to the anemic processor and poky storage. There was no reason to update...nor any reason not to given low time investment and viable fallback options if the wheels somehow fell off. Bessy is good for another round. :)
[Fire Original Android Development] obsidience:
DELETED
[Fire Original Android Development] ipdev:
I have been meaning to try this. When ever I sit down to do it, a different device seems to steal my time.

Yes it worked. Oddest flash I have done. Not sure if it's clean or dirty?

I'll try to keep this post short. I started from fireOS, backup and flashing from external SD card.

I made a new full FlashFire backup of fireOS. (SuperSU-SR5, FlashFire .73-B1, along with a few other apps.)

Installed and configured. l-12.1-20180504, SR5-SuperSU, open_gapps and quite a few other apps and settings. Then made a full ff backup.

Restored my newest fireOS backup. Full Wipe

Then Flashed l-12.1-20180602, SR5-SuperSU and open_gapps with little or no configuration.

Used adb to install FlashFire .73-B1 and then restored data and internal storage from my l-12.1-20180504 backup.

Wipe

-3rd party

-Dalvik

-Internal storage

-Cache partition

Restore

-Data

-Internal Storage

Internal storage was not restored, expected that, so I ran ff again to restore internal storage.

Wipe

-3rd party

-Dalvik

-Cache partition

Restore

-Internal Storage

Note:

Before someone chimes in.

It takes longer and seems more complicated to describe the steps than they actually are. I could have simply tested from my older backups but, I wanted to test with the most current files. And yes I always make full backups.
[Fire Original Android Development] DB126:
Excellent methodolgy, execution and explaination. :)
[Fire Original Android Development] _bor_:
microg

Hello,

is there any success story about installing/using microg on the device?
[Fire Original Android Development] chillma:
I never get rid of the battery drain after installing microg even after all the gcm apps were registered. Maybe I did something wrong but it's possible. In the end I have to realize what type of tablet the Fire is. From my personal experience this rom works very very good without microg or gapps. Have a trust source for apps and install only the stuff you really need :good:
[Fire Original Android Development] DB126:
Exactly. From a battery endurance perspective MicroG is unnecessary on this device (and most others) with good hygiene and thoughtful app selection. MicroG has other characteristics that appeal to various communities. That said, one must accept a higher maintenance level to realize the supposed benefits. Bigger fish to fry IMHO.
[Fire Original Android Development] _bor_:
I suppose to use at least one application which requires latest gapps (some features like pushing).

But I have only last CM on the device and very old gapps.

So wondering which way to chose:

1. update to latest Lineage and gapps

2. update to latest Lineage and MicroG

3. update to MicroG on current CM (is it possible?)

4. update to latest gapps (only)

Please advise.
[Fire Original Android Development] DB126:
Most conservative option is #4; going any other route will likely entail a trip through FireOS (with associated brick potential) and hours of work. Life is much easier if your device can boot TWRP but that is highly unlikely unless you purchased an early gen device (late 2015 or early 2016).

Best resource is reviewing past threads. No one is going to hold your hand given age of device, limited utility and complexities involved.
[Fire Original Android Development] amazon_noob:
[ deleted ]
[Fire Original Android Development] amazon_noob:
Bricked my Amazon Fire

Today I tried to update my Amazon Fire with the latest LineageOS update using FlashFire. Unfortunately it went wrong and my device is bricked now. It is stuck at the Amazon logo. I can get into "Fastboot mode", but trying to reboot it via "fastboot reboot" didn't work.

I liked the device, any ideas how to get it back to life?
[Fire Original Android Development] desilynn79:
flashfire

i dont have twrp it seem or any other custom recovery.

flashfire keeps force closing but i want to update to 5.3.1 can someone please help me.

i rooted when i first got the tablet with rootjunky supertool

i am running 5.1.1 right now with the nexus rom

build number says lp-fire-nexus-rom - 20161124@ggow

kernel version is 3.10.54+
[Fire Original Android Development] Neffy27:
You are going to have to restore to stock.

https://xdaforums.com/amazon-fire/general/howto-how-to-restore-frimware-device-t3238740
[Fire Original Android Development] amazon_noob:
Thanks for the reply.

I got into recovery mode. What is my best option?

Just "Wipe data / factory reset" or should I try to sideload via ADB?
[Fire Original Android Development] amazon_noob:
You could set the date back to 2013.

It worked for me in May.

But be careful, I bricked my device yesterday.
[Fire Original Android Development] DB126:
Sideload. Be sure to use the same version of FireOS that was previously loaded on your device. Downgrading can yield a brick; upgrading can result in a permanent loss of root capability.

---------- Post added at 12:43 PM ---------- Previous post was at 12:40 PM ----------

Leave it alone until you have a better understanding of what you have and where you want to go. Attempting to mess with what you don't understand will likely lead to an unfortunate outcome.
[Fire Original Android Development] amazon_noob:
I'm not sure what version of FireOS I used when I replaced it with CM 12.1.

So factory reset is the best option in my case?
[Fire Original Android Development] Reynald0:
I saw this:

Changelog / Release Notes

23 June 2018

- ASB June 2018 patches (sec. string 2018-06-05)

- Privacy Browser updated to version 2.10

- Privacy-default setting (at clean install): Sensitive information is hidden on the lock screen

But is not online, was this version retired?

Thanks.
[Fire Original Android Development] amazon_noob:
https://www.androidfilehost.com/?w=files&flid=200071

(Link is hidden behind the "Show content" button.)
[Fire Original Android Development] ms372591:
The latest on the above site is lineage-12.1-20180602-UNOFFICIAL-ford.zip
[Fire Original Android Development] desilynn79:
i asked for help because no matter which version of flashfire i try to use it force closes when checking for pro. i dont seem to have a custom recovery like twrp, which i would like to install and i know is possible just cant seem to find the correct post about doing so.

this is not my first rodeo with rooting, flashing, bricking or recovering a soft bricked device. could someone guide me how to get twrp on my device rather than tell me to leave it alone?
[Fire Original Android Development] amazon_noob:
Do you know about the timebomb in FF?
[Fire Original Android Development] desilynn79:
timebomb??? no

ff closes before it fully starts. i cant do anything in it
[Fire Original Android Development] amazon_noob:
You have to set the date to an earlier year. Try 2013.
[Fire Original Android Development] desilynn79:
how can i do that if flashfire closes ever ytime i open it and can do nothing in it?
[Fire Original Android Development] amazon_noob:
Change the date on your device, not in FF.
[Fire Original Android Development] DB126:
A factory reset will likely yield no positive benefit if running a custom ROM. It certainly won't restore FireOS. If uncertain of previous version sideload 5.3.1; don't allow it to auto-uodate to a higher build if interested in retaining root capability and/or installing custom ROMs (which require root). Keep WiFi off; do not register device w/Amazon during initialization.
[Fire Original Android Development] desilynn79:
ok so how do i do that? i have never had to do that before
[Fire Original Android Development] DB126:
Clearly your first rodeo with Amazon devices in general and this one in particular. No twrp or custom recovery if bootloader version is greater than 5.01 which it almost certainly is. No Flashfire unless device is rooted and set to a date prior to April 1st, 2018 (v0.73). Lots of documentation around all these points. See index thread for links.
[Fire Original Android Development] desilynn79:
also i found this (amazon fire utility) http://www.android.gs/root-kindle-fire-install-twrp-recovery-using-kf-utility/

but im already rooted...

wondered if it would actually install twrp but dont wanna try without asking first and having full use of my computer for a while since we use it for entertainment too lol..

we dont watch tv so this means im sharing the computer with others on the regular

i appreciate you trying to help me amazon_noob
[Fire Original Android Development] Ace42:
In settings...find Date & time. Then set the date manually.

Also, every kindle can't use TWRP. If your FireOS version was 5.1.1 or higher a recovery can't be used.
[Fire Original Android Development] DB126:
Recent FireOS builds will not allow date to be set manually. Need to use adb or purchase FF pro on another device that has Play Store access.
[Fire Original Android Development] Ace42:
FF is such a pain, glad I don't need to touch it. :)
[Fire Original Android Development] desilynn79:
yes this is my first and only amazon device.

i have had flashfire on the device before but now it just force closes. device IS ROOTED . as i said i rooted when i first got it years ago with root junkies SUPERTOOL

im running a custom rom now... android version is 5.1.1, kernel version is 3.10.54+ build@ip-10-11-19-170#1, android security patch level is 11-01-2016, build number lp-fire-nexus-rom-20161124@ggow

this all came from the about tablet screen

cant remeber if i updated before or after rooting, been too long. pretty sure it was before updating i know i diabled otas...

i dont have the ads on my lockscreen etc... disabled that too.

i dont use the tablet much but thats because its sooooo slow... wanting to update to the 5.3.1 as maintains root people say runs smoother etc

then maybe the dinosaur would get some use... especially since it is backup entertainment/ research device when needed and the computer is in use for whatever reason, ya feel me

i have seemn videos of using adb to run twrp and i havent tried this as im not sure its worth a shot.

i do have adb on the computer but i havent ever had to play with it too much and im very timid here... i have developer options and usb debugging is enabled computer has permission and sees it and they do communicate. thats about all i have tried to do in adb...

any further assistance with this would be helpful. thank you. i am looking into getting the 10 in tab as well soooo... i need to get familiar with amazon devices.

im kinda partial to samsung devices, at least for my phone anyway.

thanks davey

---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------

ok so heres an update and then someone please tell me what my options are...

I CAN AND DID MANUALLY SET MY DATE AND TIME

have set it to jan 1 2013

hopefully maybe the fact i can change my date and time will give some clues, flashfire still force closes..... dont have the pro version but maybe willing to purchase, just afraid im still going to have the force close issue...

thanks yall
[Fire Original Android Development] amazon_noob:
It worked!

Thank you very much!
[Fire Original Android Development] DB126:
The device is slow due to a relatively pokey processor (CPU) and limited memory (RAM). There really isn't a way to fix the problem - especially if the device used for multitasking or browsing 'rich' web pages. Installing a different ROM or ROM version won't solve the problem. Reports of FireOS 5.3.1 being faster/smoother are either relative to some other slow build or a snapshot assessment based on a specific app portfolio that likely does not match yours. This device works best performing a single, non-resource intensive, content consumption task such as email, lite browsing, viewing videos, etc.

I strongly suggest you NOT attempt to update the current ROM (Fire Nexus 20161124) to a more recent build as there have been numerous reports of less than favorable outcomes. You could reload FireOS but that will almost certainly yield slower performance due to a large number of pre-installed Amazon apps that launch at boot and continuously run in the background chewing up precious CPU and memory.

You best bet IMO is to enter stock recovery and perform a 'factory reset'. This will remove all personal content, flush caches and effectively return the device to the state it was in just after installing Fire Nexus. See what that buys you.
[Fire Original Android Development] ggow:
I haven't had a chance to test and release it yet.

I usually put a running list of any changes made in the change log whilst putting the next build together.
[Fire Original Android Development] amazon_noob:
I am now on 5.3.1. and would like to root the tablet again. i think I was on 5.1.1. before, because I used Supertool to root it. But anyway I can't go back if I understand it correctly.

So I searched for a method to root it again but only found the Google sheet which said "Kingroot". I installed it, but it seems not to work as intended. Is there an other way to root the 5th Gen?
[Fire Original Android Development] DB126:
Kingroot is the only reliable method. You'll need to toggle WiFi on for a brief period at the start of each run for the tool to download its payload. Be sure to flip WiFi off after 20-30 sec to avoid downloading the latest OTA updates which, if installed, will permently disable root access. KingRoot is relatively unsophisticated so you may need to run it multiple times before it identifies exploitable vulnerabilities. Good luck.
[Fire Original Android Development] skiwarz:
Anyone else been experiencing frequent crashes on the 2018 builds?

I'm not sure if it's caused by play services or caused by the os, but the symptom is my device basically does a "soft reboot" roughly every 10-15 minutes while in use. If I let it sit for a couple hours it calms down and stays asleep.

Occurred with the january and june builds, clean installs from fireos 5.3.1
[Fire Original Android Development] chillma:
Are you using gapps or microg? I had a similar problem with microg.
[Fire Original Android Development] skiwarz:
Gapps from opengapps.org
[Fire Original Android Development] DB126:
Nope. Never had an spontaneous reboot with this device. Could be a heat or other hardware issue. Run with 5.3.1 for a few days to confirm your theory.
[Fire Original Android Development] skiwarz:
Looks like it is probably due to the play framework. I did a clean reinstall without gapps and it seems to be working fine. No more crashes.
[Fire Original Android Development] yakov116:
Me! the last 2 weeks
[Fire Original Android Development] DB126:
Try snagging the latest OpenGapps Nano build (arm/5.1).
[Fire Original Android Development] skiwarz:
I had been using the pico build. Might try the nano today.