Database Info

Telstra One XL Thread - RUU Added to OP

Telstra have released the One XL. But unlike the Americans, we get 32GB
All custom ROMs work on the Aussie One XL :good:
RESOURCES
[GUIDE] Telstra One XL - Root/Unlock/Recovery/ROMs/APN/Tweaks
Telstra One app
1.81 RUU
1.89 RUU
Rooted & Deodexed Stock Telstra ROMs by radavs
One Click Unlock (ozjubb has modified the One Click Unlock to work with our Telstra One XL)
------------------------------
Build.prop Edits
Most custom ROMs are not optimised for Telstra. Edit these values in your build.prop to get the best HSPA+ speeds and HD Voice:
Code:
ro.ril.hsdpa.category=24
ro.ril.enable.amr.wideband=1
Telstra APN Settings
Most custom ROMs won't have the correct APN due to the ATT crap, so you'll need to enter these manually.
(Internet)
Name: Telstra Internet
APN: Telstra.wap
Proxy: 10.1.1.181
Port: 80
APN type: default
Leave other fields unchanged
(MMS)
Name: Telstra MMS
APN: Telstra.mms
MMSC: http://mmsc.telstra.com:8002
MMS proxy: 10.1.1.180
MMS port: 80
APN type: mms
Leave other fields unchanged

I'm also curious of what ROM I could install - hoping that CM9 will support telstra's one xl.

I would expect it to be at least a couple of months before CM9 is ported and stabilised on the HTC One XL

Arrived this morning!
Can anyone confirm a root technique for this device?
I'll be giving it a shot this afternoon.

If its anything like the velocity/vivid then roms are interchangeable
Sent from my SGH-I777 using Tapatalk 2

Just got mine this morning so will update here as I find out what its like Battery life etc
So far a big jump in speed comapred to old Desire running a miui rom. To be epxected tho
Cheers

Got mine today as well.
Pretty curious about the ROMS and rooting. Planning on rooting in the next day or so.
But so far I like the speed. Both LTE and the device.

Got mine, it's a gorgeous phone!
Still waiting for the micro SIM to become active..taking ages
Still unsure too if we can use the same development files as the ATT One X or not?

the_scotsman said:
Still unsure too if we can use the same development files as the ATT One X or not?
Click to expand...
Click to collapse
Ive read that root is possible on the ATT files. however I haven't found any hard evidence that it actually works.
I also found on the Ausdroid forums that there is a root guide for the Telstra One XL, but still no confirmation on success. - Any one here tried this?

wonder if it worth trying this ? to at least get the bootloader unlockable.
Found this here
????
Phone has to be rooted first.....which we maybe able to achieve this way

Hmmm...I'm not 100% game to try yet.
Though someone on whirlpool posted that this works for root: http://ausdroid.net/2012/05/21/how-to-root-the-htc-one-xl-generic-telstra/

wells79 said:
Arrived this morning!
Can anyone confirm a root technique for this device?
I'll be giving it a shot this afternoon.
Click to expand...
Click to collapse
Confirming that rooting via [EASY][GUIDE] The SuperUser's Guide - All Things Root! worked on my one out of the box.
1.81 Firmware

wells79 said:
Confirming that rooting via [EASY][GUIDE] The SuperUser's Guide - All Things Root! worked on my one out of the box.
1.81 Firmware
Click to expand...
Click to collapse
SO you only rooted? Did you unlock the bootloader or flash any ROM?

the_scotsman said:
SO you only rooted? Did you unlock the bootloader or flash any ROM?
Click to expand...
Click to collapse
I used that method and got root, just starting to look around to see about superCID and bootloader unlock.

Cool...keep us posted here guys so we know what's what. Telstra still haven't activated my SIM card yet so I'm waiting for that before I start playing.

the_scotsman said:
Cool...keep us posted here guys so we know what's what. Telstra still haven't activated my SIM card yet so I'm waiting for that before I start playing.
Click to expand...
Click to collapse
Also done the superCID following the guide here:
http://forum.xda-developers.com/showthread.php?t=1671396
Just have to go through the HTCDev to see if I can unlock it, HTCDev doesn't seem to be working ATM though.
EDIT: Should point out it was change TELST001 to 11111111 not CWS__001 for the Telstra handset for the SuperCID

