Unable to apply newest cricket OTA update - HTC One SV

I have an unlocked bootloader and them routed, although I was unable to achieve s-off following any of the guides on this forum. When I try the OTA update, I get an error in CWM saying it was unable to flash the image and it was cancelled. I have tried it with signature verification enabled and disabled, with the same results.
Sent from my HTC One SV using Tapatalk now Free

zomgitsanoob said:
I have an unlocked bootloader and them routed, although I was unable to achieve s-off following any of the guides on this forum. When I try the OTA update, I get an error in CWM saying it was unable to flash the image and it was cancelled. I have tried it with signature verification enabled and disabled, with the same results.
Sent from my HTC One SV using Tapatalk now Free
Click to expand...
Click to collapse
The update to Jelly Bean i guess?
As long as you have cwm installed you will not be able to update. The OTA update is not for flashing in recovery!
You need stock boot.img, stock recovery and stock system partition to update.

Already on jb. Update 2.04.1050.5
I assume the same rules still apply, though?
Sent from my HTC One SV using Tapatalk now Free

zomgitsanoob said:
Already on jb. Update 2.04.1050.5
I assume the same rules still apply, though?
Click to expand...
Click to collapse
Ah, ok. Cricket gets also a small update.
Yes, the same rules as before

OTA installation aborted
I have bought this phone a couple of months ago and rooted it and have clockworkmod recovery 6.0.3.2 installed. The phone is running good and i have not had problems. However, I see that there is an OTA update for the version 2.04.1050.5. I tried installing the 15 mb file and it told me to restart the phone. When it does, it takes me to the clockworkmod Recovery thing and tells me the installation is aborted? What do I do? Do I really need this update or can I go without? Also, is this the update for the 4.2.2 Jelly Bean?
Any help is appreciated.

quickser4u619 said:
I have bought this phone a couple of months ago and rooted it and have clockworkmod recovery 6.0.3.2 installed. The phone is running good and i have not had problems. However, I see that there is an OTA update for the version 2.04.1050.5. I tried installing the 15 mb file and it told me to restart the phone. When it does, it takes me to the clockworkmod Recovery thing and tells me the installation is aborted? What do I do? Do I really need this update or can I go without? Also, is this the update for the 4.2.2 Jelly Bean?
Any help is appreciated.
Click to expand...
Click to collapse
that tiny update cab be accepted if you haven't deleted or modified ahh of the system.
if your s-on then you have to relock your bootloader
but first of all you need to flash the stock boot.img and stock recovery.img

Related

OTA update

