Database Info

[Q] Reload 1.53 without unlock?

If this is covered somewhere else please post a link. I can't find one.
I've got a locked non-rooted phone and the 1.84 update fubar'd my radio. Is there a way that I can reflash the 1.53 ruu without unlocking my phone? That version worked fine for me (yeah, I know, why did I apply the update? I'm an update whore. I admit it).
I'd like to keep it as stock as possible in case I have to return the phone but I'd also like to try going back to 1.53 while (if) tmo fixes the problems with the 1.84 update.
I've got lots of experience flashing custom and stock roms on my Vibrant but I've only had the One for a couple of weeks.

I'm starting to think I might have to unlock, flash the ruu and relock.
Sound about right to those who have done this kind of dance?

If your talking about the bootloader then it needs to be locked and also a stock recovery, im about to do this once my RUU has finished downloading

Contact T-Mobile and let then know it borked you're radio. They'll have you contact technical support and they will walk you through a Master Reset. This will put you back on 1.53.
Sent from my HTC One S using XDA Premium

A master reset doesn't roll back the ROM. I've just discovered that first-hand.
After a MR I still have 1.84.x
On the other hand, it's a factory new 1.84.x except that my SD card contents are still there

i cant seem to find the stock US tmobile ruu 1.53. does anyone have it?

If you've got 1.84 the 1.53 ruu won't help you. It'll refuse to load

michaelh99 said:
If you've got 1.84 the 1.53 ruu won't help you. It'll refuse to load
Click to expand...
Click to collapse
well im using the 1.53 now but i want to get rid of the tampered thing on the bootloader or whatever. but the ruu i have is this 1.53.531.16_R2 CL47441 release-keys and someone said the STOCK ROM for original TMOUS is 1.53.531.16 CL47441 release-keys. notice there is a R2 in my ruu and it doesnt have that on the stock tmobile rom which is weird.

[Q] What's the difference between 1.85 and 1.88 RUU? Why is 1.88 disappearing?

Scrosler based cleanrom 4.0 off the 1.85 ruu, whereas the previous one was 1.88. I also noticed the Att one x resource Page no longer has a link for the 1.88 RUU. What gives? Did we discover that 1.88 is subpar? I thought everyone agreed 1.85 was junk?

thechilipepper said:
Scrosler based cleanrom 4.0 off the 1.85 ruu, whereas the previous one was 1.88. I also noticed the Att one x resource Page no longer has a link for the 1.88 RUU. What gives? Did we discover that 1.88 is subpar? I thought everyone agreed 1.85 was junk?
Click to expand...
Click to collapse
Scott decided to base Cleanrom on 1.85 because It's the official firmware from AT&T. He said there are less problems and fewer tweaks necessary to make his changes work by using the "official" firmware for the phone he develops on.

Just thought that I'd point out my battery life was MUCH better on 1.88 while using CR DE 2.3. I wish I could find that version to download again.

gunnyman said:
Scott decided to base Cleanrom on 1.85 because It's the official firmware from AT&T. He said there are less problems and fewer tweaks necessary to make his changes work by using the "official" firmware for the phone he develops on.
Click to expand...
Click to collapse
I see, thanks for the info. I figured that I might be able to find the answer in one of the later pages of the ROM's thread, but that it might also be heinously difficult to locate.
Did he also mention why he's decided to go with odex? Is it for the same reason?

Odex is wicked fast.

Ignore me

gunnyman said:
Odex is wicked fast.
Click to expand...
Click to collapse
I agree.

Never knew there was a link to the [email protected] 1.88 leak can someone post it
Sent from my HTC One X using Tapatalk 2

vdub804 said:
Never knew there was a link to the [email protected] 1.88 leak can someone post it
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
there ISN'T an AT&T 1.88. That firmware is for the Asian HOXL

vdub804 said:
Never knew there was a link to the [email protected] 1.88 leak can someone post it
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
You know, now that I think on it I don't actually know if a link was ever up. Is there an asian model that also uses S4? Answered right before me. And, weren't there grumblings about 1.85, or am I confusing myself..

gunnyman said:
there ISN'T an AT&T 1.88. That firmware is for the Asian HOXL
Click to expand...
Click to collapse
Thanks man I got excited for nothing
Sent from my HTC One X using Tapatalk 2

gunnyman said:
Scott decided to base Cleanrom on 1.85 because It's the official firmware from AT&T. He said there are less problems and fewer tweaks necessary to make his changes work by using the "official" firmware for the phone he develops on.
Click to expand...
Click to collapse
hey dude could you help me? i get a AT&T One XL i knew that the phone is rooted and unlocked i don't know what kind of method to unlocked the used (i received my phone and i just need to put my microSim on it)
i tried to update to the new version of the ICS 4.0.1 and HTC sense 4.1 without any success (yes its too sad) because when i tried to do it via OTA i get the message "we have determined that your phone may be running a modified version of its system software, etc, etc"
my android version is 4.0.4
HTC sense versio 4.0
Software Number 1.88.707.2
HTC SDK API level 4.11
HTC Extension Version 403_1_GA_4
i really appreciate your help
thanks in advance

fjej78 said:
i tried to update to the new version of the ICS 4.0.1 and HTC sense 4.1 without any success (yes its too sad) because when i tried to do it via OTA i get the message "we have determined that your phone may be running a modified version of its system software, etc, etc"
Click to expand...
Click to collapse
Can't be said enough: Don't ever install an OTA on a rooted Android device.
At a minimum, you will lose root. You may also be stuck in a bootloop, or you may get stuck on an unrootable firmware (depending on what they updated, and what holes they plugged).
If you are already rooted and bootloader unlocked, flash one of the stock rooted ROMs here under "Stock Rooted": http://forum.xda-developers.com/showthread.php?t=1671237
Not sure what 1.88 was updated to. But 2.23, 2.29, 2.33 are all very recent firmware builds (2.23 is Asian region for the carrier Singtel). Only difference is the carrier bloat, and you may need to manually enter the APN info for your carrier.

redpoint73 said:
Can't be said enough: Don't ever install an OTA on a rooted Android device.
At a minimum, you will lose root. You may also be stuck in a bootloop, or you may get stuck on an unrootable firmware (depending on what they updated, and what holes they plugged).
If you are already rooted and bootloader unlocked, flash one of the stock rooted ROMs here under "Stock Rooted": http://forum.xda-developers.com/showthread.php?t=1671237
Not sure what 1.88 was updated to. But 2.23, 2.29, 2.33 are all very recent firmware builds (2.23 is Asian region for the carrier Singtel). Only difference is the carrier bloat, and you may need to manually enter the APN info for your carrier.
Click to expand...
Click to collapse
Thanks for you quickly response, then if I remove the root of my phone, i will be able to update via OTA? I'm am a Rookie in this type of problems the only thing that i want its update my phone with the new version of ICS and HTC sense.
could you help me please?
Thanks in advance

fjej78 said:
Thanks for you quickly response, then if I remove the root of my phone, i will be able to update via OTA? I'm am a Rookie in this type of problems the only thing that i want its update my phone with the new version of ICS and HTC sense.
could you help me please?
Thanks in advance
Click to expand...
Click to collapse
If you are a noob, the best thing to do is read read read, and find out:
-What root and flashing ROMs means, and whether you will want them.
-What firmware number the new OTA is, and what has been changed.
People get all excited about a new OTA, without even knowing what has been changed. Newer firmwares include a new hboot, which patches holes which allowed flashing kernels and radios. You may not want to update.
Also, root and unlocked bootloader are both good things. There is really no reason to give them up, just for the latest firmware. If its just the newest firmware you want, as I already mentioned, there are stock rooted ROMs in the Development forum that you can flash, and probably in less steps than unrooting and installing the OTA.

redpoint73 said:
If you are a noob, the best thing to do is read read read, and find out:
-What root and flashing ROMs means, and whether you will want them.
-What firmware number the new OTA is, and what has been changed.
People get all excited about a new OTA, without even knowing what has been changed. Newer firmwares include a new hboot, which patches holes which allowed flashing kernels and radios. You may not want to update.
Also, root and unlocked bootloader are both good things. There is really no reason to give them up, just for the latest firmware. If its just the newest firmware you want, as I already mentioned, there are stock rooted ROMs in the Development forum that you can flash, and probably in less steps than unrooting and installing the OTA.
Click to expand...
Click to collapse
thanks and i started to read, in fact i tried to flashed my HOX with this stocked room "stock rooted 2.33.162.2 - odex/deodex and unsecure boot.img with init.d" using odex version but when the phone restarted the room wont boot then i think "i have a nice brick" could you help me i tried to post this problem in the develop section but i cant because i dont have he number of post to do it i dont know whats step i need to follow to bring from the death my phone

Did you factory reset and wipe cache and Dalvik before flashing?
Come to think of it, that's one reason that people like OTAs, they keep your user data (but that can often be a bad thing, as I've seen it mess up the performance for some people after the OTA). Also, wiping data is not really that big a deal. With Titanium Backup Pro, I'm up and running again in about 20 minutes after wiping data and flashing a new ROM.
Can you still get into hboot and recovery?

