Database Info

[FIX] HtcDev Blocks SuperCID

Just a heads up, HTCDEV unlocking no longer works with supercid. Changing cid to 22222222 does work. Thanks BEAUPS for already confirming that (Hes a beast)
Seeing that the chances of the hox exploits getting updated are pretty slim heres a easy fix to get people unlocked
Easy fix-
Use any existing exploits that changes your cid to supercid. Once done-
From bootloader use the fastboot cmd
fastboot oem writecid 22222222
Then proceed with getting your unlock token as usual using htcdev
The above cmd will only work with supercid. Once you change it to anything other, the command no longer will change cid. You have to do it manually.....
This is just a heads up and a quick workaround for those that need it.

18th.abn said:
Just a heads up. Changing cid to 22222222 works. Thanks BEAUPS for testing/confirming that.
Easy fix-
Use any existing exploits that changes your cid to supercid. Once done-
From bootloader use the fastboot cmd
fastboot oem writecid 22222222
Then proceed with getting your unlock token.
The above cmd will only work with supercid. Once you change it to anything other, the command no longer will change cid. You have to do it manually.....
This is just a heads up and a quick workaround for those that need it.
Click to expand...
Click to collapse
They just started blocking it? I just Unlocked my Bootloader last Sunday with 11111111 just fine

Re: HtcDev wesite Blocking Supercid FIX
Great work
Sent from my SPH-L710 using Tapatalk 2

Seriously?! Why would they do this? Is SuperCID a security risk? I thought I had left this kind of crap behind when I retired my iphone.
This is my first and last HTC phone.
Sent from my Nexus 7 using Tapatalk HD

does this mean updating to jb sense with 22222222 will no longer brick phone like with supercid?

Supercid doesn't cause brick or atleast out of the many ota's I have done it has never caused an issue. Who actually did have issues with supercid and an ota?

twistedddx said:
Supercid doesn't cause brick or atleast out of the many ota's I have done it has never caused an issue. Who actually did have issues with supercid and an ota?
Click to expand...
Click to collapse
I get an issue with SuperCID: I apply an ota from an official RUU to get Jelly Bean, the ota was very well installed but at the end of the process the phone doesn't boot an was locked in QHSUSB_DLOAD and at this time when you're locked in this mod by OTA update with superCID you can't rewrite partitions with the topic "unbricking evita".
My only solution was mobiletechvideos.com who fixed it very well

mik93250 said:
I get an issue with SuperCID: I apply an ota from an official RUU to get Jelly Bean, the ota was very well installed
Click to expand...
Click to collapse
What ruu did you apply? Was the phone modified in any other way than supercid? Eg was the hboot downgraded? Previous unlocked bootloader? Current unlocked bootloader?
What was the full state of the phone prior to accepting ota.
How was the ota applied? Did you simply check for updates and accept then follow prompts. Or installed via fastboot?
I have upgraded 2 hk one xl's with supercid to 3.17 via ota without issue. One was previously hong Kong ruu then wiped and had singtel stock Rom flashed then accepted singtel 3.17 ota. Could not use singtel ruu as Hong Kong ruu was newer and already installed. Hboot downgrade and software version tinkering still did not allow singtel ruu. I could only reinstall honk Kong ruu.
The other via o2 ruu and o2 3.17.
There seems to be some differences in the protections in hboot. Downgrading my phones hboot to 1.09 did not make flashing radio and boot from recovery functional again. It did not let me install older ruu's. My devices, one that has had every mod and flash done to it and the other very very little, both seem super hboot protected now!
The similar theme is both devices have been through all 4 generation of ota's. Following different ota and ruu paths but have now got the same outcome.
Maybe it relates to when supercid was applied even. Both my devices had supercid applied at hboot 1.09.

Damn HTC and ATT! They are bent on making this difficult. My next phone will be Nexus, enough of this crap!

We've had worse patches to overcome on the Evita, atleast its a simple solution for the time being. I do agree tho. I moved on from htc for the time being.
Sent from my SPH-L710 using Tapatalk 2

iElvis said:
Seriously?! Why would they do this? Is SuperCID a security risk? I thought I had left this kind of crap behind when I retired my iphone.
This is my first and last HTC phone.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
done moved over to the nexus 4 myself

Great to know, although I already have mine unlocked.

CheesyNutz said:
done moved over to the nexus 4 myself
Click to expand...
Click to collapse
Can you get Beats Audio or any other sound enhancements on a Rooted Nexus 4 via Custom Rom or other methods?

Viper4713 said:
Can you get Beats Audio or any other sound enhancements on a Rooted Nexus 4 via Custom Rom or other methods?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 7 using Tapatalk HD

