Database Info

Get back to stock sensation (T-Mobile) with s-on?

How would I go about doing this sso I can sell it? I'm currently on a 3.5 rom.

Same problem here (warranty exchange). I've done everything recommended here http://forum.xda-developers.com/showthread.php?t=1192300 but when I rune the .exe, I get an error [155] (incorrect ruu). I have searched everywhere for an up-to-date RUU, but have not had any luck.

You need to change your cid number to correspond with your carrier if you search the forums there is a list of them I presume you know how to go about this as you would have to have the super cid 11111111 or Eu HTC__001 to flash another Ruu other than your carriers
Sent from my HTC Sensation Z710e using XDA App

Change Cid number? Why would I have to do this? I've never messed with that before.

My apologies I presumed you had installed a unbranded firmware prior to rooting
Normally you have to change the cid to do this as the gold card method won't work
Sent from my HTC Sensation Z710e using XDA App

I followed a thread here to return to S-ON and then flashed the newest RUU from the post that lists all of the RUU's for the Sensation.

alright I've been reading and I'm still a little confused.
Basically, I have an s-off sensation with root and a rom. It's a T-Mobile sensation. I never debranded or anything like that.
What exactly do I need to do to return to stock as if I just bough it? I also noticed there are two TMOUS ruu files....which one do I use?

OK, lets begin
When you S-OFF'd the HBOOT changed to a newer one than your stock, TMOUS ROM. Because of this, you NEED Super CID to be able to go to a lower HBOOT. So that's why you need to change to it.
Once done, you can flash the stock 1.29.531.2 RUU. Once this has completed, you can change the CID back to the TMOUS one and then go back to S-ON and voila - one stock, ready to sell Sensation

Has any one got the Vodafone UK ROM please?
Cancel that. The download hasn't got that long left, so I'll just wait for it to finish.

EddyOS said:
OK, lets begin
When you S-OFF'd the HBOOT changed to a newer one than your stock, TMOUS ROM. Because of this, you NEED Super CID to be able to go to a lower HBOOT. So that's why you need to change to it.
Once done, you can flash the stock 1.29.531.2 RUU. Once this has completed, you can change the CID back to the TMOUS one and then go back to S-ON and voila - one stock, ready to sell Sensation
Click to expand...
Click to collapse
Thanks....so how exactly would I do this super CID thing? lol
So basically...do super cid thing, flash stock RUU, then super cid again? Sorry, I've never really done much other than flash roms, so I don't know what this cid stuff is.

You should've really learnt all this before jumping in as you should always know how to get out of something before you go ahead with it.
The guide you followed to S-OFF has the Super CID procedure:
http://forum.xda-developers.com/showthread.php?t=1192300
However, before changing it you need to make a note of your current one. To do so, you need to run the following fastboot command:
fastboot getvar cid
Once done, use the guide above to write the Super CID. This will allow you to flash the 1.29.531.2 RUU.
Then, using the same procedure as writing Super CID, write your old one back. Then follow the guide to get S-ON
Having said all that, you could just try flashing the 1.29.531.2 RUU and if it works then follow the guide to go back to S-ON - it may work

I have tried to change it to 111111... but the exe gives me the error nontheless. What do i change the CID TO?

akbisw said:
I have tried to change it to 111111... but the exe gives me the error nontheless. What do i change the CID TO?
Click to expand...
Click to collapse
I'm sure you've already figured it out since the thread hasn't been updated since a couple of months back, but here's the link to the thread with the answer if anyone gets here while searching for the right T-MOUS Stock CID for sensation:
http://forum.xda-developers.com/showthread.php?p=23046170

be careful
if u updated firmware to ics be careful before flashing an ruu this messed up my phone

Sorry for bumping an old topic, this topic was helpful with what I needed. I need to return my phone to stock for a replacement. I completed all the steps but what can I double check to make sure I did it correct. I have stock rom and s on. My CID still shows "11111111". I was trying to get the OTA update to ICS but it won't let me download it so it worries me that I still am not completely stock.

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

stock rom fail

Hi,
I'm trying to go to the stock rom because I have to return my phone because I have battery problems and dust behind my screen.
But when I try to flash a stock rom it doesn't work. It says that I using the wrong image update.
Current image is 1.11.401.110 and I want to go to the lastest stock rom 3.32.401.105
What do I have to do?
Thanks

What was the original CID ? What CID do you now have ?
1.11.401....... wow that seems really old.
x.xx.401.... will need CID "HTC__001" or SuperCID "11111111".
What exactly does it say when you run the RUU ? Does it connect OK to the Sensation, does it say what the existing version is on the phone ?

gol_n_dal said:
What was the original CID ? What CID do you now have ?
1.11.401....... wow that seems really old.
x.xx.401.... will need CID "HTC__001" or SuperCID "11111111".
What exactly does it say when you run the RUU ? Does it connect OK to the Sensation, does it say what the existing version is on the phone ?
Click to expand...
Click to collapse
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz

tommeke19 said:
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
Click to expand...
Click to collapse
OK I don't understand where 1.11.401.110.... figures in the situation. If I understand correctly that is a custom ROM based off a different platform with Sense 4.0. Probably wrong though..
Are you fully S-OFF (clutching at straws here). Assuming you are you should be able to install an RUU easily. I recently went from 3.32.161.... to 3.32.401.. then back to 1.27.161... with no issues at all.
I'm sure someone more able than me can help you here.
GL

