Database Users

KFSOWI: update despite host file manipulation

Hello,
My system underwent an fireos update to. 11.3.2.1 despite manipulation of the hosts file. I will try rerooting my device using known methods as soon as I get home and keep you updated.

jonathanlyng said:
Hello,
My system underwent an fireos update to. 11.3.2.1 despite manipulation of the hosts file. I will try rerooting my device using known methods as soon as I get home and keep you updated.
Click to expand...
Click to collapse
Same here ... any luck with re-rooting?

Danged Amazon and their OTA
jonathanlyng said:
Hello,
My system underwent an fireos update to. 11.3.2.1 despite manipulation of the hosts file.
Click to expand...
Click to collapse
Same here. I suppose I'll patiently wait for the next iteration of rooting this one. And hopefully a good way to stop the OTA updates from Amazon. If anyone reads this and knows of anything I can do in the way of offering files from my now unrooted device (ADB still connects at user level), I'll be glad to help the cause.
On the bright side, most stuff I've done works fine without root. I didn't bother with Google Play because that hadn't been perfected and the 1 Mobile Market seems to work fine, as well as side loading.

If you feel like it you can downgrade your is now, there no utility to do it for you yet, but the images are there now so you can flash the older pre-rooted system and boot image from fastboot and it should do the trick, just figure out a way to keep it from updating as well.
Sent from my Amazon Kindle Fire HD using Tapatalk

Sorry about that
chalid said:
Same here ... any luck with re-rooting?
Click to expand...
Click to collapse
I didn't have spare time yet. I'm gonna try whenever, I get some gadget time.
Downgrading? It would be worthwhile if I knew the push server's IP; and it's clearly not any of those that have roamed the net. There is a stray IP that hasn't been identified yet. downgrading and keeping the system offline or under a low battery level is too anoying to be worthwhile IMHO.
But those who want may try to proxy their wifi connection through their computer, downgrade their device, leave it alone and check in their proxy logs to pinpoint which IP is uploading the update to their device. Re-downgrade, root, re-wall their device.I'll try this but I won't be able to do it within the next few days.
In the meantime, gotta go.

Couldn't you just leave an adb shell running on the PC while running a continuous netstat?
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Couldn't you just leave an adb shell running on the PC while running a continuous netstat?
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Oh... yes, obviously... *puts on dunce hat*
BTW: such a thing might not be necessary, as I read on the HDX forum this about said update:
"It now appears that renaming or removing com.amazon.dcp.apk stops Amazon ota updates. Ex. com.amazon.dcp.apk.old"

jonathanlyng said:
Oh... yes, obviously... *puts on dunce hat*
BTW: such a thing might not be necessary, as I read on the HDX forum this about said update:
"It now appears that renaming or removing com.amazon.dcp.apk stops Amazon ota updates. Ex. com.amazon.dcp.apk.old"
Click to expand...
Click to collapse
Yeah I've done something like that (on the 2012 model), but instead I used Android Firewall to block it from using Wi-Fi, no OTA updates now, been good for months
Seems the best way to prevent updates.

stunts513 said:
If you feel like it you can downgrade your is now, there no utility to do it for you yet, but the images are there now so you can flash the older pre-rooted system and boot image from fastboot and it should do the trick, just figure out a way to keep it from updating as well.
Click to expand...
Click to collapse
I presume the files you speak of are:
boot0block.zip img CRC = AA7AB538
stock-boot.zip img CRC = DF69BAA8
stock-recovery.zip img CRC = B95DDD44
stock-system.zip img CRC = CA6A9595
But NOT the boot0block.zip img because that's specific to the individual's device. I thought about doing this, but admittedly, was a little uncertain. I don't want to brick it. Basically, if I fastboot, I can push those images over safely? I presume I'd want to have my wireless turned off in advance of this operation, lest I end up exactly where I began with the thing wanting to update right away again.
Thanks much for the feedback!

kfsowi 11.3.2.1
hello people,
this is my first post here love the site, anyways anything yet that can be done about kfsowi on 11.3.2.1 yet can it be rooted or downgraded so i could get my root back.
thanks

SOLUTION!
http://forum.xda-developers.com/showthread.php?t=2544736&page=30#post_message_50878798
Courtesy of GranPC

Fastboot cable
where is the best and fastest way to get a fastboot cable online or in a store.
thank you