Do you miss LTE cheesy? I live in Canada so I understand I can get LTE on nexus 4 but if I couldnt I don't think I could live without it now
Sent from my VENOMized HoxL

CheesyNutz said:
Yes
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the Info, I guess my next phone later on will be a Nexus Phone

area51avenger said:
Do you miss LTE cheesy? I live in Canada so I understand I can get LTE on nexus 4 but if I couldnt I don't think I could live without it now
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
LTE is not in my area so in would have no idea
Sent from my Nexus 7 using Tapatalk HD

I can't believe at&t would be this petty... Or that HTC would go along with it. I'm glad I unlocked my boot loader when I did.
Sent from my Nexus 7 using xda premium

Just tested.
Hong Kong One XL running 3.17.707.1.
Supercid 11111111
Just went through http://htcdev.com unlock process and got an unlock token 100% fine.
Again there is nothing wrong with Supercid, at least not in general. It works with htcdev.com and does not brick phones.
Someone needs to check if it is just AT&T phones that are struggling with supercid or if something else is upsetting things.
It is not supercid on its own, supercid(11111111) works fine!
HTC/AT&T might be actively checking for modified AT&T phones that are getting unlock tokens via root exploits and changing cid.

Non at&t phones don't need supercid, so this only affects at&t phones. All the other carriers phones will unlock with out messing with the cid number.
Sent from my Nexus 7 using xda premium

Brand New HTC One X AT&T build 3.18 -- WANTING ROOT/UNLOCK/S-OFF

Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.

Bubbled said:
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
Click to expand...
Click to collapse
Unfortunately the answers are no and no. JB is decent even on fully stock AT&T, you will just have to look the other way when scrolling through your app tray

I don't think the current root methods allow for the 3.18 build to gain root. Might be in the 2.20 boat all over again until someone can find a definite procedure.

soooooooooooooooooooooo lame. my rezound had viper rez rom and it was based off one x jb but had all the tweaks and stuff so right now its like a major downgrade lol
guess i'll cry and wait for the HTC One to come out later this month, since i only grabbed the one x cause it was literally 11 cents at walmart with a 14 day return and my rezound is acting up and randomly restarting/tanking battery!
sigh
thanks for the info though Groovy

Bubbled said:
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Click to expand...
Click to collapse
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...

lightflier said:
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
Click to expand...
Click to collapse
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2

iElvis said:
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
OK...

I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure

juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Sent from my Nexus 7 using xda premium

panda_mode said:
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Click to expand...
Click to collapse
Damn that's annoying! If that were me I would sell my AT&T phone and with the cash buy an overseas One XL model with 32GB

juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).

redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Sent from my VENOMized HoxL

area51avenger said:
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Click to expand...
Click to collapse
I suppose it doesn't hurt to try. Otherwise, I'd just take the phone back, if root/S-off, etc. is important to the OP. I assume 11 cents is a subsidized price. So no point in using up an upgrade on a phone that can't be modded, if he wants to get the HTC One when its released.
OP may also check to see if the store has any older stock with 2.20 firmware (or any previous firmware version except 3.18). Phones with 3.18 out of the box must be very new, so I wouldn't be surprised if they had some older stock also.

I returned the one x today. will be looking into the t-mobile version of the HTC One which they told me comes out friday the 22nd. being a new phone i know i wont be able to do any mods or anything for a while, but that won't take long with the awesome Devs we have here! All the other models of the One X were sold out, and im guessing that someone realized that the new firmware was Out of Box so picked em all up. only had 2-3 stores with one each so its possible. now all the new stores have the new firmware no big deal, i'd prefer an HTC DNA anyways, but we'll see what the One is all about.

redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.

Techinstein said:
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Click to expand...
Click to collapse
Yes, the CID for AT&T is cws_001 on all of the previous firmware versions, as well. This hasn't changed. cws__001 is blocked on HTCDev.com.

So i have the key for my past bootloader unlock can i use it?
Enviado desde mi HTC One X usando Tapatalk 2

coldrazor said:
So i have the key for my past bootloader unlock can i use it?
Click to expand...
Click to collapse
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.

redpoint73 said:
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
Click to expand...
Click to collapse
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.

exad said:
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
Click to expand...
Click to collapse
Really? Kinda negates part of the purpose of having S-off, doesn't it?

Having trouble rooting (updated to 4.1.1)

