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.

Install a custom ROM with HTC official unlock

Can anyone please tell me how to install a custom ROM onto my Desire S with the bootloader unlocked via HTC Dev and S-ON?
My guess is that you install CWMR and flash it via that. But you need root access to do that, I thought unlocking the bootloader was meant to eliminate this.
Also, I've been reading that people are having issues installing ROMs this way, they are experiencing a hang at the HTC logo on boot.
Any information will be greatly appreciated, thank you.

spagmuff said:
Can anyone please tell me how to install a custom ROM onto my Desire S with the bootloader unlocked via HTC Dev and S-ON?
My guess is that you install CWMR and flash it via that. But you need root access to do that, I thought unlocking the bootloader was meant to eliminate this.
Also, I've been reading that people are having issues installing ROMs this way, they are experiencing a hang at the HTC logo on boot.
Any information will be greatly appreciated, thank you.
Click to expand...
Click to collapse
After you flash the custom ROM using CWM, you then have to extract the boot.img file from the ROM.zip file and manually flash it in FASTBOOT mode. That is the nature of the unlocked bootloader. The boot partition is not mounted R/W in recovery mode, it is only mounted R/W when you are in bootloader FASTBOOT mode.

Ok, from reading yours and various other posts in the forum, I need to do the following to install a custom ROM with an unlocked bootloader and S-ON:
1. Unlock bootloader via HTC's website
2. Root phone (with gingerbreak apk?)
3. Install CWM via ROM manager
4. Backup existing ROM with CWM and backup files with titanium
5. Install ROM via CWM (wipe data, wipe cache, install ROM)
6. Flash boot.img (HBOOT, fastboot, and flash image)
7.Reboot into cyanogenmod
If I have anything wrong, please let me know. Thanks.

spagmuff said:
Ok, from reading yours and various other posts in the forum, I need to do the following to install a custom ROM with an unlocked bootloader and S-ON:
1. Unlock bootloader via HTC's website
2. Root phone (with gingerbreak apk?)
3. Install CWM via ROM manager
4. Backup existing ROM with CWM and backup files with titanium
5. Install ROM via CWM (wipe data, wipe cache, install ROM)
6. Flash boot.img (HBOOT, fastboot, and flash image)
7.Reboot into cyanogenmod
If I have anything wrong, please let me know. Thanks.
Click to expand...
Click to collapse
Step 2 and 3 are not necessary. After you Unlock the bootloader, you could then simply flash ClockworkMod in FASTBOOT mode.
1. Unlock bootloader.
2. Flash CWM image in FASTBOOT mode.
3. Backup existing ROM with CWM.
etc.

Successfully installed latest nightly r2 yesterday night :O
All is fine, 3D performance is smoothly and fine...
Thanks for yours posts

I would also like to thank you tpbklake, haven't tried it yet, but I'm sure it'll work!

I will be getting a new unbranded Desire S in a couple of days,
In case it will be running HBOOT 2.00.0002 with S-ON will I be still able to flash a custom rom on the device? AKAIK S-ON only protects the radio from being modified.
sorry, I'm new to this
edit: okay i read its not possible to flash a custom rom, but then what can i do when I rooted and flashed a custom recovery?

kjdfkvdjjndvldmv; awesome

xStreame said:
I will be getting a new unbranded Desire S in a couple of days,
In case it will be running HBOOT 2.00.0002 with S-ON will I be still able to flash a custom rom on the device? AKAIK S-ON only protects the radio from being modified.
sorry, I'm new to this
edit: okay i read its not possible to flash a custom rom, but then what can i do when I rooted and flashed a custom recovery?
Click to expand...
Click to collapse
Either isn't possible without s-off, look at the index thread, it's all there.
Swyped from my desire s running damn sweet ice cream

I'm on an Inc2 but since it's basically the same I hope this applies...
I'm in the same position as the OP with the newly unlocked bootloader via HTC.
I flashed cwm through fastboot but now I can't reflash through ROM Manager. I installed both SuperUser and BusyBox but both point the finger at eachother saying the other needs to be installed. What am I missing??

Kayak83 said:
I'm on an Inc2 but since it's basically the same I hope this applies...
I'm in the same position as the OP with the newly unlocked bootloader via HTC.
I flashed cwm through fastboot but now I can't reflash through ROM Manager. I installed both SuperUser and BusyBox but both point the finger at eachother saying the other needs to be installed. What am I missing??
Click to expand...
Click to collapse
Download the latest su-3.0.x.zip file. Then boot into CWM recovery and install this zip file. This will root the current ROM you have installed and then ROM Manager and BusyBox will both be happy.

