yashsingh1/xdaforums huggingface dataset:
[Fire Original Android Development] steve8x8:
Your Galaxy is running fireOS?
[Fire Original Android Development] DB126:
Believe he's stating FlashFire 0.73 doesn't work properly on his Galaxy running a 'native' 5.1.1 based Android ROM (not FireOS).
[Fire Original Android Development] DragonFire1024:
Correct. In order to see if older versions have the same effect, I need to go to an older SuperSU version. Like the latest FlashFire only works with latest superSu and as low as 2.79. unfortunately it's hard to downgrade on Galaxy devices. Chances are I'd loose root before being able to test the theory.
[Fire Original Android Development] ldeveraux:
So I have everything 99% working on the 1202 build. Fit some reason the Wi-Fi keeps cutting out and nothing I can do to restore it. Would a dirty ROM flash in Flashfire fix this? I'd there another solution? It's gotten so I can't really use the tablet anymore...
[Fire Original Android Development] DB126:
A dirty flash probably won't make much difference; wiping the system partition (retaining data) might be more effective. Also wipe dalvik and cache.

A few other ideas:

- try a full power off; wait 5 sec and then restart

- remove and re-add AP profile(s)

- utilities like L Speed can mess with network configs; a full OS reload and kernel reset is sometimes needed

- also try disabling bluetooth to see if that makes a difference (sometimes helps on 3 gen HDX models)
[Fire Original Android Development] ldeveraux:
I don't have BT active, and don't use any network config apps etc. How to wipe the system partition without wiping data? Do I have to boot to TWRP for that, then it rebuilds itself? Haven't done that in a while. REALLY don't want to have to wipe and fresh install for the 3rd time in a month :D
[Fire Original Android Development] DB126:
While possible via FlashFire booting TWRP is the the best option by far:

- download latest Lineage and GAaps (nano) zips; store on SD card

- refresh your memory/skills on booting TWRP (ask if you need help)

- once in TWRP backup up your current config; save to external SD card

- use the advanced wipe option to clear the system, cache and dalvik partitions

- do not wipe data partition

- use install option to flash Lineage + GAaps

- reboot and (hopefully) enjoy stabilized WiFi connectivity
[Fire Original Android Development] chaosp:
I just made an update from a previous LineageOS version (not sure, I suppose it was the one from September) to the 20171202 via FlashFire (including wipe of dalvik cache and cache) but now the tablet stucks with reoccuring popup "the process com.android.phone has been ended" (in German) and when I manage to start SuperSU it says it's not rooted anymore.

Any idea, how to solve the problem?

Should I try to reinstall the rom via fastboot mode/TWRP? (>> not possible, see edit!)

Should I do a factory reset in Android itself?

Please help!

- edit -

I just tried to boot TWRP in fastboot mode, but this is not possible:

