Database Users

[Q] Is the Kindle Fire still "hackable"?

Hi!
I have read a few posts about the Kindle fire now being locked from rooting(if I have understood them correctly).
As I have an unopened device at home that I'm givning myself for christmas I have a few questions.
1. Is there an update that makes my untouched Kindle Fire un-rootable?
2. Will this update install automatically when connected to Wi-Fi?
3. Is it the bootloader that is locked or will it be rootable/able to install other ROM's in the future?
Would very much appreciate if someone took some time and answered these questions. I would also appreciate if someone could make some kind of summary. Read a lot on the forum but i am still a bit confused about the current status.
/Masssy
Edit: Read on some more about it and I believe that is is thr 6.2.1 update that screws things up.
Does that make me able to not enable Wi-Fi and then flash CM7 before even using WiFi on the device? That should make it fully hackable with ICS etc in the future, right?

Masssy said:
Hi!
I have read a few posts about the Kindle fire now being locked from rooting(if I have understood them correctly).
As I have an unopened device at home that I'm givning myself for christmas I have a few questions.
1. Is there an update that makes my untouched Kindle Fire un-rootable?
2. Will this update install automatically when connected to Wi-Fi?
3. Is it the bootloader that is locked or will it be rootable/able to install other ROM's in the future?
Would very much appreciate if someone took some time and answered these questions. I would also appreciate if someone could make some kind of summary. Read a lot on the forum but i am still a bit confused about the current status.
/Masssy
Click to expand...
Click to collapse
If it was me i would root it and install titanium using ADB before i connect it to wifi then freeze or uninstall the otasilentinstall app.
---------- Post added at 09:14 AM ---------- Previous post was at 09:09 AM ----------
you could rename or move the OTA certs, and change the hosts file as well if your paranoid about it.
apparantly they are pushing the update even if the device isnt registered with amazon.
Check this thread

6.2.1 breaks root and prevents the only method anybody has used so far. Another method will most likely surface. That said, there is a pre-rooted 6.2.1 ROM, the Fire semi supports android market in Silk in the latest update, and installing CM7 totally gets rid of any Amazon stuff.
You’re best bet is to disable wifi or block the amazon server in your host file.

Winglerw28 said:
6.2.1 breaks root and prevents the only method anybody has used so far. Another method will most likely surface. That said, there is a pre-rooted 6.2.1 ROM, the Fire semi supports android market in Silk in the latest update, and installing CM7 totally gets rid of any Amazon stuff.
You’re best bet is to disable wifi or block the amazon server in your host file.
Click to expand...
Click to collapse
I'm going to open it up when I am away for christmas. Although, I have no use for starting to use WiFi on it that day.
Just keeping WiFi off and then root+CM7 directly when I'm home should be smartest, right?
Edit: I'm not after the Amazon crap anyway since I'm from Sweden.

Been gone for a few weeks..

Playin w/ roms on my new Rezound... Anyways I noticed the wife's KF got updated to 6.2.2 and FFF/twrp got axed.. Came back lookin for an updated way to get it back quickly. From my last 30 mins or so of reading it would seem the KFU and burritoroot are like fragmented now or something. I tried KFU for twrp and it failed- then I saw there was a burritoroot v3 but it doesn't install a recovery. Just wondering if there's any automated way to get it all done again or if I'm gonna have to keep searchin for links to recoveries etc. If so, no biggie- but if there's an easy way to get twrp back obviously I'll go that route. If there's a thread on it- I must just be missing it- granted I've had a few tonight.

I rooted my 6.2.2 kindle with burritoroot3 and then used KFU to flash TWRP recovery. Make sure you have the updated run.bat found in the KFU thread before trying to flash TWRP

Yep- I found the post from stevenmirabito seconds after posting this damn thread and I've already got twrp back on.. Sorry for the wasted thread.. Still kinda wondering why BR3 hasn't been worked into a new version of KFU but I'm sure if I was really interested enough there's prob some threads on that too- hopefully no drama. Anyways- thanks BluesHawk for responding to my question.
One more thing- I'm assuming it's ok to remove the old burritoroot? Got two icons now

Once you got the burritoroot you may as well uninstall unless your sentimental :_
done and done!

Well- I didn't do perm root- so that I could keep the streaming vid working. I fig'd I'd keep it around though for temp root/unroot

