Database Users

Latest FireOS 5.1.1 (Bellini) OTA file is captured !!! :

Update2 : the update file has been captured !!! See this :
http://forum.xda-developers.com/showpost.php?p=65303839&postcount=31
Update: see at the bottom
According to the Slickdeals crowd, FireOS 5.1.1 OTA update for Fire HD 6 & 7 2014 has been spotted in the wild. Thus, we gotta capture it & torture it !
In the meantime, double check that your OTA updates are blocked if you don't want to catch it accidentally.
If the Fire 7 2015 situation is any guide, the upgrade should be fairly smooth (via TWRP), if the bootloaders are kept as is. Try to preserve 5.2.0 bootloaders, if you can.
Here is the guide :
http://forum.xda-developers.com/fire-hd/general/how-to-upgrade-to-lollipop-root-gapps-t3163950
If you caught 4.5.5.1, it looks like the bootloaders from 5.1.1 should be able to run without bricking. So your path is to go to 5.1.1 from 4.5.5.1, sideload 4.5.3, root, and update via TWRP to 5.1.1 (preserving 5.1.1 bootloaders as to avoid bricking).
If 5.2.2u2 bootloaders upgrade OK to the new bootloaders, we could sunset those.
Update - Feb 5th, 2016: It looks like Amazon is probably swamped with the downgrade requests, so they put together this page:
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201980430
How nice - "Downgrading to Fire OS 4 requires a factory reset and will remove all of your personal information, Amazon account information, downloaded content, and applications from internal storage."
I just checked my Fire that has FireOS 5.0.1 with root, and it's offering to downgrade it to FireOS 4. So this immediately offers a path to 5.1.1, first, request FireOS 4, put it back yourself via TWRP, then request an upgrade, and it should give you FireOS 5.1.1. This is where one could capture the update file.
Also note that if you already have 5.1.1, you still need to downgrade to 4.5.3 to get root. So request FireOS 4, downgrade to 4.5.3, root, then go back, request FireOS 5, and grab the update file. At this point we'll explain here how to put that 5.1.1 back on your device, but now with root.

bibikalka said:
If you caught 4.5.5.1, it looks like the bootloaders from 5.1.1 should be able to run without bricking. So your path is to go to 5.1.1 from 4.5.5.1, sideload 4.5.3, root, and update via TWRP to 5.1.1 (preserving 5.1.1 bootloaders as to avoid bricking).
Click to expand...
Click to collapse
I am not new to rooting and flashing, but I am new to trying it on the Amazon Fire HD. I came here to figure out how to root so I can turn it into a plain-jane Android tablet. However, I now see that I "caught" 4.5.5.1 this week after recharging the dead tablet. How exactly do I do what is listed? Is there a root guide for someone who has a pristine, unrooted 4.5.5.1 system?

What does this mean? A new update based on Android 5.1.1? So a FireOS version newer than 5.2.2u2? Featuring the Blue Shade feature?

troycarpenter said:
I am not new to rooting and flashing, but I am new to trying it on the Amazon Fire HD. I came here to figure out how to root so I can turn it into a plain-jane Android tablet. However, I now see that I "caught" 4.5.5.1 this week after recharging the dead tablet. How exactly do I do what is listed? Is there a root guide for someone who has a pristine, unrooted 4.5.5.1 system?
Click to expand...
Click to collapse
Most likely you'll have to wait for 5.1.1 being OTAed to you, then you can downgrade to 4.5.3, get root, and upgrade back to 5.1.1
So stay put till some official Lollipop is beamed down to you.

I am one of the guys over at Slickdeals who has an HD7 running on 5.1.1. Although, it wasn't an OTA update - it actually came to me that way! I bought one of the $30 specials when they were on sale a few weeks ago (actually I bought a bunch of them!), and this last one came to me with 5.1.1 already installed on it. There have been a few other people who said theirs updated with an OTA update, first to 5.0.1 and then to 5.1.1, but those instances have been very rare. I'm guessing with the millions of HD7 devices out there it's probably going to take a while for the complete roll out.
Does anyone know how they prioritize the OTA roll out? Is it done by serial # or manufacture date? Or by the date the devices was first registered?