louiep said:
where is the best and fastest way to get a fastboot cable online or in a store.
thank you
Click to expand...
Click to collapse
From Amazon.COM though they are quite easy to make
Sent from my KFSOWI using xda app-developers app

Kingroot not working today?

Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root

positivehxcgo said:
Been toying with some development which has led to a few factory restarts... On the latest, Kingroot won't root
Click to expand...
Click to collapse
just try kingroot 4.1 (New Version)
has worked for me
LG Noah

Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?

jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
There is no official download for 4.5.4 yet, did you get it OTA ? If so, it's a big warning for everybody out there to disable the OTA updates!!!
Most likely Amazon fixed the Kingroot exploit, so I'd be actually surprised if 4.5.4 is rootable via the same approach as before.
Fellas, cherish the root that you got, and don't even think about updating !!!

Is there any way to downgrade to 4.5.3 without going through Amazon?

what is the command line to disable auto update ?
and does it auto update ?

alucard_xs said:
what is the command line to disable auto update ?
and does it auto update ?
Click to expand...
Click to collapse
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.

jmz said:
Code:
pm block com.amazon.otaverifier
You can also use my tool in OG dev to do it also.
Click to expand...
Click to collapse
Thanks so just adb to my device and this command line is enough ?

alucard_xs said:
Thanks so just adb to my device and this command line is enough ?
Click to expand...
Click to collapse
yes. I dunno if it gets reset on boot or not. I think it does.
My tool also does
Code:
mv /system/priv-app/DeviceSoftwareOTA.apk /system/priv-app/DeviceSoftwareOTA.apk.bak

Yeah it was an OTA update. Literally just as is was getting my laptop out to block them

otaverifier stays blocked with boot
jmz said:
yes. I dunno if it gets reset on boot or not. I think it does.
Click to expand...
Click to collapse
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.

DoLooper said:
Hi--Haven't been able to use your tool yet, but with the adb shell command you showed, otaverifier stays blocked through reboots. (Used Debloater by GatesJunior to confirm)
.
Click to expand...
Click to collapse
Ok. I wasn't sure.

what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?

alucard_xs said:
what is the exact command line ? wihing adb
"pm block com.amazon.otaverifier" is not ok for me, it tells me it's not a program in adb,
do I have to write adb in front of pm ?
Click to expand...
Click to collapse
Code:
adb shell pm block com.amazon.otaverifier

Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted

CrazyRach said:
Same thing happened to me today. A few days ago I put my kindle back to factory settings, turned it on today to start playing around with it, only to find it had started to update. Tried various ways to stop this from happening, but none succeeded and sadly my kindle has now updated itself which is so annoying.
Anyway, I presume there no way to roll it back, and I think I may just sell mine, even though its probably worth nothing now it cant be rooted
Click to expand...
Click to collapse
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time

jon_lad said:
Hi I've tried both Kingroot 4.0 and 4.1 but still having no luck rooting. Do they work with fire OS 4.5.4?
Click to expand...
Click to collapse
blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?

bibikalka said:
Wow, lucky you !!! Remember that you can always update manually, so the whole OTA pool is kind of useless.
But I wonder if there is a way to intercept Amazon's downgrade to one's Fire, and use it to downgrade other devices. There must be a moment when that downgrade bin sitting nicely in /cache, waiting to be copied ...
Perhaps, after a downgrade, you can try to recover the downgrade bin file from the system?
Click to expand...
Click to collapse
i actually had my device proxied via burpsuite while contacting support and them conducting the rollback but wasnt able to capture anything
one interesting thing i noticed while having the hd6 proxied is that the silk browser constantly tries to phone home to internal.amazon.com

blackwat3r said:
had this happen to one of my hd6's a few days ago because i forgot to block ota updates after rooting.
i was able to get downgraded back to 4.5.3 by amazon support, then i blocked ota updates, and contacted support again to have them move my device back to the normal ota update pool to keep the ability to update in the future if another root method appears that works against newer updates/kernels so then ota can be re-enabled at that point in time
Click to expand...
Click to collapse
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.