Hag77 said:
Well- I didn't do perm root- so that I could keep the streaming vid working. I fig'd I'd keep it around though for temp root/unroot
Click to expand...
Click to collapse
Unnecessary... Just perm root it and be done with it.
Use OTA Rootkeeper and you will be able to view your Amazon Videos.

Oh ok cool- like I said I've been gone for a while.. Pretty sure last time I was active on these forums OTA RK was a no go for prime video.

It has been the only method that I've ever seen.
o Using OTA rootkeeper use Unroot
o Go to settings -> Applications
o find Amazon Video and force close it
Now run Amazon Video again and it will work. You can even go back and root using OTR Rootkeeper and it will still work until your reboot your device.
This works on the Stock roms... CM7 and ICS doesn't

Cool thx for the info.. Last time (6.2.1) I did perm root, installed market and other apps, FFF&twrp, then unrooted (had to manual delete su files on the device)- so OTA-RK sounds easier. Unfortunately, this is my wife's fire- so I don't get to have that much fun with it. She's way into the amazon ecosystem and likes the stock rom.. So unless ICS final just kicks complete ass- I'll prob have to buy my own to play w/ those roms.. Not even sure why I ended up putting twrp back on it really- I just can't help myself!

krelvinaz said:
It has been the only method that I've ever seen.
o Using OTA rootkeeper use Unroot
o Go to settings -> Applications
o find Amazon Video and force close it
Now run Amazon Video again and it will work. You can even go back and root using OTR Rootkeeper and it will still work until your reboot your device.
This works on the Stock roms... CM7 and ICS doesn't
Click to expand...
Click to collapse
If on CM7, you can leave rooted, use the browser to view Amazon video if you set the user agent to Linux desktop, and that works.

Rooting while keeping OTA updates

I'm intrigued in rooting my Nexus 7, but I also love google's stock android, no extra bloatware and apps makes me a happy camper, and thats why I waited for a Nexus tablet in the first place. Here's my question:
Is it possible to root the Nexus 7, get superuser permissions, change DPI settings, etc.... while retaining stock android (no flashing or different roms) so that whenever an OTA gets released, the device still lets you install the updated without giving any problems?

jakeellis01 said:
I'm intrigued in rooting my Nexus 7, but I also love google's stock android, no extra bloatware and apps makes me a happy camper, and thats why I waited for a Nexus tablet in the first place. Here's my question:
Is it possible to root the Nexus 7, get superuser permissions, change DPI settings, etc.... while retaining stock android (no flashing or different roms) so that whenever an OTA gets released, the device still lets you install the updated without giving any problems?
Click to expand...
Click to collapse
Yeah, you can root and get su permissions without changing stock. You need to use this to get OTA and still keep root: https://play.google.com/store/apps/details?id=org.projectvoodoo.otarootkeeper&hl=en
I'm not sure if the DPI would revert back to the original settings when updated, but it's something to try.
Also, if you remove any of the apk's under the system folders, you will not be able to update. The update checks to see if they are all there before it starts installing.

great..... do you think the device would still be rooted after an official OTA?

Don't see why not. You would need to run OTA root keeper again, to re enable root. If you read the description in play, it tells you that it temporarily disables root so that it hides it from the OTA update

Anyone actually try this yet? I had OTA Rootkeeper on my razr and it didn't work sometimes.

Dawg5 said:
Anyone actually try this yet? I had OTA Rootkeeper on my razr and it didn't work sometimes.
Click to expand...
Click to collapse
I haven't tried it yet. I let mine update before I rooted it.
Have head mixed reports on here, most say it works and some say it doesn't. You just have to take the chance.
If it does not save, its very easy to root again using a toolkit so it's not a big problem......

FireOS 4.5.5.2 is out; breaks root; how to block OTA updates