@korenisko
So you unlocked via HTC dev, flashed custom recovery, wiped all partitions, flashed cyanogenmod, rebooted into fastboot, flashed boot.img via fastboot (fastboot flash boot /pathtobootimg/boot.img, if i recall correctly) and then you were able to boot into cyanogen?
I did exactly these steps (only with 4ext instead of cwm, which shouldn't affect the result) and was stuck with the white bootscreen and no adb logcat output whatsoever.
Currently I am back on a prerooted official RUU (2.3.3), but it still performs really bad and I would like to have cyanogenmod.
Btw: I have a Desire S, hboot 2.00.0002, S-ON, no carrier branding.
Thanks,
wenzlern

The currect way
I Have HTC Desire S with original Rom 2.10.401.8 and HBOOT 2.00.0002 S-On
My goal is to install the Endymon
I read many thread and i understood that the curret way to do this is:
Downgrade My ROM from 2.3.5 ( 2.10.401.8 with HBOOT 2.00.0002) to a ROM 2.3.3 with HBOOT 0.98.00000 (Ex: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed.exe)
To do this i need to follow the steps from 1 to 7 of this
http://forum.xda-developers.com/showpost.php?p=20535265&postcount=26
Now i need to change HBOOT, Change Recovery and Root the phone. To do this i need to use Revolutionary tool for Windows from http://revolutionary.io/ and follow the istruction.
Now i can download the custom Rom and install using this way:
http://forum.xda-developers.com/showthread.php?t=1257731
Is It right?
Thanks

Hello, I just want to share my experience on how i managed to S-OFF my phone. My main problem was that I had the latest ruu on 2.10.401.8 and couldnt downgrade. Even though i unlocked the bootloader using the htcdev .bin file I couldnt install the proper recovery (clockwork mod) nor a previous ruu. So here is what I did.
I first unlocked the phone using the htcdev.
Then I followed those pretty 7 steps mentioned on prev post.
and changed my version to a prev one.
I r e l o c k e d my phone using htc supertool and
clicked my 1.47 ruu exe file. That worked and it downgraded my phone.
After that it was a piece of cake to use the revolutionary tool to S-OFF.
Thanks all the xda community for the infos i got and managed to do it....
cheers

mannkan said:
Hello, I just want to share my experience on how i managed to S-OFF my phone. My main problem was that I had the latest ruu on 2.10.401.8 and couldnt downgrade. Even though i unlocked the bootloader using the htcdev .bin file I couldnt install the proper recovery (clockwork mod) nor a previous ruu. So here is what I did.
I first unlocked the phone using the htcdev.
Then I followed those pretty 7 steps mentioned on prev post.
and changed my version to a prev one.
I r e l o c k e d my phone using htc supertool and
clicked my 1.47 ruu exe file. That worked and it downgraded my phone.
After that it was a piece of cake to use the revolutionary tool to S-OFF.
Thanks all the xda community for the infos i got and managed to do it....
cheers
Click to expand...
Click to collapse
Congrats. XDA is really helpful.

Sarina,
No need to wipe dalvik cache?
bcoz few ROM's developers days it a must!!!!
I trying to flash CM7.1 stable version.

mannkan said:
Hello, I just want to share my experience on how i managed to S-OFF my phone. My main problem was that I had the latest ruu on 2.10.401.8 and couldnt downgrade. Even though i unlocked the bootloader using the htcdev .bin file I couldnt install the proper recovery (clockwork mod) nor a previous ruu. So here is what I did.
I first unlocked the phone using the htcdev.
Then I followed those pretty 7 steps mentioned on prev post.
and changed my version to a prev one.
I r e l o c k e d my phone using htc supertool and
clicked my 1.47 ruu exe file. That worked and it downgraded my phone.
After that it was a piece of cake to use the revolutionary tool to S-OFF.
Thanks all the xda community for the infos i got and managed to do it....
cheers
Click to expand...
Click to collapse
Many thanks for this it has helped me get S-off again after a very frustrating weekend.

[Q] Downgrade from android 4.0 to 2.3 on sensation

Hello xda users.
I want to root my sensation, and therefor i need to get it from android 4.0.3 to 2.3 so it can be possible for me to do.
My HTC
HTC Sensation Z710e
Android 4.0.3
Sense 3.6
Softwarenumber 3.32.401.5
Here is the thing, ive looked around for hours on filefactory.com
put i cant seem to find a file that can put my sensation back to stock rom, so i can start root it. Could any of you be kind and help an noob out here?

Are you S-ON?

Yes S-on ..

you can root your ICS with S-On
Go to htcDev and unloock your phone
flash in a new recovery using "fastboot flash recovery recovery.img" using the recovery.img file extracted from PG58IMG.zip
then using cwr flash the updatede SU
Boom! your root
using htcdev unlock whill wipe all your programs and settings AND void your waranty. and u might brick your phone
AND FYI u cant downgrade your Hboot if u are S-ON and the new 1.27 is imposible at this time to get s-off

i will go do that asap ..
Thank you for your quick answers ..
Best regards

maydayind said:
you can root your ICS with S-On
Go to htcDev and unloock your phone
flash in a new recovery using "fastboot flash recovery recovery.img" using the recovery.img file extracted from PG58IMG.zip
then using cwr flash the updatede SU
Boom! your root
using htcdev unlock whill wipe all your programs and settings AND void your waranty. and u might brick your phone
AND FYI u cant downgrade your Hboot if u are S-ON and the new 1.27 is imposible at this time to get s-off
Click to expand...
Click to collapse
THe line "then using cwr flash the updated SU", can you explain further please?

Use CWM (Clockwork Mod) to flash the SU package - if you don't know how to do that then don't even try

i do know what that is, its just my english isnt that well.
i went to htcDev, and unlocked my sensation.
then i got rom manager on android market and tried Flash Cwr but im stuck at here..

SirLange said:
i do know what that is, its just my english isnt that well.
i went to htcDev, and unlocked my sensation.
then i got rom manager on android market and tried Flash Cwr but im stuck at here..
Click to expand...
Click to collapse
ROM Manager needs root to function, and since you don't have root yet you'll have to flash the recovery through fastboot. Then you can install Superuser through your recovery.
But wait, you want to downgrade to Gingerbread? You won't be able to do that since your device will still be S-ON, and Gingerbread won't boot on HBOOT 1.27 (necessarily for ICS).

So the thing Maydayind said about
"you can root your ICS with S-On"
What did he mean with it ?

Update user Dictionary in Android 4.x
Hello,
Anyone who has an app where you can update many words into the user Dictionary?
Thanks.

problems with TMOUS unlocked sensation ICS 4.0.3.

hi guys,
I'm completely new to all this android stuff, so please point me to the right direction since i have problems with my HTC Sensation.
1. I have HTC Sensation 4G from T-Mobile US (used with Beeline Armenia SIM card in Armenia) which had Android default version for that model - 2.3
2. I updated it with Software Update from the phone menu to version 4.0.3. and after that my wi-fi refuses to work.
I've searched numerous posts on this forum on how to fix this issue and found solution named Elegancia by Steve007 with some custom rom and other stuff.
Can you please help me with sorting this issue, i'd appreciate anything that can help me to resurrect wi-fi on my phone.
Thanks in advance
for HBOOT i have the following info displayed there:
*UNLOCKED*
PYRAMID PVT SHIP S-ON RL
HBOOT - 1.27.0000
eMMC - boot
Jan 13, 2012, 17:33:34

From what I read in your post you downloaded a official 4.0.3 update via OTA to your device and then let it flash via the device. Now your WiFi does not work.
Also from your post I see you are HTC Dev unlocked. This tells me you need to flash the correct boot.img via fast boot because Wifi not working is a common problem for devices that a HTC Dev unlocked after flashing. What is weird though is that is a official update package and it should have flashed the boot.img.
Please post if you have the stock recovery or a custom recovery like Clockwork Mod Recovery or 4EXT Recovery.
Look on your SD card in your Download folder and see if the update file is still there, and if so post the name of the file.
Also have you tried to flash any other ROM to your device besides the update?

Hi,
Yes I'm in HTCdev Unlocked mode.
I have no idea why the official update package hasn't flashed the boot.img file.
I looked into the Downloads folder on SD card and found nothing there.
I think i don't have any recovery.
I haven't tried other ROM, the only thing i tried was PG58IMG.zip file from HBOOT menu which contained the cid T-MOB010, which my phone originally had, but i think it didn't do anything.
Thank you
T-Macgnolia said:
From what I read in your post you downloaded a official 4.0.3 update via OTA to your device and then let it flash via the device. Now your WiFi does not work.
Also from your post I see you are HTC Dev unlocked. This tells me you need to flash the correct boot.img via fast boot because Wifi not working is a common problem for devices that a HTC Dev unlocked after flashing. What is weird though is that is a official update package and it should have flashed the boot.img.
Please post if you have the stock recovery or a custom recovery like Clockwork Mod Recovery or 4EXT Recovery.
Look on your SD card in your Download folder and see if the update file is still there, and if so post the name of the file.
Also have you tried to flash any other ROM to your device besides the update?
Click to expand...
Click to collapse

big_tig said:
Hi,
Yes I'm in HTCdev Unlocked mode.
I have no idea why the official update package hasn't flashed the boot.img file.
I looked into the Downloads folder on SD card and found nothing there.
I think i don't have any recovery.
I haven't tried other ROM, the only thing i tried was PG58IMG.zip file from HBOOT menu which contained the cid T-MOB010, which my phone originally had, but i think it didn't do anything.
Thank you
Click to expand...
Click to collapse
The PM58IMG.zip file you flashed what was it suppose to be flashing to your device? Can you upload it to dropbox or something so I can downlosd it and take a look at it. Also I will see if I can not get a boot.img from the official T-Mobile ICS update and upload it so you can try to flash it via fastboot.

[Q] Flashing RUU on s-off?

Didn't find to much related to specifically to what I want to do.
I was tinkering with my software and messed something up and won't boot.
I can seem to find a strict stock rooted rom from t-mobile
Can I do the following without messing up my phone?
I already have s-off and twrp and a none working rom.
I want to relock bootloader, flash ruu
unlock again and flash recovery and root file.
I think this should work without messing up the phone and I should still have s-off right?

M9x3mos said:
Didn't find to much related to specifically to what I want to do.
I was tinkering with my software and messed something up and won't boot.
I can seem to find a strict stock rooted rom from t-mobile
Can I do the following without messing up my phone?
I already have s-off and twrp and a none working rom.
I want to relock bootloader, flash ruu
unlock again and flash recovery and root file.
I think this should work without messing up the phone and I should still have s-off right?
Click to expand...
Click to collapse
I've ran an RUU a couple times and still had S-off when it was done. It should not impact that at all.

Or you can skip all that and just flash the t mobile ROM in the dev section.
But, yeah, you will keep soff through the ruu
HTC_One_S | S-OFF | ViperOneS_2.2.0 | Black&Blue_Inverted_Sense | Bulletproof_1.4
Inverted Sense _4+_and_5_click me

No need to relock bootloader if s-off. You should flash stock recovery so and use a CID according to your RUU file.

Stock recovery not needed.
Just ruu away
Verstuurd van mijn HTC One S met Tapatalk

Oooh
I also thought too you needed to re lock to flash a ruu.
I guess that is only if not s off then.
Just need to match cid though still.

SCID will work with any RUU. But you shouldn't use it if you insist to upgrade by OTA... Some people reported a brick this way.

Updating EU RUU from 2.31.401.5 to 3.16.401.8 (going from a CM10.1 version)
Well here is what I've done if it can help some. No warranty that it'll work for everyone, but let's go:
First thing : I've started with CM10.1, S-OFF, SuperCID (11111111) and TWRP 2.5.0.0
I DID NOT relock the bootloader and NOT put back the original Recovery
1) I've put back my original CID (EU Bouygues eg. HTC__203. You should put your original one). Fortunately, I had the original mmcblk0p4 file backup (just copy back the original file to /dev/block. See here : http://forum.xda-developers.com/showthread.php?p=26516911#post26516911).
2) once my original CID has been put back (still S-OFF and TWRP and not relock), I've started in bootloader mode the RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5 and let things run
3) after the installation and reboot, I went to Parameters/Update/Check to force the JB update 3.16.401.8 download.
4) I've let the JB update to be performed (several reboot): all went fine. Going into fastboot, I'm still Unlocked / S-OFF / HTC__203 (original) / Radio 1.11.50 and HBOOT 2.15.000. Sounds good !
5) I went back into fastboot to re-flash the TWRP 2.5.0.0 (fastboot flash recovery openrecovery-twrp-2.5.0.0-ville.img)
6) I then reboot into Recovery : now TWRP is back ! In TWRP, try to reboot into bootloader. TWRP will warn you that you're not ROOT and suggest to install root on your phone. Hit YES.
7) Reboot normally your phone : you should have now a Super SU Installer icon in your apps. Open it, choose install via TWRP, and you're good to go! You've now the latest HTC JB sense version with root.
Optional :
-You can perform a full TWRP backup (with Sense/original CID) in case of further HTC update (?)
-You can put back your SuperCID if wanted
Now if you want to test the CM10.1-3.4 kernel here http://forum.xda-developers.com/showthread.php?t=2302248, it's booting fine (after full wipe)
Voilà !
Hope this helps

