Database Info

[Q] Problem with HBOOT 2.00.0002

Hi guys.. I really hope someone can help with this as i am desperate.
I unlocked my Desire S with Revolutionary, then upgraded HBOOT to ENG 2.00.0002. Until now ,after running all roms possible found on this great site, I had the pre-rooted deodexed stock 2.10.401.4
Today I downloaded the RUU_Saga_S_HTC_Europe_2.10.401.5, unpacked copied the PG88IMG.zip to my sdcard and begun update. The update was unsuccessful. Now my device says this:
*** LOCKED ***
*** Security warning ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO_3822.10.08.04_M
eMMC-boot
The phone is stuck is FASTBOOT, and selecting BOOTLOADER only loads again PG88IMG.zip, and of course after "Checking PG88IMG.zip" it errors with Main version is older! <Power> to REBOOT.
IS there anything that can be done? PLS HELP!

OPPiuM said:
Hi guys.. I really hope someone can help with this as i am desperate.
I unlocked my Desire S with Revolutionary, then upgraded HBOOT to ENG 2.00.0002. Until now ,after running all roms possible found on this great site, I had the pre-rooted deodexed stock 2.10.401.4
Today I downloaded the RUU_Saga_S_HTC_Europe_2.10.401.5, unpacked copied the PG88IMG.zip to my sdcard and begun update. The update was unsuccessful. Now my device says this:
*** LOCKED ***
*** Security warning ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO_3822.10.08.04_M
eMMC-boot
The phone is stuck is FASTBOOT, and selecting BOOTLOADER only loads again PG88IMG.zip, and of course after "Checking PG88IMG.zip" it errors with Main version is older! <Power> to REBOOT.
IS there anything that can be done? PLS HELP!
Click to expand...
Click to collapse
If you remove or rename the PG*.... file from the root of your SD card this should stop happening..
Then you should be able to enter recovery, where I'm hoping that you'll have an available Nandroid backup that you could restore to.

Problem is that choosing recovery from bootloader does nothing, just brings me back into fastboot. I think that recovery was wiped during the failed update process.
Also my device is S-on now so i cannot flash a new recovery in fastboot.

Now I'm afraid that I'm a little out of my depth here so won't offer any more advice.......but, you should be able to flash the recovery partition from fastboot...So hopefully all is not lost yet...
EDIT: Apology, only just read that you're S-ON and am not sure what to recommend.

You should look at my guides below. Both will tell and show you how to flash recoveries via fastboot.
Check my sig below.
Sent from my HTC Desire S using XDA App

Thanks, but before i wrote this question i did read all guides possible, including yours . Problem is I am stuck in fastboot, i cannot boot the phone, use adb or flash anything via fastboot as my device now is LOCKED and S-ON. Also i have no recovery not even stock one...
Smells more and more like a bricked Desire. Damn.

OPPiuM said:
Thanks, but before i wrote this question i did read all guides possible, including yours . Problem is I am stuck in fastboot, i cannot boot the phone, use adb or flash anything via fastboot as my device now is LOCKED and S-ON. Also i have no recovery not even stock one...
Smells more and more like a bricked Desire. Damn.
Click to expand...
Click to collapse
If you have read the guide, you should have known that before you can flash ANYTHING on fastboot, you have to be UNLOCKED first..
You should have tried to unlock it BEFORE flashing anything..
If these doesn't work, then you may be right on your last sentence..
Goodluck!

Before attempting the RUU update with pg88img.zip i had ENG HBOOT with S-OFF, but during that update something went wrong. It managed to update to the official HBOOT 2.00.2002 S-ON, but then i got the "Main Version is older - Update Fail! error and i think I need to send it to HTC as I see no way out of this. What i do not understand is this "Main Version is older - Update Fail!" error! why did this happen in the first place as i was updating from pre-rooted deodexed stock 2.10.401.4 to 2.10.401.5.

