Database Info

[GUIDE] Get back to HTC Stock ROM (from anything) [UNDER CONSTRUCTION]

Hi there,
This is a guide under construction that gather different ways to get (back) to HTC stock ROM from almost everything : branded ROM, custom ROM, ROOTed/S-OFFed/etc. DHD.
Whatever you do with your phone, I cannot be responsible for it. Don't blame me if you brick it. I'll try to keep this up to date.
How to read this ?
Colors :
This answer is known and working
This answer still needs some testing/feedback
This answer is probably wrong or untested, help me correcting it
Letters : This is a change of situation. Multiple case possible, choose your path and skip the others
Numbers : This is a step or a question, go through them one by one
Here we go for the GUIDE part :
I have never ROOTed/S-OFFed/Radio S-OFFed/CWMed my phone
In this case you have either a stock HTC ROM or a branded ROM (SFR/Vodaphone UK/T-Mobile/...)
1) How do I know that I have a branded ROM or an HTC stock ROM ?
HTC Stock ROMs are often up to date if you do all the OTAs so, update your phone OTA and check your version number, it should be the last one. Moreover, branded ROMs often have a custom boot screen (with awful logo) and custom (unremovable) apps.
1.A) I have DHD with stock ROM !
You have nothing to do in this thread then. Bye bye
1.B) Damn, I have a branded ROM...
Don't cry, we'll go through it together
1.B.1) Will RUUs work ?
Sometimes it will, sometimes it won't, the best thing to do is to try. The worst that could happen is... nothing.
Warning : At this point, if RUU works, you'll have a stock ROM on your HTC and you won't be able to go back to your branded ROM (except for T-Mobile phones as a RUU is available for them). No turning back ! Anyway, that shouldn't be a problem for warranty as RUUs are "public and official".
1.B.2) Why RUUs wouldn't work ?
HTC allow brands to put their own custom firmware that we call here a "branded ROM". Those include brand promotional items such as specific apps and boot screen. Plus, they have their specific OTA that could be on a very different schedule than official ones (from HTC). For this reason and to avoid county-specific (chineese) to be converted in WWE phones, HTC RUUs check for a specific number in your phone called CID. This CID tells if you can use RUUs and if yes, wich one (WWE, chineese, etc.)
1.B.3.a) RUU worked !
Lucky boy, we're done with you. Bye bye
1.B.3.b) RUU didn't work...
Please, hold you're tears, we're still not done here. (More to come)
1.B.3.b.1) Now you have a few solutions
The zip trick :This is a method that uses a test RUU (that doesn't check for the CID). Then you fake it replacing the test ROM by the one of your choice (here an official one). This method is described here but not tested on branded phone. This may not allow OTAs (need feedback).
ROOT & Radio S-OFF/SuperCID/Unlock your phone :By changing the Radio with this guide you will be allowed to flash all RUUs. No revert tool so far to restore the Radio but this is coming soon.​
The F.A.Q. part :
1) Is that possible to find a stock ROM extracted from RUU without any cooking and flash it with CWM ?
Yes
2) Where can I find the zip to use with CWM ?
Here (link needed)​
Glossary :
CWM or CM : ClockworkMod
Random stuff :
http://forum.xda-developers.com/showthread.php?t=835595 : Maybe a way to flash a RUU without changing the CID ? Need confirmation
http://forum.xda-developers.com/showthread.php?t=841890 : Same here
http://forum.xda-developers.com/showthread.php?t=835595&page=4#edit9551194 : Working exemple without goldcard ?
Working on this thread... Any help is welcome
Please submit your questions/answers in this thread, i'll add them.
If giving answers, please, also give a source or guide (link) if possible and the color (green or orange, no red accepted as red cannot be trusted)

for later use

same as above

