yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] DB126:
Love the "inhomogeneous" quip...great word! :)

Network speed has a significant baring on whether an OTA uodate can 'slip in' during root attempts. If you are rocking a 100+ Mbps connection (and see that level of throughput) there's a good chance an entire update will stream down before the device restarts. The later is key as partial downloads are discarded on reboot. As KingRoot tends to reboot the device frequently OTA updates rarely download in their entirety on more pedestrian home/public networks (at least in the US). Also why a quick reboot immediately after securing root is highly recommended.
[Fire Android Development] steve8x8:
"Rocking" is the word. I'm at the end of a rather old and rotten, 2 Mbps landline (and rocking it!) - with a typical upgrade size I'm indeed pretty safe... 5.3.2 has 629 MB (or roughly 5000 Mbit), which buys me 2500 seconds or about 40 minutes. If the amount of data KIng wants to pull (per cycle) is below a few MB (anyone counted?), there's indeed no reason to be worried. Sometimes outdated technology has its advantages. :)

Still I'm surprised nobody seems to have sniffed OTA traffic - blocking access to the download server, via local DNS override, might provide another level of safeguarding against unwanted upgrades... wishful thinking only?
[Fire Android Development] TOCS88:
Just wanted to jump in and say THANKS!

I bought one of these cheap tablets last year and used a 'noob friendly' guide that appears to be abandoned now. Found this guide and it worked like a CHARM. Fully rooted and running google launcher with OTAs blocked no ads. (My 5th gen came out of the box with 5.1.1. Purchased on black friday 2016) My last fire survived a 2 year old for 10 months. We shall see how long this one lasts. I obviously ran all of this before every connecting to wifi to ensure I didn't get updated.

Thanks again!
[Fire Android Development] Tomsgt:
[YOUTUBE]iv0VcNM8IAw[/YOUTUBE]

https://youtu.be/iv0VcNM8IAw
[Fire Android Development] DB126:
Kingroot consumes few resources and hardly any data depending on the number of iterations. The algorithm for finding an exploitable vulnerability doesn't appear to be terribly sophisticated. Better than trial/error but not by much. Explains the wide ranges of experiences on nearly identical devices.

Blocking OTA traffic is more involved than shutting down a few domains/IPs. Many a Amazon device has spontaneously updated despite best efforts of the owner to block every IP/domain known to be associated with Amazon inc. On some devices this yielded non-rootable scenarios or worse - a non-recoverable brick. I have long since dropped the idea of sequencing OTAs at the network level. David vs Goliath taking on a massive CDN.
[Fire Android Development] filipr86:
rott after cm install

Hi

How to root device once cm is install. King root and superSU does not root device any longer? PLEASE support
[Fire Android Development] steve8x8:
CM (I just checked 20161122) comes pre-rooted, there's a /system/xbin/su present. You just need the SuperSU *app* (from the PlayStore or apkmirror) to assign (or revoke) root permissions.
[Fire Android Development] DB126:
SuperSU is not required - simply enable root access under Developer Options and reboot (required). SuperSU adds a layer of complexity that is not needed by many users. Not bashing SuperSU; I use it regularly! Just not necessary on this rom as the integrated root manager works well.

---------- Post added at 03:14 PM ---------- Previous post was at 03:07 PM ----------

See previous post for solution. However, if you attempted to root CM 12.1 with KingRoot (bad idea) there's a good chance you will need to reload FireOS and start over as KingRoot may have removed/damaged the integrated SuperUser binary (su).
[Fire Android Development] joefuf:
Hey guys,

Just grabbed a Kindle Fire 7" and I was hoping to get it rooted and Google Play ready. I was able to use the Google Play install zip, but when I went to root, I had some issues.

I am on 5.1.3, so I know that's not optimal. Am I correct in understanding that I need to use the SuperTool in the OP in order to downgrade to 5.1.2 and then I will be able to root? Just wanted to avoid bricking the thing since it seems as though restoring isn't as easy as Android phones in general.

Anything to know in general or be aware of about this process?
[Fire Android Development] platypoid:
yes you need to down grade to 5.1.2 . There is a Root Junky downgrade supertool on his site that I used to do that. Then use this supertool to root and install play store and whatever else it does. All the info is on the first page of this thread .
[Fire Android Development] joefuf:
Cool, thanks for the confirmation.

