yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] pappasmurfsharem:
Looks ok on my end

press a key to reboot the device in fastboot mode
< waiting for device >
...
(bootloader) APPEND KERNEL CMDLINE

OKAY [ 0.007s]
finished. total time: 0.007s
resuming boot...
OKAY [ 0.003s]
finished. total time: 0.004s
--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
remount succeeded
2601 KB/s (170232 bytes in 0.063s)
241 KB/s (1976 bytes in 0.007s)
2411 KB/s (75364 bytes in 0.030s)
3633 KB/s (5904943 bytes in 1.586s)
1966 KB/s (29972 bytes in 0.014s)

It might be a strange issue with the Administrator having "odd rights" on your User/Desktop folder.

Try moving the folder to the root of your C drive
[Fire Android Development] revdirty:
trying now, and for anyone else, i am opting to have this conversation in the thread instead of a pm so that it may help others later.

Edit: still same error msg as before , attempted to run from root of C: with running bat as admin
[Fire Android Development] Pond-life:
Very relevant I'm afraid and yep you are out of luck. You definitely won't be getting root from it.

---------- Post added at 02:40 PM ---------- Previous post was at 02:33 PM ----------

On stock 5.1.1 on Fire 7, the supertool can root, install Google play, block lock screen ads, block further ota updates, but cannot get you into twrp for installing a new rom.

There is another way to get to other roms but isn't as stable, featured and safe as it's an app and one in beta. It currently works to install SlimLp and seen one on RR, but only from stock attempts from SlimLP seem to fail, and CM isn't currently able to install this way.
[Fire Android Development] jhebert121:
Is there a list of what will and will not work?

What I am looking to do is add Google Play, install Nova launcher, block OTA, and hide bloatware. (edited)
[Fire Android Development] npompei:
On stock 5.1.1 on Fire 7, the supertool can root, install Google play, block lock screen ads, block further ota updates, but cannot get you into twrp for installing a new rom.

There is another way to get to other roms but isn't as stable, featured and safe as it's an app and one in beta. It currently works to install SlimLp and seen one on RR, but only from stock attempts from SlimLP seem to fail, and CM isn't currently able to install this way.[/QUOTE]

Wow that's fantastic thank you! So would adding recovery and installing a rom be something that can essentially be added on or would we need another full reboot, recovery install, rom install, etc?

I'm just looking to speed this thing up as it's a dog right now. I have Google Play installed and I feel like for whatever reason it totally bogged it down.
[Fire Android Development] Pond-life:
You can't really add recovery it's all from an app. You need to be rooted. See this thread, there's a video

http://xdaforums.com/amazon-fire/general/how-to-flashfire-app-to-install-rom-t3269839

---------- Post added at 03:33 PM ---------- Previous post was at 03:22 PM ----------

Having had a quick gander through the HD8 I could only see mention of the google play working
[Fire Android Development] Blacktruck:
Can this supertool be used with version 5.0.1, or is it 5.1.1 only?
[Fire Android Development] npompei:
Boom, rooted and it's like a whole new tablet! Thanks a ton man!

Other than getting ADB installed/running, this was as simple as pie. Super quick, clean and simple!
[Fire Android Development] theholycow01:
Windows 10 will refuse to install the drivers and I don't think SuperTool includes the command that you need to fix it. Here's what I wrote in another thread:

I succeeded with Windows 10 x64 using the drivers in the zip file for installing Google Play found in this thread: http://xdaforums.com/showthread.php?t=3216122

I had to disable driver signature enforcement before it would accept the drivers. Pop an admin command prompt (try the new Windows+X key combo and click admin command prompt there!), then run the following two bcdedit commands:

bcdedit -set loadoptions DISABLE_INTEGRITY _CHECKS

bcdedit -set TESTSIGNING ON

Reboot and proceed to install the drivers. I did it manually from Device Manager, clicking "Let me specify a location" (or whatever that one says) and such. Once I did that, all was well.
[Fire Android Development] pappasmurfsharem:
The BCD edits were completely unnecessary for me, i just installed manually through devmgmt on Win10 x64
[Fire Android Development] theholycow01:
Interesting. I wonder what the difference is. Is there a set of drivers that Windows trusts, do you have a different edition of Windows that doesn't check, or maybe there's a GPO on my or your domain that does something?

