Trouble going to 3.2.5 from 3.0.8.. help diagnosing? - Kindle Fire HDX 7" & 8.9" Q&A, Help & Troubleshoot

I've looked and tried what other people tried in threads, but:
Still getting "Error" on the flashing screen when doing the upgrade to 3.2.5.
Verified that it is unrooted, framework removed, ota updates re-enabled, safestrap is removed. Also factory reset and cleared caches. However whether I download the 3.2.5 upgrade file or I let the kindle download it, it will verify the file ok, start the upgrade, reboot into the regular upgrade/flashing screen, go a little ways on the progress bar, and then Error, and eventually reboot back into the regular OS.
So something else is causing it to hang up, is there anything I missed on getting it back in condition ready to take the 3.2.5 upgrade? ANy help appreciated> Thanks.

PaulieP said:
I've looked and tried what other people tried in threads, but:
Still getting "Error" on the flashing screen when doing the upgrade to 3.2.5.
Verified that it is unrooted, framework removed, ota updates re-enabled, safestrap is removed. Also factory reset and cleared caches. However whether I download the 3.2.5 upgrade file or I let the kindle download it, it will verify the file ok, start the upgrade, reboot into the regular upgrade/flashing screen, go a little ways on the progress bar, and then Error, and eventually reboot back into the regular OS.
So something else is causing it to hang up, is there anything I missed on getting it back in condition ready to take the 3.2.5 upgrade? ANy help appreciated> Thanks.
Click to expand...
Click to collapse
Why do you want to update to 3.2.5 anyway? Versions below 3.2.4 (i.e. 3.2.3.2 and lower) give you the chance to install TWRP recovery (a lot better than Safestrap) and to unlock the bootloader. Both would open the wonderland of HDX ROMs for you.
So I'd suggest to install TWRP (must remove Safestrap first!), update to 3.2.3.2 (can and should be done from TWRP, may be just update the bootloader to 3.2.3.2), unlock the bootloader and flash Nexus, CM11 or CM12 (note that CM12 is NOT Safestrap compatible, read the installation notes and requirements carefully!).
If in doubt, ask first, i.e. before you brick your HDX.

Related

[Q] 13.3.2.1 - Using device and securing Custom ROM possibility