Simmilar problem, still wifi not working
I have got simmilar problem on desire s, got revolutionary S-OFF with 0.98 then tryied RUU with sense, something went wrong.. now i have hboot 2.00.0002 radio 3822.10.08.04_M i opened the hboot via HTC development page, then i flashed the newest ROM by Adidas108: RUU_Saga_S_HTC_Europe_2.10.401.5_signed_prerooted SENSE 3.0(http://forum.xda-developers.com/showthread.php?t=1183684)
now the system is booting properly and i can use the phone again, but the wifi is not working, which sucks because there is newest radio and according adidas108 newest ROM. I havent found solution for this as my hboot is in S-ON now and i cant flash different version of radio. I think first i need to find how to make hboot 2.00.0002 into S-OFF. Anyone any idea?
UPDATE 1: now i managed to install the ROM build 1.28.401 prerooted by Adidas108, everything seems to be working again, even wifi is ok. It is strange that the old ROM is working with newest RADIO and the newest ROM not, does anyone has any reasonable explanation to this issue?

Can you please be more specific on how you dealt with your HBOOT. Did you somehow managed to get it S-OFF. I sure need to flash a new recovery and from there i am good, i can resurrect my phone.

No my hboot 2.00.... Is s-on, i just unlock the recovery it means i can flash roms, but i cant overvrite radio or hboot on its own. I also need a solution how to make my phone s-off, and as revolutionary is only supporting hboot .98 it will not be easy. For now ill better stáy on my old ROM with sense 2.1
Sent from my HTC Desire S using XDA App

I unlocked my bootloader on htcdev. After that my old rom booted up normaly and everythig was back to normal. I then flashed in recovery RUU_Saga_S_HTC_Europe_2.10.401.5_signed_prerooted SENSE 3.0 by Adidas108 and it all works perfectly now since my radio was updated before the error with "Main version is older" in the official RUU_Saga_S_HTC_Europe_2.10.401.5. thanks guys for the help.. i read Skanob guides again and found out about htcdev.

moloto said:
No my hboot 2.00.... Is s-on, i just unlock the recovery it means i can flash roms, but i cant overvrite radio or hboot on its own. I also need a solution how to make my phone s-off, and as revolutionary is only supporting hboot .98 it will not be easy. For now ill better stáy on my old ROM with sense 2.1
Sent from my HTC Desire S using XDA App
Click to expand...
Click to collapse
BTW, from my experience it seems that you could update your radio to latest version if you try with the official RUU_Saga_S_HTC_Europe_2.10.401.5. It will probably error "Main version is older" and lock your bootloader, but you could unlock it on htcdev, and enter custom recovery after that and flash Adidas108's RUU. My wifi works perfectly with 20.4801.30.0822U_3822.10.08.04 radio.

Solution
So finnally my cell is working with sense 3.0. I downgraded hboot to 0.98.0000 thanx to Skanob(http://forum.xda-developers.com/showthread.php?t=1318919), then S-Off with revolutionary, flashed actual clockwork mod recovery, after the newest saga radio and as the last the newest ROM by Adidas108. Everything works fine, even with hboot 98.0002. End of Story

[Q][SOLVED] No Super-CID, can't boot into ROM, fastboot won't flash older ROMs...

Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
edit: Issue solved, see page 2.

Also, in case this information helps - I do have a goldcard.img but it doesn't appear to work. My CID is T-Mob005
this guy seems to have been in the same boat as me but he did everything correctly - http://forum.xda-developers.com/showthread.php?t=1378921
if he still has his goldcard.img is there a chance it would work in my phone? I've PM'd him asking if he still has it

FrakEarth said:
Hi, I think I may have completely screwed the phone up...
I've been on T-Mobile UK with this phone for quite a while now, 2.3.5 updates being available in Europe and on other UK providers for ages, and I know friends have recently received it on T-Mo UK too, but I couldn't get it for some reason. Investigating why with T-Mo customer service was futile so I decided to try and set about upgrading it myself.
I used superoneclick to get temporary root, flashed revolutionary recovery to get S-Off and got myself permanent root on 2.2 -- however something went wrong after this and I'm not quite sure what.
On trying the European RUU (2.10.401.8) it seemed as though it was successful, but going into HBoot, I could see it was no longer Revolutionary branded - instead it says:
Code:
*** LOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Trying to flash another recovery tool doesn't work, trying to flash an earlier version of HBOOT doesn't work. Re-flashing the European unbranded RUU doesn't work because its now picking up that the CID isn't right, and in this environment (Hboot) my gold card doesn't seem to be working. The latest Desire S T-Mobile RUU I can find is version 1.30.110.2, and as its older I get the "Main version is older" error.
I tried extracting the rom.zip from the RUU .exe file, renaming it to PG88IMG.zip - but same error there - and trying to fool it by changing the version number in the manifest inside the archive just makes the sig check fail...
I'm totally outta ideas here, anyone got any more for me to try, or am I going to have to send this off to someone to fix?
Cheers!
Click to expand...
Click to collapse
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.

tpbklake said:
Relax, you have simply gotten the locked bootloader flashed to your phone. You can go to the HTCDEV.com site and unlock the bootloader and then you will be able to install a custom recovery and root the phone again.
Click to expand...
Click to collapse
Thanks, that's one problem down!
At present I have this RUU Europe Rom that won't load, and the T-MO UK ones still won't install either. I've installed ClockwordMod Recovery 5.0.2.0, so that's good, but I take it I still need a goldcard if I'm going to install a ROM that doesn't match my phone's carrier ID?
Is the reason these older T-Mobile ROMS won't install because of S-ON and the higher radio version number?
edit: by the way, cyanogenmod and similar ROMs appear to install with no errors in clockworkmod recovery but I don't think they are. If I load one of the RUU exes it shows the same 2.10.4 version number with no changes evident whatsoever.

Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium

gefilus said:
Don't do all so fast. READ FORUMS, READ COMMENTS. Revolutionary wont work with 2.00.0002 . It wont work
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
I realise that now... I'm less concerned about rooting / getting full S-Off again and more concerned with just getting any working ROM at all onto the phone... as it seems the only ones that are probably going to work are T-Mobile ones, and the only available ROMs I can find are older - I may have to send this off to someone

So you cab get into fastboot?? If you can then use downgrading without HTC Dec unlocked bootloader, there is a post about this, try it should work and use misc_version to let phone thinks he is on older hboot and then use latest T-Mobile ruu. I hope and it should work.
Sent from my HTC Desire S using xda premium

i would do this:
unlock with htcdev.com
downgrade hboot to 0.98.0000
use revolutionary for s-off
change cid to supercid
relock bootloader again
and flash the ruu of youre dreams.
think this should do it

This worked for me in the same situation
http://forum.xda-developers.com/showthread.php?t=1443636

Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).

FrakEarth said:
Is there a way to get adb terminal access when the phone won't actually load a ROM?
Because all the tutorials I can find for downgrading HBOOT or installing an older ROM (with misc_version etc) - seem to require adb access. I can *only* get into fastboot or a recovery tool like clockworkmod recovery.
Installs of ROMs just aren't working at all. I'm getting "Security Fail" on some of the official ROMs, and the custom roms just aren't working (I assume because of S-ON).
Click to expand...
Click to collapse
Only if you left on USB dedebuging if it's off then sorry can't. Bet if its o n you can easy make him to boot into fastboot. Take a try, and you need to be installed sdk and adb tools on, PC. Try switch on phone put into USB and open terminal, write adb devices if it works there will show a list and HTXXXXXXXXXX something. If it so then adb reboot - bootloader or if you have custom recovery boot there. If don't anderstand look commands in Wikipedia about adb. Good luck
Sent from my HTC Desire S using xda premium

Okay guys, managed to get this sorted.
Firstly, I read that if you mounted /system from Clockwork mod that ADB commands work... well I didn't get to try that out, because something else worked.
One of the reason RUU updates were failing was because the bootloader was unlocked, when I relocked (fastboot oem lock) they started working again, but I was getting Carrier ID errors on the European RUUs and the T-Mobile ones were too old.
I decided to visit a friend who also has a Desire S and from his phone I was able to get the CID (card identification register) code from a smaller microSD card I have -- this was one I hadn't tried as a goldcard before, and I was unable to try without being able to get at the GoldCard Helper app on my phone... so after using his phone and writing down BOTH CIDs, I tried both and it worked -- I now have the phone updated fully using the European RUU.
I think my mistake the first time may have been copying the wrong CID from Goldcard Helper: if you press Menu > Copy Code it seems to copy the code from MMC1, whereas my SD card was clearly MMC2 -- so my goldcard.img was completely incorrect the first time I tried it. I don't know why the phone let me partially install the European RUU without a goldcard and almost brick the phone, but I suspect it was because I had the Revolutionary bootloader with S-OFF.
So in summary if you have this problem I would suggest borrowing an Android phone (any should work) to get the right goldcard CID needed and then try installing an RUU.
Many thanks to everyone who replied and tried to help me, you guys helped me exhaust every other possibility - and I appreciate it a lot! Thanks!

[Q] stuck on splash-screen

Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow

onemanshow85 said:
Hey guys
I've got a bit of a situation. A friend of mine gave me this sensation (carrier T-mobiel) wich was all but bricked. Since I have some experience rooting and flashing custom ROMs, he asked me to give it a try at reviving it.
The owner had been messing around a bit himself and he managed to install clockwordmod recovery. Don't know if he installed any ROM, the device gets stuck on splashscreen.
I did the following; full format, superwipe and install a ARHD ROM. result was te same; stuck on splash-screen.
Then I did another full format, wipe and installed Cyanogenmod, still the same result.
I wanted to try and install 4EXT touch recovery, but the device doesn't respond to any USB connection method so ADB won't work. there's no working ROM so installing through the app won't go either. basicly, I don't know if there's a way to uninstall and install a recovery through flashing.
I have another phone to use to store required files on a SDcard.
these are the things dat DO work:
Bootloader, fastboot and clockworkmod recovery v5.8.0.9
this is the device's bootloader information
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
RADIO-10.14.9035.01_M
Aug 2 2011, 22:35:52
my guess is that I'm trying to install ROM's that don't work with the current firmware. I don't know if the owner installed the OTA ICS before he got these problems. But I don't know what firmware is currently on this this device, and how to check it.
Lost for clues here and calling out for help
Onemanshow
Click to expand...
Click to collapse
Hi,
2 things you can try.
1.Run a GingerBread RUU.
Look HERE
2.If that works,try s-off.
Look HERE
Then,you could change firmwares and do whatever you like.

Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
edit: I downloaded and executed a RUU that apearantly wasn't compatible with the phone. I'm guessing it removed whatever ROM was installed, but didn't install the ROM from the RUU.
I also followed step 3; RUU to restore stock up to the part of relocking the bootloader. I didn't come any further cause I can't find the right RUU.
the phone now only boots into bootloader with "security warning" displayed below "relocked".
I'm guessing, if I find the correct RUU with gingerbread, things will be okay again.
on a sidenote, does a RUU install also returns the recovery to stock?

onemanshow85 said:
Hi Malybru,
I understand what you suggested and I'm currently working on it. Only I can't find the right RUU for this phone.
Current CID is: T-MOB003
getting it superCID'd was no go since I can't get it S-OFF with the revolutionary utility. is there another way to S-OFF the phone besides revolutionary?
Click to expand...
Click to collapse
Hi,
RUU does not matter too much as long as it is Europe and GB.
If you can find a dutch tmo ,then even better.
No harm will come if it is the wrong one.
It will only throw up an error.
This will at least get a ROM on your phone,so that you can s-off .
Revolutionary is the easiest way to s-off.

so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?

onemanshow85 said:
so, to summarize:
the RUU has to be TMO for either UK or EU. Does the radio need to match the one that's currently displayed in the bootloader?
Click to expand...
Click to collapse
Hi,
The closer the match,the more chance of success.
But close will do.
Yes,with the same radio.

finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?

onemanshow85 said:
finding a dutch RUU with this radio for TMO is pretty challenging. So I tried it with a german version (DE). Other then that it matches the radio, and the carrier.
the first method through the RUU.exe failed, it tells me to get the right RUU for my carrier/phone.
So I tried it through flashing with a SDcard. I changed the CID in the notepad file in the PG58IMG.zip to T-MOB003. In bootloader, it checks the file twice and after that nothing happens, the regular bootloader screen is prompted.
Then I tried to flash it through fastboot CMD command, pretty much my last option according to the guid you linked me. This also fails with the notification that it failed to verify 12 signatures.
now I found some universal firmware packages but they don't seem to contain any ROM and recovery, only firmware. are there any of these universal packages as complete RUU?
or is there a way to bypass the signature check with a fastboot command?
Click to expand...
Click to collapse
Hi,
Try the European RUU with the 10.14 radio that matches yours.
Add your CID in the PG58IMG text file.
Make sure you have the phone in fastboot when you attach your USB cable(it should say "fastboot USB"),and start running the RUU from your PC.

http://db.tt/A7lS7PaD
Here is a link to 4ext touch recovery as a IMG. http://db.tt/KFKpcrhB and here is a pg58img.zip. put the zip file onto the sdcard and boot to boot loader. It will hopefully flash the recovery. If not fast boot flash the IMG. Once you have the recovery installed enable smart flash and then flash the roms. Hopefully that will work for you
Sent from my HTC Sensation using xda premium

tnx for the files.
I tried the suggestions you made but flash from sdcard doesn't work; it checks the file once and doesn't do anything after it.
when I try to flash either one of the files through fastboot I get signature verification fail.
my bootloader says RELOCKED, I got that after following step 3.1 in the RUU flash guide to return to stock. I don't know if this is blocking anything from being flashed with the nasty signature notifications?
also, most like because nothing is installed on my device, when I plug in the USB cable when it's turned off, it automatically swithces on displaying SECURITY WARNING below RELOCKED.

Damn, wasn't fast enough. I'm not sure what the best way to approach this is. Either attempt to full s-off the device with revolutionary/ jupuntobear, or re-unlock your boot loader with htcdev, then fastboot flash the recovery. Then install the rom. Then run jupuntobear to full s-off
Sent from my HTC Sensation using xda premium

heavy_metal_man said the right thing. First focus on unlocking it on hTCdev.com and afterwards, flash a 4Ext Recovery to make things easyer. Then put the device in bootmenu (not in the Graphic shell) and attach a USB, start any Official European RUU that is Gingerbread - with 1.50 in the numbers.

an update
I managed to get it unlocked again with htcdev.com. After that I flashed 4EXT recovery, succesfully.
only thing now I need to do is installing a ROM. I tried the following without succes so far:
with RUU
I can't find a dutch RUU for TMO with radio 10.14.9035 anywhere so I tried the closest match possible, a german one. through the .exe method I get incompatibility errors. So I extracted the ROM/.zip, added my CID and tried with SDcard flash and fastboot flash, both unsuccesfull. Hboot checks the file twice and does nothing afterwards, and fasboot prompts the message "FAILED (remote ** unknown fail)"
Universal firmware package to make sure I'm on 3.32, so I can install ARHD 6.7.2 or any other ICS rom
I took one from http://forum.xda-developers.com/showthread.php?p=21711154#post21711154.
I get the same errors as when I was trying to flash the ROM.zip from the RUU, both with sdcard flash and fastboot flash.
a random Gingerbread ROM
I found this GB ROM http://forum.xda-developers.com/showthread.php?t=1226564.
I installed it through EXT4. after a reboot it's stuck in a bootloop. No splash screen is shown however, it get's to the withe-field-green-HTC-screen and reboots after, showing the same.
I don't understand what's wrong. I got a good recovery now and the bootloader is unlocked. For some reason the ROM's I tried are incompatible with the current state of the device and I can't figure out why. are dutch T-mobile branded phones so tough to crack or what?
also, after a certain step wich I can't remember, my bootloader doesn't display a radio anymore.
Current bootloader:
UNLOCKED
PYRAMID PVT SHIP S-ON RL
HBOOT-1.18.0000
eMMC-boot
Aug 2 2011,22:35:52
EDIT: I would be less restricted in my actions if the damn thing were to be S-OFF. is there any way to get get S-OFF through bootloader/fastboot? All the S-OFF methods and utillities I found so far need the device to have a ROM running.

SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help

onemanshow85 said:
SOLVED
with help of KGS1992, I managed to restore the device.
- installed a stock GB ROM since I was on hboot 1.18, and to get root acces
- aquired root through adb
- gained S-off with revolutionary
reason why I couldn't manage this before is because I didn't have a genuin stock ROM.
tnx all for the help
Click to expand...
Click to collapse
Glad you got sorted pal and thanks for letting us know

[Q] can't s-off to update tried htcdev doesnt work!

Hi all
I have a desire s
android 2.3
HBOOT ***unlocked***
saga pvt ship s-on rl
HBOOT 2.00.0002
I have rooted last year I think I used superoneclick and now I want to S-off to get update rom so far I have:
downloaded revolutionary=Device not supported,
HTC\dev gone through webside instructions a few times flashed the unlock code they sent cmd says succesfull but it did nothing to phone which just stayed in fastboot. (tried a few times on xp and win7)
tried running the ruu from htc but that fails saying wrong version error 155 (tried a few times for some reason it wont start on my xp but runs ok on win7)
now I am stuck, could anyone please help?
Thanks Paul

Run RUU with HBoot version of 0.98.0000 or 0.98.0002 to be able to S-OFF with Revolutionary.

pauldve said:
Hi all
I have a desire s
android 2.3
HBOOT ***unlocked***
saga pvt ship s-on rl
HBOOT 2.00.0002
I have rooted last year I think I used superoneclick and now I want to S-off to get update rom so far I have:
downloaded revolutionary=Device not supported,
HTC\dev gone through webside instructions a few times flashed the unlock code they sent cmd says succesfull but it did nothing to phone which just stayed in fastboot. (tried a few times on xp and win7)
tried running the ruu from htc but that fails saying wrong version error 155 (tried a few times for some reason it wont start on my xp but runs ok on win7)
now I am stuck, could anyone please help?
Thanks Paul
Click to expand...
Click to collapse
Hi
First:
In order to use revolutionary s-off, you'd need to lower your software version number(misc_version)
1. Lock your bootloader- fastboot oem lock
2, then flash correct RUU -matching your CID
3.use revolutionary....
Second:
As you state in your bootloader screen info,
, htcdev unlock worked indeed- your bootloader is UNLOCKED-as you've said yourself-
, that's what it does...
Third:
If you wish to update-as you said-then update to what?
a) official RUU saga 4.0.4:
1.and foremost- you must lock your bootloader again in order to flash a RUU
2.if your device is branded by any mobile carrier- must create gold card
, in order to flash WWE version of the RUU
3. Certainly you flash that in fastboot
b) custom ics rom:
1. There are many to chose from- much more sofisticated than the official RUU 4.0.4 release
2. Not need to s-off realy in order to flash most of them
3. You only have to flash boot.img from the rom you're flashing,, via fastboot (again)
Fastboot flash boot boot.img
http://forum.xda-developers.com/showthread.php?t=1146601
This is where it all begins
http://forum.xda-developers.com/showthread.php?t=2143855
And that is where people could render some knowledge for you
Edit:
Last but not least:
Keep unlock_token from htc- in a safe place because
, if you decide to upgrade by the official RUU
, you must unlock bootloader again in order to flash any custom rom
, and you do it by that same key (unlock_token)....
When there are any troubles with connection < pc- phone > check your windows drivers

