Related
read in a german board, that someone mailed to vodafone about the upcoming update to get s-off.
VF answered that they dont know if they remove the locked bootloader in the upcoming updates.
so my question: is it tecnically possible for VF to switch s-on again if they are getting a s-off update from htc? would this be legal?
just asking because just received my branded sensation on friday and if the unbranded sensation is coming the next 2 weeks i could change it.
but i only would do this if there isnt any way for the vodafone branded version to get s-off.
hope u can get me
The answer to your question would be yes your carrier could switch you back to S-On with an OTA, or send out an OTA with a locked bootloader/refuse to send out an OTA with an unlocked bootloader.
I would think though that HTC would just release the unlocked bootloader update, on their website for us to flash ourselves through the Rom Update Utility.
It's also unclear how they are trying to work with the carriers so that we'll have nice, bloated, roms with unlcoked bootloaders, instead of HTC just releasing a cleaned up rom. WOn't matter anyway cause once we have # we're gonna get rid of anything we don't want anyway.
The ear piece speaker on my One S broke, and I'm sending it into repair. I bought my phone unbranded from Phones 4U. Currently, I have this latest RUU loaded up:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
I believe this RUU is from Three, because it added a load of Three bookmarks to my browser.
In HBOOT, it does say "Relocked", but it doesn't say "Tampered", which I gather is the best you can get after rooting.
Considering the phone should be unbranded, should I try loading the most recent stock HTC RUU? I'm just worried they're going to point that out and refuse to repair :/
id like to know this too as i have an unbranded uk one s and im using the same RUU
jimnastics said:
The ear piece speaker on my One S broke, and I'm sending it into repair. I bought my phone unbranded from Phones 4U. Currently, I have this latest RUU loaded up:
RUU_Ville_U_ICS_40_S_HTC_Europe_2.31.401.5_Radio_1.06es.50.02.31_10.09a.50.04L_release_275655_signed
I believe this RUU is from Three, because it added a load of Three bookmarks to my browser.
In HBOOT, it does say "Relocked", but it doesn't say "Tampered", which I gather is the best you can get after rooting.
Considering the phone should be unbranded, should I try loading the most recent stock HTC RUU? I'm just worried they're going to point that out and refuse to repair :/
Click to expand...
Click to collapse
I don't think you need to load a new RUU. Your problem is a hardware related so they shouldn't bother about the OS on the phone as it's not related to the problem and the OS is an official HTC one anyway..
When I swapped my HOS there was an unofficial ROM (plus I installed my own and the CID was an Orange one). An O2 guru sent it to a repair centre and they accepted the phone even with the development notice at startup..
Your phone is ok by software but not ok by hardware. I see no reason why to refuse it..
It don't matter, I have sent one of my phones back rooted and unlocked before 2 times for hardware problems,..
when I was on sprint rooted, unlocked, they run the RUU to make sure its not software related, then they repair what needs to be repaired.
I called them back to say why did you upgrade my hboot, they said "they put it back to manufactor default stock rom, sprint, tmobile, att, they run the RUU first on any phone.
I would run an RUU they will charge you if its unlocked as it breaks their warranty. MAKE SURE ITS LOCKED AND STOCK in uk.
Any EU RUU should do the trick ! If it was originally carrier branded and you cannot find RUU for that carrier, Just change CID to HTC__001 and run an unbranded EU RUU.
Relocking the bootloader is a must! It takes 10 seconds so dont take no risks !
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.
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Bubbled said:
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
Click to expand...
Click to collapse
Unfortunately the answers are no and no. JB is decent even on fully stock AT&T, you will just have to look the other way when scrolling through your app tray
I don't think the current root methods allow for the 3.18 build to gain root. Might be in the 2.20 boat all over again until someone can find a definite procedure.
soooooooooooooooooooooo lame. my rezound had viper rez rom and it was based off one x jb but had all the tweaks and stuff so right now its like a major downgrade lol
guess i'll cry and wait for the HTC One to come out later this month, since i only grabbed the one x cause it was literally 11 cents at walmart with a 14 day return and my rezound is acting up and randomly restarting/tanking battery!
sigh
thanks for the info though Groovy
Bubbled said:
Okay i just bought a brand new ATT HTC One X and out of the box it comes with 4.1.1 and is build 3.18 with the 2.14 hboot.
i have flashed htc phones before and so im not new to it.
HOWEVER! lol
I was looking over the forum (and as confusing as it is with the different versions of the htc one x/xl/s/whatever else ) i believe this is the correct forum.
I am completely stock and those are my build and hboot out of the box. I want to root/unlock BL but so far no luck with any of the exploits.
Anyone here successfully rooted a 3.18 one x? or could i flash an RUU for the 2.20 build? how would i flash without first being rooted/custom recovery?
sorry if seem noob questions, been browsing the forums and google/bing all day and can't find a straight answer.
Click to expand...
Click to collapse
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
lightflier said:
I had exact the same issue and trust me I tried everything I could find. Finally I used exploit v2.1.1 and then rooted with Revolution HD Root using TWRP 2.4.1.0...
Click to expand...
Click to collapse
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
iElvis said:
Try that and you'll get a brick. Those are tools/roms for the Tegra 3 One X.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
OK...
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Sent from my Nexus 7 using xda premium
panda_mode said:
AT&T version of the One X isn't officially supported by htcdev to unlock boot loader (which is why many needed to change cid). If people who have the AT&T version are s-on, relocked, RUUed to 2.20, and flashed ota, they cannot root/unlock boot loader unless an amazing dev creates an exploit
Click to expand...
Click to collapse
Damn that's annoying! If that were me I would sell my AT&T phone and with the cash buy an overseas One XL model with 32GB
juicejuice said:
I thought something like this would work:
1. HTCdev bootloader unlock
2. Flash custom recovery (TWRP)
3. Achieve SuperCID (can do this via TWRP adb?)
4. Run S-OFF procedure
Click to expand...
Click to collapse
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Sent from my VENOMized HoxL
area51avenger said:
At least 1 person had success with xfactor so he could try but if it doesn't work then he's sol
Click to expand...
Click to collapse
I suppose it doesn't hurt to try. Otherwise, I'd just take the phone back, if root/S-off, etc. is important to the OP. I assume 11 cents is a subsidized price. So no point in using up an upgrade on a phone that can't be modded, if he wants to get the HTC One when its released.
OP may also check to see if the store has any older stock with 2.20 firmware (or any previous firmware version except 3.18). Phones with 3.18 out of the box must be very new, so I wouldn't be surprised if they had some older stock also.
I returned the one x today. will be looking into the t-mobile version of the HTC One which they told me comes out friday the 22nd. being a new phone i know i wont be able to do any mods or anything for a while, but that won't take long with the awesome Devs we have here! All the other models of the One X were sold out, and im guessing that someone realized that the new firmware was Out of Box so picked em all up. only had 2-3 stores with one each so its possible. now all the new stores have the new firmware no big deal, i'd prefer an HTC DNA anyways, but we'll see what the One is all about.
redpoint73 said:
The AT&T CID is blocked within HTCDev.com. A unique situation, almost certainly directed by AT&T. Therefore, on AT&T version of the One X, you need at least temp root to change the CID, then you can unlock the bootloader.
No root/temp root on AT&T 3.18 = no bootloader unlock. It also means no S-off (since you need root to change the CID).
Click to expand...
Click to collapse
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Techinstein said:
I tried Xfactor and it said the cid for my device out of box 3.18 firmware 2.14 hboot was CID Cws__001.
Click to expand...
Click to collapse
Yes, the CID for AT&T is cws_001 on all of the previous firmware versions, as well. This hasn't changed. cws__001 is blocked on HTCDev.com.
So i have the key for my past bootloader unlock can i use it?
Enviado desde mi HTC One X usando Tapatalk 2
coldrazor said:
So i have the key for my past bootloader unlock can i use it?
Click to expand...
Click to collapse
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
redpoint73 said:
Yes.
If you were unlocked before, how did you get on the 3.18 RUU/OTA? Did you change your CID back to AT&T's CID? Or did you S-off.
If you are S-off, no need to unlock the bootloader.
Click to expand...
Click to collapse
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
exad said:
Yes, you still need to have the bootloader unlocked to write to recovery and some other stuff. I tested this myself.
Click to expand...
Click to collapse
Really? Kinda negates part of the purpose of having S-off, doesn't it?
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