Hi Guys,
i just got my HDX (7" - Thor) this week and was trying to get the Thor GAPPS ROM by Cpasjuste to work. Having found nothing specific for FireOS version 13.3.2.1 i went ahead and tried my luck with the "old" version of the ROM (thor-gapps-13.3.0.0-v2.zip).
Unfortunately i couldn't get it to work and am back to factory defaults. Which is good, since it's not a brick. So now i'm trying to play it safe and wait for the developer's magic to happen
i'm eager to play around with the device, but don't want to risk losing my chances of running a custom ROM in the future. i already own the first Kindle Fire and wouldn't want to miss the near stock Android on that.
So, finally, my question:
If i use the HDX Toolkit to root and disable OTA updates, i assume it will be safe to use the device until the bootloader gets unlocked or some other magic happens. Am i correct with this assumption?
Edit1 [2014-07-09 - 21:21]: sorry for the soonish edit, but i just prepared the device in case someone confirms, that it is more or less safe to use it with OTA disabled.
Upon disabling OTA, i get a few rows of "killed" messages in the HDX toolkit. When i first disabled OTA i saw that some services were being disabled or uninstalled. Is "killed" a confirmation that the components are already killed? i have already factory resetted, as i cannot find a way to do a full wipe. The result is the same.
Thanks in advance.
umm
kobayashimaru said:
Hi Guys,
i just got my HDX (7" - Thor) this week and was trying to get the Thor GAPPS ROM by Cpasjuste to work. Having found nothing specific for FireOS version 13.3.2.1 i went ahead and tried my luck with the "old" version of the ROM (thor-gapps-13.3.0.0-v2.zip).
Unfortunately i couldn't get it to work and am back to factory defaults. Which is good, since it's not a brick. So now i'm trying to play it safe and wait for the developer's magic to happen
i'm eager to play around with the device, but don't want to risk losing my chances of running a custom ROM in the future. i already own the first Kindle Fire and wouldn't want to miss the near stock Android on that.
So, finally, my question:
If i use the HDX Toolkit to root and disable OTA updates, i assume it will be safe to use the device until the bootloader gets unlocked or some other magic happens. Am i correct with this assumption?
Edit1 [2014-07-09 - 21:21]: sorry for the soonish edit, but i just prepared the device in case someone confirms, that it is more or less safe to use it with OTA disabled.
Upon disabling OTA, i get a few rows of "killed" messages in the HDX toolkit. When i first disabled OTA i saw that some services were being disabled or uninstalled. Is "killed" a confirmation that the components are already killed? i have already factory resetted, as i cannot find a way to do a full wipe. The result is the same.
Thanks in advance.
Click to expand...
Click to collapse
Never factory reset stock slot if you have run the OTA blocker the utility also has a eNAble option for the OTA blocker always uninstall xposed framework and modules before factory reset also .. Always returning the unit to as close to factory as you can before doing a factory reset in factory recovery. Otherwise you risk breaking your device.. If you look around you will find ways to do a manual update to a slightly newer firmware just not the newest and your ROMs will work.
jimyv said:
Never factory reset stock slot if you have run the OTA blocker the utility also has a eNAble option for the OTA blocker always uninstall xposed framework and modules before factory reset also .. Always returning the unit to as close to factory as you can before doing a factory reset in factory recovery. Otherwise you risk breaking your device.. If you look around you will find ways to do a manual update to a slightly newer firmware just not the newest and your ROMs will work.
Click to expand...
Click to collapse
Thanks. i will look for the update method you mentioned. i might have already read it on Friday, but didn't think it would apply to my version.
i have removed everything related to modding before factory resetting from the FireOS settings. At that point, there was only safestrap left, which i uninstalled.
If i decided to stay on FireOS after all, until a better method comes up, is there a way for me to check, if the OTA blocker is actually working?
lol
kobayashimaru said:
Thanks. i will look for the update method you mentioned. i might have already read it on Friday, but didn't think it would apply to my version.
i have removed everything related to modding before factory resetting from the FireOS settings. At that point, there was only safestrap left, which i uninstalled.
If i decided to stay on FireOS after all, until a better method comes up, is there a way for me to check, if the OTA blocker is actually working?
Click to expand...
Click to collapse
It works. Just open settings go device,system updates ,check for updates, should fail immediately..if it stars to dl. kill wifi
jimyv said:
It works. Just open settings go device,system updates ,check for updates, should fail immediately..if it stars to dl. kill wifi
Click to expand...
Click to collapse
Thanks, i'm always scared with such new devices.
"Update failed". Perfect.
i got the Thor GAPPS working by now, so i'll try using that for now.

Possible to unlock bootloader on HDX 8.9" (apollo)

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.

Safestrap/TWRP/Gapps

I've got my 4.5.5.1 setup rooted but I was unable to get gapps working... got everything installed but the Play Store just force closes any time I try to open it, even after rebooting. I eventually got past that to where I should sign in but it's saying there's an error contacting Google, even though the internet works fine for other apps like Facebook. Snapchat, which I installed via 1Mobile, requires GPS, and that's also not letting me sign in.
I've been getting tired of the hassle and I'm thinking of going the Safestrap/CM route to get more reliable Google Play experience. The Safestrap thread says I have to be on 4.5.2, though... is that still accurate, or can I do it with a rooted (Kingroot) 4.5.5.1? I had tried installing it on 4.5.5.1 but it didn't seem to take, nothing showed up when I rebooted, and the option to reboot from the app to recovery was still greyed out. I'm also seeing that the safestrap dev dropped support a while back, should I look at rolling back to 3.2.8 and going with TWRP instead? What's the best/most recommended method at this point?
Thanks.
You can NOT install TWRP, downgrading to 3.2.8, and then updating to 4.5.2, root, and using Safestrap v4 with either CM11 or Nexus for Safestrap v4 would be your options. CM12, CM13 and SlimLP are NOT Safestrap compatible!
You can NOT downgrade below 3.2.8 due to rollback protection by Amazon, attempt would brick the device!
Note that you must disable WLAN/keep flight mode active during the down- and update procedure! Getting updated OTA by Amazon while on the downgrade-3.2.8 will brick the device!
Also note that you should use the stock slot in Safestrap v4, ensure you understand the risks of using the stock slot before you flash anything to it! Also create a backup of the stock slot and move it to your PC before you flash anything to it.
And always remember: Never restore a backup of a secondary slot to the stock slot! Would overwrite Safestrap files and brick the device.

Can't upgrade to 3.41.651.4 OTA

Hi, I am trying to upgrade my Sprint HTC One M9 to 3.41.651.4.
Current Software Version: 2.11.651.19
My phone finds and installs 2.11.651.180, everything seems to work correctly, however, after rebooting, my phone is still on software 2.11.651.19.
My phone has never been rooted, s-on/off, or anything else. The only thing that I have changed on it is adding an SDCard. Everything else has been OTAs. Last factory reset was 3 weeks ago to solve a problem I was having with Gmail not syncing properly.
I would prefer to not have to factory reset it again by manually upgrading the firmware. Is their a log somewhere that will show what is preventing the upgrade from taking?
Ok, some more details. It appears when doing the OTA, the error I am getting is a System 7 error?
Then when I try to flash following the instructions on HTC's site using the RUU .exe, I get a 155 error.
From googling it appears both of these errors are caused by modifying the system partition. Which is great, except I haven't. I haven't monkeyed with my phone. Not unlocking, s-on/off, bootloader, recovery, etc. So I'm not sure how it came to be this way or how to restore it. Previous OTAs have all installed without issue.
Software Status: Modified
Locked
S-ON
Security Warning
And now my phone is stuck with a white screen. Menu options are:
Reboot
Reboot to Bootloader
Boot to Download mode
Boot to Recovery Mode
If I select recovery mode, it is unable to launch and takes me back.
Ok, I set it to Download mode and re-ran the RUU .exe, and it seems to have flashed properly now. So I guess I'm good. But I do have questions:
A) Why did the OTA fail multiple times with the System 7 message
B) Why did the RUU .exe wipe everything and give me the 155 failure the first time
C) Is there anything I should do/install/check to prevent problems in the future?
shawndoc said:
Ok, some more details. It appears when doing the OTA, the error I am getting is a System 7 error?
Then when I try to flash following the instructions on HTC's site using the RUU .exe, I get a 155 error.
From googling it appears both of these errors are caused by modifying the system partition. Which is great, except I haven't. I haven't monkeyed with my phone. Not unlocking, s-on/off, bootloader, recovery, etc. So I'm not sure how it came to be this way or how to restore it. Previous OTAs have all installed without issue.
Software Status: Modified
Locked
S-ON
Security Warning
Click to expand...
Click to collapse
you did something to make status modified
Yes, but what? Every other OTA has installed fine. I haven't tried to root or mess with s-on/off. The only thing I can think of, is last time I reset my phone (due to gmail failing to get push notifications) I uninstalled a bunch of the bundled apps, but I did it using the normal apps management settings.
shawndoc said:
Hi, I am trying to upgrade my Sprint HTC One M9 to 3.41.651.4.
Current Software Version: 2.11.651.19
My phone finds and installs 2.11.651.180, everything seems to work correctly, however, after rebooting, my phone is still on software 2.11.651.19.
My phone has never been rooted, s-on/off, or anything else. The only thing that I have changed on it is adding an SDCard. Everything else has been OTAs. Last factory reset was 3 weeks ago to solve a problem I was having with Gmail not syncing properly.
I would prefer to not have to factory reset it again by manually upgrading the firmware. Is their a log somewhere that will show what is preventing the upgrade from taking?
Click to expand...
Click to collapse
You probably got all those errors due to the fact you manually tried to update the firmware/software. And according to what you wrote you currently had 2.11.651.19 tried to update with an older firmware 2.11.651.180. Second if you are stock, not rooted or s-off and previously did OTA's, why didn't you wait for the 3.41.651.4 OTA?
schmeggy929 said:
You probably got all those errors due to the fact you manually tried to update the firmware/software. And according to what you wrote you currently had 2.11.651.19 tried to update with an older firmware 2.11.651.180. Second if you are stock, not rooted or s-off and previously did OTA's, why didn't you wait for the 3.41.651.4 OTA?
Click to expand...
Click to collapse
Re-read my first post, it was the OTA that was failing to install with the System 7 error, which then led me to try installing manually.
The OTA is a two part OTA. First it installs 2.11.651.180 and then it installs 3.41.651.4. See here: http://www.htc.com/us/support/htc-one-m9-sprint/news/
It was 2.11.651.180 OTA that was giving me the original error message.
shawndoc said:
Re-read my first post, it was the OTA that was failing to install with the System 7 error, which then led me to try installing manually.
The OTA is a two part OTA. First it installs 2.11.651.180 and then it installs 3.41.651.4. See here: http://www.htc.com/us/support/htc-one-m9-sprint/news/
It was 2.11.651.180 OTA that was giving me the original error message.
Click to expand...
Click to collapse
Gotcha, the 2.11.651.180 was the pre-MM update then the MM full OTA. Yes it is weird you were getting those error on a OTA. Even the RUU shouldn't have lead to an error as well. You still having problem or everything ok now?
Yup, all good now. Forcing the phone into download mode and performing the upgrade took. Thanks.