Thank you.
I was trying to flash official ics but I will go for a custom instead.
I see now where I was going wrong thanks I thought I had to unlock the Hboot by making it s-off to flash official rom of ics, thats why it was failing because its unlocked.
Thank you

[Q] Return HTC Desire S to factory

Hi there, firstly i apologise if this has already been asked, i am looking to put my phone back to factory state as i have to send it back to HTC under warranty as it is now broken my current state is as follows:
UNLOCKED
SAGA PVT SHIP S ON RL
HBOOT 2.00.0002
RADIO 3822.10.08.04_M
eMMC boot
my recover is 4ext Recovery ver 2.2.7 RC5
if somebody could provide me with a step by step guide or show me where to find one it would be hugely appreciated!

Goodbye you pretty virgin LOCKED bootloader :'(
Sorry mate, all you can do is go down to an old hboot to cover the unlocked or relocked state...
Oh and if you want the old HTC ROM, you must relock and run a RUU.

ok can you maybe give me a step by step guide to achieve this?

Make sure adb is enabled in the phones developer settings.
Then:
On PC with adb set up enter the following commands:
adb shell
reboot bootloader
then when phone reboots to bootloader, make sure it is in fastboot mode
enter on PC:
fastboot oem lock
Then your Phones Bootloader should show RELOCKED and you can run a RUU that fits your Phones CID/Region since you don't have super CID.

