Hello folks, sorry for the dumb questions but this is new for me. I have HTC One X (AT&T) phone, bought in USA. This is my first android phone and I barely know android as a software. I unlocked the phone buying an unlock code from ebay and I am using the phone on another carrier. My question is, how can i manually update my phone (what is the newest update?) since AT&T is not a carrier in my country and I cannot update automatically.
At the moment my software information are:
Android version 4.0.3
HTC Sense version 4.0
Software number 1.85.502.3 710RD
Kernel version 3.0.8-01155-gca24d1eroo[email protected] # SMP PREEMPT (why is there root in the kernel version, my phone has never been rooted?)
Build number 1.85.502.3_R2 CL63811 release-keys
Doing this manual update if possible will the phone be locked to AT&T again, or my phone will remain unlocked?
I'm sorry for my bad english and sorry if there is already a question like this (I watched the noob video and did use the search button)
Thank you in advance
If you ever want to root or flash custom ROMs or other mods, I would advise not installing the latest (2.20) version AT&T firmware. Installing the official 2.20 firmware updates the bootloader, which plugs the holes by which kernels and radios can be flashed from recovery.
If you want root, I would root on 1.85, SuperCID, and unlock bootloader. Then you can install any firmware you want, including stock rooted versions that are more up to date than 2.20.
If you still want to install the 2.20 firmware, you can download the RUU (ROM updated utility) from HTC and run it on a PC, with the phone connected via USB. The phone should remain SIM unlocked after running the RUU. But RUU will wipe your data partition (but not the internal SD).
A lot of this may be over your head, so this may help: http://forum.xda-developers.com/showthread.php?t=1784459
redpoint73 said:
If you ever want to root or flash custom ROMs or other mods, I would advise not installing the latest (2.20) version AT&T firmware. Installing the official 2.20 firmware updates the bootloader, which plugs the holes by which kernels and radios can be flashed from recovery.
If you want root, I would root on 1.85, SuperCID, and unlock bootloader. Then you can install any firmware you want, including stock rooted versions that are more up to date than 2.20.
If you still want to install the 2.20 firmware, you can download the RUU (ROM updated utility) from HTC and run it on a PC, with the phone connected via USB. The phone should remain SIM unlocked after running the RUU. But RUU will wipe your data partition (but not the internal SD).
A lot of this may be over your head, so this may help: http://forum.xda-developers.com/showthread.php?t=1784459
Click to expand...
Click to collapse
Thank you redpoint73 for your answer, I will follow your advice and will root it on 1.85.
I suppose what I should do first is rooting my phone following this guide: http://forum.xda-developers.com/showthread.php?t=1644167.
Than I should do this: http://forum.xda-developers.com/showthread.php?t=1672284
Please correct me if I am mistaken
After doing all of that which firmware do you suggest or stock rooted version, or its just matter of taste? Now again the same question will I lose my SIM-unlock after rooting mt phone?
StoleMacuk said:
Thank you redpoint73 for your answer, I will follow your advice and will root it on 1.85.
I suppose what I should do first is rooting my phone following this guide: http://forum.xda-developers.com/showthread.php?t=1644167.
Than I should do this: http://forum.xda-developers.com/showthread.php?t=1672284
Please correct me if I am mistaken
After doing all of that which firmware do you suggest or stock rooted version, or its just matter of taste? Now again the same question will I lose my SIM-unlock after rooting mt phone?
Click to expand...
Click to collapse
The root method you linked is actually for 1.73. You want to use this one for 1.85: http://forum.xda-developers.com/showthread.php?t=1709296
The SuperCID method you linked is correct.
ROM/firmware is very much a matter of taste, and what features you are looking for. If you want stock, you can install the stock rooted 2.20 AT&T firmware in the Development forum (after unlocking the bootloader and installing TWRP). If you want something based on stock, but with cool added features and customizations, look at ViperXL, CleanROM, or Nocturnal LE. But that doesn't mean that any of the other ROMs are not also great. And that doesn't even mention the more "vanilla" (no HTC Sense) Android experience you can get from AOSP based ROMs, and their variants.
The differences and benefits of each are simply too extensive to discuss here. Just start looking at the ROMs and see what looks interesting to you.
Take a look at my index to see all the resources in an organized list:
http://forum.xda-developers.com/showthread.php?t=1671237
redpoint73 said:
The root method you linked is actually for 1.73. You want to use this one for 1.85: http://forum.xda-developers.com/showthread.php?t=1709296
The SuperCID method you linked is correct.
ROM/firmware is very much a matter of taste, and what features you are looking for. If you want stock, you can install the stock rooted 2.20 AT&T firmware in the Development forum (after unlocking the bootloader and installing TWRP). If you want something based on stock, but with cool added features and customizations, look at ViperXL, CleanROM, or Nocturnal LE. But that doesn't mean that any of the other ROMs are not also great. And that doesn't even mention the more "vanilla" (no HTC Sense) Android experience you can get from AOSP based ROMs, and their variants.
The differences and benefits of each are simply too extensive to discuss here. Just start looking at the ROMs and see what looks interesting to you.
Take a look at my index to see all the resources in an organized list:
http://forum.xda-developers.com/showthread.php?t=1671237
Click to expand...
Click to collapse
I have a doubt. As I'm no from USA, I'll have no option to update the firmware over the air. How must I proceed in this part of the manual method?
Won't I have any issues with this?
Thank you guys in advance...
galitore said:
How must I proceed in this part of the manual method?
Click to expand...
Click to collapse
My advice? Stop now. If, in fact, "This is my first android phone and I barely know android as a software," you're not ready to root.
You need to spend the next week (at least) reading and searching and reading some more. Don't come back until you can answer the following questions:
1. What does "rooting" mean, what exactly does it do to your phone?
2. What are you doing when you unlock the bootloader?
3. What's the difference between stock and custom recovery, and stock and custom ROMs?
Once you feel like you understand all this, you're ready to proceed. If you push forward now, you'll almost certain to get into trouble that you won't be able to get out of without extensive help.
iElvis said:
My advice? Stop now. If, in fact, "This is my first android phone and I barely know android as a software," you're not ready to root.
You need to spend the next week (at least) reading and searching and reading some more. Don't come back until you can answer the following questions:
1. What does "rooting" mean, what exactly does it do to your phone?
2. What are you doing when you unlock the bootloader?
3. What's the difference between stock and custom recovery, and stock and custom ROMs?
Once you feel like you understand all this, you're ready to proceed. If you push forward now, you'll almost certain to get into trouble that you won't be able to get out of without extensive help.
Click to expand...
Click to collapse
Hi iElvis,
actually it wasn`t me who said "This is my first android phone and I barely know android as a software"... it was another member.
I had an Motorola Atrix 4G which I rooted a coupe of times, but this one was made for my country market, differently than my HOX, that is at&t. But in one thing you`re right. I have not much experience with HOX. That`s true...
My question was regarding the part of the manual process which needs a communication between at&t and my cellphone. In this case I wouldn`t find any upgrade option to accept or deny. So i don`t know what would happen in this case... does anyone know?!?!
galitore said:
Hi iElvis,
actually it wasn`t me who said "This is my first android phone and I barely know android as a software"... it was another member.
I had an Motorola Atrix 4G which I rooted a coupe of times, but this one was made for my country market, differently than my HOX, that is at&t. But in one thing you`re right. I have not much experience with HOX. That`s true...
My question was regarding the part of the manual process which needs a communication between at&t and my cellphone. In this case I wouldn`t find any upgrade option to accept or deny. So i don`t know what would happen in this case... does anyone know?!?!
Click to expand...
Click to collapse
Whoops! Sorry about that.
As far as I know, the only way is to flash a custom rom with the base you want, or to run the RUU for that base, which will leave you relocked and unrooted.
Related
Hi!
First i want to say that i know that there must be other threads about this problem but my lack of knowledge in these matters has made it very difficult to actually know what to look for.
I have a htc Sensation, which is branded (for an operator called the three).
My goal is in the current situation to try to get the original version of the HTC Sense. The version you get on a non-branded version of HTC Sensation.
Later I am thinking about getting CM7, but that is not relevant here
When i started to look into how to proceed I found that I know very little about these things.
And so I turn to you for help.
My first question is: Can you use HTC's official method to unlock the bootloader on a branded phone? I have software number 1.45.771.4 (which is 2.3.4) but on HTC's website it says that you should have 1.45.401.2.
If not, what is the next best way to unlock the bootloader?
My second question is: Can you somehow get the original version of the HTC Sense? I do not mean a custom version of the original, but the actual original? Is there any relevant difference?
My third and final question is: How do I install the original version of the HTC Sense on my phone?
Hope I have explained well enough and that someone has the desire to help me with my small troubles
/Jonathan Sterner
i uses this thread to debrand my vodafone device (it is rooted via revoltionary tools) http://forum.xda-developers.com/showthread.php?t=1193033
Sent from my Sensation using XDA App
Maybe i should clarify that i think it is kind of scary to use unofficial methods and i would like to find a way that are as "Safe" as possible.
I know that "Safe" may have little to do with the method being official or not but i would first like to explore the official ways before turning to the unofficial ones simply because i think that they are scary.
The ONLY way to debrand is:
1. S-OFF
2. Write the Super CID to your phone
3. Flash an unbranded ROM to your phone
This is easily done with the Revolutionary method, and is 100% reversible should you need to return the phone
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!
I'm used to samsung so please bear with me...
I just came across an at&t one x that is running 1.85 with the hboot 1.9.000
I am kind of confused as to how to go about rooting/unlocking (if possible) this phone
it seems the xfactor/motochopper methods of rooting (which are in the noob friendly toolkit) are not available for this firmware version. All I see is this method http://forum.xda-developers.com/showthread.php?t=1709296
Most importantly, as I profoundly despise sense, I just want to unlock the boot loader, put a custom recovery on and get some Cm 10.1 on here.
I have read methods which require some hex editing, changing the cid to 111111111, etc...
My question is what is the best way to get a custom recovery on this phone now, as some of these methods seem really old (2012)
i'm just confused because it seems i have a pretty old firmware version and i don't want to break anything.
Oogy said:
I'm used to samsung so please bear with me...
I just came across an at&t one x that is running 1.85 with the hboot 1.9.000
I am kind of confused as to how to go about rooting/unlocking (if possible) this phone
it seems the xfactor/motochopper methods of rooting (which are in the noob friendly toolkit) are not available for this firmware version. All I see is this method http://forum.xda-developers.com/showthread.php?t=1709296
Most importantly, as I profoundly despise sense, I just want to unlock the boot loader, put a custom recovery on and get some Cm 10.1 on here.
I have read methods which require some hex editing, changing the cid to 111111111, etc...
My question is what is the best way to get a custom recovery on this phone now, as some of these methods seem really old (2012)
i'm just confused because it seems i have a pretty old firmware version and i don't want to break anything.
Click to expand...
Click to collapse
absolutely nevermind, i figured everything out.
Hi,
As you've already imagined, I'm not any god-alike person in XDA. I don't know a lot about android developing. Yes, I am an amateur. (Although not a beginner) I'm just in a bit of trouble here and would love to have someone to help me.
Anyway, I've been using an HTC One [(M7_UL), (PN0710000)] for about 3 weeks now. And I've already tortured it a lot (not physically! ) I've unlocked the bootloader, installed CWM custom recovery, installed the 2.17.401.1 stock ROM posted by mike1986. (believe me, this guy is awesome!!)
Now I want to get back to COMPLETELY STOCK so that I can get OTA updates again and remove the "TAMPERED" mark from my device's bootlocker menu. So I relocked my bootloader, downloaded an RUU (RUU_M7_UL_JB_50_HTC_Europe_1.28.401.7_Radio_4A.13.3231.27_10.31.1131.05_release_310878_signed.exe) and tried to install it. The interesting part is, this RUU is for "x.xx.401.x" based devices only. But mine was a SIM-Unlocked Vodafone UK (x.xx.161.x) based device out of the box. So, As I imagined right from the beginning, I couldn't install this RUU. I got the "ERROR [131]: CUSTOMER ID ERROR". But I also noticed that the .401 and the .161 variants have many similarities. Such as they are both M7_UL devices and their model numbers are same too (PN0710000). Honestly, I don't like Vodafone (I don't know why I bought it from them) and right now, I want the PURE STOCK ROM, not any career-branded ROM. So, I though if it was possible for me to install a "x.xx.401.x" based RUU in my device. And if it is possible in any way (there SHOULD be a way, right?), how do I do it? Please help me. And if you need any other information in order to answer my question, I'm ready to answer.
Thanks a lot....
I have a Telus evita phone on 4.1.1. I was wondering if I could flash the German O2 or T-Mobile OTA to receive 4.2.2. My phone is SuperCID and S-OFF. Phone is currently stock because I ran a RUU then updated to 4.1.1. Will I lose my data if I flash the OTA?
Thanks
dx99 said:
I have a Telus evita phone on 4.1.1. I was wondering if I could flash the German O2 or T-Mobile OTA to receive 4.2.2. My phone is SuperCID and S-OFF. Phone is currently stock because I ran a RUU then updated to 4.1.1. Will I lose my data if I flash the OTA?
Thanks
Click to expand...
Click to collapse
I would just flash TWRP back onto the phone, then flash Turge's stock T-Mobile Sense 5 ROM posted in Development. Install the 2.15 firmware if you experience signal drops or random reboots.
My typical recommendation is to stay away from official OTAs if you are modded.
I just don't want to flash anything on my phone that's not official. That's why I'm asking, I want to keep my phone stock and just get an official update not a rom from another source.
Your phone is already far from stock, with SuperCID and S-off. You're already down the rabbit hole. And putting an OTA for another version is also not going to be "stock" or "official" for your phone.
The stock ROM is just from the OTA dump, completely unmodified (not even rooted, in fact). Its what is on my phone, and is running great.
Running the OTA might be risky. OTA does not necessarily have all the components. For instance, the T-Mobile 5.05 OTA does not have all the hboot modules. It assumes you are coming for the most recent T-Mobile RUU or OTA. So depending on what is currently on your phone, you can brick.
In theory, I think what you are proposing will work if you RUU to the most recent T-Mobile Germany RUU, than T-Mobile Germany Sense 5 OTA.
But again, you're making it more complicated than need be. What is exactly the issue with "unofficial" ROMs? If you don't trust the devs here, you would not have done SuperCID and s-off to begin with.
It's not that I don't trust the devs I just want to use official carrier updates. I know my phone isn't stock what I meant is using stock/original files from carriers. So even though my phone is from Telus and I used a RUU from them to get back to stock firmware I can flash a T-Mobile RUU over top of it then use their OTA afterwards?
dx99 said:
So even though my phone is from Telus and I used a RUU from them to get back to stock firmware I can flash a T-Mobile RUU over top of it then use their OTA afterwards?
Click to expand...
Click to collapse
Yes, the only thing stopping the RUU from running would be the carrier ID check and hboot version check (might be some other checks). But since you have s-off, all security checks are bypassed by definition.
Alright, would there be any issues with the fact that I'm on 4.1.1 and going backwards in firmware first? Since most RUU are 4.0.
dx99 said:
Alright, would there be any issues with the fact that I'm on 4.1.1 and going backwards in firmware first? Since most RUU are 4.0.
Click to expand...
Click to collapse
Now that you mention it, it looks like you would have to run the most recent RUU from T-Mobile Germany (3.17.111.1) then run two OTAs (3.17.111.2, and then finally 5.08.111.2). Run them out of sequence, and you risk a brick.
RUUs can be installed out of sequence, but there isn't one for 5.08.
I retract my former idea to RUU then OTA. I can't personally recommend such action upon further consideration. Its more complicated than I originally thought. I go back to my former statement, in that you are making this much more complicated than it should be. You are actually creating a higher risk of bricking your phone due to some imagined fear of "unofficial software".
redpoint73 said:
Now that you mention it, it looks like you would have to run the most recent RUU from T-Mobile Germany (3.17.111.1) then run two OTAs (3.17.111.2, and then finally 5.08.111.2). Run them out of sequence, and you risk a brick.
RUUs can be installed out of sequence, but there isn't one for 5.08.
I retract my former idea to RUU then OTA. I can't personally recommend such action upon further consideration. Its more complicated than I originally thought. I go back to my former statement, in that you are making this much more complicated than it should be. You are actually creating a higher risk of bricking your phone due to some imagined fear of "unofficial software".
Click to expand...
Click to collapse
So then its not possible to use the T-Mobile RUU and OTA on my Telus phone?
dx99 said:
So then its not possible to use the T-Mobile RUU and OTA on my Telus phone?
Click to expand...
Click to collapse
I think its possible, but its needlessly complicated and possibly risky. If you do it wrong, you might brick.
I don't personally recommend it, and its my personal opinion that you don't have a particularly valid reason for going that route when simpler methods exist. So if you proceed, its at your own judgement and you take all responsibility if something goes wrong.
If it does manage to work so you think there might be compatability issues with the play store or region specific things?