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.
I know there are several threads like this one but I prefer not to write another RUU request while you're answering to another user
So, I got a HTC One S S3 yesterday... I began to unlock it because I wanted to change its CID. I found that in the S3 version the CID can't be changed (still) when I had already installed the TWRP Recovery.
Now I'd like to go back to stock, but there is not a RUU compatible with my device: It has VODAP102 as CID, but the RUU for Vodafone AT here doesn't work. I found the kernel source for the same software version I have in htcdev.com, my question is: is it possible to build a RUU or at least a boot.img from it?
The sources can be found in htcdev /devcenter/downloads (sorry but being new I can't post direct links!), HTC One S as Device, Vodafone as Carrier and UK -
1.11.161.133 as software version. Actually I am in Italy, but the software and kernel version are exactly the same.
Thank you in advance.
Bump to first page and a little addendum:
I've read again all the possibilities I have with this phone, and if I have understood accurately then I'm forced to go back to stock, roms like the ThickDroid seem to require a non-branded CID, but that's the point... it is the CID that's compelling me to maintain this original Vodafone software, otherwise I would have already installed the HTC "basic" rom.
Am I missing something?
Thank you again!
Have you tried looking on HTCRUU.COM?
Check your radio id on the bootloader screen then flash the appropriate ROM
mikejasonsmith said:
Have you tried looking on HTCRUU.COM?
Check your radio id on the bootloader screen then flash the appropriate ROM
Click to expand...
Click to collapse
Yes I checked, but they have just unbranded RUUs, here in the forum there's one RUU for Vodafone but the region isn't the same as mine.
I've read that it is possible to flash an OTA update deleting the string that checks the CID - I'll have to take a look about that (moreover, it seems very difficult to find .zip OTA updates for this phone...).
Nevertheless I'd like to find this RUU update too - it is an important option too. So... bump to first page.
Hello everyone.
I am new to this part of the forum for i just received a somewhat non working AT&T HTC ONE XL from a friend.
I presume he did not read much into his issue at the time and messed up this phone one way or the other.
Basically the phone works, just not as a phone.
So i will take my time to explain the whole situation with as much detail as possible.
I am personally familiar with rooting, setting up recovery and installing custom roms on android phones (just not on this model yet).
The phone details in its current state are:
- android version 4.0.4
- htc sense version 4.0
- software number cleanrom 4.5 beta2
- htc extension version htcextension_403_1_ga_20
- kernel 3.0.8-01564-gdc95f45
- baseband 0.16.32.09.01_3_10.79.32.08L
As soon as i received the phone, i contacted at&t to ask for an unlocking code, they gladly oblige.
I insert the new SIM card (non AT&T) and the phone asks me to insert the code. After correctly inserting it, the phone accepts the code and proceeds to reboot. After the reboot i get the phone locked screen again and asks me for the code one more time.
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
So at this point i am open for ideas.
I'm positive the issue is not very hard to solve but i also know that i am missing the original recovery. I can only guess no official updates were installed so the phone was running the original 4.0.4 version.
Meanwhile i will be scouting this forum on how this phone exactly works for i understood that there were two forms of recoveries for it (one full and one partial).
I still don't know the recovery version, if it's good, how to access it (different combinations of volume and power pressing didn't work for me).
Finally your opinion on how to make the phone unlocking code work, as in would i need to go back to official, or would a custom different rom work as a solution.
Wish you guys a good day and awaiting your feedback.
Cheers.
Need more info. Boot into bootloader by holding down both the volume down rocker and the power button. After the power button is held for a few seconds, you should see the capacitive buttons flash a few times, and the phone will reboot. Let go of the power button, but DO NOT let go of the volume down rocker until the while hboot screen comes up. When you see the hboot screen, tell us what it says.
In particular, we need to know if it says s-off or s-on, if it says CID 11111111, and hboot version. Also, if it says LOCKED, UNLOCKED, or RELOCKED.
Official RUU will not run if the bootloader is UNLOCKED (needs to be RELOCKED or LOCKED). But be aware, if the phone is superCID and s-on, running a Jellybean RUU or OTA will brick the phone. Which is one of the reasons we need the bootloader info.
RUU does not need to have stock recovery to run, only OTA does. My guess is your bootloader is unlocked, or its the wrong RUU. Any error message when the RUU fails (if so, what does it say)?
Hi, thank you for your quick reply.
I'm going to write down all that is written in the recovery for i still don't understand what locked or unlocked means, s-on or s-off.
anyway, here goes:
tampered
unlocked
evita pvt ship s-on rl
hboot-1.09.0000
radio-0.16.32.09.01_3
opendsp-v25.1.0.32.0405
emmc-boot
i can't find anything related to cid and i'm still not used to this recovery just yet. wouldn't want to press anything just yet.
i hope i gave enough info and i guess it doesn't look too good just yet.
thank you again for your help.
you should remind me to reduce the use of "just yet".
i'm doing some more reading about superCID and S-on or S-off.
I understand there's a utility from this thread that could determine the supercid status.
http://forum.xda-developers.com/showthread.php?t=1672284
again i'd like to point out i have no clue what has been done to this phone so i am trying to handle it with as much care as possible in order not to brick it.
in case superCID is 1111111 and naturally i don't have the original CID, where would that leave me?
As i am understanding slowly how this phone works, if the previous user managed to install a custom rom and a custom recovery on it, would only make sense to assume the superCID has been modified? (i'll be running the tool shortly unless someone jumps and says NOOOOOOOOO don't do it!!!)
I also noticed the teamwin recovery installed is 2.1.8.1
next is understanding what s-on and s-off are all about.
i have a feeling my chances of reverting to stock firmware are slimming. this is quite a complicated phone, nice challenge.
i'm going to point out again what my main problem is: i can't unlock the sim using the code provided by at&t since as soon as the phone reboots it asks me again. so i don't mind whichever route to take, whether custom or stock, as long as i can unlock the sim the simple way.
cheers.
srasiroslayer said:
At this point i start searching online for the official firmware from htc for this specific model and find the 4.2.2 version and proceed to install it according to their requirements and steps (in manual mode from a desktop pc since the rom installed doesn't have the update feature).
The process gets locked at a point and cannot proceed further.
Phone boots normally again and i decide to do a factory reset. This i when i notice a teamwin custom recovery was installed which is what is blocking the official rom installation.
Click to expand...
Click to collapse
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
srasiroslayer said:
i have a feeling my chances of reverting to stock firmware are slimming.
Click to expand...
Click to collapse
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
redpoint73 said:
This is not correct (the text I've bold faced above). OTA requires stock recovery, but RUU does not.
What stopped the RUU from working, is that you bootloader is unlocked (as indicated by the "unlocked" text in hboot). But in your case, you are lucky, since if you were trying to run the 3.18 Jellybean RUU, if it had gotten past the bootloader lock check, it would have bricked the phone (known bug) if you have SuperCID (which is pretty likely).
To reiterate: DO NOT try to relock the bootloader and run the 3.18 RUU, as with S-on and SuperCID, this will brick your phone.
If you have a working adb/fastboot environment, you can easily check CID with the command: fastboot getvar all
---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------
That is far form the truth. Getting back to stock is not that hard.
But if you only want to SIM unlock, I'm not sure that going stock will necessarily help you. You are on CleanROM now, which is pretty close to stock, and I don't think there have been many issues getting SIM unlock on CleanROM.
Click to expand...
Click to collapse
Wunderbar,
Thank you again for clarifying things up.
I've been taking this time to read more about this phone on this thread:
- http://forum.xda-developers.com/showthread.php?t=1671237
So i am starting to understand how it works.
i have to admit that i should consider myself lucky for if the phone had a locked bootloader, it would've been bricked.
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Cheers
srasiroslayer said:
Wunderbar,
i've been reading a bit about superCID and i don't have a working linux environment (other than virutal) running right now.
but i'll figure out how to check if it's superCID or not (more likely yes).
Click to expand...
Click to collapse
You don't need a Linux environment to get fastboot/adb working. And you will need them if you want to get s-off or change the CID (which would be the solutions to your problem of running the RUU).
To get fastboot/adb going, I'd suggest you start here: http://forum.xda-developers.com/showthread.php?t=1754018
There are some apps what will read the phone's state including CID. Others here have mentioned the name of one (or more) such app, but I can't recall, and I don't use it. I'm used to using fastboot.
srasiroslayer said:
now that i've figured out one way or the other that the simlock has nothing to do with the firmwares or recovery........... what could cause it?
again i just want it to work and then i'll take the time to play with the custom roms.
I have the correct unlocking code from AT&T since it wouldn't have accepted it to reboot the phone if it was wrong.
so what could be messing it up?
Click to expand...
Click to collapse
Not sure. Going back to stock might help. Its all I can think of. But don't be disappointed if it still doesn't work.
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
My question is, shouldn't i have the original CID number?
and another off topic point, i have no clue what s-on or s-off are.
i'll get into that reading mode again in a bit.
Thank you again, i feel i'm on the right track now and confident.
Cheers
P.S.: do you need me to post the "fastboot getvar all" results? or only thing missing to be sure of was the CID?
Hang on, you're s-on and SuperCID, don't run the RUU or you'll brick your phone. You need to do some reading and research all this before you try these things.
Sent from my Evita
Guys I am Vivek Rajput, from India. I have AT&T HTC oneX. Anything related to internet is not working except whatsapp. Every app is showing network error msg. Showing some data here which i got after reading here. Assume me complete novice about software/cellphones.
***LOCKED***
EVITA PVT SHIP S-ON RL
HBOOT-1.14.0002
RADIO-0.19as.320911_2
OpenDSP-v29.1.0.45.0622
eMMC-boot
Jun 11 2012,14:36:28
Click to expand...
Click to collapse
Have you checked your APNs?
Sent from my Evita
srasiroslayer said:
Alright,
So i figured out my CIDnum is 1111111111 using fastboot.
I understand there's a tool that can revert that.
I should also switch to s-off next.
Then at the end lock the bootloader using the adb commands.
Am i on the right track?
At this point i'll try running the RUU and cross my fingers.
Click to expand...
Click to collapse
If you are going to s-off, you DO NOT want to change the CID. SuperCID (11111111) is needed to s-off.
As mentioned, make sure you s-off before RUU, or you will brick.
Once you are s-off, it shouldn't matter whether you lock the bootloader or not. S-off means all security checks are bypassed, including the check for bootloader lock.
srasiroslayer said:
and another off topic point, i have no clue what s-on or s-off are.
Click to expand...
Click to collapse
s-off, as mentioned above means all security checks are off. There are good and bad points to this.
The good, is that you will be safe of the SuperCID + RUU brick condition. Custom ROMs will also be easier to flash, if you are interested in doing that (do not need to flash boot.img separately).
The bad of s-off, is that because all security checks are off, there are no safety checks to prevent you from flashing the wrong things. You have to be very careful you don't flash something that is not intended for the device, as it may brick the phone.
Are you are okay with that, then proceed with s-off. If not, the alternate solution is to change the CID back to the proper AT&T CID (cws__001). This will also prevent the SuperCID + RUU brick condition. But may make the phone harder to s-off in the future, if you later choose that route.
It looks like then that the s-off route is the one to take, since i will definitely in the future be interested in flashing custom roms.
And it looks relatively easy as per:
http://forum.xda-developers.com/showthread.php?t=2155071
After doing some reading, it also looks safe to achieve s-off on custom roms such as my case.
I'm still reading if s-off will work on my bootloader version or if there are any specific versions to run it at. (so far no mention so good)
I'm guessing i will run s-off today and if everything works out as it should will post my results here.
Only then will i proceed to run the RUU which i downloaded from htc for the at&t model specifically (no chance i could go wrong with that).
Thank you for all the help, i honestly don't think i would've found my way around easily without guidance.
Cheers
Yes, the s-off method is easy, and it should work on any hboot version.
Good luck.
Could just having S-off fix my sim locked issue?
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
srasiroslayer said:
Could just having S-off fix my sim locked issue?
Click to expand...
Click to collapse
I doubt it. SIM lock and s-off are not related, to my knowledge.
srasiroslayer said:
In any case new questions arise in my head such as since my model number is PJ8310000 and that with s-off i will be installing PJ8312000-OneX.zip, will that affect running the RUU later on?
Click to expand...
Click to collapse
Once you are s-off, all security and safety checks are off by definition. As long as you are running an RUU meant for EVITA, you will be safe, and it should run properly.
Looks like i got the 99 error thing.
at first i had the error 92 and all was working good but after the final reboot didn't get s-off
the second try i'm getting error 99.
I'm going to read more into it.
I'm still s-on so.......
So here are the current updates.
As i mentioned in the previous post, running it the first time resulted in error 92 which is normal, followed instructions and didn't get s-off.
second time i had error 99. still no s-off.
I turn off the device and power it back on, run the script all over again with a real good attention and precision (i usually don't f*ck things up).
This time i get the error 92 again and still no success at the end. (did this over 4 times now and no s-off).
would i be logical for me to assume that once the rom is booted it's messed up somewhere? hence the last part of the script not working and also hence sim unlock not working?
what's a good custom rom that would i could install using recovery and not brick my phone?
maybe just installing one would solve all my issues.
Cheers
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
timmaaa said:
What ROM are you attempting s-off on?
PS. Asking for a suggested/best/favourite ROM isn't allowed here.
Sent from my Evita
Click to expand...
Click to collapse
Hi,
I'm trying it on CleanROM 4.5 beta2.
And by best rom in my case was asking one that would be compatible with my situation, as in hboot 1.0.9, teamwin 2.1.8.1 recovery, supercid, unlocked, s-on.
Cheers.
I have an AT&T HOX running the original stock ICS 4.0.2 The phone is rooted, bootloader unlocked and has Supercid.
I would like to install one of the new Cyanogenmod ROMs that require HBoot version to be 2.14 or newer, but I'm having problems. I can't use an RUU to upgrade to 4.2.2 or whatever, because I'm supercid and will probably brick the phone. Facepalm/Rumrunner/Firewater/moonshine etc, S-Off tools do not work with this particular kernel for whatever reason, and I just get the "Please install an 'unsecure kernel" advice at the end of the attempt.
So, basically, I can't get S-Off because none of the tools work with my OS version, and I can't update my OS via the normal channels because of having supercid, and I can't upgrade my firmware because I'm not S-Off. Kind of a catch 22-22-22 situation.
I'm not even sure what question to ask at this point, so I'm open to any advice you guys are willing to offer in regard to upgrading to HBoot 2.14 to meet the requirements to install CM 11 on my phone. My current HBoot version is 1.14
**Edit** Current firmware - 2.20
Thanks in advance.
Maybe a solution
Well, I finally found a thread by someone with a similar situation. It looks like the procedures outlined by Heisenberg in his replies did the trick for that particular person, so I'm gonna give that a try I guess. I'm not sure how I missed that thread after all the searching I've done before now, but for anyone who might be interested:
http://forum.xda-developers.com/showthread.php?t=2218990
Thanks
Try to flash Kickdroid 5.0 as outlined in the other thread, then you should be able to get s-off.
Would somebody please advise me about the pro's and cons of changing my HBOOT version.
I can successfully root my phone via The Revolutionary method after downgrading using an earlier RUU etc.
What I am not clear about is whether I then need to flash an ENG HBOOT after this process .... which version.... why I should do this ?
If I have the "wrong" HBOOT installed will that prevent certain ROMs from running correctly ?
Do I need a specific "level" of HBOOT for a GB based ROM to run and another for an ICS based ROM
Choosing your HBOOT Version
I don't know absolutely everything about this, but since you've waited over a month with no replies, I'll tell you what I know. It should be enough to answer your question, if you're looking for something more advanced then you may need to keep looking!
The original HBOOT version is 0.98.00000, this is the HBOOT version that you need if you want to S-OFF your phone as the later version, 2.000.00002, blocks the vulnerability that allows the Revolutionary exploit to work. S-OFF unlocks root level access to the phone permanently, allowing you to flash new ROMs directly from the SD card without having to use ADB and USB Debugging to flash the boot image every time.
Basically, if you want S-OFF you may need to downgrade your HBOOT to 0.98.0000 if that's not the version you already have.
The phone originally shipped with Android Gingerbread 2.3, this can be upgraded to a certain point, beyond which, the newer version of HBOOT is required. I don't know which version is the crossover point but I'm sure a quick search of the forums will provide the answer, I'll leave that up to you (I think the main reason you haven't had any replies is that ALL this info is already available in the various guides in the forum, so people think you're being lazy not looking for it!).
So....
Unless you're trying to do something out of the ordinary, the most common approach is a follows;
Unlock bootloader on HTCDev.
Downgrade to HBOOT 0.98.00000 (f necessary).
Use Revolutionary to gain S-OFF.
Upgrade to HBOOT 2.000.00002 (not necessary for Android 2.3 but later versions require this)
Download and flash new ROMs directly from the SD card using custom recovery, such as TWRP or Clockworkmod.
I hope this helps, I do understand that it's not always easy piecing things together from multiple forum threads to learn about something new, but ALL the info you needed IS already available on here.
There are some excellent guides and tutorials here on XDA Developers, both official and unofficial. I would say if you don't already have a bit of knowledge then stick to the official guides and you can't go wrong.
Hint: Try searching the forum for [Guide]