Database Info

[Q] Anyway to know the ORIGINAL stock rom version?

Hi people, I'm a noob
Anyway, I just installed the latest HTC Revolution HD ROM which gives the Sensation XE for the normal Sensation. It's great. But then I discovered that I'm having the hardware problem. I need to send my phone back to the HTC support and let them fix. However, since I've just rooted it, I lose my warranty. And I need to restore my phone back to my original stock ROM.
BUT, I don't know what's my original stock ROM was.... anyway to find out? I live in Thailand, I downloaded the Asia WWE ROM, doesn't work.... So I really need help now....
Thank you very much...

What's the CID of the phone?

surely as long as it's a stock version on the phone you should be ok? or has that all changed now from the old Windows Mobile days when you just had to security lock it and stick an official ROM back on to hide all traces of being hacked?

Different regions have different versions, and then on top of that you have operator versions - a lot more than WinMo

Im sorry to ask this, but how to check Srnsation CID?
Sent from my HTC Sensation XE with Beats Audio using XDA App

Reboot into fastboot, and make sure you have the android SDK (adb, fastboot, etc.) and use command prompt to navigate to wherever you have the android sdk saved. Type fastboot getvar cid and it will read your cid.
Mine is T-MOB010, (tmous), my stock version that came on the phone was 1.29.xx I believe, but an OTA immediately updated me to 1.45.xx. Unless of course you have a Sensation XE, in which case I believe it's 1.73. But that's tmobile US, I don't think you have tmobile us, so check your CID.

Specifically your stock ROM is 1.29.531.2, there may be other 1.29.xxx.x RUUs so always best to be specific to avoid confusion
The current stock XE RUU is 1.73.401.2

MusicMan374 said:
Reboot into fastboot, and make sure you have the android SDK (adb, fastboot, etc.) and use command prompt to navigate to wherever you have the android sdk saved. Type fastboot getvar cid and it will read your cid.
Mine is T-MOB010, (tmous), my stock version that came on the phone was 1.29.xx I believe, but an OTA immediately updated me to 1.45.xx. Unless of course you have a Sensation XE, in which case I believe it's 1.73. But that's tmobile US, I don't think you have tmobile us, so check your CID.
Click to expand...
Click to collapse
Do i need to run CID on adb to restore my phone to stock. Im on tmous also and i have the ota update before i root and flash my phone, but i need to restore it back to out of the box condition so i can send it also for warranty. Im a super noob and not really a techy guy so im asking for your help on the steps to restore my phone. I have read most of the threads and some of them are too confusing for a noob like me. From what I understand is i have to run adb to change my CID then download the correct RUU.exe for Tmous. Do i really need to run the adb and go straight to run RUU? Thanks in advance and sorry to question you so much.

[Q] Sending Sensation back for repair - Warranty Q

So my Sensation was S-Off and rooted however it started to play up so went back to S-On and Un-rooted, HBOOT now reads ****Locked**** and S-On. Is this all I need to do, does something more need to be done, will they be able to tell? They said on the phone if warranty is voided then I must incur the cost of fixing it..
Id really appreciate your help guys.

If its fully stock with s-off and stock recovery your good to go

ilostchild said:
If its fully stock with s-off and stock recovery your good to go
Click to expand...
Click to collapse
Ok thanks, how do I know if I have stock recovery?

Hi, i am sending mine back tomorrow as well.
Do I have to put it back to S-ON? I've heard its risky.

Best to, and it's not risky if you follow the guide to a T
Make sure you've set the CID back to what it should be before doing it (assuming you changed it in the first place)

Hey, it looks like mine's going back as well.
I'm a little unsure of which version HTC rom was default on it because I bought it from Pixmania and not a carrier.
It originally had Vodafone branding and the box is written in German.
I don't think I've changed off of the original kernel or radio as I've only switched roms through ROM Manager since I rooted the phone using these instructions.
-ANkh

I too am wondering the same thing, but my problem is slightly different. My phone wont even power on so i was unable to s-on factory rom it, im unsure of what exactly needs to be replaced on the phone so idk if theyre gonna be able to see that the software has been changed.

Hi again,
I found my CID: VODAP102, it's for Vodafone Germany.
Where can I find the matching stock ROM?
Thanks,
ANKh