fjej78 said:
thanks and i started to read, in fact i tried to flashed my HOX with this stocked room "stock rooted 2.33.162.2 - odex/deodex and unsecure boot.img with init.d" using odex version but when the phone restarted the room wont boot then i think "i have a nice brick" could you help me i tried to post this problem in the develop section but i cant because i dont have he number of post to do it i dont know whats step i need to follow to bring from the death my phone
Click to expand...
Click to collapse
btw I dont know why if i connect the phone to the computer, HTCSync Detects the phone and shows me the information but the phone still death without boot

Also, what is the state of the phone. Do you have the white HTC screen at least?

fjej78 said:
thanks and i started to read, in fact i tried to flashed my HOX with this stocked room "stock rooted 2.33.162.2 - odex/deodex and unsecure boot.img with init.d" using odex version but when the phone restarted the room wont boot then i think "i have a nice brick" could you help me i tried to post this problem in the develop section but i cant because i dont have he number of post to do it i dont know whats step i need to follow to bring from the death my phone
Click to expand...
Click to collapse
redpoint73 said:
Did you factory reset and wipe cache and Dalvik before flashing?
Can you still get into hboot and recovery?
Click to expand...
Click to collapse
i cant get into hboot or recovery (i tried with power button +volume)
and i just install the zip from sdcard and the end i wipe the cache and dalvik and fixed the permissions and when the phones started just shows me the white screen of htc and a thin yellow bar in the right side like if something is loading and suddenly turns of and its all

