Database Info

(Q) Change CID

Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?

smash_07 said:
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
Click to expand...
Click to collapse
Hi,
This is a SENSATION forum.

malybru said:
Hi,
This is a SENSATION forum.
Click to expand...
Click to collapse
Yes I noticed it i already asked the moderation if they could move the thread to the Desire S section.

I need to find this out to? I dont want to root my Desire S, I just want to changde CID so i could put unbranded software to it...?

You can just create a GoldCard and make it work, without root or S-Off.
Earlier today I created a GoldCard and upgraded my DS using the European RUU and I'm S-ON & Unrooted.
See here: http://forum.xda-developers.com/showthread.php?p=19171606

doghous said:
You can just create a GoldCard and make it work, without root or S-Off.
Earlier today I created a GoldCard and upgraded my DS using the European RUU and I'm S-ON & Unrooted.
See here: http://forum.xda-developers.com/showthread.php?p=19171606
Click to expand...
Click to collapse
Yes I know that works I have a Goldcard. The thing here is that I would like the phone to be completely unbranded without the need os special cards so in case i want to sell it or send it to warranty it won't be noticed that i changed something there. So if there is a way to re write de CID it would be good.

Well i actually successfully installed the unbranded european ROM 1.28.401.1 using the gold card. But now i can't receive OTA updates. Is there a way to get it to work?

Why don't you run the European RUU 2.10 version (RUU_Saga_S_HTC_Europe_2.10.401.5_Radio_20.4801.30. 0822U_3822.10.08.04_M_release_219480_signed) from the following link:
http://forum.xda-developers.com/showthread.php?t=1002506
That's what I did

smash_07 said:
Hi everyone,
I got a branded Desire S (Vodafone Portugal) and I would like to change its CID in order to turn it unbranded. I have tried the fast boot method of "fastboot oem writecid HTC__001" and it gives me back an error as "COMMAND ERROR!!!" with no real specification of what error it is.
Is there a way that i can change the CID?
Click to expand...
Click to collapse
Just to answer your question:
(I may need to be corrected on this one)
Based on my observation and experimentation. The CID that you are trying to change, or the CID that the RUU is checking is actually on the build.prop on your phone.
Code:
ro.aa.maincid
But there are two checks that I've observed. Even though you changed the maincid, the corresponding cwkey should be changed accordingly.
cwkey created on your phone corresponds on what is on the build.prop and I believe is also being checked by RUUs.
And maybe just to be on the safe side, RUUs do check what is on your build.prop. If they are not what your RUU wants, it will not push through. Hence, you need a GoldCard.
I myself don't exactly, by codes, know how the GoldCard bypasses the checks. All I do know, is that it works.

Skanob said:
Just to answer your question:
(I may need to be corrected on this one)
Based on my observation and experimentation. The CID that you are trying to change, or the CID that the RUU is checking is actually on the build.prop on your phone.
Code:
ro.aa.maincid
But there are two checks that I've observed. Even though you changed the maincid, the corresponding cwkey should be changed accordingly.
cwkey created on your phone corresponds on what is on the build.prop and I believe is also being checked by RUUs.
And maybe just to be on the safe side, RUUs do check what is on your build.prop. If they are not what your RUU wants, it will not push through. Hence, you need a GoldCard.
I myself don't exactly, by codes, know how the GoldCard bypasses the checks. All I do know, is that it works.
Click to expand...
Click to collapse
So what that means is the phone has to stay branded? There is no way that we can fully unbrand the phone by changing the CID?
And after we use the Goldcard what happens to the CID of the phone?

smash_07 said:
So what that means is the phone has to stay branded? There is no way that we can fully unbrand the phone by changing the CID?
And after we use the Goldcard what happens to the CID of the phone?
Click to expand...
Click to collapse
The goldcard does not alter the CID. It just tells the bootloader to ignore the CID check when running a RUU.
One way to alter the CID is to XTC clip the phone.

Well i ended up doing what you all suggested and flashed the RUU with the 2.10 european rom with the goldcard in it.
But something went wrong and my Desire S is in a strange situation. For some reason the Goldcard did not work like the first time and gave me a CID error. But it flashed the hboot 2.00.0002 but retained the 1.28 rom i had installed on it. I have used the HTCDev method to unlock the bootloader but everytime i try to flash the 1.28 RUU again (to flash the old hboot again) it gives me an "unknown error" that is actually a security error.
Is there a way to get the old hboot back?