As of this posting two contributors running FireOS 4.5.5.1 reported being upgraded to 4.5.5.2 which breaks root and various side-loaded apps including Google Play Store. It is not known if 4.5.5.2 can be rooted and/or Safestrap v4 compatibility. Those running rooted FireOS v4 should block OTA updates to protect from unsolicited Amazon distributions.
How to disable OTA updates (source):
- Get a file explorer which has root access (I used ES File Explorer because it was already in the Amazon App Store but every other file explorer should work too)
- Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk
- Just rename DeviceSoftwareOTA.apk to whatever you like (Important: After renaming the file mustn't end with .apk)
- Profit! You can now access the internet freely without the fear of evil amazon updates
Edit: OTA updates on FireOS v4.x can also be blocked using the technique described in this post.

Davey126 said:
As of this posting two contributors running FireOS 4.5.5.1 reported being upgraded to 4.5.5.2 which breaks root and various side-loaded apps including Google Play Store. It is not known if 4.5.5.2 can be rooted and/or Safestrap v4 compatibility. Those running rooted FireOS v4 should block OTA updates to protect from unsolicited Amazon distributions.
How to disable OTA updates (source):
- Get a file explorer which has root access (I used ES File Explorer because it was already in the Amazon App Store but every other file explorer should work too)
- Browse to /system/priv-app/ and search for DeviceSoftwareOTA.apk
- Just rename DeviceSoftwareOTA.apk to whatever you like (Important: After renaming the file mustn't end with .apk)
- Profit! You can now access the internet freely without the fear of evil amazon updates
Click to expand...
Click to collapse
Which Users? and which apps? Just Google Apps? or are there many that some of us might be using atm ?

DBCAB said:
Which Users? and which apps? Just Google Apps? or are there many that some of us might be using atm ?
Click to expand...
Click to collapse
Ref: http://forum.xda-developers.com/kin...oot-how-to-install-google-play-store-t3339865
Relax - just block OTA updates and put yourself in the driver's seat. Then you get to decide if/when to upgrade, not Amazon.

Davey126 said:
Ref: http://forum.xda-developers.com/kin...oot-how-to-install-google-play-store-t3339865
Relax - just block OTA updates and put yourself in the driver's seat. Then you get to decide if/when to upgrade, not Amazon.
Click to expand...
Click to collapse
Yes I know how to block ota and all but was wondering if the update even exists and what it does , my mother has a stock kindle never rooted etc and hasn't received anything yet, cant find any info on it but ty for reply , and yeah i like being able to control my device , we all should be able to anyway without modifications, we paid for the device should be able do whatever we want.

I am from germany and got the update last tuesday

Kingroot not work on 4.5.5.2
Hi all,
I am new on the forum and very unlucky!
Yesterday my Kindle Fire HDX 8.9" 3rd gen was upgraded to 4.5.5.2 and I decided to try another way to enjoy my Kindle.
I red this forum and decided to install the Nexus ROM.
First pass was to root the device with Kingroot but it doesn't work (ended with error "ROOT FAILED - no strategy now")
So I think that the new version of firmware 4.5.5.2 CAN'T be rooted directly with Kingroot 4.9.6.
Bye
Davey126 said:
As of this posting two contributors running FireOS 4.5.5.1 reported being upgraded to 4.5.5.2 which breaks root and various side-loaded apps including Google Play Store. It is not known if 4.5.5.2 can be rooted and/or Safestrap v4 compatibility. Those running rooted FireOS v4 should block OTA updates to protect from unsolicited Amazon distributions.
Click to expand...
Click to collapse

Tried and retired kingroot 8x. Did not work. What are some other things I can try?

AzizA MeelaS said:
Tried and retired kingroot 8x. Did not work. What are some other things I can try?
Click to expand...
Click to collapse
4.5.5.2 is not rootable at present. Keep trying Kingroot from time to time.

Too late to block OTA! My Kindle Fire 7 HDX 3rd gen updated automatically to 4.5.5.2 and Google Service stops working and could not open Google Play Store, keeps crashing it. Could not login Google account, can't see Google Photos.
Kingroot 4.9.6 failed to root.
Hope can be fixed soon.

mxnerd said:
Too late to block OTA! My Kindle Fire 7 HDX 3rd gen updated automatically to 4.5.5.2 and Google Service stops working and could not open Google Play Store, keeps crashing it. Could not login Google account, can't see Google Photos.
Kingroot 4.9.6 failed to root.
Hope can be fixed soon.
Click to expand...
Click to collapse
At present the only solution is a risky downgrade to 3.2.8 followed by a controlled upgrade to 4.5.5.1. Instructions must be carefully followed to avoid bricking; all personal apps/data will be lost. Consider waiting for a root exploit which could happen tomorrow or never.

Any updates to root 4.5.5.2?

aaronkatrini said:
Any updates to root 4.5.5.2?
Click to expand...
Click to collapse
Best option is to try Kingroot from time to time. The community will only know if someone reports success.

is this bad
I rooted on 4.5.5.1, blocked updates then turned system off. I turned it on in the morning to find it has reset itself. I looked for the update file in /system/priv-app, but it wasn't there. Is this bad?

Android Rom Guy said:
I rooted on 4.5.5.1, blocked updates then turned system off. I turned it on in the morning to find it has reset itself. I looked for the update file in /system/priv-app, but it wasn't there. Is this bad?
Click to expand...
Click to collapse
Obvious questions:
- what version of FireOS does it show now?
- still rooted?

i accidentally update to 4.5.5.2 too from a rooted 4.5.5.1
i'am so frustrate right now as there is no way to root this damn 4.5.5.2 version

n.fajira said:
i accidentally update to 4.5.5.2 too from a rooted 4.5.5.1
i'am so frustrate right now as there is no way to root this damn 4.5.5.2 version
Click to expand...
Click to collapse
You can rollback to 3.2.8 and then upgrade back to 4.5.5.1, root and block OTA updates to prevent recurrence. Also possible to unlock the boot loader which opens the door to all custom roms for this device. Note 3.2.8 rollback carries a risk (permanent brick) if not executed properly. A summary of the procedure can be found here. Make sure you fully understand before attempting. Guessing 50% of those who start end up bricking their device by simply not following instructions.

Davey126 said:
You can rollback to 3.2.8 and then upgrade back to 4.5.5.1, root and block OTA updates to prevent recurrence. Also possible to unlock the boot loader which opens the door to all custom roms for this device. Note 3.2.8 rollback carries a risk (permanent brick) if not executed properly. A summary of the procedure can be found here. Make sure you fully understand before attempting. Guessing 50% of those who start end up bricking their device by simply not following instructions.
Click to expand...
Click to collapse
i'am sorry i forgot to mention my device version is Kindle fire HD 7 soho. i know i suppose to be in other thread. anyway, you think i can follow the steps you mention above?

n.fajira said:
i'am sorry i forgot to mention my device version is Kindle fire HD 7 soho. i know i suppose to be in other thread. anyway, you think i can follow the steps you mention above?
Click to expand...
Click to collapse
Likely not. The specially crafted 3.2.8 rollback image was captured during a brief period when Amazon honored downgrade requests. It is device dependent and would probably brick a HD 7.

Davey126 said:
Obvious questions:
- what version of FireOS does it show now?
- still rooted?
Click to expand...
Click to collapse
Version- 4.5.5.1
Still Have Root after rooting on 31/06/16 with Bigfoot 4.5.0

Android Rom Guy said:
Version- 4.5.5.1
Still Have Root after rooting on 31/06/16 with Bigfoot 4.5.0
Click to expand...
Click to collapse
Suspect reset was random given many days have passed without further consequence.

FireOS 5.3.1.1 is coming - root 5.3.1 ASAP & disable OTA !!!

I've glanced at the updates for the latest Fire HD 8 2016 model, and it has version 5.3.1.1 already available :
https://www.amazon.com/gp/help/customer/display.html?nodeId=202073860
So if history is any guide, all the other Fires will see the same update real soon now ...
Use the latest Kingroot to root FireOS 5.3.1, and disable OTA !!!
http://forum.xda-developers.com/amazon-fire/general/root-t3471289

How do I remove ota Updates?
I renamed 2 APKs now when I check for updates it reports "Failed" am I Fine?
I want to switch to CM12.1 but I am afraid to try the method for 5.1.2 someone said it is the same procedure but I am not yet srue.
and I need to pay for Super Sume I guess.
so At least can someone clear out how we disable ota updates? I don't trust PM hide method, Renamed some apk but I am not sure if it worked.

-Yami- said:
How do I remove ota Updates?
I renamed 2 APKs now when I check for updates it reports "Failed" am I Fine?
I want to switch to CM12.1 but I am afraid to try the method for 5.1.2 someone said it is the same procedure but I am not yet srue.
and I need to pay for Super Sume I guess.
so At least can someone clear out how we disable ota updates? I don't trust PM hide method, Renamed some apk but I am not sure if it worked.
Click to expand...
Click to collapse
You could use rootjunky's supertool but if it already says failed it should be fine

tonibm19 said:
You could use rootjunky's supertool but if it already says failed it should be fine
Click to expand...
Click to collapse
thanks I'll go ahead and also apply rootjunkies supertool method, I wasnt sure if it gonna work on 5.3.1 so didn't try.
Just to make sure I am not letting it connect to internet, switching to CM12.1 will be the best.

-Yami- said:
How do I remove ota Updates?
I renamed 2 APKs now when I check for updates it reports "Failed" am I Fine?
I want to switch to CM12.1 but I am afraid to try the method for 5.1.2 someone said it is the same procedure but I am not yet srue.
and I need to pay for Super Sume I guess.
so At least can someone clear out how we disable ota updates? I don't trust PM hide method, Renamed some apk but I am not sure if it worked.
Click to expand...
Click to collapse
Really need to take a step back and review the documentation that has already been posted starting with the forum index . Tons of relevant material. The SuperTool should handle everything you need in advance of flashing a new ROM if that's your objective:
- SuperTool can disable OTAs, replace KingUser with SuperSU and perform a host of other useful tasks
- "renamed some apk" is not helpful; details matter
- don't need to pay for anything beyond the device itself
- if still worried about OTA updates turn off WiFi and keep reading on another device

Davey126 said:
Really need to take a step back and review the documentation that has already been posted starting with the forum index . Tons of relevant material. The SuperTool should handle everything you need in advance of flashing a new ROM if that's your objective:
- SuperTool can disable OTAs, replace KingUser with SuperSU and perform a host of other useful tasks
- "renamed some apk" is not helpful; details matter
- don't need to pay for anything beyond the device itself
- if still worried about OTA updates turn off WiFi and keep reading on another device
Click to expand...
Click to collapse
I am aware of supertool, I was not sure if it gonna work on 5.3.1 or not and someone said he switched using super sume so it was paid.
I renamed otaverifier.apk and devicesoftwareota.apk
I'll go ahead and use supetool thank you.
edit:
I got an option:
1 block OTA updates from Amazon 5.0.1
2 block OTA updates from Amazon on 5.1.1 and 5.1.2
so this was why I avoided this tool, not sure which one to use and not sure if it gonna brake something or not because I am on 5.3.1
I'll go ahead and read .bat file.
edit2:
found these lines
files\adb.exe shell pm hide com.amazon.otaverifier
files\adb.exe shell pm hide com.amazon.device.software.ota
files\adb.exe shell pm hide com.amazon.settings.systemupdates
Renamed those APKs.
but the tool also have this:
files\adb.exe shell su -c "rm -r /system/app/otaverifier"
files\adb.exe shell su -c "rm -r /system/priv-app/DeviceSoftwareOTA"
files\adb.exe shell su -c "rm -r /system/priv-app/SystemUpdatesUI"
so these are responsible APKs, I missed out "SystemUpdatesUI" on my first try thanks to this tool now I know what do rename.
I must be safe now I guess, it is not going to download and replace those bcz I didnt use PM-Hide.
edit:
I also cannot find any option to convert from kingroot to SuperSu in supertool.
at least not in its menu.

-Yami- said:
I am aware of supertool, I was not sure if it gonna work on 5.3.1 or not and someone said he switched using super sume so it was paid.
I renamed otaverifier.apk and devicesoftwareota.apk
I'll go ahead and use supetool thank you.
edit:
I got an option:
1 block OTA updates from Amazon 5.0.1
2 block OTA updates from Amazon on 5.1.1 and 5.1.2
so this was why I avoided this tool, not sure which one to use and not sure if it gonna brake something or not because I am on 5.3.1
I'll go ahead and read .bat file.
Click to expand...
Click to collapse
- devicesoftwareota.apk is the operative file; just make sure it does not end in .apk
- as noted in numerous recent posts follow the procedures for 5.1.2 with 5.3.1
- if you can read/interpret the .bat file then none of this should be a mystery; the SuperTool simply automates a number of relatively trivial tasks that can be performed manually if desired (taking nothing away from the SuperTool; it is a fantastic resource for a huge community of individuals who have benefited from the selfless individual who authored it; props to @tomstg, a.k.a. Root Junkie!).
- if you have a question, ask; just be sure you have done your homework first given the vast pool of resource that is already out there; no interest in repackging what has already been written; props to @sd_shadow who tirelessly collects information from contributors and and assembles guides for YOUR benefit.
- if still uncertain shelve the device for a few weeks until the dust settles given the recent (<48 hours old) discovery that 5.3.1 can be rooted

Can 5.3.1.1 be downgraded to 5.3.1.0?

Danny1976 said:
Can 5.3.1.1 be downgraded to 5.3.1.0?
Click to expand...
Click to collapse
Unknown but assume not unless posted otherwise. Only way to know is someone tries it and scores success or a brick.

I got my Fire HD8 (6th gen/2016) and the update for 5.3.1.1 is available. Still hasnt updated, I turned it off now. I cannot root 6th gen HD8 and I dont know of any methods that prevent the OTA update without root. Help
Edit: ops, I fail at navigating the xda forum apparently. I didn't see im in the wrong section.

I guess a benefit of the having a low end device like the Fire 7" is that they receive updates later than other devices. So you are aware of problems related to rooting early.
Anyways I ordered a Fire at Amazon Germany that arrived today and was initially shipped with Firmware 5.0.1.
I wonder why they still ship out devices with such old firmware. But tht's good for us

sebr said:
I guess a benefit of the having a low end device like the Fire 7" is that they receive updates later than other devices. So you are aware of problems related to rooting early.
Anyways I ordered a Fire at Amazon Germany that arrived today and was initially shipped with Firmware 5.0.1.
I wonder why they still ship out devices with such old firmware. But tht's good for us
Click to expand...
Click to collapse
You know the drill - root and protect that bootloader before connecting to WiFi! Or take the express route and boot directly into fastboot via <power>+<vol-down>, fire up TWRP and have your way with a custom ROM. Bounce back if you need any help with procedures.

Yeah no worries CM12 already running on it. But what is different in Bootloader versions past 5.0.1? I thought the bootloader is locked anyways - regardless of what firmware version is used - and cannot be flashed.

sebr said:
Yeah no worries CM12 already running on it. But what is different in Bootloader versions past 5.0.1? I thought the bootloader is locked anyways - regardless of what firmware version is used - and cannot be flashed.
Click to expand...
Click to collapse
5.0.x bootloader allows a custom recovery (eg: twrp) to be booted from fastboot. Nothing like a true recovery to expedite flashes and recover from missteps.

Yeah.... I wasn't able to get KingRoot to work with 5.3.1.1 and now I'm on 5.3.2 and it still won't work. I just got this tablet about a week ago. I should have rooted it before I first connected to WiFi, but I received it as a gift, so I hadn't researched the process in advance and I wasn't certain that I wanted to mess with it. I usually root my devices, but I considered leaving this one unrooted... until it was too late. Sometimes, a little hesitation makes the decision for you.

ManWithCamera said:
Yeah.... I wasn't able to get KingRoot to work with 5.3.1.1 and now I'm on 5.3.2 and it still won't work. I just got this tablet about a week ago. I should have rooted it before I first connected to WiFi, but I received it as a gift, so I hadn't researched the process in advance and I wasn't certain that I wanted to mess with it. I usually root my devices, but I considered leaving this one unrooted... until it was too late. Sometimes, a little hesitation makes the decision for you.
Click to expand...
Click to collapse
First I have heard of 5.3.1.1 and 5.3.2 for 5th gen tablets. Sure you have a 7" model (first released Sept 2015) and not the latest HD8 (released 2016)?

Davey126 said:
First I have heard of 5.3.1.1 and 5.3.2 for 5th gen tablets. Sure you have a 7" model (first released Sept 2015) and not the latest HD8 (released 2016)?
Click to expand...
Click to collapse
That's probably because the smart people on here have already blocked their updates. Yes, I confirmed that a 7" tablet is what was ordered from Amazon. It also has 2015 stamped on the back and it claims to be a 5th generation tablet in the settings. It installed the 5.3.2.0 update last night at 11:18pm.

ManWithCamera said:
That's probably because the smart people on here have already blocked their updates. Yes, I confirmed that a 7" tablet is what was ordered from Amazon. It also has 2015 stamped on the back and it claims to be a 5th generation tablet in the settings. It installed the 5.3.2.0 update last night at 11:18pm.
Click to expand...
Click to collapse
So now we know: FireOS 5.3.2 is in the wild and (apparently) can not be rooted w/KingRoot at present. What isn't known is whether 5.3.2 can be rolled back to 5.3.1 without bricking. Typically someone has to sacrifice their device (accidentally or intentionally) to determine that.
I'll create a new thread with you findings later today if someone doesn't beat me to it. Thanks for sharing.