Database Info

[Guide] Telus HTC One X: Root, Recovery, ROM

Hello fellow users, this will be a step-by-step guide on how to modify the Telus version of the HOX on 1.91 firmware. This procedure is similar to that of the Rogers variant I believe, but there is currently no "one-click" method for the Telus firmware. I would like to stress that I am not a developper and that anything that you do to your phone is at your own risk. Neither myself, any those mentioned in this post and XDA can be held responsible for what you do to your phone.
Here we go!
Unlocking the bootloader:
NOTE: If you are using the AT&T One X with the 2.20 firmware, you will need to use the X-Factor exploit found here. This will effectively allow you to skip to part 2 of my guide.
1. Download the attached files. One will be to help you unlock your bootloader. The other is TWRP 2.3.1.
2. Ensure that you have ADB functioning on your computer and all drivers for your phone are installed.
3. Once you are all set, with your phone on, run the Spoof-CID.bat. Do this by right-clicking on the file and select "RUN AS ADMINISTRATOR". Do not close this window. Read each line carefully!
4. Log into htcdev.com and follow the instructions there. On completion, you should get your unlock token emailed to you.
5. Place the unlock token file in the same folder as Spoof-CID.bat and hit enter in your command prompt. On completion, you can close this window.
6. This will now unlock your bootloader! Congrats!
Installing TWRP 2.3.1:
1. Place the recovery image in the same folder as your ADB files.
2. Boot your phone into bootloader mode and select fastboot. If you are proceeding from part one, you should already be here.
3. Open a command prompt with Administrative rights and cd to your ADB folder.
4. In command prompt, type in "fastboot flash recovery [file name].img" without the quotes and replace [file name] with that of the name of the recovery file.
5. This will now flash TWRP 2.3.1! Congrats!
Flashing a custom ROM:
1. Boot into your recovery. If you are coming from the previous section, go back to bootloader and select recovery.
2. Perform a backup.
3. Mount your SD card from the Mount menu.
4. Choose a ROM. Ensure that it is for the One XL and not the One X International Version.
5. Copy this ROM into your SD card and flash!
6. Congrats! You now have a rooted Telus One X with a custom recovery and custom ROM!
/End How-To
APNs
If you install a custom ROM with no APNs set up, you will need to add them manually.
Telus LTE APNs
Must create two separate APNs
<name> TELUS SP
<apn> sp.telus.com
<proxy> not set
<port> not set
<username> not set
<password> not set
<server> not set
<mmsc> http://aliasredirect.net/proxy/mmsc
<mms proxy> 74.49.0.18
<mms port> 80
<mms protocol> WAP 2.0
<mcc> 302
<mnc> 220
<authentication type> not set
<apn type> default,mms,hipri
<bearer> unspecified
<name> TELUS ISP
<apn> isp.telus.com
<proxy> not set
<port> not set
<username> not set
<password> not set
<server> not set
<mmsc> not set
<mms proxy> not set
<mms port> not set
<mms protocol> WAP 2.0
<mcc> 302
<mnc> 220
<authentication type> not set
<apn type> dun
<bearer> unspecified
Rogers LTE APN settings
Name: Rogers LTE
APN: ltemobile.apn
MMSC: http://mms.gprs.rogers.com
MMS proxy: 10.128.1.69
MMS port: 80
MMS protocol: WAP 2.0
MCC: 302
MC: 720
APN enabled
Bearer: Unspecified
-----------------------------------------
Again, big thanks to the following:
kennethpenn (Him him with a thanks!): For providing the original Spoof-CID for Rogers and AT&T users
BIGMOH (Hit him with a thanks!): For modifying kennethpenn's original Spoof-CID tool to work with Telus users
ticklemepinks (Hit him with a thanks!): For providing me with insight
n3gkiwi: For the Rogers LTE APN
XDA & Community: For providing a supportive community
-----------------------------------------
Please let me know if this guide can be amended for clarity or correction of errors. I will do my best to keep it updated when one-click tools become available.