Ankhwatcher said:
Hi again,
I found my CID: VODAP102, it's for Vodafone Germany.
Where can I find the matching stock ROM?
Thanks,
ANKh
Click to expand...
Click to collapse
Stock rom are here http://forum.xda-developers.com/showthread.php?t=1074559 , but No Voda DE. So Vodafone UK is logical path i presume...

dublinz said:
Stock rom are here http://forum.xda-developers.com/showthread.php?t=1074559 , but No Voda DE. So Vodafone UK is logical path i presume...
Click to expand...
Click to collapse
I'm not so sure. This guy had a Vodafone_DE RUU, so I've sent him a message begging him to re-post it.

EddyOS said:
Best to, and it's not risky if you follow the guide to a T
Make sure you've set the CID back to what it should be before doing it (assuming you changed it in the first place)
Click to expand...
Click to collapse
Uhoh, i didn't change the CID back but I did S-ON...
Will they notice if its just a hardware repair?
Too late now, I guess I will find out...

Okay, my Sensation is ready to go for repairs:
I found an old HTC_Pyramid_Vodafone_DE RUU here.
I installed it. And updated... and updated... and updated...
Because I still had my original cid I was able to get my phone into fastboot and "fastboot oem writesecureflag 3".
Now my phone is running a stock rom with locked bootloader and locked S-On and stock recovery.
-ANkh

help i have my sensation at the newest ics, tried running this and said update failed unknown error, please help im desperate.

Ankhwatcher said:
Okay, my Sensation is ready to go for repairs:
I found an old HTC_Pyramid_Vodafone_DE RUU [...]
I installed it. And updated... and updated... and updated...
Because I still had my original cid I was able to get my phone into fastboot and "fastboot oem writesecureflag 3".
Now my phone is running a stock rom with locked bootloader and locked S-On and stock recovery.
-ANkh
Click to expand...
Click to collapse
Hi,
was the method successful? Did they not recognize anything?
I have to return my Sensation for repair (dust under the screen), and i don't want to loose my warranty.

greg.house said:
Hi,
was the method successful? Did they not recognize anything?
I have to return my Sensation for repair (dust under the screen), and i don't want to loose my warranty.
Click to expand...
Click to collapse
Yes it did, HTC UK repaired the phone and converted it to a stock HTC UK phone without any German or Vodafone stuff on it anymore.
They didn't charge me anything for it.

I've send my desire s back to HTC caus of some probs with my battery.. it was rooted and s-off.. when I get it back it was s-on and unrooted.. I've paid for nothing..
Sent from my HTC Sensation XE with Beats Audio Z715e using XDA

I sent my Sensation back a few weeks ago because the touchscreen stopped working with S-OFF and they didn't notice and is still S-OFF now!

flashing ICS back to stock

Hey guys,
I have to flash my HTC Sensation back to stock, because it have a little hardware error (its sometimes suddenly shutting down ...)
My Sensation is from Germany..
On my phone is currently the Cyanogenmod 9. Yesterday I flashed the eng Hboot 1.17, because I read somewhere that i have to. Is this true?
After this I wanted to restore my backup of the original Rom, but this doesn't work. There were some errors and so on.
I think if I would send it back to HTC I have to uninstall the CWM and I have to install the old Hboot 1.18, but after a lot of reading today and yesterday I'm very confused., because I found no working way ...
greets
Tobi

http://forum.xda-developers.com/showthread.php?t=1516255
Person with pretty much same problem and some advice.