I opened 2 of my 8gb 7HD and 1 was on 5.1.1 straight from the box while the other one is on 4.5.5. I have put the 2nd one in airplane mode and now following the guide to get it rooted.

jleonard711 said:
I am one of the guys over at Slickdeals who has an HD7 running on 5.1.1. Although, it wasn't an OTA update - it actually came to me that way! I bought one of the $30 specials when they were on sale a few weeks ago (actually I bought a bunch of them!), and this last one came to me with 5.1.1 already installed on it. There have been a few other people who said theirs updated with an OTA update, first to 5.0.1 and then to 5.1.1, but those instances have been very rare. I'm guessing with the millions of HD7 devices out there it's probably going to take a while for the complete roll out.
Does anyone know how they prioritize the OTA roll out? Is it done by serial # or manufacture date? Or by the date the devices was first registered?
Click to expand...
Click to collapse
fizz1234 said:
I opened 2 of my 8gb 7HD and 1 was on 5.1.1 straight from the box while the other one is on 4.5.5. I have put the 2nd one in airplane mode and now following the guide to get it rooted.
Click to expand...
Click to collapse
One of you guys can help us !
Amazon put a page together here "Reset and Downgrade Your 4th Generation Fire Tablet to Fire OS 4" :
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201980430
What you do is request downgrade to FireOS4, then go load 4.5.3 manually, root it, and perhaps load 4.5.5.1 as per these instructions :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
This should make the attempted downgrade to FireOS 4 fail since it'll try to load 4.5.5.1 on top of 4.5.5.1
Then go back and request upgrade to FireOS5 as per Amazon's instructions. I checked my Fire, it does not have the upgrade option yet (or the downgrade one for that matter).
If you are careful, you can catch the upgrade file to 5.1.1 on the way back, and post it here.
Unfortunately, not an easy path yet ...

bibikalka said:
One of you guys can help us !
Amazon put a page together here "Reset and Downgrade Your 4th Generation Fire Tablet to Fire OS 4" :
http://www.amazon.com/gp/help/customer/display.html/ref=hp_left_v4_sib?ie=UTF8&nodeId=201980430
What you do is request downgrade to FireOS4, then go load 4.5.3 manually, root it, and perhaps load 4.5.5.1 as per these instructions :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
This should make the attempted downgrade to FireOS 4 fail since it'll try to load 4.5.5.1 on top of 4.5.5.1
Then go back and request upgrade to FireOS5 as per Amazon's instructions. I checked my Fire, it does not have the upgrade option yet (or the downgrade one for that matter).
If you are careful, you can catch the upgrade file to 5.1.1 on the way back, and post it here.
Unfortunately, not an easy path yet ...
Click to expand...
Click to collapse
I would be nervous to downgrade to OS 4 and then not be able to get back to OS 5, since mine came with it preinstalled rather than receiving it OTA.

jleonard711 said:
I would be nervous to downgrade to OS 4 and then not be able to get back to OS 5, since mine came with it preinstalled rather than receiving it OTA.
Click to expand...
Click to collapse
It would not actually matter ... But to grab the update file requires some skill, so that's not for everybody.

bibikalka said:
. . .
What you do is request downgrade to FireOS4, then go load 4.5.3 manually, root it, and perhaps load 4.5.5.1 as per these instructions :
http://forum.xda-developers.com/fire-hd/general/upgrade-to-4-5-5-root-t3174449
This should make the attempted downgrade to FireOS 4 fail since it'll try to load 4.5.5.1 on top of 4.5.5.1
. . .
Click to expand...
Click to collapse
What am I missing? When you request downgrade to OS4, won't you (probably) get 4.5.5.1? Can't manually load 4.5.3 on that.

DoLooper said:
What am I missing? When you request downgrade to OS4, won't you (probably) get 4.5.5.1? Can't manually load 4.5.3 on that.
Click to expand...
Click to collapse
Who knows ... If you have 4.5.3 and have a request for FireOS 5, would it go straight to 5.1.1, or with a detour to 4.5.5.1 ?
I actually have TWRP backups of both 4.5.5.1 and 5.2.0, so I'll try to request downgrade, manually go to 4.5.5.1, and then request an upgrade to 5, and see if I can grab the file then.

