yashsingh1/xdaforums huggingface dataset:
[Fire General] ogpog:
Hi, yes thanks for that. I also worked it out once I realised that SuperTool worked on Linux now. FWIW there were a few differences between the latest mrw from here (2.4. I presume this is the original source) and the one in the Supertool from here (2016-10-06). I don't know the signiicance of them but here is a diff for anyone interested:

< = Supertool version
> = W0lfdroid version (original)

3a4
> echo ---------- Made By : Mr.W0lf ----------
8d8
< am kill com.cafeteam.user
17c17
< cat /sdcard/mrw/busybox > /system/bin/busybox
---
> cat sdcard/mrw/busybox > /system/bin/busybox
43,44d42
< rm -r /data/app/com.cafeteam.user-1 >/dev/null 2>&1
< rm -r /data/data/com.cafeteam.user
78,79d75
< echo the screen freezers here just close it and restart the device
< echo after making sure that supersu app has been opened and updated
81d76
< rm -r /system/app/Cafeuser
84d78
< rm -r /sdcard/Cafeuser
87c81
< exit
---
> sleep 2
[Fire General] jaggeddingo:
5.3.1 root success!!!

noob here thanks to wtfjajaja ! rootjunky, chainfire and you know how u r!!!!!!thx

used root junky's supertool to root 5.3.1

-do not register with amazon

-out of the box with 5.3.1 root junky's supertool successfully rooted tablet (kingroot version of root proccess)

-do not restart until flashfire and supersu and googleplay store installed

not sure where I'm going with this but all questions are welcome

i haven't tryed costom rom install yet; noticing small anomalies in flash fire, and i am afraid to commit.

apps that were granted root acces on 5.3.1:

twrp,flashfire,supersu......once root is obtained root junky supertool successfully block ota's,lock screen ads, update adb, novav launcher,etc all works

oh well nuff for now
[Fire General] trlkly:
Can I root without changing the OS? Some of the directions make it seem like it'll brick if I don't. I apologize if this has already been asked.

I'm used to this OS and I like the Amazon Underground apps.

Also, am I right that the safest way is to use the supertool?
[Fire General] DB126:
Absolutely! Use the SuperTool to root, block OTA updates and (perhaps) remove ads/bloat. Can even install the Google Play Store for access to a wider selection of apps. Nothing wrong with FireOS if you like the UI.
[Fire General] trlkly:
Cool. I'm currently a bit sick. But I learned the hard way that you need to root ASAP before a new OTA update makes it impossible. I can figure out how to do everything I want to do later.
[Fire General] Zebedez:
I used the supertool to root 5.31, and got stuck at the fire logo, thought it was bricked. Connected usb, windows warning came up MediaTek MT65XX PreLoader not installed, opened supertool ran test adb & fastboot, adb came up OK, but fastboot was just blank. Closed & reopened supertool and ran test again, this time they both worked & tablet rebooted OK. Reran install kingroot so I could get to next step & replace with su.

Tablet seems to run fine, but do I have to go back to stock because of that MediaTek MT65XX PreLoader warning or has everything sorted itself out, would like to install CM, pretty obvious I don't understand what I'm doing.

If I can go ahead & install CM do I have to back step anything. Have SuperSu & Flashfire already installed, manually removed leftover bits of kingroot, ota blocked & nova launcher.

Thanks for advice.
[Fire General] trlkly:
Got it, even without a System Restore! Ran into an interesting issue though. After I went ahead with the KingRoot replacement, I ran into an issue where the files it tried to delete said they didn't exist. I thought maybe this was normal, and waited, but the script hung. I tried to follow the instructions about updating the SuperSU binary and restarting, but no apps would stay open for longer than a few seconds. I barely got the Normal option chosen in SuperSU, and I eventually did an adb reboot* and, fortunately, the device did not brick. I restarted the SuperTool and chose to root again. Then it went through and worked properly. Then later I was prompted to update SuperSU,

The only thing I can think is that I have an app called SmartDimmer that I use to reduce the brightness lower than you can normally. I think it was set to turn on at boot. I only noticed after I got everything sorted out, and I find that I can't click on the Grant button unless I have it turned off.

