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] Desire S crash during official OTA update

Hi
it is the second time that an official OTA ROM update of HTC crash during installation. Result : the phone is dead and has to be sent to service center
I would prefer install a new ROM on it. But how can I go for it knowing that my phone is not rooted yet and that I have no operational ROM... I can still go to the bootloader.
Small point, as a true Android fan, I am on linux or mac, no more windows pc at home
thanks a lot if anybody can give me a hand

complementary information :
HBOOT 2.00.0002
RADIO 3822.10.08.04_M

A simple way : unlock via HTCdev.
But be aware that htcdev method gets your phone info and that it is a single-way method. You have no chance locking the phone again so that htc will never see you unlocked your phone. They will definitely know it. So, practically, you will lose your warranty.
It can be done via fastboot. Follow instructions on the website www.htcdev.com
Sent from my Desire S with Virtuous Affinity

***LOCKED***Security Warning on bootloader

Hi all,
I have tired to flash the new Rom yesterday and during checking the signature device reboot and installer said that it can not proceed.
After reboot phone goes directly into fastboot and gives ***Locked*** with Security Warning massage. I have tried different RUU but it is exactly the same.
Installation is failing on the checking signature.
I have tried Unrevoked3 but it is not able to find the device. Could you please let me know how to do it?
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-2822.10.0804_M
eMMC-boot
I was trying to upload RUU_Saga_S_HTC_Europe_2.10.401.9_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_234765_signed

http://forum.xda-developers.com/search.php?searchid=23896455
Error nr 141?
LE: hope it works now, if not search the forum, the link reffers to the search results.
You will certainly get the answer there.

Link does not work:
Sorry - no matches. Please try some different terms.

I have tried to find an answer but no luck so far, I am quite new to this. Is there anyone who can point me in the right direction?

Another solution is to try the RUU 2.10.401.8
I had some problems with the same Ruu, but not with the signature, and the previous version worked flawlesly.
What's your CID?
Sent from my HTC Desire S

I have tried few others RUU and every single of them is falling during the installation.

ok I manage to unlock the device finally
But again it is falling during the installation of a new ROM. Do I have to revert back Hboot to 0.98 before installation? if so how to do it?

So the RUU that I recommended completed successfully?
What do you want to do next?
Now you are S-ON, if you want to install custom roms you have to unlock your bootloader with the htcdev method(you will lose your warranty and need to flag manually the boot file) or to downgrade.
Sent from my Samsung Galaxy Tab

I want to downgrade the phone to orginal ROM T-mobile uk. So I could take off the simlock, I have put the unlocking code yesterday but nothing happens. I was advised to downgrade the rom and should be ok.

Could some help me out with my problem please when ever I am trying to upload new rom it is stuck on signature verification.

I will quote Enigmaamit as he said it better than me:
enigmaamit said:
SIM unlock and bootloader unlock are two completely different things.
Click to expand...
Click to collapse
The only way to SIM-unlock your phone yourself is a XTC clip... better ask your phone operator.

I know the diffrance between those two, I have ordered unlocking code. After putting this into device when ever I put into new sim card it stoped nofifing me about it. But it is not able to find a new network. Below what I have receive form operator:
"It said "Successful" but nothing has happened
Darren
posted this on Apr 11 16:22
This has happened to a handful of customers who have all had one thing in common - the phones have been "rooted".
By rooting a handset the owner has removed some of the restrictions on the phone, which allows the owner to install whichever software of the phone that they wish. Unfortunately this has caused some issues when an unlock code has been entered.
It is easily rectified by reinstalling the original operating system that the phone was supplied with, then applying the unlock code and the phone should be unlocked, truly, successfully.
You can then reinstall the software you had on the phone before attempting the unlock and continue using the phone as you wish."
So that is the reason why I am trying to revert any changes.

i for one don't believe this

So their replay is bull**** in that case?

