yashsingh1/xdaforums huggingface dataset:
[Fire Android Development] Echoecho33:
Supertool worked (for me) 5.1.3, but...

Hello there. I am new to XDA, and Kindle Rooting in general, but I have a question (at the bottom of the page). I'll quote my post in another thread, if you want the background information

I am thrilled (I kept reading that it wasn't supposed to with this Firmware version)!

So here's my questions:

After disabling the OTA updates (via the Super Tool) I go to Settings - Device Options - System Updates to verify that it did "freeze" and as soon as I hit the "system updates" part, the screen flashes but then goes back to the first "Settings" page. Is this okay? How do I know what OS it's running on now?

Did I screw something up by not downgrading to 5.1.2? Should I do anything about this?
[Fire Android Development] DB126:
Welcome to XDA and the Fire forums. Recently KingRoot has acquired the ability to root FireOS 5.1.3; you are the second or third individual to report success in this area. No worries.

The response you are observing is characteristic of a device that has OTA updates blocked.

As an aside, best not to cross post questions to help keep the forum clean. Same folks monitor most of the threads.
[Fire Android Development] steve8x8:
First, congratulations for rooting a 5.1.3 - this proves that KR is still evolving and one day may be able to tackle 5.3.2.1.

To find out which *bootloader* you're running you may use the "whichpl" script from my GDrive (see sig). It requires root (sorry, but otherwise no access to the BL partitions). If you really got 5.1.3 preserved, then I'm interested in the "build stamp" output - nobody found a flashable 5.1.3 yet, and I couldn't extract the BL files for fingerprints. Thanks in advance!
[Fire Android Development] DB126:
FYI - signature blocks do not display in XDA labs and other apps used to access XDA content.
[Fire Android Development] fuzzynco:
figuring out what OS (/system) I'm running

I have a fireOS 5.3.x system with 5.1.2 bootloaders.

Supertool's block updates has a side effect of breaking the

the device's notification of what OS its running. Otaverifier

I think reports that.

Is there anyway to figure out with software what /system (OS version),

I am on? Whichpl reports 5.1.2 and since Alexa works so it is at least 5.3.2.

Originally downgraded from 5.1.3 to 5.1.2 via sideload.

then supertool to root via kingroot/supersu,

disable updates and play store.

I then used flashfire to 5.3.2 while keeping

5.1.2 bootloaders and supersu + google pico.
[Fire Android Development] Echoecho33:
I'm sorry, I am so new to this. I don't understand what you just advised.
[Fire Android Development] anatoliy@forex.ua:
I installed the OS from Amazon OS 5.1.2 to Android 5.1.1. (Lollipop). It worked a few days and started intermittently working sensor and I decided to reinstall another Android 5.1.1. After reinstalling the tablet does not turn on. Then I went in fastboot and through ADB installed Amazon OS 5.1.1.

The result: the tablet when turn on does not show screen AMAZON, that is does not react to pressing the power button. When connected to the computer constantly appears and disappears "PreLoader USB VCOM Port".

Tell me, please, how can I restore the tablet after that?
[Fire Android Development] steve8x8:
Running "uname -a" in a terminal emulator will identify the kernel version and build date. If you are root, you may also read /system/build.prop, which contains a number of version strings:

ro.build.version.incremental=37.5.5.2_user_552153420
ro.build.version.number=552153420
ro.build.version.name=Fire OS 5.3.1.0 (552153420)
ro.build.version.fireos=5.3.1.0
ro.build.version.fireos.sdk=4
ro.build.version.fireos=5.3.1.0
ro.build.version.fireos.sdk=4
ro.build.version.sdk=22
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=5.1.1
ro.build.version.security_patch=2016-05-01
ro.build.version.base_os=

That's as close as you can get, I suppose.
[Fire Android Development] DB126:
You posted the EXACT same question in at least four different threads.

You bricked your device; it is not recoverable. A little more reading/research will help avoid writers cramp the next time around.
[Fire Android Development] fuzzynco:
[Resolved] How to find fireOS version

When otaverifier has been removed to avoid updates.

As suggested I used a root shell and looked for the

tag in build.prop.

cat /system/build.prop | grep 'ro.build.version.name'

which told me what the system thinks it is.

thanks :)
[Fire Android Development] TechDad378:
Great job with this tool! This is very helpful with Amazon Fire ?
[Fire Android Development] steve8x8:
Just a quick remark.

