Database Info

[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] Procedure following bootloader unlock?

Hi,
I recently unlocked my bootloader follow this tutorial: http://forum.xda-developers.com/showthread.php?t=1952038
It looks like I did it successfully, but my phone seems to have been restored. During the process the phone automatically made two backups, and I was wondering if it is possible to restore those, or if I just have to re-download everything.
Also now that my bootloader is unlocked, does that mean I'm rooted? What other steps do I need to do to get superuser or be actually rooted.
Thanks!

the backups are for you to remove the supercid. you need to hold onto those two backups[assuming they are mmcblk0p4MOD and mmcblk0p4ORIG] and your Unlock_code.bin you need to keep those 3 files. you will probably only ever use Unlock_code.bin if you need to run ruu at anytime. in order to restore the other two files you do this process [2.20 Firmware] Remove Pesky root.
what you actually need to do now is "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img" from TWRP 2.3 - HTC One X (ATT/evita) then flash this [29.08.2012] SuperSU v0.96 that will flash your twrp recovery and give you root. once you do that you can make modifications to your stock rom or ability to flash custom roms.
Remember to NEVER factory reset in bootloader or your will corrupt your sdcard.

DvineLord said:
the backups are for you to remove the supercid. you need to hold onto those two backups[assuming they are mmcblk0p4MOD and mmcblk0p4ORIG] and your Unlock_code.bin you need to keep those 3 files. you will probably only ever use Unlock_code.bin if you need to run ruu at anytime. in order to restore the other two files you do this process [2.20 Firmware] Remove Pesky root.
what you actually need to do now is "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img" from TWRP 2.3 - HTC One X (ATT/evita) then flash this [29.08.2012] SuperSU v0.96 that will flash your twrp recovery and give you root. once you do that you can make modifications to your stock rom or ability to flash custom roms.
Remember to NEVER factory reset in bootloader or your will corrupt your sdcard.
Click to expand...
Click to collapse
I did the "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img" using this tutorial: http://forum.xda-developers.com/showthread.php?t=1952076
but I don't notice any changes on the phone. Also, I'm unaware what the 'flashing' terminology is. Is there any way I can pay you a bit to show me how on teamviewer? I'm very unacknowledged with this topic and don't want to ruin a second HTC One X. :/
And also, is there no way to get my files back while keeping my bootloader unlocked? Or should I re-add all my songs and apps?

therealbzb said:
I did the "fastboot flash recovery openrecovery-twrp-2.3.1.0-evita.img" using this tutorial: http://forum.xda-developers.com/showthread.php?t=1952076
but I don't notice any changes on the phone. Also, I'm unaware what the 'flashing' terminology is. Is there any way I can pay you a bit to show me how on teamviewer? I'm very unacknowledged with this topic and don't want to ruin a second HTC One X. :/
And also, is there no way to get my files back while keeping my bootloader unlocked? Or should I re-add all my songs and apps?
Click to expand...
Click to collapse
I'll help you out. PM your teamviewer stuff
Free of charge - your money's no good here.

you cant recover you data from unlock or wipe

Fix for Stuck at HTC logo, after Font install fail?

I use official ICS, but I root my mobile and s-off. All works exelent. But I yesterday instal from google play ,,font instaler *root*,, and I check some font, click install, then reboot. Reboot cant be succeful. Stuck on htc logo. Now I just can open cwm recovery. I try wipe(all), factory reset, instal another custom rom, then I tried to instal RUU from hboot (I put PG88IMG.zip on sd card) loading succesful, but when he try to instal show for secund ,,PARSING.....PG88IMG.zip.... and back me on home hboot. Now when I try to on my phone After first htc logo show ,,black,,....no go... WHAT TO DO :crying: HELP ME PLEASE....
hboot 2.02.0002
Unlocked
S-ON

Are you using hboot 7.00?

teadrinker said:
Are you using hboot 7.00?
Click to expand...
Click to collapse
No, I use hboot 2.02.0002.

