Related
Hey guys,
I am an amateur in all these stuff. I recently picked up at&t one x white unlocked from US running 4.0.3
I wanted to update my phone but i guess i am afraid if my phone gets locked . Moreover i cannot even update it through settings as it says not able to connect to AT&T server.
Please help me regarding custom ROMS , updates Rooting etc and steps to follow.
Links to Threads that can help will be awesome.
Hoping you guys will help a new member
Thanks
Ankit
trojan_virus said:
Hey guys,
I am an amateur in all these stuff. I recently picked up at&t one x white unlocked from US running 4.0.3
I wanted to update my phone but i guess i am afraid if my phone gets locked . Moreover i cannot even update it through settings as it says not able to connect to AT&T server.
Please help me regarding custom ROMS , updates Rooting etc and steps to follow.
Links to Threads that can help will be awesome.
Hoping you guys will help a new member
Thanks
Ankit
Click to expand...
Click to collapse
1) you mean Sim - unlocked right? In that case it won't get locked even if you update the phone software.
2)First and important step is using the search function and I known its very hard for you but once in a while try using the search function, trust me you won't get tired
Follow the instructions in this link http://forum.xda-developers.com/showthread.php?p=30741993
Sent from my HTC One X using xda premium
trojan_virus said:
Links to Threads that can help will be awesome.
Click to expand...
Click to collapse
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=1671237
And don't update. The newest 2.20 version firmware is not currently rootable. And hope you don't already have 2.20 on the phone.
redpoint73 said:
Everything you need is here: http://forum.xda-developers.com/showthread.php?t=1671237
And don't update. The newest 2.20 version firmware is not currently rootable. And hope you don't already have 2.20 on the phone.
Click to expand...
Click to collapse
Thanks for correcting... I learned how to provide better reply
Sent from my HTC One X using xda premium
a little help guys...
I also have an unlocked HOX. I tried updating the software manually by downloading the AT&T ROM Update from the HTC website but got an error and now i'm stuck on a white screen that says:
**** TAMPERED ****
**** UNLOCKED ****
EVITA PVT SHIP S-ON RL
HBOOT.1.09.0000
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
RUU
Update Fail!
* I did a factory reset and now passed that white screen...does anyone know what the problem was? is my phone rooted?
y2janz said:
a little help guys...
I also have an unlocked HOX. I tried updating the software manually by downloading the AT&T ROM Update from the HTC website but got an error and now i'm stuck on a white screen that says:
**** TAMPERED ****
**** UNLOCKED ****
EVITA PVT SHIP S-ON RL
HBOOT.1.09.0000
OpenDSP-v28.1.0.32.0504
eMMC-boot
Apr 2 2012,21:08:24
RUU
Update Fail!
* I did a factory reset and now passed that white screen...does anyone know what the problem was? is my phone rooted?
Click to expand...
Click to collapse
You cannot run an RUU on a boot loader unlocked phone. relock it first.
gunnyman said:
You cannot run an RUU on a boot loader unlocked phone. relock it first.
Click to expand...
Click to collapse
Thanks. Unfortunately I don't know how to do that. I guess I'll hold off 4.0.4 for now...
You need to read some more, before running things willy-nilly without the proper research.
I would advise against running the 2.20 RUU. As I already mentioned, it updates the hboot, which robs you of the ability to flash kernels and radios. There is no upside to it, since you can flash the ROM in other ways. Your phone is bootloader unlocked, and has full ability to flash kernels and radios. These are all good things. Don't take a step backward by flashing the 2.20 RUU.
If all you want is to update the ROM to 2.20, just flash the pre-rooted ROM (which will not replace the hboot): http://forum.xda-developers.com/showthread.php?t=1812459
But in fact, these are more recent versions:
http://forum.xda-developers.com/showthread.php?t=1789059
http://forum.xda-developers.com/showthread.php?t=1838135
Ya know, you guys CAN extract the rom.zip from 2.2x ruu and pull each image and flash them individually to get the 2.2x updates and keep your unlocked 1.09 hboot intact. That way you dont have to do the kernal flashing and what not. It will be fully updated, sbl's, radio everything.:beer:
18th.abn said:
Ya know, you guys CAN extract the rom.zip from 2.2x ruu and pull each image and flash them individually to get the 2.2x updates and keep your unlocked 1.09 hboot intact. That way you dont have to do the kernal flashing and what not. It will be fully updated, sbl's, radio everything.:beer:
Click to expand...
Click to collapse
how I wish I had done this.
Thanks a lot guys. I should have done some research. I bought this phone second hand thinking "unlocked" meant I could use it on other networks --didn't know the previous owner meant he unlocked the bootloader...hahaha...I guess i'll do some research to relock it.
y2janz said:
I guess i'll do some research to relock it.
Click to expand...
Click to collapse
Didn't read a thing I typed, apparently.
No need to relock it. Just run one of the stock rooted or custom ROMs in Development. Flash a new radio if you want.
I'm sorry, i really don't know how to do any of those stuff...
I just got the phone a couple of days ago and i am still waiting on my t-mobile non-gba micro sim that i ordered online, now im really not sure anymore if its unlocked to other networks...
I won't know til that sim card gets here, but in the mean time i'll do some reading on all those stuff you mentioned =)
I went to the HTC site and did a manual update, but I dont have sense 4.1. anyone know if the ATT version will get it?
plz help
I have a at&t one x I bought last night that is unlocked and I am using on telus.
The phone isn't rooted and is running on android 4.0.3 and HTC sence 4.0
When I try to update it nothing happens. My brother has the same phone thro telus and has received updates. I have went to settings about phoneat&t updates but when I search it does not do nothing .
An AT&T phone won't get the updates unless it's on their network it seems. Just download the ruu
Sent from my VENOMized HoxL
Bump. I unlocked my Rogers One X a while back, because I am planning on selling it. Since that time though, I have run an RUU on it. I no longer have another carrier's SIM card to test, so I just want to know if the unlock is permanent , or if it gets relocked when an RUU or factory reset is run.
The SIM unlock is permanent and will survive any RUU or factory reset.
Sent from my Evita
I bought one S from Fido Canada. And unlocked rooted and disables many start-up apps. But I'm not sure if I can get OTA update.
CID is ROGER001
Android version 4.03
Software number 1.84.631.9
Anyone whose CID is ROGER001 can help me ?
You need to be completely stock (unrooted, with all Rogers crapware intact) for an OTA to work, even if it is offered to you.
As an aside, the 4.0.4 update has not been pushed out to the Bell/Virgin, Rogers/Fido, or TELUS/Koodo One S as of yet. I'm not even sure if the One S on Mobilicity, Wind, or Videotron shipped with it as the T-Mobile USA version hasn't received the update yet.
"You need to be completely stock (unrooted, with all Rogers crapware intact) for an OTA to work, even if it is offered to you."
Thanks for replying.
You mean if I want to receive OTA update, I have to lock, and unroot my phone?
EdwardGamma said:
"You need to be completely stock (unrooted, with all Rogers crapware intact) for an OTA to work, even if it is offered to you."
Thanks for replying.
You mean if I want to receive OTA update, I have to lock, and unroot my phone?
Click to expand...
Click to collapse
I think so.
invasion2 said:
I think so.
Click to expand...
Click to collapse
OK I will try that.
Thanks very much
Still no OTA for Rogers/Fido?
RUU for Fido/Rogers ?
EdwardGamma said:
"You need to be completely stock (unrooted, with all Rogers crapware intact) for an OTA to work, even if it is offered to you."
Thanks for replying.
You mean if I want to receive OTA update, I have to lock, and unroot my phone?
Click to expand...
Click to collapse
Would you know which RUU version to use for Fido provider if I was to flash back to stock?
You just need a stock recovery, and a stock ROM. You don't need to re-lock.
EdwardGamma said:
Still no OTA for Rogers/Fido?
Click to expand...
Click to collapse
I was wondering the same thing and after lots of internet reasearch i figured out 3 things:
1- The only ones having the 4.04 update are international version and T-mobile versions of HTC OneS
2- Canadian carriers are so freaking lazy as to getting out updates
3- If you want the update you need to change to super cid with root (the 111111 cid)and get the international OTA
=> However ive seen some people reporting having network problems after updating
So yea...it sucks..im having the same problem here so i feel you bro
I managed to unlock the bootloader easily, and I thought that would do the trick and let me update my phone...nope. Is there any way for me to be able to receive ota updates straight from HTC rather than having to wait for fido to smarten up? I remember on my sgs I could flash the international rom. I'm not too familiar with ruu, can someone help me out?
mahmoud.hawa said:
I managed to unlock the bootloader easily, and I thought that would do the trick and let me update my phone...nope. Is there any way for me to be able to receive ota updates straight from HTC rather than having to wait for fido to smarten up? I remember on my sgs I could flash the international rom. I'm not too familiar with ruu, can someone help me out?
Click to expand...
Click to collapse
You need to root, switch your CID to HTC_001 (or super CID), and flash a stock rom. There are threads on the topic use the search box.
rgbggb said:
You need to root, switch your CID to HTC_001 (or super CID), and flash a stock rom. There are threads on the topic use the search box.
Click to expand...
Click to collapse
I heard that supercid doesnt let you update ota?
As of now there is an OTA for rogers/fido but you have to be completely stock (lock bootloader, stock recovery, unrooted) I cant seem to find the RUU file to do that, has anybody come across a link?
nez762 said:
As of now there is an OTA for rogers/fido but you have to be completely stock (lock bootloader, stock recovery, unrooted) I cant seem to find the RUU file to do that, has anybody come across a link?
Click to expand...
Click to collapse
I've been looking for it as well.
Anybody ?
I'm with FIDO and I have updated my phone succesfully to Jelly Bean. like mentioned above, I couldn't find an RUU that would work with my phone.
So, in order to use the Rogers RUU file that is available, you have to downgrade your HBOOT. Its a bit scary of a process the first time around. But has worked perfectly several times for me now. Just follow the instructions exactly!
After that, you have to flash a stock rom, also widely available, in TWRP (or CWM). Then relock your bootloader. Then run the RUU!
That works for me! :good:
nez762 said:
As of now there is an OTA for rogers/fido but you have to be completely stock (lock bootloader, stock recovery, unrooted) I cant seem to find the RUU file to do that, has anybody come across a link?
Click to expand...
Click to collapse
I don't know if this would help. http://www.androidfiles.org/ruu/?dir=Ville
---------- Post added at 09:23 PM ---------- Previous post was at 09:11 PM ----------
fansou55 said:
I've been looking for it as well.
Anybody ?
Click to expand...
Click to collapse
Try checking this out too. http://www.androidfiles.org/ruu/?dir=Ville
bmb1983 said:
I'm with FIDO and I have updated my phone succesfully to Jelly Bean. like mentioned above, I couldn't find an RUU that would work with my phone.
So, in order to use the Rogers RUU file that is available, you have to downgrade your HBOOT. Its a bit scary of a process the first time around. But has worked perfectly several times for me now. Just follow the instructions exactly!
After that, you have to flash a stock rom, also widely available, in TWRP (or CWM). Then relock your bootloader. Then run the RUU!
That works for me! :good:
Click to expand...
Click to collapse
Thanks, I will give it a try !
whyfi said:
I don't know if this would help. http://www.androidfiles.org/ruu/?dir=Ville
---------- Post added at 09:23 PM ---------- Previous post was at 09:11 PM ----------
Try checking this out too. http://www.androidfiles.org/ruu/?dir=Ville
Click to expand...
Click to collapse
Thanks mate but they only have RUU_Ville_U_Rogers_WWE_1.70 which has hboot 1.06. Hboot downgrade seems to be the only solution so far.
You can try one of the sense based custom ROMs. Then you don't have to go through all the trouble of downgrading. If, you're concerned about WiFi not working, then you can try my fix
I have a S4 Phone branded to T-Mobile Germany (CID: T-MOB101).
I have take the Jellybean OTA update, and I'm trying to SUPERCID with the method here: http://forum.xda-developers.com/showthread.php?p=26516911#post26516911 but without success.
So the question is:
Has anyone with T-Mobile Germany managed to SUPERCID? And with what bootloader-ROM?
yep - no problem. It was one of the early bootloaders, 1.06 or 1.09. as my device now is one year old.
rootrider said:
yep - no problem. It was one of the early bootloaders, 1.06 or 1.09. as my device now is one year old.
Click to expand...
Click to collapse
Unfortunately I have take the 3.16.111.7 OTA update with 2.15 bootloader. Every time I modify the mmcblk0p4 partition to take supercid, but after the rebooting the system recovers the original one. I supose HTC has lock something (at least for the branded phones).
I've read about your problem in one of the threads here.
You might possibly need a t-mobile DE simcard to change CID successfully according to your problem. We could try that. If you want, I could buy a prepaid one and send it to you this week. You can send it back to me afterwards.
If this won't help, you can send me your device and I'd try to s-off it with my simcard here.
Out of interest, could you tell me the first six digits of your device serial? Something like HT23FW... Settings ->Info -> Identity
rootrider said:
I've read about your problem in one of the threads here.
You might possibly need a t-mobile DE simcard to change CID successfully according to your problem. We could try that. If you want, I could buy a prepaid one and send it to you this week. You can send it back to me afterwards.
If this won't help, you can send me your device and I'd try to s-off it with my simcard here.
Out of interest, could you tell me the first six digits of your device serial? Something like HT23FW... Settings ->Info -> Identity
Click to expand...
Click to collapse
Thank you for your kindly offer. But I don't think has something to do with the sim. I think has to do with 2.15 bootloader and branded phones.
My serial is HT26BW...... The phone was came with 4.0.3. But unfortunately I didn't try to supercid early enouph.
taxtax said:
Thank you for your kindly offer. But I don't think has something to do with the sim. I think has to do with 2.15 bootloader and branded phones.
My serial is HT26BW...... The phone was came with 4.0.3. But unfortunately I didn't try to supercid early enouph.
Click to expand...
Click to collapse
So your phone was manufactured in Taiwan 2012/June/11.
This means it was basically sold with ICS. Bootloader version 2.15 came with the JB update in December last year. So this means that the preowner of that phone must have changed the device to SCID or any other CID that was able to receive the JB OTA and install it. T-Mobile DE never offered JB for it's devices so far.
To sell it he returned to the stock CID and possibly messed up the device serial. That might be a reason for your efforts don't work. So lets assume your'e on the wrong serial.
Now you should check the devices serial (IMEI) e.g. with Phone Explorer and in the Info -> Phone Identity and compare it to that one in mmcblk0p4. Else enter *#06# for checking IMEI.
--- edit
I read the OP again. How did you manage to get the JB OTA update with your CID T-MOB101?
rootrider said:
So your phone was manufactured in Taiwan 2012/June/11.
This means it was basically sold with ICS. Bootloader version 2.15 came with the JB update in December last year. So this means that the preowner of that phone must have changed the device to SCID or any other CID that was able to receive the JB OTA and install it. T-Mobile DE never offered JB for it's devices so far.
To sell it he returned to the stock CID and possibly messed up the device serial. That might be a reason for your efforts don't work. So lets assume your'e on the wrong serial.
Now you should check the devices serial (IMEI) e.g. with Phone Explorer and in the Info -> Phone Identity and compare it to that one in mmcblk0p4. Else enter *#06# for checking IMEI.
--- edit
I read the OP again. How did you manage to get the JB OTA update with your CID T-MOB101?
Click to expand...
Click to collapse
I bought the phone new in Christmas (S4 with T-MOB101 cid).
As I said it was with the 4.0.3 and the same day I taked the 4.0.4 OTA update.
At 1 February I taked the jellybean OTA update (version 3.16.111.5)
And at 28 February I taked a minor OTA update (version 3.16.111.7)
I have the OTA updates if you want them.
Thanks for your information. I am wondering about that you could get the JB OTA Update with that CID. You could still check if your IMEI is right, but I'm running out of ideas...
Hello all. Quick question about running the 2.20 RUU -- I seem to recall, around the time that the 3.14 OTA update came out for the AT&T Version of the One XL a lot of folks were hard-bricking their phones that were previously rooted on a separate JB ROMs..perhaps something with the Super CID? I did not investigate this much because I wasn't ever interested in taking the 3.14 OTA but my question is: Can I safely run the 2.20 RUU on hboot 1.14 S-OFF; I am currently running a JB ROM right now. Sorry for the question but I can't seem to find the threads that explained why users were getting hard bricks from the OTA -- I'm about to wipe my phone and give it to someone else and I would hate to hard-brick it and the phone be no longer usable
TheEmpyre said:
Hello all. Quick question about running the 2.20 RUU -- I seem to recall, around the time that the 3.14 OTA update came out for the AT&T Version of the One XL a lot of folks were hard-bricking their phones that were previously rooted on a separate JB ROMs. I did not investigate this much because I wasn't ever interested in taking the 3.14 OTA but my question is: Can I safely run the 2.20 RUU on hboot 1.14 S-OFF; I am currently running a JB ROM right now. Sorry for the question but I can't seem to find the threads that explained why users were getting hard bricks from the OTA -- I'm about to wipe my phone and give it to someone else and I would hate to hard-brick it and the phone be no longer usable
Click to expand...
Click to collapse
The issue pertained to those with Super CID and S-ON.
Since you're S-OFF, it's safe to run the RUU. no need to relock the bootloader or change your CID.
exad said:
The issue pertained to those with Super CID and S-ON.
Since you're S-OFF, it's safe to run the RUU. no need to relock the bootloader or change your CID.
Click to expand...
Click to collapse
Thanks for the reply. Wow thats great, I remember last time I RUU I had to fastboot oem lock and then run it and flash the unlock token again which was pain in the a$$.
Thanks again for the clarification -- added [Solved]
exad said:
The issue pertained to those with Super CID and S-ON.
Since you're S-OFF, it's safe to run the RUU. no need to relock the bootloader or change your CID.
Click to expand...
Click to collapse
Just to clarify --- can I also run the 3.14 OTA if I am S-OFF without Brick?
TheEmpyre said:
Just to clarify --- can I also run the 3.14 OTA if I am S-OFF without Brick?
Click to expand...
Click to collapse
That's right.
Unfortunately for me, I was s-on and supercid when I took the OTA. Hard bricked my phone and I had to have it replaced lol.
marcur12 said:
Unfortunately for me, I was s-on and supercid when I took the OTA. Hard bricked my phone and I had to have it replaced lol.
Click to expand...
Click to collapse
Yeah I just vaguely remember seeing some unfortunate threads after the OTA came out and so I just thought I would check. Bummer about your device sorry
Sent from my HTC One using Tapatalk 2
TheEmpyre said:
Yeah I just vaguely remember seeing some unfortunate threads after the OTA came out and so I just thought I would check. Bummer about your device sorry
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Fun fact: Running the 2.20 RUU down from a 3.17 based ROM removes the "TAMPERED" tag from the bootloader. At least on hboot 1.14 and S-OFF
TheEmpyre said:
Fun fact: Running the 2.20 RUU down from a 3.17 based ROM removes the "TAMPERED" tag from the bootloader. At least on hboot 1.14 and S-OFF
Click to expand...
Click to collapse
Running any RUU should remove that Tampered text which is documented in the modding your bootloader screen thread.
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?