1.3 (Nov 21, 2012) - Updated attached files, added note to AT&T users on 2.20
1.2 (Oct 9, 2012) - Added Rogers APN information
1.1 (Aug 20, 2012) - Added Telus APN information; Confirmed working, LTE enabled
1.0 (Aug 4, 2012) - Initial release

wicked!
Athrun88 said:
People seem to do this =p
Click to expand...
Click to collapse
Looks good from what i can remember, as i had this phone around May
Glad to see Telus users here!!!

im a complete android noob, and i used this method to unlock and load a custom ROM on my rogers HOX,. worked flawlessly. The only difference is that i just followed the steps on HTCdev to unlock the bootloader without using the SpoofCID.
Thanks!

Hey thanks a lot. I just wanted to know, how can you tell if your HTC one X is from telus or rogers? Is there a way?

dan798 said:
Hey thanks a lot. I just wanted to know, how can you tell if your HTC one X is from telus or rogers? Is there a way?
Click to expand...
Click to collapse
Best way to tell if you haven't unlocked your phone is to download "CID Getter" from the Play store and see what the CID is. If it was from Telus, it will be Telus001 and if Rogers, then Rogers001 (i think)
either way, this method will work with both phones.

what about re-unlocking with 2.20 and original token?

ssconceptz said:
what about re-unlocking with 2.20 and original token?
Click to expand...
Click to collapse
Not sure about relocking the AT&T HOX. Relocking on the Telus version is fairly simple as bootloader unlocking is natively supported.

Athrun88 said:
Best way to tell if you haven't unlocked your phone is to download "CID Getter" from the Play store and see what the CID is. If it was from Telus, it will be Telus001 and if Rogers, then Rogers001 (i think)
either way, this method will work with both phones.
Click to expand...
Click to collapse
Awesome holy crap thank you!! Now I know haha, thats craiglist for you.

I'm not sure the Telus ISP APN is necessary. I have always just used the Telus SP one and I have LTE on my One X. What radio/RILs are people using? I seem to have similar connection and signal regardless so I switched back to the stock Rogers 1.94 one (using a Rogers One X on Telus).

dpvu said:
I'm not sure the Telus ISP APN is necessary. I have always just used the Telus SP one and I have LTE on my One X. What radio/RILs are people using? I seem to have similar connection and signal regardless so I switched back to the stock Rogers 1.94 one (using a Rogers One X on Telus).
Click to expand...
Click to collapse
Do a speed test, how's your ping and download speeds, then retest with second apn an tell us, lol not Telus, how big a difference in results.
For me same scenario as you almost, Rogers onex on Telus, poor ping an speeds until I added second apn, then full on LTE.
WR
Burnt off a Beast CleanRomV @ 2.1

dpvu said:
I'm not sure the Telus ISP APN is necessary. I have always just used the Telus SP one and I have LTE on my One X. What radio/RILs are people using? I seem to have similar connection and signal regardless so I switched back to the stock Rogers 1.94 one (using a Rogers One X on Telus).
Click to expand...
Click to collapse
This is how Telus has set up their version of the One X. It's not like I pulled it from thin air. If LTE truly works for you without the second APN setting, that's great; however, for my Telus variant with stock radio and RIL's, both APNs are required to get consistent LTE connection when in the GTA/Durham area.

how do i know the root worked?
i justed used your TWRP recovery on my telus ht one x and it reboot after pressing recovery mode in bootloader mode but how do i know that the root worked?

YYCsupreme said:
i justed used your TWRP recovery on my telus ht one x and it reboot after pressing recovery mode in bootloader mode but how do i know that the root worked?
Click to expand...
Click to collapse
Did you properly flash TWRP? Try the flash process again following the instructions closely. If you select recovery from the bootloader and it reboots, that's usually a bad flash. You won't have root until you flash a ROM that has already been rooted (ex. CleanROM) so make sure you back up your current ROM.
Sent from my HTC One XL using xda app-developers app

Are there any changes now that the JellyBean OTA update has come out?

raisage said:
Are there any changes now that the JellyBean OTA update has come out?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=39339584
Sent from my VENOMized HoxL

[Q] RUU downgrade - 130 - Model ID Error