*adb reboot means opening up a new Command Prompt, changing to the same directory as the SuperTool and then the files subdirectory (Type "CD %USERPROFILE%\Desktop\AmazonFire5thGenSuperTool\files" without the quotes) and then typing "adb reboot" without the quotes. It was only after I rebooted in this manner that KingRoot was able to root, getting up past 30% before my fire rebooted. I wonder if the (adb) reboot works differently than a Power off/power on.
[Fire General] DB126:
Read through your post; should be good to go. Be sure to read flashing instructions carefully which are located in the first post of the CM 12.1 thread.
[Fire General] Zebedez:
Thanks, worked great.

Got a really noisy keyboard, tried silent but I like some feedback.

But think I may have to go back to stock, some apps I use are now incompatible even when sideloaded. Installed gapps pico, will try nano but doubt it will make a difference.
[Fire General] DB126:
GAaps edition won't make a difference in compatability. Surprised sideloaded apps are not working correctly on CM 12.1. The only stable apps that should outright fail are those:

- designed for a different version of Android (FireOS v5 can CM 12.x are both based on Android 5.x/Lollipop)

- explicitly designed for FireOS (eg: Freetime; some Kindle reader builds; etc)

- those that demand different hardware (in which case they wouldn't run on FireOS either).
[Fire General] Zebedez:
They are all working on the other fire I've rooted but kept fire OS. I've been looking through files and see "null account" in the cache of the none working apps, side loaded apps don't show as installed on playstore, so maybe the apps can't get some info they need.
[Fire General] DB126:
Seems unlikely. If comfortable doing so share a few titles so others can try. Or restore FireOS and go through the root/flash process again as there were some self-reported bumps on the previous attempt. Might be some detritus getting in the way.
[Fire General] trlkly:
Not sure if this makes more sense here or in the SuperTool thread.

For some reason, when I try to install the Xposed framework using the Supertool, I get an error about the included Flashfire APK being invalid. I used the EVOZI APK downloader to get the APK from the Play Store, but that file still was considered invalid. I wound up just installing Flashfire from the Play Store and then running the SuperTool to install Xposed.

And it has worked. I was able to install YouTube Adaway (after downgrading to YouTube 11.39.54), and all seems to work.
[Fire General] sd_shadow:
it's either an issue with Supertool, FlashFire or xposed

but not a rooting issue
[Fire General] DB126:
Also question method for obtaining the APK. Stick to trusted sites like apkmirror and forego clever techniques for extracting installs from the Play Store.
[Fire General] BigT74:
Thank you all SO MUCH for figuring out how to root 5.3.1.0!

My mom won a Fire 7 in a drawing, but she already had one, so I bought the new one from her.

It started out with an earlier 'rootable' version of Fire OS, but before I could stop it, it updated itself 5.3.1.0.

I thought all was lost, but I followed this forum closely and hopefully. Now, I'm very happily running CM 12.1!

One note of caution: After you've successfully rooted Fire OS 5.3.1.0, you've installed Flashfire, and you're ready to flash your ROM, DO NOT forget to add a flashable supersu.zip to the list of files. If you don't, you won't have root when you boot to your new ROM of choice.

It took me a good hour or two to figure it out, but SuperSUMe ultimately saved my bacon.

- Big T
[Fire General] DB126:
No need to include a SuperSU zip when flashing CM 12.1 or Fire Nexus as both builds come prerooted. The toggle to enable root on CM 12.1 is located under developer options. Nexus simply needs the SuperSU app installed which can be downloaded from the Play Store or apkmirror. Other flashable ROMs may need the SuperSU zip to enable root; always read the OP for prerequisites, recommended supplemental packages and flashing/installation guidance.
[Fire General] BigT74:
I'd just I like to clarify a couple of things:

The first thing I did was to go into Developer Settings and tick the "Enable Root" option.

Still, anything that required root, Flashfire in particular, threw an error stating that I indeed did not have root. Rebooting made no difference.

I also downloaded SuperSU from the play store. Still, I received errors stating that I don't have root. SuperSU also stated that the binary needed updated, and it failed EVERY TIME. Rebooting did not help either.

It wasn't until I downloaded, installed, and ran SuperSUMe that all of this was resolved. Only then did the binary update complete successfully in the SuperSU app.

Look, I may not be a developer, but I've been rooting and playing with various Android ROMs/mods for myself and others since I got my first Android phone (HTC Desire HD) in 2011. Honestly, this is the very first time I ran into an issue like this one.

Please don't take this to be mean or rude: If someone is genuinely trying to be helpful, and the suggestion is very unlikely to cause damage (as is the case with my suggestion), why not just leave it alone?

Thanks,

Big T
[Fire General] sd_shadow:
you need to reboot after selecting

settings>about tablet>tap on build number 7+ times, to enable Dev options>go back to Settings>Developer options>Root access>Apps and ADB
[Fire General] DB126:
Appreciate the feedback. Thoughts:

- First and foremost I am glad the combination of FlashFire, Super-Sume and SuperSU worked for you when >>executed from CM 12.1<<. That's an important distinction.

- Recent builds of Super-Sume have proven unstable on certain hardware and ROM combinations, including 4th gen HDX and 5th gen Fire devices running FireOS. A commonly reported outcome is a soft brick following reboot. While some locked devices can be salvaged with a FireOS/ROM restore from stock recovery no such option exists for HDX owners. I'm currently working with an individual that toasted a $480 USD HDX following the use of Super-Sume. Cause->effect are both understood and predictable.

- While steadily improving FlashFire is not a true recovery environment and can stumble with complex flash operations. Keeping it simple increases the odds of a favorable outcome. There is no need to include SuperSU in the flash operations when installing CM 12.1 or Fire Nexus on this device.

- Recent builds of SuperSU (>2.76) have introduced network instability with some Amazon devices running custom roms. While evidence is scant devices with dual band radios running CM 13 have reproducible network disconnects when SuperSU is installed. Whether that's a defect in the ROM build or SuperSU has yet to play out. Bottom line is there is no need for SuperSU on CM 12.1 as it has an integrated root manager. The version included with Fire Nexus is 2.76.

I have had the unfortunate experience of being 'involved' (as a XDA contributor) with dozens of bricked Amazon devices, many at the hands of individuals who have experience with other device types. Amazon hardware, recoveries, roms, etc are not your typical Android fare. Special procedure are often needed; recovery from missteps can be difficult if not impossible (in that regard 5th gen devices are better than most). My focus is to make things as simple and reliable as possible for those not familiar with this platform's idiosyncrasies. That is why I opted to respond to your original post.
[Fire General] BigT74:
Thank you so much for the very thorough clarification. You've provided a lot of really interesting information that I wasn't aware of.

All of that leads me to a question: Any idea why, in my case, I lost root, even after enabling it in the Developer Options in CM? I genuinely want to know. I'd be happy with a wild guess.

Thanks,

BigT74
[Fire General] DB126:
- can't provide a definitive answer as individual circumstances vary

- IMHO FlashFire is a contributor - hence comment about keeping it simple

- on rare occasions I have experienced a 'rootless' CM install w/FlashFire; full wipe and reflash fixes it

- all CM flashes initiated from TWRP have been successful (same devices w/exploitable bootloaders)

As an aside, it is essential to flash a GAaps package (any) with many CM builds; adding after initial CM boot can be problematic. Seems to be more of an issue with CM13+ but also reported with CM 12.1. Typically results in no Play Store access, problems accessing previously purchased apps or 'core' Google services failing.
[Fire General] BigT74:
Yep, I used the latest OpenGApps micro package. Everything runs "like buttah".

It is conceivable, however, that some ROMs only allow enough room for the pico or nano OpenGApps package. I think there's one that has the GApps baked-in as well. So make sure to carefully read the installation instructions carefully before flashing.

- BigT74
[Fire General] DB126:
Yep, nothing over mini on this device due to limited space in system partition (items added from the Play Store and elsewhere are placed in the data/user partition). My preference is Nano as it contains all the core Google components some of which can not be installed independently. Fire Nexus rom has Nano baked it. All others for this device require a seperate GAaps zip flashed concurrent with rom.
[Fire General] trlkly:
The APK I got was identical to the one in the SuperTool.

Still, I've replied in the SuperTool thread instead since you guys basically said this was the wrong thread, since it wasn't a rooting problem. The main reason to post it here was in case someone else had the same problem--they could see what I did to get around it.

I'll leave it to the SuperTool people to actually figure out what went wrong. Maybe it's that the old method doesn't work on 5.3.1.
[Fire General] DB126:
Rereading your original post I wonder if you got caught up in a file name script error in the latest version of the SuperTool (here). This was raised by another contributor a few days earlier but remains unaddressed as of today. I apologize for not remembering that issue in my earlier reply if it applies to your experience.

Stand behind recommendation regarding extracting apks from the Play Store which violates Google's TOS; apkmirror is a better option IMO.
[Fire General] Zebedez:
Sorry got busy.

Decided I had nothing to lose, so before redoing everything I ran sdMaid (app, system and databases) & no longer have problems, playstore still says incompatible but sideloaded apps now work. Sdmaid is showing about 16 corpse amazon folders & some amazon databases, since I'm now on CM it should be okay to delete them shouldn't it?

PS where is the thanks button on here

---------- Post added at 03:34 AM ---------- Previous post was at 03:19 AM ----------

Flashfire didn't work for me either, until renamed as mentioned in the link you provided, never thought to mention it when I originally posted.
[Fire General] DB126:
Glad all is well; SD Maid is a good tool. Yes - safe to delete all Amazon detritus provided you don't have any Amazon apps installed (store, kindle reader, etc). What client are you using to view XDA content? Suggest XDA Labs (available here) as it is the most robust client to date with an obvious 'thanks' button. :)
[Fire General] Zebedez:
Downloading now & thanks
[Fire General] trlkly:
Well, crud. I don't know what's causing it, but all of the sudden my Fire went back to the Fire loading screen while it was just laying there, not even in use. It would occasionally show the lock screen for a second, then go back to the fire loading screen. I did a hard reset, and the same symptoms kept happening.

The SuperTool seems to still be able to see it and do stuff, but I can't really do anything. And even if I do a factory reset, I don't know what went wrong, to make sure it doesn't happen again.

Edit: Okay, so I did the factory reset (using adb restart recovery, as I couldn't get holding volume down and power to work), and got myself back to where I was--at least, with the apps I use often. Here's hoping it doesn't go wrong again.
[Fire General] DB126:
Suggest reloading FireOS via the stock recovery menu which will also perform a comprehensive device wipe including the system partition. You can then root with the SuperTool and carry out other tweaks using learnings from earlier attempts. That will all but eliminate a software glitch unless there is something unique in your app portfolio.
[Fire General] MistahJ73:
Thanks for everyone's work on this, I was finally able to root my Fire and flash CM 12.1 after only one failed attempt(forgot to move 'wipe' to top of the list in Flashfire.) Now running CM 12.1 but the problem I have is that the Google Play store app is nonfunctional. Tap the icon and nothing happens. Anyway to fix this without having to go back to square one? I used the latest OpenGApps micro version and flashed it with CM12.1
[Fire General] MistahJ73:
Sorry if this is in the wrong place, but I've searched and still not found a solution. I've done this several times and I still have the same problem.

- wiped and sideloaded stock 5.3.1

- factory reset through recovery

- wipe cache

- rooted with kingroot

- installed supersu-me 6.7 and ran it

- updated binaries without rebooting

- downloaded and installed Flashfire 0.53

- followed instructions from Flashfire thread to flash CM12.1 and OpenGapps micro from SD

Device boots normally, everything appears to be in order but tap on Play Store app and nothing happens. What am I doing wrong?
[Fire General] DB126:
Check last 24 hours in the CM 12.1 thread for potential solutions. Also:

- use SuperTool to install SuperSU vs SuperSume

- verify you are installing the correct GAaps version (arm/5.1)

- suggest nano over micro (typically fewer install issues)

- reboot device before running FlashFire 0.53

- position a full wipe (system/data/cache/dalvik) at top of operations sequence

- retain all FlashFire defaults

- be sure to include GAaps with CM
[Fire General] MistahJ73:
Thanks, I just checked the CM12.1 thread and I'm hoping that getting the apks and installing them does the trick. Everything else you mentioned checks out.

- GApps version is correct ARM/5.1/micro

- made sure wipe was at top of sequence

- included GApps with CM12.1

Only thing I didn't do was reboot before running Flashfire
[Fire General] MistahJ73:
Thanks again Davey126, all it took was to download and install the apks and now I have full Google Play access.
[Fire General] Zebedez:
Received refurb fire 5.1.1, spent last couple of hours searching, now totally confused - can I just let it update & follow these instructions, which worked well for me on 2 other (5.1.4 &5.3.1) tablets.

Sorry to be a bother, but having a real problem finding info on 5.1.1, which isn't full of dire warnings.

---------- Post added at 09:10 PM ---------- Previous post was at 08:38 PM ----------

Duh, bad comprehension day, using supertool now.

And

Fire Nexus running fantastically.
[Fire General] ZentixZaneic:
If I do this, will I be able to return back to stock? Also, what are some advantages to doing this? I've been thinking about it as I have experience with CM, but I'm not sure whether I want to dip my toes into the proverbial pool.
[Fire General] sd_shadow:
to restore stock firmware see

Unbrick 7in Fire 2015 5th Gen with ADB Sideload
[Fire General] DB126:
Use the SuperTool to root and prepare your device for a custom rom.
[Fire General] ZentixZaneic:
So I would be able to return to stock just as if I was sideloading a firmware update, I just have to factory reset when it's done? Or is there something I'm missing?
[Fire General] sd_shadow:
Factory reset only removes user data, it will not restore system apps
[Fire General] yugj_0h:
I restarted after step 4 and my device is now bricked.

when a power on my device is stuck on the fire logo.

I try restart using <power> + <volume up> but recovery menu not appears

How can i do. someone help me
[Fire General] DB126:
If you can't access the recovery menu via <power>+<volume up> the device can not be recovered.
[Fire General] yugj_0h:
Can I do anything else ?
[Fire General] sd_shadow:
return to Amazon for a one time exchange, if still under warranty
[Fire General] yugj_0h:
Thanks man. But i can't do it cuz my Fire warranty expires. I just try something else
[Fire General] Brsuperboy9:
My fire will not install the app AT ALL. It just says app not installed.
[Fire General] sd_shadow:
What app?

Version?

From where?
[Fire General] Brsuperboy9:
KingRoot with the latest version from KingRoot.net
[Fire General] sd_shadow:
May need to factory reset

And try version in XDA thread
[Fire General] Brsuperboy9:
I really don't want to factory reset until I back up my games but I will try the version in this thread? Or XDA in general?
[Fire General] sd_shadow:
KingRoot XDA thread
[Fire General] Brsuperboy9:
The download link found for downloading KingRoot is invalid
[Fire General] sd_shadow:
http://xdaforums.com/devdb/project/dl/?id=21115

---------- Post added at 09:06 PM ---------- Previous post was at 09:05 PM ----------

http://xdaforums.com/devdb/project/dl/?id=21115&task=get
[Fire General] kaliddu:
My experience:

Hello

I followed the procedure with kingroot as the first post for my fire 5th generation 5.3.1.

Once you have the root (5-6 attempts) and installed supersu-me 6.7 and FlashFire 0.53 my device has become unstable and I could not keep the windows open.

I had to reboot the device, and the result was a brick. :crying:

I made a unbrick to 5.3.1 as indications without problems (except for a problem with the micro USB cable to which I had to cut a piece of plastic to thread it more deeply and make it work properly).

Second attempt with Supertool latest version:

I launched Supertool to which I said that you have the 5.3.1., He has thought to install kingroot and always after 5-6 attempts I got the root.

Supertool uninstalled kingroot and installed SuperSu and Flashfire.

A wipe of the device and one always restart from 5.3.1. and everything worked well yet.

Started yet Flashfire 1 time I reloaded before a wipe and the last Rom lp-fire-nexus.

I waited about 5 minutes and i started the custom rom fast and perfect. :)

This was my experience, I believe that my problem was not removed kingroot before installing SuperSU.

The version installed by Kingroot Supertool is not the last.

I hope this can be useful to someone.

Sorry for my bad English. :):):)
[Fire General] yugj_0h:
My Kindle Fire was a brick. Please tell me How did you unbrick your Kindle Fire?
[Fire General] DB126:
Method will not work in your situation as you can not boot into stock recovery. Been through this already: http://xdaforums.com/showpost.php?p=69392186&postcount=262
[Fire General] texasraptor:
I was able to get my device rooted and installed cyanogenmod 12.1 however the gapps zip did not flash over. I tried to boot into recovery to install from .zip but the option is not there since it is still using the amazon recovery screen. Is there a way to get gapps installed? I went to get arm 5.1 nano since i heard that is easier to isntallbut also have arm 6.0 stock 20161103 this is for a kindle fire 5th gen
[Fire General] ldeveraux:
You have to use API level 22 for this ROM, since it's Android 5.1. You can get into recovery the same way you did to install the ROM, through fastboot.