Database Info

HTC Unlock Bootloader Tool Advice Needed

I'm currently at this moment in time:
*** LOCKED ***
Pyramid PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011,12:14:25
CID - 11111111
I want to unlock my bootloader via HTCDev as i like knowing i have access to Fastboot commands if needed, but what i'm wondering, before i do this, is will it send me back to Stock CID and S-Off, or will everything be left as it is whilst just unlocking my bootloader?
Sorry if this has been discussed before, but i've had a look about and not come accross my answer.
Thanks!

It is unlocked, its just saiz locked. A common problem

Brownie2k said:
I'm currently at this moment in time:
*** LOCKED ***
Pyramid PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011,12:14:25
CID - 11111111
I want to unlock my bootloader via HTCDev as i like knowing i have access to Fastboot commands if needed, but what i'm wondering, before i do this, is will it send me back to Stock CID and S-Off, or will everything be left as it is whilst just unlocking my bootloader?
Sorry if this has been discussed before, but i've had a look about and not come accross my answer.
Thanks!
Click to expand...
Click to collapse
Hi,
It will unlock everything for you.
But HTC will then have a record of what you have done,and this will give you warranty problems,should they ever arise.

Thanks for the help guys!
Much appriciated. I've gone as far as getting my unlock code sent to e-mail, but i've not actually flashed it yet as i was rather unsure.

big_sw2000 said:
It is unlocked, its just saiz locked. A common problem
Click to expand...
Click to collapse
Hi,
It's locked to advanced fastboot,like installing radio.
Basic fastboot like get cid is still available.

Malybru, thats pretty much why i'd want it unlocked - I'm so used to flashing radio etc via Fastboot. I know you can do it via HBoot with PG58IMG, but i've been doing it via Fastboot with my Streak, Desire HD etc and just find it easier doing it like that.

Brownie2k said:
Malybru, thats pretty much why i'd want it unlocked - I'm so used to flashing radio etc via Fastboot. I know you can do it via HBoot with PG58IMG, but i've been doing it via Fastboot with my Streak, Desire HD etc and just find it easier doing it like that.
Click to expand...
Click to collapse
Hi,
I know what you are saying.
But you will invalidate your warranty by doing anything from HTCDEV...
EDIT:
You can always return to 1.17 HERE

this what throws me off alot, unlocking the Bootloader gives us fastboot commands, which i dont want to lose, once you have done the Revolutionary you get s-off which takes security off to flash radio etc, once we update the hboot, it says locked but its truly not, and it still says s-off so once we do the unlock from htcdev we still have s-off so fastbooting flash radio should still work since that security is still off
i searched and asked there is no real answer as everyone jus shrugs and says use the PD58IMG to do things then the thread dies or OP says ok that will be fine
and it will not fully void your warranty if its any type hardware issue, it only voids software side, as say you did a bad flash and bricked it, if they recovery it and see you are unlocked then yes its voided, but if the digitizer not responsive, power button stuck, backlight died, whatever that is still coverd

I know i could return to 1.17, but would that mess up the fact i'm running RCMix ICE 4.0.3? I'm no desperate for the Fastboot commands, but just knowing i have access to them is a weight off my mind.
I've never needed to use my HTC warranty, but loosing access to it is putting me off a little. I think i'll lay off unlocking for a while.

malybru said:
Hi,
It's locked to advanced fastboot,like installing radio.
Basic fastboot like get cid is still available.
Click to expand...
Click to collapse
Oh dear, locked does not mean only basic fastboot. The hboot version determines the basic fastboot. 1.17 has advanced fastboot but none others do
Sent from my HTC Sensation XE with Beats Audio Z715e using xda premium

If you've gone as far as getting the unlock code emailed across then go for it.
I unlocked mine with HTCDev first, now i have hboot 1.23 unlocked and s-off..

It's not going to clear my S-Off or Super CID i take it then?
Thats the only main reason i've been holdinf off doing it, the warranty is a downside, but it's not a huge thing. I bought the phone second hand, so i've no idea who it was first registered to anyway.

I can't answer that one i'm afraid as I did it the other way around, HTC first, then revolutionary.
TBH i'm not sure what the difference is between having an unlocked bootloader and S-Off, or whether they are one and the same. When I did the HTC unlock it said it had been successful but still said S-Off in HBoot so i used the revolutionary method as a follow up.
In retrospect I think the HTC unlock did work, at least in part, because i've flashed the most recent ruu (complete phone image direct from HTC) and have both 'unlocked' at the top and 's-off' showing in hboot. most if not all users who have not done the HTC unlock end up with a 'locked' 's-off' combination.
this doesn't really help with your dilemma unfortunately but i'm sure somone with a definitive answer will be along...