I went and got as far as Step 2 before I hit a snag. I was able to get Google Play on there fine (so the device drivers and adb drivers should be good on my Windows 7 laptop), but I get an error after getting into adb sideload mode that says "error: no devices found." Sure enough, Device Manager lists KFFOWI under Other Devices...

What am I missing?

---------------------------

EDIT: And the answer was that I needed this post from my friend [MENTION=4267571]sd_shadow[/MENTION] describing that you need to install the Android Composite ADB interface driver for this device within Device Manager. Currently 24% into the downgrade process, and hopefully I won't need to post for help again!

---------- Post added at 06:09 AM ---------- Previous post was at 05:29 AM ----------

Following my last post, I was able to downgrade to 5.1.2 successfully. Now I am having the same problem with rooting that I had earlier.

I make it into Fastboot mode just fine, but when I start the rooting process, I get an error that reads "FAILED <remote: unknown command>"

The message on the screen of my Kindle appears successful though, reading:

I've let it sit for a little while now, but I don't get the impression it's going to reboot on its own...
[Fire Android Development] platypoid:
You used Kingroot to root it ?

Did you test the fastboot drivers to make sure they work - one of the first steps .
[Fire Android Development] joefuf:
I don't think I used KingRoot. I used the root_fire.zip file that I got off of the rootjunksdl website. Was I supposed to use KingRoot?
[Fire Android Development] platypoid:
Did you get the latest version of Supertool ? Yes it uses Kingroot. Go back to about page 128 of this thread and start reading posts . Someone put a very detailed step by step on here somewhere - don't remember where exactly .
[Fire Android Development] joefuf:
I do not have the latest version of SuperTool. I didn't realize it was separate from the zips that I'd already downloaded in anticipation of receiving my Kindle in the mail today. Of course, now that I know that I need it, it looks like rootjunkysdl's website is down and I can't get to it.

I did download and install KingRoot before I realized I needed to downgrade from 5.1.3 to 5.1.2 in order to root, and I have gotten this far while I was waiting for your reply. It looks like it worked, but I don't understand Chinese to know the difference between the two options. I'll go back and look for what you're talking about in this thread unless I get my Google Translate app to tell me what this means before I get there...
[Fire Android Development] platypoid:
When you get the supertool it will remove kingroot and install supersu .

You should turn off the wireless until you get supertool so you don't get an amazon update . And so you don't get any of that Kingroot stuff going on either.
[Fire Android Development] joefuf:
I did manage to get to his website and download SuperTool. I ran it and removed KingRoot and it installed SuperSU. For some reason, my computer isn't detecting it anymore, so I'm about to reboot my laptop and see if that helps. I've already rebooted the tablet a few times to no avail. Looks positive otherwise.

I haven't connected it to my home wifi because I was afraid right out of the box it might try to OTA update and then I'd be in bigger trouble. I think I used one of the other tools to block OTA updates already, but I'll try with SuperTool after the reboot to be sure.

I think I'm just a new launcher away from being all set with this thing. I only plan on using it for eBooks, videos, and web surfing, so I don't know if I necessarily need to flash a ROM or CM to it to meet my needs. Opinions welcome though.

---------- Post added at 07:21 AM ---------- Previous post was at 07:01 AM ----------

Sweet, we're green across the board. Root, OTA blocked, and Google Now Launcher installed and defaulted.

I'm guessing this is the reason people would flash another ROM, but is there a good way of getting rid of the Amazon bloatware?
[Fire Android Development] DB126:
For awareness:

- Google Now launcher performs poorly on this device (lag) but carries other benefits that offset the disadvantages; Nova is a popular alternative

- once rooted ads and "bloatware" can be blocked/removed with appropriate tools but it is an arduous process

- custom ROMs offer a clean slate and dramatically improved performance; downsides include complexity (for some) and rebuilding app portfolio from scratch
[Fire Android Development] joefuf:
Thanks man. I'll keep an eye out for lag with Google Now. I have it on my phone, and I enjoy the Cards, so we'll see if that's worth the hassle if I come across any issues.

The last thing I did last night was go through with a Root Uninstaller app and remove a bunch of Amazon things. That was easy enough with a reboot. I got the 16gb variant, so I'm probably okay for space anyway.