In my opinion yes(i can't say that i am a very experienced user) but i like to think i know some stuff about this.
I can't imagine what custom rom/Ruu version/app will "block" you to sim unlock your phone.
The only restrictions may be made by the phone manufacturer.

So i will try through HTC Clip in that case. But why I can upload any new RUU?

like i said earlier, i had some problems to with the 2.10.401.9 ruu.
Try the 2.10.401.8 it should work, if your phone is branded try a gold card.

[Q] My phone is bricked (or what ever)

Hi
Before starting I want you to know that I have been through 5-10 threads regarding the subject problem and still not know what to do. I am basically a layman to Flashing. The most adventurous thing I have done is downgrading a Sony Xperia Arc S from ICS to Gingerbread using a simple sofware sort of thing called "flashtool" and downloading ......... (i am leaving it blank cuz at the moment I am quite confused. Lets call it its original firmware)
And before I can explain the problem I am confused between the following terms: RECOVERY, ROM, KERNEL and RUU. Kernel i know is a software layer between H/w and OS. But then why we need to flash it seperately???? it should be a part of OS: which i think is called a ROM. RUU is the update to a recovery. but what exactly is the difference between ROM and RECOVERY. both seem to be like some sort of an image file that contains complete OS. Then there are bloody BOOTs that you have to unlock and keep lock at some times. God knows why
Now coming to the problem:
My HTC One X (bought here in Pakistan and should be containing the international firmware, i dont know for sure)
One fine morning a few days ago my phone showed up the update HTC released recently which changes the appearance of the GUI. I was quite happy to see it and immediately selected the option to install the update. The update ran and installed successfully. I used the new GUI for 2 days or so and then suddenly my phone got stoned (or brick or stuck). It turned off when i tried to use it and then started showing
*** LOCKED ***
*** Security Warning ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.73.0000
CPLD-None
MI CROP-None
RADIO-5.1204.167.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW secure boot: enabled
MODEM PATH : OFF
Jun 21 2013, 18:24:41
Battery level is too low to flash
FASTBOOT USB
HBOOT
REBOOT
REBOOT BOOTLOADER
POWERDOWN
So I am screwed really badly. The USB debugging mode that i know is essential to install a firmware is not enabled. and my device is not rooted. The device is not charging up properly.
I have downloaded Hansoon all in one toolkit (which seems to be of no use since debugging mode is not enabled). I have android SKD downloaded in my pc. so is HTC Sync. But dont have any idea where to begin.
AND MOST IMPORTANTLY I WANT TO SAVE THE DATA INSIDE THE PHONE THAT I CANT ACCESS.

..... i am trying to root the device using hansoon. but for that i need to generate some sort of a code. Now my device is showing up one option named barcode where i can see MB SN and IMEI of the device. is it possible to generate that code using these three???

I think I have posted it in the wrong forum. mods please delete it. I am starting a new thread in the right forum

Your phone is HTC one X Endeavour ......this forum for HTC one X Evita.....please check HTC one X forum ....we can't really help u that much ... BTW u go to www.htcdev.com to generate unlock_code.bin and follow instruction from there coz right now your bootloader show ****security warning****
Swyped From BlueICESense_JBE

Looking for a compatible RUU File for HTC One S Cincinnati Bell (PJ40110)

Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance

Auraburst said:
Hello everyone! Sorry for my bad English
I've got a HTC One S (HTC__017) with unlocked bootloader, S-ON, HBOOT 1.06.0000 and Radio 1.11.50.05.28 and recently, i'm a little motivated to give a try for a Custom ROM (Obviously, there's more work to do with the S-ON) but i want to prevent a big accident in the process and i need the correct RUU File for my phone, I've been looking on my own the file but I couldn't find it
Now, someone knows which RUU file can I use? I'm novice with HTC Phones and this is new for me
Thanks in advance
Click to expand...
Click to collapse
It's easier to find the correct one if you know your firmware version/build number. If you're still using stock rom you can find it in settings>about>software information>more. If you already deleted the stock system on your phone you need to use
Code:
fastboot getvar all
in fastboot mode (look at the line beginning with "version-main"). Since you already unlocked your phone I assume you know how to use fastboot with the windows cmd.
RUUs can be found here for example. Just use the search function of your browser and be sure that you download a RUU and not an OTA. Since there are two versions of the One S you need to be careful not to use VilleC2 (Snapdragon S3 with 1.7 gHZ) files on a Ville (Snapdragon S4 with 1.5 gHz) and vice versa (this rule applies on roms, kernels, etc., too). If I remember correctly your hboot is Ville specific but if you want to be sure you can find the answer in the getvar all output (look at the line beginning with "product").

Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)

Auraburst said:
Thank you so much man, i understand a little more but i have another problem: i can't find a proper version of the RUU File (My build number is 3.14.422.11) and there's only one similar (3.14.422.9) and matches with my radio version (1.11.50.05.28) but i'm not sure if it works with my One S (It's a Snapdragon S4 and in the "product" line says "vle" btw)
Click to expand...
Click to collapse
The problem is that the only file with the 422 SKU is an OTA and not a RUU. If your phone was S-OFF you wouldn't need to use corresponding RUUs because you were able to flash any you want. It's a vicious circle in your case since you wanted the correct RUU before you start flashing. On the other side if you carefully follow the instructions of the S-OFF guides there shouldn't be any risk of bricking. Simply don't try to use any short cuts if any step doesn't not work the way the instructions tell you. Since I'm not living in the states I'm not completely sure but Cincinnati Bell is part of Bell Mobile, right? If that's correct I would change the CID to SuperCID (depending on the S-OFF method you use you may need to get the SCID anyway) and try to run one of the "BM" RUUs on AndroidRUU. Since all of them are older than you actual firmware your phone will be downgraded then but you can update it by using the OTA function in settings>about.
Btw.: With that output you can be sure it's the Ville and not the VilleC2.

Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone

Auraburst said:
Okay, so, in simple words, what can I do with SuperCID (S-OFF) is:
-Restore my phone with any RUU regardless of my version of Radio, and without any risk
-Safe downgrade to upgrade my version of HBOOT (Because I want to try a custom ROM and most require HBOOT 2.15)
If not so, tell me in what I am wrong, btw, there's any custom ROM that you can recommend? I want to try Cyanogenmod 12.1 or MaximusHD, both look great but I'm a little undecided and would listen to someone more experienced with this phone
Click to expand...
Click to collapse
Actually your radio doesn't matter at all in regard of RUUs. Flashing a RUU is never risky as long as it's a signed/official one and you do not turn off the phone during the flashing process or disconnect it from your pc. If you are not S-OFF and your CID and/or firmware version doesn't match (SCID always matches) official RUUs will simply abort the flashing process.
After you achieved S-OFF and got the SCID you simply need to relock your bootloader, boot into fastboot mode, connect the phone to your pc and run the RUU.exe. (As far as I remember relocking was needed for being able to install OTAs afterwards but I'm not completely sure. I just remember that I always did when I downgraded. Maybe someone else can confirm this.)
I personally do not like Cyanogenmod on this phone. Since there never was a GPE of the One S (the first HTC GPE that ever existed was the HTC One M7 GPE which is actually younger than this phone) there are no AOSP drivers for this phone and you can notice this problem for example in a worse camera quality on roms that are not based on sense (there are other problems but that's the most prominent one I can remember).
MaxximusHD is based on the leaked but never officially published android 4.2.2 firmware of the One S. If you want to use it without memory problems (the leaked firmware changes the way the phone interacts with it's memory) you need to flash the hboot 2.16. Instructions can be found in the Maxximus thread for example. I personally prefer hboot 2.16 because of its reorganized memory but the radio 1.20 that gets flashed with that firmware has some problems with the incall voice quality.
To sum it up, every custom rom has its pros and cons and every user has his/her own preferences so it's hard to tell others which rom to use. The best way is to look which ones fullfil your needs and to test them out by yourself.
Edit: Downgrading isn't needed if you just want to start flashing. I just wanted to point out what happens if you run a RUU that is older than your actual firmware.
Edit2: Nevertheless here is a chronological list of the roms I liked and used longer than a week on this phone: Viper 2.2 (hboot 2.15), MaxximusHD (hboot 2.16), Viper 3.2.1 (hboot 2.16).