To get the official OTA from Verizon, will I need to flash the stock Froyo ROM back? I'm on a GB ROM right now. I haven't had any notification of it yet and from what I've seen it should be here by now.
TeeRom said:
To get the official OTA from Verizon, will I need to flash the stock Froyo ROM back? I'm on a GB ROM right now. I haven't had any notification of it yet and from what I've seen it should be here by now.
Click to expand...
Click to collapse
You would need to go back to S-On. Probably best to just flash a stock RUU. Keep in mind once you do get the OTA you won't be able to root it until someone figures out the method.
loonatik78 said:
You would need to go back to S-On. Probably best to just flash a stock RUU. Keep in mind once you do get the OTA you won't be able to root it until someone figures out the method.
Click to expand...
Click to collapse
Actually you dont need to go s-on and wouldnt want to unless you want to loose the ability to root. All you need to do is stay s-off and flash the stock froyo 2.2 ruu, then wait for the ota, then reroot by flashing a custom recovery in hboot, and then flashing the su binary thru recovery. The OTA does not check to see wether you are s-off or not, nor does the ruu.
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
mayashoval said:
I have an unlocked HTC One X, running Stock Rom and CMW recovery. CID 621. (never installed any custom roms, only CMW recovery and unlocking the phone)
I haven't updated my phone in a while since OTA failed due to the recovery. Last night I reverted back to the stock recovery and updated, successfully, OTA version 2.18.751.7.
After updating my One X informs me there's a JB OTA update, 3.14.751.20 but when I try to run it, it reboots, shows the green progress bar for about 30 seconds then shows the red rectangular of failure (rebooting starts up the device normally).
I tried reflashing the stock recovery, tried the recovery from the latest RUU for my CID (RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed) but the OTA update keeps failing.
I also tried disabling SuperSU and used Voodoo Root Keeper to disable root, still the same red rectangular. Tried using the nandroid backup and running through the updates again, but same issue (2.18.751.7 installs correctly, but 3.14.751.20 fails).
Any help would be appreciated!
Thanks,
Maya
Click to expand...
Click to collapse
Have you tried relocking your bootloader? 'fastboot oem lock'
Also, maybe try flashing the stock kernel as well?
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
ArmedandDangerous said:
Also, maybe try flashing the stock kernel as well?
Click to expand...
Click to collapse
I'm hesitant about flashing a kernel, as I did not change the original stock one, and it feels too risky.
BenPope said:
Did you remove anything?
You might try running an RUU if you can one one new enough, or restoring a backup (there are threads here for both backups and RUU, but look on htcruu.com, the device is endeavoru)
Click to expand...
Click to collapse
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
mayashoval said:
I thought about that, but the most recent RUU for my CID is older than what getvar is telling me (INFOversion-main: 2.18.751.7. latest RUU I found is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_2.1204.136.21_release_275588_signed).
As to relock, I went through quite a few similar threads and in all relocking did not make any difference. Also, if that was the case, I don't think the first OTA update would have gone through.
Click to expand...
Click to collapse
I think the update to hboot requires it to be locked, your previous update was most likely ok with the hboot it was on.
mayashoval said:
I thought about that
Click to expand...
Click to collapse
Then look for a backup of your ROM version in the backup thread.
BenPope said:
Then look for a backup of your ROM version in the backup thread.
Click to expand...
Click to collapse
Sorry to be a noob but what do you mean? I thought I couldn't use a backup older than the one listed under "main version". Or am I confusing things?
Edit:
Can I install the most recent RUU?
INFOversion-main: 2.18.751.7.
latest RUU is: RUU_ENDEAVOR_U_ICS_40_S_Chunghwa_2.17.751.2_Radio_ 2.1204.136.21_release_275588_signed.
Update: locking the phone did not help
I locked the phone, but the update still fails at the same location. The green bar expands for about 20 seconds, covering about a quarter of the bar, and the the red triangle appears.
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
sorry for being a noob
gffmac said:
You could always attempt to update the firmware/hboot manually download it here for your cid http://forum.xda-developers.com/showthread.php?t=1957376
Or there is a tool here http://forum.xda-developers.com/showthread.php?t=1924003
Click to expand...
Click to collapse
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
mayashoval said:
the tool looks easy enough, but they ask to include the custom JB rom of my choice. I want the Stock update, so what do I do?
The manual update list points to a broken link. I did find it somewhere else. How do I manually update? are these the commands?
fastboot oem rebootRUU
fastboot flash zip firmware.zip
do I need to unlock my phone again? can I use the same Unlock_code.bin I got from HTC last time (saved it) or do I have to go through the process again?
I'm asking all these questions because I don't want to end up with a bricked phone.
Click to expand...
Click to collapse
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
exocetdj said:
There are a couple of really good stock looking ROMs on there with enhanced performance. There's one mentioned in my sig, it may also be the easiest route out of your issue using the tool posted above
Click to expand...
Click to collapse
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
mayashoval said:
Yes I am running to issues... turns out that manually flashing the firmware.zip just got my phone into a bootloop since it turns out you must install a custom rom after it. I did not want to install a custom rom just to get the OTA update to install. now my phone keeps rebooting and I'm waiting for ADHD to download (takes FOREVER! for some reason).
This really sucks. I wanted to stay with stock, and it looks like I can't even go back anymore, can't even restore with a RUU.
Click to expand...
Click to collapse
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
exocetdj said:
There should be a RUU out for your region soonish but Until then, a stock style custom rom is a brilliant option beleive me
Click to expand...
Click to collapse
don't really have a choice now...
downloading maXimus as per your recommendation (and because ADHD will take another 9 hours
You can restore an older backup, it's just like installing a custom ROM.
You might also be able to install a 2.17 RUU on 2.18, I'm not sure the hboot was updated. It's also possible to dissect an RUU and install the bits manually.
You have a few options.
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
Sorry did not find a solution. Ended up installing a custom rom, even though I wanted to keep using the stock one
plaktoets said:
i am having the same issue, I have the stock rom (never flashed) on a rooted phone. So i relocked the bootloader and flashed stock recovery, but im getting the red triangle when installing the update.
OP, did you already find a solution?
Click to expand...
Click to collapse
I hope you did this the other way around......first flash the recovery and the relock the bootloader.....
But if you are on stock rom, kernel and recovery you do not have to relock the bootloader, it updates fine with a unlocked one.
I'm on stock 1.54.401.10, rooted, s-off and with twrp.
I'd like to go to stock recovery to install OTA.
Need answers for some questions first:
What do I need to install update?
I know about recovery, do I need to relock bootloader?
Also there was an issue with custom hboots on m7, so can I relock bootloader, update software, etc, if I don't have red text during boot? Gone after using firewater.
Not sure if this is related, just want to be sure, I won't brick my phone during update.
Or maybe it is better to flash firmware and newer rom manually?
wor3q said:
I'm on stock 1.54.401.10, rooted, s-off and with twrp.
I'd like to go to stock recovery to install OTA.
Need answers for some questions first:
What do I need to install update?
I know about recovery, do I need to relock bootloader?
Also there was an issue with custom hboots on m7, so can I relock bootloader, update software, etc, if I don't have red text during boot? Gone after using firewater.
Not sure if this is related, just want to be sure, I won't brick my phone during update.
Or maybe it is better to flash firmware and newer rom manually?
Click to expand...
Click to collapse
With stock recovery and stock rom you can install official updatea, no need for relocking bootloader.
Because you're s-off you can also do it manually, see this post.
I planned on converting my One M8 to a GPE edition but I couldn't gain S-Off, so now I have a phone with root access and TWPR installed. In preparation for HTCs upcoming Lollipop OTA, I would Like to bring my device back to full stock so I can install the OTA. I can't seem to find a way to do this without having S-Off. Could someone help me please?
Thanks, Nathan
nathbullen said:
I planned on converting my One M8 to a GPE edition but I couldn't gain S-Off, so now I have a phone with root access and TWPR installed. In preparation for HTCs upcoming Lollipop OTA, I would Like to bring my device back to full stock so I can install the OTA. I can't seem to find a way to do this without having S-Off. Could someone help me please?
Thanks, Nathan
Click to expand...
Click to collapse
You can always flash to stock recovery
https://www.youtube.com/watch?v=PPPT5J8xG6w
Good luck!
L1nuz said:
You can always flash to stock recovery
Click to expand...
Click to collapse
Will that remove my root user permissions too?
And do I need to relock the boot loader to install OTA's?
Thanks!
nathbullen said:
Will that remove my root user permissions too?
And do I need to relock the boot loader to install OTA's?
Thanks!
Click to expand...
Click to collapse
sakitech didn't mention anything about losing root or relock bootloader requirements to receive OTA updates after following his video.
L1nuz said:
sakitech didn't mention anything about losing root or relock bootloader requirements to receive OTA updates after following his video.
Click to expand...
Click to collapse
No, he didn't, but it was part of my original question!
nathbullen said:
No, he didn't, but it was part of my original question!
Click to expand...
Click to collapse
Oh, sorry for not being clear xD
No, I don't think you will lose root and you don't have to relock bootloader afaik.
Even so.. you can always redo the process of rooting and unlock the bootloader after OTA update.. no biggie
but if you run stock rom and recovery.. it shouldnt affect root or if ure unlocked with OTA updates
I just reverted back to stock last night with s-on. you will have to relock your bootloader (I used a tool kit, but had to boot into the bootloader myself to get the toolkit relock it) and flash a stock RUU (exe or zip). I suggest using an exe to flash if available. I have a sprint HK edition so I used an RUU exe for that model, and all worked perfectly. I was able to install the OTA update they just released with no problem after I was back to stock.
sakitech's method should work too if you want to try and keep root and the bootloader unlocked
I see the One m9 Marshmallow update is out today.
If we are currently rooted with TWRP and S-OFF, what do we need to do to get the OTA?
I assume flash the stock recovery back first, take the OTA, then reflash twrp and root again?
Did I miss anything?
You have to be 100% stock (other than s-off) to take an OTA, which means running a RUU.
But being s-off, why not just wait until the firmware gets posted and update manually?
iElvis said:
You have to be 100% stock (other than s-off) to take an OTA, which means running a RUU.
But being s-off, why not just wait until the firmware gets posted and update manually?
Click to expand...
Click to collapse
Ah yes of course... good call. Thanks
iElvis said:
You have to be 100% stock (other than s-off) to take an OTA, which means running a RUU.
But being s-off, why not just wait until the firmware gets posted and update manually?
Click to expand...
Click to collapse
How would you update manually?
Manually - in case of S-OFF - means flashing firmware that has e.g. been extracted from the OTA using fastboot.
In such a case it is even possible to exchange the stock recovery by the latest TWRP, to be able to flash custom ROMs right away after doing the manual upgrade.
As those named firmware zip-files in most cases you're going to find around this forum, are no longer files which are signed by HTC they can only be flashed if your device got S-OFF'd.
That's as far as a brief explanation of the term "manually" is possible.
Send by the swarm intelligence of my coffee machine ?.