I'll keep the custom ROM possibility in my back pocket. One thing I thought I read (but could be wrong about because I can't always tell which model a thread is referring to) is that playing videos on some ROMs is glitchy and you have to mess around with hardware acceleration? Is that accurate? I'd probably just be throwing an mp4 or mkv on it and using whatever the best Android video player is to watch a movie or TV episode.
[Fire Android Development] DB126:
Video playback was an issue with some early custom ROM builds for this but I haven't seen it mentioned lately. Most users stream video so there's always a small community with NetFlix or YouTube issues. Most are user specific and can not be reliably reproduced by the community. Local playback of mp4/mkv vids is less common.

If app space becomes a concern there are several 3rd party tools that facilitate migration to the SD card (ask when ready; you want something that supports 'symbolic links'). Lollipop's built in tools are not terribly robust and partially depend on developer support.
[Fire Android Development] Andal:
Any mirror for SuperTool? RootJunkySDL keeps crashing today.
[Fire Android Development] joefuf:
I'm uploading my Kindle files folder to my Amazon Drive right now. I should be able to share a link to the zip in a few minutes.

EDIT: Here is a link to the zip. Had the same problem with his website yesterday.
[Fire Android Development] viceless:
Thanks a TON, good sir! I've gotten to ~120MB 3 times in around 30 tries since last night. It was killing me, lol
[Fire Android Development] Mervingio:
Sorry to ask or maybe not read the entire thread but I need send my son's Fire Kids Edition back to AMAZON (he broke screen) so I use this tool to install PS remove ad on lock screen and block ota so I need remove all of this before send it back right?
[Fire Android Development] DB126:
If within warranty Amazon apparently has a 'no questions asked' policy on exchanges (never seen software customizations challenged). Just send it back as-is.

If you still feel compelled to restore it to 'factory' condition:

- perform a factory reset to remove personal apps and data

