yashsingh1/xdaforums huggingface dataset:
[Fire General] Mr McBoatface:
Waiting on delivery of another tablet bought on ebay, it wouldn't register to amazon so got it cheap :) Judging by the picture on ebay I thinks its got OS 5.3.2.1 on it . So looks like I'll be joining the 5.3.2.1 root hunt soon enough :)

Just to pass on my observations of rooting several tablets with Fire OS 5.3.1.0 either I own or have set up for family. It was very difficult to get a defined process in place, however in my observations the following helped

(1) A factory reset.

(2) I placed the unzipped files from the zip attachment in the fire tablets internal storage.

(3) No apps downloaded or installed

(4) No SD Card

(5) After kingroot installed from supertools script and the "press any key to remove kingroot and install supersu once kingroot has working root access" appeared I removed the USB cable from the table. I only re-attached it once it rooted.

The files in the attachment where left behind after a very quick (almost instant ) successful root on 5.3.1.0, I've no idea why it rooted so quick and what the files contain. Rooted with kingroot 4.92 (MD5 # 728a132043eb49083bcdc7706841ecaf) in supertools

By following the above the tablets "usually" rooted fairly quickly and "usually" with first or second run. However some did need a second factory rest after repeat fails, then they rooted perfect !! I know 5.3.2.1 is a different beast but hopefully it helps.

The above didn't help with me rooting 5.1.4 earlier this week, a different kingroot version was needed in that case.
[Fire General] Mr McBoatface:
No root yet but..... just a little update/note. If for what ever reason you decide to do an adb recovery on 5.3.2.1 and accidentally load the earlier OS 5.3.2 and realise your error after the adb recovery completes but before you hit the reboot button you can still recover the tablet :)

(1)Do not reboot

(2)Wipe cache

(3)Wipe data

(4)ADB sideload correct OS file :)

(5)When ADB recovery completes, Repeat above 2 more time

(6)Select Power Down instead of reboot (say a prayer)

(7)Start up Kindle

And no you can't follow the above process to attempt go from 5.3.2.1 to 5.1.x then back up to 5.3.1. :silly:It will brick the tablet:p . The anti rollback system seems to detect the last fully booted OS rather than the last installed.

I don't mind the brick, some spare motherboards arrived today from the US along with the tablet I ordered. The spare mothered had either 5.0.1 or 5.1.1 on them .... happy days :)

Replacing the motherboard is very easy.
[Fire General] TechDad378:
Update...

Gplay works no issues. Still no root. Got to the point where kingroot would not reboot during process and stop around 75% then say "please wait for the update patiently".

I am starting to believe KingRoot finds a vulnerability within an app then applies root. Question is what app?

Side note: Anyone attempt the "moo" vulnerability found in many devices laat year? (maybe saying exp name wrong).

