As reported here and on SU, the maintenance update from Sprint/HTC is being rolled out over the air. Can people with Root and/or a custom ROM tell us what happens if you update? I doubt you'll loose root but I'm just curious and I'm sure other are too.
This is only for rooted users. No need to post if the update isn't available to you yet. IF it works for you and you're rooted/rom'ed, post.
Root: Yes or No
ROM: Tell us which
Reuslts: Still rooted, working fine?
As for me, the update isn't available yet but I want to know what I'm getting in to before I allow it.
EDIT: So far it looks like the update won't even install for rooted users - Recovery image gets in the way...
EDIT2: freshlyill has provided a direct download of the update pkg file in post #7
EDIT3: This update definitely cannot be made on rooted Heros but doesn't hurt the phone if you try. No risk.
EDIT4: UPDATE: SUCCESS! thecodemonk has confirmed that root is still available on page 4. Process: Use stock RUU to bring it back to stock, download and apply update, re-root like normal!
EDIT5: Satinkzo has also confirmed that the above works. Now, somebody ROM this sucker up
Im rooted on Fresh ROM. Dl the update now, at about 20%...
I cannot get it to install on rooted phone. Looks like the recovery image or something gets in the way.
freshlyill (from fresh rom) got the update and also said it seemed to error out because of the recovery image. But he rebooted again and it appeared to work. He still has root but has no signs that the update applied. Still getting wake lock on stock messaging app.
No firmware update available for my phone yet.
Decided to take the plunge since I nandroided recently...whee! (going about 1%/second ^_^)
same here. Rooted with no custom rom. Won't take the update.
here's the update..
http://rapidshare.com/files/308943608/update.pkg
Rooted: Yes
Custom ROM: No
Results: Failed to update with the following message:
Welcome
Build : RA-heroc-v1.2.3
Finding Update Package
Opening Update Package
Verifying Update Package
E:No signature (265 files)
E: Verification failed
Installation aborted
At this point I select reboot system now and it boots normally to the old firmware.
ElAguila said:
Rooted: Yes
Custom ROM: No
Results: Failed to update with the following message:
Welcome
Build : RA-heroc-v1.2.3
Finding Update Package
Opening Update Package
Verifying Update Package
E:No signature (265 files)
E: Verification failed
Installation aborted
At this point I select reboot system now and it boots normally to the old firmware.
Click to expand...
Click to collapse
Same here, but using Fresh ROM
@Fresh: how did you get the update to take?
Same as ElAguila
ElAguila said:
Rooted: Yes
Custom ROM: No
Results: Failed to update with the following message:
Welcome
Build : RA-heroc-v1.2.3
Finding Update Package
Opening Update Package
Verifying Update Package
E:No signature (265 files)
E: Verification failed
Installation aborted
At this point I select reboot system now and it boots normally to the old firmware.
Click to expand...
Click to collapse
Ditto...I'm going to nandroid, RUU, then apply the update and see if I can re-root from there. I'll let ya know (assuming someone doesn't beat me to it)
Verification failed here as well.
thecodemonk said:
Ditto...I'm going to nandroid, RUU, then apply the update and see if I can re-root from there. I'll let ya know (assuming someone doesn't beat me to it)
Click to expand...
Click to collapse
I'm in that process right now just to test. You might beat me though
thecodemonk said:
Ditto...I'm going to nandroid, RUU, then apply the update and see if I can re-root from there. I'll let ya know (assuming someone doesn't beat me to it)
Click to expand...
Click to collapse
Good luck solder lol i would not risk loosing root.
shouldn't we wait to include this in a custom rom? Sense no one rooted has this update we cant get a Nand backup of it
Satinkzo said:
I'm in that process right now just to test. You might beat me though
Click to expand...
Click to collapse
The reason it won't work is that the rooted image has testkeys and the stock image has release keys. You don't want to apply the maintenance update on a rooted phone in any manner. The purpose of the maintenance release, from what I've heard, is to fill the hole that makes root possible.
I downloaded and opened the update.pkg and it is just a zipped file. I wonder if it would be possible to push it with adb?
Negrito said:
Same here.
@Fresh: how did you get the update to take?
Click to expand...
Click to collapse
i didn't.. i just found the update.pkg after downloading, update didnt install though. i'm facing same problems. looking like we will have to flash back to stock then root again..
kylez64 said:
Good luck solder lol i would not risk loosing root.
shouldn't we wait to include this in a custom rom? Sense no one rooted has this update we cant get a Nand backup of it
Click to expand...
Click to collapse
It's actually not as dangerous as it sounds since I can always RUU back to the vulnerable version and nandroid restore.
EDIT: Status...RUU complete, applying update now.
chicojd said:
The reason it won't work is that the rooted image has testkeys and the stock image has release keys. You don't want to apply the maintenance update on a rooted phone in any manner. The purpose of the maintenance release, from what I've heard, is to fill the hole that makes root possible.
Click to expand...
Click to collapse
If that is the case then you don't want this MR if you want to stay rooted then. I was kind of hoping that wasn't the case with this MR.
freshlyill said:
i didn't.. i just found the update.pkg after downloading, update didnt install though. i'm facing same problems. looking like we will have to flash back to stock then root again..
Click to expand...
Click to collapse
My mistake, i misread 'flipz' post.
For the few days ive been trying to get the OTA to install correctly.
I have seen other people talking about this, and i have tried all i could find about this problem.I
m not sure if im posting this in the correct place, sorry if nok!
I did find out its because of the used custom recovery that it wont install.
So using the allinone tool i put the stock recovery on, i believe with succes.
And i had also installed the ota rootkeeper app (not sure why)
But the OTA keeps on reporting errors when installing
assert failed apply patch check /system/app/phonesky.odex (long numbers)
E: error in internal sdcard/download/ota-ville u htc europe 1784012-1.53401.2 release-numberrapskwje.zip
status 7
aborted
I tried (in stock recoverymode) installing a zipfile i found somewhere which was the 1.78..update (I think) but that also gave errors, i cant find a ruu for 1.78, so cant try that.
Is there a complete list of things you have to do to get this update? and if so can someone help, thanks.
Lacuna666 said:
For the few days ive been trying to get the OTA to install correctly.
I have seen other people talking about this, and i have tried all i could find about this problem.Im not sure if im posting this in the correct place, sorry if nok!
I did find out its because of the used custom recovery that it wont install.
So using the allinone tool i put the stock recovery on, i believe with succes.
And i had also installed the ota rootkeeper app (not sure why)
But the OTA keeps on reporting errors when installing
assert failed apply patch check /system/app/phonesky.odex (long numbers)
E: error in internal sdcard/download/ota-ville u htc europe 1784012-1.53401.2 release-numberrapskwje.zip
status 7
aborted
I tried (in stock recoverymode) installing a zipfile i found somewhere which was the 1.78..update (I think) but that also gave errors, i cant find a ruu for 1.78, so cant try that.
Is there a complete list of things you have to do to get this update? and if so can someone help, thanks.
Click to expand...
Click to collapse
Retry to install Rootkeeper or u can do it later
Use this tool: [TOOL] HTC One S All-In-One Toolkit V1.0 (find at Android Development). Boot to fastboot mode then reflash the "STOCK RECOVERY"
After that go to Setting-About-Software Update and install it with the choice "install now".u get it.
if u didn't use RootKepper,just re-root again with the same tool.
Have Fun.
After that go to Setting-About-Software Update and install it with the choice "install now".u get it.
Thanks, but I dont undersstand your answer.
Are you saying to : do the OTA update just after flashing the stock recovery?
Thats exactly what i did.
That was exactly what i did too.
so u can try re-flash the shipp Rom at "[ROM]Ville Shipped ROM Collection" (Thread of Football, at Development).then do it again.
Coz i think the Problem is at ur Stock Recovery.mb there is smth not right there...
i did exactly what i wrote and it worked for me.
Good luck!
Ok, i will try :
using the europe 1.53 ruu(from post from "Football")
then use the all_in_one tool to put the stock-recovery back again
then try the OTA again
i will let you know later on,..thank you
I ran the europe 1.53 ruu(from post from "Football")
After a while it said error 155 image update error, get correct image
I still have no idea how to get the 1.78 update,
Can anyone help please?
=====> Never mind, luckily today football released a 1.78 basis rom which does work for me
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
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?
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