what am i missing? i have 5.0.1 on my hd 6 but im not getting the option to downgrade on the device action dropdown. help.

pilferedpastry said:
what am i missing? i have 5.0.1 on my hd 6 but im not getting the option to downgrade on the device action dropdown. help.
Click to expand...
Click to collapse
Is it registered? (just a thought)

DoLooper said:
Is it registered? (just a thought)
Click to expand...
Click to collapse
yes, im pretty sure it is.

pilferedpastry said:
yes, im pretty sure it is.
Click to expand...
Click to collapse
Try to deregister and register again. I just re-registered a 5.0.1 device, and it immediately offered to downgrade it.
I am seeing some weird effects. I use TWRP to clone 1 registered Fire onto another. (backup /boot, /system, /data, change serial number in the directory name, and then restore to the new Fire, updating bootloaders afterwards if it's FireOS 5) Then while the serial for the 2nd fire does not match, this 2nd fire can still deregister both devices.

bibikalka said:
Try to deregister and register again. I just re-registered a 5.0.1 device, and it immediately offered to downgrade it.
I am seeing some weird effects. I use TWRP to clone 1 registered Fire onto another. (backup /boot, /system, /data, change serial number in the directory name, and then restore to the new Fire, updating bootloaders afterwards if it's FireOS 5) Then while the serial for the 2nd fire does not match, this 2nd fire can still deregister both devices.
Click to expand...
Click to collapse
Really strange. Of course you changed it in build.prop, too! Wonder what Amazon sees at their end--and how such a situation could be used to our advantange! Ah, well, straightens itself out at boot, right?
Yes, registration is the key. I notice all my gazillion devices show a deregister option, even those that weren't replacements and have never been registered. I get the downgrade option for the "truly" registered HD7 (along with a bunch of other options), but the unregistered HD7 on July developers preview just has deregister, set as default and manage firefly.
I'm eagerly awaiting the report that you captured 5.1.1, and then to learn what OS4 they downgrade you to. Seems like lots of potential here!

DoLooper said:
Really strange. Of course you changed it in build.prop, too! Wonder what Amazon sees at their end--and how such a situation could be used to our advantange! Ah, well, straightens itself out at boot, right?
Yes, registration is the key. I notice all my gazillion devices show a deregister option, even those that weren't replacements and have never been registered. I get the downgrade option for the "truly" registered HD7 (along with a bunch of other options), but the unregistered HD7 on July developers preview just has deregister, set as default and manage firefly.
I'm eagerly awaiting the report that you captured 5.1.1, and then to learn what OS4 they downgrade you to. Seems like lots of potential here!
Click to expand...
Click to collapse
Well, I don't really plan to capture the FireOS 4 downgrade file since I am not sure how to do that logistically. I was going to request the downgrade, then reload FireOS4 TWRP backup on that device, and hope that it would recognize that the downgrade has happened, and will offer me to upgrade back. Of course, I may end up unregistered, and it'll be futile since if I just register a FireOS4 device, it won't be offering an upgrade to FireOS5 ...
Enabling DeviceSoftwareOTA produces a lot of weird effects (downloads continue after I block it again), so I am not clear at the moment how the operations like this proceed.

@ DoLooper
I've set up a sacrificial FireOS5 device, unblocked all of the Amazon stuff (including OTA), and requested the downgrade to FireOS4.
Immediately in the Amazon's device menu I get an option "Upgrade to FireOS5".
I am in the airplane mode, will check up on the network activity periodically, to see if it wants to start beaming down the downgrade file ...
I wish I knew how to do this automatically ...

bibikalka said:
@ DoLooper
I've set up a sacrificial FireOS5 device, unblocked all of the Amazon stuff (including OTA), and requested the downgrade to FireOS4.
Immediately in the Amazon's device menu I get an option "Upgrade to FireOS5".
I am in the airplane mode, will check up on the network activity periodically, to see if it wants to start beaming down the downgrade file ...
I wish I knew how to do this automatically ...
Click to expand...
Click to collapse
Ha! Looks like we crossed in the mail I wait with baited breath. :fingers-crossed:
@bibikalka: What about an OTA block <--> logcat loop script? Something like 15-20 minutes blocked, 90 second logcat then block again? @bibikalka: right, can't turn off a logcat. Maybe with eclipse or some other tool?

bibikalka said:
Try to deregister and register again. I just re-registered a 5.0.1 device, and it immediately offered to downgrade it.
I am seeing some weird effects. I use TWRP to clone 1 registered Fire onto another. (backup /boot, /system, /data, change serial number in the directory name, and then restore to the new Fire, updating bootloaders afterwards if it's FireOS 5) Then while the serial for the 2nd fire does not match, this 2nd fire can still deregister both devices.
Click to expand...
Click to collapse
nope. still nothing.

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.

5.3.1 ROOT! :)

Kingroot now roots 5.3.1!
If you are having trouble installng cm 12.1, try the supertool or @wtfjajaja's instructions.
wtfjajaja said:
try it a few times, i encountered the same problems as well
here's what i did
1. factory reset through recovery
2. root with kingroot, (it worked for me after 2 to 3 tries)
3. installed supersu-me 6.7
4. update su binary
it's important here! don't restart yet, my device bricked few times here
5. install flashfire 0.53
6. follow the steps to install cm12.1 under flashfire from here
7. enjoy
Click to expand...
Click to collapse
Supertool: http://forum.xda-developers.com/amazon-fire/development/amazon-fire-5th-gen-supertool-root-t3272695
Bricked?: http://forum.xda-developers.com/amazon-fire/general/unbrick-amazon-fire-7in-2015-5th-gen-t3285294

Fingers crossed! I can't wait to start flashing roms!

If you're root then maybe you can use flashfire to flash a rom just like 5.1.2

tonibm19 said:
If you're root then maybe you can use flashfire to flash a rom just like 5.1.2
Click to expand...
Click to collapse
Flashfire needs supersu
or Cmsu to work.

hooks024 said:
Flashfire needs supersu
or Cmsu to work.
Click to expand...
Click to collapse
Try rootjunky's supertool after rooting to see if it can install it.

.
tonibm19 said:
Try rootjunky's supertool after rooting to see if it can install it.
Click to expand...
Click to collapse
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1

DoctorDark_ said:
I just installed coverted kingroot into supersu using supersume. I then used flashfire to install CM12.1
Click to expand...
Click to collapse
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.

marvelous news!!!

DoctorDark_ said:
Kingroot now roots 5.3.1! Hopefully someone can quickly push out a toolkit.
Click to expand...
Click to collapse
Would you add the 5.3.1 version in the title ???

tonibm19 said:
So you installed cm12.1 coming from fireos 5.3.1?
That's awesome!
You should create a tutorial so others can do that to.
Click to expand...
Click to collapse
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.

Nice I will try it out.

Good chance the latest versions of Kingroot (always evolving) will also work for those on FireOS 5.1.2.1-5.1.4. Worth a try before attempting a rollback to 5.1.2.

I couldn't get super sume to work.

not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)

ttcontributor said:
not working here only upto around 17% restarted a dozen times still not work (Fire 7 2015 5.3.1)
Click to expand...
Click to collapse
Not good - earlier builds of Kingroot froze around 29% before crapping out. Make sure you have the latest Kingroot app. Also try a factory reset (warning: you will loose personal apps/data) and do not register with Amazon during subsequent device initialization. This proved effective for some in the past. Recognize the community is still learning; expect some failures along the way.

Davey126 said:
Same procedure as if coming from FireOS 5.1.2; a new tutorial is not required.
Click to expand...
Click to collapse
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.

-Yami- said:
Which same procedure?
I found a thread but I am not sure if it'll work for new KingRoot, should I pay for Super Sume?
Also what about anti-rollback. What happens when I flash with FlashFire and say I somehow bricked the device?
Can I still adb sideload 5.3.1 back?
We really need a new guide or toolkit because all of these makes me confused.
For those who cannot root.
Tablet shuts down, you go back in Kingroot click root it starts somewhere from 20%s and then reports failed,
You click root again then it roots.
Click to expand...
Click to collapse
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.

Davey126 said:
Take a deep breath and start researching what has already been posted (forum index). We don't need a "need a new guide or toolkit" because you are new to the game and haven't done your homework. Everything that was written for 5.1.2 should be applicable to 5.3.1 until proven otherwise.
Click to expand...
Click to collapse
Come check my browser, I've read every single thread on the forums man, the thing is 5.1.2 is not same as 5.3.1 and device has locked bootloader and anti-rollback.
So it is not like my Motorola with unlocked bootloader, I am not sure if I always can save the device and also I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
So I had to make it clear everything works for 5.1.2 also will work for 5.3.1
Now I have to convert kingroot to supersu somehow (can't find the option under supertool like you mentioned.)
Your approach was a little bit harsh on me m8
It doesn't say "What can be done on 5.1.2 also can be done on 5.3.1" anywhere, it says the opposite everywhere.
So someone had to clear it out. Thank you for your help, It really helped me a lot.

-Yami- said:
Come check my browser, I've read every single thread on the forums man...
Click to expand...
Click to collapse
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
-Yami- said:
I cannot send it back to amazon if something goes wrong. (I think I can adb sideload 5.3.1 if I hard brick? see I am not sure).
Click to expand...
Click to collapse
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu

Davey126 said:
...wow, could make a fortune teaching others to speed read. Installing FlashFire from the SuperTool will take care of the necessary prerequisites around KingUser->SuperSU migration. To be honest I'm not sure it's still necessary with more recent FlashFire builds
- if the device is within the warranty period for your region Amazon will exchange it no questions asked (many data points)
- if you 'hard brick' the device nothing can recover it short of board replacement
- a soft brick can be recovered by side loading FireOS 5.3.1 via the stock recovery menu
Click to expand...
Click to collapse
The reason that I cannot return device to amazon is, shipment will cost more than the actual device from here to amazon, and I got it as a gift.
and Thanks so I missed out the part that Supertool automates the conversion when I click install Flashfire, thank you.
Now after this post everybody jumping right onto 5.3.1 root gonna know it, and the guy on first page have used Super Sume, so he probably would use
Supertool if he knew.

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.

5.3.2.1 Root

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.
https://forum.xda-developers.com/am...-5th-gen-supertool-root-t3272695/post70784402
Reminder: Do not attempt to rollback FireOS 5.3.2.1; you will likely be rewarded with a brick.

No success for me. I have assumed "Gave both king root and purify full access via setting" as enabling these apps in accessibility under services?
I have tried KR 4.9.2, 4.9.6, 4.9.7, 5.0.0 and 5.0.3 numerous times. Also done a factory reset and followed the steps stated to no avail.
Maybe I am just unlucky.

stonedpsycho said:
No success for me. I have assumed "Gave both king root and purify full access via setting" as enabling these apps in accessibility under services?
I have tried KR 4.9.2, 4.9.6, 4.9.7, 5.0.0 and 5.0.3 numerous times. Also done a factory reset and followed the steps stated to no avail.
Maybe I am just unlucky.
Click to expand...
Click to collapse
Not having any luck with it either.

This is just a quick overview for testing purposes. As always, there is an extreme chance of the undesired "Bricked Device". You are warned...
1. Make sure adb and fastboot drivers are enabled and working to the 5th gen Fire. Extremely important.
2. Once connection is working follow the "Super Tool" setup directions.
3. Disable ota, disable ads and install GPlay. Somethings can only be done after root.
4. Once you have Gplay setup, use Super Tool to install KingRoot.
5. When you first run KingRoot, it will advertise "Purify Battery Saver" install it.
6. Afterwards run KingRoot. It will reboot 3-5 times before applying root. This process of rooting consumed over an hour and may need to be restarted if KingRoot fails.
7. Please keep in mind it is just an overview in order to determine the steps correctly.
If necessary I will start from square one and document all my steps. After rooting, I downgraded to 5.3.1 and verified 2 roms worked (Fire Nexus and CM Fire.)
My apologies for not providing more accurate details, its just an overview.

TechDad378 said:
This is just a quick overview for testing purposes. As always, there is an extreme chance of the undesired "Bricked Device". You are warned...
1. Make sure adb and fastboot drivers are enabled and working to the 5th gen Fire. Extremely important.
2. Once connection is working follow the "Super Tool" setup directions.
3. Disable ota, disable ads and install GPlay. Somethings can only be done after root.
4. Once you have Gplay setup, use Super Tool to install KingRoot.
5. When you first run KingRoot, it will advertise "Purify Battery Saver" install it.
6. Afterwards run KingRoot. It will reboot 3-5 times before applying root. This process of rooting consumed over an hour and may need to be restarted if KingRoot fails.
7. Please keep in mind it is just an overview in order to determine the steps correctly.
If necessary I will start from square one and document all my steps. After rooting, I downgraded to 5.3.1 and verified 2 roms worked (Fire Nexus and CM Fire.)
My apologies for not providing more accurate details, its just an overview.
Click to expand...
Click to collapse
Are you sure it was 5.3.2.1 you where on ? I only ask because downgrading to 5.3.1 from 5.3.2.1 should result in a brick as the boot loader used in 5.3.1 and 5.3.2 changed from on 5.3.2.1 and the anti-roll back measure amazon have should have kicked in to give you a brick.
How did you roll back ? Through ADB or placing the update file in the internal SD ?

Correct it was 5.3.2.1. While playing around with it I hit a black screen while booting. Upon reading some posts, I thought there was no return because of the version. Since the device responded via usb on pc, adb sideload worked causing downgrade to work.
Don't get me wrong this may have been just pure random luck. But hopefully my results my lead to "Fire Lineage OS".

No luck with this method. Will keep trying.

Zero Luck yet as well. Will try again. Hopefully something more reliable will come about soon.

Sorry to hear you have had no success. Will revert everything back and document each step. Once the method has been identified as successful, the information will be provided.

You still need to provide us with one of the most important tips, what version of kingroot you are using.
Thank you

TechDad378 said:
... But hopefully my results my lead to "Fire Lineage OS".
Click to expand...
Click to collapse
Quick side note: No LineageOS for this pup while the bootloader remains locked. LineageOS begins with Android 6 (Marshmallow); the current suite of Android 5 (Lollipop) ROMs is all we'll see due to FireOS 5 kernel restrictions. Unless Amazon releases and back ports FireOS 6 to older devices. Highly unlikely IMHO ... economics don't square.

If someone succeeds, could they try to post the kmPlugins.zip from their downloads folder? If we can get that from a successful root, then we could probably skip all the repeated failures and just get KingRoot to use that method immediately.

What ever happened to the guy that had rooted it? I knew he was bs.

Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
Hmm...
Interesting response.
With a full time job and a family, this is a hobby I do for fun in my spare time. Most mods are done with patience and diligence.
Recommending following command,
C:/yourself/ adb sideload patience.zip
---------- Post added at 03:20 AM ---------- Previous post was at 03:09 AM ----------
Davey126 said:
Quick side note: No LineageOS for this pup while the bootloader remains locked. LineageOS begins with Android 6 (Marshmallow); the current suite of Android 5 (Lollipop) ROMs is all we'll see due to FireOS 5 kernel restrictions. Unless Amazon releases and back ports FireOS 6 to older devices. Highly unlikely IMHO ... economics don't square.
Click to expand...
Click to collapse
Point taken. Just hoping LineageOS will be as widespread.
As for the root, I reverted back to original. Trying to recreate the environment which allowed success.

Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
Nice. If you bothered to read his post history you might think differently. Well presented/documented with all the appropriate caveats.

Geek Surfer said:
What ever happened to the guy that had rooted it? I knew he was bs.
Click to expand...
Click to collapse
What a shame that people can't be considerate online anymore.

@TechDad378 Could you verify what supertool version you are using . I'm trying to figure what version of gapps got installed, and can you recall if you installed any apps from playstore like chrome ?
I don't have a tablet with 5.3.2.1 but it occoured to me that kingroot may have found a backdoor to root in playstore or another installed app. I've tested on a tablet with previously unrootable 5.1.4 and the difference in root behaviour pre/post play store installion is very noticable. The tablet reboots several time during root with playstore installed , it only rebooted once without it installed.
Ive not managed to root it yet but kingroot now stuck on verifing root status, it previouly detected it as unrooted, something has changed
My router is blocking OTA so going keep playing with this

5.1.4 Rooted !!!!!
Mr McBoatface said:
@TechDad378 Could you verify what supertool version you are using . I'm trying to figure what version of gapps got installed, and can you recall if you installed any apps from playstore like chrome ?
I don't have a tablet with 5.3.2.1 but it occoured to me that kingroot may have found a backdoor to root in playstore or another installed app. I've tested on a tablet with previously unrootable 5.1.4 and the difference in root behaviour pre/post play store installion is very noticable. The tablet reboots several time during root with playstore installed , it only rebooted once without it installed.
Ive not managed to root it yet but kingroot now stuck on verifing root status, it previouly detected it as unrooted, something has changed
My router is blocking OTA so going keep playing with this
Click to expand...
Click to collapse
Well it may not be the news most visiting this thread are looking for but I've rooted the previously unrootable 5.1.4 !!!!
I played around with various play store installations as suggested in my post above looking for a back door to root. 3 hours and got no where. Decided to downgrade to 5.1.2 and use supertools to root it the tablet. For the life of my I couldn't root this rootable OS..... six attempts failed each with multipul reboots. Then I read up a bit more and use kingroot 4.8.2 as suggested in this thread - https://forum.xda-developers.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300. This time 5.1.2 Rooted first time one reboot using Kingroot. I had always thought the Kingroot edition used didn't really matter that the files it used came from the online database. This result put that assumption into doubt.
Decided to go back to 5.1.4 and retry using the kingroot as above....... Didn't work. Not being someone who gives up easy i tried the impressively long-named "NewKingrootV5.0.1_C165_B377_xda_release_protected_2016_12_22_20161222120332_105243_signed.apk" from here https://forum.xda-developers.com/devdb/project/?id=9793#downloads
Rooted first time !!! It did reboot a few times, I had to manually restart the root process each time it rebooted but it picked off at the % point where it rebooted.
Moral of the story never give up and try some kingroot versions from the xda links above
Going to reset the device and confirm it's repeatable.

Mr McBoatface said:
Well it may not be the news most visiting this thread are looking for but I've rooted the previously unrootable 5.1.4 !!!!
I played around with various play store installations as suggested in my post above looking for a back door to root. 3 hours and got no where. Decided to downgrade to 5.1.2 and use supertools to root it the tablet. For the life of my I couldn't root this rootable OS..... six attempts failed each with multipul reboots. Then I read up a bit more and use kingroot 4.8.2 as suggested in this thread - https://forum.xda-developers.com/amazon-fire/general/flashing-kindle-5-1-2-using-kingroot-t3346300. This time 5.1.2 Rooted first time one reboot using Kingroot. I had always thought the Kingroot edition used didn't really matter that the files it used came from the online database. This result put that assumption into doubt.
Decided to go back to 5.1.4 and retry using the kingroot as above....... Didn't work. Not being someone who gives up easy i tried the impressively long-named "NewKingrootV5.0.1_C165_B377_xda_release_protected_2016_12_22_20161222120332_105243_signed.apk" from here https://forum.xda-developers.com/devdb/project/?id=9793#downloads
Rooted first time !!! It did reboot a few times, I had to manually restart the root process each time it rebooted but it picked off at the % point where it rebooted.
Moral of the story never give up and try some kingroot versions from the xda links above
Going to reset the device and confirm it's repeatable.
Click to expand...
Click to collapse
Nice! While you can downgrade 5.1.4, this mean it may be possible to root without using a PC to downgrade first. I'm going to try on 5.3.2.1, and see how it works.
Sent from my Amazon Fire using XDA Labs

Repeated root on 5.1.4, replace the kingroot in supertools with the "NewKingrootV5.0.1_C165_B377_xda_release_protected _2016_12_22_20161222120332_105243_signed.apk" version and ran the script.
It needed 2 attempts this time but it rooted. The supertools script removed it and replaced with supersu.
See attached video in zip to confirm