The day I got my Canadian One S, I had an HTC upgrade waiting to be applied...
I was soooooo stupid to apply that, which made me Hboot 1.13 and radio 0.17...
I have rooted and s-off and all other necessary to install JB...
All went nice... I got ParanoidAndroid ROM(thanks guys, very nice job seriously) running smoothly...
However, after several days I've noticed that many people have been complaining that they can't reach me...
I've activated the operator's missed call SMS function and the result was shocking...
I was missing 70% of the calls each day... I started to track the status of the device then...
This is what I've discovered:
Network is constantly switching between 3G, H and H+...
Even if there's H on the screen, sometimes there's no connection actually.
While searching for the probable root cause of the problem, I've installed seven different ROMs, including Android 4.0.4 and 4.1.
The problem remains, so I assume ParanoidAndroid ROM works fine. I have a different problem.
I kept searching and found out that many people have similar problems but I failed to find an exact solution.
One of the articles says that it may be the radio version, which makes sense to me.
Now I'm trying to downgrade the phone since three days.
The RUU I've been trying is:
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
because I was thinking that GSM network is GSM network and so EU RUU shall work.
But the error I get is Model ID Error, coded 130; which actually tells me that I'm being stupid again because I'm using a wrong RUU.
Now, I'm very tired(really, physically tired, I don't mean that I'm bored) so I need some sleep...
Is there any guru here who may help me? What RUU is correct for my Canadian One S? I got it from Fido in Toronto but because of my work, I'm using it in Asia, in Kazakhstan.
Cheers... :silly:

erol.savas said:
The day I got my Canadian One S, I had an HTC upgrade waiting to be applied...
I was soooooo stupid to apply that, which made me Hboot 1.13 and radio 0.17...
I have rooted and s-off and all other necessary to install JB...
All went nice... I got ParanoidAndroid ROM(thanks guys, very nice job seriously) running smoothly...
However, after several days I've noticed that many people have been complaining that they can't reach me...
I've activated the operator's missed call SMS function and the result was shocking...
I was missing 70% of the calls each day... I started to track the status of the device then...
This is what I've discovered:
Network is constantly switching between 3G, H and H+...
Even if there's H on the screen, sometimes there's no connection actually.
While searching for the probable root cause of the problem, I've installed seven different ROMs, including Android 4.0.4 and 4.1.
The problem remains, so I assume ParanoidAndroid ROM works fine. I have a different problem.
I kept searching and found out that many people have similar problems but I failed to find an exact solution.
One of the articles says that it may be the radio version, which makes sense to me.
Now I'm trying to downgrade the phone since three days.
The RUU I've been trying is:
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
because I was thinking that GSM network is GSM network and so EU RUU shall work.
But the error I get is Model ID Error, coded 130; which actually tells me that I'm being stupid again because I'm using a wrong RUU.
Now, I'm very tired(really, physically tired, I don't mean that I'm bored) so I need some sleep...
Is there any guru here who may help me? What RUU is correct for my Canadian One S? I got it from Fido in Toronto but because of my work, I'm using it in Asia, in Kazakhstan.
Cheers... :silly:
Click to expand...
Click to collapse
You can change your carrier ID so you can pass the model check when using any RUU by follow the instructions at the link below. If you do change your carrier ID then you'll need to unlock your bootloader though htcdev.com after you run a RUU.
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Also, after you change to super cid keep in mind you can only run RUU's which contain the same hboot version you are currently running or a higher version. In your case hboot 1.13 or hboot 1.14.