Phone has just told me that an update; 'System enhancement 59.02 MB' is available, I've downloaded it, installed it and the phone has rebooted.
However... it reboots into Clockworkmod recovery so I have to select 'Reboot now'.
Aswell as producing an 'abnormal reset' error, the update is still available; it doesnt seem to have installed.
Phone has been rooted with superoneclick following HTC bootloader unlocking. As nandroid backup was not available from recovery, I installed clockworkmod recovery. Is this causing the issue? Can I stop the phone booting into recovery every time?
Help?
Please?!
you need stock recovery to get OTA updates.. flash the stock recovery and you will be fine
Thanks.
erm. How?
azzledazzle said:
you need stock recovery to get OTA updates.. flash the stock recovery and you will be fine
Click to expand...
Click to collapse
Allow me to say it better: You need a stock recovery to implement the OTA updates - you can download w/o it but must have it to install it.
How do I get stock recovery or disable/uninstall clockworkmod?
Badmiker said:
How do I get stock recovery or disable/uninstall clockworkmod?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1604677
Thanks so much! That has solved the CWM issue and phone is now trying to update.
1st attempt failed. Is now downloading update again. Maybe a different update now the firmware has changed?
Installing again....
Arg! assert failed: apply_patch_check
?
orenfl said:
Allow me to say it better: You need a stock recovery to implement the OTA updates - you can download w/o it but must have it to install it.
Click to expand...
Click to collapse
I used the all-in-one toolkit to unlock bootloader and all that good stuff. But i never flashed a recovery. Phone is rooted and everything. Is it absolutely necessary to flash the recoveries in that toolkit? What are the purposes for it? (noob status >_>) I know what the stock one is but was always wondering about the rest and if you really needed them.
ToterPunkt said:
I used the all-in-one toolkit to unlock bootloader and all that good stuff. But i never flashed a recovery. Phone is rooted and everything. Is it absolutely necessary to flash the recoveries in that toolkit? What are the purposes for it? (noob status >_>) I know what the stock one is but was always wondering about the rest and if you really needed them.
Click to expand...
Click to collapse
Actually, I haven't done root yet to this specific phone, just for my previous ones.
Try to look in that linked thread to search for an answer.
Is this a TMO US update?
ive just got my update for my sim free carrier free one s. Im in the uk.
Not sure what the changes are supposed to bring...cant say ive noticed any difference at all yet.
This is very frustrating, it's really not happening for me.
I've unrooted & reflashed with stock recovery then downloaded update but it's still failing to install.
assert failed: apply_patch_check ("SystemUI.apk", big code)
E:Error in /internal sdcard/download/OTA)Ville_U_HTC_Europe....
Status 7
Installation aborted.
Dammit. Is the phone getting the wrong update? Can anyone help please?
Badmiker said:
This is very frustrating, it's really not happening for me.
I've unrooted & reflashed with stock recovery then downloaded update but it's still failing to install.
assert failed: apply_patch_check ("SystemUI.apk", big code)
E:Error in /internal sdcard/download/OTA)Ville_U_HTC_Europe....
Status 7
Installation aborted.
Dammit. Is the phone getting the wrong update? Can anyone help please?
Click to expand...
Click to collapse
For the OTA update you will nedd to have stock recovery on your phone, bootloader relocked and a stock rom without any apps uninstalled.
Relock the bootloader?!
Why?!
HTC allow me to unlock it, so surely they should support an unlocked bootloader?
Locked with AIO toolkit and trying update again...
Badmiker said:
Locked with AIO toolkit and trying update again...
Click to expand...
Click to collapse
Thats most important for a sucessfull update. Had this problem with TMO Germany and after relocking the bootloader everything went fine. I used the RUU instead the OTA.
My update always stopped upon a checksum failure as long as the bootloader was unlocked. It was gone after relocking.
Someone please try skype video chat
Hello,
Can someone please see if the video chat in Skype is fixed.
Preferably someone who has already seen how bad it is before the update.
Thanks,
~Eric
I finally got my update HTC One S simfree in Canada to 1.78
incase anyone cares
I got my update yesterday...maybe it's wishful thinking, but my battery seems to have improved...this moring i was left with 26% after playing all night...normally I would be down to 5%
Here's the OTA update I got today:
OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2_release_258562piuubd9lrapskwje.zip
radio
does this update contain a radio update?
Can someone separate it and post it.
If you do please state which carrier/country you got the update from.
So far no t-mo usa update. Non usa customers claim the update solves the mutitasking issue reported on engadget.com for htc one x (s)

[ REQ ] What are the steps to be followed for getting OTA?

