yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] msm1965:
Not getting beyond first screen

Hi, I am having difficulty passing beyond the getting device id as tool quits after few seconds from displaying the device id.

My computer is running win10 anniversary version and devices OS5.3.1.

I tried the previous tool version and it loads the options (blue screen) etc but as I understand it is not updated and may cause bricking the device.

Any advice/help to resolve this would be appreciated.
[Fire Android Development] kamor:
Am I right that there is currently no way to root the Fire HD 8 (2016) even with this tool?
[Fire Android Development] DB126:
Wrong forum; not for HDxx devices. Post your question here. If/when specialized tools become available for 6th gen devices the details will be posted in the linked forum or another created for this device.
[Fire Android Development] kamor:
I know. I asked in this thread because this tool actually works on the old HD8. I was just hoping to get an answer from the dev.
[Fire Android Development] DB126:
PM the dev; don't contaminate the forum with off-topic questions.
[Fire Android Development] kamor:
PM a mod; stop backseat modding, stop contaminating the forum with even more off-topic
[Fire Android Development] sd_shadow:
I'm pretty sure that tomsgt doesn't have an HD10 or HD8
[Fire Android Development] kamor:
I see. I used it to install Google Play. And it pushed Kingroot on my device so I assumed that everything might work. I won't post in this thread anymore and wait for a solution. Thanks.
[Fire Android Development] fmc000:
Good.
[Fire Android Development] Tomsgt:
that is correct i have only tested it on the Amazon fire 5th gen 7in
[Fire Android Development] sd_shadow:
For those with the HD 8 and HD10 models, please discuss and ask questions in

[Q&A/T] Amazon Fire 5th Gen [SuperTool] (Un/Official Help Thread for HD8/HD10)

I will try to keep an up todate FAQs [MENTION=4246643]Tomsgt[/MENTION]
[Fire Android Development] highspeedfelon:
Just had same issue earlier. To fix look in the apps folder and rename the flashfire app to match it in the script. Its missing the "v" do that and it will work.
[Fire Android Development] ext23:
Life saver!
[Fire Android Development] DB126:
Can also snag the latest version of FlashFire from here .

[MENTION=4246643]Tomsgt[/MENTION] - for awareness; minor bug in script.
[Fire Android Development] ttcontributor:
So I can use the "9. Update SuperTool Files" to get the latest version for rooting fire OS 5.3.1.0?
[Fire Android Development] paschott:
Worked on my Kindle Fire HD7 w/ 5.3.1.0 - had to reboot once along the way, but was able to install the Play store and related apps. Now just need to figure out why some of my purchased apps show up in the Play store as needing to buy them again, but that could be something else entirely and could just be an update is missing somewhere. I appreciate your work getting this together for the 5.3.1.0 OS.
[Fire Android Development] DB126:
Please the appropriate forum for HDxx devices: http://xdaforums.com/fire-hd
[Fire Android Development] Mr.Montesa:
Hey,

Tried SuperTool in my 5.3.1 7in fire and it worked great. Was able to root/stop OTA updates,etc. Booted several times and played a bit with it. Then left it running over night.

Since next day it now hangs in a boot loop. After boot finishes welcome screen opens. Then swiping to unlock and suddenly device goes black and reboots. Every now and then it enters the "Optimizing apps for first boot. Please wait up to 10mins" section but does not finish the same. I have to force power-cycle and continue with the boot loop.

Did a wipe cache and factory reset via default recovery, but no change in behavior.

Any clue what this might be? Or how to get the tab working again? Goal would be to install a SlimRom or CG.

Thanks much for your help.
[Fire Android Development] Neilyboy:
worked great on my 5.3.1 after finding out that its calling for a file named something different than the flashfire apk that exists in /apps/ just rename it to whatever its calling for and it worked flawlessly! well done Tom

Neil
[Fire Android Development] sd_shadow:
I would restore firmware in recovery see

http://xdaforums.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294
[Fire Android Development] Mr.Montesa:
Thanks for the hint. That worked well. Restored to 5.3.1, rooted again and flashed CM 12.1 which is running nicely on the device now. All looking good now.