Hi, I Just picked up the HTC One X earlier last month and decided that I wouldn't root until I realized that there's certain apps I use that won't run without root (sixaxis controller for example) so after I had already updated to 4.1.1, I figured that I'd enable USB debugging and so that I could receive root access using Hasoon 2000's simple all in one toolkit, however I can't get the xFactor root exploit that changes your CID working..
I'll get prompted to restore first backup, which doesn't work (starts, then ends immediately), it automatically tries a second time, then sends me to the bootloader. I then get prompted to check my CID before I proceed, and it still hasn't changed from my original 'Rogers01" CID to the 1111-sequence of numbers. I have the latest HTC drivers installed for my One X..
Anyone have a clue on what's going on here? Could this be happening because I updated?
Thanks for taking the time to read this.
TL;DR version
I updated to 4.1.1. and I'm trying to root, can't change CID

I don't think you have to change cid with rogers just go to htcdev.com get you unlock token unlock boatloader push a recovery then flash a Rom and boot.I'mg
Sent from my HTC One X using Tapatalk 2

jerrycoffman45 said:
I don't think you have to change cid with rogers just go to htcdev.com get you unlock token unlock boatloader push a recovery then flash a Rom and boot.I'mg
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
awesome, thanks pal

I just didn't want to ruin anything. works great, thanks!

I thought you couldn't root from stock 4.1.1...I'm so confused now.

Mozgus said:
I thought you couldn't root from stock 4.1.1...I'm so confused now.
Click to expand...
Click to collapse
You can't if you on att because atts cid is blocked on htcdev.com and so you need to change your cid to supercid which we can't do on 4.1.1 yet
Sent from my HTC One X using Tapatalk 2

jerrycoffman45 said:
You can't if you on att because atts cid is blocked on htcdev.com and so you need to change your cid to supercid which we can't do on 4.1.1 yet
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Oh, Rogers is a Canadian provider? Didn't realize what that was til now. Ok then. Bummer.

[Q] ATT HTC ONE XL, CID Stuck

I have a HTC One X from ATT and i tried to return it back to stock.. but apparently entered in the wrong CID (HTC__001) before i did S-On and a Lock.. now my screen says tampered and I can't change the CID with the All in One Toolkit by Hasoon2000, can someone please advise or help? I'm trying to send my phone into warranty to get my digitizer fixed thanks in advance!:laugh:

Have you tried unlocking from the HTC dev site? If you do that than you can s-off and make everything look stock.
Sent from my evita

RollTribe said:
Have you tried unlocking from the HTC dev site? If you do that than you can s-off and make everything look stock.
Sent from my evita
Click to expand...
Click to collapse
Hell Rolltribe, you were actually correct! All i had to do was get unlock file from HTCDev, Sorry i was under the impression that CID would affect the unlock. THanks for your help!!

cant unlock at&t htc one x bootloader

Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody

Darkpikasso said:
Hi everybody first of all excelent website...
I never had problems but when happens I look all over ethe Google or sea developers but this time I realy can't seem to get it done.
Moving from Samsung galaxy to HTC one x I can't unlock bootloader in order to flash a recovery and a Rom
I have try several tut but nnothing dosent change CID to unlock trought htcdev or the one click method or all one kit
And yes I search in all xda I like I say I don't get it right
Can someone help me, my info is:
Hboot 2.14
Android 4.1.1
Firmware version 3.18
At&t HTC one x
Thanks to everybody
Click to expand...
Click to collapse
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app

It's an at&t phone, the at&t CID is blocked by htcdev so you need to get SuperCID before being able to unlock the bootloader. Click the Everything Evita link in my signature and bookmark that thread, it's a resource thread that contains everything you'll ever need. Once you're in that thread navigate to the root section and find the 3.18 root method, this is the only method that'll work with your current firmware. Follow the instructions in that thread and then you can unlock your bootloader.
Once you have an unlocked bootloader you can install TWRP recovery which will allow you to root your stock ROM or install custom ROMs. If you need instructions on this click the How-To Guide For Beginners link in my signature, it's a thread I put together detailing some basic operations. If you have any questions feel free to ask in my Noob Friendly Q&A + General Help thread.
Sent from my One X using Tapatalk

You need to use the correct root method that corresponds to your firmware version in order to change your CID. Trying other methods you randomly Google around for is not going to work.
Use my Index thread, look under "ROOT" and find the method that matches your firmware number (3.18).
http://forum.xda-developers.com/showthread.php?t=1671237
There is not one-click method that works for firmware 3.18. Trying methods that don't match your firmware number is a waste of time.
Also, when asking for help, you need to be absolutely specific as to what you have tried, and what you haven't (including the result such as error messages, etc). If you don't give us specifics, it makes it even harder for us to help you.
Hasoon2000's all-in-one toolkit should work on 3.18. But if this is the one you tried, you haven't told us what happens when you try to use it.