I thought I would mention that it looks like the WIFI slow down problem is an issue with this phone too.

I have rooted the device but it wont give me the code to get it unlocked...just hangs on waiting for device in the command prompt.

ozjubb said:
Should point out it was change TELST001 to 11111111 not CWS__001 for the Telstra handset for the SuperCID
Click to expand...
Click to collapse
Thanks ozjubb - makes sense - I will have a go at this during the week too. Perhaps see if I can modify the "One Click" script which implements the same procedure.
I'm the person that posted on whirlpool as ref'd above - and can confirm that the root worked OK as described on AusDroid on May 21 as linked above.
I'll also be scanning for bootloader news.

logularjason said:
Thanks ozjubb - makes sense - I will have a go at this during the week too. Perhaps see if I can modify the "One Click" script which implements the same procedure.
I'm the person that posted on whirlpool as ref'd above - and can confirm that the root worked OK as described on AusDroid on May 21 as linked above.
I'll also be scanning for bootloader news.
Click to expand...
Click to collapse
I have looked at the oneclick batch file, changes would be easy enough to make as it is only a couple of extra lines so it looks for the Telstra CID "TELST001".
I have now unlocked my bootloader through HTCDev as well.
EDIT:
Here is a link to a modified copy of the Spoof-CID.zip file that should work for Telstra handsets.
I haven't tested this as I had already unlocked etc before modifying the zip file.