CrazyRach said:
What exactly do you say to customer support in order for them to roll your firmware back. I do find it very annoying there you can't opt out of ota. I mean even Apple give you the option.
Click to expand...
Click to collapse
apologies for the delayed response,
ive been dealing with a serious injury over the past few days.
i just went and told them that after updating to 4.5.4 i was having issues with the screen flickering and glitching, and system lags that persisted across factory resets.
if i have the time to try later im gonna see if i can get them to roll back one of my other devices while monitoring my entire network this time vs just proxying the device via burpsuite like i did before, then perhaps this may shed some light on the rollback/upgrade process

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 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.

FireOS 5.3.2.1 rollbacks

FYI - early indications 5.3.2.1 -> 5.3.1.0 rollbacks are problematic.
http://forum.xda-developers.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/post70052733

Here as well
http://forum.xda-developers.com/amazon-fire/general/fireos-5-3-2-arrived-t3500922/post70061090

Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files
Attached a scatter file I found online for the MTK8127 chipset, which fire has. No idea if it's right. SP tool for some reason won't keep the com port open...

kaysond said:
Bricked mine too. It shows up as a USB COM port and spits out "READYREADYREADYREADY" until it disconnects itself. I think this means it should be possible to restore 5.3.2.1 via sp flash tool (or maybe another serial loader). If we can get the right files
Attached a scatter file I found online for the MTK8127 chipset, which fire has. No idea if it's right. SP tool for some reason won't keep the com port open...
Click to expand...
Click to collapse
scatter files haven't worked, with any firmware versions
Sent from my sailfish using XDA Labs
---------- Post added at 05:50 PM ---------- Previous post was at 05:47 PM ----------
see http://forum.xda-developers.com/amazon-fire/development/unbrick-fire-7-5th-gen-downgrade-t3388747
Sent from my sailfish using XDA Labs

Yeah, I got the READYREADYREADYREADYREADY brick that I was expecting. Three tablets, got two of them rooted and OTA blocked, then had an emergency and the third apparently wasn't actually Off so it happily ****ed me.
There's never been a recovery from the READYREADYREADY firmware loader, I'd assume? Deciding if I should keep or toss this one. At least this ****'s cheap since we don't actually own it.

I just got an Amazon Fire and am new to this whole thing. Ultimately I'd love to root it, and install a different ROM. But in the short term, I'm just playing with installing the Play Store and turning off lock screen ads. Anyway, I just opened the package up today, and I let it update itself to 5.3.2.1 before I was aware that this might cause me trouble.
I did download the SuperTool here:
http://rootjunkysdl.com/files/?dir=SuperTool
I successfully installed the Play Store. I next tried disabling the lock screen ads, but the tool said I would need to root first. When I selected the option to do that, it asked for my FireOS version, but didn't give 5.3.2.1 as an option. So I'm afraid to go through the root process.
It sounds like downgrading to an earlier version will brick this. What about rooting it with a tool like the one I downloaded? Is that likely to cause trouble as well? Is there much I can do with this currently?

There's no known way (yet) to flash 5.3.2.1 back to something earlier, that's true (and some who got hit by a brick will confirm).
There's also no known success (yet) rooting this, but since KingRoot is evolving, there may be hope. There are multiple releases of KR around, and the cloud part (where the methods are kept) seem to be constantly changing - if you decide to keep the Fire, you may as well spend some time trying to get it rooted... KR versions 4.8.5, 4.9.2, 4.9.6 have been suggested; if you decide to use KR 5, you will have to remove it from the list of device administrators before replacing it with SuperSU - of course only if you're successful. We're all waiting for RootJunky to release a new SuperTool that will possibly automate this - ATM Nov 29 is still the latest version available...

Does the RootJunky SuperTool just use KR under the hood? I'll have to keep an eye on this. I don't mind getting my hands a bit messy on this, but I don't want to be blazing a new trail. I'm not experienced enough with it. I don't mind waiting a bit to get some hand holding.

komi_9 said:
Does the RootJunky SuperTool just use KR under the hood?
Click to expand...
Click to collapse
It does:
Code:
$ grep -ri kingroot.apk .
./1-Amazon-Fire-5th-gen.bat:files\adb.exe install -r apps\Kingroot.apk
./3-Amazon-Fire-5th-gen-linux-mac.sh: sudo $ADB install -r apps/Kingroot.apk
SuperTool is a zip file - and the "magic" is done in human-readable scripts (bat or bash). Firmware bin files are zips too. Open them in your fav archive tool, and inspect what's inside.
tl;dr: ST installs whatever you put into apps/Kingroot.apk - watch out for Spelnig when replacing the version coming with ST with another one you have dl'ed from apkmirror.