milosrdni94 said:
No, I use hboot 2.02.0002.
Click to expand...
Click to collapse
1) with this hboot you cannot be S-OFF (except with XTC Clip)
2) use the ICS RUU it should bring your phone back (but not as PG88IMG - just run the exe on your PC with a phone connected and in FASBOOT USB mode)
If the ICS RUU cannot restore your system you most probably have a faulty eMMC

amidabuddha said:
1) with this hboot you cannot be S-OFF (except with XTC Clip)
2) use the ICS RUU it should bring your phone back (but not as PG88IMG - just run the exe on your PC with a phone connected and in FASBOOT USB mode)
If the ICS RUU cannot restore your system you most probably have a faulty eMMC
Click to expand...
Click to collapse
1)I see wrong, is S-ON.
2) I try this, and on my pc show message ,, error conect,,. Maybe because dont turn on usb debuging?
here is app>>> https://play.google.com/store/apps/...SwxLDEsImNvbS5qcnVtbXkuZm9udC5pbnN0YWxsZXIiXQ.. read a worning mesage...

Connect to PC, reboot to bootloader and then select FASTBOOT with the volume buttons and press POWER button. You should see "FASTBOOT USB" written on the screen of the phone. Then run the ICS RUU
Sent from my HTC Desire S

I now try to instal ruu from PC. strart good, done some proces susceful, and when come ,,*something signature,, tu izbaci gresku. When I unplug usb on hboot show me message ,, ruu security faild,,..... What to do? Please help me.... Do something from CWM ?

You have to lock the bootloader as well:
fastboot oem lock
Sent from my HTC Desire S

amidabuddha said:
You have to lock the bootloader as well:
fastboot oem lock
Sent from my HTC Desire S
Click to expand...
Click to collapse
What you mean exactly? I dont understood what I to do now?

Can anyone help me? Please :crying:
This is a message from author of apk FONT INSTALER >>> Hey Lazar,
I sincerely apologize that your device is currently “soft bricked”. It’s never fun to have your device temporarily not working and I hope I can help you as best as possible.
When someone roots their device there is always a possibility of things going wrong. 99.9% of the time the device is easy to get back up and running. It does take some research to figure out exactly what needs to be done.
For this reason, our apps all include warnings of creating a nandroid backup before messing with the customization options.
When modifying system files a factory reset will not fix the device. This is because the factory reset wipes your data partition but your system is left untouched.
The easiest way to fix your device is to restore a “nandroid” backup in recovery. When a user roots his/her device a custom recovery, like clockworkmod recovery, is usually installed. In recovery you can create backups and restore your whole device to a previous state. If you created a nandroid backup and have a custom recovery please try to restore that backup in recovery. This will restore your system to a previous state and your device should be working again.
If you don’t have a nandroid backup but you do have a custom recovery you can install a ROM. There are many ROMs that can be found on xda-developers.com and rootzwiki.com. Installing a ROM in recovery will overwrite your system files and your device should then be working again.
If you don’t have a custom recovery installed then we are limited to our last option. Many manufacturers provide ways to restore the entire device. For devices made by Motorola this process involves using a “SBF” or “FXZ” and “RSD Lite”. Samsung uses “ODIN” and other devices may “fastboot flash” their device. I cannot provide great assistance here and your best option is to sign up on an Android forum and ask users who have your same device for help. I simply don’t know every process for every device and wish I could be more helpful. xda-developers.com and rootzwiki.com have many help forums and users willing to provide assistance. Also, usually if you just google “unbrick <your device>” then you can find a guide on how to fix your device.
Again, I apologize for the inconvenience and hope that the info I provided helps you out.

Can someone send me nandroid backup (ICS official wit htc sense) to try soft unbrick my desire s.

milosrdni94 said:
Can someone send me nandroid backup (ICS official wit htc sense) to try soft unbrick my desire s.
Click to expand...
Click to collapse
No!! What use would it be. Simply flash the ROM correctly. Read in the Stickies and Index thread, everything you need is in there.

How to apply OTA update on Rooted At&t One X