Again, thanks much.
[Fire Android Development] Jackie78:
Will installing the play store also work on a 2016 Fire HD 8?
[Fire Android Development] DB126:
Not a HDxx forum; ask here or just try it. If it works share findings in the HD8 forum so others can profit from your experience.
[Fire Android Development] trlkly:
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. This worked.

The only other info I have is that the Google Play download said it was around 10.8MB but the APK file seems to be 11.4MB. Maybe it's the wrong APK file, perhaps one for Android 6/7?
[Fire Android Development] ethan1701A:
I ran the latest supertool version, and had it install KingRoot on the device. I was surprised to see that the version it installed was 4.9.2 and not 4.9.6.

I downloaded the 4.9.6 APK from their site, and placed it in my AmazonFire5thGenSuperTool\apps on the computer. I then uninstalled KingRoot from the Kindle and ran the SuperTool again. This successfully installed 4.9.6 onto the device. Once I disabled the lock screen pin code, and gave KingRoot administrative privileges, root succeeded on first try. (took me 6 tried to figure this out).

I then continues with the SuperTool, it failed to find the KingRoot APK it was looking for (I presume because I had replaced it with another), and SuperSu requested to update, but failed to do so.

I then manually uninstalled KingRoot, swapped back the original apk in the folder on my computer, and went through the process again. This time it managed to remove KingRoot, and SuperSu successfully updated. RootChecker confirms I have root!

For whatever reason, KingRoot says the device is running Android 5.1.1, even though it's on 5.3.1.0. Any idea why?

Thanks for this great tool!
[Fire Android Development] sd_shadow:
5.3.1.0 is FireOS

5.1.1 is Android
[Fire Android Development] rootfye7:
Hi - My Fire is using OS 5.1.1, but I accidentally ran the root process for OS 5.3 (dumb mistake... I know :/). The Fire is still functioning fine, but now when I go try to go through the correct root process for 5.1.1, root does not work and I get the following messages / permision errors:

mkdir failed for /system/app/SuperSU, File exists

mkdir failed for /system/bin/.ext, File exists

cp: /system/xbin/su: Operation not permitted

Unable to chmod /system/xbin/su: Operation not permitted

chcon: Could not label /system/xbin/su with u:object_r:system_file:s0: Operation not permitted

cp: /system/xbin/daemonsu: Text file busy

cp: /system/xbin/supolicy: Operation not permitted

Unable to chmod /system/xbin/supolicy: Operation not permitted

chcon: Could not label /system/xbin/supolicy with u:object_r:system_file:s0: Operation not permitted

cp: /system/bin/app_process32_original: Text file busy

Also - I have tried to remove SuperSU through the "Unroot Device Entirely" option in settings, but it always seems to fail.

Does anyone have any suggestions which may possible help me get root access to function?
[Fire Android Development] HughJeffner:
When installing FlashFire I had to rename the file in the apps directory from flashfire-0.53.apk to flashfire-v0.53.apk for it to install. Should be an easy fix if you happen to update the tool.

Edit: Using Windows batch file
[Fire Android Development] DB126:
Think the most expeditious (safe, reliable) path is to reload FireOS 5.1.1 via the stock recovery menu. You could update to 5.3.1 but there is no benefit in doing so (and a possible deficit if a bootloader exploit is ever identified) if your goal is to flash a custom rom.

Not so concerned about the script errors (easy fix) but rather lingering SuperSU binaries that can cause downstream havoc with KingRoot/KingUser.
[Fire Android Development] flowforger:
flashfire package failed to install in linux script

In the linux script the flashfire package failed to install. I simply replaced the flashfire apk file with a newly downloaded apk of the same file, switched filenames and tada its working as it should. Cheers,