I just went ahead and did it... when the screen appeared asking if i wanted to unlock, i vol upped to Yes and pressed Power. Nothing happened, tried again, nothing happened. Pressed Power on NO my phone restarted.
Went back into Hboot, now says *** Unlocked ***, Ship S-OFF RL, and Supercid says 11111111, so all went well it seems, Only odd thing is, my rom seemed to factory reset, and the RCMix ICE splash screen has changed to the stock Android Spash Screen. All seems ok though, still rooted, etc?

Sounds promising. It's a bit of a steep learning curve at first for sure and not all of the guides and info are in plain english. Still, all's well that ends well.

All seems fine. Reading on HTCDev.com, it does factory reset your Rom and Settings, so i decided to just reflash RCMix Ice and all is well and good now.
*** UNLOCKED ***
Pyramid PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011,12:14:25
Fastboot getvar cid shows cid - 11111111
All is good now. I agree that sometimes the guides are a little confusing, but it's the after affects that bother me just as much as what could go wrong. I'd hate to have unlocked and had everything set back to default

Put europe stock rom

Hello everybody, i've a big question for you I got an HTC One S with cid TIM__041, still locked. The installed ROM is the stock customized by my operator TIM, that's crappy without any updates, and i want to put the europe stock rom changing the cid to HTC__001 if it's needed. But i don't want to void my warranty. The device is OK, it has no problems.
How can I resolve this? Sorry for my bad english, but i'm an young italian
If you need bootloader information, here is it:
*** LOCKED ***
VLE PVT SHIP S-ON RL
HBOOT-1.13.0000
RADIO-0.16.31501S.17_2
OpenDSP-v25.1.0.32.0405
eMMC-boot
Apr 20 2012,15:14:18
Click to expand...
Click to collapse

no one?

Sevenarth said:
no one?
Click to expand...
Click to collapse
That was only 2½ hours later, in which the USA is mostly asleep. Patience young grasshopper ..ehmm.. I mean Italian.
EDIT: I missed the AM/PM. It was 14.5 hrs like frdd correctly corrected in the post below this one. Sorry for that.
I'm not 200% sure but I don't think you can change your CID without unlocking your bootloader. Unlocking your bootloader will not completely void your warranty. It will still cover unrelated defects. Also, you can always re-lock and go back to stock afterwards, but only if you have a RUU for your phone that accepts your new HBOOT (that comes with the EU RUU).
If the 'problem' is that you want to tinker with your device but not take responsibility, then there is no solution.
-Jobo

Try 14.5 hours but yeah jobo is correct you need htcdev unlock to root and change cid

So, if I unlock the bootloader, the warranty for hardware problems will not voided? I need only to get the european stock rom, what's the best way to get it? However, i don't think putting european stock rom will void the warranty :/
Thanks for answering my topic But when I maked the topic, in USA was day. xD

Me too, though I am on T-MOB005 CID. And I don't want to exactly root my phone. So until we get S-OFF, there is no way. Just have to wait and be patient, like me. (I'm still on 1.77 and 2.21 has already been released)

usaff22 said:
Me too, though I am on T-MOB005 CID. And I don't want to exactly root my phone. So until we get S-OFF, there is no way. Just have to wait and be patient, like me. (I'm still on 1.77 and 2.21 has already been released)
Click to expand...
Click to collapse
me too, i'm at 1.78, and i still didn't get 2.21 update i need it for wifi problems.

So, are there no other way?

You can try to just run the 2.21.401 RUU but probably won't work.
Or you can wait for TIM to release the OTA if you're only after the new radio, your branding will still be there.
You need root to change cid, and you need htcdev unlock to root. No other way yet.

Hm..are there some news about s-off?

s
I hope it's ok to post other sites like but there is a nice tutorial here that have links to xda forum!
hwupgrade.i t/forum/showpost.php?p=37896138&postcount=320

Sevenarth said:
me too, i'm at 1.78, and i still didn't get 2.21 update i need it for wifi problems.
Click to expand...
Click to collapse
I need it to fix camera focus issues. The camera won't focus on something close-up.