yeah
with the tmo model I can get the JB ruu right from HTC
I have just been having issues that I want to get stock and maybe root.
Will double check CID and just flash then.
I think hboot and radio on jb equivlent already but will try that.
Thank you

I wanted to post a little warning here, and relate what happened with my RUU update. First, I'm unlocked, s-off, Hboot 1.13.0000, superCID (11111111), running TWRP 2.5.0.0.
So I read somewhere that the latest RUU may not install correctly if on an older Hboot so I fastboot flashed the latest 2.15, no problems. Then I found a decrypted ROM that Hasoon2000 had posted thinking that this would give me the firmware I wanted, I believe this was based off of RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1. 11.50.05.28_10.27.50.08L_release. I then Fastboot flashed: (I didn't relocking bootloader or changing CID but I did first flash stock recovery because I wasn't sure it I needed to or not)
1. fastboot erase cache
3. fastboot oem rebootRUU
4. fastboot flash zip "name of ROM".zip
The script ran and everything flashed successfully, so I reflashed TWRP 2.3.3.0 and the phone booted just like stock ROM. At this point I checked the Hboot and it was 2.04 something! with a 1.11?? radio. (So this told me I likely wouldn't have needed to first flash the 2.15 Hboot not sure about this tho) I then tried to restore my backed up SDcard and here is where I ran into problems. My SDcard/internal storage only had 48.6MB of space! Nothing I did would change it I worked with this for several hours last night before giving up and this morning I thought to try running a different Tmobile RUU. Found this thread http://forum.xda-developers.com/showthread.php?t=2250573 and downloaded this Firmware package: http://www.filedropper.com/firmware_1 and ran the same fastboot commands (changed recovery back to stock which I probably wouldn't have needed to do...??) and everything flashed perfectly (I needed to run the "fastboot flash zip firmware.zip" the second time, which is normal). I now have my SDcard back with Hboot 2.15, radio 1.13, superCID and s-off yet, "hopefully" am ready to flash the new 3.4 updated stuff!
I suspect the reason for my problems lay in my flashing a euro ROM/RUU, but I really don't know that for sure. This is just what happened to me. Hope this helps a bit!