c:\FTV>fastboot boot c:\adb\TWRP_Fire_2.8.7.0_adb.img
downloading 'boot.img'...
OKAY [ 0.260s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.266s

- edit 2 -

as mentioned before, it's not rooted anymore, so I can't start/user FlashFire again.

But it seems, that the ROM has been flashed ... somehow (see attached screenshot; it was not easy to do one without the popup)
[Fire Original Android Development] DB126:
It would seem the bootloader on your device is version 5.1.1 or higher which does not permit booting TWRP. In that case you will need to reload FireOS and start over. Go with FireOS 5.3.1 if uncertain what build was previously on the device. Be sure to maintain network isolation (WiFi OFF!) except while rooting to avoid taking an unwanted OTA update.

So why did this happen? One possibility is you may have neglected to include the recommended wipes and/or positioned them incorrectly in the FlashFire operational sequence. Another possibility is the presence of SuperSU binaries which can create havoc when updating Lollipop based ROMs that include their own root solution like Lineage 12.1. While I prefer SuperSU to other root manager/solution and have it most of my devices I do NOT use it with this ROM and device due to past difficulties with spontaneously loosing root (despite having the ability to boot TWRP and fix such anomalies...annoyances that I don't care to deal with).
[Fire Original Android Development] chaosp:
I just found the log file of the FlashFire in the internal storage. See attachment!

In it I can see, that I had the CustomRom version from July.

I'm pretty sure, that I managed to prevent the tablet from doing updates of the original Rom via OTA all the time, since I have it (February 2016).

Any disadvantage if I flash it with FireOS 5.3.1 now?

And is it the way described here? https://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

Or can I try to root the tablet now for starting FlashFire again and do a fresh flash again (with system wipe)?

- edit -

Damn! I see it now. It was not this CustomRom before on it but the Fire Nexus Rom. I idiot, clicked on the wrong thread (in the thread list) and did not recognize it ... even not during reading the last pages, the download, ....

Anyway. please see my above question.

- edit 2 -

Now it is stucking in the amazon boot logo after some tries. I have really to revover it via recovery.

And I discovered somebody with very similar situation (four weeks ago) in the unbrick thread, so I'll continue there: https://xdaforums.com/showpost.php?p=74741017&postcount=385
[Fire Original Android Development] ldeveraux:
OK, did this, not sure if it's a related problem. I have it sitting on a desk charging and updating from Play Store. I left it for a few minutes, then turned the screen back on to no WIFI. I checked settings and "Keep WIFI on during sleep" is set to always. Any other reason it might be going off?
[Fire Original Android Development] DB126:
This appears to be kernel related vs a ROM issue as others have noted WiFi drop outs when the device sleeps regardless of setting. I can't speak from experience as I am happy with that behavior (on this device). Amazon is pretty aggressive with screen off power management so I would be surprised if the 'feature' is baked into lower level firmware.
[Fire Original Android Development] Khaeroth:
Hi friends. I'm the guy who was about to sideload the FireOS rom. I found a fix without doing it.

I tried installing the root through the last version of the SuperTool and it worked!

I used the FireOS 5.1.1 option, even when I was on LineageOS. Now I flashed through Flash Fire and everything is working without problems.

Thanks for all your replies.
[Fire Original Android Development] tekanina:
While attempting to flash the latest build using twrp 3.0.2.1 it appears that my cache partion may be corrupted. I've tried the repair option with receiving an error along with an error trying to wipe cache saying error no such device. I'm coming from a build of cm 12.1 from over a year ago. I'm on the original bootloader as I've never updated and device was purchased around the release date. I know from using Nexus devices that I would just reflash the factory image to fix this sort of thing but I have no idea on this device. Any help would be appreciated.
[Fire Original Android Development] huffmybrd:
wheres the link to 12/17/2017 version? cant find it on AFH
[Fire Original Android Development] ldeveraux:
All releases to the Lineage ROM for this device are released here. There's no official build that's updated.
[Fire Original Android Development] huffmybrd:
https://xdaforums.com/amazon-fire/o...neage-12-1-t3639447/post74875718#post74875718
[Fire Original Android Development] DB126:
Pulled after various issues reported by several members (including self). Root cause undetermined; likely NOT the build. Suspect [MENTION=5749760]ggow[/MENTION] will provide a new build when when the next round of security updates are released.

https://xdaforums.com/amazon-fire/orig-development/rom-lineage-12-1-t3639447/post74890561
[Fire Original Android Development] huffmybrd:
totally skipped page 42 when i was reading through the thread lol. thanks!
[Fire Original Android Development] DB126:
Must have got distracted by the "Summer of '42"... :)
[Fire Original Android Development] DB126:
Do you see any results in TWRP navigating the following (image the screen if possible): Wipe->Advanced Wipe->{tick cache}->Repair or Change File Systems? File system should be ext4 with a size ~242MB.

There may be a way to recreate/reformat the cache partition from TWRP v3. Normally this would be done from Fastboot but I suspect Amazon crippled the required commands...even on the old 5.0.x bootloader.
[Fire Original Android Development] WaywardOne:
Hi, I would love to try this on my Fire, but FlashFire says "Root was found, but could not be acquired!" I'm currently running FireOS 5.1.1, rooted with KingRoot. What might my options be? I ran into some issues in the past replacing KingRoot with SuperSU, am I going to have to try that again?
[Fire Original Android Development] DB126:
FlashFire requires SuperSU binaries. You'll need to switch root managers (KingRoot -> SuperSU). The SuperTool automates this process; suggest going that route as KingRoot resists removal.
[Fire Original Android Development] TheLoonyRebel:
Wouldn't SuperSUMe work as well to move over to SuperSU?
[Fire Original Android Development] DB126:
Variable results using that app. Recall previous posters issues. Better to stick with the SuperTool.
[Fire Original Android Development] WaywardOne:
Thank you, after wrestling with KingRoot I finally got it replaced with SuperSU. Now, however, when I try to flash everything, FlashFire says "Loading" and just stays there. I already reset the device, perhaps I should sideload the same version of FireOS it's running to make sure it's completely fresh?
[Fire Original Android Development] DB126:
Usually this symptom is tied to a root snafu and associated tale of woe. Side loading FireOS via stock recovery entails redoing everything (including root) but is probably the most expeditious path to a better place unless you enjoy repeatedly dunking your head into a pot of boiling oil.

Be sure to maintain network isolation until OTA updates are blocked.
[Fire Original Android Development] ggow:
Heads Up

I am testing the next release which has been rebased on https://github.com/cm12-amami.

I thought it would be worth mentioning in advance that a clean install is recommended and may be required to function correctly.

It's looking good so far, will release when I'm happy enough with it.
[Fire Original Android Development] DB126:
Might consider a new thread if a clean install is required and the outcome of a dirty flash yields an unstable device and FireOS reload.

I know that would never happen as everyone always reads/follows directions. Just looking out for that one poor chap ....
[Fire Original Android Development] nirogu325:
He can always put it in red big bold letters or put the download link behind a hidden tag that boldly states what it requires. That way, user is forced to read in order to access the link.
[Fire Original Android Development] DB126:
I heard the figurative 'poor chap' is both color blind and illiterate. :)
[Fire Original Android Development] borisboing:
5.1.1 devices have no need to use kingroot, you can achieve temp root with just adb which will allow you to install SuperSU.