are you able to supply me with a link to find a list of ruu's

http://forum.xda-developers.com/showthread.php?t=2094389

Jann F said:
http://forum.xda-developers.com/showthread.php?t=2094389
Click to expand...
Click to collapse
hi im sorry but im struggling to find the correct ruu for my phone is there anyway that you can steer me in the right direction - i downloaded the saga vodafone uk one but it hasnt worked

You need to find a RUU correct to your location and service provider, if branded.
If have used the correct RUU, based on the above, then you need to post the error that is showing up. You may need to create a gold card or lower your misc_version. Steps on how to do both can be found in this thread.

I USED THIS ONE RUU_Saga_Vodafone_UK_1.32.161.1_Radio_20.28b.30.0805U_38.03.02.15_M_release_179398_signed.exe
I get the bootloader screen, it says erasing data, sending, then updating signature, then i get error (140) bootloader version error, the rom update utility cannot update your android phone, please get the correct rom update utility and try again.
This issue i have is that there isnt a desire s option in the list of ruu's !

gazs1 said:
This issue i have is that there isnt a desire s option in the list of ruu's !
Click to expand...
Click to collapse
That isn't the issue. The codename for the Desire S is "Saga". As you can see, all of the RUUs listed are for the Desire S.
Your misc_version may be higher than the version of the RUU you're trying to run. Follow the steps under the heading "Modifying the version of your phone" in the thread I linked you to above and see if that works.

oddoneout said:
That isn't the issue. The codename for the Desire S is "Saga". As you can see, all of the RUUs listed are for the Desire S.
Your misc_version may be higher than the version of the RUU you're trying to run. Follow the steps under the heading "Modifying the version of your phone" in the thread I linked you to above and see if that works.
Click to expand...
Click to collapse
Hi been reading this thread, so is it correct that if you have unlocked your bootloader and rooted that you can no longer return to manufacturer?

After unlocking the bootloader you can re-lock it and return to stock, although your bootloader will contain the message "RELOCKED" which is evidence of having rooted your phone, and can't be removed. You could run a pre-2.3.5 RUU which doesn't show the lock status of your bootloader and hope that the manufacturer won't notice and won't write off your warranty.
This is why S-OFF is much better than unlocking your bootloader, since you can root and also return to stock without affecting the lock status of your bootloader.