Since this is my first post I sadly cannot provide link - but its from flashfires own webpage (not the flashfire.com, but the chainfire.com site)
[Fire Android Development] msgreenf:
Is root still working for everyone? I just tried to root this version 5.3.1.0 with kingroot unsucessfully.
[Fire Android Development] cpubradley:
I rooted successfully this last weekend using the latest supertool successfully - was running 5.3.1
[Fire Android Development] DB126:
Yes - try again. Sometimes takes a few attempts.
[Fire Android Development] adamo86:
how many times does one have to try?
[Fire Android Development] BRANDENDEUCE:
Until it takes root. I have had better experience with using the Windows software of kingroot through the USB port
[Fire Android Development] DB126:
If all efforts are in vain you can reload FireOS (fresh start) and then decline to register w/Amazon when the device boots. Some contributors claim this makes rooting more reliable. Also make sure you have a stable network connection as Kingroot calls home frequently for further instructions during the rooting process.
[Fire Android Development] adamo86:
it worked with the latest version of kingroot apk i uninstalled it and downloaded supersu via playstore but i cant update binaries. is there a way to flash super su. its done thanks
[Fire Android Development] DB126:
Err...SuperTool? Wait ...
[Fire Android Development] adamo86:
I lost root after installing cyan is their a way to get root again I tried king root it's not working.the pc version doesn't even respond and I tried supertool
[Fire Android Development] Tomsgt:
start over by restoring Amazon Stock firmware with adb sideload then do it all again this time make sure you flash supersu zip
[Fire Android Development] stifuco:
Root after unroot

Hi! I have unrooted my tablet via the supersu page in the settings, and now I want root back. Tried with the supertool, it works until rebootbut then if stucks on the "your device is rebooting and will inject root files" part.

What can I do?

I have 5.1.1 android on it.

Thank you
[Fire Android Development] DB126:
Reload FireOS 5.1.1 via stock recovery then reroot with the SuperTool.
[Fire Android Development] adamo86:
Does that mean if I start from stock rom I can flash any firmware. Currently I'm on unofficial cyan cm12.1. Before flashing cm12.1 I was on the latest stock rom. Also can I extract the supersu file from supertool and flash it if not can someone give me a link to a flashable supersu. Thank you
[Fire Android Development] sd_shadow:
no you cannot flash any firmware

in most cases firmware cannot be downgraded

if you had latest, only use latest

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

https://download.chainfire.eu/696/supersu/
[Fire Android Development] adamo86:
I'm not downgrading from stock I'm actually downgrading from cm12.1 to an earlier release of stock does the device still have data which stock rom it was running from before.
[Fire Android Development] sd_shadow:
bootloader and kernel are still stock

downgrading will brick
[Fire Android Development] DB126:
If you use the SuperTool to root allow it to install SuperSU as migration from Kinguser can be tricky depending on starting version of FireOS.
[Fire Android Development] adamo86:
I uninstalled king root and tried a different version of king root . Because I have to start again it will take some time .looks like I'll be rebooting the device many times before I can achieve root.

The king root windows version doesn't seem to work. I click on icon but no response does anyone have a link to king root version that works on pc I tried 2.2...
[Fire Android Development] DB126:
You can fight through each step manually downloading/uninstalling/retrying/failing (which is fine if you know what you are doing) or just use what's packaged with the SuperTool.
[Fire Android Development] adamo86:
I'm currently running Cm12.1 since its a custom rom shouldn't it be easier to root it?
[Fire Android Development] DB126:
As previously advised reload FireOS and start from the top: http://xdaforums.com/amazon-fire/de...-5th-gen-supertool-root-t3272695/post69340094
[Fire Android Development] adamo86:
i have finally got root it was quick. thank you everyone. im having an issue installing playstore i tried supertool and the following gapps pico nano micro mini. any suggestions ? currently running cm12.1 latest version
[Fire Android Development] sd_shadow:
Normally I suggest installing at same time as the ROM

But you could just download files posted in

http://xdaforums.com/amazon-fire/general/how-to-install-google-play-store-fire-t3486603

And install using a file manager
[Fire Android Development] adamo86:
The way I done it was I tried to install it via super tool then I also tried manually from super tool now I'm going to try the links you gave.

---------- Post added at 08:25 PM ---------- Previous post was at 08:04 PM ----------

I tried the links it still doesn't work you mentioned to do it at the same time as flashing rom how is this done. I did the following using flash flashfire to flash cm12.1 . Is there a flashable zip which I can use to flash it at the same time. Thank you so much for replying quick. I just tried slim rom with slim rom gapps no playstore. Am I missing something. I just noticed the flashfire is only flashing the ROM But not gapps even though it shows it is any reasons why?

At last got the playstore to work. Thanks everyone
[Fire Android Development] stephen1214:
can't download supertool, stuck at 99%, help please thanks.
[Fire Android Development] DB126:
So you're all set now - root, Play Store, etc working OK?