How does driver signing work? Is it similar to web SSL certificates? Could be that the driver's signature depends on a new root certificate and I (as well as others who experienced the same issue) am behind on Windows Updates that would have brought it in.
[Fire Android Development] sirhackawain1:
Is there a way to run this tool "manually"? I'm asking because the automated sequence to root the device isn't working. When my Fire gets into fastboot the tool doesn't recognize it. I think I can fix this by unplugging and re plugging in my Fire but the tool runs by itself anyway and I don't want to screw something up while its working.
[Fire Android Development] pappasmurfsharem:
Right click the .bat and click edit,

You will see the captions for the menu options then the commands under it

Alternatively you can open notepad then click file > open > then select the .bat
[Fire Android Development] Pond-life:
It can
[Fire Android Development] sirhackawain1:
Looking at the commands it seems simple enough to just enter each command in sequence. However I'm not sure what "fastboot continue" and "adb wait-for-device && adb remount" do. Is there anything at all I need to be aware of before trying this (I don't a lot of coding)?
[Fire Android Development] pappasmurfsharem:
Fastboot continue does exactly what it says.

After you do the first line that changes the kernel setting it continues the boot process.

adb wait-for-device && adb remount

Is just two commands in one line

adb wait-for-device ( this is more or less saying wait for the device to appear ) && (then do) adb remount (mounts the partitions as read/write so you can modify the contents)
[Fire Android Development] sirhackawain1:
Thanks for the help! Using those commands I managed to root my device!

Curiously though Root Checker thinks the root wasn't installed properly but my Root Browser works just fine.
[Fire Android Development] borisevstratov:
It would be very much appreciated if you add debloat function to your script (adb shell pm hide or smth with root remove) to get rid of all those Amazon apps&bloat!

:angel::angel::angel:
[Fire Android Development] Tomsgt:
you reallt need to check out this amazing tool my buddy gates made it http://xdaforums.com/android/software/debloater-remove-carrier-bloat-t2998294
[Fire Android Development] borisevstratov:
So, that one is kinda universal? Will that work with our Fire 7"?
[Fire Android Development] dullian:
Thanks. And can I install another launcher directly from the Play Store or with an apk? Or it's limited to Nova Launcher and via recovery?

---------- Post added at 04:13 AM ---------- Previous post was at 04:08 AM ----------

Does it say 'list of devices attached' but there's a blank space? Not even saying that the device is not connected?

I had this problem when I tried rooting on Windows 7, could never solve the problem, had to do it on another computer. Guess my OS was messed up, I had too many performance problems, but after formatting and installing Windows 10 my Fire and Android devices are recognized by ADB. I also tried rooting via a virtual machine, but the disconnection that happens on each reboot makes me wary and didn't work either, after the first reboot the device wasn't recognized anymore by the vm
[Fire Android Development] Pond-life:
You can install launchers readily enough, just the stock one doesn't let them take it's place if it's there. Make sure at least one other one on there before getting rid of stock.

If the stock launcher is hidden,frozen, disabled or removed you can make any of the launches you've got the default. Though Google now launcher can be awkward to get it to take control.
[Fire Android Development] theholycow01:
I experienced plenty of that. I didn't let it bother me. Each time I just went into Device Manager, manually chose the driver again, and it worked.
[Fire Android Development] tyloud78:
Is there an easy way to determine which OS you are currently on? I've looked in "device options" section and still can't locate.
[Fire Android Development] theholycow01:
Pull down the notifications from the top. In the tool buttons, if you have one for "Blue Shade" then you have 5.1.1. If not then you have the older version.

If you have an unrooted KFFOWI on wifi then you almost assuredly have 5.1.1.
[Fire Android Development] Killerfish1450:
I've been having trouble getting the tool to work, so i decided to try manually block OTA on 5.1.1. I used the tool to check all drivers are working and used the tool to root. upon entering codes manually i get 2 "error : unknown host service" messages after using "adb wait-for-devices". Any ideas what is causing it?
[Fire Android Development] STEyeAndroid:
Quick Questions