1. Flash old 1.17 FW (unless you're Super CID, in which case you may not need to)
-> ok i flashed a 1.17 FW. Everything is still working without any issue,but after I unlocked my phone i had the 1.17.111and so on FW. Now I have the 1.17.2008. Is this maybe a wrong fw?
2. Flash the RUU of your choice (normally the one your phone came with, if available)
->I don't know the RUU which my phone came with , the most was done by the program revolutionary. I have an unbranded European Sensation. Which is the right RUU?
RUU_Pyramid_HTC_Europe_1.27.401.3_Radio_10.42.9007.00P_10.11.9007.15_M_release_192183_signed.exe
RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007.00P_10.11.9007.15_M_release_192608_signed.exe
RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.9007.00U_10.51.9007.27_M3_release_198179_signed.exe
RUU_Pyramid_HTC_Europe_1.45.401.2_Radio_10.56.9035.00U_10.14.9035.01_M_release_208857_signed.exe
RUU_Pyramid_HTC_Europe_1.45.401.3_Radio_10.56.9035.00U_10.14.9035.01_M_release_219990_signed.exe
RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.9035.00U_10.15.9035.02_2_release_228602_signed.exe
I read that I can brinck my phone very fast with it, so it is very important
I just have to download the exe and run it, after this it will flash my phone if it is in USB Debugging ?
I hope it is so easy to downgrade the phone from 4.0.3 to 2.3.4
3. Reset Super CID to one of your choice (again, usually the one your phone came with)
Is this important? Or is it enought if I just reinsert the battery, becuase I don't know if I'm Super CID
4. S-ON using the fastboot command in the guide in the Dev forum
with adb-tools:
-fastboot oem writesecureflag 3
-fastboot reboot-bootloader
right?

RUU_Pyramid_HTC_Europe_1.50.401.1_R_Radio_10.58.90 35.00U_10.15.9035.02_2_release_228602_signed.exe
This was on my unbranded Sensation when I bought it.
For SuperCID look here (Step 4):
http://forum.xda-developers.com/showthread.php?t=1192300&page=1

warning
i updated to icecreamsandwich firmware h boot 1.23. i neede to go back to stock so i follwed directions on guide to s-on and ran ruu that came with my phone and it says error get the right bootloader ruu .however it didnt brick it but bootloader says security warning wifi and wifi hotspot both gives error. ive tried everything i know to fix it with no luck. ive heard its because i upgraded the firmware.

ok I'm now on Super cid. This was just very easy
Ok now I have to download the RUU (filefactory is very slow... )
What will happen, when I would flash the wrong EU ROM? Or is this just impossible?
Is it important to reset the cid to the cid which was set, when I got the phone? Or is it set back by flashing the RUU?
I have a lot of questions, but I don't wanna brick my lovely phone
Edit:
Ok everything is now fine. My phone is now on Andorid 2.3.4, S-On, old CID and unrootet...
I hope they will repair it, because sometimes the phone run 2 days without any issue and sometimes it just runs some hours without issue...

Help restoring Orange Uk HTC One S to stock?

Hi There,
I've sold my HTC One S and need to reflash it to stock. It was originally on Orange UK.
I can't find the Orange UK rom or RUU anywhere.
While I don't think the buyer will know or care what ROM it has, the HTC boot screen saying its running a software build owned by HTC doesn't really help.
Has anyone got any ideas of what I can do?
Thanks,
Omar

omar_g said:
Hi There,
I've sold my HTC One S and need to reflash it to stock. It was originally on Orange UK.
I can't find the Orange UK rom or RUU anywhere.
While I don't think the buyer will know or care what ROM it has, the HTC boot screen saying its running a software build owned by HTC doesn't really help.
Has anyone got any ideas of what I can do?
Thanks,
Omar
Click to expand...
Click to collapse
OKAY,
1. Try flashing stock recovery hopefully the initial boot image shall be gone ELSE
2. Save your CID, change it to generic CID like 11111111, run 2.2 RUU(EUR firmware or your firmware if available) (by this time you should have manually flashed stock recovery, and bootloader locked), after this your phone is completely STOCK! If wanna return back to orange, unlock bootloader, flash custom recovery, gain root and change the cid back to original! than flash stock recovery and bootloader lock!

[REF] Dead/Bricked phone after JB OTA, QHSUSB_DLOAD

Hi All,
There are more and more reports coming in from people who ended up with a dead/bricked phone after the JellyBean Update 4.1.1 , 3.16.401.8 OTA. As you connect it to your PC you will soon find out it's in QHSUSB_DLOAD mode.
The purpose of this threat is to see how many people are affected, what people have done to attempt to recover their phone, and to find a possible solution (this chance seems rather small though).
There are alot of post about this in the JellyBean Speculation/News/Discussion threat, starting from page 157.
There are 2 threats about it in Q&A:
One S in QHSUSB_DLOAD mode
My HTC to really died
Reported attempts to recover:
QHSUSB_DLOAD Fix by team Unlimited
Unbricking HTC devices with the QHSUSB_DLOAD issue tutorial by kgs1992
Step 3 (and some others) from [TUT] Downgrade/Unbrick Ville S4
Another HTC one V recover guide where i can't find the link for.
Please report here if you have this issue. Please mention your CID, in what country you downloaded the OTA, the software version you upgrade from and the hboot version.
Also any new ideas to recover our phones our self are welcome!
My phone:
2.31 Unbranded Europe
1.14 Hboot
Downloaded in The Netherlands
1111111 Supercid

I have exactly the same problem, waiting...

As far as I know the issue is only caused by people who previously had SuperCID.
Sent from my HTC One S using Tapatalk 2

usaff22 said:
As far as I know the issue is only caused by people who previously had SuperCID.
Click to expand...
Click to collapse
I thought I saw a report of a fully stock device and one htc__001 cid as well. I can't find them at the moment, but this is also why I started this threat. But there seem to be more of these reports of supercid indeed, though there are also allot with supercid who successfully updated.

My phone is bricked too
Orginal CID was HTC_0001 (maybe), branded by 1&1 Germany
but changed to 11111111 to flash a unbranded RUU (what had worked)
I had Stock Recovery and relocked bootloader

My phone is bricked too
SuperCID 11111111 Hboot 1.14 Recovery Stock y Relocked bootloader.

My phone is bricked too
Orginal CID was HTC_203 (maybe), not branded by telecom company - France
but changed to 11111111
I had Stock Recovery and relocked bootloader and flash the 2.31 RUU

hellgod said:
My phone is bricked too
Orginal CID was HTC_203 (maybe), not branded by telecom company - France
but changed to 11111111
I had Stock Recovery and relocked bootloader and flash the 2.31 RUU
Click to expand...
Click to collapse
Dam it didnt mean to hit thank so enjoy that lol.
@Vauix, did you run a RUU before updating? if so what one?

let's discuss who and what options tried to output the list of sections? How you think why it happened?

All of them seem to be caused by SuperCID. But the updater script allows flashing for SuperCID, so I wonder why they get bricked.
Sent from my HTC One S using Tapatalk 2

I agree with you. But what it is necessary to undertake that Ubuntu saw sections?

Same here.
SuperCID and ota
Now nobody can call me

Same here.
SuperCID too

Darknites said:
Dam it didnt mean to hit thank so enjoy that lol.
@Vauix, did you run a RUU before updating? if so what one?
Click to expand...
Click to collapse
Yes I ran a RUU prior to flashing this update, i didn't chance anything to the rom yet but to search for the OTA. it was the RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed.exe
I thought about my supercid before I ran the RUU but i thought the worst thing that could happen was i could get a error that it couldn't flash it.
Its rather weird that some guys with supercid managed to flash it successfully. And i still think I saw some people with other cid's with bricked devices.

SuperCID too, previously Vodafone germany, unbranded an relocked ...

I ran the OTA update twice on my supercid'd device successfully.
In opposite to what I could read here, my bootloader was unlocked before and still after the update.
The first time I ran the update I forgot to reflash stock recovery. The phone started updating and rebooted, but no changes had happened. After restoring stock recovery and downloading the update again, I successfully updated.
As I couldn't get root I restored Venom and downgraded my new hboot from 2.15 to 1.06.
Today I started a second try successfully without a glitch.
Basically I keep an untouched nandroid backup of every new rom installation on my local harddisk. This means in case of custom roms I do a nandroid before the first boot.
As this is not possible on stock recovery I change back to custom recovery after the first boot, doing my backup then. I'm just checking the needed boxes otherwise I only proceed during the setup - the complete customization is done afterwards.
In this case I restored a backup called 2012-08-23--08-18-16_htc_stock_2.31
Stock here means: No apps, no customizations, no nothing, simply: stock and supercid.
After that was done I restored apps with Titanium.
That's how it worked (pretty simple) Maybe this will help you find some reasons for what has happened to your devices.

Same problem here...
SuperCID

All people here seem to have SuperCID, I have not.
I got my ville for about 7 months now and never had SuperCID.
I did it like everytime:
-Wiped everything ( Data / Cache / System )
-Flashed Stock Recovery
-Relocked
-Flashed 2.31 Europe RUU in Bootloader ( yes, that works but I guess noone knows )
-Downloaded 4.1.1 Update and let the Device do its magic
Now my phone is bricked.
Strange enough, a good friend of mine whos barely able to use its phone, got the same issue.
Im 100% sure he doesnt have any modifications done to his device.
Already tried the Ubricking-Tutorial but the Partitions just dont show up :-/

I did the super CID, too. No my phone is dead. Won't even charge.
I tried to do Enumerating the partitions but could only find up to 3. No 4 or 12.
Please help :crying:

SuperCID, German ONE S unbranded. Dead.
Unbrick/Downgrade instruction did not work here.