i believe i have an issue that is too challenging for me. i flashed the lates trickdroid and for some reason i couldnt get my radio to show. my baseband version was unknown. i tried to flash a new radio tto no avail. finally i flashed the jb ruu and now the rom will work for a couple of minutes and then reboot still with unknow baseband radio version. im s off with super cid. any thing to help woul be appreciated.

Did you run the ruu exe or how did you flash it?
Sent from my HTC VLE_U using xda premium

Clom801 said:
i believe i have an issue that is too challenging for me. i flashed the lates trickdroid and for some reason i couldnt get my radio to show. my baseband version was unknown. i tried to flash a new radio tto no avail. finally i flashed the jb ruu and now the rom will work for a couple of minutes and then reboot still with unknow baseband radio version. im s off with super cid. any thing to help woul be appreciated.
Click to expand...
Click to collapse
Have you tried the fastboot flash zip firmware.zip method? It's working great at updating firmware for all the AOSP ROMs.

TheArtiszan said:
Did you run the ruu exe or how did you flash it?
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
i ran the RUU. i tried the TMOUS ICS and EU JB
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
el_smurfo said:
Have you tried the fastboot flash zip firmware.zip method? It's working great at updating firmware for all the AOSP ROMs.
Click to expand...
Click to collapse
is that the new method posten in the development section? i will try
ok, tried it and it didnt work. still shows no signal with an x ans reboots after a couple minutes

You can try the tmous jb one.
That might be better as not a downgrade.
Not sure about the eu one but that could be why the ics one is not working.
Sent from my HTC VLE_U using xda premium

Clom801 said:
i ran the RUU. i tried the TMOUS ICS and EU JB
---------- Post added at 06:58 PM ---------- Previous post was at 06:57 PM ----------
is that the new method posten in the development section? i will try
ok, tried it and it didnt work. still shows no signal with an x ans reboots after a couple minutes
Click to expand...
Click to collapse
Interesting thought... Try a cm based ROM. They use a radio in a different system folder. If it still doesn't work, sounds more like a hardware failure.