[Help Needed] Flashed 4.5.2 cant update update failed

I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
DroidDogg said:
I flashed 4.5.2 Apollo on my 8.9 HDX from CM11 now Im stuck it doesnt update just says update failed I removed the recovery didnt fix the problem either. Is there a flashable 4.5.5.1 apollo zip? I tried changing the bin to a zip and flashing didnt work said apollo_full instead of apollo as error. Anyone know how to fix it just downloads the update fully then says update failed...
Click to expand...
Click to collapse
Be happy 4.5.5.1 didn't take when SafeStrap recovery was installed; device would have bricked. Assume you used the Safestrap compatible variant of 4.5.2 (here). After flashing that (stock slot only; never use secondary slots in SS v4) reboot device and remove Safestrap recovery via SS app. Power down and boot into stock recovery via <power>+<vol-up> and perform a factory reset (you'll loose all apps/data). Reboot again and initialize FireOS. It should then accept OTA updates.
Be 100% sure Safestrap recovery is uninstalled prior to doing a factory reset.
Curious - why to you want 4.5.5.1? Offers no advantage over 4.5.2 if running custom ROMs. Nor will it automatically update to FireOS v5 as Amazon has no plans to release a v5 update for 3rd gen devices.
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
DroidDogg said:
Ok I went back to 4.5.2 > installed kingroot > went to safestrap > uninstalled recovery > rebooted to stock recovery and factory reset . Its still doing the same thing it downloads to 100 and doesnt do anything...
Click to expand...
Click to collapse
DroidDogg said:
I might be selling the device and going to a Nexus 9 so I have to make sure it can update or Im going to lose money on the sale.
Click to expand...
Click to collapse
IDK - should work. You can try downloading the latest version of FireOS here; installation instructions here. Also verify OTA apk is installed and properly named (here).
It's likely 4.5.x is the terminal release of FireOS for 3rd gen devices; potential buyers will not be severely disadvantaged on 4.5.2.
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
As previously posted - IDK and I do not think anyone else does either. What I do know is every flash (some which appear questionable) presents another failure opportunity that could yield an unrecoverable device. Keep experimenting and posting results; others will learn from your efforts. Just recognize the risk and know when to say 'good enough'. Pushing from 4.5.2 to 4.5.5.1 buys you no additional capability/functionality/stability at this time.
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
Do you checked if the DeviceSoftwareOTA.apk is there? (which @Davey126 mentioned above).
I was in the same situation and had to rename it back, which I'd renamed before as described in the OTA blocking tutorial. http://forum.xda-developers.com/showpost.php?p=59160158&postcount=1
DroidDogg said:
OK I tried to update to 4.5.5.1 from 4.5.2 (said it was invalid update) do I need to update sequentially like 4.5.3 first?
Update 1: Tried 4.5.3 said update file not valid again. I'm beginning to think this restore file I found on here that was Safestrap 4.5.2 might be the wrong zip for this device even though it installs...
Update 2: Tried another TWRP 4.5.5, it installed, then I did the same thing again removed SafeStrap. Then factory reset...
Why can't I update to 4.5.5.1 after returning from CM11 this is so frustrating.
Click to expand...
Click to collapse
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
mzk1 said:
did you ever figure this out? i'm in the same boat right now, except i don't even know how to remove the recovery. i'm running safestrap 4.01 and fire rom 4.5.2. I saw another post here http://forum.xda-developers.com/showpost.php?p=49687774&postcount=9 but i'm not quite sure if it will work ( i just don't want to brick my kindle). I got it unrooted but that is about it
Click to expand...
Click to collapse
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Davey126 said:
Ignore that post; dangerous to futz with build.prop on this device. Try the following:
- reroot (yes, this is necessary)
- browse to /system/priv-app/ and search for DeviceSoftwareOTA.???, where '???' is likely 'bak' but could be any series of characters
- rename above file to DeviceSoftwareOTA.apk (this is the app {likely one of several} that handles OTA updates on FireOS v4)
- reboot again
- verify device is registered with Amazon
- check every 10-15 min for availability of OTA update; it will almost certainly be 4.5.5.1; allow the update to proceed
Click to expand...
Click to collapse
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
mzk1 said:
Thanks for the steps but I've tried that already. The kindle does find the update but only to 4.5.3. It downloads it and then does nothing. just stays there. It might give an error after a while and go back to where it checks for updates. I tried to side load the newest rom which I have manually downloaded from amazon, the tablet recognized it at first but then gave me an error. Is it crucial to remove the recovery in order to obtain the update?
Click to expand...
Click to collapse
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Davey126 said:
If you are referring to Safestrap v4 recovery then absolutely yes. The app itself can stay but recovery must be removed (uninstalled). Lucky you didn't score a brick trying to update FireOS with Safestrap recovery installed.
Click to expand...
Click to collapse
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
mzk1 said:
I got to the step where everything is ready to go. the device has been reset to factory default, safestrap recovery has been uninstalled. the device got registered in amazon store and found an update 4.5.3 but it still can't flash it after downloading. I copied the newest 4.5.5 bin file to the tablet, but when i tried to hit update I got a message: unable to complete update because the update file is not valid. please try downloading file again. Right now I'm on the 13.4.5.2 rom which I got here http://forum.xda-developers.com/kindle-fire-hdx/development/hdx-stock-images-pre-rooted-updates-t2911954. Is there any other ideas on how to make update to work?
should I just edit buildprop for downgrade? i will need root for that. Can you advise, please
Click to expand...
Click to collapse
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Davey126 said:
Four choices:
- Modify build.prop, attempt a downgrade and brick your device. Go ahead, I'll wait ...
tip: relying on uncollaborated guidance in a three year old post is rarely best practice
- Root, reinstall Safestrap v4 + CM/Nexus and leave well enough alone. Your device works. Upgrading is not all it's cracked up to be. Kinda like that sweet looking honey/hunk in the bar on a foggy Saturday night.
- As above but reflash the Safestrap compatible (no other) version of FireOS 13.4.5.2. Possible something didn't go well the first time around which is preventing OTAs from being processed correctly. AFAIK - OTA is the only path to 4.5.5.1 as Amazon only offers 4.5.5 for download.
- Attempt a rollback to 3.2.8 followed by an immediate upgrade to 13.4.5.2 as documented here. This path is both the riskiest and the one most likely to clear whatever is blocking OTA updates. If you choose this option be sure to follow instructions exactly including linked files (not others you may have lying around). It is essential WiFi remain off (airplane/flight mode engaged) during the brief window your device is on 13.3.2.8. If an OTA update arrives on this version the device will hard brick with NO possible recovery.
Click to expand...
Click to collapse
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
mzk1 said:
thanks for the solutions. I figured since it is such a pain to get it to work I'll just stick with Nexus ROM now.
Click to expand...
Click to collapse
Yep - that would be my choice too. Take note there are two Nexus builds, one for devices that have a 4.5.5.1 kernel, the other for older kernels. Try the former first as it as actively maintained and has a broader feature set. Links below:
old: http://forum.xda-developers.com/kindle-fire-hdx/development/rom-hdx-nexus-v4-0-1-t3125808
new: http://forum.xda-developers.com/kindle-fire-hdx/orig-development/rom-fire-nexus-rom-ktu84q-t3322931

Categories

Resources