Can't Get Back To Unrooted Stock No Matter What I Try

Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.

antny said:
Last week I went back to stock to familiarize myself with the process (which unfortunately brought my HBoot to 1.14). I also decided to try out TWRP when I rooted again. But before I could finish up I hit a button in TWRP that didn't need any confirmation. I don't remember which button because it did what it did quicker than I could notice. After that I couldn't even flash a ROM because I couldn't mount the sd card and whatever happened erased everything on my phone but I ended up figuring that out.Now I'm on ViperOneS but I can't unroot. I can't flash either of the RUU (Error 155) that are for T-Mobile US I even changed my CID to 11111111 but no dice(and yes I did flash the stock recovery and boot before relocking). The only thing I can do to get close to unrooted stock is flash the nandroid of a rooted stock ROM. Now I haven't mentioned every method I've tried, so before I start getting bashed for not searching, I want to mention that I've been at this for about 4 days and I have tried EVERYTHING that I've found on XDA and other forums but nothings worked. Is it my HBoot that prevents from doing anything? Should get another One S? Or should I just be thankful that I have a functioning phone?
Sorry for the long winded post but I wanted to make sure I put in as much detail as possible.
Click to expand...
Click to collapse
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?

dc211 said:
It's most likely your hboot that prevents the RUU's from working. You can only use a RUU that contain a hboot of 1.14 or higher.
Since your signature says HBoot: 1.14 & Radio: 1.08ts.50.02.16_10.08e.50.04L. I assume you updated via the T-mobile US OTA, is that correct?
What's interesting is that other hboots in the 1.14 family are listed as 1.14.0002 but the T-mobile OTA the hboot is labeled 1.14.0004. I haven't seen anyone state if this is will prevent "downgrading" to 1.14.002 and don't feel like finding out myself.
What RUU are you trying?
Click to expand...
Click to collapse
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium

antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.

I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
antny said:
Yeah it was the T-Mobile OTA, worst decision ever... I've tried both the 1.84 and 1.53 T-Mo RRU's multiple times and since I changed my CID I've thought of trying another carriers but I don't want to possibly make things worse.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S

