yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] Pond-life:
Sounds like you need to look at fastboot mode drivers again then unfortunately. When you initially said "I successfully installed and tested the adb and fastboot drivers" I assumed they'd passed the test, but those seem to be the problem.

Did you download it before or after Tomsgt said that he'd added updated ones to the supertool? Some computers don't seem to get on with the ones that were there before I used the drivers direct from amazon.

---------- Post added at 08:15 PM ---------- Previous post was at 07:46 PM ----------

Well you'd need to use the temporary root same as the supertool did root it temporarily when you switched to nova and blocked the ads. Your tablet has already been rooted, it's just not permanent. So you'd utilize the same temporary root and find the ota files and rename them. Can't talk you through it exactly as I immediately rooted mine properly and deleted them all in ES explorer.

When in temp root you could try the last three commands in this post.

http://xdaforums.com/showpost.php?p=64351445&postcount=54

No clue on the network, never seemed reliable method to me, and don't know if the tablet uses the same servers even.

---------- Post added at 08:17 PM ---------- Previous post was at 08:15 PM ----------

It gives the option to delay but think it then updates when you next reboot. They want everyone to update remember so wouldn't make it easy to ignore them.
[Fire Android Development] blueberry.sky:
It's not a good idea to try to block OTA via your router. People tried it with a different amazon device, amazon switched update servers & all those people got updated. To have a chance you'd need to block the entire range of addresses that amazon owns but then no amazon services would work.

See this thread on how to access temporary root.
[Fire Android Development] mattzildjian:
Thanks for the info.

If the other options like remove ads and install nova actually temporarily root the device, why does the disable ota option state that it requires root?

It would be great if there was a disable OTA option that just temp roots like the other options!

Well if I was to root and disable OTA, can I easily unroot after while keeping ota disabled?
[Fire Android Development] Pond-life:
I came to reply to the bit you edited out :D Guess I won't :D

Yeah that does seem risky plan with router.
[Fire Android Development] blueberry.sky:
I edit so often, I barely recall what it was!
[Fire Android Development] Pond-life:
I wondered why it was done that way as well tbh, seemed like it could have been done with the same temp root method as those, maybe just didn't occur to him at the time to do it that way and just used method closest to the old way. Could be there is a reason I'm not seeing that it needed to be done with the permanent one.

The temp root just goes after reboot, not sure whether the permanent root would leave anything behind if unrooted that apps could spot. But unrooting wouldn't re-enable the ota.
[Fire Android Development] mattzildjian:
I wonder if there is a reason for it.. Perhaps the developer will fill us in?

I don't mind rooting the device to disable OTA as long as I can unroot after, but there is no unroot option in this supertool, how would I do it?
[Fire Android Development] pappasmurfsharem:
Why not root?

The whole point of blocking the OTA is so that you CAN root and not lose it.

It doesn't make sense to block the OTA if you don't intend to root. :confused:
[Fire Android Development] Pond-life:
SuperSU app has a "Full Unroot" in the settings menu. I've never used it.

---------- Post added at 08:41 PM ---------- Previous post was at 08:36 PM ----------

It's not, for some the point is to block the ads, change the launcher, install google play store and know that a future ota wouldn't revert it all. Especially if the device is going to someone else as in this case.

He said why he doesn't want root as the Skygo app looks for it and then refuses to work if found. Several of the tv apps over here do that.
[Fire Android Development] mattzildjian:
Can anybody confirm this will work? Any volunteers to test it? :)
[Fire Android Development] Pond-life:
Well they need to have Skygo too...
[Fire Android Development] mattzildjian:
Hmm, ok looks like I gotta take the risk and see what happens. If I boot into TWRP using the supertool can I make a full backup that I can revert to if needed?
[Fire Android Development] pappasmurfsharem:
Then you just need to do the fastboot "temp root" method on the first post

Then hide the 3 ota files through adb shell

Edit:

Also there is the "hide my root" app
[Fire Android Development] Pond-life:
That's what I suggested trying last page somewhere.

Skygo seems better at spotting root than HBO apps for example, it doesn't work on some devices that haven't even been rooted as it's so zealous in it's application of root checking.
[Fire Android Development] pappasmurfsharem:
Download the Super Tool.

Extract the ZIP to some folder