I can confirm that with Radio S-OFF it is possible to flash a RUU and get OTAs work. Everything will go back to stock except the Radio S-OFF, which will remain. If the device had also a bootloader S-OFF (ENG hboot), it will be replaced with the stock one.
If a device has only bootloader S-OFF, flashing a RUU is not recommended, as it will fail at version checking (because of no SuperCID). Eng bootloader has a higher version number than stock bootloader, and without Radio S-OFF the system will not allow downgrading.

jkoljo said:
I can confirm that with Radio S-OFF it is possible to flash a RUU and get OTAs work. Everything will go back to stock except the Radio S-OFF, which will remain. If the device had also a bootloader S-OFF (ENG hboot), it will be replaced with the stock one.
If a device has only bootloader S-OFF, flashing a RUU is not recommended, as it will fail at version checking (because of no SuperCID). Eng bootloader has a higher version number than stock bootloader, and without Radio S-OFF the system will not allow downgrading.
Click to expand...
Click to collapse
Is there a way to flash back the Radio S-OFF to the original one ? As far as I know, Radio S-OFF creates a backup of the partition it changes but I didn't see any tool that can change back this partition.
Edit: Seems I'm not the only one asking this question : http://forum.xda-developers.com/showpost.php?p=9642351&postcount=64
Also, when you say "not recommended" it's because it'll always fail or it has a little chance to fail ?
If you are S-OFF (not radio) there is no way to flash RUU again ? What about extracting the ROM from the RUU and flashing it with CWM ? same problem ?
Thanks

As stated in my Radio S-OFF thread somewhere in the last few pages (forum search is recommended), tools for Radio S-OFF removal are coming, but you just have to wait a bit longer. The backup that has been made is vital for the process, so do not lose it!
Not recommended, as it will most likely (probably always) fail. Without Radio S-OFF RUU is indeed not possible, unless you manually flash back the original bootloader using the original way of getting it in there (wpthis.ko + dd image). You would have to be in the stock ROM for that to work. Extracting a ROM should be possible, but I am not a ROM chef, so do not believe me

See my thread here for how to extract the rom.zip [i.e: update.zip] out of an RUU. RUU will write practically all partitions, but won't overwrite a radio-set S-OFF (i.e done through radio, not through hboot)

ivolol said:
See my thread here for how to extract the rom.zip [i.e: update.zip] out of an RUU. RUU will write practically all partitions, but won't overwrite a radio-set S-OFF (i.e done through radio, not through hboot)
Click to expand...
Click to collapse
Thanks, will add this to the FAQ/GUIDE

ivolol said:
See my thread here for how to extract the rom.zip [i.e: update.zip] out of an RUU. RUU will write practically all partitions, but won't overwrite a radio-set S-OFF (i.e done through radio, not through hboot)
Click to expand...
Click to collapse
ivolol said:
note: This is mainly for stock phones, for vendor-derived ones (e.g Vodafone DHDs in Australia) you will also need a goldcard.
Click to expand...
Click to collapse
I understood that it'll wipe everything except Radio S-OFF but what if this is done (method A or B) with a vendor-derived DHD ? Will that work ? Why wouldn't it ? Will OTAs be possible ?

Thread re-open. Follow the OP's rules and suggestions please.
Cheers,
M_T_M

jkoljo said:
As stated in my Radio S-OFF thread somewhere in the last few pages (forum search is recommended), tools for Radio S-OFF removal are coming, but you just have to wait a bit longer. The backup that has been made is vital for the process, so do not lose it!
Not recommended, as it will most likely (probably always) fail. Without Radio S-OFF RUU is indeed not possible, unless you manually flash back the original bootloader using the original way of getting it in there (wpthis.ko + dd image). You would have to be in the stock ROM for that to work. Extracting a ROM should be possible, but I am not a ROM chef, so do not believe me
Click to expand...
Click to collapse
Are there any issues with the wpthis.ko + dd image method to write the original hboot over the engineering? I've returned system, boot, recovery, etc. to their branded originals. I don't see why there would be a problem but just seeing if anyone's tried this.
The other option is 'fastboot flash hboot'. With this method, I'm not sure if I'd have to 'fastboot erase hboot' first and frankly doing that seems a bit risky because if the fastboot flash fails, you're really screwed.