Thanks a lot but...
dc211 said:
You can change your carrier ID so you can pass the model check when using any RUU by follow the instructions at the link below. If you do change your carrier ID then you'll need to unlock your bootloader though htcdev.com after you run a RUU.
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Also, after you change to super cid keep in mind you can only run RUU's which contain the same hboot version you are currently running or a higher version. In your case hboot 1.13 or hboot 1.14.
Click to expand...
Click to collapse
Thanks a lot.
In fact I read the CID change method but most probably because of late-night-sleepy mood, I've considered the method as brand and model specific thing. After five hours sleep, I see that it is not...
I've performed all the steps and I've succeeded to install this RUU:
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
As you have mentioned about hboot, the RUU didn't downgrade my hboot from 1.13 but it did downgrade the radio from 0.17 to 0.16. and OpenDSP from v28 to v25.
I've performed all rooting and installed CWM recovery and I've restored the backup.
I got JB back without any hassle.
However, the 3G, h and H+ switching problem still remains, which actually made me look for a solution for RUU installation.
So radio downgrade didn't help...
It's very annoying to see the network constantly switching... And I have reasons to believe that this switching is draining the battery.
Would you have any suggestions on that particular issue?
(I don't know if this is important but I since the problem is still remaining, let me mention anyway...
The geniuses in Fido, even after asking about it for three times, gave me an operator locked phone...
So when I arrived here and have inserted the KZ operator SIM, the phone got locked.
I unlocked it myself...)
Cheers

How did you S-OFF?
Sent from my locked, tampered ville

erol.savas said:
Thanks a lot.
In fact I read the CID change method but most probably because of late-night-sleepy mood, I've considered the method as brand and model specific thing. After five hours sleep, I see that it is not...
I've performed all the steps and I've succeeded to install this RUU:
RUU_Ville_U_HTC_Europe_1.78.401.2_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_258480_signed
As you have mentioned about hboot, the RUU didn't downgrade my hboot from 1.13 but it did downgrade the radio from 0.17 to 0.16. and OpenDSP from v28 to v25.
I've performed all rooting and installed CWM recovery and I've restored the backup.
I got JB back without any hassle.
However, the 3G, h and H+ switching problem still remains, which actually made me look for a solution for RUU installation.
So radio downgrade didn't help...
It's very annoying to see the network constantly switching... And I have reasons to believe that this switching is draining the battery.
Would you have any suggestions on that particular issue?
(I don't know if this is important but I since the problem is still remaining, let me mention anyway...
The geniuses in Fido, even after asking about it for three times, gave me an operator locked phone...
So when I arrived here and have inserted the KZ operator SIM, the phone got locked.
I unlocked it myself...)
Cheers
Click to expand...
Click to collapse
Glad it worked. For the network switching I think that's fast dormancy doing it's thing but your carrier has to support it. To disable it add these lines to your build.prop file.
ro.ril.fast.dormancy.rule=0
ro.ril.disable.power.collapse=1
or if those already exist change them to match above and see if that fixes it.

I'm sorry
usaff22 said:
How did you S-OFF?
Sent from my locked, tampered ville
Click to expand...
Click to collapse
I'm very sorry to alarm you; my mistake...
I have been very exhausted last night... I've mistyped few but very critical things, such as s-off.
Within my technical limits ans skills, of course no s-off...
I've corrected my signature.
Sorry again...
Cheers

Now, let me track the status
dc211 said:
Glad it worked. For the network switching I think that's fast dormancy doing it's thing but your carrier has to support it. To disable it add these lines to your build.prop file.
ro.ril.fast.dormancy.rule=0
ro.ril.disable.power.collapse=1
or if those already exist change them to match above and see if that fixes it.
Click to expand...
Click to collapse
Thanks mate.
I've added the two lines to build.prop
Even though the switching still is going on, I suspect that it is quite less dynamic than before.
Today, I'll be watching the status of data and the missed call SMS' from the operator.
I'll of course let you know the outcome tomorrow.
Cheers :good:

erol.savas said:
Thanks mate.
I've added the two lines to build.prop
Even though the switching still is going on, I suspect that it is quite less dynamic than before.
Today, I'll be watching the status of data and the missed call SMS' from the operator.
I'll of course let you know the outcome tomorrow.
Cheers :good:
Click to expand...
Click to collapse
Don't forget you gotta reboot for it to take effect.

dc211 said:
Don't forget you gotta reboot for it to take effect.
Click to expand...
Click to collapse
Yes, sure.
I've rebooted after adding those two lines.
So far it's better...