tommeke19 said:
I at the moment I have SuperCID so '11111111'.
My sensation was connected correctly to the pc
And do you need my Hboot version or my firmware?
My Hboot: 1.27.1100
Firmware: 3.33 full package
Greetz
Click to expand...
Click to collapse
ok you are SOFF seeing that you have revolutionary HBOOT ..
so when returning stock ...its better to flash the correct stock...which can be found using CID
but as you have supercid now ...you need to know your original cid or the carrier/country the phone is linked to ..for finding the proper stock RUU
this guide helps you in fiding the proper stock RUU and it has flashing instructions too

Hi,
I followed the link and tried to get my CID but I only get 11111111 so i don't know what I have to download now

Install "cid getter" from the market.
AFAIK the entry for "ro.cid" should tell you your original CID.
e.g. It says VODAP001 for me while "fastboot getvar cid" gives "11111111".

tommeke19 said:
Hi,
I followed the link and tried to get my CID but I only get 11111111 so i don't know what I have to download now
Click to expand...
Click to collapse
from which country you bought the phone from and to which carrier it is linked to ?

Thanks everyone for helping me, but after using google I've found a site and found the solution.

Help Me Find

so i am S - OFF and need to run a RUU (long Story)
so when i ran the RUU it said please download the right rom utility update
this is the one i ran http://bugsylawson.com/files/file/3...00528-10275008l-release-301814-signed-2-4exe/
and i changed my CID to HTC__001 and also i can change back to SuperCID 11111111
i heard you have to have a ruu which is lower than your HBOOT my HBOOT:2.13.0000
what shall i do please ould someone help thanks

Zaman-The-Man said:
so i am S - OFF and need to run a RUU (long Story)
so when i ran the RUU it said please download the right rom utility update
this is the one i ran http://bugsylawson.com/files/file/3...00528-10275008l-release-301814-signed-2-4exe/
and i changed my CID to HTC__001 and also i can change back to SuperCID 11111111
i heard you have to have a ruu which is lower than your HBOOT my HBOOT:2.13.0000
what shall i do please ould someone help thanks
Click to expand...
Click to collapse
Since you are Soff I don't think it matters what hboot it is. You just have to run the RUU that matches the CID. May want to double check, but that has been my experience. Once you are Soff it's easy to switch CID.
Sent from my HTC VLE_U using xda app-developers app

npiper05 said:
Since you are Soff I don't think it matters what hboot it is. You just have to run the RUU that matches the CID. May want to double check, but that has been my experience. Once you are Soff it's easy to switch CID.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
my cid is HTC__001 so shall i run the latest unbranded RUU could you link be to the latest unbranded RUU ? i dont trust my self

Zaman-The-Man said:
my cid is HTC__001 so shall i run the latest unbranded RUU could you link be to the latest unbranded RUU ? i dont trust my self
Click to expand...
Click to collapse
Sending you a PM now

[Q] Upgrading Through RUU Help Needed

Hello My Dear Learners & Teachers....:angel:
my question is my At&t HOX is on 4.0.3 ICS Wanted To Install JB i went to htc site and got the RUU Link
(RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial)
The Filename mentioned ... want to know is it correct RUU for my At&t HOX?
My Current Info is
Software Number "1.85.502.3" | Radio 0.17.32.09.12 | Hboot 1.09.0000

That is the right RUU for the AT&T version.
Is your phone stock or modded?

xoreg93 said:
Hello My Dear Learners & Teachers....:angel:
my question is my At&t HOX is on 4.0.3 ICS Wanted To Install JB i went to htc site and got the RUU Link
(RUU_EVITA_UL_JB_45_S_Cingular_US_3.18.502.6_Radio_0.24p.32.09.06_10.130.32.34_release_signed_With_Partial)
The Filename mentioned ... want to know is it correct RUU for my At&t HOX?
My Current Info is
Software Number "1.85.502.3" | Radio 0.17.32.09.12 | Hboot 1.09.0000
Click to expand...
Click to collapse
If you have Super CID, do not run the RUU. It will brick your phone.
If you're not sure, type the following command into your command line:
fastboot oem
readcid
redpoint73 said:
That is the right RUU for the AT&T version.
Is your phone stock or modded?
Click to expand...
Click to collapse
Sent from my HTC One XL using XDA Premium 4 mobile app

//JavaJ said:
If you have Super CID, do not run the RUU. It will brick your phone.
Click to expand...
Click to collapse
If the phone is s-on, yes that is right.

First of All Thanksss
yeahhhh its S-on
and please let me know why super cid will brick?? I thought super cid means any ruu will work..lol :silly:
and no mine is not super cid ... so I will upgrade it. :highfive:

SuperCID just means that at&t phones were able to unlock via htcdev because the at&t CID was blocked. SuperCID + s-on + jb RUU = brick. This is because a CID check that occurs halfway through the RUU update doesn't allow the RUU to finish, therefore ending up with a partially completed RUU, which means a bricked phone.
Sent from my Evita

xoreg93 said:
and please let me know why super cid will brick?? I thought super cid means any ruu will work..lol :silly:
Click to expand...
Click to collapse
What timmaaa mentioned is basically a bug. The RUU shoudn't run halfway like that, but for some reason on JB RUUs, it does (past RUUs were fine with SuperCID).
But also, what you said above is not true. SuperCID will not allow "any" RUU to work. It only bypasses CID check. Trying to run a RUU for an older hboot will fail version check. You need s-off to run "any" RUU.

thanksssss ALL Update Successful.....