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
Related
Hello all my fellow Canadians. The time has come to update those stinky 1.73 stock roms and uneash the power of your HOX! This tutorial will set you up with CleanROM w/ 1.85 rom. The phone feels twice as fast and all those pesky bugs are resolved. All ATT bloatware is removed and you are left with a de-branded, rooted, bootloader unlocked, super tweaked (FAST) HOX
Note: Before running any scripts make sure the adb.exe process is stopped and HTC sync is closed. This will prevent errors from occurring when running scripts.
STEP 1: UNLOCK BOOT LOADER AND RESET CID TO GENERIC VALUE
http://forum.xda-developers.com/showthread.php?t=1672284
STEP 2: RELOCK BOOT LOADER AND FLASH 1.85 RUU
-lock boot loader by using the command "fastboot oem lock" in cmd (refer to htcDEV steps for instructions if not sure how)
-download 1.85 RUU and flash to device
http://forum.xda-developers.com/showthread.php?t=1670238
STEP 3: UNLOCK 1.85 with standard HTCDev instructions procedure
STEP 4: [if links are broken, use links from here: http://forum.xda-developers.com/showpost.php?p=26540652&postcount=117 ]
-> Flash CWM Recovery -> http://forum.xda-developers.com/show....php?t=1671873
-> Download and copy SuperSU (CWM-SuperSU-v0.89.zip) to /sdcard from -> http://forum.xda-developers.com/show....php?t=1538053
-> Reboot into CWM Recovery and flash CWM-SuperSU-v0.89.zip
-> reboot phone
-> start SuperSU from app launcher and let it update the su binary
***OKAY: at this point your are defiantly going to hate all the ATT junk, boot screen, att bloatware, etc. Ill show you how to make it good!
STEP 5:
download CoolROM: http://forum.xda-developers.com/showthread.php?t=1655011
save it to your SD card and flash using CWM [follow instructions ^^^there^^^ then come back here when your done to setup ROGERS settings]
STEP 6:
enjoy the sexy nexus boot logo
STEP 7: SETUP ROGERS APN's and SMS center numbers (allows ATT rom to fully communicate with rogers servers!)
-go into your messanger and click the app switcher button(linked to menu key) and click settings. Click sms settings, and the input this number into call center number:
+17057969300
-Go into settings and click on mobile data (4th down) and click APN.
APN SETTINGS:
Name: Rogers
APN: ltemobile.apn
MMSC: http://mms.gprs.rogers.com
MMS Proxy: 10.128.1.69
MMS Port: 80
MCC: 302
MNC: 720
(EVERYTHING ELSE BLANK)
select the apn on the right and a green circle will fill in
STEP 8: YOUR DONE
do a little dance
PM me for any questions!
Thanks: [steps 1-4 were acquired from this thread: http://forum.xda-developers.com/showpost.php?p=26540652&postcount=117 ]
Helpful thread: http://forum.xda-developers.com/showthread.php?t=1671237
Thanks!!!!!
---------- Post added at 01:50 PM ---------- Previous post was at 01:17 PM ----------
Can you provide a little more detail on how to do step 1-4 i keep getting this error when i run the .bat
What do you mean by reset cid to generic value?
Just updated my Rogers phone. I did not have to enter the pan or mms setting. Worked out of the box and found the Rogers towers.
Sent from my HTC One X using XDA
Quick question for Step 1, my Rogers HOX is being rooted/BL unlocked, can I just run the SuperCID tools or I have to relock the BL before i run the tools?
Links 3 and 4 are broken.
I'm out for 2hours then I'll come on and clarify everything. All scripts are run with USB debugging enabled, adb.exe disabled, and htcsync disabled
I'll be on to fix the links in 2 hours. Sorry for the hold up.
If you are already unlocked, relock and use the tools in the procedure
Followed all instructions and cant get any data. It will let me input apns but it wont let me select the apn
sm625614 said:
Followed all instructions and cant get any data. It will let me input apns but it wont let me select the apn
Click to expand...
Click to collapse
The data apn should be selectable where as the mms auto applies
for some reason when I flash the CWM recovery in step 4, it doesn't work and it relocks my bootloader
EDIT: I manually installed it. thanks for this tutorial
Here is the LTE APN:
APN - ltemobile.apn
Proxy - <not set>
Port - <not set>
Username- <Not set>
Passwors - <not set>
Server < not set>
MMSC - http://mms.gprs.rogers.com
MMS - proxy 10.128.1.69
MMS - Port 80
MMS protocol - Wap 2.0
MCC - 302
MNC - 720
APN Type - *
Should be the only APN you need. There is also an lteintenret.apn with all the same settings but I don't know if it is any different or just an alias.
Haven't been able to get tethering to work with any of them.
Sh
---------- Post added at 10:33 PM ---------- Previous post was at 10:31 PM ----------
Could someone look at their Rogers APN settings that hasn't flashed the ATT rom yet? Interested to know what they are as it might be related to the tether issue I am facing.
spacemoneky said:
I'm out for 2hours then I'll come on and clarify everything. All scripts are run with USB debugging enabled, adb.exe disabled, and htcsync disabled
I'll be on to fix the links in 2 hours. Sorry for the hold up.
If you are already unlocked, relock and use the tools in the procedure
Click to expand...
Click to collapse
Does that apply to supercid spoof too? Since I understand it's required to relock the BL before flashing RUU but also want to know if it's necessary to relock to spoof the CID
Sent from my HTC One X
If links are broken
get links from step 3-4 from here http://forum.xda-developers.com/showpost.php?p=26540652&postcount=117
Elin28 said:
Does that apply to supercid spoof too? Since I understand it's required to relock the BL before flashing RUU but also want to know if it's necessary to relock to spoof the CID
Sent from my HTC One X
Click to expand...
Click to collapse
The only way i did it was by relocking and the spoofed and then locked again, flash 1.85, unlock with HTCDev, etc
MoeKz said:
What do you mean by reset cid to generic value?
Click to expand...
Click to collapse
It sets your cid to 1111111 so that you can flash to 1.85. without doing the spoof, the flashing wizard detects rogers and wont let you load the att rom.
did everything it says to do but when i try to re-unlock it doesnt seem to work, the token is accepted and it brings up the screen saying yes or no, when i say yes it wipes the phone but when i go back in to the BL it still says RELOCKED at the top hope im not stuck like this, will try and flash the ruu again and try re re unlocking
If you are having trouble unlocking do this:
-relock,even if already says relocked, (trust me). Then unlock using htcdev. There is a weird glitch to.some people and.you have to do.it a few times for it to.stick. it ok it will eventually work. (worked first time.for me)
Let me.know if you are successful!
spacemoneky said:
If you are having trouble unlocking do this:
-relock,even if already says relocked, (trust me). Then unlock using htcdev. There is a weird glitch to.some people and.you have to do.it a few times for it to.stick. it ok it will eventually work. (worked first time.for me)
Let me.know if you are successful!
Click to expand...
Click to collapse
that worked, weird i tried soooo many times i thought i was stuck! thank you very much!
Half tempted to go back to the standard stock Rogers RUU after going through this entire process and seeing how much is missing and can't be restored easily. So many fewer accounts that can be setup, stuff like Facebook for HTC Sense is gone and can't be installed...
Anyone got the APKs for some of the stuff that's missing?
Flashing superuser in clockwork is an unnecessary step as cleanrom is rooted
Sent from my HTC One X using Tapatalk 2
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.
I bought a One S for my Mom on eBay to replace her water-damaged S2 - the listing said factory sealed, unlocked, brand new.
Dropped Bell Canada SIM card in, worked well for 2 months.
After a Bell OTA update, phone will not maintain a signal.
Bell looked up IMEI, said the phone belonged to Fido and was unlocked and activated by Rogers.
Ran Root Checker to see if it was rooted - sure enough, it had been rooted and I have the "this device does not have proper root access".
So I've been forced to try and figure this out, and I'd like to restore the phone to stock - I've read cbetso's great "Restore to Stock" post and looked through the AIO toolkit, but I don't know which "RUU to run". Fido? Rogers? Bell? Do I even need it? Everyone's issue seems very personal and specific to their carrier / etc. and I'd like to restore it.
Thanks.
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
Telling by the software version it runs the Fido software. You would have to run a Fido RUU, but if you want to change it to unbranded HTC software you can change CID to HTC__001 and then run an unbranded RUU such as 2.31.401.5 (latest, Android 4.0.4 RUU)
usaff22 said:
Telling by the software version it runs the Fido software. You would have to run a Fido RUU, but if you want to change it to unbranded HTC software you can change CID to HTC__001 and then run an unbranded RUU such as 2.31.401.5 (latest, Android 4.0.4 RUU)
Click to expand...
Click to collapse
Thanks again. I have an unlock code for the device; my hope was to restore it back to the way it came from Fido and SIM unlock it for use with another carrier. I suppose I'll try the step-by-step process listed in the "restore" post I mentioned. After trying to figure this out for the past week, I truly appreciate the work of developers here in the forum.
So I've located an RUU for Rogers (which covers Fido in Canada, apparently) but it's for a 1.70 build. The one currently on the device, I believe is higher than that. I'd like to try the All in One Toolkit to bring the phone back to stock and then unlock it for use with Bell or 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) - can I run the 1.70 Rogers RUU without issues? Thanks for the advice!
tykidd66 said:
So I've located an RUU for Rogers (which covers Fido in Canada, apparently) but it's for a 1.70 build. The one currently on the device, I believe is higher than that. I'd like to try the All in One Toolkit to bring the phone back to stock and then unlock it for use with Bell or 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) - can I run the 1.70 Rogers RUU without issues? Thanks for the advice!
Click to expand...
Click to collapse
If you are on a higher software version than the RUU, unfortunately it's not possible unless you downgrade your HBOOT which is risky for people who are new to the whole unlock/root thing. If the software version is the same or less, go ahead.
usaff22 said:
If you are on a higher software version than the RUU, unfortunately it's not possible unless you downgrade your HBOOT which is risky for people who are new to the whole unlock/root thing. If the software version is the same or less, go ahead.
Click to expand...
Click to collapse
Thanks. I'm not new, I'm COMPLETELY new. Maybe I'll have to wait until the higher version come out for Rogers. Right now I have a virtually unusable phone, and although I don't know what I'm doing, I'd still like to try and get it back to stock. Can you point me in the direction of a good downgrade tutorial? I've looked around a bit but haven't seen anything I trust. Much appreciated.
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
I need some major help, good folks of XDA. I've purchased this HTC One S from a guy who got it from Fido; naturally it was locked to Fido. I was planning on giving it to my girlfriend who is with Telus. I used cellunlocker.net to unlock the phone to find out that it didnt work with Telus. It would pick up signal then lose signal, pick up signal and lose signal every 10 seconds or so. I thought if I put a custom ROM on it might get me signal so I unlocked bootloader, rooted and put Viper ROM on it but it turns out it still wouldn't pick up network on Telus. So I decided to try it on my network, Rogers, and it picks up network but only 2G!!! Now my One S has the stable CM10 on it with baseband 1.08ts.50.02.16_10.08e.50.04L, unlocked bootloader with s-on, hboot 1.06, radio - 0.16.31501s.02
Here are the solutions I have tried so far to this problem;
-Tried to install multiple RUU both with ROGER001 CID and Super CID:11111111 and I couldn't install any of the RUUs, kept getting Error 155 with Rogers RUU and Check CID errors with other RUUs.
-Used to have 1.13 hboot but downgraded to 1.06 so I could change basebands and everytime I flash a different baseband, nothing changes after reboot.
-There is a recent jellybean rogers ota update zip but I dont know how to install it
please someone help!!! Thank you in advance and even more if my problem ever gets solved
Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium
alltubetone said:
Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Just asking, why is this the wrong (forum) as you say cuz this forum handles all devices does it not and I don't see anything wrong with his post?
SuperCID lets you flash any RUU, that error is most likely down to the bootloader being unlocked so if you really want to run a RUU then you want SuperCID and the lock the bootloader then run the RUU and also before you start the RUU be in fastboot mode first.
Darknites said:
SuperCID lets you flash any RUU, that or is most likely down to the bootloader being unlocked so if you really want to run a RUU then you want SuperCID and the lock the bootloader then run the RUU and also before you start the RUU be in fastboot mode first.
Click to expand...
Click to collapse
I did fastboot oem lock before flashing and got the same results; rather frustrating
alltubetone said:
Wrong forum for this kind of question. Have you tried flashing the telus radio? Also modifying the build.prop with the telus settings might help. Odd that you're having that issue on Rogers since Fido is the same network. Sounds like someone may have sold you a dud...
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
is it possible for a dud phone to have only 2g working and not get 3g?
dpk0875 said:
I did fastboot oem lock before flashing and got the same results; rather frustrating
Click to expand...
Click to collapse
Try hex editing mmcblk0p23 .... There is a method here for flashing RUUs that is discussed in the development forum in the sticky for downgrading your bootloader.... Try the hex edit, and then lock and then flash.
You could also try flashing a different baseband radio. For Canada, I didnt get the best reception from 1.08. You can d/l new baseband radios either for your phones radio partition or for CM10 (which uses a different location). There is a thread with radios collected in them in the development section.
I would try flashing a different radio before the RUU... The RUUs will upgrade your bootloader and then you cant flash new radios and other partition on SENSE seperately (ie ROMS wont flash properly and you will need to fastboot the boot.img every time)...
Funny , I unlocked my Original Fido One S to use it on Wind and it works perefectly. It should work on Telus ...have you tried inputting telus apn and restarting the phone after?