No, dd can overwrite it just fine.
BUT I would do it like this (now that my tool can do radio s-on):
Radio S-OFF (if not already)
Run stock RUU
Do stock cid and radio s-on with my tool
And your device is stock.

jkoljo said:
No, dd can overwrite it just fine.
BUT I would do it like this (now that my tool can do radio s-on):
Radio S-OFF (if not already)
Run stock RUU
Do stock cid and radio s-on with my tool
And your device is stock.
Click to expand...
Click to collapse
I was thinking about this solution which works flawlessly it seems. I made this guide for ppl that wanted their HTC Stock for real and your tool wasn't able to S-ON ^^
Anyway, still missing the feature to restore the CID as it was BEFORE your tool makes radio S-OFF.
I follow your thread and so far, as I understood, there's a field where we can put the string we want but nothing to restore as it was before. Right ?
For ppl who want to restore to their branded ROM (if they made a backup with CWM) what do they have to do ?
My guess :
1) Root + Radio S-OFF
2) Remove S-OFF if any (not Radio S-OFF !) by flashing any RUU
3) Root again (as root is lost by flashing RUU)
4) Reinstall CWM
5) Now the phone is still S-OFF and SuperCID, right ?
6) Restore ROM via CWM (does this restore the S-OFF we had when we made the backup via CWM ?)
7) Remove S-OFF if still here (how ?)
8) Radio S-ON with the tool (with previous CID)
9) Done, happy branded stock ROM fully functional

Diaoul said:
6) Restore ROM via CWM (does this restore the S-OFF we had when we made the backup via CWM ?)
7) Remove S-OFF if still here (how ?)
...
9) Done, happy branded stock ROM fully functional
Click to expand...
Click to collapse
6) CWM/Nandroid doesn't backup/restore hboot so we'll still have stock S-ON hboot from RUU.
7) See above
9) Except you still have CWM recovery as this would have been flashed when you made the ROM backup (either replace recovery.img in CWM backup with stock recovery before restoring? or overwrite with dd after?). Also, the ROM you restored might still be rooted (unroot with Visionary?).

dazweeja said:
6) CWM/Nandroid doesn't backup/restore hboot so we'll still have stock S-ON hboot from RUU.
7) See above
9) Except you still have CWM recovery as this would have been flashed when you made the ROM backup (either replace recovery.img in CWM backup with stock recovery before restoring? or overwrite with dd after?). Also, the ROM you restored might still be rooted (unroot with Visionary?).
Click to expand...
Click to collapse
As far as I understand, people with branded phones will still have the recovery from CWM. And, so far, no easy way to replace it.
It seems like a tool to do that would be welcome here. What do you think jkoljo?

Diaoul said:
My guess :
1) Root + Radio S-OFF
2) Remove S-OFF if any (not Radio S-OFF !) by flashing any RUU
3) Root again (as root is lost by flashing RUU)
4) Reinstall CWM
5) Now the phone is still S-OFF and SuperCID, right ?
- Yes
6) Restore ROM via CWM (does this restore the S-OFF we had when we made the backup via CWM ?)
- Does not restore s-off
7) Remove S-OFF if still here (how ?)
- Radio S-ON has to be removed, see next step
8) Radio S-ON with the tool (with previous CID)
9) Done, happy branded stock ROM fully functional
- You should do visionary remove permroot, then the system is full stock
Click to expand...
Click to collapse
If you have non branded device, my tool will automatically restore the stock cid. Otherwise a user has to check the cid from the bootloader himself before doing s-off.
Sent from my Desire HD using Tapatalk