---------- Post added at 12:45 AM ---------- Previous post was at 12:42 AM ----------

Nothing anyone here can do to help with downloads. Something wonky with your desktop/laptop internet connection. Try again later to see if it clears up.
[Fire Android Development] DB126:
FlashFire option "Mount /system read/write" is selected by default and should not need to be modified for ROM or GAaps flashes. Why were you changing it? The CM 12.1 OP is clear on this. Seems many of your recent issues are the result of not following posted guidance.
[Fire Android Development] DB126:
Assume you are referencing [url="https://youtu.be/4dwguHoxTvoÃ??Ã?Â¢?Ã??Ã?Â]this[/url] video. While providing an excellent overview it was produced nearly a year ago by a 3rd party; some info is no longer relevant or outdated. Always follow guidance in the OP of the ROM or tool you are trying to install which contains the latest info from the actual developer.
[Fire Android Development] BA20020:
I have installed the Kingroot that came with the updated SuperTool, ran it and rebooted 3 times, couldn't get root. Checked on here and found that there was a 4.9.6 to replace the 4.9.2 that came with SuperTool, installed that, ran it five times with reboots, still no root. It has Admin privilege set.

I am not familiar with the Kingroot software, and on the Google store there seem to be multiple apps titled 'Kingroot' with different authors that look questionable. I'm hesitant to install Windows software from relatively unknown sources. Can you folks vouch for the safety of these Kingroot apps (such as the author is someone from the XDA-Devs)? And if so, how many times have you folks needed to run it to obtain root on your 5th gen Fires?

It strikes me as very strange that you would need to run a piece of software a dozen times before it actually does what it's supposed to.
[Fire Android Development] adamo86:
Best way is wipe your device clean before doing root is quicker.

---------- Post added at 06:36 PM ---------- Previous post was at 06:35 PM ----------

Just a quick question since I'm running cm12.1 do I need to disable ota updates via super tool?
[Fire Android Development] gtallmadge:
I think if you would read further you would discover that Kingroot is not a trusted application. Hence, using SuperTool to install and replace KingRoot with SuperSu, which is a trusted application. Unfortunately, KingRoot is problematic and may require numerous attempts to gain root. And, as indicated, no one is going to vouch for the safety of Kingroot. It is not trusted. However, the beauty of SuperTool is that it replaces Kingroot with SuperSu automatically and allows you to have a safe rooted device to install a custom ROM in.
[Fire Android Development] DB126:
KingRoot is sketchy at best but at present it is the only way to reliably secure root on FireOS v5 (especially higher revs). The authors are definitely not from a trusted XDA community. Gotta ask yourself why this tool exists sans advertising and self promotion.

Now we have FUD out of the way here's how to improve odds KingRoot will find a root solution that works with a minimal number of attempts:

- If you have messed with FireOS, installed Google Play Services or your device otherwise deviates significantly from 'out of the box' it is best to start fresh and reload the IDENTICAL version of FireOS via the recovery menu.

- Perform a 'factory reset/refresh'. When the device restarts do NOT register it with Amazon.

- Insure you have a solid network connection. KingRoot calls home frequently for further instructions (and likely sends back photos of the interior of your home...JK)

- Use the latest version available here

- Politely decline to install suggested components such as Purify

- Once rooted immediately use the SuperTool to remove KingRoot detritus (in particular KingUser) and install SuperSU which is a well regarded root manager and a FlashFire prerequisite. Don't attempt to use SuperSume or other method for banishing KingUser; more likely than not you'll end up with a soft brick and have to start over.

Good luck.

---------- Post added at 09:13 PM ---------- Previous post was at 09:11 PM ----------

Nope - not relevant.
[Fire Android Development] BA20020:
I was finally able to get it to root. Here are the steps I went through:

- I removed the Kingroot and SuperSU from my Fire that had gotten loaded from previous attempts.

- I took the plunge to install the Kingroot Windows app. It didn't root my tablet by itself, but it did seem to do something as the PC version ran differently the second time and the apk jumped ahead quickly %-wise during the re-run.

- I re-ran SuperTool to install Kingroot with 4.9.6 apk replacing the old 4.9.2

- Ran Kingroot, let it reboot, but instead of rebooting the tablet to try running Kingroot from fresh startup again, told Kingroot to run the root process again immediately after it showed that it had failed.

- After another root-ing run and reboot, finally had root!

I'm not sure which of these were the missing link, but it seems to have finally worked. Now to run a Malwarebyte's Anti-Malware on my machine to make sure that PC installer didn't leave anything nasty behind.
[Fire Android Development] GambrinusX:
Fresh Install of 5.3.1, trying to root with newest SuperTool (10-06-2016):

Device successfully rooted. SuperSU asked me to delete "other SU-Tool", allowed it, only KR Purifiy seemed to remain (deleted it afterwards).

Now i´m a little bit worried: Is King Root uninstalled completely (regarding cited error-messages)?

Thanks in forward!
[Fire Android Development] DB126:
Won't matter if your goal is to Flash a custom rom provided SuperSU is installed and behaving as the active root manager. Otherwise yeah, I would be suspicious. That said, I'm not familiar with the SuperToool logic tree or expected outcomes. The messages could be 'normal' and simply reflect an extra set of checks (or left over code). Let's see it the developer weighs in.
[Fire Android Development] bovirus:
[MENTION=4246643]Tomsgt[/MENTION]

Is your latest tool version compatible with FireOS 5.3.1?

The latest tool can unlock 5.3.1 OS?
[Fire Android Development] DB126:
Posting in a public forum allows for a community response.

- current SuperTool fully supports FireOS 5.3.1

- SuperTool assists with root and other adminstrative tasks

- can not unlock bootloader on 5th gen Fire

- no custom recoveries (eg: TWRP) above 5.0.x

- FlashFire can be used to install several custom ROMs
[Fire Android Development] Lewzephyr:
Just wanted to say thank you for this tool.

I have just used it to root my Fire 5th Gen that was running 5.3.1.

I would like to let you know of an issue I came across using the tool.

When attempting to install flashfire via your tool, it would error.

It appears the tool is calling for a file named: flashfire-v0.53.apk but the file included in the tool is named flashfire-0.53.apk

once adding the v to the file name it was no issue.

Another issue I cam across was not due to the tool, but more of a Kinrroot problem.

it kept failing to root the tablet. It looks like some ISP's may have an issue with where the device is connecting to during the attempted root process. I installed a VPN proxy app and told it to use some location over in Russia, and the root process worked just fine. (this was after numerous attempts using different ISP's here in the US.

Hope this helps others in their process to freedom from the FireOS lock down.

Thanks again for your efforts.
[Fire Android Development] 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 Android Development] sd_shadow:
FlashFire
[Fire Android Development] DB126:
Please don't cross post; answered your question here
[Fire Android Development] ahmedaa16:
Thank you. I got rooted in the first attempt after doing a factory reset
[Fire Android Development] dokjon:
apk file for flashfire has an incorrect filename. invalid apk error. noticed that the filename was misspelled. should be "flashfire-v0.53.apk" but it was "flashfire-0.53.apk". added a 'v' to the filename then it worked.

ROOT option should be number 1. Because my blind self could not find the root option, I had to do my own king root research to root my fire. Then I came back to your script and noticed the option 6.

Nevertheless, I thank you. :good:
[Fire Android Development] dice4206:
Fire 10 hd OS 5.3.1

Does anyone know for sure how to root a Fire 10 H.D. OS 5.3.1? Ive tried the super tool from Root Junky and King root. No success. Ive looked at every article and website that comes up in a search but no joy so far. Any assist would be appreciated. Thank you
[Fire Android Development] DB126:
Wrong forum; ask here: http://xdaforums.com/hd8-hd10
[Fire Android Development] tkr9000:
To anyone who rooted on 5.3 how many times did you guys have to restart your device before KingRoot was able to get root to stick? I've restarted my device several times each time KingRoot got closer and closer to 100% but now it's been stuck on the "Verify Root Status" screen for some time and i cant get it to go past this screen. I've uninstalled KingRoot and have used the Amazon Fire Tablet Tool to reflash King Root onto the device but it just stays on the same "Verify Root Status" screen. Has anyone experienced this problem? PS SuperSU has not yet been installed.