Open a CMD Prompt (Shift + Right Click > in some "white space" in the Super Tool Folder > Click Open Command Window Here)

[IMG="Stuff"]http://i.imgur.com/Gxu3HXM.jpg[/IMG]

Paste the following

adb reboot-bootloader

when you see FASTBOOT on the screen

fastboot oem append-cmdline "androidboot.unlocked_kernel=true"
fastboot continue
adb wait-for-device && adb shell

Then

pm hide com.amazon.otaverifier
pm hide com.amazon.device.software.ota
pm hide com.amazon.settings.systemupdates
[Fire Android Development] mattzildjian:
Will try this now. THANKS

Worked Perfectly! Much Appreciated!!
[Fire Android Development] Tomsgt:
to answer your question on ota disable. I did it without using temp root for 2 reasons. one it is faster to just use supersu root access and doesnt require a bunch of reboots and 2 if you are blocking ota updates its because you want to keep root. so that made sense to me at least :)
[Fire Android Development] jhedfors:
At this point, it is currently not possible. Check out the General section. The highest version that can be rooted is 5.3.1.0. You are limited to the non-root tools available.
[Fire Android Development] Canon7:
Ok, thank you.

Will there be a chance soon?
[Fire Android Development] DB126:
There is no timeframe. It could be tomorrow or never.
[Fire Android Development] Catastropeace:
Hey there I am looking for an updated guide for the Fire Tablet (5th Gen) I am on FOS 5.3.1. I am quite sick of the random apps being installed on my Tablet when I am asleep and these annoying lockscreens. Amazon keeps pushing their products one me when I try to watch a show on my Fire and it's incredibly annoying. Is there an updated 2016/2017 guide for jailbreaking/hacking this tablet to get rid of this annoying crap? I got the play store on here already.

Update

The damn thing installed 5.3.2 on my tablet without even asking me. The hell is this?
[Fire Android Development] DB126:
1) Turn off WiFi and leave it off (or risk getting another OTA)

2) Check version of FireOS. If 5.3.2.0 there is (with some effort) the possibility of blocking further updates or installing a custom ROM. If 5.3.2.1 then nothing can be done at this time.
[Fire Android Development] Catastropeace:
Bleh. It's too late then. :/

---------- Post added at 04:27 AM ---------- Previous post was at 04:20 AM ----------

Bleh. It's too late then. :/
[Fire Android Development] Wishkah420:
I bought 3 5th gen fire tablets, one for each of boys and one for myself. They are running 5.1.2 and I spent all day yesterday trying to root and get a ROM installed. I'm using rootjunky's script and it will put kingroot on and after a few tries i successfully obtain root, i confirm withey joeykrim's rootchecker.

My problem is after obtaining root per the script I hit any key to remove kingroot and replace with superuser. This is where i have a problem, it removes kingroot but superuser doesn't get installed. I tried installing superuser and busy box from the play store but the binaries won't update and root is lost when kingroot is removed.

I also saw in another thread that the root.sh is missing a / on line 17 so I added that with notepad++ but it didn't change my results.

Can some please help me keep root and switch to superuser so I can use flashfire. Any help is greatly appreciated! Thank you!
[Fire Android Development] TechDad378:
Verify the superuser.apk is in the zip file/folder. Double check you are using the correct tool version.

TD378
[Fire Android Development] Wishkah420:
Superuser is there and the version is correct. I used the supertool straight from rootjunky's website.

The downgrade tool worked perfectly to get me to 5.1.2 it's the supertool root process that is giving me a hard time. I guess i run the downgrade tool again to wipe it and then try the supertool again... I was just hoping once i was rooted with kingroot there was another method of swapping it with superuser.
[Fire Android Development] TechDad378:
Downgrade from version x.x.x?

Seems you are missing a step somewhere or the proper drivers.

Post OP has more of a familiarity with the script and the processes. Hopefully he'll chime in :cool:

TD378
[Fire Android Development] Wishkah420:
The tablets came with 5.1.3 and I have successfully downgraded to 5.1.2 so I know my drivers are fine. I'll keep at it, I've been rooting devices since the sdk days but have never had this type of difficulty. Usually it's something silly but I'm not good enough with the scripts or adb to just manually try to replace kingsroot with superuser. Damn Amazon and their super cheap tablets, normally I buy Samsung but if I can get Android on these things it'll be great. I feel like I'm halfway there since I can establish root with kingsroot.