dc211 said:
I feel your pain. I updated with the OTA that moved us to hboot 1.13 before anyone said they changed the security :crying:.
The 1.84 and 1.53 RUU's wouldn't work for sure. 1.84 has the 1.13 hboot and 1.53 has the 1.09 hboot. Your only hope of using an RUU at this time is one of the Europe RUU's. The good news is that you already moved to supercid so you got that out of the way.
The ones that might work are the ones labeled "RUU_Ville_U_ICE_40_S_Europe_2.xxxxxx"
Here you can get the 2.21 RUU I can't recall if it's the 4.0.4 based one though. Not really sure where to get the other ones as file factory changed their download rules.
http://www.mediafire.com/?xlklqrlljb2zt#r9489rkr82wh2
You might need to click the "mainver error fix" on the on the All-in-one tool kit to get them to work since you would be downgrading the rom.
And if you do use that RUU from mediafire you can go here and click the thanks button for SneakyGhost for putting up the RUU for you to download.
http://forum.xda-developers.com/showpost.php?p=32262143&postcount=153
Then go here and click the thanks button for Football since he's the only source of RUU's there is.
http://forum.xda-developers.com/showpost.php?p=23542379&postcount=1
Good luck.
Click to expand...
Click to collapse
I've thanked Football and gone to the link you provided but I don't get the whole Pt.1,2 and 3 thing. What am I supposed to do with that?
Edit: All good, just got it from the Dropbox link.... T-Mobile and Easy Tether don't mix.
fmedrano1977 said:
I've downgraded from 2.31 to 2.21, I know both have HBOOT 1.14 but not exactly sure if they have the exact identical numbers after the 1.14.
HTC One S
---------- Post added at 08:38 AM ---------- Previous post was at 08:34 AM ----------
2.21 RUU worked better for me than the T-Mobile stock Rom, it doesn't have w Wi-Fi calling do if that's a must for you only hope is to wait for the T-Mobile 2.35 RUU to be released.
HTC One S
Click to expand...
Click to collapse
I don't really care about wifi calling, cool feature but I hardly use it. Is it 4.0.4 and Sense 4.1 though? It wouldnt stop me from using it if it wasn't but I'm just curious haha.

4.0.4 and Sense 4.0
HTC One S

fmedrano1977 said:
4.0.4 and Sense 4.0
HTC One S
Click to expand...
Click to collapse
Cool Cool Cool thanks

Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium

antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Glad it worked out for you.

antny said:
Ah! Great success. I'm now running the European 2.21 RUU and it's great. Thanks again guys. Hopefully if someone's in the same position as I was they'll find this useful.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S

Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?

DoogleDood said:
Yes! Thank you. This seems to be what I'm looking for. You can see the question I posted recently about this similar issue. But I also don't understand the part 1, 2, and 3 thing. Help?
Click to expand...
Click to collapse
What are you trying to do?
HTC One S

Nevermind I got it! I wasn't sure if the 3 "parts" of the EU RUU needed to be combined or... what. But upon extracting I found the full file.

fmedrano1977 said:
One last thing I did after installing that RUU was edit the build.prop to match some lines from the T-Mobile one:
ro.ril.hsdpa.category=24
ro.ril.hsupa.category=6
ro.ril.hsxpa=4
ro.ril.fast.dormancy.rule=2
ro.ril.radio.svn=1
Make sure those match, these have given me the fastest DL speeds.
HTC One S
Click to expand...
Click to collapse
Why thank you sir.

antny said:
Why thank you sir.
Click to expand...
Click to collapse
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!

johnyguy said:
Please someone help me I just flashed axiom rom wifif won't work I tryd other roms too, wifi won't work how can I fix this ??
Do I need to flash a RUU I am new to this. I had th latest tmo update before I rooted the phone people says that's why wifi won't work in other thread.
Please help me fix this !!!
Click to expand...
Click to collapse
I'm honestly not to sure on how to fix this. I've searched it before I went back to stock (going back to stock is a definite fix) and couldn't find much on it. I'm sure something has developed from it by now though. Actually :: navigates to another tab:: http://forum.xda-developers.com/showthread.php?t=1900644 if it's compatible with your ROM, this kernel claims to have a fix for wifi and sound (I don't know what the sound issue is all about) but try that, it might work. But most importantly search, read, search and read some more, especially since you're new to this, I've rooted many phones and I still had problems with the One S. Good luck!

Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402

sylvestk said:
Found RUU 2.35 and finally got my phone back to stock. I posted info here:
http://forum.xda-developers.com/showthread.php?t=1941402
Click to expand...
Click to collapse
That release gives you the no data when screen is off issue.
HTC One S

[Q] can i get JB firmware with this CID ?

hi , sorry for the noob question but i was wondering if with this cid was possible to get JB firmware
im from mexico and my hboot is 1.14 my htc one x (evita) cingular_us is unlocked and rooted
im on cleanrom 5.0 final
sense 4.1
android ver . 4.0.4
based on 2.20.502.7 CL79936 release keys
radio 0.19as.32.09.11_2_10.105.32.25L

alex2693836 said:
hi , sorry for the noob question but i was wondering if with this cid was possible to get JB firmware
Click to expand...
Click to collapse
Now, someone feel free to correct me. I do believe to get the JB OTA update, you'll have to RUU back to stock when you know the update has been pushed out. You're CID shouldn't matter in getting updates.

Myrder said:
Now, someone feel free to correct me. I do believe to get the JB OTA update, you'll have to RUU back to stock when you know the update has been pushed out. You're CID shouldn't matter in getting updates.
Click to expand...
Click to collapse
and if i flash the firmware of the maximus rom , can i flash it ?
and i have TWRP 2.3.1.0 recovery this works too , right?

Myrder said:
Now, someone feel free to correct me. I do believe to get the JB OTA update, you'll have to RUU back to stock when you know the update has been pushed out. You're CID shouldn't matter in getting updates.
Click to expand...
Click to collapse
Probably correct. Root will either prevent you from getting the OTA notification altogether, or make the install fail (possibly even putting you into a bootloop, or stuck on the bootscreen). Likewise, unlocked bootloader will prevent the OTA from installing.
Moreover, I don't think the OP will get the OTA, since the phone is the US version, and not in the US. Probably need to download the RUU to get it at all.
And also, I would advise not installing any new OTA or RUU until folks on here have sorted out what it means to hboot, root, etc. They have plugged the root exploits for every firmware version to date, so I don't expect JB to be any different. Plus, I'll bet the JB firmware will be posted here on Development, in a safe, recovery-flashable, pre-rooted form. And probably soon after the OTA starts to hit. Maybe even before the OTA, if it gets leaked.

redpoint73 said:
Probably correct. Root will either prevent you from getting the OTA notification altogether, or make the install fail (possibly even putting you into a bootloop, or stuck on the bootscreen). Likewise, unlocked bootloader will prevent the OTA from installing.
Moreover, I don't think the OP will get the OTA, since the phone is the US version, and not in the US. Probably need to download the RUU to get it at all.
And also, I would advise not installing any OTA or RUU until folks on here have sorted out what it means to hboot, root, etc. They have plugged the root exploits for every firmware version to date, so I don't expect JB to be any different. Plus, I'll bet the JB firmware will be posted here on Development, in a safe, recovery-flashable, pre-rooted form. And probably soon after the OTA starts to hit. Maybe even before the OTA, if it gets leaked.
Click to expand...
Click to collapse
so that means i cant flash it ? or the phonw will not suport the firmware , sorry for my english :$$

alex2693836 said:
and if i flash the firmware of the maximus rom , can i flash it ?
Click to expand...
Click to collapse
That is definitely not ok. Maximus is for the international One X (Tegra3 version). Completely different hardware. ROM won't work, and you might brick your phone.
Stay in the One X/XL forums that say "AT&T".
http://forum.xda-developers.com/forumdisplay.php?f=1538
Also, just so you kow, JB has not started going out for our version of the One X. Only for the international version.

If there isn't a RUU for my phone, will it be possible for me to get the OTA update whenever it comes?
I have a backup of my stock rom, if I flash back to that when it's out will it be possible?