I have the Amazon Fire that is on 5.0.1. I have not turned on Wi-Fi on so it hasn't updated the firmware. Couple of questions:

- Should I stay on 5.0.1 or take the OTA to 5.1.1? If I do take the OTA, can I revert back to 5.0.1?

- If I block OTAs, can I un-block them if I wanted to take OTAs in the future?

- If I were to root my device , change to Nova Launcher, and install the Play store, how do I get back to stock if I wanted to? Is it possible to undo things? Just do a factory reset in OS?

- Lastly Is it possible to do a complete (nandroid) backup before doing anything?

Thanks in advance!
[Fire Android Development] Butcher98:
I still can not get fastboot to run, 2 different pc's. This is crazy, I have unlocked bootloaders, flashed all kinds of stuff but this device is killing me! Lol

3rd pc did it! Christmas was saved.
[Fire Android Development] Tomsgt:
do not update to 5.1.1 you will not be able to downgrade again. yes you can unlock them but best way to update later is to sideload the stock firmware again
[Fire Android Development] STEyeAndroid:
Thanks for the clarification on that. I will ensure that I block the OTAs with this tool.

Can anyone shed some light on my other questions?
[Fire Android Development] Pond-life:
1) Stick. And nope it's one way.

2) Yep you could unblock them, but you wouldn't as it's easier to install them in twrp as we can stop it blocking twrp access that way. Also I get the feeling that even now the custom roms are more compelling and that will only increase.

3) You could flash the recovery image from Amazon in TWRP to take you back to stock, factory reset doesn't do what it sounds like it just removes registration, installed apps and pics and the like.

4) So long as you stay on 5.0.1 yep, boot through to twrp and back it up.
[Fire Android Development] STEyeAndroid:
Thanks a bunch pond. I am going to try to use this tool and keep 5.0.1. Hopefully things work out ok.
[Fire Android Development] blueberry.sky:
There is a thread on how to go back to stock. Be aware that OTA will be re-enabled. There is also a thread on how to upgrade from 5.0.1 to 5.1.1 without having amazon cripple your fastboot. But 5.1.1 doesn't bring much that is even worth the upgrade unless the Fire will be for a child.
[Fire Android Development] STEyeAndroid:
It is going to be for a child. What are the differences that benefit kids?
[Fire Android Development] blueberry.sky:
I was afraid you were going to ask. They add a couple apps to help control a child's use of the tablet but I don't recall exactly what they do.
[Fire Android Development] theholycow01:
...and for adults, the "blue shade" feature means that my wife can read for hours after my bedtime with less distraction keeping me awake. I guess it also means that staying up reading will mess with her circadian rhythm less too.
[Fire Android Development] jbraney:
Will this tool still work if I have used flashfire to install CM12.1 on my tablet? I had 5.1.1 BTW.

I somehow lost root, and I want to regain root access, but without the FireOS, I don't want to screw anything up...

---------- Post added at 01:04 AM ---------- Previous post was at 12:54 AM ----------

NVM wow I forgot about that and feel stupid... Root access is in developer settings on CM12.1
[Fire Android Development] theholycow01:
You could edit the .bat file to add a "pause" command where you need time, which will cause it to stop and prompt you to press any key to continue.

To do the steps manually, you could just paste the commands from the .bat file.
[Fire Android Development] Hesacon:
So I am stuck on getting the drivers to install (the first step in the process). I notice in the tool there are drivers for AMD64 and i386, however I only have access to x64 machines and Windows 8.1 rejects the drivers included with the tool. How can I get the drivers installed?

[Edit] Reading is hard, I was using the wrong "Browse" option in the Device Manager, and everything seems to have worked swimmingly, with some differences from the original video.

Confirmed that it works.
[Fire Android Development] theholycow01:
Replace "timeout 8 > nul" with "pause" or add the pause in that vicinity.
[Fire Android Development] FrankieChen:
pause > nul or just pause?
[Fire Android Development] theholycow01:
Just pause. If you do pause > nul then you won't see a prompt reminding you to hit any key, which could get confusing.
[Fire Android Development] FrankieChen:
Woohoo! Thank you - that worked :)