smash_07 said:
Well i ended up doing what you all suggested and flashed the RUU with the 2.10 european rom with the goldcard in it.
But something went wrong and my Desire S is in a strange situation. For some reason the Goldcard did not work like the first time and gave me a CID error. But it flashed the hboot 2.00.0002 but retained the 1.28 rom i had installed on it. I have used the HTCDev method to unlock the bootloader but everytime i try to flash the 1.28 RUU again (to flash the old hboot again) it gives me an "unknown error" that is actually a security error.
Is there a way to get the old hboot back?
Click to expand...
Click to collapse
My reply to this post of yours is already a hint.
Use search PLEASE.

[Q] S-Off not possible because of "Error 131" - doesn't matter which RUU

Hi guys,
I am new here, so maybe I missed something.
Anyway, I followed the tutorial step-by-step to unlock my HTC Desire S which I got today (so it has a 2.x bootloader) like stated here:
http://forum.xda-developers.com/showthread.php?t=1443636
But I can't seem to install any RUU cause of "Error 131", as told in the tutorial, I must use the RUU for my specific region.
So, my Region is Germany and my phone is from o2.
So first I used
RUU_Saga_HTC_Europe_1.28.401.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_177977_signed.exe
Click to expand...
Click to collapse
because Germany is in Europe. And the only GER RUU is from "TMO" which may mean "T-Mobile" I guess. But it didn't work.
Next I thought "**** that ****" and I tried to flash (after repeating all tutorial steps):
RUU_Saga_TMO_DE_1.30.111.1_Radio_20.28b.30.0805U_38.03.02.11_M_release_178580_signed.exe
Click to expand...
Click to collapse
But it still shows up "Error 131"... so now I am depressed. Can anyone tell me what I am doing wrong?
Thank you very much

Samwan said:
Hi guys,
I am new here, so maybe I missed something.
Anyway, I followed the tutorial step-by-step to unlock my HTC Desire S which I got today (so it has a 2.x bootloader) like stated here:
http://forum.xda-developers.com/showthread.php?t=1443636
But I can't seem to install any RUU cause of "Error 131", as told in the tutorial, I must use the RUU for my specific region.
So, my Region is Germany and my phone is from o2.
So first I used
because Germany is in Europe. And the only GER RUU is from "TMO" which may mean "T-Mobile" I guess. But it didn't work.
Next I thought "**** that ****" and I tried to flash (after repeating all tutorial steps):
But it still shows up "Error 131"... so now I am depressed. Can anyone tell me what I am doing wrong?
Thank you very much
Click to expand...
Click to collapse
Hi there,
You need to flash the RUU that is supported by your phone's version.
Turn the phone into fastboot mode (voldown + power), click fastboot, wait till it shows fastboot usb.
Open console in PC and find the android tools, type:
<androidtool dir>\ fastboot getvar all
It should come up as: INFOversion etc.
What you need to look for is INFOversion-main and INFOcidnum
Go to http://forum.xda-developers.com/showthread.php?t=1002506
and download the RUU that matches!
If you've S-OFF'd the phone with Revolutionary, then RUU will have some problems with overwriting the bootloader, follow this guide to re S-ON.
http://forum.xda-developers.com/showthread.php?t=1187231

anchemis said:
If you've S-OFF'd the phone with Revolutionary, then RUU will have some problems with overwriting the bootloader, follow this guide to re S-ON.
http://forum.xda-developers.com/showthread.php?t=1187231
Click to expand...
Click to collapse
Very helpful reply buddy.
But i don't think the last line applies to him. He said he just got the phone, and it had the v2.xxx hboot to begin with, so he went looking to downgrade. If he had acheived S-off, he wouldn't be asking how to S-off in the first place.
@OP : You should try using a Goldcard when faced with a difficult choice of Region-specific RUUs. Try making one (Use Search function) and then re-running the European RUU. (You may also have to check your Misc_version to ensure compatibility, or you may hit a roadblock again.

Hi,
I just wanted to confirm for further searches / use that what has been stated inside the first answer is fully working.
I got my Desire S downgraded, S-OFFed and was able to flash MIUI, so it's finding it's way to my girlfriend as birthday present soon thank you for helping.

[Q] Help back to S-ON sensation

Hi everybody, i'm new on this forum 'cause i'm french indeed i spend my time on Frandroid.fr !
First of all i would like to say sorry for my bad english i'll use i'm just trying to do my best in order to you can read this message.
So, i'm here because i have a problem with my HTC sensation, he had the problem that he powered off all the time even when i didn't use it. To escape this problem i flashed an ICS ROM with Recovery etc.. Then the problem hasn't been resolved so i decided to send my phone at the warranty, but before i have to put my sensation in S-ON, so i used the RUU VODAFONE and i changed my CID in VODPA203. I've seen that there were 3 steps before put the phone in S-ON, first i must have an Hboot less than 1.18 that i have, second be in official ROM that i have and the last step is have a CID HTC that i have (VODAP203).
The problem i have is that on the bootloader, i haven't got the ***LOCKED*** at the top of the screen (sorry i can't put my photo links yet...)
In other words, i THINK, but i'm not sure that my bootloader is not LOCKED.
So can i do the process in order to put my phone in S-ON without the ***LOCKED*** ? Is it risky to do it without ?
I hope that you'll understand my message because it's probably bad english, and a bit to long but i think that i had to explain my problem to you understand.
Thank you, Sharazed.

