Hello,
I was rooted running OS 4.2.2 and everything was great until one day I came home from dinner, got out my kindle and saw the dreaded message: "OS Updated to 4.5.4." I forgot to disable OTA! I can't believe I made such a silly mistake, but now I'm wondering if I can rollback 4.5.4 to 3.2.8, and then update to 4.5.2 and root. Does this only work for 4.5.3, or is it possible on 4.5.4? If it is possible, can someone link me to instructions?
Thanks,
Zman8881
Update
I talked to Arun from Amazon support who said it's not possible. He did, however, credit my Amazon account with $5.00 and tell me that an update resolving the inability to rollback will be available soon (EDIT: he later said 3-4 months, nevermind...) , meaning hope for myself and all of you out there who made the same mistake that I did.
EDIT: Is there any backdoor way to downgrade that someone can think of? I have no use for this device without a root, so I'm willing to risk bricking it.
-Zman8881
Zman8881 said:
Hello,
I was rooted running OS 4.2.2 and everything was great until one day I came home from dinner, got out my kindle and saw the dreaded message: "OS Updated to 4.5.4." I forgot to disable OTA! I can't believe I made such a silly mistake, but now I'm wondering if I can rollback 4.5.4 to 3.2.8, and then update to 4.5.2 and root. Does this only work for 4.5.3, or is it possible on 4.5.4? If it is possible, can someone link me to instructions?
Thanks,
Zman8881
Click to expand...
Click to collapse
The 'classic' 3.2.8 rollback method has reportedly worked for some. There does not appear to be any harm in trying; your device will either accept/recognize the file or not. Obviously follow all the usual cautions if you are successful (eg: keep WiFi off at all times!).
Zman8881 said:
I talked to Arun from Amazon support who said it's not possible. He did, however, credit my Amazon account with $5.00 and tell me that an update resolving the inability to rollback will be available soon (EDIT: he later said 3-4 months, nevermind...) , meaning hope for myself and all of you out there who made the same mistake that I did.
EDIT: Is there any backdoor way to downgrade that someone can think of? I have no use for this device without a root, so I'm willing to risk bricking it.
-Zman8881
Click to expand...
Click to collapse
I highly doubt Amazon is addressing the rollback issue. Why would they do that? The tech had a good laugh at your expense. Best path (aside from attempting a 3.2.8 rollback) is to enjoy or shelve your device until a root exploit becomes available for 4.5.4. You will need to keep it off the network as Amazon will undoubtedly push new updates that will be root resistant. And no - there is no known (or at least well communicated) way to root 4.5.4 as of now.
Davey126 said:
The 'classic' 3.2.8 rollback method has reportedly worked for some. There does not appear to be any harm in trying; your device will either accept/recognize the file or not. Obviously follow all the usual cautions if you are successful (eg: keep WiFi off at all times!).
I highly doubt Amazon is addressing the rollback issue. Why would they do that? The tech had a good laugh at your expense. Best path (aside from attempting a 3.2.8 rollback) is to enjoy or shelve your device until a root exploit becomes available for 4.5.4. You will need to keep it off the network as Amazon will undoubtedly push new updates that will be root resistant. And no - there is no known (or at least well communicated) way to root 4.5.4 as of now.
Click to expand...
Click to collapse
Can you by chance link me to instructions and/or the link for the 3.2.8 rollback method?
Okay, so here is the rollback file, but I urge you to proceed with caution. If you let Amazon update this build, you are ensured a brick. You need to use the hdx toolkit to block OTA on *.3.2.8.
http://forum.xda-developers.com/showthread.php?p=59220996
Good luck.
Zman8881 said:
Can you by chance link me to instructions and/or the link for the 3.2.8 rollback method?
Click to expand...
Click to collapse
Relevant thread here. Basic procedure is described in the first post. Take care to insure your device can not connect after rolling back to 3.2.8. Keep the device in airplane mode and/or disable wifi. Depending on the method used to root 3.2.8 and 4.5.2 you may need to enable network connectivity momentarily during the rooting process (typically no longer than 30-60 sec). Be sure to turn it off immediately after. There is no need to block OTA on 3.2.8 if your intent is to immediately upgrade to 4.5.2. That said, if you do receive an OTA update on 3.2.8 your device will brick (unrecoverable). The consequences on 4.5.2 aren't as grave: you'll simply be updated to 4.5.4 and have to start the whole process over again. Ultimately you will need to block OTA once on 4.5.2 but that can only be done after obtaining root.
BTW - once on 4.5.2 (rooted) you now have an option to run a custom version of Nexus 7 which presents a much different interface than FireOS. Risks are low and you can always return to FireOS if you don't care for Nexus. There are several distinct advantages to Nexus including full access to Google Services (including play store) and no worries about blocking OTA and/or receiving an update that breaks root. Everything works except LTE; that's being worked on now. More info here.
Good luck.
One Last Question...
Davey126 said:
Relevant thread here. Basic procedure is described in the first post. Take care to insure your device can not connect after rolling back to 3.2.8. Keep the device in airplane mode and/or disable wifi. Depending on the method used to root 3.2.8 and 4.5.2 you may need to enable network connectivity momentarily during the rooting process (typically no longer than 30-60 sec). Be sure to turn it off immediately after. There is no need to block OTA on 3.2.8 if your intent is to immediately upgrade to 4.5.2. That said, if you do receive an OTA update on 3.2.8 your device will brick (unrecoverable). The consequences on 4.5.2 aren't as grave: you'll simply be updated to 4.5.4 and have to start the whole process over again. Ultimately you will need to block OTA once on 4.5.2 but that can only be done after obtaining root.
BTW - once on 4.5.2 (rooted) you now have an option to run a custom version of Nexus 7 which presents a much different interface than FireOS. Risks are low and you can always return to FireOS if you don't care for Nexus. There are several distinct advantages to Nexus including full access to Google Services (including play store) and no worries about blocking OTA and/or receiving an update that breaks root. Everything works except LTE; that's being worked on now. More info here.
Good luck.
Click to expand...
Click to collapse
Thanks for all of the help... Just one last question. What is the name of the internal storage folder on the kindle that I should put the file in? Sorry, I'm new to Android. Believe it or not, I won my Kindle Fire from an arcade machine! Sorry again.
-Zman8881
Zman8881 said:
Thanks for all of the help... Just one last question. What is the name of the internal storage folder on the kindle that I should put the file in? Sorry, I'm new to Android. Believe it or not, I won my Kindle Fire from an arcade machine! Sorry again.
-Zman8881
Click to expand...
Click to collapse
Hey - congrats on the win! The rollback file goes in the root of sdcard when viewed from a tool such as ES File Explorer. If you have tethered your Kindle drop it into "internal storage" which is the base folder when viewed from Windows. After the file is in place reboot. If nothing seems to happen (give it 5-10 min) use the 'check for updates' function from within FireOS (located somewhere under settings). At some point the file will either be recognized/processed, recognized/rejected or ignored all together. Post back your results.
Although it has probably been burned into your brain be sure to do whatever is necessary to prevent network access if your Kindle rolls back to 3.2.8.
Davey126 said:
Hey - congrats on the win! The rollback file goes in the root of sdcard when viewed from a tool such as ES File Explorer. If you have tethered your Kindle drop it into "internal storage" which is the base folder when viewed from Windows. After the file is in place reboot. If nothing seems to happen (give it 5-10 min) use the 'check for updates' function from within FireOS (located somewhere under settings). At some point the file will either be recognized/processed, recognized/rejected or ignored all together. Post back your results.
Although it has probably been burned into your brain be sure to do whatever is necessary to prevent network access if your Kindle rolls back to 3.2.8.
Click to expand...
Click to collapse
I thought I did it, but after I hit update, I was stopped by an error message telling me that an update isn't possible because the update I'm trying to install is an earlier version than what I have on my device. Oh well, I guess it will be a long wait until someone finds a root exploit for 4.5.4. Thanks for all of your help!
-Zman8881
Zman8881 said:
I thought I did it, but after I hit update, I was stopped by an error message telling me that an update isn't possible because the update I'm trying to install is an earlier version than what I have on my device. Oh well, I guess it will be a long wait until someone finds a root exploit for 4.5.4. Thanks for all of your help!
-Zman8881
Click to expand...
Click to collapse
Sorry it didn't work. There is a way around that message but you need root to make the change. Catch 22.
The wait may not be that long. Fingers crossed
Couple more questions
Davey126 said:
Relevant thread here. Basic procedure is described in the first post. Take care to insure your device can not connect after rolling back to 3.2.8. Keep the device in airplane mode and/or disable wifi. Depending on the method used to root 3.2.8 and 4.5.2 you may need to enable network connectivity momentarily during the rooting process (typically no longer than 30-60 sec). Be sure to turn it off immediately after. There is no need to block OTA on 3.2.8 if your intent is to immediately upgrade to 4.5.2. That said, if you do receive an OTA update on 3.2.8 your device will brick (unrecoverable). The consequences on 4.5.2 aren't as grave: you'll simply be updated to 4.5.4 and have to start the whole process over again. Ultimately you will need to block OTA once on 4.5.2 but that can only be done after obtaining root.
BTW - once on 4.5.2 (rooted) you now have an option to run a custom version of Nexus 7 which presents a much different interface than FireOS. Risks are low and you can always return to FireOS if you don't care for Nexus. There are several distinct advantages to Nexus including full access to Google Services (including play store) and no worries about blocking OTA and/or receiving an update that breaks root. Everything works except LTE; that's being worked on now. More info here.
Good luck.
Click to expand...
Click to collapse
Hey, Davey126, sorry to post here again quite a while after it's relevant, but I had a couple more questions.
You state here that you just have to make sure the wifi is not enabled, so OTAs aren't pushed. But another user (below) seems to push that I'll have to use the HDX Toolkit--which I can't seem to figure out how to actually use; is just disabling the wifi enough to keep it from bricking from an immediate OTA after the rollback?
lekofraggle said:
Okay, so here is the rollback file, but I urge you to proceed with caution. If you let Amazon update this build, you are ensured a brick. You need to use the hdx toolkit to block OTA on *.3.2.8.
http://forum.xda-developers.com/showthread.php?p=59220996
Good luck.
Click to expand...
Click to collapse
I haven't actually tried to get the update to be recognized yet, because I want everything to be sorted out question wise before diving in, but let's say it works and I get my kindle to roll back. How would I then get it up to 4.5.2?
Sorry for the questions! I just can't seem to find the answers anywhere else.
Rvby1 said:
Hey, Davey126, sorry to post here again quite a while after it's relevant, but I had a couple more questions.
You state here that you just have to make sure the wifi is not enabled, so OTAs aren't pushed. But another user (below) seems to push that I'll have to use the HDX Toolkit--which I can't seem to figure out how to actually use; is just disabling the wifi enough to keep it from bricking from an immediate OTA after the rollback?
I haven't actually tried to get the update to be recognized yet, because I want everything to be sorted out question wise before diving in, but let's say it works and I get my kindle to roll back. How would I then get it up to 4.5.2?
Sorry for the questions! I just can't seem to find the answers anywhere else.
Click to expand...
Click to collapse
Good questions; I appreciate you looked around before posting. If your intent is to rollback to 3.2.8 and then immediately upgraded to 4.5.2 there is no need to block OTA updates on 3.2.8 provide WiFi remains off (as an added precaution I would keep your device in Airplane mode). However, you'll need to enable WiFi for a few seconds while rooting. While that's not enough time to download a complete update a file fragment could potentially cause complications. Hence an OTA block could be beneficial. Really depends how fast you work and whether you can detect an incoming OTA update. You'll need to remove the block before upgrading to 4.5.2.
HDX Toolkit is a tethered solution. It runs on a Windows host and requires USB debugging to be enabled. Commands are issued to your device via the tether. Nothing needs to be installed on your device. You will also want a working tether to copy the 4.5.2 bin and possibly other files to your device when it's time to upgrade. Some folks load everything on the device in advance but I prefer to copy files as they are needed.
Davey126 said:
Good questions; I appreciate you looked around before posting. If your intent is to rollback to 3.2.8 and then immediately upgraded to 4.5.2 there is no need to block OTA updates on 3.2.8 provide WiFi remains off (as an added precaution I would keep your device in Airplane mode). However, you'll need to enable WiFi for a few seconds while rooting. While that's not enough time to download a complete update a file fragment could potentially cause complications. Hence an OTA block could be beneficial. Really depends how fast you work and whether you can detect an incoming OTA update. You'll need to remove the block before upgrading to 4.5.2.
HDX Toolkit is a tethered solution. It runs on a Windows host and requires USB debugging to be enabled. Commands are issued to your device via the tether. Nothing needs to be installed on your device. You will also want a working tether to copy the 4.5.2 bin and possibly other files to your device when it's time to upgrade. Some folks load everything on the device in advance but I prefer to copy files as they are needed.
Click to expand...
Click to collapse
Gotcha!
Actually, thanks a bunch for not only explaining the tool a bit, but prompting me to go take another look at it. Turns out I was downloading the wrong batch of files--everything seems to be working now. You just tether your kindle and tell it to block OTA, right? Don't have to worry about version number or anything like that?
So with upgrading to 4.5.2, is the process pretty well the same as with downgrading to 3.8.2? If so, where can I find the update file?
Thanks a million!
Rvby1 said:
Gotcha!
Actually, thanks a bunch for not only explaining the tool a bit, but prompting me to go take another look at it. Turns out I was downloading the wrong batch of files--everything seems to be working now. You just tether your kindle and tell it to block OTA, right? Don't have to worry about version number or anything like that?
So with upgrading to 4.5.2, is the process pretty well the same as with downgrading to 3.8.2? If so, where can I find the update file?
Thanks a million!
Click to expand...
Click to collapse
HDX Toolkit only works on FireOS v3 (3.2.8 and below). After rolling back to 3.2.8 tether your Kindle and use the toolkit to block OTA. Once OTA is blocked you can enable WiFi and use towelroot to root. Gather any other files you may need on your device, disable WiFi (also recommend 'airplane mode') and then use the toolkit to reenable OTA (under '5 More'). Move the 4.5.2 bin (here) to the root of sdcard and check for updates. Once on 4.5.2 you'll need to root and block OTA once again. Check the forums for the appropriate tools and method for FireOS v4. Kingroot and renaming DeviceSoftwareOTA.apk seem to be the most reliable.
Davey126 said:
HDX Toolkit only works on FireOS v3 (3.2.8 and below). After rolling back to 3.2.8 tether your Kindle and use the toolkit to block OTA. Once OTA is blocked you can enable WiFi and use towelroot to root. Gather any other files you may need on your device, disable WiFi (also recommend 'airplane mode') and then use the toolkit to reenable OTA (under '5 More'). Move the 4.5.2 bin (here) to the root of sdcard and check for updates. Once on 4.5.2 you'll need to root and block OTA once again. Check the forums for the appropriate tools and method for FireOS v4. Kingroot and renaming DeviceSoftwareOTA.apk seem to be the most reliable.
Click to expand...
Click to collapse
Okay, thanks so much for all the information! I actually just got my kindle to rollback to 3.2.8, but this brought up two more questions for me.
With the HDX Toolkit, it's asking me to grant root access on the device, which I can't do yet until it blocks OTAs; despite this message, it seems to go through and, after displaying the same message 5 times, state that OTAs are blocked. Is there anyway to safely check that they've actually been blocked? Also, is doing it twice okay? The message seemed less than assuring, so I did it again, but it displayed a different message 5 times on the second attempt.
Lastly, I want to root 3.2.8 and /then/ update to 4.5.2, right?
Thanks so much!
Rvby1 said:
Okay, thanks so much for all the information! I actually just got my kindle to rollback to 3.2.8, but this brought up two more questions for me.
With the HDX Toolkit, it's asking me to grant root access on the device, which I can't do yet until it blocks OTAs; despite this message, it seems to go through and, after displaying the same message 5 times, state that OTAs are blocked. Is there anyway to safely check that they've actually been blocked? Also, is doing it twice okay? The message seemed less than assuring, so I did it again, but it displayed a different message 5 times on the second attempt.
Lastly, I want to root 3.2.8 and /then/ update to 4.5.2, right?
Thanks so much!
Click to expand...
Click to collapse
The OTA blocker in HDX Toolkit is very comprehensive (probably overkill). Some actions require root, others do not. I suspect OTA is effectively blocked but there is no way to conclusively test. Suggest rooting with towelroot (you'll need to toggle WiFi momentarily) and then run the OTA blocker again. Multiple executions should have no adverse consequences. While unlikely to happen watch for any signs of a download in progress. If you see it turn off WiFi and post back for further instructions.
Remember to undo the OTA block after the 4.5.2 bin is in place; otherwise your device won't 'see' it.
Technically you don't absolutely have to root 3.2.8 to upgrade to 4.5.2 but I find it much easier to move files around and take corrective action if something goes wrong. Downside is root gives you unfettered access to everything; navigate carefully.
Davey126 said:
The OTA blocker in HDX Toolkit is very comprehensive (probably overkill). Some actions require root, others do not. I suspect OTA is effectively blocked but there is no way to conclusively test. Suggest rooting with towelroot (you'll need to toggle WiFi momentarily) and then run the OTA blocker again. Multiple executions should have no adverse consequences. While unlikely to happen watch for any signs of a download in progress. If you see it turn off WiFi and post back for further instructions.
Remember to undo the OTA block after the 4.5.2 bin is in place; otherwise your device won't 'see' it.
Technically you don't absolutely have to root 3.2.8 to upgrade to 4.5.2 but I find it much easier to move files around and take corrective action if something goes wrong. Downside is root gives you unfettered access to everything; navigate carefully.
Click to expand...
Click to collapse
Gotcha!
Alright. I think this is the final question before I go through with everything: on rooting with Towelroot, can I just use the HDX Toolkit for that? It says it only works up to 13/14.3.2.6 and below, so I just want to be safe.
Rvby1 said:
Gotcha!
Alright. I think this is the final question before I go through with everything: on rooting with Towelroot, can I just use the HDX Toolkit for that? It says it only works up to 13/14.3.2.6 and below, so I just want to be safe.
Click to expand...
Click to collapse
Neither Towelroot nor HDX toolkit has changed much (if at all) in the past 12-18 months. The version range was likely current when coded. It can't hurt to try; it will either work or not with no side effects. If it doesn't work head off to towelroot.com for the official variant. Obviously this means keeping WiFi on for a longer period.
Davey126 said:
Neither Towelroot nor HDX toolkit has changed much (if at all) in the past 12-18 months. The version range was likely current when coded. It can't hurt to try; it will either work or not with no side effects. If it doesn't work head off to towelroot.com for the official variant. Obviously this means keeping WiFi on for a longer period.
Click to expand...
Click to collapse
Got Towelroot to go through, despite a weird error the first execution. I didn't seem to have to enable wifi at all, believe it or not, and HDXTools said I was properly rooted.
I've been searching for the past hour or so, but I can't for the life of me find anything that clearly states how to go about rooting 4.5.2 once I get my kindle updated. I've found the supposed root file through the rollback thread, but I can't find out how to actually use it. As for Kingroot, I can only seem to find threads for 4.5.3. Can you impart any knowledge to me about this?
Also, in trying to find the solution, I found another post by you:
Davey126 said:
You'll need to follow the guide linked by ggow (here) which is rather technical and requires a Windows host to complete (there are variants for Linux and OS X) plus a fair bit of technical knowledge. There are no canned tools, videos or step-by-step tutorials. Unlocking is not risky (failed attempts won't harm your device) but it can be a frustrating experience.
If unlocking feels uncomfortable you can do a controlled upgrade to FireOS 4.5.2 and then install Safestrap v4 followed by Nexus v4 or CM11. However, you will permanently loose the ability to unlock your bootloader which is the key to running roms like Nexus and CM in 'native' mode. Unlocking also offers greater recovery capability should something go wrong.
There is also the 'do nothing' option which leaves you with a perfectly serviceable device running a very nice Nexus rom (Jelly Bean 4.2 based).
Click to expand...
Click to collapse
From all that I've read, it seems like we can only go back as far as 3.2.8 now. Is it too late to unlock the bootloader? Sorry for bringing an entirely different thread here, haha--I just want to make sure I get everything done in one fell swoop.
Rvby1 said:
Got Towelroot to go through, despite a weird error the first execution. I didn't seem to have to enable wifi at all, believe it or not, and HDXTools said I was properly rooted.
Click to expand...
Click to collapse
Surprised about that but glad it worked! Perhaps the version built into HDX Toolkit contains the bits & pieces that normally require online access.
Rvby1 said:
I've been searching for the past hour or so, but I can't for the life of me find anything that clearly states how to go about rooting 4.5.2 once I get my kindle updated. I've found the supposed root file through the rollback thread, but I can't find out how to actually use it. As for Kingroot, I can only seem to find threads for 4.5.3. Can you impart any knowledge to me about this?
Click to expand...
Click to collapse
Kingroot works great on 4.5.2 and is far easer than the alternative methods. Some question the origins of Kingroot (China) but the tool is widely used across a variety of platforms. Personally I could care less where it comes from as long as the reputation is solid. Sharing this in case you have a different perspective.
Rvby1 said:
Also, in trying to find the solution, I found another post by you:
[removed - see previous post for content]
From all that I've read, it seems like we can only go back as far as 3.2.8 now. Is it too late to unlock the bootloader? Sorry for bringing an entirely different thread here, haha--I just want to make sure I get everything done in one fell swoop.
Click to expand...
Click to collapse
As your start point was FireOS v4 your device was never eligible for bootloader unlocking. More specifically, Amazon fixed the vulnerability that allowed bootloader signature forging in 3.2.4. Clever folks figured out how to roll back to 3.2.3 up through 3.2.6. Starting with 3.2.7 Amazon became aggressive about blocking rollbacks. Any attempt to do so will blow an efuse which is equivalent to a brick. It's always possible another vulnerability will be discovered in higher firmware levels that permits bootloader unlocking. Don't hold your breath.
Related
Hello,
I have this Kindle Fire HDX with Fire O.S. 4.5.3
I can't see the firmware version in settings, any alternative in order to find it?.
What would the basic steps to follow in order to be able to install a ROM?
I'm not asking for instruction for each step, I can search for that, I'm just hoping to get a comprehensive step by step.
I'd guess I need to root first, but in order to root I need to have certain OS and/or firmware version, therefore I'll need to rollback?
Then what would be next?
peterpayne said:
Hello,
I have this Kindle Fire HDX with Fire O.S. 4.5.3
I can't see the firmware version in settings, any alternative in order to find it?.
What would the basic steps to follow in order to be able to install a ROM?
I'm not asking for instruction for each step, I can search for that, I'm just hoping to get a comprehensive step by step.
I'd guess I need to root first, but in order to root I need to have certain OS and/or firmware version, therefore I'll need to rollback?
Then what would be next?
Click to expand...
Click to collapse
I found how to rollback to version 13.3.2.8, and did the towelroot root... with the KFHDX ToolKit v0.95
But it seems there's no way currently to install a bootloader unless I have 13.3.1.0 and I haven't seen if there's a way to rollback further.
If I find a way, I'll post again I guess...
I for one have many of the same questions you are asking. I honestly have done a decent amount of research on this, having successfully rooted and installed custom ROMs and recovery on my HTC One M8, I feel I have the basics down.
So if you learn more please share, and I also would like to know how you found your firmware info?
, kk,
Sent from my SM-G355HN using XDA Free mobile app
I just got an HDX 7 (3rd gen) today for free, been mucking around with it for the past few hours (it's a piece of crap, really) and kinda pissed at Amazon (nothing new for me considering).
Here's what I've gleaned so far in a few hours of research... and please understand that since the OP said he's already on 4.5.3 this info is specifically related to what can be done with an HDX running 4.5.3.
What you can't do: If you're on 4.5.3 forget doing anything at all - you can't root it, you can't install custom ROMs (no Safestrap use at all), you can't unlock the bootloader, you can't do a damned thing, period. Well, you could use it like Amazon wants you to use it: a consumption device overall but that's not why we're here at XDA basically so there goes that ridiculous idea. (note this information applies to 4.5.3 specifically and nothing else)
What you can do: The only thing you CAN do if you're on 4.5.3 is to roll it back to 3.2.8 using the 3.2.8 firmware bin copied to the storage root (you can find that yourself someplace, I did but I don't have the particular link to that particular thread at the moment).
Once you're on 3.2.8 you CAN root it (I don't have the thread for that at the moment, I think the HDX Toolkit or whatever can do it using Towelroot or something). At that point you can stick with 3.2.8 and do whatever (disable OTA's, etc) - I believe you can install Safestrap as well and then install that Nexus ROM I see mentioned but that's Jelly Bean based and CM11 and CM12/12.1 cannot be used presently - the best you'll ever be able to do with 3.2.8 is running the Nexus ROM as I understand things (I could be wrong on that, someone else can chime in as needed).
Another thing you can do once you're on 3.2.8: you CAN update it to 4.5.2 using the 4.5.2 firmware bin copied to the storage root (again, you'll have to find this yourself) and 4.5.2 CAN be rooted but that's where you're stuck because you can't install Safestrap or any custom ROMs at all (not even the Nexus one), but you can kill off the OTA updates and stay with 4.5.2 as long as you want because if you don't it will update to 4.5.3 again the first chance it gets.
I didn't know all this about 6 hours ago, I got the HDX and it had 3.0.5 on it - I didn't know not to update it - well, yes, I did, but I forgot about the WiFi thing and as soon as I realized that the update had downloaded it was already too late - as soon as I rebooted it installed and I couldn't stop it from happening so that ruined my ability to do the bootloader unlock and potentially get CM12.1 on it. My fault, my mistake, but that's what happens sometimes.
As it stands I don't even want this piece of crap to be honest, I find it useless overall unless you can do custom ROMs 'cause Amazon and FireOS just flat out suck for me - if I can't do what I want with the device then I can't use it, basically, so it's listed on craigslist for sale at the moment and I hope someone grabs it quick.
That's the gist of what I've learned in the past few hours with respect to this HDX device and doing an awful lot of reading and research not only here at XDA but MobileRead and some other places.
Hope this helps...
br0adband said:
I just got an HDX 7 (3rd gen) today for free, been mucking around with it for the past few hours (it's a piece of crap, really) and kinda pissed at Amazon (nothing new for me considering).
Here's what I've gleaned so far in a few hours of research... and please understand that since the OP said he's already on 4.5.3 this info is specifically related to what can be done with an HDX running 4.5.3.
What you can't do: If you're on 4.5.3 forget doing anything at all - you can't root it, you can't install custom ROMs (no Safestrap use at all), you can't unlock the bootloader, you can't do a damned thing, period. Well, you could use it like Amazon wants you to use it: a consumption device overall but that's not why we're here at XDA basically so there goes that ridiculous idea. (note this information applies to 4.5.3 specifically and nothing else)
What you can do: The only thing you CAN do if you're on 4.5.3 is to roll it back to 3.2.8 using the 3.2.8 firmware bin copied to the storage root (you can find that yourself someplace, I did but I don't have the particular link to that particular thread at the moment).
Once you're on 3.2.8 you CAN root it (I don't have the thread for that at the moment, I think the HDX Toolkit or whatever can do it using Towelroot or something). At that point you can stick with 3.2.8 and do whatever (disable OTA's, etc) - I believe you can install Safestrap as well and then install that Nexus ROM I see mentioned but that's Jelly Bean based and CM11 and CM12/12.1 cannot be used presently - the best you'll ever be able to do with 3.2.8 is running the Nexus ROM as I understand things (I could be wrong on that, someone else can chime in as needed).
Another thing you can do once you're on 3.2.8: you CAN update it to 4.5.2 using the 4.5.2 firmware bin copied to the storage root (again, you'll have to find this yourself) and 4.5.2 CAN be rooted but that's where you're stuck because you can't install Safestrap or any custom ROMs at all (not even the Nexus one), but you can kill off the OTA updates and stay with 4.5.2 as long as you want because if you don't it will update to 4.5.3 again the first chance it gets.
I didn't know all this about 6 hours ago, I got the HDX and it had 3.0.5 on it - I didn't know not to update it - well, yes, I did, but I forgot about the WiFi thing and as soon as I realized that the update had downloaded it was already too late - as soon as I rebooted it installed and I couldn't stop it from happening so that ruined my ability to do the bootloader unlock and potentially get CM12.1 on it. My fault, my mistake, but that's what happens sometimes.
As it stands I don't even want this piece of crap to be honest, I find it useless overall unless you can do custom ROMs 'cause Amazon and FireOS just flat out suck for me - if I can't do what I want with the device then I can't use it, basically, so it's listed on craigslist for sale at the moment and I hope someone grabs it quick.
That's the gist of what I've learned in the past few hours with respect to this HDX device and doing an awful lot of reading and research not only here at XDA but MobileRead and some other places.
Hope this helps...
Click to expand...
Click to collapse
This is a reasonably accurate accounting of the current state for those starting at 4.5.3. A minor footnote is the ability to install Google Play Services on 4.5.2 once rooted. That makes the device a bit more intersting as most apps in the Play Store will happily run on Fire 4.5.2. However, there is both effort and risk going this route. A safer alternative is to utilize an alternative market such as 1mobile to secure free (and some paid) content offered in the Play Store.
br0adband said:
I just got an HDX 7 (3rd gen) today for free, been mucking around with it for the past few hours (it's a piece of crap, really) and kinda pissed at Amazon (nothing new for me considering).
Here's what I've gleaned so far in a few hours of research... and please understand that since the OP said he's already on 4.5.3 this info is specifically related to what can be done with an HDX running 4.5.3.
What you can't do: If you're on 4.5.3 forget doing anything at all - you can't root it, you can't install custom ROMs (no Safestrap use at all), you can't unlock the bootloader, you can't do a damned thing, period. Well, you could use it like Amazon wants you to use it: a consumption device overall but that's not why we're here at XDA basically so there goes that ridiculous idea. (note this information applies to 4.5.3 specifically and nothing else)
What you can do: The only thing you CAN do if you're on 4.5.3 is to roll it back to 3.2.8 using the 3.2.8 firmware bin copied to the storage root (you can find that yourself someplace, I did but I don't have the particular link to that particular thread at the moment).
Once you're on 3.2.8 you CAN root it (I don't have the thread for that at the moment, I think the HDX Toolkit or whatever can do it using Towelroot or something). At that point you can stick with 3.2.8 and do whatever (disable OTA's, etc) - I believe you can install Safestrap as well and then install that Nexus ROM I see mentioned but that's Jelly Bean based and CM11 and CM12/12.1 cannot be used presently - the best you'll ever be able to do with 3.2.8 is running the Nexus ROM as I understand things (I could be wrong on that, someone else can chime in as needed).
Another thing you can do once you're on 3.2.8: you CAN update it to 4.5.2 using the 4.5.2 firmware bin copied to the storage root (again, you'll have to find this yourself) and 4.5.2 CAN be rooted but that's where you're stuck because you can't install Safestrap or any custom ROMs at all (not even the Nexus one), but you can kill off the OTA updates and stay with 4.5.2 as long as you want because if you don't it will update to 4.5.3 again the first chance it gets.
I didn't know all this about 6 hours ago, I got the HDX and it had 3.0.5 on it - I didn't know not to update it - well, yes, I did, but I forgot about the WiFi thing and as soon as I realized that the update had downloaded it was already too late - as soon as I rebooted it installed and I couldn't stop it from happening so that ruined my ability to do the bootloader unlock and potentially get CM12.1 on it. My fault, my mistake, but that's what happens sometimes.
As it stands I don't even want this piece of crap to be honest, I find it useless overall unless you can do custom ROMs 'cause Amazon and FireOS just flat out suck for me - if I can't do what I want with the device then I can't use it, basically, so it's listed on craigslist for sale at the moment and I hope someone grabs it quick.
That's the gist of what I've learned in the past few hours with respect to this HDX device and doing an awful lot of reading and research not only here at XDA but MobileRead and some other places.
Hope this helps...
Click to expand...
Click to collapse
Thanks, but at what point can you actually unlock the bootloader? If you have 4.5.2 (never updated to 4.5.3), are you able to downgrade far enough to unlock the bootloader, or what? Is 4.5.3 essentially the cutoff point?
3.2.7 was the cutoff point. Sorry.
Sent from my KFTHWI using Tapatalk
I can't seem to find any working root for my kindle and i'm need help to root this darn thing.
I really want to Get rid of amazon and go get Android kit-cat and use the Google play. Your answer will be thanked if your answer works.
i heard about roll backing my kindle fire hdx but i need more info on how to get into the internal storage folder.
My kindle runs Fire os 4.5.4
I have no idea how to find the firmware...
As of now, it cannot be done yet. Sorry.
lekofraggle said:
As of now, it cannot be done yet. Sorry.
Click to expand...
Click to collapse
Oh ok..
Its been a long while though.
I guess amazon won the war against rooting...:crying:
This is a brand new update. So, it actually has not been that long. There has been a root found for almost every other release including 4.5.3, but I think they patched it with this new release.
lekofraggle said:
This is a brand new update. So, it actually has not been that long. There has been a root found for almost every other release including 4.5.3, but I think they patched it with this new release.
Click to expand...
Click to collapse
4.5.3? You sure because i Looked everywhere for answers only to find out the roots does not work... But i hope they find a root.
By the way can you reply to me when they have a root out for my 4.5.4 Update. make sure to give me the link. That will be really Nice.
You should be reading through the boards yourself. If you had, you would know they found a root option in China which worked on 4.5.3. It did take a while to find, but they found one.
I can't just hotlink to a file or post because this device is so fickle, you need to understand what you are getting into when you root. I have been on Android since 2.0 and I have never seen a device so easy to ruin and difficult to fix. Sorry.
That Chinese root also doesn't work 100% of the time. It didn't work on my Saturn(HDX 8.9). That said, I seemed to be the only one who had trouble with it.
The update for 4.5.4 came out in the last week.
XxD34THxX said:
That Chinese root also doesn't work 100% of the time. It didn't work on my Saturn(HDX 8.9). That said, I seemed to be the only one who had trouble with it.
The update for 4.5.4 came out in the last week.
Click to expand...
Click to collapse
I actually did get root to work with Kingroot, prebuiltgmscore apk downloaded separately here and minimal google bundle here
I have a 8.9 HDX 4th generation also called Saturn.
Did Kingroot work with 4.5.4?? If so, I will try it again.
XxD34THxX said:
Did Kingroot work with 4.5.4?? If so, I will try it again.
Click to expand...
Click to collapse
No, my device is a kindle fire hdx 7, it runs 4.5.4 and it seems like kingroot does not work.
When it fails it gives me this Email Icon with a check mark
and then a number 13096
i even checked it with a root checker and it said no Root access
So that's the error screen. Hope they find a root for 4.5.4 Soon!
XxD34THxX said:
Did Kingroot work with 4.5.4?? If so, I will try it again.
Click to expand...
Click to collapse
I'm on 4.5.3 sorry....
There is a way: downgrade to 3.5.8 (there is a thread for it) then upgrade to 4.5.3 then root it with kingroot.
herophuong93 said:
There is a way: downgrade to 3.5.8 (there is a thread for it) then upgrade to 4.5.3 then root it with kingroot.
Click to expand...
Click to collapse
Use great caution if going this route. There are numerous reports of bricked devices following 3.2.8 rollback apparently due to an immediate ota push of 4.5.4 which renders the device unusable. To date there is no known recovery method. If you opt to downgrade you must either block the ota mechanism via HDX Toolkit (other methods do not work) or take steps to prevent network connectivity until 4.5.2 is successfully installed.
wonder
wonder if there is a way to downgrade back to is 4.5.3
Braders2345 said:
wonder if there is a way to downgrade back to is 4.5.3
Click to expand...
Click to collapse
Not at this time. Nor is there a benefit relative to 4.5.2. If you are on 4.5.4 you can roll back to 3.2.8 then upgrade to 4.5.2. However, there are risks involved (unrecoverable brick); procedures must be followed exactly.
Davey126 said:
Not at this time. Nor is there a benefit relative to 4.5.2. If you are on 4.5.4 you can roll back to 3.2.8 then upgrade to 4.5.2. However, there are risks involved (unrecoverable brick); procedures must be followed exactly.
Click to expand...
Click to collapse
Davey, I am willing to give downgrade a shot, I just need to know the correct link to use. Will you please post the correct link to downgrade, I have a 4th Gen HDX 8.9 Saturn....just a FYI....Thanks
chargedbird said:
Davey, I am willing to give downgrade a shot, I just need to know the correct link to use. Will you please post the correct link to downgrade, I have a 4th Gen HDX 8.9 Saturn....just a FYI....Thanks
Click to expand...
Click to collapse
Sorry - Saturn devices can not be rolled back. The OTAs used are specific to Apollo and Thor. Amazon never offered rollbacks for Saturn thus no one was able to capture the rollback file. The internals are sufficiently different that you'd likely build a brick if you tried to 'force' an Apollo update. Apologize if I missed a prior reference to Saturn and falsely got your hopes up.
Heres the deal I have a kindle fire HDX 8.9" (Apollo) On firmware version 14.3.2.4_user_324002120 and was wondering if it is possible to unlock the bootloader.
Montisaquadeis said:
Heres the deal I have a kindle fire HDX 8.9" (Apollo) On firmware version 14.3.2.4_user_324002120 and was wondering if it is possible to unlock the bootloader.
Click to expand...
Click to collapse
Yes. Procedure involves a rollback to FireOS 14.3.1.x, installation of TWRP recovery, updating the native bootloader and then working through the unlock procedure (tedious for some). Once complete you can flash several HDX compatible roms including Nexus v4, CM11, two lollipop variants (CM12, SlipLP) or stick with FireOS provided you don't want to install gapps.
If needed I can post an outline and link to contributor supplied guides in a day or so ... or perhaps someone will jump in with the gory details. Or you also can browse through the forums. I'd wait for more info as it's pretty easy to brick your device (no recovery) if you go off script. In no case should you tweak build.prop or flash different versions of FireOS without specific instructions.
"If needed I can post an outline and link to contributor supplied guides in a day or so..."
This would be highly appreciated! Thanks!
fabische said:
"If needed I can post an outline and link to contributor supplied guides in a day or so..."
This would be highly appreciated! Thanks!
Click to expand...
Click to collapse
With 3.2.4 you could use the rollback images provided by @ggow. Check page 2 of this thread (page 1 is about 3.2.5/3.2.6 users, who can NOT use the rollback images!).
This would require rooting with HDX Toolkit and installing Safestrap 3.75. With Safestrap v3.7x note that factory reset means standard wipe only! Do NOT open advanced wipe menu, and especially do NOT wipe system! Keep WLAN off/flightmode active to avoid getting updated by Amazon, (re-)root and disable OTA via HDX Toolkit after downgrade, then flash TWRP, update 3.2.3.2 bootloader via TWRP, unlock bootloader and flash ROM of your choice - be sure do create a backup of your Fire OS in TWRP and move it to your PC before you flash any custom ROM!
Read the info, and ask first if you have questions, i.e. before you brick your HDX.
Cl4ncy said:
With 3.2.4 you could use the rollback images provided by @ggow. Check page 2 of this thread (page 1 is about 3.2.5/3.2.6 users, who can NOT use the rollback images!).
This would require rooting with HDX Toolkit and installing Safestrap 3.75. With Safestrap v3.7x note that factory reset means standard wipe only! Do NOT open advanced wipe menu, and especially do NOT wipe system! Keep WLAN off/flightmode active to avoid getting updated by Amazon, (re-)root and disable OTA via HDX Toolkit after downgrade, then flash TWRP, update 3.2.3.2 bootloader via TWRP, unlock bootloader and flash ROM of your choice - be sure do create a backup of your Fire OS in TWRP and move it to your PC before you flash any custom ROM!
Read the info, and ask first if you have questions, i.e. before you brick your HDX.
Click to expand...
Click to collapse
cheers mate! Just wonder how I can rollback my Apollo from 14.4.5.2 to 14.3.2.4 which is required to unlock the bootloader.
All the instructions that I can find state that you cannot rollback below 14.3.2.8....
fabische said:
cheers mate! Just wonder how I can rollback my Apollo from 14.4.5.2 to 14.3.2.4 which is required to unlock the bootloader.
All the instructions that I can find state that you cannot rollback below 14.3.2.8....
Click to expand...
Click to collapse
You can't. Any attempt to rollback below 3.2.8 will brick your device (anti-rollback protection). There is no way to unlock the bootloader on a device that has been upgraded (or began life) above 3.2.6.
However, with 4.5.2 you can root, install Safestrap v4 and then have a choice of CM11 or Nexus v4. Post back if you need assistance.
Davey126 said:
You can't. Any attempt to rollback below 3.2.8 will brick your device (anti-rollback protection). There is no way to unlock the bootloader on a device that has been upgraded (or began life) above 3.2.6.
However, with 4.5.2 you can root, install Safestrap v4 and then have a choice of CM11 or Nexus v4. Post back if you need assistance.
Click to expand...
Click to collapse
Thanks for the quick reply! Basically, I have constant issues with GAPPS running on my rooted 4.5.2 Apollo. For the last six months I have simply blocked any updates of Google Play Services (+chattr command). This was fine for a while, however, meanwhile apps like Google+ & Photos are working less than satisfying. I have updated Google Play Services today which eventually killed my Google Play Store. I managed to get back to the previous so-so state because I had backed up the Google Apps files with Titanium backup. Though my "simple" aim remains to have a working Gapps package on my system. However, the safestrap method, for some strange reason, is currently no option: when I install safestrap 4.1 and try to enter recovery the system goes into a black screen.
To cut a long story short my longterm plan now is to rollback to 3.2.8 again, upgrade to 4.5.2., root and reinstall Gapps manually (or is there a quicker option?). Possibly, Safestrap will work again then too.
Does this make any sense to you?
cheers!
fabische said:
THowever, the safestrap method, for some strange reason, is currently no option: when I install safestrap 4.1 and try to enter recovery the system goes into a black screen.
To cut a long story short my longterm plan now is to rollback to 3.2.8 again, upgrade to 4.5.2., root and reinstall Gapps manually (or is there a quicker option?). Possibly, Safestrap will work again then too.
Does this make any sense to you?
cheers!
Click to expand...
Click to collapse
You are in a tricky situation. If Safestrap v4 won't boot the contents in one of the native Amazon partitions (boot, recovery or system) may be damaged. You need some of these components to rollback or upgrade. If attempted outcomes can range from refusing to process the rollback/update file to an unrecoverable brick. You sometimes see this in a pure stock device. Working fine then bricks after receiving an OTA.
Thoughts:
- it is possible to 'refresh' the recovery partition with Flashify but you will need to find a compatible 4.5.2 recovery image
- suggest you upgrade to 4.5.5 first. Based on limited feedback the risk of a minor FireOS v4 upgrade is less than rolling back.
- if the upgrade is successful you can then attempt a rollback to 3.2.8 followed by upgrade to 4.5.2 (keep WiFi off!!)
- you should uninstall GAaps before upgrading/downgrading.
- there is increased risk if you previously changed permissions on system files to block OTA, etc.
- you will need to reenable OTA (hopefully just a file rename) to up/downgrade.
- I believe Safestrap v4 will install and run correctly if you successfully rollback and upgrade to 4.5.2.
Davey126 said:
You are in a tricky situation. If Safestrap v4 won't boot the contents in one of the native Amazon partitions (boot, recovery or system) may be damaged. You need some of these components to rollback or upgrade. If attempted outcomes can range from refusing to process the rollback/update file to an unrecoverable brick. You sometimes see this in a pure stock device. Working fine then bricks after receiving an OTA.
Thoughts:
- it is possible to 'refresh' the recovery partition with Flashify but you will need to find a compatible 4.5.2 recovery image
- suggest you upgrade to 4.5.5 first. Based on limited feedback the risk of a minor FireOS v4 upgrade is less than rolling back.
- if the upgrade is successful you can then attempt a rollback to 3.2.8 followed by upgrade to 4.5.2 (keep WiFi off!!)
- you should uninstall GAaps before upgrading/downgrading.
- there is increased risk if you previously changed permissions on system files to block OTA, etc.
- you will need to reenable OTA (hopefully just a file rename) to up/downgrade.
- I believe Safestrap v4 will install and run correctly if you successfully rollback and upgrade to 4.5.2.
Click to expand...
Click to collapse
Thanks, davey126. Before I set off for this next adventure: what is your guess that we will see an unlocked bootloader for current fire OS versions in the future? (this might save a lot of trouble)
fabische said:
Thanks, davey126. Before I set off for this next adventure: what is your guess that we will see an unlocked bootloader for current fire OS versions in the future? (this might save a lot of trouble)
Click to expand...
Click to collapse
Close to (effectively) zero. A new vulnerability would have to be discovered followed by an exploit to leverage it. 3rd gen devices have been discontinued; we don't even have root for 4th gen devices. I suspect few resources are being expended on this device. All the (Amazon) excitement surrounds the new $50 USD tablets that have been rooted and have a selection of custom roms. HDX is quickly becoming a beautiful dinosaur. Hi specs are out, cheap is in.
Davey126 said:
You are in a tricky situation. If Safestrap v4 won't boot the contents in one of the native Amazon partitions (boot, recovery or system) may be damaged. You need some of these components to rollback or upgrade. If attempted outcomes can range from refusing to process the rollback/update file to an unrecoverable brick. You sometimes see this in a pure stock device. Working fine then bricks after receiving an OTA.
Thoughts:
- it is possible to 'refresh' the recovery partition with Flashify but you will need to find a compatible 4.5.2 recovery image
- suggest you upgrade to 4.5.5 first. Based on limited feedback the risk of a minor FireOS v4 upgrade is less than rolling back.
- if the upgrade is successful you can then attempt a rollback to 3.2.8 followed by upgrade to 4.5.2 (keep WiFi off!!)
- you should uninstall GAaps before upgrading/downgrading.
- there is increased risk if you previously changed permissions on system files to block OTA, etc.
- you will need to reenable OTA (hopefully just a file rename) to up/downgrade.
- I believe Safestrap v4 will install and run correctly if you successfully rollback and upgrade to 4.5.2.
Click to expand...
Click to collapse
Am I in serious trouble now?
I have followed to downgrade path by first updating (my 3rd Gen Apollo) from 4.5.2 to 4.5.4 and then to 4.5.5. Next was the 3.2.8-downgrade file:
mod-update-kindle-apollo-14.3.2.8_user_714328020.bin
However, starting this downgrade always results in a "Last update failed" message.
It turns out that there are two different 4.5.5 update files.
update-kindle-22.4.5.5_user_455001820
update-kindle-14.4.5.5_user_455001320
I have updated to the more recent "455001820" which actually refuses the downgrade to 14.3.2.8.
Seems I am stuck now?
Can I at least root update-kindle-22.4.5.5_user_455001820?
Thanks!
UPDATE:
Stuck where I was, I allowed my apollo to go online again. It found a newer 4.5.5 Fire os update and I let it download and run through. It now seems that I am on the latest version of 4.5.5. However, with this setup I am still unable to downgrade to 3.2.8. Every attempt to do so delivers a "Last update failed" message...
AFTERTHOUGHT
Could it make any difference if I factory reset the device (i.e. with regards to the downgrading process)? I have also noticed that I did not uninstall GAPPs before updating Fire OS to 4.5.5. However, I did manage to uninstall Google Apps and then also deleted google related files by searching with ES Explorer.
fabische said:
Am I in serious trouble now?
I have followed to downgrade path by first updating (my 3rd Gen Apollo) from 4.5.2 to 4.5.4 and then to 4.5.5. Next was the 3.2.8-downgrade file:
mod-update-kindle-apollo-14.3.2.8_user_714328020.bin
However, starting this downgrade always results in a "Last update failed" message.
It turns out that there are two different 4.5.5 update files.
update-kindle-22.4.5.5_user_455001820
update-kindle-14.4.5.5_user_455001320
I have updated to the more recent "455001820" which actually refuses the downgrade to 14.3.2.8.
Seems I am stuck now?
Can I at least root update-kindle-22.4.5.5_user_455001820?
Thanks!
UPDATE:
Stuck where I was, I allowed my apollo to go online again. It found a newer 4.5.5 Fire os update and I let it download and run through. It now seems that I am on the latest version of 4.5.5. However, with this setup I am still unable to downgrade to 3.2.8. Every attempt to do so delivers a "Last update failed" message...
AFTERTHOUGHT
Could it make any difference if I factory reset the device (i.e. with regards to the downgrading process)? I have also noticed that I did not uninstall GAPPs before updating Fire OS to 4.5.5. However, I did manage to uninstall Google Apps and then also deleted google related files by searching with ES Explorer.
Click to expand...
Click to collapse
I do not think the different subversion of 14.4.5.5 are significant in your situation although good to know they exist.
Yes - I would try a factory reset as others have reported success when update (rollback) files fail to process. This is one of the few cases where benefits of a factory reset outweigh risks. Make sure usb debugging is enabled as it may prove beneficial if your device has trouble restarting after the reset.
Davey126 said:
I do not think the different subversion of 14.4.5.5 are significant in your situation although good to know they exist.
Yes - I would try a factory reset as others have reported success when update (rollback) files fail to process. This is one of the few cases where benefits of a factory reset outweigh risks. Make sure usb debugging is enabled as it may prove beneficial if your device has trouble restarting after the reset.
Click to expand...
Click to collapse
Thanks, davey126. I have made factory reset on my device. I will try to downgrade later today. With regard to unlocking the 4.5.5. bootloader there has been an interesting development: a couple of days ago somebody managed to crack the 4.5.5 bootloader - unfortunately for the Kindle HD 7 (3rd Gen, 2013) only. What is your guess: could this prove useful for the HDX? Could this become a Safestrap alternative? Is it worth the wait?
http://forum.xda-developers.com/kin...ment/unlock-kfsowi-bootloader-unlock-t3262770
fabische said:
Thanks, davey126. I have made factory reset on my device. I will try to downgrade later today. With regard to unlocking the 4.5.5. bootloader there has been an interesting development: a couple of days ago somebody managed to crack the 4.5.5 bootloader - unfortunately for the Kindle HD 7 (3rd Gen, 2013) only. What is your guess: could this prove useful for the HDX? Could this become a Safestrap alternative? Is it worth the wait?
http://forum.xda-developers.com/kin...ment/unlock-kfsowi-bootloader-unlock-t3262770
Click to expand...
Click to collapse
Aside from sharing a generational identifier the two tabs have little in common. It's possible there is some similar code in the bootloader...but that seems unlikely. The real issue imo is the number people working on HDX vs HD variants. Only a few talented devs (I'm not one of them) tinkering with the former which is now discontinued.
Installing Safestrap does not decisively close the door to leveraging future BL exploits should one become available. I also think we may see some progress on a LP/MM rom for SS over time. Fingers crossed!
Davey126 said:
Aside from sharing a generational identifier the two tabs have little in common. It's possible there is some similar code in the bootloader...but that seems unlikely. The real issue imo is the number people working on HDX vs HD variants. Only a few talented devs (I'm not one of them) tinkering with the former which is now discontinued.
Installing Safestrap does not decisively close the door to leveraging future BL exploits should one become available. I also think we may see some progress on a LP/MM rom for SS over time. Fingers crossed!
Click to expand...
Click to collapse
Thanks again, Davey126. All is well now.
It all turned out as you predicted: downgrading 3.2.8 was possible after I made a factory reset on 4.5.5.
The rest was easy: upgrading back to 4.5.2 and rooting.
Your second prediction also proved correct: Safestrap 4.0.1 was not working properly on my fire os stock ROM. However, by going through this whole down- and upgrading process again Safestrap couldn't run smoother as it runs now. Finally, a working Safestrap opened the road (Hallelujah!!) to GET RID OF FIRE OS ONCE AND FOR ALL. I am now on rooted CM11 with GAPPS and starting to explore a new, liberated tablet! One more reason to celebrate!
fabische said:
Thanks again, Davey126. All is well now.
It all turned out as you predicted: downgrading 3.2.8 was possible after I made a factory reset on 4.5.5.
The rest was easy: upgrading back to 4.5.2 and rooting.
Your second prediction also proved correct: Safestrap 4.0.1 was not working properly on my fire os stock ROM. However, by going through this whole down- and upgrading process again Safestrap couldn't run smoother as it runs now. Finally, a working Safestrap opened the road (Hallelujah!!) to GET RID OF FIRE OS ONCE AND FOR ALL. I am now on rooted CM11 with GAPPS and starting to explore a new, liberated tablet! One more reason to celebrate!
Click to expand...
Click to collapse
Excellent - glad everything went as hoped. I suggest you glance through previous posts to make sure everything is configured to give you the best experience.
Enjoy your liberated HDX.
Or do we have another way to unlock bootloader without root?
Is downgrading still possible for out of warranty device?
kkcheong said:
Or do we have another way to unlock bootloader without root?
Is downgrading still possible for out of warranty device?
Click to expand...
Click to collapse
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Thanks. I thought only 4.5.5.1 supported based on first page of the downgrade thread. Upon reading, seems like work on 4.5.5.2 too.
Davey126 said:
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Click to expand...
Click to collapse
Davey126 said:
- FireOS 4.5.5.2 can be downgraded to 3.2.8 and rooted w/towelroot (procedure)
- once rooted bootloader unlock proceeds as described here
- it is *essential* WiFi be disabled while on 3.2.8 except for the few seconds needed for rooting
- recommend engaging airplane/flight mode as an additional precaution
- failure to observe the above cautions will (with great certainty) result in an unrecoverable brick if an OTA update is downloaded/installed
Click to expand...
Click to collapse
Wait are you saying that towelroot works with 4.5.5.2? Or do you mean that towelroot works after using the downgrade file?
bigboolean said:
Wait are you saying that towelroot works with 4.5.5.2? Or do you mean that towelroot works after using the downgrade file?
Click to expand...
Click to collapse
TowelRoot only works with FireOS v3. However, it is more reliable than KingRoot on FireOS v4 so worth the downgrade effort IMO.
Davey126 said:
TowelRoot only works with FireOS v3. However, it is more reliable than KingRoot on FireOS v4 so worth the downgrade effort IMO.
Click to expand...
Click to collapse
Can you explain the differences and reliability issues with Kingroot FireOS V4?
Archangel1183 said:
Can you explain the differences and reliability issues with Kingroot FireOS V4?
Click to expand...
Click to collapse
- TowelRoot typically roots within seconds; KingRoot can take many iterations
- KingRoot modifies various system files and installs additional components (crapware) without permission
- KingRoot actively resists uninstallation with each revision being increasingly difficult to remove
- TowelRoot is only effective against FireOS 3.x (Android 4.2 based); Kingroot works on a much wider range of Android builds and at present is the only reliable root solution for FireOS v4 and v5
I just rooted my Kindle HDX 7 firmware version 4.5.5.2 with Kingroot v. 4.9.2. You just have to be "VERY PERSISTENT" because it root will fail over and over again but eventually the firmware will give up and let Kingroot root your tablet. I took me 3 hours to root mine so be persistent. Now I'm working on blocking Amazon firmware updates.
RMNDGGG said:
... but eventually the firmware will give up and let Kingroot root your tablet. I took me 3 hours to root mine so be persistent. Now I'm working on blocking Amazon firmware updates.
Click to expand...
Click to collapse
It's not Amazon's firmware somehow resisting rooting; KingRoot's vulnerability detection and exploit matching algorithm is (generously) unsophisticated. Not much better than trial and error with a short fuse.
Also consider unlocking the bootloader and installing a custom ROM (ie: pure Android) to fully liberate your device. You'll probably want to do this anyhow to remove the malware like detritus KingRoot leaves behind.
RMNDGGG, I just installed kingroot 5.0.1 after reading your message and ran it. It looks like my hdx rooted successfully. I double checked it with a root checker and it also said that it's rooted.
Now I need to install Android. I'll search for instructions, but if anyone has a link, can you shoot it over? Thanks
Archangel1183 said:
RMNDGGG, I just installed kingroot 5.0.1 after reading your message and ran it. It looks like my hdx rooted successfully. I double checked it with a root checker and it also said that it's rooted.
Now I need to install Android. I'll search for instructions, but if anyone has a link, can you shoot it over? Thanks
Click to expand...
Click to collapse
You will need to unlock the bootloader first: https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
I renamed 2 OTAupdated files to prevent it from auto updating and turned it off. When I turned it back on, I got a message saying "Updating applications" and it loaded on to a black screen where the home screen should be. I restarted it several times and now it just gets stuck on the "Kindle Fire" loading screen.
Archangel1183 said:
I renamed 2 OTAupdated files to prevent it from auto updating and turned it off. When I turned it back on, I got a message saying "Updating applications" and it loaded on to a black screen where the home screen should be. I restarted it several times and now it just gets stuck on the "Kindle Fire" loading screen.
Click to expand...
Click to collapse
Likely reamed the wrong file(s). If you haven't unlocked the bootloader it's pretty much game over. You can try a 'factory reset' from the stock recovery menu but that rarely fixes system problems. Stock recovery does not offer the ability to reload or repair FireOS. Sorry ...
Yeah, I think I did one too many files. The post I read only mentioned one file but I found two with similar names. I'll try a factory reset later. Thanks, Davey.
I used the Kindle Fire Unbrick Utility V1.1 that I found on the forums. I tried a couple different options offered in the tool and it seemed like none of them were doing anything. They kept saying "Device not found". I knew the computer was detecting it because I installed the drivers a couple weeks back and it was showing "Fire" in device manager. I was done with the tool and was going to use this unbricking method (forum.xda-developers.com/showthread.php?t=2793253), when my kindle suddenly went passed the boot screen into my lock screen. I unlocked it and again got a black screen. I wanted to get into ES File explorer to rename the 2nd file back to the original name, but I couldn't see any app icons. I accidentally swiped up from the bottom and a menu with app icons popped up. I was then able to get into ES File explorer and rename the file. I exited the app and wooot.... no more black screen.
For anyone reading this..... DO NOT Rename DeviceSoftwareOTAContracts.apk or you will get a black home screen without any apps. I renamed DeviceSoftwareOTA.apk to DeviceSoftwareOTAold (no apk) and it's working fine. So far my Kindle fire HDX 7 is still rooted.
Someone on another forum posted that this version of Kingroot, apparently updated 1/22/17 (v 5.0.3), works for the last update of Fire OS on Thor (4.5.5.2). Has anyone tried this out? I want it to be true, because I lost root on the last update, but I don't want to brick my device or open myself up to any other issues if it's some sort of trojan. At some point I was going to try a rollback and then root, but I would much prefer to use a one and done apk if possible. Can anyone confirm that this works?
Vanb85 said:
Someone on another forum posted that this version of Kingroot, apparently updated 1/22/17 (v 5.0.3), works for the last update of Fire OS on Thor (4.5.5.2). Has anyone tried this out? I want it to be true, because I lost root on the last update, but I don't want to brick my device or open myself up to any other issues if it's some sort of trojan. At some point I was going to try a rollback and then root, but I would much prefer to use a one and done apk if possible. Can anyone confirm that this works?
Click to expand...
Click to collapse
All KingRoot builds use the same cloud database to scan for vunerabalities and match up with known exploits. The various KingRoot clients may sequence tests differently and clutter your device with varying 'gifts'... especially the v5 series. I would go the rollback and root path. It's safe, easy and fast. Only caveat is the device must maintain network isolation (WiFi off; airplane mode engaged) while the device is on FireOS 3.2.8. If the device takes an OTA update while on 3.2.8 it will brick with no possible recovery.
Davey126 said:
All KingRoot builds use the same cloud database to scan for vunerabalities and match up with known exploits. The various KingRoot clients may sequence tests differently and clutter your device with varying 'gifts'... especially the v5 series. I would go the rollback and root path. It's safe, easy and fast. Only caveat is the device must maintain network isolation (WiFi off; airplane mode engaged) while the device is on FireOS 3.2.8. If the device takes an OTA update while on 3.2.8 it will brick with no possible recovery.
Click to expand...
Click to collapse
KingRoot is basically how I was planning on rooting my device anyway. Is there any real advantage, in terms of "safety" with applying KingRoot after I've done the rollback as opposed to before doing one? And can KingRoot even be don on 4.5.5.2? I've been told ad naseum that this version of Fire OS cannot be rooted, but it looks as though it can now. If I'm going to be taking a risk with KingRoot anyway, wouldn't it be better to do so without the rollback and possible bricking of my device? Has there been any confirmation that KingRoot can in fact root 4.5.5.2 now?
eta: And just to be clear, this is KingRoot that we're talking about, right, not KingORoot?
Yes, I used Kingroot 4.8.1 to root 4.5.5.2. It took a couple of retries, but eventually it was successful.
Vanb85 said:
KingRoot is basically how I was planning on rooting my device anyway. Is there any real advantage, in terms of "safety" with applying KingRoot after I've done the rollback as opposed to before doing one? And can KingRoot even be don on 4.5.5.2? I've been told ad naseum that this version of Fire OS cannot be rooted, but it looks as though it can now. If I'm going to be taking a risk with KingRoot anyway, wouldn't it be better to do so without the rollback and possible bricking of my device? Has there been any confirmation that KingRoot can in fact root 4.5.5.2 now?
eta: And just to be clear, this is KingRoot that we're talking about, right, not KingORoot?
Click to expand...
Click to collapse
KingRoot is borderline malware but gets the job done (eventually; often takes multiple attempts) and carries no additional liabilities if the device is going to be immediately unlocked and wiped. 4.5.X -> 3.2.8 rollback is not unduly risky if network isolation is maintained on 3.2.8. TowelRoot is the tool of choice on FireOS v3; fast and reliable. Ultimately the choice is yours. Good luck.
Davey126 said:
KingRoot is borderline malware but gets the job done (eventually; often takes multiple attempts) and carries no additional liabilities if the device is going to be immediately unlocked and wiped. 4.5.X -> 3.2.8 rollback is not unduly risky if network isolation is maintained on 3.2.8. TowelRoot is the tool of choice on FireOS v3; fast and reliable. Ultimately the choice is yours. Good luck.
Click to expand...
Click to collapse
Another quick newbie question. Does KingRoot have to stay on your device in order to maintain root access? Can I use it to root and then uninstall it and still maintain root access? Is that what you mean by "unlocked and wiped?"
Vanb85 said:
Another quick newbie question. Does KingRoot have to stay on your device in order to maintain root access? Can I use it to root and then uninstall it and still maintain root access? Is that what you mean by "unlocked and wiped?"
Click to expand...
Click to collapse
Uninstalling KingRoot (KingUser) via conventional means also removes root. There are methods for transitioning a different root manager (eg: SuperSU) if you plan to stay on FireOS. SuperSume is one such tool. Does not seem to be effective against more recent KingRoot builds which actively resist removal.
Unlocking refers to the bootloader; wiping is a recommended prerequisite for cleanly replacing FireOS with a custom ROM. Wiping also removes KimgRoot detritus.
Anatinae said:
Yes, I used Kingroot 4.8.1 to root 4.5.5.2. It took a couple of retries, but eventually it was successful.
Click to expand...
Click to collapse
Have you tried installing SuperSu or another root manager as a replacement since rooting with KingRoot?
I unlocked the bootloader and installed LineageOS. Using the default root included with the latest unofficial build.
Anatinae said:
I unlocked the bootloader and installed LineageOS. Using the default root included with the latest unofficial build.
Click to expand...
Click to collapse
I see. So you replaced KingRoot with the default root manager that came with the LineageOS build?
Update: I did install KingRoot. And I installed the Google Play Store after that. I was unable to replace KingRoot with SuperSu. So, I uninstalled KingRoot, and of course, it took root access with it. But I got what I wanted, for the most part, which was to be able to install the Google Play Store on my HDX. It appears to be working fine even without root access. I would have preferred to keep root access, but I don't really trust KingRoot enough to keep it on my device. Now, I just need to block updates so Amazon doesn't mess with GPS.
Can anyone tell me if it's okay that I moved the DeviceSystemOTA.apk to another folder? It wouldn't allow me to rename it, so I cut and paste it into another folder to rename it with the intention of moving it back to the system folder. I realized after it wouldn't allow me to put the file back that I can't do anything with the system folder (can't rename things, can't add files) now that I don't have root. It only let me remove the file. Is it okay that the file is just not in the system folder? I was essentially going to make it inoperable by renaming it and removing "apk" from it anyway. @Davey126?
Vanb85 said:
Can anyone tell me if it's okay that I moved the DeviceSystemOTA.apk to another folder? It wouldn't allow me to rename it, so I cut and paste it into another folder to rename it with the intention of moving it back to the system folder. I realized after it wouldn't allow me to put the file back that I can't do anything with the system folder (can't rename things, can't add files) now that I don't have root. It only let me remove the file. Is it okay that the file is just not in the system folder? I was essentially going to make it inoperable by renaming it and removing "apk" from it anyway. @Davey126?
Click to expand...
Click to collapse
Should not be a problem provided you remember where it resides should you wish to enable OTA updates at a later time. Note there are other system files containing the characters "OTA" that should not be moved or renamed.
Davey126 said:
Should not be a problem provided you remember where it resides should you wish to enable OTA updates at a later time. Note there are other system files containing the characters "OTA" that should not be moved or renamed.
Click to expand...
Click to collapse
Good to know. Yeah, it was just the one file. Thanks so much for your help.
Took delivery of a couple of HDX tablets today. I got a chance to try a "Replace Kingroot with SuperSU script" I modded for the HDX. The script was taken from supertools which also used chainfires root.sh script.
Anyway it seems to have worked perfect, I've two HDX on 4.5.5.2 with SuperSU on them instead of Kingroot 4.8.2 which was used in the script. That kingroot version rooted on the 2nd attempt on both tablets, both factory reset and unregistered.
Files attached feel free to modify as required.
any ideas
so im rooted , ota are turned off, and safe strap is installed and here comes the but... it lets me install recovery but when i hit reboot to recovery it reboots and then powers up like normall?? it doesnt let me go into a recovery mode??? o and 4.5.5.2 is what is running
thumper_ss said:
so im rooted , ota are turned off, and safe strap is installed and here comes the but... it lets me install recovery but when i hit reboot to recovery it reboots and then powers up like normall?? it doesnt let me go into a recovery mode??? o and 4.5.5.2 is what is running
Click to expand...
Click to collapse
Please don't cross post; responded in other thread.