While I've been waiting for a newer release of RJ's SuperTool, I found that there's no need for one, and the Nov 28 version is probably still the best you can get.

KingRoot 4.9.2 (the Kingroot.apk in the apps folder) is fine, and removal/replacement techniques are under good control - while 4.9.6 has some surprises under the hood, and 5.x.y has a lot more of them (the dev admin "feature" being the most prominent).

My advice is, keep 4.9.2.

If it doesn't work properly, disconnect the device from your account, and remove the SD card (if you plugged one).

Find a WiFi that's slow.

Block DNS requests for known OTA hosts, if you can.

(Now I wish I had modified RJ's script to keep a backup copy of OTA packages (otaverifier, DeviceSoftwareOTA, SystemUpdatesUI) like it's done with FireLauncher... would be interesting to know which FQDNs are hidden inside them (and whether those have changed between fireOS versions). Got to find a way to "read" system.new.dat files.)
[Fire Android Development] jaladhjin:
Isn't workin' for me :(

I've got Kingroot 5.0.3 & some change on a Kindle Fire 5th gen..

Currently on FireOS 5.3.1

I unchecked the Device Administrator box.. & am on my 3rd reboot now of tryin' to get SuperSU to take over..

Is your tool just batching these instructions & files ? http://www.w0lfdroid.com/2015/05/How-to-Remove-Replace-KingUser-KingRoot-with-SuperSU.html

I've tried that with Terminal Emulator & the 2.4 zip as well..

Also tried letting SuperSU attempt to take over & remove other root management utilities as it seems to want to do when it pops up.. no dice :(

Any suggestions ?
[Fire Android Development] DB126:
Best guidance: reload FireOS (same version as you have now) and then reroot with KingRoot 4.92 which is more easily transitioned to SuperSu. Hundreds have done it before you and managed to avoid the dreaded OTA update. Partial downloads OTA downloads are erased on every reboot and KingRoot reboots frequently. Find a slow AP (library, coffee shop, etc) and you'll be fine. Recent versions of Kingroot have malware like characteristics. Avoid v5.x if at all possible.
[Fire Android Development] jaladhjin:
That might be what I end up doing but since it isn't a main device of mine I also don't mind waiting for the new breed of anti KR countermeasures..

And have been mentioning to anyone that might find it useful I'm more than willing to use my device to test potential fix scripts & updates to apps like SuperSU-Me..

So fingers crossed.. we'll see what the future holds :)

Thanks for all your advice specifically as well.. very much appreciated
[Fire Android Development] Mervingio:
Sorry to ask but today I received the new replacement for my son but have 5.3.1.0 again sorry to ask but this can root??
[Fire Android Development] DB126:
Yes - it can be rooted as-is. Be sure to keep it off the network (airplane/flight mode engaged) as Amazon will eagerly download and install FireOS 5.3.2.1 which can neither be rooted nor rolled back.
[Fire Android Development] Mervingio:
We'll say is already downloaded by itself but not installed yet I use this tool a year back so not want brick [emoji16]
[Fire Android Development] DB126:
You'll want to erase the downloaded update as it will likely install on the next boot. Easily identified: large file ending in '.bin' located in 'internal storage'.
[Fire Android Development] Mervingio:
Damn it I power off the tablet [emoji24] [emoji24] [emoji24]
[Fire Android Development] sd_shadow:
reboot to recovery, wipe cache
[Fire Android Development] Mervingio:
Did you know how? Ilittle lost with this table
[Fire Android Development] sd_shadow:
hold volume up button and power on
[Fire Android Development] Jimmy1life:
So Im stuck with it at 5.3.2.1 is there any chance that will get cracked and rooted or down grade able? The update was dec 25th 2016.
[Fire Android Development] DB126:
No one can predict the future. Could happen tomorrow or never. 5.3.2.x looks to pretty tight; might be a long wait.
[Fire Android Development] Mervingio:
I'm on 5.3.1 but trying to root with Kingroot but tried many times and can't root.....I used this with my LG Pad 7 tried for months and one day Boom Rooted.
[Fire Android Development] DB126:
Lots of tips in this thread on improving KingRoot run quality. Keep trying.
[Fire Android Development] Mervingio:
All right is ROOTED!!!! now trying to install SuperSu but get few errors but still Rooted with Kingroot.
[Fire Android Development] TechDad378:
Could not root 5.3.2.1 after multiple times. Installed google play via "Super Tool" and downloaded the app "purify battery saver". Gave both king root and purify full access via setting, then root was achieved. Tried the steps a few times and was successful each time when rooting. Not sure why the battery saver app helped but just providing my results.

After accomplishing root, the device reboots and I turn off WiFi. While WiFi is off used super tool for a few changes it provides.

Hope this may help or maybe it was just odd outcome, you decide!
[Fire Android Development] DB126:
Thanks for sharing. Started a new thread to capture results:

https://xdaforums.com/amazon-fire/general/5-3-2-1-root-t3547136
[Fire Android Development] Duke91:
What Kingroot version did you use?
[Fire Android Development] TechDad378:
Used the KingRoot version provided by "Super Tool".
[Fire Android Development] DeLonge:
root still not work for 5.1.3? so I must downgrade to 5.1.2?
[Fire Android Development] DB126:
5.1.3 can (now) be directly rooted with Kingroot.
[Fire Android Development] DeLonge:
Thank you.. I'm succeeded root directly from 5.1.3
[Fire Android Development] likehelly:
the only possible way you could have done that, is if you had root access already.
[Fire Android Development] TechDad378:
Unable to deny or agree with your statement since having previous root was not documented.

At the same time that may give others an opportunity to root before updating then test after updating.

TD378
[Fire Android Development] kingrat:
I have version 5.1.1 upgraded from version 5.0.0 I have tried this several times and no luck.

I have tried Kingroot on the PC and on my Fire HD 10 and no luck - I have tried them several times and still no root.

I run option 1 to make sure I have the drivers working and I get this

[*] Press any key to check if your drivers are installed

[*] correctly.

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

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

[*] Is there a device listed under list of devices attached?

[*] IF no then reboot computer and run the driver install option

[*] again then recheck

[*] press any key to continue

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

List of devices attached

G000HH03xxxxxxxx device

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

[*] Once the screen is black and says fastboot in the corner

[*] press and key to continue the script.

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

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

[*] If you see a number with Fastboot after it your drivers are good

[*] IF no then open device manager and install fastboot drivers

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

G000HH03xxxxxxxx fastboot

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

[*] press any key to reboot device

[*] if your device doesnt reboot then close script and run the driver

[*] install option again to install fastboot drivers.

[*} Or hold POWER AND VOLUME DOWN UNTIL THE DEVICES REBOOTS

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

rebooting...

finished. total time: 0.016s

[*] RootJunky OUT

hit ENTER to return to start:

and it restarts

If I choose 6:

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

[*] Please select your Fire OS version to root. Then the script

[*] will walk you through the process to Root your Amazon Fire 5th gen

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

1 Root Fire OS 5.0.1 and below

2 Root Fire OS 5.1.1

3 Root Fire OS 5.1.2 or 5.3.1

Please make a selection then hit ENTER:

I select #2 and then it reboots into fastboot mode - IT DOES NOT SAY FASTBOOT IN THE CORNER

I hear my windows 10 make a few sounds - I see all black on the screen but I can see a little backlight on so I know that it is on and not turned off.

I get this message

...

FAILED (remote: unknown command)

finished. total time: 0.031s

and then it reboots

any ideas on what I need to do?
[Fire Android Development] platypoid:
Not sure if it is the same problem I had when I did mine - would always fail at the Fastboot stage. Somehow I finally figured out that HTC fastboot or drivers were interfering with it .Once I uninstalled the HTC stuff everything worked fine.

Good luck
[Fire Android Development] kingrat:
how can I tell if I have HTC drivers installed?
[Fire Android Development] platypoid:
You probably don't if you never owned an HTC phone - there was an app that you used to link up to the phone.

I think I had an HTC driver installation program that I uninstalled.

You could maybe do a search for fastboot in your files and make sure that you only have one on your computer - the one that you are trying to use for the Fire.
[Fire Android Development] kingrat:
UPDATE

I gave up on it on Friday and picked it back up on Saturday and I tried to run Kingroot again and on the first try it was rooted!! I didn't do anything else. After that I ran the program again and blocked OTA updates, google play, etc and no issues at all. I later installed Titanium backup and froze all the amazon apps since I dont want to use them or have them. It seems to run alot quicker now.
[Fire Android Development] DB126:
KingRoot utiIzes a cloud database to perform much of its magic. If servers are busy/down, networks are slow or you have a spotty connection KingRoot will fail without revealing the reason.
[Fire Android Development] ccMustard:
Want to root Amazon Fire HD series 5 running 5.1.2

Hi,

I want to root an Amazon Fire HD series 5 running 5.1.2. Apologies for being a bit late to this party :)

From what I have read in this thread...and there is a lot to read I have a few questions before I give it a go using RJ's supertool. Are there any obvious things I need to watch out for? Also....

Do I need to put the device into areoplane mode somehow to stop it trying to update itself automatically to 5.3.2.1 (when trying doing this process)?

If the root works is it still worth updating to the CyanogenMod now that project is dead? Which version works well with this device? Are there any other ROMS worth considering for this device?

Is there a way of recovering the device if the root fails or am I going to be left with a brick? Do I need to backup anything before I start?

Thanks very much for your help and advice.
[Fire Android Development] BeeWall:
This is not an HD device forum. For other ROMs look in the right forum (does HD series 5 mean the hd8? I don't know much about other fires.) These ROMs will not work.

To prevent an update, check the sdcard for a huge file with the .bin extension, and delete it. KingRoot needs wifi to root. However, you can turn wifi off after the first reboot. If it fails and you need to retry, turn it back on until reboot, and turn it off again.
[Fire Android Development] ccMustard:
Amazon Fire series 5 running 5.1.2

Thanks for your reply.

Apologies maybe it is not a HD series 5 just a series 5. It is running FireOS 5.1.2. I bought it new around Nov in 2015. It is there a way to confirm the device one has? It has 2 buttons (volume and power) and usb connection on the top.

I appreciate this thread is not about ROMS but it seemed a good place to ask the question.

There is so much information on this site that it is quite tricky and confusing for a noob like me to find the right area to look at and which bits are still relevant and up to date for the device you have (esp with a lot of the posts being quite old now).
[Fire Android Development] DB126:
Wrong forum; see response from [MENTION=7559542]PorygonZRocks[/MENTION]. Being 'late to the party' carries an advantage of having copious material from other contributors to assist with your journey. Lots of basic questions that have been answered dozens of times.
[Fire Android Development] BeeWall:
Go to settings>device options. What does it say under device model?
[Fire Android Development] DB126:
Also see this reference from forum index (post #2): https://xdaforums.com/kindle-fire/help/index-amazon-kindle-fire-t3205350
[Fire Android Development] ccMustard:
Thanks.

I am pretty convinced it is the 7inch series 5 (2015) version. I will check the device info when I get my hands on it again.

It is definitely running 5.1.2...which got it got updated to when I first turned it on a while back.

After reading even more posts....do I need to flash it to 5.1.2 as some of the posts seem to state that upgraded to 5.1.2 devices don't root very well if at all?

Also still a bit confused as when I should turn wifi on when trying to root the device (to avoid OTA)? Is it a case of leaving it off until Kingroot runs? and do I just leave wifi on until hopefully Kingroot completes successfully (even during reboots)? and can I access the OTA .bin file during this process to delete it via the PC? Can you do this before you start the root process using the RJ supertool?

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

Sorry forget to ask is it possible to stop the OTA service? or block the update server DNS names via your router?
[Fire Android Development] sd_shadow:
if it is a 7in, doesn't say HD on it and has a SD card slot

its a 5th gen Fire
[Fire Android Development] BeeWall:
Here's a thread about rooting without it updating: https://xdaforums.com/amazon-fire/help/dilemma-t3545062

Also, if you disable wifi after KingRoot reboots, it should still work, as it will already have downloaded the necessary files from the server.
[Fire Android Development] ccMustard:
Thanks for all the advice so far. Very useful and appreciated.

As suspected it is a fire(5th gen) serial G000........etc running fireos 5.1.2 (which it updated to when I first switched it on a while back). Do I need to roll it back to 5.1.2 as it auto updated?

Unfortunately I also seem to have registered the device to me...is this going to cause problems when trying to root or block updates?

Out of interest how can I connect the device to the PC just to have a poke around before trying to root it? I guess I have to install the drivers the Supertool uses at the start?

Also I assume once rooted I can then decide which ROM I would like to replace FireOS with? Probably Nexus or CyanogenMod. Is there a recommended one?

Thanks

---------- Post added at 11:52 AM ---------- Previous post was at 11:49 AM ----------

Sorry forget to as what happens when you select restore to factory defaults? Will it go back to the original FireOs the device came with or the current one?
[Fire Android Development] sd_shadow:
5.1.2 cannot be downgraded

root with super tool, or directly with KingRoot

factory reset only removes user data, resets default s
[Fire Android Development] thanhdat007:
Please help me!

I just downgraded my device exactly like the instructions in this video on YouTube: "Downgrade from 5.3.2 to 5.3.1.0 and Root Amazon Fire Tab 7" but it seems to be bricked or something... The device is now completely died. I have tried to charge it, hold power and volume button for more than 10 minutes but nothing happens.

I used FASTBOOT FILES WINDOWS to adb sideload the "update-kindle-global-37.5.5.2_user_552153420.bin" file. The process was successfully done without any errors. But after reboot the device, now, it is completely died!

Someone please help me!

Thank you.
[Fire Android Development] DB126:
Only FireOS 5.3.2.0 can be downgraded to 5.3.1.0. If the device was a recent purchase it likely had 5.3.2.1 (note last digit) which can not be downgraded.

A corrupt/damaged ROM file can result in a bricked device. Did you check the signature (MD5 hash) after downloading? A bad USB cable or connection can also introduce errors.

Contact Amazon for a courtesy exchange if still under warranty.
[Fire Android Development] pandimus:
Curious.. I rooted and locked otas on my fire when I got it.. put it away and forgot about it.. I'm not sure what version firmware it has and when I go to system updates it say the requested action is not permitted. Check parental controls settings and retry. I suspect this is somehow the OTA lock. I did check parental controls and can't seem to figure out how to unlock, although not sure if I want to. I just want to check firmware so that I can see if I can put TWRP and another firmware on.. any ideas?
[Fire Android Development] BeeWall:
If you can root, you can use FlashFire to flash without TWRP.

To check version: https://xdaforums.com/amazon-fire/development/identify-bootloader-version-t3424634

Yes, it's the OTA block. Since the app is disabled, it won't work.
[Fire Android Development] cwhiatt:
This kindle fire 7" 5th generation was purchased around Christmas and was promptly downgraded to 5.1.2. Following that it was effectively rooted and running fine.

I went to flash CM12 on it using flash fire and it must not have completed effectively because now the device is only booting to the orange fire screen.

The CM12 zip is on the kindle itself. The device is not showing up via adb devices or in device manager but it is recognized as a fastboot device. I do have an actual fastboot cable.

I've tried a number of fastboot commands (trying to flash the 5.1.2 bin file, trying to flash TWRP image, trying to run update command on the CM zip).

I should mention as well that when trying to flash the kindle reads "flashing not allowed" which strikes me as completely odd because I know that this thing was unlocked in Dev Options before things went off the rails.

I'm at a total loss here.
[Fire Android Development] sd_shadow:
there is no unlockeing the 5th Gen

if install failed you need to reinstall stock firmware via stock recovery

Unbrick 7in Fire 2015 5th Gen with ADB Sideload
[Fire Android Development] cwhiatt:
The problem I'm having at present is that the device is not recognizing as an adb device. It will however recognize as a fastboot device.

Does that allude to a problem with the driver install? Honestly I've done so half a dozen roots of various devices etc. and have gone in and out of adb just as many times that I'm hard pressed to think these drivers are not updated.
[Fire Android Development] sd_shadow:
fastboot mode only work if firmware was 5.0.X

any thing higher fastboot is non functional
[Fire Android Development] cwhiatt:
When you say "non functional" would that be non functional to such an extent that it would not list the device?

I'm looking at my external hard drive and I've got the "fire OS 5.1.2 update bin file" which has a date modified of 12/24/2016 so I'm quite certain that I used the supertool method to download it to 5.1.2 before proceeding with rooting. I can't recall the firmware version it was packaged with.

Presumably I am going to have to first get it recognized as an adb device before I can do anything but assuming I can get that resolved I'm not sure which firmware version I should attempt to sideload.

I'm inclined to go with the 5.1.2 that I did back in January. What do you think?