My advice would be to sideload 5.1.1 fresh, follow https://xdaforums.com/amazon-fire/orig-development/root-t3272362 to root, then install flashfire.

Will take a few mins and you'll not have to deal with the horror that is kingroot.
[Fire Original Android Development] DB126:
Results from temp root method appear muddled. It is important to follow OP carefully and not get drawn into bootloader component munging which will yield a non-recoverable brick. If one is comfortable with ADB commands and operating at a command prompt the linked method may be more appealing.

That said, KingRoot is fast and effective on FireOS 5.1.1 as is transitioning to SuperSU using the SuperTool as a vehicle to accomplish both.

I agree KingRoot (and similar derivatives) are borderline malware but it really doesn't matter if the ultimate goal is replacing FireOS with a custom ROM.
[Fire Original Android Development] t3chwizard:
I use flashfire without SuperSU I'm confused
[Fire Original Android Development] DB126:
If you used the SuperTool to root it likely (silently) replaced KingRoot binaries with SuperSu equivalents.
[Fire Original Android Development] t3chwizard:
I flashed a ROM using the TWRP that booted over fastboot back when I got my tablet.
[Fire Original Android Development] DB126:
Well yes, that's an entirely process made possible by having an early build device with a vulnerable bootloader. Not the same as starting from FireOS.
[Fire Original Android Development] k8500:
So I got a chance to buy a cheap Fire 7 / 5th generation, but I have no idea what FireOS version it comes with. I've read the opening post, but I'm having doubts - will FlashFire really work regardless of the current installed FireOS version? And, will I have root in Lineage OS?
[Fire Original Android Development] DB126:
Device must be running FireOS 5.3.1 or lower to secure root which is a prerequisite for using FlashFire which is used to install custom ROMs. Higher builds of FireOS can NOT be rolled back to obtain root. If you were fortunate enough to get a device running FireOS 5.0.x a custom ROM can be installed w/o first obtaining root. You should query the seller regarding the FireOS build before purchasing. If you buy the device be sure to maintain network isolation (WiFi off) until rooted and OTA updates blocked as FireOS will quickly update itself to the latest build which likely will not be rootable.
[Fire Original Android Development] WaywardOne:
So I finally got it flashed correctly, and I must say I am extremely impressed with the performance as well as the ROM itself. Thank you for your help :) I do have another question though- if I ever wanted to, would I be able to safely go back to Fire OS 5.1.1 (the version it had last)? And the same for my other Fire, running 5.3.1. Would that one be able to go back to 5.3.1 as well?
[Fire Original Android Development] DB126:
Great - glad you made it. :)

