Related
Good evening/morning all
Just grabbed this new OTA from my One S so i thought i would make an appearance... And before anyone asks, yes - I am working on a ROM
OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2
Please note: This OTA takes you from 1.53.401.2 to 1.78.401.2
Change log from the updater service (rather vague):
System enhancment
Enjoy
P.S > Had no time to analyse the actual content but the OTA contains full firmware updates including HBoot & Radio.
Edit: Just noticed paul has done a repack of the base already.. may still come in handy for you devs out there
I knew you would come just like I asked for and others.
Thanks Lee.
If you can work on a T-Mobile ROM/EU ROM.
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Can't wait for some goodness from you!
Sent from my US HTC One S using Tapatalk 2
Dimson75 said:
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Click to expand...
Click to collapse
Certainly will be
Sent from my LeeDrOiD One Xtreme loaded HTC One X
woohoo !! about time you made an appearance !! I knew you was hanging around here somewhere
missed you since i left the sensation forums
I know this is probably a really stupid question but I'm going to ask anyway...
Can you actually install an OTA package on the phone somehow or is it just useful to take files out of it?
And the other question, my phone doesn't find any OTA updates anymore since I've 'tampered' with it so is there a way to make it find and install the OTA updates again?
Thanks
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
LeeDroid said:
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
Click to expand...
Click to collapse
The other thing is that when I try installing the stock RUU it's telling me it's for the wrong device or something like that, although it's definitelly the correct RUU.
Also, my phone is HTCDev unlocked but is still S-ON so if I install the OTA package usign CWM is it going to update the radio and the hboot (I thought it can't do that if you're S-ON)?
Thanks
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Did'nt work for me, wrong CID...
edit the info.txt to match your CID
azzledazzle said:
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Click to expand...
Click to collapse
Ok, maybe I'm not getting this right but I'm talking about two separate things:
Issue 1. My understanding is that I can install the OTA zip package using ClockworkMod, is that correct?
Issue 2. The RUU package won't install on my phone:
i) I have restored via ClockworkMod the nandroid image of the stock ROM (image that I've taken straight after I unlocked the boot loader and flashed a custom recovery, but before I rooted the phone). Then, I flashed the stock recovery image using fastboot. So now my phone should be back to stock.
ii) I then tried to install RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
When I do this, the RUU goes through right up to the step where it says 'Updating signatures' and then it stops saying 'unknown error' and it leaves my phone on that screen with black background and white HTC logo. Then, I have to hard boot and the phone starts up fine but in the state it was before the RUU - not even the user data is missing. To me this means that for some reason it doesn't even try to flash the RUU onto the phone but it stops when checking the signatures - I just can't understand why this is happening...
Can you help?
Thanks
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
azzledazzle said:
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
Click to expand...
Click to collapse
Sorry for my ignorance, but how do I initiate the installation of the OTA zip package using the stock recovery? As I said, I can't actually get it 'over the air' but I've just downloaded the zip package from this thread...
ok put the package on your sd card.
boot into fastboot, flash the stock recovery using the command ''fastboot flash recovery recovery.img'' (or recovery_signed.img) (also no quotes)
when thats done, select recovery from fastboot using volume button..
When you get a red ! press volume UP and power button, That will take you into stock recovery
Then look for the option, install from sd card or something like that
select your OTA package and BOOM !!! job done
Reflash CWM and away you go
Damn... I had no idea that you can actually get into the menu of the stock recovery... It all makes sense now...
me neither till about 3 days ago
I might not seem like a noob,,,,,but deep down i am
azzledazzle said:
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
Click to expand...
Click to collapse
I've tried that again and it actually breaks down when it gets to 'Checking Header...' and it exits with 'ERROR [155]: UNKNOWN ERROR". Maybe this is a bit more specific...
this is what i found for error 155
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Alternatively (in some cases) right click on the file and choose "Run as Administrator".
Or use the rom.zip -> PGXXIMG.zip flashing method.
Click to expand...
Click to collapse
I dont know if it will fail when flashing the rom.zip in CWM - usually you have to rename it to the model number and flash in fastboot, however you cant do this with S-ON
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)
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 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
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
VictorCic said:
Hi guys, a few day ago my One SV had some problems, rebooting itself and runs very slowly; so i tryed to do something like root it, but not knowing what i'm doing 'cause i don't have much time.
Probably installing a wrong rom, now I'm stuck in the bootloader with S-ON Tampered, Locked, and Security Warning flags.
The phone stuck with htc logo, i only manage to go into bootloader, pdanet gives me sync error, twrp recovery doesn't work anymore.
Is there something I can do now?
Click to expand...
Click to collapse
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
old.splatterhand said:
As long as your device is Locked, you can't flash a custom recovery.
So unlock your device at htcdev.com, flash Twrp recovery and flash back a working rom.
Use a Android 4.1.2 rom, otherwise you will have problems with noisy sound.
Click to expand...
Click to collapse
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
VictorCic said:
Thanks, i've unlocked it and flashed Twrp recovery, but trying to using this last one always says unable to mount sd...
And could you help me to find the right rom or stock rom?
And trying to put it in s-off with revone, rumrunner, moonshine doensn't work
Thank you very much!
Click to expand...
Click to collapse
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
old.splatterhand said:
How do you mount the sd?
At least pull it out of your device and put it into your PC and copy needed files in this way.
One thing i could not solve earlier (because of bad internet connection): did you already install the Android 4.2.2 update or what was your software running on your device before? Thats important to give you the right rom for your firmware!
I'll give you the links anyway:
4.1.2 -> http://forum.xda-developers.com/showthread.php?t=2254384
4.2.2 -> http://forum.xda-developers.com/showthread.php?t=2512742
Rumrunner & moonshine are confirmed working for your hboot, but which you should use at least also depends on your previous software.
Click to expand...
Click to collapse
Im sorry That error is from the twrp recovery when i try to install superuser.. It says unable to mount int sd.. I think internal memory
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
old.splatterhand said:
Ignore it. Only use the files, recommended in my index thread (use SuperSu, not Superuser), link in my signature.
And answer the other question.
Click to expand...
Click to collapse
Sorry i had update it to 4.2.2
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
old.splatterhand said:
Ok, so you can use the second link for the stock rom. And rumrunner for S-off.
Click to expand...
Click to collapse
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
VictorCic said:
I installed the 4.2.2 versions, seems completed but phone remains with black screen showing only the top bar with the clock, then reboot itself; sometimes after reboot it shows the bottom clock and lock, you can also unlock it, but then it reboots;
One time it shows me the backgroud.
Maybe it's a motherboard problem, what do you think?
Thanks
Click to expand...
Click to collapse
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
VictorCic said:
Yes, flashed boot.img and wipe data/cache/dalvik.
Later i'm gonna try the 4.1.2.. I hope that will work
Click to expand...
Click to collapse
old.splatterhand said:
Have you flashed the boot.img with fastboot? Did you wipe everything before?
May give the 4.1.2 rom a try.
Click to expand...
Click to collapse
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
VictorCic said:
installed the 4.1.2 version..same as before (black screen, only the first time turned on it showed the background), apart it can show every time the ring to unlock the screen; unlocking it it reboot itself...
Click to expand...
Click to collapse
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
old.splatterhand said:
Stop. Did you only wipe data/cache/dalvik.
No system?
You need to wipe all, except internal & external sd!
Click to expand...
Click to collapse
Also system yes. And if i wiped the internal sd?
anyway after installing the rom, from twrp internal storage is 0 MB
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
old.splatterhand said:
Then i'm running out of ideas
As the roms worked for other people, i also start thinking thats something bugged with your device.
You checked md5sum of the roms? Using latest TWRP recovery?
Click to expand...
Click to collapse
Yes, used the latest TWRP recovery.
the recovery say to me no md5 file, is this the problem?
How can I check the md5 now?
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
old.splatterhand said:
I don't know the name of the tool (i'm at work), but you will find it with google search, i think.
In recovery this is not a problem, its only to check on your pc, if the downloaded file is the same as the upload.
Click to expand...
Click to collapse
Checked, the codes matches..
Then i think your device has a defect
old.splatterhand said:
Then i think your device has a defect
Click to expand...
Click to collapse
Hi, i managed to change the motherboard, so trying to put a mod, the phone now stuck on the htc logo...
I unlocked it with htcdev, then installed the recovery but this one doesn't work, it says starting recovery but doesn't start..(trying to install a different recovery, it seems unable to rewrite it)
trying to do something i flashed with fastboot the stock boot.img and now the phone doesn't start anymore..
what can i do now? :crying: