Database Info

[Q] HTC One X (AT&T) HTCdev Unlock problems

My friend and I are having problems unlocking his HTC One X. we've tried various tutorials and followed many threads but have had no luck. We've tried the One_X_ATT_All_In_Kit_v2.1.1, Root-one-x and OneXRootOneClick with no luck. The bootloader will not unlock, we kept getting an error code 160 and MID not allowed. So no Unlock_Bin was generated. It has been upgraded to 4.1 via the AT&T update.
Bootloader screen reads:
EVITA PVT SHIP S-ON RL
HBOOT-2.14.0000
RADIO-0.24p.32.09.06
OpenDSP-V34.1.0.45.1219
eMMC-boot
Nov 26, 2012, 18:37:14:-1
If anybody can point us in the direction of where we can go to root the phone, that'd be great.

Try asking in the Evita forum here: http://forum.xda-developers.com/forumdisplay.php?f=1538
This forum is for the International version (Endevor)

I'm sorry about that, is there anyway a Mod can move this over to that forum? I don't want to create another thread for the same issue

Request sent.

Welcome to the One XL thread!
http://forum.xda-developers.com/showthread.php?p=33189590
[TOOL] HTC One X (Evita) All-In-One Toolkit V2.1.1 [2-1-2013] [PERM ROOT][Noob-Proof]
Here is what you need. If you took the job ota I'm afraid you stuck without root for now. But if you need further assistance let us know?
Sent from my HOX w/CM10.1 4.2.2 s-off

nawarkk said:
HBOOT-2.14.0000
Click to expand...
Click to collapse
I'm afraid you're out of luck for now. There is no root method for JB yet.

iElvis said:
I'm afraid you're out of luck for now. There is no root method for JB yet.
Click to expand...
Click to collapse
Duh... I all ways forget to look at the specifics
2.14 vs 1.14
Thanks Elvis.
Yea too bad we can't spoof the cid as before.
Sent from my HOX w/CM10.1 4.2.2 s-off

I believe, via the all in one toolkit, we were able to get the CID to change to 111111, but only after a few tries. I'll have to check back with him if it indeed did change.
So what you guys are saying, is unless somebody finds a way to crack JB, there is no way to unlock the bootloader/root?
Is it not possible to run the RUU that would place him back to the android and hboot he had before? (Don't know if it was ICS or what it was)

nawarkk said:
I believe, via the all in one toolkit, we were able to get the CID to change to 111111, but only after a few tries. I'll have to check back with him if it indeed did change.
So what you guys are saying, is unless somebody finds a way to crack JB, there is no way to unlock the bootloader/root?
Is it not possible to run the RUU that would place him back to the android and hboot he had before? (Don't know if it was ICS or what it was)
Click to expand...
Click to collapse
Can't run a ruu for older firmware without s-off.
But if you actually achieved supercid, you should be able to unlock, root, and s-off.

Are you positive about that? Because I was able to run an older RUU on my HTC Evo 3d, and got the phone to an older firmware without S-Off..
We'll have to check for sure on the CID and report back when we can.

nawarkk said:
Are you positive about that? Because I was able to run an older RUU on my HTC Evo 3d, and got the phone to an older firmware without S-Off..
We'll have to check for sure on the CID and report back when we can.
Click to expand...
Click to collapse
Different phone. Newer ruu's check for hboot versions. Won't work on this one.

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

[Q] help please

hey everyone, i had my telstra one xl on JB for awhile then i wanted to do the newest update from them so upon reading up on it i need to have supercid and s-off, so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111, sweet now to do s-off which failed to flash the RUU, i needed to relock the bootloader, so i relocked it.
problem is now its stuck in a bootloop to fastboot and wont show up in ADB devices, i also cant get into twrp in recovery now.
is there any way to fix this or throw the phone out?

It's a bit difficult to make out what you're saying in parts of that post.
Was s-off successful?
Was the RUU successful?
Which RUU did you use?
What are your current bootloader details?
Sent from my Evita

sirus17 said:
so i thought no worries i'll check my cid first which was telst001 (or something like that), found a one click script and changed to the supercid, so it was 11111111,
Click to expand...
Click to collapse
Did you actually verify that you had SuperCID? I don't think there is a one-click for the Telstra version. The one-click app for SuperCID I'm aware of is intended for AT&T, and will fail with any other CID.
Which may actually be a good thing (if SuperCID failed). Since if a Jellybean RUU is flashed with SuperCID and s-on (its not clear whether you were successful with s-off) it will pretty much a guaranteed brick.
sirus17 said:
is there any way to fix this or throw the phone out?
Click to expand...
Click to collapse
If the screen comes on, its probably possible to recover. But we need more info as timmaaa indicated above.

There is actually a one-click tool for the Telstra version, I stumbled across it very soon after getting my phone mid last year. I found it on an Australian Android site, I think it was Ausdroid.
I'm not sure whether the tool is specifically for the Telstra version alone, but it definitely works on Telstra Evitas as I used it on my fiance's Evita (and mine which is a Hong Kong model).
Sent from my Evita

I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.

twistedddx said:
I thought the one click tool here supported AT&T, Rogers and Telstra CID changing.
Click to expand...
Click to collapse
Really not sure, now that I look into it more. If its the old one by DesignGears, it does work with Rogers, but doesn't seem to mention Telstra (at least if I just search the thread for "Telstra"): http://forum.xda-developers.com/showthread.php?t=1672284
And x-factor also fails for any CID except AT&T, if I understand correctly. So it seems these scripts all look for certain CIDs, so if its not explicitly included, they will fail. Of course, if there is one made specifically for Telstra (as timmaaa mentioned) it apparently wasn't posted on XDA.
But really my main point is that the OP needs to verify and be clear on this, as well as several other factors.

[Q] Telstra One XL Help.....

I was wondering if someone could help me? ... I recently acquired a Telstra Htc One XL and am having troubles trying to update.
Current stats
android 4.1.1
sense 4+
software 3.17.841.2
EVITA PVT SHIP S-OFF RL
*****locked*****
CID-11111111
HBOOT 2.14.0000
RADIO- 0.23a.32.09.29
I'm 99.9% sure most testra one xl's are up to 4.2.2 with sense 5 which is i think two updates in front of mine
can anyone shed some light on my situation?

When you say you're having trouble updating what exactly do you mean?
Sent from my Evita

When i "Check for Updates" it tell me that there are no more updates.... when Im sure there are another two...

Are you in Australia?
Sent from my Evita

Sure am ... Good old city of churches" Adelaide" ..

timmaaa said:
Are you in Australia?
Sent from my Evita
Click to expand...
Click to collapse
His profile says he is

Yeah, but still needed to check. Have you thought about re-unlocking your bootloader? It's been modified in the past which might have something to do with your update problem. If you unlock your bootloader you'll be able to install a custom recovery and then you can install whatever ROM you like. We have the stock Telstra Sense 5 Android 4.2.2 ROM in our development section. We also have a few other Sense 5 ROMs to choose from, ranging from stock to tweaked.
Sent from my Evita

The thing is that it hasnt been messed with.I got the phone from a HTC rep that i know ... he had it in his draw for over six months ...I just wanted the stock update but maybe rooting might be the easier way

It definitely has been messed with, phones that are s-off and have SuperCID don't come out of the factory like that. Somewhere along the way someone has done those alterations to the device.
There is just one problem I've realised, your phone has a SuperCID of 11111111 which has been blocked by htcdev. You're s-off though so you can actually change that as many times as you like using fastboot. If you want to unlock your phone you'll need to change it to 22222222 using the following fastboot command:
Code:
fastboot oem writecid 22222222
You can then check the new CID by using this command:
Code:
fastboot oem readcid
Once that's done you can go to htcdev and go through with the unlock bootloader process.
In order to do the above process you will need to install adb/fastboot and HTC drivers.
Sent from my Evita

No problem ... thanks for that ....I have rooted my one x before HTC_023 fairly basic but my mate swears that the phone came straight from HTC as a Tell us what you think before we send you more kind of thing .. Cheers for the info ...
Actually one more thing ... is it possible to do a RUU update with this to 4.2.2?

There is no RUU for 4.2.2, the only way is to run an earlier RUU and take OTA updates to get there. Since you can't get the OTA I guess that isn't an option though.
Sent from my Evita

grekojim said:
Sure am ... Good old city of churches" Adelaide" ..
Click to expand...
Click to collapse
Within 30 minutes drive from me no doubt
Supercid and s-off from factory or not still means you are off the official path.
Things I might do:
fastboot oem writecid TELST001
Then try the OTA again
or
RUU back to 1.89.841.9 as a RUU exists for that, then ota forwards to 5.06.841.1
or
Unlock bootloader
Flash Turges 5.08 firmware zip and then take one of the Sense 5 ROMs. There is a stock Telstra ROM even.
PS nag the HTC rep for a more recent RUU, eg 2.40.841.4, 3.17.841.2, 3.17.841.9 or 5.06.841.1 and share with us
---------- Post added at 12:56 PM ---------- Previous post was at 12:48 PM ----------
timmaaa said:
Once that's done you can go to htcdev and go through with the unlock bootloader process.
Click to expand...
Click to collapse
He has s-off does he need a token or even need to unlock at all?

I have often wondered the same thing, but I've been assuming that in order to flash TWRP recovery you need an unlocked bootloader.
It's nice to see a few Aussies on here by the way, I'm in Melbourne myself.
Sent from my Evita

great ... trying the cid thing first ...

My phone from an att employee came s-off and with a locked boot loader as well. It just looks like that's how HTC and att do it.
Sent from my HTC One XL

Alright cid change didnt work ..now to find the 1.89.841.9 RUU

Click the link in my signature, from there you'll find a link to the HTC RUU thread.
Sent from my Evita

RUU links all changed and the index doesnt keep good track of the current RUU sites.
Try:
http://www.androidruu.com/?developer=Evita
http://www.androidruu.com/getdownlo...09.01_10.93a.32.20L_release_266699_signed.exe

Thank you heaps .....

Just in case .. i got the unlock code from htc deV But when my cid was 11111111 .....would that matter if i use that code now that my cis is telst001?

Detailed instructions for S-Off region change

I have recently purchased a dual sim htc u12+ and was hoping someone could provide details to change it to an US Unlocked Model. I have found instructions for older models of the HTC but want to make sure of the all precautions I should take

Have you looked in the Guides, news, discussion sub forum?
Sent from my HTC U12+ using XDA Labs

I did and no one has posted a guide for the conversion process. I understand you need to use sunshine and modify certain settings. I have read people discussing success but not really explaining the details. The fastboot commands needed to change said details, what all settings need to be changed, should a RUU be used immediately, how to use S-off if you can't boot from any mistakes. These are things I'm looking to get answered. I understand things keep changing as new HTC models come out and just want some feedback on what precautions to take. I would gladly send a donation to any user who would take the time to post a handy guide to share with the rest of the community as well.

You need to unlock your Bootloader and root your phone, afterwards use Sunshine to gain S-OFF. Reboot into fastboot and set the cid you'd like to use. Than flash a RUU/Factory image on your phone matches your new cid.

mdxdave said:
You need to unlock your Bootloader and root your phone, afterwards use Sunshine to gain S-OFF. Reboot into fastboot and set the cid you'd like to use. Than flash a RUU/Factory image on your phone matches your new cid.
Click to expand...
Click to collapse
What fastboot command do you use to set the CID? Is changing the MID not necessary? I want to use US Unlocked and according the firmware thread I know that MID: 2Q5520000 and CID: BS_US001 are for US Unlocked. Is this information correct?

Command should be
Code:
fastboot oem writecid
But check your current details by typing
Code:
fastboot getvar all
and post here just to be sure

Thank for you all for the help.

8bitbang said:
Thank for you all for the help.
Click to expand...
Click to collapse
Would you be able to post a write up of how you did this? I'm looking to change my CID so I can finally get Pie but I'm not 100% either. I've done a bunch of other HTC phones before but none with temp S-OFF and that's giving me a little hesitation

heslo.rb26 said:
Would you be able to post a write up of how you did this? I'm looking to change my CID so I can finally get Pie but I'm not 100% either. I've done a bunch of other HTC phones before but none with temp S-OFF and that's giving me a little hesitation
Click to expand...
Click to collapse
Sure I'll be glad to make instructions, give me a bit and I'll update the topic

8bitbang said:
Sure I'll be glad to make instructions, give me a bit and I'll update the topic
Click to expand...
Click to collapse
Legend! Cheers