Yes, FireOS 5.3.1 can be restored to either device with relative ease. However, FireOS 5.1.1 can only be restored to a device that was previously running 5.1.1 or lower. Attempting to apply that build to a device that was previously running FireOS 5.1.2 or higher will result in a non-recoverable brick.
[Fire Original Android Development] ggow:
New Build is Up

- Dated 28 January 2018

- Rebase ROM on https://github.com/cm12-amami - Thanks [MENTION=7929484]MSe1969[/MENTION]

- Includes security patches up to Jan 2018

- A clean install is recommended and may be required to function correctly.
[Fire Original Android Development] Old old man:
Thanks for your updated rom.

I did a clean installation. It stop on Amazon logo and not go any further.
[Fire Original Android Development] ggow:
That's strange, working fine here - flashed with TWRP.

FlashFire 0.73 might be problematic for our device. I would recommend trying version 0.58. Try and let me know what happens.

What version of FireOS was on your device prior to flashing a custom ROM?
[Fire Original Android Development] Old old man:
I did with flashfire 0.73
[Fire Original Android Development] ggow:
Try flashfire 0.58 is what I meant.

What was your original FireOS version?
[Fire Original Android Development] Old old man:
I don't remember the original fireos version. I will try 0.58 once I unblock the fire.
[Fire Original Android Development] ipdev:
Using FlashFire .60, coming from lineage-12.1-20171202-UNOFFICIAL-ford, I got the same mounting errors as before. failed to mount /dev/block/platform/mtk-msdc.0/by-name/system at /system: Device or resource busy symlink: some symlinks failed

When rebooted, it was stuck on the Amazon splash screen.

Using FlashFire .73(v0.73-20171001124337-B1), coming from update-kindle-global-37.5.4.1_user_541112720, I did not show errors but, defiantly a broken install. (Rebooted straight to desktop, no initial setup, lock screen, dev options, root..)

I was able to root it, install FlashFire .58 and restore a ff stock backup.

(Stock fireOS 5.1.1 with nothing removed. Only SuperSU 2.46 and FlashFire v.58 added.)

From there I used ff v0.58 to install lineage-12.1-20180128-UNOFFICIAL-ford. No errors.

:) Happily running the current build.

Note: I flashed the same files in the same order with all 3 versions of ff I tried. To be able to use FlashFire v0.58 you need to set your date back. (Hey I'm back in January 2017 :laugh: )
[Fire Original Android Development] Old old man:
Good to heard you work it out.

I did some stupid thing. I can't get to recovery menu by push the volume down and power button. Any suggestion? Thanks
[Fire Original Android Development] ipdev:
If you can get into fastboot mode try

fastboot oem reboot-recovery

I know that works with 5.1.1 devices. (Not sure beyond.)
[Fire Original Android Development] cry-o-nic:
Is it just me or is root access missing in the developer options?
[Fire Original Android Development] Old old man:
Thanks for your fast response.

I can't turn on adb or fastboot on the tablet any more. My PC doesn't recognize fire.
[Fire Original Android Development] Hallo32:
[MENTION=5749760]ggow[/MENTION]

Can you give any background information why you rebased the rom?

---------- Post added at 01:56 AM ---------- Previous post was at 01:54 AM ----------

Is the fire listetd on the device manager?

Are you hearing a plugin/remove sound?
[Fire Original Android Development] Old old man:
I can heard sound on off once I plug tablet to PC (detect USB device). It seem reset all over again. Don't have chance boot to recovery menu .
[Fire Original Android Development] Hallo32:
Sounds like a boot loop for me.

Can you see which device is detected by windows?
[Fire Original Android Development] Old old man:
Not really .
[Fire Original Android Development] micgeb:
I have make a dirty installation and all works fine. Only the rom is not prepared for root. But Kingroot will work. Ty

I installed the rom with flashfire

Edit:

Kingroot don't work. Now I must go back to stock rom.
[Fire Original Android Development] ipdev:
I use macOS. (only boot into windows if need be ;) ) I have noticed with some devices, it makes a difference if I plug the usb cable into my laptop first then the device, or device then laptop.

If the device doesn't go into fastboot (volume key closest to power button + power button) or recovery (volume key furthest away from power button + power button)

I hate to say it but, it reminds me of when I bricked a fire 8. Don't flash when you are tired. :eek:
[Fire Original Android Development] ggow:
Ok, it seems changes introduced in later versions of flashfire may have broken it for our device.