To make it easier, here's the link to the 3.18 root method:
http://forum.xda-developers.com/showthread.php?t=2285086
You'll still want to bookmark the Everything Evita thread linked in my signature.
Sent from my One X using Tapatalk

Thank you everybody
When I try the all in one kit gave the error of waiting for the device, updated the adv drivers and still dosent show the CID change
In htcdev give me the MID not allowed error
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again

Darkpikasso said:
In most cases, all in one method, Jose method, motoXchopper method dosent seems to work what I'm going to try is to uninstall all the drivers for HTC one x and install again
Click to expand...
Click to collapse
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices

ruffain said:
There is a thread HTC one x noobs u check that I hvnt searched enough unlocking is a simple process and it's all over the xda
Here is the url
http://forum.xda-developers.com/showthread.php?t=2567916
Or just search root method for 3.18 HTC one x
Sent from my HTC One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Come on, you of all people shouldn't be giving attitude to this guy telling him he hasn't searched enough. You've asked me multiple questions that could have been answered if you had searched for the answer, including how to unlock your bootloader, that's kinda like the pot calling the kettle black.
It's easy for you to say unlocking the bootloader is an easy process once you've done it. The fact is that it isn't that simple for someone who is unaware that there are different methods for different firmware versions.
Sent from my One X using Tapatalk

redpoint73 said:
What the heck is "Jose method"? Again, I think your are fumbling around with methods that aren't even intended for your device or firmware version.
Do you have a working adb environment? What is the response if you use the command:
adb devices
Click to expand...
Click to collapse
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?

You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita

Darkpikasso said:
Thank you for all the responses
The error that gives me still is the same mid not allowed
Still having problems, but someone told me that it is first to root and then change the CID to superCID 1111111 and then run a all in one program to unlock
Is it thruth?
Click to expand...
Click to collapse
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.

Roadrunner? I don't think such a method exists for this device. You can't get s-off without root, you can't get root without an unlocked bootloader, you can get an unlocked bootloader without SuperCID, the only way to get SuperCID on his firmware is to use the 3.18 root method. Hence the reason that's been stated over and over again in this thread. It's the only solution. Carrier unlocking has absolutely nothing to do with the bootloader unlock / root process.
Sent from my Evita

timmaaa said:
You've been told quite a few times now that you can't unlock your bootloader until you have SuperCID. You need to use the 3.18 root method that I linked you to a few posts ago. Forget about the toolkits, just go to that thread and follow the instructions.
Sent from my Evita
Click to expand...
Click to collapse
Got it, first root and then unlock
Keep you update and thanks a lot for the help

No, SuperCID, unlock, custom recovery, root.
Sent from my Evita

timmaaa said:
No, SuperCID, unlock, custom recovery, root.
Sent from my Evita
Click to expand...
Click to collapse
Thanks everybody for the help but I can't get superCID
The htc dosent let him write and all the exploits to change it ether dosent find the device or dosent allow to write the commands
I really don't know what is the problem
I already install new drivers uninstall the ones from Samsung that I had and nothing
Not even my phone has the option to put it in charge only it has various opcitions but none of them are charge only

What do you mean by "all the exploits"? Which exploits have you tried? Did you try the 3.18 root method I gave you the link to?
Sent from my Evita

lemonfugu said:
Ok I had the same issue several months ago. I have AT&t One x as well. I noticed I could unlock the bootloader and S-OFF when my phone was carrier unlocked. I used the roadrunner method I believe (it's been awhile). I am certain Timaaaa knows what he is saying, but if you can't find a solution, that may be your other answer as well. Worked for me.
Click to expand...
Click to collapse
I got it....
I uninstall the drivers and install again there's were got the connection and unlocked but it says TEMPERED
Is that ok? Later in the afternoon I'm going to install custom recovery s-off and root

Yeah that's totally normal. I'd suggest you have a look at my How-To Guide For Beginners thread (link in my signature), it has some good instructions on your next steps.
Sent from my Evita

timmaaa said:
Roadrunner? I don't think such a method exists for this device.
Click to expand...
Click to collapse
Probably is referring to the Rumrunner s-off method. And yes, carrier (SIM) unlock has nothing to do with bootloader unlock and/or s-off. Probably just a coincidence that that person was able to bootloader unlock after doing SIM unlock.

Thank you very much for the help now I have it everydone unlock, custom recovery, root and s-off.
I was having problems with faceoff to s-off but nothing big
I already have install viperxl with beastmode kernel
Sent from my HTC One X using xda app-developers app