I'm testing all this stuff on my branded phone.
I started with a Rooted + S-OFFed DHD with AR 1.9 :
1) Radio S-OFF
2) RUU
3) Trying to temproot gets stuck on "rooting device, please wait"... Any clue ?
Edit : I grabed another copy of VISIONary here and it worked.
I had r14 before, downloaded r14 but files were slightly different in size... Anyway, package installation worked for both and I even successfully root my device with the first one long time ago. Weird

Are you still radio S-OFF? In which case, do you need to root again? The Vision wiki says you only need radio S-OFF for permanent root:
"If you are only interested in permanent root you only need radio S-OFF"
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Maybe install Superuser.apk and busybox and then see if you can install ROM Manager/CWM.
Edit: Or try typing 'su' into a terminal app like ConnectBot or Terminal Emulator.

I've returned to the dark side with a stock Sense rom (instead of CyanogenMod), because I'd like to OTA update to HTC's gingerbread rom when it comes (hopefully soon).
I installed the signed HTC rom.
I'm not sure, but I think it's a good idea to follow the instructions for radio S-OFF, superCID and simunlock (from Apache14 himself: http://forum.xda-developers.com/showthread.php?t=857444) before installing a signed rom.
The signed rom was courtesy of xmoo's thread: http://forum.xda-developers.com/showthread.php?t=824357
Yes, there will be a CyanogenMod 7 based on Gingerbread probably soon after HTC releases their rom, and I'll be back then.
I still have root, Eng-Hboot and the official clockworkmod recovery installed. I re-installed eng-hboot and clockworkmod just to be sure, after installing the signed rom using the HTC installer
I believe that my carrier won't have anything to do with it (i.e. I won't need to wait for them to modify the Gingerbread rom), as I I'm using a plain brown HTC rom. Although someone could tell me I'm wrong.

Walker Street said:
I've returned to the dark side with a stock Sense rom (instead of CyanogenMod), because I'd like to OTA update to HTC's gingerbread rom when it comes (hopefully soon).
Click to expand...
Click to collapse
You'll probably find that LeeDroid, Android Revolution, and the other ROMs which are based on the stock HTC ROM will be upgraded within a few days of the Gingerbread HTC ROM being released. I find those to be a little better than stock as they have a lot of the crap removed. I found LeeDroid very easy on the battery too.
I'm not sure, but I think it's a good idea to follow the instructions for radio S-OFF, superCID and simunlock (from Apache14 himself: http://forum.xda-developers.com/showthread.php?t=857444) before installing a signed rom.
Click to expand...
Click to collapse
jkoljo's Windows program is a front-end for the same program that Apache14 uses (gfree) so you get the same result with less hassle.
I believe that my carrier won't have anything to do with it (i.e. I won't need to wait for them to modify the Gingerbread rom), as I I'm using a plain brown HTC rom. Although someone could tell me I'm wrong.
Click to expand...
Click to collapse
Yes, that's right. SuperCID will let you install any signed ROM. S-OFF will let you install any ROM at all.
The issue some of us are facing is trying to get back to an untouched branded ROM (for warranty purposes). It can be done a number of ways, just trying to discern the safest. I think it's probably:
1) Radio S-OFF
2) Flash RUU
3) Install CWM
4) Restore ROM via CWM
5) Restore original recovery with 'dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21'
6) Radio S-ON with the tool (with previous CID)
7) Done
I'm going to test this over the weekend.

[Solved]Cant restore ROM with RUU

Greetings!
After i play with ROMs on my HTC Desire S i got problem, cant restore official ROM that was in device before flashing. My current state is S-On, HBOOT 2.00.0002, rooted Endymion_V3.5_base_release. And here is what i did:
1st i did, i unlocked HBOOT with HTCdev (remained S-On)
2nd installed ext4recovery
3rd using ext4recovery i installed Endymion ROM
4th after that i put boot.img via fastboot (because its HTCdev unlock with S-Off)
Now my question is how i can return to stock with official RUU. I tried many solutions which I found here but after all i got ERROR [140] (incompatibile HBOOT version). Can anyone provide me some suggestions or tips becaus i wont geave up just yet?
Thanks for your patience!
EDIT: Solved using this method: http://forum.xda-developers.com/showthread.php?t=1604255