I got into TWRP and installed supersu which now shows as a app on my desktop and seems to open up without any issue.

Can I assume I've now rooted the FIRE? Not sure as the video is for 5.1.1 and shows a lot of stuff that never occurred on my FIRE (such as injecting files) Just wondering as I got 2 "error: unknown boot service" messages but then cleared and I didn't get the chance to see what they said to investigate.
[Fire Android Development] theholycow01:
My favorite way to check is to go into ES File Explorer (which is one of the first apps I install on everything) and turn on the "Root explorer" setting (Not in the "settings" menu, just under "Tools"). If it works then root was successful. If it fails then it will tell you so.
[Fire Android Development] FrankieChen:
Seems I'm in a catch 22 - didn't want to attach to wifi (to download ES File Explorer ) before ensuring root had worked. I wouldn't worry but as I said - I did get some error messages. I've used option to block updates but also got 2 "error:unknown host" messages which makes me wonder if it worked although I did get "OTA update has no been blocked" at the end. Exact screen message was:

error:unknown host

error:unknown host

package com.amazon.otaverifier now hidden state: true

package com.amazon.device.software.ota now hidden state: true

package com.amazon.settings.systemupdates now hidden state: true

I'm doubly nervous because on the previous FIRE I had (which I had to return because it went into Amazon Recovery and I couldn't get out of it), I'd blocked updates yet I still got messages sometimes when I switched on it was installing updates and it was after one of those messages that it got stuck.

What would happen if I ran the root option again - would it cause any harm?
[Fire Android Development] DB126:
1) You can sideload ES File Explorer via tether from here (or from another reputable site) using command 'adb install <path-to-apk>'. If needed install Minimal Fastboot and ADB (here) on host. Complete list of adb commands can be found here.

2) You can safely rerun the root command if desired.
[Fire Android Development] FrankieChen:
Excuse my stupidity but I thought that tethering involved attaching to another device's internet? I'm trying not to connect to the internet until I'm sure I've rooted ok.

Could I download the ES File Explorer onto a pc and then transfer it to a SD card & use that in the FIRE to install (presumably via TWRP)?

Thanks for the info re rerooting - I'll try again & see what those error messages were.

EDIT: Sorry - just understood what you mean about tether. I should send the ES File Explorer file to the FIRE via the USB cable adb command - the same way as Supersu was sent. Thanks again :)
[Fire Android Development] DB126:
- The term tethering is used (and misused) in a variety of ways. Meaning in this instance: attaching your device (Kindle Fire) to a host (eg: Windows PC) via USB cable. If you haven't done that before now probably is not the time to learn.

- Installing apk from SD card: You need a means of browsing to the apk to kick off the installation. To my knowledge stock FireOS v5 does not include a file browser so you have no means of navigating to the file to install ES File Explorer. Catch 22. Hence the adb install command suggested above which is issued from the host machine.

Understand your concern about unwanted OTAs. However, given the messages I don't think you have much to worry about. Enable WiFi and grab a copy of ES File Explorer from the Amazon store (easiest path; now is not the time to find out if the Play Store is working) if you simply want to verify root status. You can disable WiFi once ES File Explorer is installed. Rebooting your device will flush any partially downloaded OTA updates.
[Fire Android Development] Tomsgt:
thanks for all the help in this forum :) I can see you know what you are doing and it really helps to have someone with knowledge in this thread :)
[Fire Android Development] STEyeAndroid:
Is there a TWRP flashable zip for 5.1.1 that won't lock down the bootloader?
[Fire Android Development] DB126:
- TWRP does not "lock down" the bootloader

- at present there is no exploit to unlock the bootloader on 5th gen devices (2015 Amazon Fire)

- FireOS 5.0 (including bootloader) contains a vulnerability that permits access to fastboot environment which can then be used to 'boot' a custom version of TWRP. However, the bootloader remains locked so there is no mechanism for 'installing' TWRP. Amazon closed the vunerability with the release of FireOS 5.1

- you can not roll back FireOS to regain access to the vulnerability described above