Hi,
I have this AT&T one x, (I m using on NON AT&T network), so cant have an ota update.
Looking at few forums, downloaded the OTA version on XDA (631 Mb)
Saw people writing, that just rename the file to update.zip and then go to recovery and choose install from internal memory.
That dint work for me.
Error: not able to mount sd mem
Then few people wrote to choose install from external mem.
That dint work either.
Error: not able to mount sd mem
Then saw few people saying that I need to root my device and unlock bootloader.
I dint that, and tried from bootlaoder to install from zip.
That also dint work.
Now saw, I few wrote that i need to be S - OFF.
Which I tried doing it, but i m not able to do s-off for myself.
Pls pls pls.... can any of you EXPERTs out here help me.
Waited like for AT&T to release the update, now when it is out, i m not able to make it through.
Your step by step instruction would be highly appreciable.

Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460

redpoint73 said:
Be aware, that if you have the AT&T version, and you are rooted, then you probably have SuperCID (in fact, you must have SuperCID, unless it was already changed back). If you have SuperCID you must S-off (or return to the AT&T CID) before applying the OTA, or you will brick your phone!
I am not all that familiar with the process to install using OTA.zip (and haven't done it myself), but it was discussed in these threads:
http://forum.xda-developers.com/showthread.php?t=2180408
forum.xda-developers.com/showthread.php?t=1701460
Click to expand...
Click to collapse
How to S Off ATT HOX???
Thats the big question.
I have rooted my phone through one click TWRP Toolkit.

abhishek jain said:
How to S Off ATT HOX???
Thats the big question.
Click to expand...
Click to collapse
No, that is a very small question. Or at least a very easy one to answer.
Take 5 minutes to look around before asking "big" questions: http://forum.xda-developers.com/showthread.php?t=1671237
http://forum.xda-developers.com/showthread.php?t=2136172

If you would read my first post, I have already posted that I tried doing that was not able to do.
On the third comment that we need push in , where it given an error 92 or something like that, I dint got that.
Tried many times and then it became a "big" for me.
We all are born not experts in every field.
So before comenting pls try to know what's behind it
Sent from my HTC One X using xda app-developers app

Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right

a box of kittens said:
Lol it doesn't take an expert to read and take five mins..this is probably one if the easiest s off methods you'll see for awhile... You probably didn't set up your adb fastboot environment up right
Click to expand...
Click to collapse
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded

abhishek jain said:
Changed my laptop and tried again.
Now I am S-OFF
THough I applied the same comments on three different machine.
4th Time it worked.
Now how to install this OTA updated which I have downlaoded
Click to expand...
Click to collapse
Anyone to help me out in this case:
I am S OFF
Rooted
Unlocked bootloader
AT&T HOX on non AT&T network
631 mb update.zip
Looking top update

Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.

iElvis said:
Rename file update.zip and copy to internal storage.
Reboot to bootloader and enter recovery.
Push power+ vol up when recovery screen appears to enter recovery dialog.
Ignore errors.
Select install from internal storage
Select update.zip
Phone will reboot a couple of times.
Click to expand...
Click to collapse
I tried this method couple of time before : unlocking, rooting and S-off ing
In this case , do i need to relock my bootloader and stock recovery?
If yes, where can i find stock recovery, i have deleted it.

By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.

iElvis said:
By "i deleted it" do you mean you installed a custom recovery? If so, yes you need to get stock recovery back on.
Only way I know of to reinstall stock recovery is to run the 2.20 ruu. Since you're s-off, you don't need to relock; just run it.
Click to expand...
Click to collapse
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock

abhishek jain said:
I am not a techie but as far as i know, i have not installed a custom recovery.
I did TWRP tool kit, rooting and unlocking bootloader.
How can see if i am custom recovery or stock
Click to expand...
Click to collapse
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.

iElvis said:
You probably have a custom recovery. Reboot to bootloader and select recovery and see what you get. If it's TWRP, you'll get a teamwin splash screen and then some options. Stock recovery will just show a screen with a green circle.
Click to expand...
Click to collapse
Then I have custome recovery.
Could you gimme a link for stock recovery image

I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.

iElvis said:
I do not know if one is available. I have never seen one posted. Running a ruu will put it back on.
Click to expand...
Click to collapse
Yes now i have got my phone updated with the OTA update

abhishek jain said:
Yes now i have got my phone updated with the OTA update
Click to expand...
Click to collapse
Please click "Thanks" if anyone in the thread helped you.

iElvis said:
Please click "Thanks" if anyone in the thread helped you.
Click to expand...
Click to collapse
I have already done that.
And now in case anyone needs help, i can help those people out.
Coz the method is simple, but it is not at all explained clearly in any of the threads.
It has come in bit and pieces.

I have noticed one thing.
That after installing the update and again unlockin the bootloader and rooting, I am not able to see "TAMPERED" being written in the boatloader.
Also, now when I am rooted and also have SU permission, I m not able to switch on my WiFi tether with the files mentioned in the thread
http://forum.xda-developers.com/showthread.php?t=1677261

The "TAMPERED" flag goes away when you're s-off and flash a new hboot.
I believe wifi tether is blocked on the new AT&T base. You can flash a custom rom on the 3.17 base and it should work.

[Q] Totally stuck - Desire S. cant boot :(

Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
HTC Desire S GSM
unclocked via htcdev
S-ON
hboot: 2.02.0002
Radio: 3831.19.00.110
Latest CMWR
Gets stuck @ white screen
Tried:
factory reset / wipe / dalvik / batt stats
reboot to recovery: install SU, gapps, cwm rom 10.1 (also tried 7.1). reboot / then fastboot boot boot.img (from the CWM zip). nothing.
Ive tried re installing the EU RUU - also nothing. Renaming the rom.zip to PG**IMG.zip, it reading the file then stops 2 fastboot screen. nothing. nada.zip.

fstarockr said:
Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
Click to expand...
Click to collapse
There are so many people, blindly walking in to troubles just because they do not read,
and you seem to be one of them....
When you unlock your device via htc dev, your device stays s- on,
it means- whatever you flash, you have to flash boot.img from that thing ( meaning rom naturaly )
via fastboot
through command:
fastboot flash boot boot .img
Without it your phone will never boot...
Recovery you flash via fastboot as well via command:
fastboot flash recovery recovery.img
Then , when you have it, reboot your device to recovery
and flash superuser and its binaries
And that woud be all you have to do in order to have rooted and booting device...
Edit: Now i've seen your other post- it is a 100% the one im reading now,
You should know it is enough to post your question once,
people'll find it...
Because of impatience you're in trouble already with your phone

tx -
tx for that info - ill give it a go.
I reposted because some1 there said i was in the wrong section and supplied a link for the correct section (here) - so yes, i reposted to get the correct replies.
not to digress:
but as for not reading - i can assure u ive read alot. Been a freelance developer for 15 years. That doesnt mean that rooting often requires a handful of little hacks when things dont go smooth. Just like alot of programming tuts, the rooting ones have a similar "assumption" that u know whats half potting, and what will cause what and what wont. All the articles i read i made sure were either 2012 or 2013 - there is ALOT of old non applicable info around, I stick to xda of course as i really trust this place. as usual, not all is 1-2-3. thats all.
asgardr said:
There are so many people, blindly walking in to troubles just because they do not read,
and you seem to be one of them....
When you unlock your device via htc dev, your device stays s- on,
it means- whatever you flash, you have to flash boot.img from that thing ( meaning rom naturaly )
via fastboot
through command:
fastboot flash boot boot .img
Without it your phone will never boot...
Recovery you flash via fastboot as well via command:
fastboot flash recovery recovery.img
Then , when you have it, reboot your device to recovery
and flash superuser and its binaries
And that woud be all you have to do in order to have rooted and booting device...
Edit: Now i've seen your other post- it is a 100% the one im reading now,
You should know it is enough to post your question once,
people'll find it...
Because of impatience you're in trouble already with your phone
Click to expand...
Click to collapse

Well thats true, obvious things for me do not have to be obvious for
somebody else- one sometimes forgets that- begging your pardon
If not for XDA, i'd've known not much at all...
I've given the shortest and simpliest way that never failed me before
so, i truly hope, for you it'll turn out to be usefull as well- with no further accidents...
As for comming back to stock: you must relock device's bootloader before flashing,
otherwise procedure will always be throwing an error....
Success

details details
As for coming back to stock: you must relock device's bootloader before flashing,
otherwise procedure will always be throwing an error....
Im trying to get a picture of the inter relations ~ pls bear with me:i dont want to be trying to sys c: when i dont have a partition kind of scenario - absolute clarity is needed - my apologies as i try wrap this up..
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
#S-on/Off
I have been unable to get mine to off -
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Im trying to figure out what i can do once, and what i have to keep fiddling with, so i can hone in and get up and running.
If my questions appear ignorant - then ignore me. Im trying to paint a very clear picture of the tech relations between the various aspects and how they relate / interact - which is crucial to moving on from noobness - so pls bear with me and drop the remarks / attitude. Ive read my a$$ off and am still unclear for what many assume is basic understanding.
Im sure there are ALOT of sane unlazy logic ppl out there stuck in the same boat - and sometimes ppl who are VERY knowledgeable get a bit semi-aggressive putting ppl off from asking questions.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Success[/QUOTE]

fstarockr said:
Hi all. Ive finally managed to get a grasp of the principles of adb, shell, fastboot, etc.
Anyways - I have a Desire S which I unlocked via htcdev, and installer the lastest clockworkmod recovery. ive been trying to get S-off and nothing has worked for me. Ive spent the last 2 days downloading so much stuff my desktop if full of it - and im nowhere.
I had ICS for htc running before without any mods and wanted to try the root / mod thing.
My phone hangs at the htc boot screen. I have tried installing 3 different cw10.1 zip files all from xda to no avail, they always give me an error. Ive tried running the RUU exe and it ends in an error. I then fund the rom.zip file in the directory and renamed it to PB99IMG.zip, dropped it in root of sdcard and nothing.. it just skips past the lines and goes to fastboot. Should it not be named PB88IMG.zip? I recall seeing those numbers flit past.
Is it possible to force the bastard phone to take cwm this way by renaming the zip? (Ive read no - its only for official RUU's).
anyway - the oneclick didnt work, nor did ver1, ive tried various shell methods (which i cant even recall). Im currentlyunlocked, S-ON, firmware 20.2.2000 or something (the one that revolutionary WONT work on).
Ive been chasing my tail and just gave up.
please give me some info as to what i could have dobe wrong. I installed clockwork via lpay store. I factory reset, cleared caches and batt logs and was able to go into the OS a few times - but obviously one of the methods i tried did something.
thanks again great forum, but honestly, what a complete mess!! there are so many approaches with so many pitfalls its crazy.. esp for a noob when the noob apps dont work either!
HTC Desire S GSM
unclocked via htcdev
S-ON
hboot: 2.02.0002
Radio: 3831.19.00.110
Latest CMWR
Gets stuck @ white screen
Tried:
factory reset / wipe / dalvik / batt stats
reboot to recovery: install SU, gapps, cwm rom 10.1 (also tried 7.1). reboot / then fastboot boot boot.img (from the CWM zip). nothing.
Ive tried re installing the EU RUU - also nothing. Renaming the rom.zip to PG**IMG.zip, it reading the file then stops 2 fastboot screen. nothing. nada.zip.
Click to expand...
Click to collapse
i think u have MDDI pannel (not the one compatible with cianogen) try to flash a sense rom
have a look of THIS

Hi
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
Click to expand...
Click to collapse
On HTC devices, the bootloader is called HBOOT. This is a 100% device-specific program whose sole purpose is to initialize the hardware so that an operating system (such as Android, i.e. Linux) can load. If your bootloader is damaged, your device is 100% bricked.
To prevent tampering with the system, HTC have locked ("S-ON") their bootloaders so that they won't accept unsigned ROM images. So, on your HTC phone, you cannot install any operating system other than what's provided by HTC. You can partially lift these restrictions by unlocking via htcdev, as you have, or you can fully lift all restrictions on your device by going S-OFF. S-OFF-ing the Desire S is done by exploiting a bug in HBOOT version 0.98 and overwriting the bootloader with a patched version ("Revolutionary") that has all write protection disabled.
In order to flash official HTC upgrade packages ("RUU"s), you can be either S-ON or S-OFF, but if you're S-ON you MUST lock the bootloader. Anything that's not a RUU can (only) be flashed without re-locking the bootloader.
Having an unlocked bootloader is only relevant when flashing new ROMs or recoveries. Having an unlocked or locked bootloader per se will not affect booting at all, with one well-known exception: if you're S-ON and htcdev unlocked, the write protection installed by the bootloader is still on for the bootloader, radio, and kernel partitions. This means that you can't flash kernels from a running OS -- only from the bootloader. This means that when you flash a custom ROM, it will not be able to flash the kernel automatically, you have to do that manually via fastboot. Failing to do that will result in your phone freezing on the white HTC screen when it tries to boot.
#S-on/Off
I have been unable to get mine to off -
Click to expand...
Click to collapse
That's expected, because you're most likely not running a ROM that has a HBOOT version that is vulnerable to the exploit used by Revolutionary.
edit: nope, your HBOOT is newer than 0.98 and is therefore not exploitable.
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
Click to expand...
Click to collapse
Only official HTC RUUs require that the bootloader be locked.
Cyanogenmod can only be installed with the bootloader unlocked, but you may always re-lock after installing it. Remember to manually flash the boot.img (that's the kernel) via fastboot directly after flashing CM through your custom recovery.
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
Click to expand...
Click to collapse
A RUU is a *complete* software package for your device made by HTC. It contains everything from bootloader to operating system. I don't really know what else you're trying to ask, so please elaborate.
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Click to expand...
Click to collapse
The recovery is a specialized mini-Android OS that allows you to flash new software (such as unofficial ROMs such as CM) to your device. What recovery you have installed has no bearing on your main OS. If you're htcdev unlocked, the only way you can install a custom (i.e. non-stock and non-crippled) recovery is via fastboot; if you're S-OFF you can use the 4EXT updater app from Google Play.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
Click to expand...
Click to collapse
Why do you want to install stock?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Click to expand...
Click to collapse
boot.img is inside the zip of the ROM you're going to flash.
I hope I've been able to answer most of your questions. If you require more help, please search first, and if you can't find what you're looking for, please do ask.

fstarockr said:
Im trying to get a picture of the inter relations ~ pls bear with me:i dont want to be trying to sys c: when i dont have a partition kind of scenario - absolute clarity is needed - my apologies as i try wrap this up..
#bootloader:
do the same rules apply for ALL installations? Does bootloader have to be locked FOR anything to boot or just the stock OS's? does it have to be in a sequence - ie do i have to do this each time i try install an OS or can i leave it? Will this break the booting if its wrong? Can i use a bootloader from company X and a rom from company Y? What files do i use/extract/where do i get them, and are they device specific - what r the base requirements?
#S-on/Off
I have been unable to get mine to off -
#unlocked bootloader
its been indicated that this will throw off a stock OS installer, will cyanogenmod work with this off?
#RUU / Mods
I assume these are the OS's - do i have to do this last/middle? and steps after? to duplicate: are they linked to the bootloader?
#recovery
this is just an upgrade to the stock junk and has no effect on booting, etc. can be left in place if working. can install via play or fastboot via zip. (and other methods im sure).
Im trying to figure out what i can do once, and what i have to keep fiddling with, so i can hone in and get up and running.
If my questions appear ignorant - then ignore me. Im trying to paint a very clear picture of the tech relations between the various aspects and how they relate / interact - which is crucial to moving on from noobness - so pls bear with me and drop the remarks / attitude. Ive read my a$$ off and am still unclear for what many assume is basic understanding.
Im sure there are ALOT of sane unlazy logic ppl out there stuck in the same boat - and sometimes ppl who are VERY knowledgeable get a bit semi-aggressive putting ppl off from asking questions.
So do i relock the bootloader before i install any mod - or is this for stock only? And do install stock first, or can i relock and follow the steps above to root / get cwm 10.7 or 7.1 running?
lastly - where do i get the boot.img from? is that device specific or can i extract it / dl it? reason im asking is because it appears this file is device specific - and needs to be backed up from stock device before rooting/unlocking etc?
Click to expand...
Click to collapse
# bootloader
The bootloader must be locked to install an RUU (stock rom), it must be unlocked to install a custom rom.
# s-on / s-off
If you unlock your bootloader through htcdev.com, the phone stays s-on. This means you can't install a different radio or hboot (mostly not necessary anyway), or write to the /boot partition or recovery apart from in fastboot.
That means, after every rom installation, you have to reboot to bootloader (fastboot), and flash the boot.img (extracted from the rom you installed)
# recovery
A custom recovery is a must for flashing custom roms (it's where you flash the zips) , I recommend 4ext, other known recoveries are Cwm and twrp. Be aware that you can only flash recoveries in fastboot (not through an app) , if your device is s-on

1.s-off means you can flash anything you want to all partitions on the phone..
S- on (htc dev unlocked) bootloader is unlocked so you gain acces to system partition,
but neither to radio partition nor bootloader itself, so you cannot freely change them at will.
While flashing rom via recovery, ( when s-on) each time you'll have to flash boot.img of that rom -via fastboot as well, because kernel partition is not reachable from recovery ,
Boot img is to bo found in the rom zip ( namely boot.img).
and is absolutely necessary to flash that particular one
or, if existing- other that is compatible with rom of you choice and phone model..
Assuming- to flash any custom:
-bootloader has to be unlocked
-you need custom recovery ( 4ext or clockworkmod)
-rom is packed in zip format ( flashing via recovery)
-each time you change roms, you have to flash boot img of that particular rom,
( to be found inside that rom.zip)
from recovery must reboot to bootloader (adb reboot bootloader)
then flash boot.img...
If it says ok you may now begin booting in to system
Recovery:
To flash anything like roms or mods etc.
custom recovery is required,
stock htc recovery is been there for slightly different purpose,
and is, well.. rather useless for any device customizing...
1.when s-on: is necessary to flash recovery via fastboot-as an < .img > file
so, when it is zipped- extract the file: xxxyy_recovery .img,
change its name just to recovery.img, and flash it...
2.when s-off : is possible to update it via market app (but only when s-off)
RUU: is a stock phone image, and ussualy contains radio and bootloader itself,
flashing it, may upgrade your device's components that normally -while s-on-
you'd not be able to touch, but there is a price:
1.you must relock bootloader: fastboot oem lock
otherwise you'll always be getting an error
(but if you still keep unlock_token from htc dev-can unlock it again)
2.you must establish
A) your device's CID - Customer IDentification number (whether is generic or carrier branded)
B) your phone's software version region ( wwe or asia or..etc)
C) software version ( froyo, gb, ics )
because, normally bootloader will not let you flash lower RUU version
than itself,
( every RUU contains bootloader, so the one working on the device
will never let downgrade itself- well not without a little trick of course-this is XDA)
Bootloader:
It is advised to use only bootloaders for your device- if you try to flash something slse,
you'll end up with a dead phone ( no fastboot no nothing- paperweight)
While s-on you cannot upgrade bootloader in any other way but by flashing official RUU...
While s-off it is possible to write to bootloader partition ( but always a bit risky)
There are:
- stock bootloaders
- patched ( revolutionary )
- eng bootloaders ( modified - possible to overwrite it by different one in case it is necessary)...
...well... now, there is much more to it if one wants to know everything
if there is something you'd like to know in particular- write back...

fantastic answers and explanations last 3 chaps!!!!
Guys - excellent answers thank you SO much! i have a MUCH better idea now thanks to your no attitude clear answers! I think this should be a sticky as it clears SOOO much confusion for a multitude of users - and fills the forums with the same problems over and over - simply because ppl lack this base understanding b4 opening the darn prompt lol (like me!!)
So to recap"
While flashing rom via recovery, ( when s-on) each time you'll have to flash boot.img of that rom -via fastboot as well, because kernel partition is not reachable from recovery ,
Click to expand...
Click to collapse
so by following these directions:
Assuming- to flash any custom:
-bootloader has to be unlocked
-you need custom recovery ( 4ext or clockworkmod)
-rom is packed in zip format ( flashing via recovery)
-each time you change roms, you have to flash boot img of that particular rom,
( to be found inside that rom.zip)
from recovery must reboot to bootloader (adb reboot bootloader)
then flash boot.img...
If it says ok you may now begin booting in to system
Click to expand...
Click to collapse
im basically working around the S-On / kernel & partition issue i take it?
Im gonna try all this now - reason i wanted to flash stock
Why do you want to install stock?
Click to expand...
Click to collapse
is so that i can apply the earlier exploits to gain S-Off - but ill try the steps above and see.
fwiw - at this point im only downloading roms specifically for my phone - its my 1st so im going with stable ones, cyanogen for now. Once I have a better grip ill explore after that
btw:
A RUU is a *complete* software package for your device made by HTC. It contains everything from bootloader to operating system. I don't really know what else you're trying to ask, so please elaborate.
Click to expand...
Click to collapse
I was trying to figure out if the OS / roms / RUU had to be tied to boot images - as it appears they do, and whether there was a specific sequence to installing them). Since u clarified the RUU's are all-in-ones i guess the installer takes care of that, where as the others have pointed out - flashing custom roms require the boot.img to be flashed AFTER installing the rom - not the best question i admit!!
If your bootloader is damaged, your device is 100% bricked.
Click to expand...
Click to collapse
So if i can access fastboot etc then i can assume mine is fine right?
Thanks again guys - if there was a ribbon bar instead of just thanks id hit all of u a few times - im SURE many noobs will find all this info really really helpful. Its hard to tie the parts together and get an idea of how they all fit - its really puzzling.. and I know u gotta break something before u really understand it - but its nice to avoid this if possible!
Ill keep u posted on progress/results

no luck .... yet
got it working guys - had to flash boot img BEFORE rom, not after.
cyanogen mod 10.1 running on Desire s.
2 days of pain over

fstarockr said:
so by following these directions:
im basically working around the S-On / kernel & partition issue i take it?
Click to expand...
Click to collapse
Exactly.
Im gonna try all this now - reason i wanted to flash stock
is so that i can apply the earlier exploits to gain S-Off - but ill try the steps above and see.
Click to expand...
Click to collapse
That's a valid reason, but in that case you don't need to flash a custom rom first. You just need to use misc_version to lower your mainversion (a fastboot variable) and then you must flash an old (exploitable) RUU. There are numerous guides on how to do this.
I was trying to figure out if the OS / roms / RUU had to be tied to boot images - as it appears they do, and whether there was a specific sequence to installing them). Since u clarified the RUU's are all-in-ones i guess the installer takes care of that, where as the others have pointed out - flashing custom roms require the boot.img to be flashed AFTER installing the rom
Click to expand...
Click to collapse
Correct, but only if you're S-ON and htcdev unlocked. If you're S-OFF the recovery has no problem writing the boot image by itself.
So if i can access fastboot etc then i can assume mine is fine right?
Click to expand...
Click to collapse
Hell, the mere fact that you can turn on your device means your bootloader is fine
got it working guys - had to flash boot img BEFORE rom, not after.
Click to expand...
Click to collapse
No you don't? The order doesn't matter, as long as you've flashed both.