Hi, guys.
I'm using a HOX AT&T with stock rom 1.85, and yes I did the deed, root, spoof CID and unlock bootloader, install TWRecovery. Now I live in Asia so no LTE here, and I don't like the ATT's bloatware at all, also I read some complaints about LTE radio constantly drains battery if not in coverage. Some flashing is in order, but before diving in I have some questions:
1./ Is the spoofed CID permanent? I mean now my HOX is 11111111 CID - like a retail/generic one's, what will happen if I flash a RUU from another operator? Does a RUU from AT&T make my phone's CID go back to before and I need to start the whole nine yards again?
2./ I understood flashing a stock rom will un-root the phone okay, but what about bootloader? A RUU flashing wont re-lock the bootloader, or will it?
3./ Like I said, I can't stand bloatware, in the roms section I saw this RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed and a newer RUU 2.29 Asia somewhere else, are those unbrand roms - like the ones come with retail/operator-free One XL?
4./ I saw warnings about this specific rom, 2.20 of AT&T, no root, new hboot... all basically spells trouble, but what about branded roms with higher version number like O2 DE 2.29 or Vodafone DE 2.33, are they kosher?
5./ AFAIK, Europe and Asia has no LTE capability, so if I flash a radio rom from European operators or Asia does it disable the LTE radio in my AT&T HOX?
That's all, thank you guys in advance.
6./ In the thread radio & RIL , I read that update 2.2x will replace HBOOT and make old radio not compatible, is it because new HBOOT resize the radio partition smaller? So if I flash a custom rom based on Asia RUU 2.29 for example (not the dreaded 2.20 ATT), my current HBOOT will be replaced by new HBOOT as well? With no S-OFF, we can not flash HBOOT so will I be stuck with the new HBOOT and therefore, new radio roms only?
Looking forward to hearing from HOXL gurus. Thanks.
linhldz said:
Hi, guys.
I'm using a HOX AT&T with stock rom 1.85, and yes I did the deed, root, spoof CID and unlock bootloader, install TWRecovery. Now I live in Asia so no LTE here, and I don't like the ATT's bloatware at all, also I read some complaints about LTE radio constantly drains battery if not in coverage. Some flashing is in order, but before diving in I have some questions:
1./ Is the spoofed CID permanent? I mean now my HOX is 11111111 CID - like a retail/generic one's, what will happen if I flash a RUU from another operator? Does a RUU from AT&T make my phone's CID go back to before and I need to start the whole nine yards again?
2./ I understood flashing a stock rom will un-root the phone okay, but what about bootloader? A RUU flashing wont re-lock the bootloader, or will it?
3./ Like I said, I can't stand bloatware, in the roms section I saw this RUU_EVITA_UL_ICS_40_S_hTC_Asia_WWE_2.23.707.2_Radio_0.19as.32.09.09_L_10.104b.32.25L_release_271654_signed and a newer RUU 2.29 Asia somewhere else, are those unbrand roms - like the ones come with retail/operator-free One XL?
4./ I saw warnings about this specific rom, 2.20 of AT&T, no root, new hboot... all basically spells trouble, but what about branded roms with higher version number like O2 DE 2.29 or Vodafone DE 2.33, are they kosher?
5./ AFAIK, Europe and Asia has no LTE capability, so if I flash a radio rom from European operators or Asia does it disable the LTE radio in my AT&T HOX?
That's all, thank you guys in advance.
Click to expand...
Click to collapse
1. Spoofed CID is permanent unless you go in and change it back. For all intents and purposes, it's permanent.
2. Actually to run an RUU, you must relock your bootloader or it will fail. As long as you have your unlock token or Super CID, you can re-unlocked your bootloader once you are done and flash SuperSU to get root back. Or just flash a pre-rooted stock ROM.
3. Not sure. Make sure to fully read the post. I have never run an RUU for a phone with an RUU from a different carrier. Again, make sure you read about that one.
4. You just don't want to run the 2.20 RUU for AT&T. It will make it so you can not flash radios at all and you must flash boot.img from adb or from Android terminal emulator. It is just the 2.20 RUU that will do this. A custom ROM will not, so no need to worry.
5. It will not disable LTE, but if you don't have an LTE APN in your phone it shouldn't be looking for LTE and you can also turn off the LTE radios on any non-AT&T ROM.
My recommendation after all of your questions would be to flash a pre-rooted stock ROM or a cleaned up debranded ROM (like Clean Rom, but there are more out there). Change the APN to what ever country you are in and do the *#*#4636#*#* thing to turn off your LTE radio. Again, the *#*#4634#*#* to turn off the radio will not work on a stock AT&T ROM.
Thank you, Butters. Still I've got one more question - added in the first post.
linhldz said:
Thank you, Butters. Still I've got one more question - added in the first post.
Click to expand...
Click to collapse
If you are flashing a custom ROM, you do not have to worry about your HBOOT being changed. It doesn't matter what the custom ROM is based on. You only have to worry about that with running an RUU (which is from HTC for a specific carrier).
If you have 1.85 on your phone, just keep a 1.85 RUU on your computer and flash away any ROM you want. If something gets messed up and you need to RUU, you'll always have that 1.85 RUU with the old hboot.
Running the 2.20 RUU, you will lose all ability to flash any radios, so you will be stuck with the AT&T 2.20 radio. Being that you are overseas, I would not recommend this because it may not (probably isn't) the best radio for your use case.
If you want a stock ROM, there are pre-rooted versions posted in Development that are flashable from TWRP. Easier then relocking the bootloader and running the RUU, and no threat of hboot changes (or having to research what was changed in the hboot).
Or just install a custom ROM. They are often based on recent firmware versions, but already de-bloated, and with awesome customizations added.
After all, if you want to run a stock RUU, why did you unlock the bootloader in the first place?
Thank guys, really appreciate. Just flashed CR5 with confidence, so far so good.
Early assessment: Quite smooth, the LTE problem with AT&T stock rom has disappeared, battery life improves greatly.
Related
Hello,
I'm running Trickdroid 8.1.0 with HBOOT-1.14, RADIO-1.06s, unlocked bootloader and SuperCID. Original my device is WWE Dutch.
I figured out there would basically two ways to update my radio to the newest 1.08ts from TMOUS 2.35.531 RUU.
1) I just run 'fastboot flash radio radio.img', but no that's not working with hboot-1.14 cause we get the 'signature fail error'
2) I flash stock recovery and then relock my bootloader (that steps are fine) and then run RUU_Ville_U_TMOUS_1.84.531.2 and then update to OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.7 to obtain the new RADIO-1.08ts. But no even that's not working, I get error 155 at the RUU cause I should need the right RUU. I thought I should be able to use TMOUS RUU cause I'm SuperCID but it's just not working.
So, it looks like there is absolute no way to update my radio to 1.08ts right?
Inferi0r said:
Hello,
I'm running Trickdroid 8.1.0 with HBOOT-1.14, RADIO-1.06s, unlocked bootloader and SuperCID. Original my device is WWE Dutch.
I figured out there would basically two ways to update my radio to the newest 1.08ts from TMOUS 2.35.531 RUU.
1) I just run 'fastboot flash radio radio.img', but no that's not working with hboot-1.14 cause we get the 'signature fail error'
2) I flash stock recovery and then relock my bootloader (that steps are fine) and then run RUU_Ville_U_TMOUS_1.84.531.2 and then update to OTA_Ville_U_ICS_40_S_TMOUS_2.35.531.7 to obtain the new RADIO-1.08ts. But no even that's not working, I get error 155 at the RUU cause I should need the right RUU. I thought I should be able to use TMOUS RUU cause I'm SuperCID but it's just not working.
So, it looks like there is absolute no way to update my radio to 1.08ts right?
Click to expand...
Click to collapse
The new Jelly Bean firmware will no doubt come with a new radio. Also I don't recommend using a different branded carrier's radio.
Sent from my locked, tampered ville
radio
uunderstanding 65 said:
The new Jelly Bean firmware will no t come with a new radio. Also I don't recommend using a different branded carrier's radio.
Sent from my locked, tampered ville
Click to expand...
Click to collapse
Hi, is my understanding correct that jb will improve the radio on my HTC one s so I should get better reception!?
Probably he means that we have to wait for the HTC Europa JB RUU, which will have the latest radio with all improvements by now.
So far I know there is no radio branding. Everyone is talking about it but I still almost sure there is no TMOUS or Europe specific Radio. Cause it wasnt there for my previous htc devices too
Sent from my HTC One S using xda premium
Inferi0r said:
Probably he means that we have to wait for the HTC Europa JB RUU, which will have the latest radio with all improvements by now.
So far I know there is no radio branding. Everyone is talking about it but I still almost sure there is no TMOUS or Europe specific Radio. Cause it wasnt there for my previous htc devices too
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Why do some RUUs have different radios than others? T-Mobile US is definitely different, they contain tweaks as far as I know that optimizes it for their frequencies etc.
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?
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
tlazarus said:
Before anyone tries to flame me, I've read all of the recent ICS and JB rom threads, as well as most of the generic question threads. I've unlocked, rooted, and flashed several roms before settling on CleanROM so I am not a complete noob. The master q&a thread doesn't cover RUUs much, and people aren't that interested in applying non rootable RUUs, so info on going back to stock on a newer or even older RUU doesn't seem to be widely available. My biggest concern is bricking my phone or losing major functionality, as some people using asian based roms seem to be having reboot and/or wifi issues.
1. Applying a different carriers S4 JB RUU is perfectly safe as long as I relock the boot loader, even with Super-CID.
I've seen conflicting reports of issues with RUUs when you have Super-CID, even with the original shipping RUU and a relocked boot loader. Can someone confirm that using RUUs is safe as long as the boot loader is relocked? What if it isn't relocked? Just an error or a bricked phone?
2. Once you unlock your phone on 1.14, you are stuck with that radio forever unless you apply an RUU or switch to Cyanogenmod.
3. Assuming RUUs are safe, applying a different carriers' RUU on my AT&T One X won't hurt anything. There may be apn issues, but otherwise everything should work (especially the camera and wifi).
Again, I understand that without root, I may not be able to add apns anyway. AT&T at least seems to have blocked the ability on their stock rom; not sure if other carriers do the same.
I really appreciate the help. I have searched, so this is more of a confirmation than anything else. Just trying to avoid bricking my phone and learn something new at the same time.
Tim
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s :
- you don't need to root your phone to add apn . I can add T-Mobile apn just fine after I flashed ruu.
- ruu.exe can't run if you bootloader is unlocked.
Sent from my HTC One X using XDA Premium HD app
tritran18518 said:
Im on hboot 1.14, firmware 2.20 att. Unlocked , rooted , flashed Rom. However , I had some problem then decided go back stock.
1. Downloaded ruu2.20 for att
2. Relock bootloader
3. Boot phone to bootloader mode then run ruu. Now my phone is stock
P/s : you don't need to root your phone to add apn .
Sent from my HTC One X using XDA Premium HD app
Click to expand...
Click to collapse
Thanks - that answers my RUU questions as far as going back to stock using RUUs. I assume the same applies to other carrier's RUUs, i.e. Telus/Asia. What about using an OTA on a phone with Super-CID?
redpoint73 said:
A factory reset or running the RUU will not change the CID.
SuperCID doesn't prevent you from getting the AT&T OTA (although root and unlocked bootloader will).
Click to expand...
Click to collapse
^^
jiggamanjb said:
^^
Click to expand...
Click to collapse
Okay, I think that answers my questions. No problems with using a RUU, AT&T or otherwise, as long as it is for the XL. Stuck on my current radio unless I use a RUU. And I need to relock my bootloader before applying a RUU, although I can unlock it after. I will lose root, however. Thanks!
Wondering, how I get back to stock for my girlfriends One Mini from T-Mobile Germany. The battery has quite strange problems and we want to give it to T-Mobile for service.
I think it won't be good, when the phone is with an International CID even if she bought it from T-Mobile with a T-Mobile CID, right? Flashing stock international would be no problem with S-Off (Just change CID and flash a stock international rom).
The main question is, can I change the CID to an international one, flash a stock rom, change CID back to T-Mobile one, make phone S-On and locked, flash stock recovery and update thorugh OTA? Will the phone get the T-Mobile OTA from then on?
Or do you think I should change the CID to an international one, flash stock, make it locked and s-on and give it to t-mobile?
Many questions but I hope I can get even one answer
Cheers,
Patrick
Klivarre said:
Wondering, how I get back to stock for my girlfriends One Mini from T-Mobile Germany. The battery has quite strange problems and we want to give it to T-Mobile for service.
I think it won't be good, when the phone is with an International CID even if she bought it from T-Mobile with a T-Mobile CID, right? Flashing stock international would be no problem with S-Off (Just change CID and flash a stock international rom).
The main question is, can I change the CID to an international one, flash a stock rom, change CID back to T-Mobile one, make phone S-On and locked, flash stock recovery and update thorugh OTA? Will the phone get the T-Mobile OTA from then on?
Or do you think I should change the CID to an international one, flash stock, make it locked and s-on and give it to t-mobile?
Many questions but I hope I can get even one answer
Cheers,
Patrick
Click to expand...
Click to collapse
Hi Patrick
I honestly don´t think you get an OTA update from T-mobile if you only change your cid.
For getting OTA´s the firmware and build number must match and also have to be T-mobile.
Even if you get an OTA it will fail through installation if both don´t match.
(Doesn´t matter T-mobile or not)
greet´s