dc211 said:
Don't forget you gotta reboot for it to take effect.
Click to expand...
Click to collapse
OK, here I am...
The problem is still going on...
However... I found out something very interesting...
Yesterday I felt very upset and disappointed with the One S and bough myself a new One X...
I didn't install any HTC updates, etc... I unlocked the bootloader and installed CWM recovery...
Put my favorite ROM, the latest version of ParanoidAndroid...
Inserted the SIM card... Guess what?.. Same thing... Switching between 3G, H, H+ !...
You can't imagine how surprised and shocked I was. I started to consider burning both phones in my back yard.
But before buying some alcohol for easier burn, I've decided to check the issue with another SIM card. :cyclops:
So I've asked from one of my friends having micro-SIM to give me his SIM for 5 mins to test...
While explaining him the problem on his One X, I saw that -with another operator SIM card- his One X is in the same situation...
His One X is pure factory default, no bootloader mods, no recoveries, no custom ROM, etc...
Since he keeps the data off all the time but uses only wifi, the guy had never noticed the issue.
So I'm shocked for two times in 20 hours
Now what?.. The networks of all operators in Kazakhstan have some kind of a problem?
Or is this really a problem?...
Four days ago I was using the same operator network with my good-old HTC Desire and I haven't witnessed such issues with that one, neither with the two EVO 3Ds I have, nor with the Motorola Xoom. By the way, they're still fine... No switching issues so far...
What may the difference be between these old models and the new series?
Problematic new radio hardware or firmware HTC uses in the One series?
If this was only a switching issue, I might think that it may not be a problem actually but the phone still is dropping from the GSM network and I still receive missed call SMS from the operator...
Delays in sending SMS, etc...
What the heck is going on here?
Cheers