usaff22 said:
I need it to fix camera focus issues. The camera won't focus on something close-up.
Click to expand...
Click to collapse
Same here!! Can you please help me here? http://forum.xda-developers.com/showthread.php?t=1813535

I decided, and now I got 2.21.401.10 :laugh:
I follow this steps: (thanks addsfsds)
1. Unlock, install recovery mod, root --> HOW-TO
2. Changed CID to generic (HTC__001) --> HOW-TO
3. Relocked bootloader (It's important!) --> Command: "fastboot oem lock"
4. Installed 2.21 HTC Europe RUU (includes stock recovery + stock rom) --> DOWNLOAD
5. I'm free!

You guys are saying you don't want to change your CID until S-Off is out because you don't want to unlock bootloader... Even if S-Off is out, you still have to unlock your bootloader to change CID *facepalm*

So I needed the best choice, because I need europe stock rom now.

ShensMobile said:
You guys are saying you don't want to change your CID until S-Off is out because you don't want to unlock bootloader... Even if S-Off is out, you still have to unlock your bootloader to change CID *facepalm*
Click to expand...
Click to collapse
Don't facepalm without knowing. We don't want to unlock the bootloader now because once we get S-OFF, we can S-ON back again with no traces of being S-OFF'ed. However, with HTCDev, it says ***RELOCKED*** which is a clear indication that the device has had its bootloader unlocked before. Some of use don't like to void our warranties, which is why we're waiting for S-OFF.

Do I need a new mobile?

Do I need a new mobile? A question that I often imagine in the last days... What's the situation?
Here are the base informations of my HTC One S:
Original CID: O2___102
Actual CID: 11111111
Boootloader informations:
VLE PVT SHIP S-ON RL
HBOOT-2.13.0000
RADIO-1.11.50.05.28
OpenDSP-v31.1.0.45.0815
eMMC-boot
Nov 20 2012, 15, 15:44:01:-1
The story
What happens. Because of the license mess with CyanogenMod I've tried different ROM's but all in all there where always a reason to change the ROM. After all I want to give Carbon a try but for this you have to upgrade the firmware and so the mess starts.
In fact o2 Germany is not able to deliver a proper RUU I've changed the CID to SuperCID (11111111) and tried to install the RUU_Ville_U_JB_45_S_HTC_Europe_3.16.401.8_Radio_1.11.50.05.28_10.27.50.08L_release_301814_signed_2_4. This and all my other installations of different RUU's breaks with a signature error. Next step was to change the CID to HTC__102 but this didn't help anything.
Now I was thinking to go back to the root and install the first custom ROM I've used. So I want to give ViperROM a try. With this it was not able to get the WiFi up and running. Next step was to give TrickDroid 10 and ZenROM a chance. There was no problem with the installation and both of them where running. The problems here are that both of them are far away from a daily driver.
Today I saw that there are again official CyanogenMod nightlies and so I've thought to install the base ROM of so many custom ROM's. This installation breaks with the error message: "failed : getprop("ro.bootloader") == 2.15.000" So It seems that the newest bootloader is a basic requirement. The problem is now that I'm unable to get the newest hboot because of the RUU signature problem.
I don't know what to do anymore. RUU update does not working. S-OFF does not working. The firmware upgrade is not working. Do I have to use the One S as a paperweight?
So .. I'm really grateful and happy about every hint, every tip or solution.
Thanks a lot
Christian

Why is S-OFF not working and why did you changed your CID back to stock? You have to get S-OFF and SuperCID so follow this guide. Report back at which step you fail

Uwe303 said:
Why is S-OFF not working and why did you changed your CID back to stock? You have to get S-OFF and SuperCID so follow this guide. Report back at which step you fail
Click to expand...
Click to collapse
Good morning,
sorry for my late response. I was so frustrated that I went off yesterday evening.
I've tried different things with the CID:
changed the O2___102 to 11111111
changed the 11111111 to HTC__102
rollback to 11111111
The reason was that I had found the RUU instructions which stated that there could be potential problems with RUU installations and SuperCID.
Based on this thread the S-Off always stops at step 5. I get an error message that says: "FAILED (remote: 99 unknown fail)". I've already tried the different things. Switch off the phone, switch off the computer, useing the original HTC USB cable and so on. Nothing worked here.
Thanks a lot
Christian

Try updating the HTC drivers on your PC then try again. There's a thread somewhere around the One S forums.

After the soff, supercid is not needed anymore.
Have you tried o2 ruus from a different country?
Btw is the ruu erroring because of your MID? Whats yours? Pj4010000?
Sometimes if a ruu errors, directly retrying sometimes works.
Verstuurd van mijn HTC One S met Tapatalk

YES! It's again up and running
After some days of troubleshooting my One S ist up and running again
First was the tip of djsubtronic. I've checked the drivers on my PC. But I've already installed the latest one. Then I've made a clean, fresh new installation on my notebook. But nothing changed.
Then I've tried some other RUU's. But there where always the same error. So... after all I was already looking for a new mobile device and then I've made ​​a final attempt.
Cleaned storage from bootloader
Reset from bootloader
Installed TWRP recovery (2.5.0.0)
Format the sdcard from Windows
Nothing left on the sdcard
System reset from TWRP
System wipe from TWRP
Followed step by step and extreme exactly the instructions of the firmware update thread
The second try to manual update the hboot then was succsessful
After that I was able to install the latest CyanogenMod nightly
Thanks a lot for every tip. They took me to re-read everything again and then start again from scratch. After all I'm already S-On. I'm happy that my phone is running again, I just do not quite trust myself to tackle the topic...
Thanks again...
Christian

Nice to hear you have your phone up and running again.
I want to ask something.
I too, don't have JB RUU for my carrier of the device.
So will S-off and subsequently changing CID to something which has an RUU help? Will that RUU work?
My basic purpose is to go fully stock.
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Nice to hear you have your phone up and running again.
I want to ask something.
I too, don't have JB RUU for my carrier of the device.
So will S-off and subsequently changing CID to something which has an RUU help? Will that RUU work?
My basic purpose is to go fully stock.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Hi, if I understand this correct than yes. If you change the CID to a "non branded" CID. (SuperCID - 111111 or HTC - HTC__102) you should be able to install other RUU's for your device. I don't know why this didn't work for me but for normal this should work.
Christian

chmarx said:
Hi, if I understand this correct than yes. If you change the CID to a "non branded" CID. (SuperCID - 111111 or HTC - HTC__102) you should be able to install other RUU's for your device. I don't know why this didn't work for me but for normal this should work.
Christian
Click to expand...
Click to collapse
From what i have read and understood, yours must be a problem of MID. This is another requirement in addition to CID.
Sent from my Nexus 7 using Tapatalk HD

Htc one x help scared croatian :(

Hello guys
Sorry for my bad english but il try to be precise as i can. I bought my htc on ebay it says new and it feels new. But after i read may treads here it seems its not new . I have problems with automatic software update it freezes on 20% then it reboots after few minutes, if i regard this problem the phone works fine. But im fustrated i want new software . Now i got in boot loader in this is what it says:
++++locked+++++ - in one tread i read this should be relocked
evita pvt ship s-off rl - i belive this is s-off i need your confirmation
cid - 11111111 - i dont understand fully this yet but its a good thing i belive
h-boot 1.09.0000 - dont understand what this means
RADIO - 0.16a.32.09.17_2 - i belive this is software for my phones antena
open dsp - v25-1-0-32-0405 - dont know if this is imortant
emmc -boot
Apr 2 2012, 21:08:24 - is this last known software update i manufacturing date
Know i need you help to explain this thing to me and if its safe and what do i have to do to install new software. Which software whould you
recommend and maybe can i install viper xl
Thanks

The phone definitely isn't new. You have SuperCID (11111111) and s-off which means it has been unlocked at some point. But the good news is you can easily unlock the bootloader at htcdev, then install a custom recovery, and then install Viper if you wish.
Sent from my Evita

Thanks for the reply, now i never unlocked bootloader can you give me some advice on the safest way to do that and where can i see when bootloader is unlocked, sorry for dumb questions but if i dont ask ill never learn

Can somebody send me some links where can i find instructions on how to unlock bootloader, make recovery image and then how to install viper xl rom

Is your phone an at&t model? If it is it'll have the at&t logo above the screen, otherwise it'll just have the HTC logo.
Sent from my Evita

Itd at&t phone
Sent from my HTC One XL using xda app-developers app

You already have SuperCID so you can go to htcdev and unlock your bootloader.
Sent from my Evita

timmaaa said:
You already have SuperCID so you can go to htcdev and unlock your bootloader.
Click to expand...
Click to collapse
The phone is s-off, does the OP even need to unlock the bootloader to install TWRP, flash ROM, etc.?
You typically won't receive OTAs for AT&T phones outside of North America. So that is probably why the update is failing.

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