hope this works! Thanks for the good work guys

dmerillat said:
Yeah, I got the READYREADYREADYREADYREADY brick that I was expecting. Three tablets, got two of them rooted and OTA blocked, then had an emergency and the third apparently wasn't actually Off so it happily ****ed me.
There's never been a recovery from the READYREADYREADY firmware loader, I'd assume? Deciding if I should keep or toss this one. At least this ****'s cheap since we don't actually own it.
Click to expand...
Click to collapse
I'm fairly certain you can still write to the flash memory from that loader, just a matter of figuring out how. There's a python script that I think will work as long as you figure out what to write...

So..there is no way to Root or downgrade 5.3.2.1??

At this moment there isn't, sorry. But tools are not static, and there's even the chance that a future fireOS upgrade will be easier to root. You've got the choice to return your Fire while/if still on warranty or wait for better days to come.
Edit: I have read rumours that KingRoot would now be able to root 5.1.3 - this, of course, may be due to the usual number confusion (and 5.3.1 was meant).
On the other hand, the patch level of 5.3.2.1 might not include DirtyCow attacks yet:
Code:
ro.build.version.security_patch=2016-10-05
and indeed I saw RootJunky add some DC stuff to his download site... There might be something around the corner, indeed.

Confirm, even hardbrick if flash from 5.3.2.1 to 5.3.2

I just used the supertool on the same model Fire tab, on 12/27/16. Here's what I've learned:
1. Amazon will indeed remove offers/ads from the discounted Fire, without cost, if you ask.
2. Supertool uses KingRoot, as of my download date.
3. Supertool was not successful in removing ads, but did install the Play Store. It did prevent OTA updates, but the root didn't work for me, so I reloaded original firmware and of course it updated right away. Next time I would try to root after registering my Fire with Amazon.
4. It aopeared to me that the Supertool attempted a downgrade (5.1.1?) before rooting, so if downgrading will brick a device running 5.3.2.1, then I think the answer to the OP's question is "no".
related question: Knowing all the above, can I still re-try the Supertool option #1, and (re)install the Play Store and remove ads? (I bought 3 of them Amazon removed ads on 1 of them so far.))

rallison203 said:
I just used the supertool on the same model Fire tab, on 12/27/16. Here's what I've learned:
1. Amazon will indeed remove offers/ads from the discounted Fire, without cost, if you ask.
2. Supertool uses KingRoot, as of my download date.
3. Supertool was not successful in removing ads, but did install the Play Store. It did prevent OTA updates, but the root didn't work for me, so I reloaded original firmware and of course it updated right away. Next time I would try to root after registering my Fire with Amazon.
4. It aopeared to me that the Supertool attempted a downgrade (5.1.1?) before rooting, so if downgrading will brick a device running 5.3.2.1, then I think the answer to the OP's question is "no".
related question: Knowing all the above, can I still re-try the Supertool option #1, and (re)install the Play Store and remove ads? (I bought 3 of them Amazon removed ads on 1 of them so far.))
Click to expand...
Click to collapse
- SuperTool does not attempt a FireOS rollback
- 5.1.1 refers to underlying Android build
- Amazon will (reluctantly) remove ads from ONE device registered to an account
- KingRoot works best if device is NOT registered with Amazon
- at present KingRoot is not effective against FireOS 5.3.2+

Thanks for responding, sorry for any misinformation, I'm quite a noob. So - if the supertool doesnt rollback, do you think I'd have trouble retrying the ad removal tool while running 5.3.2.1. ?

rallison203 said:
Thanks for responding, sorry for any misinformation, I'm quite a noob. So - if the supertool doesnt rollback, do you think I'd have trouble retrying the ad removal tool while running 5.3.2.1. ?
Click to expand...
Click to collapse
Don't see any significant risks with rerunning but also don't think it will be fully effective on an unrooted device.

Is this probably the best thread to follow if I want to be notified when it's possible to root 5.3.2.1?

valzi said:
Is this probably the best thread to follow if I want to be notified when it's possible to root 5.3.2.1?
Click to expand...
Click to collapse
I hope so, I'm certainly subscribed