Unless further vulnerabilities are discovered and exploits developed to leverage them you will not be able to use TWRP to flash custom roms. However, other methods exist to obtain root and flash roms on FireOS 5.1.1 as described elsewhere in this forum.
[Fire Android Development] STEyeAndroid:
Gotcha I thanks for the info! That being said I guess what you are saying is there isn't a 5.1.1 ROM that is flashable in TWRP since you said there are no custom ROMs for TWRP. You said that there are other methods to flash ROMs in 5.1.1, are there ways in 5.0.1? I performed a nandroid backup through TWRP, will that be reliable for restoring if need be? This is going to a child so I don't think I'll really muck around with it. It is good info for the nerdy side of me! :)
[Fire Android Development] sd_shadow:
http://xdaforums.com/showthread.php?t=3269839

How to Use FlashFire App to install a Rom
[Fire Android Development] DB126:
The issue is you can not launch TWRP once FireOS (more importantly the bootloader) has been upgraded past 5.0.1. See post by [MENTION=4267571]sd_shadow[/MENTION] for additional info in flashing roms from FireOS 5.1.1. Your question also seems to focus on restoring FireOS if you wish to return to stock. I'm not sure of the exact procedures on this device (likely depends on the version of FireOS installed before you went with a different rom) but there is away and likely more than one. You can also restore backups created in TWRP provided: 1) you have not upgraded the bootloader beyond 5.0.1; and 2) you only use backups that were created on the device that you are restoring to. While restoring TWRP backups from other devices can work it's a high-risk proposition and good way to brick your device. Finally, there are several ways to flash ROMs on 5.0.1; the choices are more limited on higher versions. As always you should use the recommend method (check the rom OP) and follow instructions carefully.

Finally, I will offer an opinion that is not shared by all: If the device is going to a child who has no exposure to Android leave FireOS on it for now. You can always flash a different ROM if your child is seeking apps not in the Amazon Store or other issues arise that suggest a version of Android closer to AOSP is needed. If you do stick with stock be sure to block OTA (over the air updates) for now as Amazon may lock down future versions of FireOS such that you can not root or flash different roms. Also - don't forget to remove root before handing the device over to a curious youngster who might be 'nerdier' than you think.
[Fire Android Development] STEyeAndroid:
To be honest, I think I will be sticking with FireOS 5.0.1 with Nova launcher + Root + Play Store installed. I backed up everything prior to messing around with it (e.g. installing play store and OTA block). I may install Titanium Backup so I can freeze some of the bloatware that comes with FireOS.
[Fire Android Development] adarof:
Hi,

Works perfect, THANK YOU!!!!!

One question: How could I add another Google Account?

Amazon has pimped the "normal" Android-Settings, thus there is no Account-List where I normally add my family account ... and I dont see any "+" for an account in Google Play store or the Google-Settings-App.

Do I miss something here?

#Edit: Just hitting the "Google Play Game" App does offer the account selection including the "Add Account" option. But .. now the other way around: How to delete a account without having the "Account management" in the device settings?

BR- Adarof
[Fire Android Development] Pond-life:
Actually from 5.0.1 there is a way to get 5.1.1 without the problems. Whether it's worth doing or not is more debatable, though does have more child related options

http://xdaforums.com/amazon-fire/general/howto-install-fireos-5-1-1-root-gapps-t3265594

The 3rd step is vital to keeping twrp access.

The update file in the op has gone but the one in fourth post works, though it is downloadable from Amazon now. Don't install it how Amazon say to though or same effect as OTA. The method in that thread is only way to keep boot as per 5.0.1.
[Fire Android Development] FrankieChen:
A HUGE thank you to

Tomsgt for this amazing script (and everyone else who helped in it's components development)

sd_shadow for being utterly incredible in just about every thread but specifically for pointing out even with the adb and fastboot drivers installed correctly, sometimes the Fire becomes unrecognisable if rebooted whilst attached to the pc & the necessity to unplug & restart the fire in order to get it's drivers recognised again.

theholycow01 for teaching me how to "pause"! in order to get round the loss of the Fire drivers on rebooting while attached.

Davey126 for your advice on getting ES File Explorer installed to confirm the root without having to connect to wifi.

You guys are completely AWESOME :)
[Fire Android Development] Tomsgt:
well stated