Not clear enough but not for the english.
What your bootloader says? **unlocked** or **locked** (I think unlocked).
If you attempt to lock again by HtcDev it will show **re-locked**.
The bootloader is now officially unlockable by htc so I wouldn't worry about it.
Not clear if you went back to s-on already or not.
This guide can be useful (step 5)

That's the problem !
Nothing is written at the top of my bootloader, neither LOCKED nor UNLOCKED, just start with PYRAMID...
I can't show you the screen because i have to post 8 messages before.. Normally there is written LOCKED or UNLOCKED but not on my bootloader, that's why i'm asking you if i can do the process, i'll see your link thank's !
After read your link i can't do it from number 6 (STEP 5) to number 9 cause i'm not sure that's my phone is locked.

You never had nothing on top since you had this phone?
I mean no **locked** and no **unlocked**?
By the way if you were able to flash an ics rom (with new firmware and custom recovery), obviously you are unlocked and s-off

Yes i think that i'm unlocked because before used the RUU i was unlocked but as it's not sure, i'm scared to brick my phone you know.
So i hope that i 'll can send you my pictures then you could compare with other phones, but on the french forum, nobody ever seen that before i can write you what i see on my bootloader:
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.17.0008
RADIO_10.11.9007.15_M
eMMC-boot
May 13 2011, 21:04:57
That's what i see !
Thank's !

Definitely your phone is unlocked.
You couldn't be S-Off, if it was locked.
Hboot is the right one for GB.
You can go through the S-ON procedure without problems.
Just be carefull and follow instructions.
Please hit thanks button if you wish

What do you mean by GB ?

Ginger Bread (android 2.3)

Okay, but i read that i had to be LOCK before go to S-ON so is it dangerous ?

Sharazed said:
Okay, but i read that i had to be LOCK before go to S-ON so is it dangerous ?
Click to expand...
Click to collapse
There is no need to lock again for 2 reasons.
1) Bootloader is officially unlockable by HtcDev. If you lock again it will show **re locked**. Your warranty is void in any case.
Your bootloader has never been locked (according to what you said).

I don't understant because on the french tutorial, it says that i must have my bootloader locked and hboot inferior at 1.18 then if the bootloader is unlocked by revolutionnary (that i had before use the RUU) it's not advisable to back to S-ON.
And you are telling me that i need not to put my bootloader locked to do the process ?
I'm totally lost !
I have to write 8 messages before link my pictures, you'll see my case

Locking bootloader and S-On are 2 different things.
Your situation is uncommon because the sensation is usually shipped **locked** and S-On.
Then, in order to S-Off you need to unlock first.
In your case you are S-Off already without unlocking by HtcDev, so it means that it was shipped unlocked (strange but this is what you say), hence no need to relock in my opinion.

No he wasn't usually shipped UNLOCKED (S-OFF..), but i have unlocked it because my phone is knowing reboot lonely, so i decided to flash Recovery and ICS rom, but with the ROM the bug had persisted.
And now I used the RUU to erase the ICS rom and put my phone in S-ON, but after using the RUU and follow all steps, i see that nothing is written at the top of my bootloader, neither ***LOCKED*** nor ***UNLOCKED*** as before..
So i'm asking you if i can finally put my phone in S-ON without the word LOCKED at the top of my bootloader ?!
Thank's !

Little up !

Nobody know ?

[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.

[Q] AT&T HTC ONE XL custom rom & recovery installed on locked phone

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.