- reload FireOS via stock recovery; see forum index (post #4) for instructions
[Fire Android Development] xm41907:
I have three new fire 5th gen tablets that I am trying to root and I can not get this tool to work. All three tablets are running Fire OS 5.3.1.0 I have attached them via the cable and run the bat file. It comes up with the daemon started successfully and will show an attached device, but then the window just disappears. I have redownloaded the tool several times and have tried it on another Windows computer and the same thing continues to happen. I'm sure there must be something I am not doing right for it to happen on multiple devices through two different computers, but I can't find anything that would be causing this. What could I be doing wrong?

*Update* I downloaded the older version from your website and it loads into the menu just fine. Unfortunately, won't root 5.3.1.0 Could something have happened with the latest version when your website went down yesterday?
[Fire Android Development] platypoid:
Did you load the device drivers so it will show up on the computer without the tool ? And you must have enable adb debugging too ?
[Fire Android Development] Pond-life:
Some have been reported to have 5.1.1 on but that can now be rooted.

5.1.1 cannot use twrp to change roms, backup etc, though if rooted Flashfire will do this in a more limited fashion.

Nothing has been seen with a firmware beyond 5.1.1 yet
[Fire Android Development] TeckniX:
Bunch of issues while trying to root brand new amazon fire 7:

--------------------------------------------------------------------------------
[*] your device is rebooting and will inject root files.
--------------------------------------------------------------------------------
adb server is out of date. killing...
ADB server didn't ACK
* failed to start daemon *
error:
error:
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
error: device not found
adb server is out of date. killing...
* daemon started successfully *
3029 KB/s (5904943 bytes in 1.903s)
adb server is out of date. killing...
* daemon started successfully *
1535 KB/s (29972 bytes in 0.019s)
adb server is out of date. killing...
* daemon started successfully *
Unable to open /data/local/tmp/root_fire.sh: No such file or directory
adb server is out of date. killing...
* daemon started successfully *
/system/bin/sh: /data/local/tmp/root_fire.sh: not found
< waiting for device >

Same result after multiple tries
[Fire Android Development] Pond-life:
Someone else had that does doing what they did help?

From this post to the next few posts.

http://xdaforums.com/showpost.php?p=64371380&postcount=97
[Fire Android Development] TeckniX:
Removing device, doing a couple of test and making sure adb device driver was used made it work finally.

Thanks!
[Fire Android Development] Killerfish1450:
Yea, I had to do that the first attempt, now it just states that it is granting the access but the tool doesn't do anything. I used the tool gain root and supersu was installed.
[Fire Android Development] Tomsgt:
updated supertool with latest adb and fastboot files from google today
[Fire Android Development] godbilla:
Okay, it's been a minute since I've messed with a fire tablet. I haven't done any updates yet, so I'm still running 5.0 fire os. Will this tool work with 5.0? Sorry for the noob question. I skimmed through the thread real quick and didn't see anyone ask, so I'm sorry in advance if someone asked this question already.
[Fire Android Development] Pond-life:
Not sure about the rest of it but play store doesn't work with 5.0.0 from what I've read in other threads.

If you try to update to 5.0.1 which it does work ok with, keep wifi off on 5.0.1 until you've blocked ota.

Though if intending to use tool to go to TWRP and install a custom rom skip updating anyway and head straight to that rom
[Fire Android Development] dancress:
I get the exact same errors even after resetting everything to right out of the box (5.1.1. because I *expletive deleted* missed how evil that update is). Any pointers?
[Fire Android Development] mattzildjian:
I have my fire running fine now with nova launcher and no lockscreen ads, thanks!

Now I want to block OTA but you cannot do that without root, and I fear if I root, apps like sky go will not work, and this is a present for my dad, sky go must work!

Is it possible to block ota without root? I know an update will revert the launcher and I will have to start over each time, my dad won't understand.
[Fire Android Development] Pond-life:
On 5.1.1. not without using root at all. Though you should be able to rename/remove the ota files in the temp root in much the same way the supertool blocks the adverts or switches to Nova.
[Fire Android Development] Moose66:
Wish I had bought the 7 instead of 10. Didn't realize that you couldn't put gapps on the 10 or am I misreading something?
[Fire Android Development] DB126:
Wrong forum, try Amazon Fire HD 8 and HD 10
[Fire Android Development] FrankieChen:
Help appreciated for rooting a 5.0.1 device using this supertool.

I successfully installed and tested the adb and fastboot drivers and then selected option 7 "Root your Amazon Fire 5th gen". I took the 1st option for devices 5.0.2 and under.

It seemed to go well, getting

[*] waiting for device

[*]

4524 KB/s (4017098 bytes in 0.867s)

--------

[*] supersu is pushed to device

--------

[*] press any key to reboot to recovery

<waiting for device>

downloading 'boot.img'...

OKAY [ 0.326s]

booting

OKAY [ 0.055s]

finished. total time: 0.385s

-------

[*] once TWRP recovery Boots up swipe to allow modifications

[*] then select install and navigate to SuperSu-v2.46.zip on the sdcard

[*] select it then swipe to flash once finished select reboot system

--------

[*] When the device has fully booted up you will have root access.

[*] check in the app drawer for supersu app.

[*] Note now that you have root please block ota updates option 3

[*] so that you can keep it safe.

------

Press any key to finish

But I never went into TWRP recovery and there wasn't any supersu app installed.

As the video shows what happens when you take the option for 5.1.1 I don't know what I should be expecting.

I ran the boot again and got the same result.

Not sure what I should do.

I don't have an SD card and wondered if that had something to do with it?
[Fire Android Development] Pond-life:
No the sdcard the batch file mentions is actually part of the internal memory.

It hasn't installed the app, that you'd do with twrp if it had gone into it, it should though have copied the supersu zip file to your fire ready for install though, so take a look for that. If it's on the fire, then try the 5th option on supertool to boot to twrp, though don't know why that part didn't work in the first place. And then follow the instructions to install it
[Fire Android Development] FrankieChen:
I think it hasn't installed the app as I checked under Settings>Apps & Games>Manage All Applications but Supersu and TWRP aren't showing.

I forgot to mention in my previous post that once the Fire reboots I get a popup message that says

USB Compatibility

Some computers require a free file-transfer utility to copy files between the computer and your Fire. If you need this utility, please open your computer's browser and navigate to kindle.com/support/downloads. Your computers USB port is a low-output power source that will slowly charge while your Fire whilst it is asleep and may not charge whilst in use.

I looked at kindle.com/support/downloads and selected the UK option but was just presented with an empty screen that asked "Was this information helpful?"

I'm using Windows 7 Home Premium Service Pack 1 - don't know if that has anything to do with it.

EDIT

Apologies, I've found the Supersu.zip file in Settings>Storage>Internal Storage>Miscellaneous.

I think from what you've said that I should now take the 5th option " Boot device to TWRP Recovery" from Rootjunky's supertool script and that will instruct me what to do with the supersu.zip file?
[Fire Android Development] Pond-life:
I said it hadn't installed it.

TWRP will not show as an app on device at any point btw.

I asked you to look for the file on the sdcard so you can try to reboot to twrp and install Supersu. But probably don't have a file browser installed on the Fire.

Does it show as device in Windows 7? Thought the file transfer thing was only needed for xp. Not that it makes any odds for adb and fastboot modes anyway, but if it does show you could look in Explorer at the Fire to see if the SuperSu-v2.46.zip is on there.

You have kept it off of wifi?
[Fire Android Development] FrankieChen:
Sorry, crossed posts. I just edited my last post saying I've found the Supersu.zip file in Settings>Storage>Internal Storage>Miscellaneous.

I haven't connected to wifi yet (in fact I put it in airplane mode just to be safe - could that have anything to do with it?)

You're also correct in guessing about the tablet not being shown as a device in Windows explorer. I have been rebooting / switching the tablet on and off/ using a different usb port but it doesn't seem to make any difference.

So the next thing I need to do is take the 5th option " Boot device to TWRP Recovery" from Rootjunky's supertool script and that will instruct me what to do with the supersu.zip file?
[Fire Android Development] Pond-life:
That's good then, if you can get it into twrp then it can be installed

No, keeping it off wifi is good, just wondered if it might've sneakily put 5,1,1 on while you weren't looking.

You might need that transfer app for windows 7 then, still doesn't matter right now as we aren't using ut.

It won't instruct you what to do, but you have the instructions already (you quoted them in the first post you made), if it will boot into it we flash it on there.
[Fire Android Development] mattzildjian:
Can you elaborate on this? Are you saying renaming those files will stop OTA working? Effectively blocking OTA?

Quick question: are ota forced? Is it easy to just dismiss an update and never install it?
[Fire Android Development] xm41907:
yes and yes
[Fire Android Development] DB126:
Normally I would never point to an 'unofficial' download location but your question seems relevant given behavior differences between current and previous versions of the SuperTool (shouldn't happen). See below.

http://xdaforums.com/amazon-fire/de...-5th-gen-supertool-root-t3272695/post70092699
[Fire Android Development] platypoid:
Look at message 1377 -- a user has the newest version of supertool available

http://xdaforums.com/showpost.php?p=70092699&postcount=1377

Also check out this post for concise step by step instructions

http://xdaforums.com/showpost.php?p=69936186&postcount=3691
[Fire Android Development] xm41907:
I got the tool working and installed Kingroot. It's not rooting the devices though. I've tried it several times on each one and always it fails. Tonight has not been my night. I've never had such trouble rooting devices before.
[Fire Android Development] platypoid:
Do you have the wifi on ? You need that to have it do it's root. Reboot too I think . I had to try a bunch of times also - finally worked . Others have used the desktop version of Kingroot.
[Fire Android Development] xm41907:
At first I didn't because I didn't want the OTA update to download. But I realized it needed network access, so I granted it. I've tried about 5 times on each device. How many did it take for yours to work?
[Fire Android Development] platypoid:
I don't remember now - a bunch ! Maybe Davey's advice will help you

http://xdaforums.com/showpost.php?p=70042765&postcount=2
[Fire Android Development] steve8x8:
You're running the bat file directly from the folder? Open a terminal session instead, and run it from the command line - this way the window will not disappear and you got a chance to read the output if there's any.
[Fire Android Development] xm41907:
Well, I was successful with two of the three. The third upgraded before I could get to it (should have kept wifi off) now it's stuck on 5.3.2.1 I guess I'm out of luck getting this done before Christmas. Oh well.
[Fire Android Development] platypoid:
Better not try to downgrade that 5.3.2.1 or you may brick it

Read on here

http://xdaforums.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/page12