Flashfire 0.58 worked good for my other tablet where as the latest gave me a broken install or stuck at the Amazon logo
[Fire Original Android Development] ggow:
https://xdaforums.com/showpost.php?p=74971734&postcount=443

The bootloop problems that we have been experiencing of late I think can be attributed to later versions of flashfire. Need more datapoints to confirm though.

I recommend we stick to version 0.58 of flashfire for the Amazon Fire 2015

EDIT: I have updated the OP to recommend using FlashFire 0.58.
[Fire Original Android Development] Hallo32:
I must have missed the posting. :D
[Fire Original Android Development] xpo:
Trying clean install of 28JAN over previous Linage 12.1 via FF 0.58:

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

symlink: some symlinks failed
​

Reboot stops on Amazon logo. Repair to factory ROM through adb was successful.
[Fire Original Android Development] ggow:
I'll look at this later today when at home, didn't see this error myself but will check my logs and repeat flash from prior version
[Fire Original Android Development] DB126:
For the fortunate few who can boot TWRP: A 'dirty' flash (ROM only; no GAaps, SuperSU, Xposed, etc.) from 20171202 to 20180128 proceeded without drama. Be sure to wipe cache/dalvik as advised. All apps and and data remained intact and usable.

For everyone else: Advise waiting for [MENTION=631273]Chainfire[/MENTION] (FlashFire developer) to return from sabbatical to assist [MENTION=5749760]ggow[/MENTION] and many others sort issues with the latest builds. My attempts to clean flash 20180128 via FlashFire 0.73 and 0.58 were unsuccessful on a fully wiped device.

Unless I'm mistaken there are no 'must have' features in 20180128 nor anything wrong with prior builds. Resist the temptation to bork your device and loose hours of your life putting Humpty Dumpty back together again.

Edit: You'll probably want to included a refreshed GApps package and Xposed Framework (if applicable) to keep everything tidy and working smoothly. My point in excluding them was to demonstrate the viability of a 'dirty' flash coming from a pre-2018 build.
[Fire Original Android Development] TheSpaceMoose:
regain lost root access

I installed Lineage-12-1 for the first time and lost root. I'm guessing by installing SuperSU via Play store.

My goal is to regain root. I'd like to make sure that I have the correct process to regain it. (When I go to Developer Options, there is no option showing for Root Access.)

1) Since I have TWRP access, am I correct that I don't need to start with FireOS again?

2) My understanding from reading through this thread is that I can boot to TWRP and flash the following from zip files:

lineage-12-1.zip

open-gapps-nano.zip

SuperSU.zip

Is that correct? And if so, what version of SuperSU?
[Fire Original Android Development] DB126:
Correct on all items. Recommendations:

- wipe system partition prior to reinstall

- go with SuperSU 2.76 (available via APKMirror)

- consider NOT flashing SuperSU and utilizing native Lineage root manager as it avoids many headaches associated w/SuperSU on Android 5.x based ROMs (including spontaneous loss of root); if you opt for 2.76 the Play Store will nag to upgrade...and may do so at some point w/o your permission

If still no joy you may need to take additional measures to fully uninstall the borked version of SuperSU. Use the unSU script posted here. Then give strong consideration to 3rd bullet (above).
[Fire Original Android Development] TheSpaceMoose:
Still not showing root.

My procedure was:

USB cable connecting Fire to PC.

On PC, use SuperTool script to boot to fastboot then custom recovery: twrp v2.8.7.0

Select partitions to wipe: (ones I selected with X)

X Dalvik cache

X cache

X data

internal storage

X system

micro SD

USB-OTG

Then install:

lineage-12.1-20180128-UNOFFICIAL-ford.zip

open_gapps-arm-5.1-nano-20180128.zip

Reboot, go thru initialization, go to Settings -> About, multi-tap build to unlock Developer options

Go to Developer Options (tried again after another reboot)

No option for Root.

My understanding is that it's supposed to be just below "Enable Bluetooth HCI snoop log". Mine just has Process Stats and Update Cyanogen recovery, before the next sub-heading of Debugging.

Any suggestions? Anything else I should try in the TWRP menu? Did I miss something?
[Fire Original Android Development] DB126:
You won't find a root option in the developer menu (that was only in CM). Have you tried to use an application that requires root? Lineage Privacy Manager should prompt for permission if root access is requested.