TD378
[Fire General] BeeWall:
Dirty cow? I tested it with Drammer, doesn't work. No bits flipped.
[Fire General] freaky2xd:
I am sooo depressed :(

I bricked my last Fire Tablet, sent it back and said I "only resetted it" which was true but I resetted the firmware and didnt use the stupid resetting options in the settings apk ^^

today I got my free replacement and what did they do?!?! they have already updated it to 5.3.2.0 :/ :/ ./

AND I HOPED THAT THEY WOULD LEAVE THE GOOD OLD 5.2.0 ^^
[Fire General] TechDad378:
Yes that's the name. This has become an interesting challenge. I honestly am unclear what caused success originally. I tried so many uncommon ways with first success yet didn't keep track of process expecting it can be easily duplicated.

Have a few more ideas to try which will lead to success or a poorly working mirror, aka brick.

Will keep you updated.

TD378
[Fire General] Mr McBoatface:
Does it have fire OS 5.3.2 or OS 5.3.2.1 . Bit of a different between both, 5.3.2 can be downgraded to 5.3.1 and rooted ... OS 5.3.2.1 you're stuck with for the moment
[Fire General] freaky2xd:
actually it is 5.3.1.0
[Fire General] Mr McBoatface:
Don't connect it to the internet !!! Factory reset and the use the root procedure from the most recent supertool. Don't connect to Internet until after kingroot is installed, disconnect it after kingroot roots the tablet. Once rooted and supersu is installed disabled ota using supertool. See my brief outline and experiences on rooting 5.3.1 at the top of page
[Fire General] physicistman:
Same with me. I've tried at least 10 different versions from the Kingroot XDA thread with many different device admin and accessibility settings and numerous purify versions along with the play store and services and the Windows app. I have noticed, using the app on numerous devices, that when Kingroot reboots for the first time if it boots to Kingroot directly with nothing that blocks it in this case the lock screen, then success is more likely. I was only able to get this result once on 5.3.2.1 I am not sure what I did this one time or whether it was a complete fluke, I guess it doesn't really matter, because it still failed. I have also tried many other root apps such as Framaroot Kingoroot and so many others I cannot remember them all. I have searched through many of the system apps looking for any weaknesses without luck although I did find that apps with the diagnostic manifest have system access. Not entirely sure how this could be used to achieve root, as I have limited experience with finding root exploits, but seemed like it was a good start.
[Fire General] jextrevor:
Where can you find these motherboards, and could you make a guide on how to replace them?
[Fire General] Mr McBoatface:
Bought them on ebay, sold as faulty cause the wouldn't register with amazon. The listing was a year old so figured they would have a early rootable OS on them. Seller sold out now

As for a guide plenty of video and guides existing . This is a good one https://www.ifixit.com/Teardown/Amazon+Fire+5th+Generation+Teardown/54868
[Fire General] TechDad378:
Update...

Officially bricked device last night. Will try to unbrick until able to get another one.

Once another tablet is purchased, will continue trying to root.

Always remember to keep an open-mind to open source.

TD378
[Fire General] jextrevor:
My condolences.
[Fire General] BeeWall:
That sucks. If you flashed an older OS, probably bricked a while. But good luck, just in case!
[Fire General] fmc000:
FWIW, on apkmirror there's a new KingRoot release, 5.0.3 . Maybe it's worth trying...
[Fire General] DB126:
To my knowledge all KingRoot 'builds' leverage the same cloud database to identify potential vunerabalities and associated exploits, although the local component may sequence activities a little differently. Success/failure with one build vs another appears more of a serendipitous event than anything to do with the build itself. Later builds (especially the v5.x series) do burdon the device with additional crud and complicate the transition to SuperSU which is a prerequisite to using FlashFire. Choose wisely.
[Fire General] TechDad378:
Yea, attempted to flash 5.3.1 for fun. Everything said complete transfer via adb but the power button said otherwise.

The device is recognized for an instant but not long enough before reboot. It makes a sound connecting to pc but then reboots. Tried stopping the boot process via script but no success.

What's rooting without bricking a device or two!

TD378
[Fire General] nsf5555:
Just wanted to report KingRoot 5.0.4 doesn't work. It was just released.
[Fire General] TechDad378:
This may be of interest...

Using a different version of Kingroot on another device with a locked bootloader, root is now achieved around 80% of the time. Originally root was achieved once on the device. Root is lost during reboot but this adds to an idea.

The believe of KingRoot version playing a role in rooting is very plausible. On the current device most versions of KingRoot do not work. Yet some versions work almost every time.

Once a method is achieved it can be applied to any device the only change should be the KingRoot version.

At this time its just an idea which will be applied on A.Fire 5th gen once successful on current device.

TD378
[Fire General] BeeWall:
What version?
[Fire General] TechDad378:
The most success was with v5.0.0_C161_B367. The newer versions did not root at all.

Keep in mind the other device and the Afire only have the locked bootloader in common. Yet it's worth a shot.

TD378
[Fire General] BeeWall:
The main problem with rooting is that KingRoot only sees the Android version, so even I it can root 5.3.2.1, as you saw, it is still using older methods, as it thinks that for example 5.3.2.1 I'd the exact same OS as any other fire os 5, even for example 5.0.0. So it keeps trying those methods, so whatever method worked for you when this thread was started is being ignored. Do you know if KingRoot stores last method in /data? If so, whenever we manage to root again, we could just adb backup and restore to get it to use the right method.
[Fire General] TechDad378:
Will need to look into if "last method" is stored and let you know.

Never been a big fan of these onestop root shops.
[Fire General] Mr McBoatface:
Just incase any wants to try it and report back there is a new kingroot February 2017 build available on the xda thread here https://xdaforums.com/devdb/project/?id=9793#downloads.
[Fire General] Duke91:
No success using version 5.0.4
[Fire General] Lobo Richardson:
Bricked mine too. :( any way to unbrick it???
[Fire General] BeeWall:
None that has been discovered. Downgrading is a permanent brick, as far as we know.
[Fire General] DB126:
FYI - Amazon will typically offer a no-questions-asked courtesy exchange for non-operational devices during the warranty period.
[Fire General] Fred Simm:
Well, I think that we all learned a great lesson. Completely document our experiments when we achieve the impossible. Then we will know what method worked.
[Fire General] BeeWall:
Documentation is important, but TBH, I doubt it would have helped in this case. We unfortunately can't force KingRoot to use specific methods, and no amount of documentation would change that. And as I don't think KingRoot stores the method after success/fail, we wouldn't be able to figure that out either.
[Fire General] TechDad378:
Generally when documenting the process, its done by keeping rough notes on what was done and not done. This tends to lead an individual in the right direction once the task is accomplished and needs to be repeated.

The idea of "one stop root shops" make the task of documentation seem irrelevant since the "OSRS" does all the work.

All Android devices seem to have something extremely similar which allows the "OSRS" to work. In theory when a device similar to "AFire" breaks the mold of similarity we most look towards other devices for answers.

The locked bootloader seems to be our problem. Other devices have been unlocked via a server command. Other devices seem to have certain features disabled upon restart. Whether those features are disabled hardware keys, disabled cache partition, etc., tends to prevent root.

The question becomes, Amazon Fire tablets are not going away but will our attempts continue?

TD378
[Fire General] Ayden7777:
The Shore:

Can you please make a video of exactly what you did to root this current version and attach it on a reply please? (Using firmware 5.3.2.1)
[Fire General] DB126:
At present 5.3.2.1 can not be rooted.
[Fire General] Ayden7777:
Oh I am so sorry, I must've gone thrown off by this message:

"A contributor is reporting success rooting 5.3.2.1 with Kingroot. No immediate confirmation...simply reposting for visability and comment. Report your results here for community benefit."

I am pretty new to fire hacking

and ya, I have noticed the device rebooting at 17% and always failing at 70% everytime< % :crying::crying:

---------- Post added at 01:39 AM ---------- Previous post was at 01:34 AM ----------

I have also noticed that someone said that not registering with Amazon helps, but I wonder if force stopping amazon applications would help...:rolleyes:
[Fire General] DB126:
Unfortunately, attempts to reproduce on 5.3.2.1 proved unsuccessful. The other tactics that you mentioned are not effective on 5.3.2.1.
[Fire General] Ayden7777:
Thanks for the information, getting a new Android tablet unless able to get a root on amazon's 5th gen. I didn't get a chance to any hacking because I soon as I got my fire, it was shipped in with firmware 5.3.2 but automatically updated after a single reboot

>:(
[Fire General] BeeWall:
Someone did manage to root. However, they have since not been able to reproduce what happened, and bricked their tablet. It has been unable to be reproduced by anybody else either. I'm of the opinion that it was actually 5.3.2, since he managed to downgrade, but maybe he was just lucky.
[Fire General] crazyates:
Kingroot 5.0.5 just came out. After several attempts, it does not appear to be working.

Still no root. :(
[Fire General] der-mali:
Can confirm this experience with KingRoot 5.0.5 and 5.3.2.1:

Reboot at 16%, proceeding to 67%, then tells that root is not possible.

There are currently only 21 user requests to KingRoot to add this device.

BTW: Fire is recognized by KingRoot as 5.1.1, not as 5.3.2.1 ...
[Fire General] crazyates:
That's because FireOS is a modified version of Android 5.1.1. FireOS version numbers and Android version numbers don't necessarily line up.
[Fire General] ctodd111:
This has been my experience also. I have trying to root with 5.05 frequently over the past two days - sometimes for hours at a time. Is trying to root over and over again useful or a waste of time? If I can't root this thing I am going to sell it on eBay. Thanks.
[Fire General] Mr McBoatface:
Root may happen any time or may not. Fire OS 5.3.1 was rooted before the previous release Fire OS 5.14 and Fire OS 5.13.

The next fire OS to be released which could happen at any time may have a vulnerability in it that can be exploited for root that's not there in the present OS.

Unfortunately it's a waiting game
[Fire General] ctodd111:
I guess what I really want to know is - does running the Kingroot program over and over help the process of finding the exploit?
[Fire General] Mr McBoatface:
As far as i know the developers of kingroot work on root procedures for the device's with most requests, so the more requests they receive and info they gather the more likely root will come.

Is it worth running it over and over again for hours ? In my opinion it's not, maybe run once or twice a night to see if a new cloud procedure has been added.

It's worth clearing the apps cache and data before you do so.
[Fire General] crazyates:
Short answer: No.

Long answer: It depends. Sometimes it does take a few attempts to root a device, but only if there is a known exploit for that device. Since 5.3.2.1 doesn't have any exploits (that I'm aware of), retrying over and over isn't going to get you anywhere.
[Fire General] ctodd111:
Prior to today, my fire 7 running 5.3.2.1 would reboot around 16-17% every time and then fail at around 67-69%. Today it is regularly getting to 25-26% before rebooting but it is still failing at 67-69%. Does it mean anything in terms of progress toward root that it is getting farther in the process before the reboot? Just curious.
[Fire General] Mr McBoatface:
It might mean a different root strategy is being used.... Or could be it's using a different cloud server and takes longer to connect. Doesn't mean it's any closer to root.
[Fire General] iSonik:
Ya. No chance rooting atm. But if you order a replacement you will get an older Version
[Fire General] BeeWall:
Not always. Sometimes it's older, sometimes not. 5.3.2.1 has been out a while now. You shouldn't get a new one unless you bricked the old. In my opinion, anyway. Quite a bit can be done without root.
[Fire General] iSonik:
True. But many people from middle europe claimed it worked aswelll. Btw i replaced mine because the Touchscreen was seperating itself from the LCD :s But i used that, and now i have Fire nexus Rom :d
[Fire General] BeeWall:
My thought was that if it didn't work, and there was no warranty problem, and you later brick it and need an exchange, they may think you are abusing the privelige. At least, if j was Amazon, I would probably suspect that. Though then again, if I was Amazon, I would unlock the bootloader ?
[Fire General] Ayden7777:
Lol
[Fire General] ctodd111:
Fire OS 5.3.3.0 update just happened on my Fire 7 tablet.
[Fire General] DB126:
Could be 'good news' as 5.3.2.1 has proven resistant to the current suite of rooting tools. Only time will tell.

No word (yet) on what new features/functionality/goodness, if any, may be baked into the latest build.
[Fire General] Mr McBoatface:
If you're going to try to root 5.3.3.0 I'd suggest you do a factory reset and don't register your amazon account when it restarts

Not showing on amazon's software download yet.
[Fire General] Conan1201:
Hi everyone. Just wanted to say I really appreciate all the hard work and time people have put into this.

I'm new to rooting androids and enjoying reading everyone's posts on the progress. If 5.3.3 is rootable hopefully we'll all be enjoying a rooted fire tab soon
[Fire General] ctodd111:
I did as suggested and tried a few times, without success. Will keep trying periodically.
[Fire General] crazyates:
My Fire running 5.3.2.1 doesn't even see the update. Hopefully within a day or two I can get it to take.

When that happens, I will try as well, but I'm not very hopeful. I doubt they would patch a bunch of vulnerabilities in 5.3.2.1, and then revert those security changes in 5.3.3.0. Just a thought tho, as you never know.
[Fire General] Mr McBoatface:
I imagine they'll roll out the updates in phases across the globe. Depending on where you are you may get the update early or not.

Regarding chances to root, 5.3.1.0 was rooted when it predecessor's where not so anything is possible. As far as we know amazon could be rolling out an update with a vulnerability that's been found on other devices more popular than the fire tablet which the folks at kingroot are working hard on.

My personal opinion is that we (the fire tablet user) benefit from vulnerability found on much more popular devices that happen to be in the Fire OS of the time.
[Fire General] ctodd111:
Is it a little strange that one of my fire tablets updated to 5.3.3.0 but not the other? Just after the first one updated, I checked the other to see if it had, but it hadn't. There was an indication that an update was ready to install, and it would do so when the tablet was not being used, but it never did. When I checked on it later, it hadn't updated and no updates were available. I can't imagine why the update disappeared.
[Fire General] crazyates:
I have one tablet on 5.3.2.1, and it hasn't seen any update. I've tried manually checking, factory resetting and checking, looking on their website, and everything else under the sun. I can't find any reference to a 5.3.3.0 update.
[Fire General] DB126:
Please see previous post by [MENTION=7968177]Mr McBoatface[/MENTION]. Perfectly reasonable explanation that is common practice across numerous devices and services. Early rollouts are often heavily throttled in case there are previously undetected issues.
[Fire General] Jake1702_:
*Crosses fingers an exploit is found in 5.3.3.0*

I haven't got it yet though, and I might actually be worried in case miraculously right after it updates a way to root is found for 5.3.2.1. Would be just my luck, and I'll be back right where I started. If it takes a while to come out, does anyone have the direct link so I can do it manually? (Yes I'm a pretty impatient person.)
[Fire General] DB126:
https://www.amazon.com/gp/help/customer/display.html?nodeId=201830180
[Fire General] Jake1702_:
That's still at 5.3.2.1? Weird...
[Fire General] Mr McBoatface:
When the role out is completed or when amazon are happy it's stable that is where you will find it. It's possible it may not appear there for some time.
[Fire General] Jake1702_:
So it's possible they may remove the only chance to root. Ugh.
[Fire General] Ayden7777:
Yes. Mine says there is 1 sys component and 1 component. When i click "update" nothing happens. What's up Amazon?!

Edit so it is 3 am and when I click check for update i get nothing
[Fire General] DB126:
Scroll back and review several explainations from experienced members. New versions are typically rolled out slowly at first until stability is assured in the wild. You'll get when Amazon decides it's ready.
[Fire General] Mr McBoatface:
System component updates are not the same as OS updates. From a fresh 5.3.2.1 there are 15 system component updates available. These are the amazon system apps updates for amazon photos, video etc.

They will install in the background if left alone when the tablet is idle.

Easy enough to confuse with a OS update but not the same.
[Fire General] jextrevor:
Can anyone else confirm this? I haven't seen a new update mentioned anywhere else.
[Fire General] ctodd111:
I took a picture.

https://goo.gl/bFQ5o5

Only one of my devices updated. Two others did not and they do not see the update, either.
[Fire General] jextrevor:
Thanks for the photo confirmation. That's odd that one device saw the update but the others didn't. I'm hopeful that 5.3.3.0 has some sort of exploit.
[Fire General] ctodd111:
Absolutely - fingers crossed! I've been trying to root since the update, but no luck, yet.
[Fire General] DB126:
Not odd at all; a small batch of serial numbers was likely targeted for early rollout. There may be several more 'waves' before the flood gates open.
[Fire General] Jake1702_:
I sure hope mine is in that. Then again what good would it do?
[Fire General] steve8x8:
I'm puzzled (although not affected): what would happen (to owners of such tablets) if the fw is bad?

Since there'd be no roll-back, would Amazon offer a replacement?
[Fire General] BeeWall:
I think they probably do testing before releasing to anybody. The limited rollout is probably a last check, but probably won't go bad.
[Fire General] DB126:
My observation (across multiple device types) is Amazon offers generous coverage during the warranty period, approving exchanges for just about any reason short of abuse. Things get much tougher outside of warranty, even if the problem was the result of an OTA gone bad. Reported exchanges or other prorated compensation are few and far between once the warranty expires. Was especially tough with HDX tablets and early Fire phones which carried substantial sticker prices.
[Fire General] Oco:
This is just to resume my unsuccesfull experience rooting a 5.3.2.1 Fire 7 with all suggestions in this and related threads:

1. Reset Fire, skip wifi/setup, enable developer mode and ADB/USD debug

2. Install Supertool on PC, connect Fire to USB checking using always use USB debug, install ADB+fastboot drivers

3. Supertool root (install kingroot 4.9.2), enable wifi, supertool Gplay (reboot, set an account), install kingroot purify through Gplay

4. Allow access to kingroot & purify from accesibility/service

5. Try 1, 2, 3, 4 Kingroot, it autoreboots Fire on 17-20%, then failed around 70%. Request research, Retry. Several versions as suggested. Nothing
[Fire General] DB126:
As expected - FireOS 5.3.2.1 can not be rooted at present (more accurately, there are no repeatable reports of securing root on 5.3.2.1 to date).
[Fire General] the_mook:
i did manage this first time out of the box with a 5.3.2.1 fire 7 using kingroot android apk downloaded from their website (this saturday) like others I cannot repeat this. I started out with supertool but then dowloaded kingroot, can't remember exact steps unfortunately and can't repeat it. (I hadn't read this thread, and din't know much about 5.2.3.1) I factory reset as I wanted to run through it again as I had installed purify etc.