Should this method always work?
dc211 said:
You can change your carrier ID so you can pass the model check when using any RUU by follow the instructions at the link below. If you do change your carrier ID then you'll need to unlock your bootloader though htcdev.com after you run a RUU.
http://forum.xda-developers.com/showthread.php?p=26516911#post26516911
Also, after you change to super cid keep in mind you can only run RUU's which contain the same hboot version you are currently running or a higher version. In your case hboot 1.13 or hboot 1.14.
Click to expand...
Click to collapse
Hi, I'm not able to run the RUU with this method (130 - Model ID Error). CID is 11111111, phone (One S) is unlocked by htcdev.com. The mid is PJ4020000 and I didn't find any way to change the it (fastboot oem writemid PJ4010000 doesn't work). Hboot version is 2.09. I tried to install both RUU_Ville_U_HTC_Europe_1.78.401.2 and RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5. Can anybody help me, please?

Problem because of S3 processor
jkniep said:
Hi, I'm not able to run the RUU with this method (130 - Model ID Error). CID is 11111111, phone (One S) is unlocked by htcdev.com. The mid is PJ4020000 and I didn't find any way to change the it (fastboot oem writemid PJ4010000 doesn't work). Hboot version is 2.09. I tried to install both RUU_Ville_U_HTC_Europe_1.78.401.2 and RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5. Can anybody help me, please?
Click to expand...
Click to collapse
Nevermind, I just found out that I couldn't update because I have the S3 version (which, of course, nobody at the store told me) and therefore need another RUU.

usaff22 said:
How did you S-OFF?
Sent from my locked, tampered ville
Click to expand...
Click to collapse
+1! Lol
HTC One S

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?

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

Ville S4 - No Mobile Data after flashing CM 11

Hi all,
I got an HTC one S (ville S4) that used to be a branded phone for TMO Germany. Assuming there was no SIM lock (or that it would be removed by changing OS), I flashed CM 11 on it and now want to use it with Orange PL. Telephony and messaging is working just fine, but mobile data refuses to work.
Here is a list of what I did:
Confirmed APN settings
Checked with different SIM of same provider - same result
Checked with same SIM in different phone (galaxy s3) - worked like a charm
Tried with TMO PL SIM in ville S4 - worked like a charm
Checked endless forum entries to no avail - either I am not knowledgable enough or links are broken or the issue described is slightly different
Made radio logs for ville s4 with Orange PL SIM and with TMO PL SIM - I can supply the relevant parts - generally though I hoped it would tell me something, but it doesn't really do that...
In short, I think I might have a SIM lock still in place which messes up my phone. I found a guide on how to remove SIM lock, but for this, I would need to be on stock. I found some links to RUUs, but most of them seem to be borken, and I generally do not know which is appropriate.
Questions:
Is there a way to remove a potentially left over SIM lock without making changes to the general setup I have atm?
Can somebody please supply a stock RUU for my phone? Would the one below listed below work?
Thank you so much!
Best wishes,
Friedrich
Added information on phone and RUU I found:
Phone:
Tampered/Unlocked
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO_1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
RUU name:
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe

Hi all - is there really anyone who is able and/or willing to help? Is it a lack of background info? If you tell me what you need, I'll happily supply it.
Thank you all!
Friedrich
Falkenfink said:
Hi all,
I got an HTC one S (ville S4) that used to be a branded phone for TMO Germany. Assuming there was no SIM lock (or that it would be removed by changing OS), I flashed CM 11 on it and now want to use it with Orange PL. Telephony and messaging is working just fine, but mobile data refuses to work.
Here is a list of what I did:
Confirmed APN settings
Checked with different SIM of same provider - same result
Checked with same SIM in different phone (galaxy s3) - worked like a charm
Tried with TMO PL SIM in ville S4 - worked like a charm
Checked endless forum entries to no avail - either I am not knowledgable enough or links are broken or the issue described is slightly different
Made radio logs for ville s4 with Orange PL SIM and with TMO PL SIM - I can supply the relevant parts - generally though I hoped it would tell me something, but it doesn't really do that...
In short, I think I might have a SIM lock still in place which messes up my phone. I found a guide on how to remove SIM lock, but for this, I would need to be on stock. I found some links to RUUs, but most of them seem to be borken, and I generally do not know which is appropriate.
Questions:
Is there a way to remove a potentially left over SIM lock without making changes to the general setup I have atm?
Can somebody please supply a stock RUU for my phone? Would the one below listed below work?
Thank you so much!
Best wishes,
Friedrich
Added information on phone and RUU I found:
Phone:
Tampered/Unlocked
VLE PVT SHIP S-ON RL
HBOOT-2.15.0000
RADIO_1.15.50.05.29
OpenDSP-v31.1.0.45.0815
eMMC-boot
Dec 14 2012, 17:10:57:-1
RUU name:
RUU_Ville_U_TMO_DE_1.77.111.5_Radio_0.16.31501S.17_2_10.23.31501S.10L_release_259421_signed.exe
Click to expand...
Click to collapse

Falkenfink said:
Hi all - is there really anyone who is able and/or willing to help? Is it a lack of background info? If you tell me what you need, I'll happily supply it.
Thank you all!
Friedrich
Click to expand...
Click to collapse
Your problem seems to be very specific. Thats probably why you get no answers. Your phone was TMO branded, means the radio is TMO version too. The solution could be to S-OFF your phone and flash unbranded EU firmware including radio.

LS.xD said:
Your problem seems to be very specific. Thats probably why you get no answers. Your phone was TMO branded, means the radio is TMO version too. The solution could be to S-OFF your phone and flash unbranded EU firmware including radio.
Click to expand...
Click to collapse
Hi LS.xD,
Thanks for taking the time to reply! Very much appreciated!
I was already thinking about flashing different radio and S-OFF the phone. However, none of the guides I found for achieving S-OFF seemed to apply for me as I felt some prerequisites weren't met by my specific case. Do you happen to have experiencing with S-OFF'ing a HTC ONE S?
If S-OFF wouldn't work - is there another chance to get another radio version and/or firmware installed?
Thanks again!
Friedrich

Falkenfink said:
Hi LS.xD,
Thanks for taking the time to reply! Very much appreciated!
I was already thinking about flashing different radio and S-OFF the phone. However, none of the guides I found for achieving S-OFF seemed to apply for me as I felt some prerequisites weren't met by my specific case. Do you happen to have experiencing with S-OFF'ing a HTC ONE S?
If S-OFF wouldn't work - is there another chance to get another radio version and/or firmware installed?
Thanks again!
Friedrich
Click to expand...
Click to collapse
Try flashing a stock RUU or sense based rom. Then use rumrunner.us to gain S-OFF.

LS.xD said:
Try flashing a stock RUU or sense based rom. Then use rumrunner.us to gain S-OFF.
Click to expand...
Click to collapse
Howdy! So I went back at this and, oh boy, did that work.
I tried some roms and ended up with MIUI from here. Ironically internet worked without problem using this ROM...
I then followed all instructions from rumrunner and it worked like a charm. Fast boot is hidden away in a different place though on MIUI and I can also confirm that on Ubuntu 14.04 64-Bit rumrunner is working despite being not supported.
All that just in case someone else will have the problem too.
Now I am trying to figure out how to install new firmware and / or change my CID from t_MOB101 - but I guess I'll manage eventually...
Thanks for the help so far!

Falkenfink said:
Howdy! So I went back at this and, oh boy, did that work.
I tried some roms and ended up with MIUI from here. Ironically internet worked without problem using this ROM...
I then followed all instructions from rumrunner and it worked like a charm. Fast boot is hidden away in a different place though on MIUI and I can also confirm that on Ubuntu 14.04 64-Bit rumrunner is working despite being not supported.
All that just in case someone else will have the problem too.
Now I am trying to figure out how to install new firmware and / or change my CID from t_MOB101 - but I guess I'll manage eventually...
Thanks for the help so far!
Click to expand...
Click to collapse
Changing CID:
fastboot oem writecid HTC__001
[HTC__001 is unbranded Europe]

LS.xD said:
Changing CID:
fastboot oem writecid HTC__001
[HTC__001 is unbranded Europe]
Click to expand...
Click to collapse
Thanks for the super-quick reply! Trying to apply this, however, doesn't seem to work for me.
I am in Fastboot Mode USB (there were tampered/unlocked is written on top etc.) I copy/paste the command into terminal and all I get is <waiting for device>. Am I simply in the wrong spot for this?

Falkenfink said:
Thanks for the super-quick reply! Trying to apply this, however, doesn't seem to work for me.
I am in Fastboot Mode USB (there were tampered/unlocked is written on top etc.) I copy/paste the command into terminal and all I get is <waiting for device>. Am I simply in the wrong spot for this?
Click to expand...
Click to collapse
type:
fastboot devices
If everything is right your device will be listed, otherwise you'll have to reconnect it.
Are you still running Linux? Fastboot must be executed as "root" or with "sudo" prefix

LS.xD said:
type:
fastboot devices
If everything is right your device will be listed, otherwise you'll have to reconnect it.
Are you still running Linux? Fastboot must be executed as "root" or with "sudo" prefix
Click to expand...
Click to collapse
Yes, I noticed... I flashed boot.img so many times with S-ON. I tried a couple of times and then simply used "sudo fastboot reboot-bootloader" to check if there is anything at all. After that it just worked with "fastboot oem writecid HTC__001" - upon rebooting another time into bootloader, now all is shiny! I still think the better explanation for this is that I did do some stupid mistake, but well...
Thank you so much! Just so you know: you helped me fix something that was bugging me since Christmas! So _really_ appreciate the help!
And with proper CID internet is working too! F**K YEAH!

Falkenfink said:
Yes, I noticed... I flashed boot.img so many times with S-ON. I tried a couple of times and then simply used "sudo fastboot reboot-bootloader" to check if there is anything at all. After that it just worked with "fastboot oem writecid HTC__001" - upon rebooting another time into bootloader, now all is shiny! I still think the better explanation for this is that I did do some stupid mistake, but well...
Thank you so much! Just so you know: you helped me fix something that was bugging me since Christmas! So _really_ appreciate the help!
And with proper CID internet is working too! F**K YEAH!
Click to expand...
Click to collapse
Stock firmware EU can be found HERE (contains also radio)
I use radio 1.20
If you need to bring your phone back to stock you can use this RUU