EDIT: Found a thread that had me replace the mrw folder and now I'm rooted and rom'd! [emoji106]
[Fire Android Development] cwhy:
Which thread did you mean in your edit? I can't seem to find it
[Fire Android Development] Rbohannon89:
Please help me .

Please do explain how you accomplish this?
[Fire Android Development] DB126:
You were advised in a different thread that FireOS 5.3.2.1 and above can not be rooted or downgraded. The contributor in the post that you quoted was running 5.3.1 which is the last (highest) rootable version of FireOS.
[Fire Android Development] Mirkoitalia:
How restore the ota updates?

I
[Fire Android Development] DB126:
Unless you know how OTA updates were originally blocked (multiple methods) best approach is to reload the *same* version of FireOS that is on the device now. Just be sure this is what you really want as there is no going back.
[Fire Android Development] Mirkoitalia:
I have v5.1.4 now.

Can i update to 5.3.1? (still compatible with this tool)

I read that v5.3 is more faster than v5.1.4
[Fire Android Development] DB126:
You can sideload 5.3.1 and may experience a temporary performance boost as a result of that activity (refreshing the OS). However, there is no evidence 5.3.x holds any long term performance advantage over 5.1.x.
[Fire Android Development] BeeWall:
As Davey126 said, you can sideload 5.3.1. However, I don't think 5.3.1 is downgradable, in case you ever want to go back for some reason. For best speed, I would recommend a custom ROM, unless you need something from FireOS that you can't get on stock Android.
[Fire Android Development] xConfusion:
Pulling my hair out

I am running Fire OS 5.3.1 using rootjunkys super tool since I am still a noob in all this. And was expecting a little struggle but not being completely lost. For life of me, I am unable to get KingRoot to root the device. I used version 4.9.2 of kingroot that comes packaged as part of the super tool, probably like 4-5 times. Gave up on that and even tried Kingroot's desktop utility, and got failed there as well. Always getting failed to root.
[Fire Android Development] daranman:
Sometimes a watched pot doesn't boil. It took maybe about 40 times of restarting the app immediately after reboots and not getting root to try something different, by just starting the app, and letting it do its thing, and not touching the phone until it returns back with a "Fail". It eventually will work, and what ever you do, don't even think about downgrading to 5.1.2 or 5.1.1 .

You could try doing a factory reset before running the supertool, as it might not get hung up on something left over.
[Fire Android Development] Blu8:
Sorry if I'm making some of you sound like broken records, but from my reading of different threads some seem to not really be on the same page. What I can gather right now is that my 5th gen 7" fire tablet on 5.3.1.0 is rootable with KingRoot included in this supertool (correct me if I'm wrong please) but where I get a little confused is this: once rooted with KR and after replacing it with SuperSU, can I use FlashFire to install a ROM? Slim perhaps? TIA
[Fire Android Development] BeeWall:
Yes, you can root your device. It may take several tries, and requires WiFi for the first part, so if you can, block the update servers, which are

After the device reboots, turn off WiFi so updates do not download. Turn it on and off as necessary. Then, you can also flash a ROM with FlashFire after replacing KingRoot with SuperSU. Currently, Fire Nexus is the only ROM under active development, but the others such as SlimLP are still good, and better than FireOS for sure. You should be able to flash SlimLP, wiping data, cache, dalvik, and system data. Be sure to drag the wipe action above the flash action after adding it, or you will have to start over from a fresh FireOS install.
[Fire Android Development] Skar3:
Sharing my experience with version 5.3.1.0:

I tried several times using the kingrooot application unsuccessful. In the end I used the desktop version, the program has reached the 35% then the message appears that the device could not be rooted, I checked and kingroot was installed correctly and the root was present. Through Supertool I installed supersu without any problems!
[Fire Android Development] Vanb85:
Someone may have answered this already, but I haven't read through this entire thread. I'm on 5.3.1, attempting to root using the RootJunky Supertool. I've tried about 5 or 6 times already without success. I know that you have to keep trying, but now the process is stuck at "Verify Root Status..." It just won't take me past that screen. Is there anything that I can do to get the root process started again? Prior to this the highest that it got was about 70%.

eta: I think that the new update has downloaded but hasn't installed. Should I try a factory reset?