Hi, I have been flashing a lot of roms after getting ics. But there was never a situation where I needed to go back to stock to get OTA again. Here is a few questions,
1. If I flash a stock rom now, will I get the OTA? Where do I get completely stock rom?
2. Will I lose root and if I do, do I have to go through the same procedure again to root?
3. I've been hearing about flashing root patch, is it a zip file which can be installed from recovery when I'm on stock?
It would be nice if someone explain how to go from any rom to stock jelly bean with root.
Sent from my Nexus S using xda app-developers app
Of you do not know use rom manager to return to stock. If you like a check flash 2.3.3. You will receive the OTA for 4.0.4 immediately...
Sent from my Nexus S using xda premium
This is easy, but you'll lose root. (you do know that rooting the Nexus S takes only 1 minute, that isn't a big deal. About getting back to stock, browse the Nexus S general section looking for a post that says something like that "all OTAs for all models". There you'll find an 4.0.3 official, signed, zip file. Just flash the correct file for your nexus S model, the signed zip contains recovery, bootloader, kernel, etc. After that, root the phone again (nexusshacks.com has an easy ICS root video) install CWM and flash CWM recovery. When you connect the phone to the Internet you'll should be prompted to update it to 4.0.4 via OTA. If you're not, wait a few moments or reboot the device. You're done, just wait for official jelly bean!!
Hope I've helped.
Sent from my Nexus S using xda premium
alexfiorani said:
This is easy, but you'll lose root. (you do know that rooting the Nexus S takes only 1 minute, that isn't a big deal. About getting back to stock, browse the Nexus S general section looking for a post that says something like that "all OTAs for all models". There you'll find an 4.0.3 official, signed, zip file. Just flash the correct file for your nexus S model, the signed zip contains recovery, bootloader, kernel, etc. After that, root the phone again (nexusshacks.com has an easy ICS root video) install CWM and flash CWM recovery. When you connect the phone to the Internet you'll should be prompted to update it to 4.0.4 via OTA. If you're not, wait a few moments or reboot the device. You're done, just wait for official jelly bean!!
Hope I've helped.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
So, this way I wont lose my apps right? Even if I flash the OTA of jellybean as a .zip file and if i root it again, I can get the apps back with titanium backup i guess.
alexfiorani said:
This is easy, but you'll lose root. (you do know that rooting the Nexus S takes only 1 minute, that isn't a big deal. About getting back to stock, browse the Nexus S general section looking for a post that says something like that "all OTAs for all models". There you'll find an 4.0.3 official, signed, zip file. Just flash the correct file for your nexus S model, the signed zip contains recovery, bootloader, kernel, etc. After that, root the phone again (nexusshacks.com has an easy ICS root video) install CWM and flash CWM recovery. When you connect the phone to the Internet you'll should be prompted to update it to 4.0.4 via OTA. If you're not, wait a few moments or reboot the device. You're done, just wait for official jelly bean!!
Hope I've helped.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
I think it's not correct,if you flash Cwm,the ota package will not be able to self-install cause it works only with stock recovery.
To recieve otas you need to have all stock,especially recovery.
Neo on Nexus S with Tapatalk 2®
(THE REAL) Neo said:
I think it's not correct,if you flash Cwm,the ota package will not be able to self-install cause it works only with stock recovery.
To recieve otas you need to have all stock,especially recovery.
Neo on Nexus S with Tapatalk 2®
Click to expand...
Click to collapse
I don't want to lose all my apps by flashing the Jellybean OTA zip file and having to download all of it from the store. Anyway I could do that is what I want to know.
(THE REAL) Neo said:
I think it's not correct,if you flash Cwm,the ota package will not be able to self-install cause it works only with stock recovery.
To recieve otas you need to have all stock,especially recovery.
Neo on Nexus S with Tapatalk 2®
Click to expand...
Click to collapse
Then flash a completely stock rom image via fastboot. There are many guides on how to do that here.
Sent from my Nexus S®
mixtapes08 said:
Then flash a completely stock rom image via fastboot. There are many guides on how to do that here.
Sent from my Nexus S®
Click to expand...
Click to collapse
We are saying the same thing...
Neo on Nexus S with Tapatalk 2®
Delete..........
MYPaT said:
i could give 4.0.3 nand backup is some one want. now uploading googledrive
i use this and later get ota 4.0.4 with wi-fi
now completly stock no recovery no root. just stock recovery 3e
Click to expand...
Click to collapse
Can you give me the link? If I install it, will i lose root? But I will het ota right? Thanks in advance
Verstuurd van mijn Nexus S met Tapatalk
No, that isn't correct
(THE REAL) Neo said:
I think it's not correct,if you flash Cwm,the ota package will not be able to self-install cause it works only with stock recovery.
To recieve otas you need to have all stock,especially recovery.
Click to expand...
Click to collapse
I flashed 4.0.3 official, signed. after that I flashed CWM recovery via adb, went to recovery, flashed superuser.zip, turned the phone on, restored my apps/titanium backup data/etc, rebooted, in about 2 minutes after the reboot I got and warning telling me about an OTA update to 4.0.4, I hit yes and the phone turned off and installed official 4.0.4.
That proved, at least to me, that its possible to get OTAs even with custom recoverys, even though the OTAs may erase the custom recovery (that didn't happened with me, because 4.0.4 is an incremental update, it doesn't have a recovery file inside it.
I'm with stock 4.0.4 and CWM recovery right now, I hope to get jelly bean official as soon as it is released.
---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------
nitrix said:
I don't want to lose all my apps by flashing the Jellybean OTA zip file and having to download all of it from the store. Anyway I could do that is what I want to know.
Click to expand...
Click to collapse
If you updated your nexus s to ICS from Gingerbread, you'll remember that you didn't lose any app nor data, so if you're on stock and flash jelly bean official OTA you wont lose anything too.
Delete..........
alexfiorani said:
I flashed 4.0.3 official, signed. after that I flashed CWM recovery via adb, went to recovery, flashed superuser.zip, turned the phone on, restored my apps/titanium backup data/etc, rebooted, in about 2 minutes after the reboot I got and warning telling me about an OTA update to 4.0.4, I hit yes and the phone turned off and installed official 4.0.4.
That proved, at least to me, that its possible to get OTAs even with custom recoverys, even though the OTAs may erase the custom recovery (that didn't happened with me, because 4.0.4 is an incremental update, it doesn't have a recovery file inside it.
I'm with stock 4.0.4 and CWM recovery right now, I hope to get jelly bean official as soon as it is released.
---------- Post added at 03:14 PM ---------- Previous post was at 03:12 PM ----------
If you updated your nexus s to ICS from Gingerbread, you'll remember that you didn't lose any app nor data, so if you're on stock and flash jelly bean official OTA you wont lose anything too.
Click to expand...
Click to collapse
You are telling me that your phone turned off,and install 4.0.4 ota?
And using what?
Clockworkmod?
I don't think so...but if it worked for you...good!:thumbup:
Neo on Nexus S with Tapatalk 2®
Delete..........
MYPaT said:
yes you wil loose root and recovery too with first boot later you will get ota
i do same and now 4.0.4 and waiting google for jelly bean
Click to expand...
Click to collapse
You guys realize that as soon as the OTA comes out, someone is going to take it, remove the recovery replacing scripts, deodex it and all the nifty stuff for us to flash a nearly stock ROM in a matter of hours, right? There's hardly any point going back to stock only to get the OTA straight away.
Chances are most people won't get the OTA as soon as it's available, either because of the slow download or because it will be rolled out in steps to serve it properly... *slaps forehead*
Delete..........
(THE REAL) Neo said:
You are telling me that your phone turned off,and install 4.0.4 ota?
And using what?
Clockworkmod?
I don't think so...but if it worked for you...good!:thumbup:
Click to expand...
Click to collapse
Well, as far as I remember it was just like that, it installed with the same background as when I first got 4.0.4 and was still unrooted. The background was the stock one, the same as when you're doing a NANbackup in CWM (an green android with the belly open).
After all this talk about recovery and OTAs I thought that maybe I was crazy, that I was saying something impossible (get 4.0.4 with CWM recovery installed), but if I remember correctly, as soon as I flashed the 4.0.3 official zip, that contains the original recovery, I plugged the phone and hit fastboot flash recovery recovery-clockwork-touch-5.8.0.2-crespo.img, and only after that got the OTA.
But I may be mistaken , maybe I only pushed CWM recovery after getting the 4.0.4. I don't know, but I'd bet my money on "with CWM recovery you'll get OTAs".
When the OTA come out I'll know the answer for all this questions, it will all depend on if I get it or if I don't.
Ok,let me know,when ota of JB comes out.
This can be useful for me too...:thumbup:
Neo on Nexus S with Tapatalk 2®
polobunny said:
You guys realize that as soon as the OTA comes out, someone is going to take it, remove the recovery replacing scripts, deodex it and all the nifty stuff for us to flash a nearly stock ROM in a matter of hours, right? There's hardly any point going back to stock only to get the OTA straight away.
Chances are most people won't get the OTA as soon as it's available, either because of the slow download or because it will be rolled out in steps to serve it properly... *slaps forehead*
Click to expand...
Click to collapse
+100 that's the way I do it
Sent from my Nexus S
me2 i think its beter to stock your phone to get the ota !!

[Q] HTC One S Root OTA Update Questions

Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Problem Fixed
DrOfLife said:
Hello Everyone,
As of today, my phone received the new OTA Update for my HTC One S. However, obviously I cannot update due to my phone being rooted. As a person who is still relatively new with rooting (about a month rooted with my phone-first time), I have a couple questions.
First and foremost, have you guys enjoyed the OTA Update so far? I have read about the list of improvements, and they look promising.
Secondly, I obviously want to stay rooted, are there any suggestions about how to update and then have my phone rooted? Preferably without losing my root, but I don't think that's possible.
Thirdly, I saw a thread about the viper (I believe that's what it's called) rom and that could be my possible solution. But, I am rooted on stock rom and have never put on another rom before. So what are your thoughts on this rom?
Thanks in advance
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
fsustrength said:
Hey Dr.
I had the same issue and fixed it. I'm enjoying the OTA update...seems snappier and the option to change the menu button and get rid of that eyesore at the bottom of the screen is great....See this post on how to fix it:
http://forum.xda-developers.com/showthread.php?p=32069130
All you have to do is download the stock recovery (link located in the post above), rename it "Recovery.IMG" and put it in the /Data/Recoveries folder that your All In One Kit uses. Then open up the All In One root kit, flash the stock recovery, and reboot your phone. It should look the same, and give you the same notification that an update is available. Install the update, and then reflash your TWRP or CWM and reroot (the OTA unroots the device, so you need to reinstall SuperSu.
Thanks to all the people that have helped me do the same!!!
Click to expand...
Click to collapse
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
TheAdictsPunk said:
I keep flashing the stock recovery with all-in-one and then downloading and installing the update. Everytime, about halfway it goes back to the red triangle with the exclamation point and restarts the phone five minutes later.
I check software and its still 4.0.3 and the update redownloads. I've tried several "stock recoveries" and the update afterwards... never works.
Click to expand...
Click to collapse
I have also tried the steps and have run into the same problem. All is well when I flash into recovery, but when the phone starts updating about quarter or half-way through it also gives me the same red error message and the phone restarts soon after with no update. I have tried several times with the same problem.
However, thanks fsustrength for the instructions, before I was getting no where, but now I almost got it
Sent from my HTC VLE_U using xda app-developers app
ckpv5 said:
As there are many questions on how to do OTA update & to revert to stock after a device is rooted and bootloader unlocked; I made this simple guide which I hope will help the newbies especially.
NOTE : always do a backup and a nandroid backup before trying any of these.
OTA update:
A) ROM is stock, bootloader unlocked, stock recovery and not rooted.
- just run the OTA update, there is no need to relock the bootloader
B) ROM is stock, bootloader unlocked, CWM recovery and not rooted.
- flash the stock recovery that comes with your RUU, extract the RUU for the stock recovery.
* boot to bootloader
* fastboot flash recovery recovery_signed.img
* fastboot reboot-bootloader
* fastboot erase cache
* fastboot reboot
- run the OTA update
C) ROM is stock, bootloader unlocked, stock recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- run the OTA update, there is no need to relock bootloader
- Once done, run OTA Rootkeeper and click restore root
D) ROM is stock, bootloader unlocked, CWM recovery and rooted
- download OTA Rootkeeper from Play Store
- run the OTA Rootkeeper and click protect root
- no need to relock bootloader
- boot to bootloader and fastboot flash the stock recovery
- run the OTA update
- Once done, run OTA Rootkeeper and click restore root
E) ROM is custom, bootloader unlocked, CWM recovery and rooted and you have a stock nandroid backup
- flash the stock boot.img if after nandroid restore, you have a bootloop
- flash the stock recovery.img
- relock the bootloader - fastboot oem lock
- boot your device and run the OTA update
F) ROM is custom, bootloader unlocked, CWM recovery and rooted and you don't have a stock nandroid backup
- if you dont have the stock nandroid backup, you need to run RUU
- before you can run the RUU you need to:
* flash the stock recovery.img
* flash the stock boot.img (maybe no need)
* relock the bootloader - fastboot oem lock
* run RUU
- run device setup
- run the OTA update
Flashing RUU to revert to stock or to update your One V after you have a custom ROM installed.
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU
Note : for people with ERROR 155 UNKNOWN ERROR they need to go into HBOOT and select FASTBOOT and run the RUU to revert to stock (thanks Lloir)
And usually:
Error 155 - usually wrong recovery.img /wrong boot.img
Error 140 - wrong bootloader / bootloader unlocked
Error 131 - wrong RUU for your device
Credit to all XDA members that posted all the guides in various forum thread and some from own experience which I compiled here for easy reference.
Click to expand...
Click to collapse
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did). I did in fact have and used the root keeper app, put it on temporary unroot, and flashed the stock rom and ran the update. Yet, I still run into the problem of the red error sign. I'm sure there is a factor that maybe could cause it to stop, but I cannot put a finger on it.
However, I did notice something while following the procedures of the guide on my phone. When I flash the stock rom on my phone, I have to re-download the system update. While downloading the system update I notice that some of my apps get root permissions from SuperSu in the background, even though in root keeper I temporarily took off root. Rootkeeper also states that my phone is unrooted. Could this problem cause the red error message? If so, any way to fix it?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Wow, that is a very useful guide right there! However, while reading the guide, Step D is exactly what both TheAdictsPunk and I seem to have done (I'm making an assumption that he did).
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
I did! Last night I even tried flashing the recovery image through fastboot instead of the all-in-one kit. Then, even, the recovery image wouldn't flash all the way through... maybe our phones are having a problem with the recovery being reflashed and not the update at all.
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
mmceorange said:
I had the same exact issue. I finally got fed up and just flashed the RUU with my computer and then just used the All-in-one program to re-root. I am now enjoying 2.31 and really glad I updated. Obviously the RUU wipes everything, but I had done a full backup using Titanium Backup, and then restored all the important settings and data (like accounts, wifi list, bookmarks, dictionary, etc.) (but not the system apps themselves! ) and it worked out pretty well. Still had some things to adjust, like sounds and such. If you want to keep your SMS's use the built-in backup in the messaging app, then restore after the update.. more reliable than any other app I've tried.
Click to expand...
Click to collapse
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
I'm strongly considering doing that, I can back all my contacts and apps and sms messages via Mobile Go. So, wiping my phone isn't too big of an issue for me because I can restore almost everything I need back on my phone. If you don't mind me asking, where did you get the source that you got the RUU? Also, I have never flashed an ruu before so is their a guide for our phone to flash a RUU?
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
mmceorange said:
http://www.lastnite.de/RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5.exe
Links to downloads are on that page.. just copy/paste.
Basically start your phone in fastboot, connect to usb, then run the ruu with admin privileges. Make sure you are on stock recovery, and already have the USB drivers installed on your PC (unless you're on Linux.. already has them.. and maybe Mac too?)
Click to expand...
Click to collapse
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Click to expand...
Click to collapse
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Rerooting
DrOfLife said:
So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I'm still running stock 1.84, but I'm rooted and unlocked. I do not have any kind recovery like CWM or TWRP. You may have to flash a stock recovery image in order to re-install the recovery of your choice. If you want to get rooted again try this method: http://forum.xda-developers.com/showthread.php?t=1577831 It's what I used to gain root. It's a rather easy to follow guide. I used this instead of the AIO kit.
I'm going to try and revert to locked and unroot in order to get the update. Wish me luck.
DrOfLife said:
Well I followed all your steps, and all was going well until I ran across RUU error 130, which states that it was using the incorrect RUU. I looked into it and I found that it was the Europe version, and I have the T-Mobile version of my phone. I'm assuming that this is the issue, am I right? Does the RUU in Europe different than the T-Mobile USA one? If so, are there any RUU's out there that cover my phone? I have searched for them with no luck..
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Oh lol sorry about that.
DrOfLife said:
Ok I figured out a couple answers to my questions. One, the Europe version and the T-Mobile Version are different. That explains why the RUU did not work and gave me Error 130. However, the T-Mobile RUU, RUU_Ville_U_TMOUS_1.84.531.2_R2_Radio_0.16.31501S, is the alternate version that also recieves the OTA update. The RUU is found here http://androidforums.com/one-s-all-things-root/560329-ruu-download-mirrors.html
Then, following the steps, I have successfully updated my phone to the newer softeware!
Click to expand...
Click to collapse
Awesome!
DrOfLife said:
But of course, I run into another problem.... The CWM recovery does not work for my phone. I flashed the recovery via the HTC One S All-in-One Toolkit. But when getting my phone into recovery mode, it "crashes." (By crashes I mean the phone will go into the htc developmental screen, then turn to black, then reload the normal bootup screen and boot normally up) So, I don't have CWM and I'm unable to root my phone again because I don't have CWM to flash SuperSu. Any thoughts on this?
Click to expand...
Click to collapse
I personally have never encountered that before, so I am of little help here. The suggestion above me sounds like the right direction though.
Red triangle error
dc211 said:
Some wonderful person wrote a guide for the One V. Every though it's not the same phone the rules are the same. If these instructions help you click the link and thank the guy for writing it.
http://forum.xda-developers.com/showpost.php?p=27288357&postcount=1
Click to expand...
Click to collapse
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
lonegunman0 said:
I'm using method C, i still get that red triangle error. Also i can't get the ruu for my phone. I'm desperate can you please help me.
Click to expand...
Click to collapse
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Stock rom
mylegiscramped said:
If this many people are running into this problem, maybe we can get a role call of whose using what method, if not stock ROM what custom they are using, and what carrier they us?
I'm stock ROM, Stock Recovery, and Tmobile US. I used Method C.
I'm wondering if they have changed the update in a way that is preventing some people from updating. like it detects a certain file before update or something idk. I'm not any sort of advanced android user so I am probably wrong, but it's the first thing that comes to mind. Otherwise, maybe they sent out a bad update file, but I feel like that probably wouldn't be the case since it's been happening for a couple days now.
Thought's ideas anyone, or am I alone in any of these thoughts?
Click to expand...
Click to collapse
skidmarc11 said:
Im getting the same thing. Even after flashing "stock recovery" that i got from the modaco link, I can't update or even go into the stock recovery...I would absolutely love to enjoy the update too!
Click to expand...
Click to collapse
Yes i agree about the file detection. I'm running stock rom but i think i've just realised my problem. Although i have a stock rom my problem is that the stock rom i'm running is deodexed. I read somewhere that if the stock rom is tweaked in any way or if any bloatware is deleted you can't get OTA updates.
Hope this helped
Wouldn't an RUU fix any of those problems?
Yes it would
Sent from my HTC One S using xda app-developers app

[Q] Any idea why I can't update my phone?

I'm not able to post links so I've had to attach the images instead:
I have an HTC One XL - which I believe is from HK (when i reset to default, everything is in Chinese and the time/date is HK)
Since getting it in December, I've not been able to do a single update.
The software update gives me
update.png
after which i get this
fail1.jpg
So I've tried to bypass that and downloaded the OTA 4.1 rom and trying to flash gives me this
fail2.jpg
I also tried to do the RUU install and that failed too.
Any ideas?
I can't see your photos, they are coming up blank for me. But are you completely stock, or do you have custom recovery? Is your bootloader unlocked?
Phone needs to have stock recovery to install OTAs.
Bootloader needs to be LOCKED or RELOCKED to run RUU.
redpoint73 said:
I can't see your photos, they are coming up blank for me. But are you completely stock, or do you have custom recovery? Is your bootloader unlocked?
Phone needs to have stock recovery to install OTAs.
Bootloader needs to be LOCKED or RELOCKED to run RUU.
Click to expand...
Click to collapse
sorry, fixed the images as best as i can.
I'm completely on stock rom and i unlocked my bootloader this morning trying to update.
I'll try relocking it and flashing.
thanks
You are using cwm you need factory recovery to get ota
Sent from my VENOMized HoxL
area51avenger said:
You are using cwm you need factory recovery to get ota
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
alrighty. I was trying to backup my current rom, unlocked bootloader, lost everything but got cwm on.
Give me 10, i'll see what i can see and will update.
thanks
I give up!
I couldn't get it to work, flashed CM10 and found it buggy, gone back to stock and still no updates.
I've tried to update the hboot by using the JBFWTOOL and nothing happens, tried doing it manually and it fails (failed <remote: 99 unknown fail>
There must be a way, but I can't find it :crying:
kingkongballs said:
I give up!
I couldn't get it to work, flashed CM10 and found it buggy, gone back to stock and still no updates.
I've tried to update the hboot by using the JBFWTOOL and nothing happens, tried doing it manually and it fails (failed <remote: 99 unknown fail>
There must be a way, but I can't find it :crying:
Click to expand...
Click to collapse
maybe:
- status 7 mean your TWRP or CWM not suitable with rom, need update newest version (happened to me, and after update CWM is ok.)
- make sure you phone unlocked bootloader already.
- your zip file is error during dowload, re-download.
dktblade said:
maybe:
- status 7 mean your TWRP or CWM not suitable with rom, need update newest version (happened to me, and after update CWM is ok.)
- make sure you phone unlocked bootloader already.
- your zip file is error during dowload, re-download.
Click to expand...
Click to collapse
I was under the impression that i needed to remove CWM...
bootloader is unlocked however if i try to open any of the zip files, they are corrupted, but it's the same wherever i download them from.
so should I put cwm back on and try updating again?

Heartbleed vulnerability in Android 4.1.1

Google has officially stated that Android 4.1.1 is vulnerable:
http://googleonlinesecurity.blogspot.ca/2014/04/google-services-updated-to-address.html
This is a notice for anyone else on the Stock ROM as I am pretty sure this was the last supported update from HTC.
Pretty sure my wife's HTC One S (Ville) is on this version. Will verify when I get home. Time to root and flash her phone this weekend
Aceangel21 said:
Google has officially stated that Android 4.1.1 is vulnerable:
http://googleonlinesecurity.blogspot.ca/2014/04/google-services-updated-to-address.html
This is a notice for anyone else on the Stock ROM as I am pretty sure this was the last supported update from HTC.
Pretty sure my wife's HTC One S (Ville) is on this version. Will verify when I get home. Time to root and flash her phone this weekend
Click to expand...
Click to collapse
Anyway to patch this flaw myself using root access? I really don't have time to install and configure a new ROM...
I guess there is no official word from HTC neither...?
vacsed said:
Anyway to patch this flaw myself using root access? I really don't have time to install and configure a new ROM...
Click to expand...
Click to collapse
You could try this hack:
http://forum.xda-developers.com/showthread.php?p=51830870
rudolfm said:
You could try this hack:
http://forum.xda-developers.com/showthread.php?p=51830870
Click to expand...
Click to collapse
Could anyone with more programming skills than me try one of the following:
1) wrap this in a zip file we can flash from recovery
2) incorporate it into the Xposed framework
Many thanks if someone can accomplish this!
I think it's just HTC wanting us to buy new devices that's all.
Sent from my HTC One S using xda app-developers app
larrycl said:
Could anyone with more programming skills than me try one of the following:
1) wrap this in a zip file we can flash from recovery
2) incorporate it into the Xposed framework
Many thanks if someone can accomplish this!
Click to expand...
Click to collapse
Maybe you can try my patch: https://www.dropbox.com/s/tqxfjwwja3uaqsn/install-patch.zip
It uses a libssl.so from a LG Optimus L5 II (4.1.2) and it works on my TrekStor Surftab Ventos 10.1
If your device does't boot after you've installed it:
The patch creates a backup of your libssl.so at /system/libssl.backup.so, so just replace /system/lib/libssl.so with that backup file
Cheers, Xorg
Edit: updated link
HTC 800# When patch my One S 4.1.1: "I can't Comment"
Aceangel21 said:
Google has officially stated that Android 4.1.1 is vulnerable:
This is a notice for anyone else on the Stock ROM as I am pretty sure this was the last supported update from HTC.
Pretty sure my wife's HTC One S (Ville) is on this version. Will verify when I get home. Time to root and flash her phone this weekend
Click to expand...
Click to collapse
-- More or less revenue for HTC: Phonecon with HTC Toll Free#, US. Over 10 minutes tech reading to me how HTC is dedicated to security, ... customers .. asked when patch will issue for my 2012 HTC One S .. Answer: "I can't comment" .. Not planning on a 4th HTC in my life. /Ev :crying:
Link doesn't work
TheXorg said:
Maybe you can try my patch: http://tslink.tk/hb-inst-2
It uses a libssl.so from a LG Optimus L5 II (4.1.2) and it works on my TrekStor Surftab Ventos 10.1
If your device does't boot after you've installed it:
The patch creates a backup of your libssl.so at /system/libssl.backup.so, so just replace /system/lib/libssl.so with that backup file
Cheers, Xorg
Click to expand...
Click to collapse
Can you repost the link? I'd like to try it on my Archos 80 Titanium tablet. Stuck on 4.1.1 with no custom roms available for this tablet
htc is officially pushing heart bleed to t-mobile one s http://www.htc.com/us/go/htc-software-updates/
wendroid said:
Can you repost the link? I'd like to try it on my Archos 80 Titanium tablet. Stuck on 4.1.1 with no custom roms available for this tablet
Click to expand...
Click to collapse
New links:
New libssl.so: https://www.dropbox.com/s/wsg3a5ave2a8655/newssl.so
Flasheable ZIP: https://www.dropbox.com/s/tqxfjwwja3uaqsn/install-patch.zip
Sent from my Nexus 4 using XDA Premium 4 mobile app
Thank you so much! I will try this soon
The OTA for T-Mobile is out.
http://support.t-mobile.com/docs/DOC-4262
dr3amsINdigital said:
The OTA for T-Mobile is out.
http://support.t-mobile.com/docs/DOC-4262
Click to expand...
Click to collapse
Do NOT update via the OTA update! It put me through a constant reboot cycle and I had to factory reset...
th3pr1nc30f3gypt said:
Do NOT update via the OTA update! It put me through a constant reboot cycle and I had to factory reset...
Click to expand...
Click to collapse
Did you have a custom recovery installed?
dr3amsINdigital said:
Did you have a custom recovery installed?
Click to expand...
Click to collapse
Yes now what?
knickerblogger said:
Yes now what?
Click to expand...
Click to collapse
I'm not sure how to fix it, but this is why you're not supposed to install OTAs if you're not on stock recovery.
Sent from my iPad using Tapatalk
I'm s off, have twrp installed and on stock ROM. Would like to install this update, or get a 4.2.2 or 4.3 stable fully functional ROM. Do you think flashing stock recovery and then ota would work even if I'm s off. Should still be able to boot an ruu from fastboot even if I boot loop. Suggestions on custom roms?
Edit: Used flashalot's recovery switcher to flash stock recovery, rebooted, then flashed the ota update. After update I lost root, but still have s off.
Plan on fastboot flashing another recovery, then flashing su binary again from the new recovery.
Hope this helps.
Sent from my HTC VLE_U using XDA Free mobile app
Anyone interested in that OTA zip ?
Sent from my HTC VLE_U using Tapatalk
---------- Post added at 09:54 AM ---------- Previous post was at 09:38 AM ----------
This might help...
If you have the OTA.zip file... but custom recovery and such like TMUS application removed..
This will wipe your phone. Making a backup is not optional !!!
http://sadevil.org/blog/2012/12/23/manually-flashing-an-ota-update/
This looks somewhat straight forward.. If you want to get the OTA downloaded:
got to settings .. and manage to get the software update.. It will download eventually into your Download folder ..
Do not Apply the OTA at this point.. select install later!!!
pull the file on your PC/Mac/Linux box and modify as described in the URL above..
reboot your phone and the OTA should not bother you ... if you have pulled (like in remove) or at least renamed the OTA file..
Before you push Firmware.. and such make sure you have made a backup with CWM !!! or whatever method you are using!!!
also make sure you have your custom recovery image somewhere available and maybe a su.zip cwm file as you may loose root as well.. not sure..
If you have rooted your HTC one S your self - this should not be hard to DIY..
Currently I am at work and cannot try it out myself .. but definitly will do it once back at home later..
Godspeed to all of you brave hackers..
Superchill11 said:
I'm s off, have twrp installed and on stock ROM. Would like to install this update, or get a 4.2.2 or 4.3 stable fully functional ROM. Do you think flashing stock recovery and then ota would work even if I'm s off. Should still be able to boot an ruu from fastboot even if I boot loop. Suggestions on custom roms?
Edit: Used flashalot's recovery switcher to flash stock recovery, rebooted, then flashed the ota update. After update I lost root, but still have s off.
Plan on fastboot flashing another recovery, then flashing su binary again from the new recovery.
Hope this helps.
Sent from my HTC VLE_U using XDA Free mobile app
Click to expand...
Click to collapse
Same situation here. Stock ROM and Rooted and S-off. Constant nag to apply the OTA update but not working. Looking for a way to do it easy. How should I proceed? Don't want to wipe the phone and create all my settings again if possible. Can I reverse S-Off and apply OTA update somehow?
can any one provide me a link to the ota update

Categories

Resources