[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

Am I Bricked?

Hello I have been working on unrooting my EVO 4G LTE the past couple of days and now find myself signed into XDA-Developers late night in panic mode
-I attempted to complete regaw_leinad's guide on unrooting but have been unsuccessful.
HTML:
http://forum.xda-developers.com/showthread.php?p=28136562
- I executed LazyPanda S-OFF for my EVO 4G LTE and it completed successfully but then sent my phone into a activation loop. I am new to the site so am unable to post to the thread for assistance as I continue to read of known issues and hopefully posting here will get me some quicker answers while I continue to read...
HTML:
http://forum.xda-developers.com/showthread.php?t=1737123&page=252
- I Attempted to run RegawMOD S-ON Writer and received message "Wrong Bootloader version. Can't Set S-ON."
- I then proceeded to contact sprint since my phone seemed to be dead in the water and I was able to get phone calls and text working thanks to the sprint representative who got me to the Mobile Directory Number(MDN) & MSID menu (Dial Pad ##443382#) changed to my 10 digit cell number. So at least I can call and text, but have no Internet or GPS. We attempted several times while on the call to 'Update Profile" but continued to receive the Error Code: 1233. The sprint folks advised me to go into a store to have the phone looked at to see what the problem is but obviously can't as it still displays ---LazyPanda--- under the bootloader and S-OFF. The sprint rep also asked if I had rooted my phone and I supplied the obvious answer of "No, what is that?"
I am currently running Stock w Goodies 2.18 ROM, & Build Number 2.13.651.1 and would appreciate any assistance or direction where to go from here to confirm if I am SOL.
Thanks
***UPDATE***
I found and ran the RegawMOD Bootloader Customizer to set the bootloader screen back to stock (LOCKED, S-ON, Boot message disclaimer gone), but I am still unable to flash a stock RUU? I have tried all 4 RUU's that are out there through "Charge Only" and "FASTBOOT USB" and continue to receive the Error 155?
At this point I am almost ready to visit a sprint store to have them look at the phone but I believe I still need to change back the 'Softare version' back to stock and I will be set.
Any assistance would be appreciated!

[Q] Is there stock recovery for a Rogers S One with RUU 1.84?

I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.

tykidd66 said:
I have a rooted S One that seems to have lost its root access and signal after OTA update from Bell - the phone was bought on eBay as an "unlocked sealed" item, which wasn't the case. I want to restore the phone to stock and SIM unlock it for use with Telus, but there's no 1.84 RUU for Rogers available. I just want to confirm I can't restore the phone to stock without the 1.84 RUU. Or, if there's an alternative to get it working again, what that alternative might be and where to start. Thanks for any help.
Click to expand...
Click to collapse
Post is a bit confusing. You talk about Bell, Rogers, and Telus all at once. Also, if you got an OTA update from Bell, you will only be able to execute an RUU that has an hboot version equal to or higher than your current one.
If you are looking for a more recent RUU than the ones posted on http://forum.xda-developers.com/showthread.php?t=1543588
then I suggest you send a private message to Football, the user who started that post. He helped me find newer Bell Mobility RUUs (which have since been posted to the thread).
Your other option is to do a bootloader downgrade (see the dev post on this, its a bit complicated), and then you can flash other radios from http://forum.xda-developers.com/showthread.php?t=1998270
If you dont want to downgrade your bootloader, you can always flash to a CM10 base (AOSP type) ROM, such as PAC Man, or Jelly Bam, etc. Then you can flash radios without having to downgrade.
Again, though this is all assuming that your true problem is with you baseband radio and now switching carriers has made your reception poor...
Also remember you will have to relock your bootloader before you execute an RUU, otherwise it wont take (that and a correct bootloader version)
AKToronto

Thanks for the info. The phone is a sim-unlocked Fido unit. It was running on Bell before the OTA update.
Here are the specs:
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Is the "build number" the RUU? I'll try Football, but do I need the Rogers (Fido) RUU?
Thanks.

you can not execute an rogers ruu on a bell phone, the cid wont match
there is an app on play who will display you the cid and the original network; like that you'll know exactly what phone do you have in hand
you just have to unlockit after and you will be able to useit in whatever network you want

Thanks. Ran CID getter and says it's ROGER001. So I've confirmed that I need a Rogers file. And I would like to unlock it, but from what I've read I cannot restore back to Rogers 1.70 because the unit has been updated to 1.84. I have read that if I can find a 1.84 Rogers file, I can use that to restore the unit. This is the next thing I need to confirm. I appreciate your help.

I think that is almost correct. You can change the CID to the Rogers one using the same technique as posted in the super Cid thread in the development section. Normally though you can't flash an older ruu as the hboot version can't be older. But You may also want to try posting a message in the bootloader downgrade thread that is stickied to n the development section. I think if you downgrade your bootloader and also do a minor hex edit to a partition you can flash an older RUU. I have downgraded my bootloader but haven't tried flashing an older ruu so I can't say for sure.
Sent from my HTC One S using xda premium

Thanks again. So I can assume the CID is already Rogers, yes? I don't want to change it. My hope is that I can use the All in One Toolkit (one of the sticky posts) to bring the phone back to stock and then SIM unlock it for use with Telus. If I run the Toolkit, and use cbetso's instructions from the "How to Return to Stock" post (after adding the stock recovery to the folder). If I locate the Rogers 1.84 RUU, can I run it without downgrading?

don't assume, your cid is rogers ROGER001, so there is absolutely no way your phone could download and execute an update from bell.
so I can not understand what has bell to do in this.
if you just want to use it on telus network, you just have to unlock it, you don't even need root for this. and the phone will work just fine.
the root is needed when you want to change ROM, radio, debloat and others.
one of the others will be tweaking the build.prop file to achieve maximum capacities of your 3g/4g desired network

Thanks - it's a difficult story to tell, really. It was a Rogers unit, SIM unlocked to work with Bell. It was on Bell's network for two months, and an OTA update caused major radio and reception problems. It will not keep a network signal anymore. I have tried other SIMs in the unit and it will not recognize them, nor start up with the "Enter Unlock Code" screen to SIM unlock it. It's my understanding that I need to return it to stock by finding the Rogers RUU file that matches the software version on the unit, which is 1.84. This is my very limited understanding of the issue, but it's what I've been able to figure out.

if it was a rogers device, and you did not change the CID, you get the ROGER001 cid with the app, your phone is still a rogers device
doesn't matter in which networks was used, for the two months before you get it, and by you after
as long the cid stays ROGER001, your phone will remain a rogers device, unlocked to be used in different networks.
so there is absolutely no way an OTA update, from bell or telus could be the source of your problems, because your phone will not download or execute an ota update from other networks
same for rogers ota update, as long the phone was unlocked, will not execute OTA updates, even the updates will be downloaded on the phone
your connection problem came from other reasons;
however it you want to return the phone to rogers stock, the key number is HBOOT version;
you can execute any RUU with HBOOT version higher or equal with your present version on the phone
if somehow you're on a very high version and you can not find the appropriate RUU, we can always downgrade RUU, check development section for tutorial
it's not very simple, but as long you're ok and you understand the steps, go for it, it is doable.
if you have root, you might try different radios before all above, or maybe a custom rom; just an ideea; as long the phone is not soft bricked or physically damaged, there is no reason a custom rom will not work

Thanks for the information. There seems to be other problems with the unit, including it won't delete all data after hard reset, it won't recognize other networks when other SIMs are put in, it has been upgraded past the 1.70 stock Rogers RUU. I wish I could get it figured out or I may have to sell it as is. Appreciate your help.

factory reset in fastboot didn't work?
means you're on some custom rom with non stock recovery?
have you tried to flash a stock recovery? any of them, whatever you'll find around here; there are no much difference in term of facilities between them;
then you should be able to restore phone to factory defaults
try find somewhere All in one kitt one S v1.0; there is stock recovery in it, and flashing is easy
in v1.1 there is no more stock recovery

donwload ruu or open up ruu..when it first starts go into your windows manager and in the link section delete what you have in that section like c:/program files and replace it with %temp% and it will find two encrypted folders with a big letter/digit name and they will show you what time they were opened . open them up and find rom.zip copy it to your desktop and then extract it somewhere safe .. in the folders in rom.zip you will see recovery_signed.img rename it recovery.img and flash it via hasoons tool kit provided in the development section..just in case you ever run into this again

Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.

tykidd66 said:
Thanks. Can I flash a stock recovery in the All in One Toolkit without having the proper RUU version I need? Will this allow me to factory reset the phone, and the radio issue is another unrelated problem? The unit is supposed to be SIM unlocked, but when I put another carrier's SIM in, I still have no radio and I do not see the screen that says "unrecognized SIM" with an "enter unlock code" option.
Click to expand...
Click to collapse
Not sure about your radio issue, that would require testing out different radios. You can do that on a higher hboot by trying AOSP ROMS and using the Radio flasher in the dev forums.
As for flashing stock recovery you can also just use the following link: http://loadbalancing.modaco.com/down...ery_signed.img
The stock recovery doesnt really change from RUU to RUU. You dont need a particular recovery to use a particular RUU, as far as I know.

Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?

tykidd66 said:
Thanks - you wanna take another look at that link? It didn't seem to be anything. Or do I need to change the extension?
Click to expand...
Click to collapse
http://loadbalancing.modaco.com/download.php?file=ville_recovery_signed.img
Try that. Sorry about the other link

I maybe miss it, but you never said what is the exact status of the phone right now;
it is booting? it is working on some network? at least partially like voice only? what ROM are you on? what HBOOT?

Hi there - thanks for getting back to me and asking. The phone seems to be booting normally and always has been. It is not able to recognize any new SIM card. It's a Rogers unit, and when I add my Telus SIM it does not go to the "Unrecognized SIM" screen, it actually registers the TELUS network for a moment, then the radio gives no signal.
How can I check the ROM, 'cause I have no idea. Is the HBOOT in these specs?
Android version: 4.0.3
HTC Sense version: 4.0
Software number: 1.84.631.9
HTC SDK API level: 4.11
HTC Extension version: HTCExtension_403_1_GA_4
Build number: 1.84.631.9 CL64348 release-keys
Thanks again.

for the Hboot version you have to reboot in fastboot
for recovery reboot into recovery
for the ROM version, once booted normaly you have to go into about phone > software
are you sure you have the right settings for Telus APN? for some reasons, the phone will not registered to network, if apn setting are wrong;
at least for me, which I'm opposite to you as I have a telus phone and using it in fido network, if I dont have Fido APN setted up, the phone does not register to network

[Q] HTC Sensation no network access

HTC Sensation 4G T-mobile. From USA, trying to make it work in Norway.
According to the previous owner it was SIM unlocked, but stopped working after an upgrade (which was the reason for passing it on to me....). When I got it it had S-ON, HBOOT 1.27, Android 4.0.3 ICS, HTC Sense 3.6. No bootloader or root access. Everything worked flawlessly, except calling: whenever I put my SIM I'd get a "your SIM does not allow connections to this network" error message, so I figured it had to do with the phone being simlocked to T-Mobile.
Then I tried numerous guides to obtain SIM unlock:
Made contact with T-Mobile to see if they could unlock the SIM, but I didn't meet their requirements.
Unlocked bootloader the official way. http://www.htcdev.com/bootloader/
Rooting done following this guide: http://theunlockr.com/2012/09/20/how-to-root-the-htc-sensation-on-hboot-version-1-27-0000/
Installed SuperSU https://play.google.com/store/apps/details?id=eu.chainfire.supersu (downloaded from the author's site)
Installed CWM http://www.clockworkmod.com/rommanager
Did the wire-trick to obtain S-OFF: http://unlimited.io/juopunutbear.htm
Ran this SIM unlocker: http://www.sieempi.eu/blog/2011/09/22/universal-sim-unlock-for-s-offed-htc-devices-536
Finally installed CyanogenMod 9.1
So I learned a lot, but basically didn't solve my original problem: When trying to call I get "Mobile Network Not Available" and when searching for networks it's "Unable to connect at this time" and asks me try again later.
My new specs are: Android 4.0.4, S-OFF, HBOOT 1.27.1111, Radio 11.23.3504.07_M2, OpenADSP-v02.6.0.2226.00.0131
Despite the guide stating it wouldn't work with HBOOT 1.27 I also tried this one, but running PG58DIAG.nbh expectedly returned error messages. They were "security fail" and "update fail".
The output of the "strings -n 8 /dev/block/mmcblk0p6" command shows "T-MOB010" under my IMEI number, so to me it seems likely it's still locked. However, the phone doesn't ask for any unlocking code except for the PIN.
Hope anybody on this forum is able to point me in new directions. Thankful for any and all input.

al_f said:
HTC Sensation 4G T-mobile. From USA, trying to make it work in Norway.
According to the previous owner it was SIM unlocked, but stopped working after an upgrade (which was the reason for passing it on to me....). When I got it it had S-ON, HBOOT 1.27, Android 4.0.3 ICS, HTC Sense 3.6. No bootloader or root access. Everything worked flawlessly, except calling: whenever I put my SIM I'd get a "your SIM does not allow connections to this network" error message, so I figured it had to do with the phone being simlocked to T-Mobile.
Then I tried numerous guides to obtain SIM unlock:
Made contact with T-Mobile to see if they could unlock the SIM, but I didn't meet their requirements.
Unlocked bootloader the official way. http://www.htcdev.com/bootloader/
Rooting done following this guide: http://theunlockr.com/2012/09/20/how-to-root-the-htc-sensation-on-hboot-version-1-27-0000/
Installed SuperSU https://play.google.com/store/apps/details?id=eu.chainfire.supersu (downloaded from the author's site)
Installed CWM http://www.clockworkmod.com/rommanager
Did the wire-trick to obtain S-OFF: http://unlimited.io/juopunutbear.htm
Ran this SIM unlocker: http://www.sieempi.eu/blog/2011/09/22/universal-sim-unlock-for-s-offed-htc-devices-536
Finally installed CyanogenMod 9.1
So I learned a lot, but basically didn't solve my original problem: When trying to call I get "Mobile Network Not Available" and when searching for networks it's "Unable to connect at this time" and asks me try again later.
My new specs are: Android 4.0.4, S-OFF, HBOOT 1.27.1111, Radio 11.23.3504.07_M2, OpenADSP-v02.6.0.2226.00.0131
Despite the guide stating it wouldn't work with HBOOT 1.27 I also tried this one, but running PG58DIAG.nbh expectedly returned error messages. They were "security fail" and "update fail".
The output of the "strings -n 8 /dev/block/mmcblk0p6" command shows "T-MOB010" under my IMEI number, so to me it seems likely it's still locked. However, the phone doesn't ask for any unlocking code except for the PIN.
Hope anybody on this forum is able to point me in new directions. Thankful for any and all input.
Click to expand...
Click to collapse
Try writing supercid to it before you try PG58DIAG.nbh.

nlooooo said:
Try writing supercid to it before you try PG58DIAG.nbh.
Click to expand...
Click to collapse
Well, I searched and found post #35 in this thread helpful.
Then I tried rebooting, but the problem persisted so I went for trying to run PG58DIAG.nbh again. Which seemingly was successful as it reported so, except I found no way of exiting the program. In the end I just removed the battery.
Now CyanogenMod was caught in a loop on reboot, so I rebooted to recovery and tried reinstalling. Lots of error messages and still stuck on startup screen. Now, what next?

al_f said:
Well, I searched and found post #35 in this thread helpful.
Then I tried rebooting, but the problem persisted so I went for trying to run PG58DIAG.nbh again. Which seemingly was successful as it reported so, except I found no way of exiting the program. In the end I just removed the battery.
Now CyanogenMod was caught in a loop on reboot, so I rebooted to recovery and tried reinstalling. Lots of error messages and still stuck on startup screen. Now, what next?
Click to expand...
Click to collapse
You found the right way to get supercid and, as far as I know, the only way to fully end the process with DIAG is to remove the battery.
Now try with a different recovery, for example 4ext, full wipe, and try some stock like rom like ARHD.

Still stuck
Thanks for helping out!
So I got 4ext Recovery Updater, the directly linked zip file. Flashed via fastboot:
Code:
fastboot flash recovery recovery.img
As instructed here I also downloaded and ran PG58IMG.zip, choosing the 3.32 version as that was similar to the firmware I had when I started.
Next I got ARHD 7.3 and installed it, wiping everything on the way. It went smoothly, except I got a little nervous when it stuck for 5 minutes + on the beats audio screen.
Then hopes got higher as the phone asked wich carrier I was using, actually offering mine as an alternative. Still no go, however. "Your SIM does not allow you to connect to this network".
Checking variables through "fastboot getvar cid" returns cid=11111111, but "adb shell" followed by "strings -n 8 /dev/block/mmcblk0p6" still shows the annoying "T-MOB010" below my IMEI number. I obviously need access to this block, to edit or remove it, but how?

Now go to dialer and type
*#*#4636#*#*
And see what is set as a network type (should be WCDMA prefered if it isn't set it).
If you still have problems check if your home network works on the right frequency with the ones available of your phone.
And it won't be bad to try another sim card.

nlooooo said:
Now go to dialer and type
*#*#4636#*#*
And see what is set as a network type (should be WCDMA prefered if it isn't set it).
If you still have problems check if your home network works on the right frequency with the ones available of your phone.
And it won't be bad to try another sim card.
Click to expand...
Click to collapse
Thanks again for providing answers, it's much appreciated!
But unfortunately these didn't solve the riddle either: Trying another SIM? Already did that, to no avail. Tried several settings, network and others, after *#*#4636#*#* (radio off / on inbetween).
Checked network frequencies, they should work (and according to previous owner the phone was working in Norway prior to some fatal update - I'd guess that was updating Android from 2.something the phone shipped with to the 4.0.3 on when I took over).
Now searching for ways to modify /dev/block/mmcblk0p6

Ok, now the last one, try flashing the newest firmware from here:
http://forum.xda-developers.com/showthread.php?t=1412618
or here
http://forum.xda-developers.com/showthread.php?t=1459767 (better one)
It will install the latest radio too, maybe that's the main reason.
EDIT: Check at ARHD thread, there's separate version for T-Mobile phones.

No signal - locked SIM
A lot of text coming, sorry! Let's recap: After trying many firmwares and ROMS, I'm now on ARHD 7.3 from this thread. I've tried the special one for T-Mobile too.
In bootloader currently these specs are given:
Code:
Firmware-3.33
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1100
RADIO-11.24A.3504.31_M
OpenADSP-v05.6.2226.00.0418
eMMC-boot
Jan 13 2012, 17:33:34
Output from adb shell "strings -n 8 /dev/block/mmcblk0p6":
Code:
[email protected]:/ # strings -n 8 /dev/block/mmcblk0p6
macaddr=D4:**:**:**:**:0E
sromrev=3
vendid=0x14e4
devid=0x432f
boardtype=0x4b9
boardrev=0x36
boardflags=0x200
xtalfreq=37400
pa0b0=5190,5190,5576
pa0b1=64229,64229,64172
pa0b2=65121,65121,65155
pa0itssit=62
pa0maxpwr=82
ofdmpo=0xCC888888
mcs2gpo0=0xCCCC
mcs2gpo1=0xCCCC
rssismf2g=0xa,0xa,0xa
rssismc2g=0xb,0xb,0xa
rssisav2g=0x3,0x3,0x3
rcal_flag=0x61
ccode=ALL
cctl=0x0
cckdigfilttype=0
ofdmdigfilttype=1
rxpo2g=0
boardnum=1
otpimagesize=182
hwhdr=0x05ffff031030031003100000
RAW1=80 32 fe 21 02 0c 00 22 2a 01 01 00 00 c5 0 e6 00 00 00 00 00 40 00 00 ff ff 80 00 00 00 00 00 00 00 00 00 00 c8 00 00 00 00 00 00 00 00 00 00 00 00 00 ff 20 04 D0 2 29 43 21 02 0c 00 22 04 00 20 00 5A
sd_gpout=0
sd_oobonly=1
rssi_offset=0
20110727
4109913031965
KC17********
SH17********
SH17********
KC17********
99HNA003-00
B6EA6213
4109913031965
PG5810000
D4206D0FD10E
2011/07/27
3550***********
T-MOB010
2A9A1B7R804050
83H00425-03
The culprit is of course the line following the IMEI number; "T-MOB010". The output of this command has stayed the same through all firmwares and ROMs I've tried.
Interestingly, a different CID is found with adb shell (same as found through various fastboot commands):
Code:
[email protected]:/ # getprop ro.cid
11111111
[email protected]:/ # getprop ro.mid
PG58*****
I used this thread to unlock SIM. I cannot use method 1 (I have a date above IMEI), so I tried method 2, running the PG58DIAG.nbh. It reported success, but I can not connect to network ("Your SIM does not allow you to connect to this network".
Next I tried sieempi's guide. I'm not sure if this bootloader report means success,
Code:
SIMLOCK
FAT32 init OK
Reading Config.dat [37]Bytes
Read MCCMNC file success
Open CID file fail
Get device IMEI success
IMEI checking...PASS!
Process done, reboot device?
but the problem surely persists. When starting my phone it asks for the SIM PIN, that's it. And everything except calling works.
While searching for ways to deal with the /dev/block/mmcblk0p6 this was the closest I got to anything, which seems way to complicated for me - not to mention that they're discussing a different phone entirely.
So I'm stumped. Any and all input still highly appreciated!

I have the same thing with string command (writen H3G_001 and I have supercid) do don't get bothered with that.
Your problem seems to be some hardware issue.

I also tried this method, step 3 b)
Code:
[email protected]:/ # sh /sdcard/simfinder.sh
Searching mmcblk0p7...
1|[email protected]:/ #
No output except changing my prompt to have a "1|" in front. I don't know what that means, and it disappears on running new commands.

Hooray!
Well, I let it all rest for a while, then tried with yet another SIM. And would ya believe it, now it works!
Interestingly, the phone also works with the SIM it (seemingly?) rejected in the first place. So while I'm happy to finally have a fully functioning Sensation, I don't really know which part of all the tricks I tried that made it work.
Nonetheless, hopefully my efforts will be of help to somebody!

woah, not so fast...
After successfully making one call, problem is back. WTF?
According to my provider here, those "SIM does not allow connection"-messages are only for SIM-locks. If this is correct, my phone must still be locked to T-Mobile. If so, hats off to them for creating a hard-to-crack-lock, but there gotta be something I didn't try?
Or is it possible that the lock is placed outside the phone, in the network? If so, how would that work - is the phone transmitting details like IMEI when calling?
Again, thankful for any and all input!

al_f said:
After successfully making one call, problem is back. WTF?
According to my provider here, those "SIM does not allow connection"-messages are only for SIM-locks. If this is correct, my phone must still be locked to T-Mobile. If so, hats off to them for creating a hard-to-crack-lock, but there gotta be something I didn't try?
Or is it possible that the lock is placed outside the phone, in the network? If so, how would that work - is the phone transmitting details like IMEI when calling?
Again, thankful for any and all input!
Click to expand...
Click to collapse
did you see this post from the unlock simcard thread?
http://forum.xda-developers.com/showthread.php?t=1232107&page=54 (post #531)

rzr86 said:
did you see this post from the unlock simcard thread?
http://forum.xda-developers.com/showthread.php?t=1232107&page=54 (post #531)
Click to expand...
Click to collapse
Thanks, yes I tried it (direct link to post), but maybe I overlooked something. It starts to get challenging to keep track of all the PG58's I've been running, but I'll give it another go!
Any particular reason why the guide says to get 3.32 not 3.33 - would it make sense to install some older stock 401 RUU first? And I have a feeling I should avoid those RUU's marked TMOUS as I expect them to keep the T-Mobile connection.

al_f said:
Thanks, yes I tried it (direct link to post), but maybe I overlooked something. It starts to get challenging to keep track of all the PG58's I've been running, but I'll give it another go!
Any particular reason why the guide says to get 3.32 not 3.33 - would it make sense to install some older stock 401 RUU first? And I have a feeling I should avoid those RUU's marked TMOUS as I expect them to keep the T-Mobile connection.
Click to expand...
Click to collapse
no there is no particular reason for the firmware version
maybe the guide was written before 3.33 fw get released

rzr86 said:
did you see this post from the unlock simcard thread?
http://forum.xda-developers.com/showpost.php?p=27813767&postcount=531 (edited link)
Click to expand...
Click to collapse
This guide solved my problem.
A little recap:
I have the 4ext recovery. After unsuccessful attempts with ARHD 7.3 I reinstalled Cyanogenmod 9.1 for pyramid. After this too proved unsuccesful I followed the above linked guide.
Download the 1.17 firmware for your device from the User Friendly Firmware thread.
Follow the instructions in the thread to flash the firmware.
So far, so good.
Remove the SD Card & get rid of the PG58IMG.zip & put PG58DIAG.nbh on your SD Card.
Reboot to the bootloader & clear S-58 data by selecting appropriate options.
Once data has been wiped, pull out the battery to power off the phone & exit from the diag.
Remove the SD Card & get rid of the PG58IMG.nbh.
Clear S58 data reportedly succeeded, but after removing battery and switching back on, volume down + power didn't work. Instead of going to bootloader menu, the phone consequently tried to start cyanogenmod and got stuck in a booting loop or just hang during startup. I had to remove the battery a couple of times before I was able to get back to bootloader.
It's not clearly stated in the guide, but I got the impression the phone shouldn't boot normally after DIAG, but go directly to those last steps:
Download the 3.32 firmware for your device from the User Friendly Firmware thread.
Follow the instructions in the thread to flash the firmware.
However it looks like it doesn't matter. I tried many ROMS in vain.
Then I followed the guide once more, making sure to use the Firmware 3.32 Universal (Non-TMOUS). Then trying again with ARHD 7.3 and calling finally worked.
Case closed

Epilogue
Well, my problem was solved for, like 15 hours, but now I'm back at the "Your sim card does not allow a connection to this network" error message.
Several other people have reported that same problem. Bingley's solution doesn't work for me.
iviarck's problem resembles mine more closely. Regardless of my settings for preferred network, they return to WCDMA preferred. My sim works in other phones.
Blocked IMEI's are mentioned in the thread, so I checked my IMEI at T-mobile's site. The message is clear: "Your device is blocked and will not work on T-Mobile’s network".
Then I checked with http://checkesnfree.com/ which shows the T-mobile block, but where it seems the phone is not reported stolen. I assume it means that the original owner didn't fulfill contractual payment. Back to check out T-Mob's FAQ: "I purchased this device from another party. How do I unblock it? Unfortunately, T-Mobile is only able to assist the party that financed the device or agreed to the annual service term with payment options or contract information."
Now, from this thread it would look possible to use the phone in Norway regardless of the block and it certainly was for at least a year, according to the previous owner.
I made the phone work with a variety of SIMs now, so I'm sure it's not a matter of SIM-lock - it looks like IMEI blocking made it across the Atlantic. I'll talk to my provider and hopefully there is some possibility of lifting the block.
Edit: My provider says to talk to T-Mobile. So I'm stuck in the loop...