eta2: So, I went ahead and did the factory reset, and that at least got the process started again, but I'm still unable to get it to root. I can't really help the update downloading, because it seems to do that automatically as soon as I set up my internet connection. It hasn't installed; it just downloaded and is sitting there waiting for an opportunity to install itself or for me to manually install it.

eta3: I was finally able to get root access. The fact that the update downloaded to the device didn't seem to make a difference, as long as it doesn't install, which it didn't have a chance to do as the device wasn't idle while I was trying to get root access. I've blocked ota updates, and I'm good to go.
[Fire Android Development] DB126:
If the update fully downloaded do an immediate factory reset to clear the files as it will only wait so long before auto-starting. Clearing the cache from stock recovery may also work.

After a factory reset do NOT register with Amazon when device restarts. That should slow OTA update delivery and also seems to improve odds of rooting.
[Fire Android Development] Vanb85:
Thanks for the reply. As I added to my post above, the downloaded update doesn't seem to have mattered. I was able to root the device anyway. I refrained from registering when I did the factory reset, but that didn't seem to slow down the download of the update. It started to download pretty much immediately as I was getting to the home screen. By the time I went to turn off the wifi, the update was almost completely downloaded. I do wonder if not registering the device gave me a better shot at getting it rooted. That seems odd, and I'm not sure why that would be the case, but I won't look a gift horse in the mouth. I'm rooted.

This is a brand new device. I didn't think that I would even get the opportunity to try to root it. I thought that it would ship with the updated software. I ordered it on Saturday night when it was on sale. I'm guessing they were getting rid of old stock. Just FYI for those looking for tablets with older versions of Fire OS still on it, just in case they go on sale again.
[Fire Android Development] DB126:
You need to get rid of the downloaded update. Depending on the method used to block OTA updates it may still attempt to install and might actually be successful. You have been warned.
[Fire Android Development] Vanb85:
Where are downloaded updates stored?

eta: I think I found it. I saw one of your posts from another thread.

I went to the root directly and didn't see any loose files with that description. I looked in the cache folder and found this:

update-ford_full_ford-552153720-to-560177220.bin

I saw in another thread that the codename for one of the updates for the Fire 5th Gen was "ford." It was about 97 MB. I wouldn't call that huge, but I'm guessing that it hadn't finished downloading. Maybe that's why it was in the cache folder. I think that's it. Is that what I needed to delete?
[Fire Android Development] DB126:
Yep - glad you found it.
[Fire Android Development] BobCat78:
evening all,

Will this still work on 5.0.1? all the info appears to suggest 5.1.x+

thanks for the help
[Fire Android Development] ndg_2000:
I've used it for 5.0.1 no issue's boots mine into TWRP for flashing and helped me recover from boot loop so worked fine
[Fire Android Development] BobCat78:
Windows 10 x64 too? Or do i need to switch to a win7 pc?

Really appreciate the help
[Fire Android Development] BobCat78:
Worked like a charm, thanks again
[Fire Android Development] Rbohannon89:
Can some one provide a link to older fire os firmware 4.1.1?
[Fire Android Development] sd_shadow:
there is no 4.x.x for 5th gen Fire

if you meant 5.1.1 see index

[Index]Amazon Fire 7" - 5th Gen-2015
[Fire Android Development] Rbohannon89:
I'm trying to root it. It updated in sleep mode to 5.3.3.0 I want to downgrade it to a older firmware so I can root and install custom recovery.
[Fire Android Development] sd_shadow:
downgrading with brick the Fire

---------- Post added at 06:32 PM ---------- Previous post was at 06:31 PM ----------

there is no unbrick method if downgraded
[Fire Android Development] Rbohannon89:
So I can't downgrade to root. How do I root it?
[Fire Android Development] sd_shadow:
cannot right now
[Fire Android Development] DB126:
You're done; no root (at present); no downgrade (likely never). Enjoy FireOS for what it is or contact Amazon for a refund if recently purchased.
[Fire Android Development] justdownload.t:
The download page seems to be down, does somebody have a backup of the Supertool and could upload it somewhere maybe?
[Fire Android Development] DB126:
It's fine now; patience is a virtue. Last thing we need is rogue links to obsolete software floating around.
[Fire Android Development] sd_shadow:
download seems to be fine
[Fire Android Development] Phanco:
Reset my Fire

Hi guys,