area51avenger said:
If there isn't a RUU for my phone, will it be possible for me to get the OTA update whenever it comes?
I have a backup of my stock rom, if I flash back to that when it's out will it be possible?
Click to expand...
Click to collapse
Stock ROM, and unrooted should be OK. But you will need to relock the bootloader too.
But I'd still just wait for the ROM to be posted in Development in a pre-rooted form, and just flash from recovery. Since you are on Telus, you will still be able to unlock the bootloader and root again (after an OTA). But why hassle with all the locking of the bootloader, returning to stock, etc.? JB will probably be posted here before you would get it OTA.
And for those on AT&T, I would definitely advise against accepting any OTA. Too many people rushed willy-nilly to accept the 2.20 OTA, then were on here complaining that they could no longer root (which for us also means no unlocked bootloader and no custom ROMs).

redpoint73 said:
That is definitely not ok. Maximus is for the international One X (Tegra3 version). Completely different hardware. ROM won't work, and you might brick your phone.
Stay in the One X/XL forums that say "AT&T".
http://forum.xda-developers.com/forumdisplay.php?f=1538
Also, just so you kow, JB has not started going out for our version of the One X. Only for the international version.
Click to expand...
Click to collapse
thanks man for real
and other thing , do you know when is the release for the one x at&t ?
n.n

alex2693836 said:
thanks man for real
and other thing , do you know when is the release for the one x at&t ?
n.n
Click to expand...
Click to collapse
No problem. Be sure to click the "Thanks" button for any posts you found helpful.
No word yet on JB release date for AT&T. Some folks are speculating November or December. But those are just guesses.

redpoint73 said:
No problem. Be sure to click the "Thanks" button for any posts you found helpful.
No word yet on JB release date for AT&T. Some folks are speculating November or December. But those are just guesses.
Click to expand...
Click to collapse
I've been told last week of Nov to the first week of Dec. But then again, its all rumors.
Sent from my One X using xda app-developers app

[Q] Help me please

Ok, so I have a HTC ONE X and i've had it since September and I have never gotten the 4.0.4 update. I contacted my provider (AT&T), they told me that they made the update available over the air. I went to my Settings app and clicked Check for Updates and after about a minute it went back to the same screen. I then contacted HTC Customer Support and the guy told me that they never made it available OTA. I'm confused. Is there something wrong with my phone? Help!?!?!

acord10 said:
Ok, so I have a HTC ONE X and i've had it since September and I have never gotten the 4.0.4 update. I contacted my provider (AT&T), they told me that they made the update available over the air. I went to my Settings app and clicked Check for Updates and after about a minute it went back to the same screen. I then contacted HTC Customer Support and the guy told me that they never made it available OTA. I'm confused. Is there something wrong with my phone? Help!?!?!
Click to expand...
Click to collapse
Att sent it ota....though you might be able to do it manually.... Don't talk to HTC employees about software its a random response every tome nothing is consistent....I do recommend rooting it and flashing maybe just a stock rooted Rom if that's what you like

omario8484 said:
Att sent it ota....though you might be able to do it manually.... Don't talk to HTC employees about software its a random response every tome nothing is consistent....I do recommend rooting it and flashing maybe just a stock rooted Rom if that's what you like
Click to expand...
Click to collapse
How can I get it to download OTA?

acord10 said:
How can I get it to download OTA?
Click to expand...
Click to collapse
Deleted

ronnie498 said:
Deleted
Click to expand...
Click to collapse
huh?

So you are on the 1.85 firmware?
If you have any desire to root, flash custom ROMs, etc., my advice would be to not update, and root the phone now. The 2.20 firmware includes an updated 1.14 hboot which plugs the exploits by which boot.img and radios can be flashed in recovery. This means that flashing ROMs takes extra steps of extracting boot.img from the ROM and flashing it over fastboot. You can't flash radios at all on the new hboot (with the exception of CM10 radios). People are actually downgrading the hboot, so they don't have to deal with these things.
Once rooted and bootloader unlocked, you can just flash any ROM you want, including stock rooted 2.20 or newer versions firmwares.
If you still want to upgrade the official way, and can't get the OTA, you can flash the RUU. It will wipe user data, but IMO this is a better cleaner way to update than OTA, anyway.

here is the ota http://fotadl.htc.com/OTA_EVITA_UL_...2.7-1.85.502.3_R2_releasenin45grzkfswb95v.zip
this method might let you manually update [How-To] Update devices via the OTA .zip