Returning to Stock few questions.

So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2.
If you have S Off, this doesn't matter, but you should always try to flash the oldest RUU, so that it is easier to S Off later, unless you don't intend to perform S Off again.
Click to expand...
Click to collapse
I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get
error: -5001. Please make sure you have finished any previous setup and closed other applications.
Click to expand...
Click to collapse
Is the problem with compatibility or something else?

Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?

SsBloodY said:
So I am returning to stock from this build:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio:/ 11.22.3504.07_M
Hboot: 1.27.1100
And I have a few questions because reading the guides just didn't help me:
1. I can't understand completely the name of the RUU's: RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
1.27.401.3 - is this HBOOT version?
10.42.9007.00P_10.11.9007.15 - This is radio but why does it have 2 values?
192183- What is this?
2. I am S Off and I want to return my phone to S-on for warranty purposes then S-Off again so I must flash the oldest RUU right? If it is this is the situation how to determine the oldest RUU by HBOOT version?
3. Firmwares? What about them does the RUU overwrites the firmware should I downgrade firmware before flashing older RUU and can it be done? Is there such thing as firmware and RUU compatibility? If there is which firmware corresponds to which RUU, the firmwares have version that are not mentioned anywhere else?
4. Which RUU's I can flash and which I can't? I mean what should I look for to be suitable? Should I install RUU that has the same HBOOT version as mine or I can install older like I am ICS and I want to install GB RUU so I can S-Off easier latter?
So I am a little confused about downgrading and picking suitable versions of everything.
I decided to try without matching anything just downloading the RUU with the oldest hboot and flash it. It's RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe and my device info is in the beggining of the thread. So in FASTBOOT i run .exe and I get Is the problem with compatibility or something else?
Click to expand...
Click to collapse
SsBloodY said:
Okay seems I've asked too much. Well I want to understand all those things but for now this is what I need to know:
Will flashing this RUU: RUU_PYRAMID_ICS_HTC_Europe_3.32.401.5_Radio_11.69.3504.00U_11.22.3504.07_M_release_246089_signed.exe
On this Phone:
ROM: CyanogenMod 9 RC1
FIRMWARE: 3.32.401.x & 3.32.401.10x
Radio: 11.22.3504.07_M
Hboot: 1.27.1100
Will be successful and can I S-off and Root again easy latter?
Click to expand...
Click to collapse
1. RUU naming convention
RUU_Pyramid_<an extra LE in the name if XE>_HTC_<country/cariier>_<rom main version>_Radio_<radio version>_release_<release version>_signed.exe
dont bother about release version ..we dont need that
the only concerns are ..
country/carrier -> which determines the cid
rom main version ->explains whether youy are on GB or ICS (lesser the version ..older it is ...only between same country/carrier RUU's)
radio version -> tells the radio
2.oldest RUU ..ive explained earlier ..the main version should be least ..but this comparison is only valid if the country/carrier matches
eg:
in case of
RUU_pyramid_tmous_1.52.xx
and
RUU_pyramid_europe_1.27.xx (you cant say which one is oldest)
3.no firmware questions when we are talking about RUU (firmware arises when you talk about custom roms)
RUU has everything ...it wipes everything and converts it to stock (RUU cant touch the SOFF and CID though ..they can be changed only manually ..i.e. by we doing it manually by commands)
4.which RUU ..is you decide by CID ...
if you are supercid ..and dont know the original cid
you need to select the RUU based on your country and carrier
there is an excellent guide on RUU and it explains everything
here is the link to it ...do read it
(it helps you in finding right RUU too )
RUU RELEATED INFO AND FLASHING GUIDE
also remember by flashing RUU ..you wont lose SOFF ...unless you change it manually ..to know how to change it please refer the above guide
also i believe this answer ..answers your second post questions too

Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app

SsBloodY said:
Thanks a lot! But I still got the problem with error I mentionted in the 1st post (error 5001) I tried with 1.27 and 1.28 HTC-Pyramid-Europe. What should I do is flashing through safe mod possible.
Sent from my HTC Sensation using xda app-developers app
Click to expand...
Click to collapse
im confused
did you mean you solved it ? or are you asking me how to bypass that error ?
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe

I can't solve the problem. I connect it in bootloader/fastboot and try to run the RUU.exe. And I did revolutionary S-OFF.

Hey no idea that
error: -5001. Please make sure you have finished any previous setup and closed other applications.
is pretty annoying.

What is the CID currently on the phone ?
The RUU with xxx.401.xxxx IRC will require SuperCID (11111111) or a CID of HTC__001.
1.27... will end up installing HBOOT 1.17.0008 (just gone through the process on my replacement replacement phone.
As mentioned earlier you'll keep S-OFF and your existing CID after installing the RUU.
As far as the comms are concerned have you got the latest HTC drivers on the PC ?
---------------snip-------------
anyways
you need to keep the phone connected to pc in bootloader/fastboot and then run the RUU.exe
Also ..if you did HTC-DEV unlock ..relock the bootloader (fastboot oem lock) and run the RUU.exe
---------------snip-------------
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.

I am super CID.

gol_n_dal said:
I've recently run a few RUUs on my phone to get to a state where I could have a carrier backup, just in case (I forgot to get one immediately after S-OFF/custome recovery, doh). At no point did I re-lock the bootloader, I unlocked it (HBOOT 1.27.0000) and it's stayed unlocked the whole time, always worked perfectly. I also didn't have the phone in bootloader/fastboot mode, it was just on the home screen, again worked perfectly. I guess YMMV.
Click to expand...
Click to collapse
regarding RUU running normally ..you should have usb debugging enabled ..and need to have proper drivers too to recognize the device ..
running from fastboot no hassle there.. (most 155 errors can be prevented from running from fastboot)
couple of people were thrown error 99 when they ran RUU with unlocked bootloader ..so relock is a safer bet to prevent that error too

[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

Cannot s-off t-mob102

Hi guys,
so happy to be a part of this community!
My HTC One S is unlocked, rooted and S-ON:
CID: T-MOB102
HBOOT: 2.15
I'm currently using MaximusHD 10.0 (though I couldn't make the firmware upgrade because I'm not S-OFF).
I'm creating this thread because none of the currently opened ones covers my case. I wanted to S-OFF earlier and tried Facepalm but could not get superCID (as far as I know this is because of the write protection), so this method didn't work for me. Moonshine I think will not work also, because I'm not using a stock ROM. ( From the Moonshine instructions: 8. Use the matching Stock RUU, some stock based ROMs may work, but we cannot test them all.)
Before flashing MaximusHD 10.0 I've made a backup of my original 4.1.1 ROM that came with the device with the custom recovery (TWRP 2.4.3.0 as far as I can remember). Unfortunately when I try restoring from backup my device is in a bootloop.
Can you please advise how to obtain S-OFF so that I can enjoy the MaximusHD?
Please accept my apologies if this is not the right place for this thread.

Did you try this?
http://forum.xda-developers.com/showthread.php?t=2511027
Sent from HTC One S using android 4.2.2 sense 5

tominozh said:
Did you try this?
http://forum.xda-developers.com/showthread.php?t=2511027
Sent from HTC One S using android 4.2.2 sense 5
Click to expand...
Click to collapse
No, unfortunately I could not find stock RUU for TMOBA devices

If you need stock ruu go to www.htc.com and select your device and download the file for this file to work you need your bootloader to be lock stock or relocked. and just run the ruu and it shold work..
so you dont have any problems enter fastboot and make sure it says fastboot usb and than run ruu and it should put your phone to stock. I just did this with my phone.

Are you refering to the downloads at htcdev because I couldn't find anything else?