I have previoulsy used supertool to root my Fire, install google play, remove ads and block ota uodates.

I now wish to move the tab on - if i reset will the device revert to stock (so can be returned to amazon) or will it still be rooted etc so they would know it had been modified.

Ta for any advice
[Fire Android Development] steve8x8:
Factory reset will clear the writable partitions but not /system (where the OS itself resides).

Root (su) lives in /system, but comes with a way to unroot (check the details on the app page).

Amazon usually doesn't care about what you did to the device if you ask for courtesy replacement.
[Fire Android Development] commerce:
Impossible to root

I have a brand new Fire 5th gen. (KFFOWI) with 5.3.1.

Twice it upgraded to 5.3.2., but I downgaded it back to 5.3.1.

Many attempts to root it both via using the app and also with the desktop version were unsuccessful.

Is there any other way to root?
[Fire Android Development] DB126:
KingRoot is the method of choice. To improve odds perform a factory reset and do not enable WiFi or register with Amazon during initilization. Keep WiFi off until just prior to wacking the 'go' button in KingRoot if using the app (no WiFi connection is needed for desktop varient). Disable WiFi after device reboots or 1-2 min. But then KingRoot will have downloaded its payload and no longer needs a network connection.

KingRoot is fairly unsophisticated attempts to identify a vulnerability that can be exploited. Seems to try stuff at random and gives up before exhusting all possibilities. Subsequent runs don't take into account prior learnings. It's hit and miss.
[Fire Android Development] Phanco:
thanks,

so if I factory reset, it will still have SU installed but I could at least pass/sell it on ....

would it still have all the fixes (i.e google play, no ads, no firmware updates ) ...
[Fire Android Development] commerce:
Thank you for your advice.

Eventually I was able to root (lose rooting and re-root multiple times) and several hours later also to flash Nexus ROM.

Very complicated. But now I have an Android tablet...
[Fire Android Development] DB126:
Not certain - if the Play Store installation method stated 'no Root' then it will likely be lost. OTA blocks *should* remain enforce but again depends on the method(s) used. As you might imagine a similar comment applies to ads.
[Fire Android Development] DragonFire1024:
If you have your tablet's setting selected to save WiFi passwords to the Amazon Cloud or Google, I found you also have to deactivate that feature before a factory reset. If it's enabled to save passwords, that setting will be applied and enabled on your device when you turn it on again.
[Fire Android Development] Rbohannon89:
I was wondering why Amazon has not updated to Amdriod 7.0. That being said is there a way to get nougat on this device?
[Fire Android Development] DB126:
- FireOS is heavily customized; takes considerable resources to get that right

- Android 5.x base is adequate to support Amazon's target customer base

- only Lollipop custom ROMs at present due to locked bootloader/kernel that won't support Android 6+
[Fire Android Development] chris4507:
Like an idiot i tryed downgading from 5.3.3 to 5.3.1 and now wont turn on is there a way to unbrick or even get it to be reconized in windows to adb firmware back on?
[Fire Android Development] DragonFire1024:
You can try holding the power button and either the volume up or down keys in at the same time to see if it will boot into safe mode. If so, from there wipe the cache, then factory reset. There is also a thread here that might help with a reset.
[Fire Android Development] chris4507:
Thank you for your reply but sadly no avail if it bricked it bricked these things happen always a learning curve lol but feel free if you have anymore ideas that i can try i will be greatful
[Fire Android Development] DragonFire1024:
This is the only other option I can think of and that I have bookmarked. I recall seeing instructions on how to do it using ADB, but I can't find them right now.
[Fire Android Development] chris4507:
Tryed that already didnt work but thank you for your help time for new tab i think lol was outdated anyway lol
[Fire Android Development] DragonFire1024:
The last option I can think of, download firmware and follow these steps if you can. If not, I am afraid I don't know of any other ways. Hopefully someone else can chime in with a fix. Nonetheless, good luck! :D
[Fire Android Development] chris4507:
Thank you for beeing so helpful but issue is cant get windows to reconized tablet as it wont power on
[Fire Android Development] DragonFire1024:
Without it powering on, I'm not sure anything can be done. Have you tried leaving it plugged in and letting it sit like that overnight? I know it's a stupid question lol. Mine powers on as soon as it's plugged in. I'm not sure if that's Amazon or the settings.