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
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!
Just a heads up, HTCDEV unlocking no longer works with supercid. Changing cid to 22222222 does work. Thanks BEAUPS for already confirming that (Hes a beast)
Seeing that the chances of the hox exploits getting updated are pretty slim heres a easy fix to get people unlocked
Easy fix-
Use any existing exploits that changes your cid to supercid. Once done-
From bootloader use the fastboot cmd
fastboot oem writecid 22222222
Then proceed with getting your unlock token as usual using htcdev
The above cmd will only work with supercid. Once you change it to anything other, the command no longer will change cid. You have to do it manually.....
This is just a heads up and a quick workaround for those that need it.
18th.abn said:
Just a heads up. Changing cid to 22222222 works. Thanks BEAUPS for testing/confirming that.
Easy fix-
Use any existing exploits that changes your cid to supercid. Once done-
From bootloader use the fastboot cmd
fastboot oem writecid 22222222
Then proceed with getting your unlock token.
The above cmd will only work with supercid. Once you change it to anything other, the command no longer will change cid. You have to do it manually.....
This is just a heads up and a quick workaround for those that need it.
Click to expand...
Click to collapse
They just started blocking it? I just Unlocked my Bootloader last Sunday with 11111111 just fine
Re: HtcDev wesite Blocking Supercid FIX
Great work
Sent from my SPH-L710 using Tapatalk 2
Seriously?! Why would they do this? Is SuperCID a security risk? I thought I had left this kind of crap behind when I retired my iphone.
This is my first and last HTC phone.
Sent from my Nexus 7 using Tapatalk HD
does this mean updating to jb sense with 22222222 will no longer brick phone like with supercid?
Supercid doesn't cause brick or atleast out of the many ota's I have done it has never caused an issue. Who actually did have issues with supercid and an ota?
twistedddx said:
Supercid doesn't cause brick or atleast out of the many ota's I have done it has never caused an issue. Who actually did have issues with supercid and an ota?
Click to expand...
Click to collapse
I get an issue with SuperCID: I apply an ota from an official RUU to get Jelly Bean, the ota was very well installed but at the end of the process the phone doesn't boot an was locked in QHSUSB_DLOAD and at this time when you're locked in this mod by OTA update with superCID you can't rewrite partitions with the topic "unbricking evita".
My only solution was mobiletechvideos.com who fixed it very well
mik93250 said:
I get an issue with SuperCID: I apply an ota from an official RUU to get Jelly Bean, the ota was very well installed
Click to expand...
Click to collapse
What ruu did you apply? Was the phone modified in any other way than supercid? Eg was the hboot downgraded? Previous unlocked bootloader? Current unlocked bootloader?
What was the full state of the phone prior to accepting ota.
How was the ota applied? Did you simply check for updates and accept then follow prompts. Or installed via fastboot?
I have upgraded 2 hk one xl's with supercid to 3.17 via ota without issue. One was previously hong Kong ruu then wiped and had singtel stock Rom flashed then accepted singtel 3.17 ota. Could not use singtel ruu as Hong Kong ruu was newer and already installed. Hboot downgrade and software version tinkering still did not allow singtel ruu. I could only reinstall honk Kong ruu.
The other via o2 ruu and o2 3.17.
There seems to be some differences in the protections in hboot. Downgrading my phones hboot to 1.09 did not make flashing radio and boot from recovery functional again. It did not let me install older ruu's. My devices, one that has had every mod and flash done to it and the other very very little, both seem super hboot protected now!
The similar theme is both devices have been through all 4 generation of ota's. Following different ota and ruu paths but have now got the same outcome.
Maybe it relates to when supercid was applied even. Both my devices had supercid applied at hboot 1.09.
Damn HTC and ATT! They are bent on making this difficult. My next phone will be Nexus, enough of this crap!
We've had worse patches to overcome on the Evita, atleast its a simple solution for the time being. I do agree tho. I moved on from htc for the time being.
Sent from my SPH-L710 using Tapatalk 2
iElvis said:
Seriously?! Why would they do this? Is SuperCID a security risk? I thought I had left this kind of crap behind when I retired my iphone.
This is my first and last HTC phone.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
done moved over to the nexus 4 myself
Great to know, although I already have mine unlocked.
CheesyNutz said:
done moved over to the nexus 4 myself
Click to expand...
Click to collapse
Can you get Beats Audio or any other sound enhancements on a Rooted Nexus 4 via Custom Rom or other methods?
Viper4713 said:
Can you get Beats Audio or any other sound enhancements on a Rooted Nexus 4 via Custom Rom or other methods?
Click to expand...
Click to collapse
Yes
Sent from my Nexus 7 using Tapatalk HD
Do you miss LTE cheesy? I live in Canada so I understand I can get LTE on nexus 4 but if I couldnt I don't think I could live without it now
Sent from my VENOMized HoxL
CheesyNutz said:
Yes
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Thanks for the Info, I guess my next phone later on will be a Nexus Phone
area51avenger said:
Do you miss LTE cheesy? I live in Canada so I understand I can get LTE on nexus 4 but if I couldnt I don't think I could live without it now
Sent from my VENOMized HoxL
Click to expand...
Click to collapse
LTE is not in my area so in would have no idea
Sent from my Nexus 7 using Tapatalk HD
I can't believe at&t would be this petty... Or that HTC would go along with it. I'm glad I unlocked my boot loader when I did.
Sent from my Nexus 7 using xda premium
Just tested.
Hong Kong One XL running 3.17.707.1.
Supercid 11111111
Just went through http://htcdev.com unlock process and got an unlock token 100% fine.
Again there is nothing wrong with Supercid, at least not in general. It works with htcdev.com and does not brick phones.
Someone needs to check if it is just AT&T phones that are struggling with supercid or if something else is upsetting things.
It is not supercid on its own, supercid(11111111) works fine!
HTC/AT&T might be actively checking for modified AT&T phones that are getting unlock tokens via root exploits and changing cid.
Non at&t phones don't need supercid, so this only affects at&t phones. All the other carriers phones will unlock with out messing with the cid number.
Sent from my Nexus 7 using xda premium
Sorry to ask but I was waiting to get the HTC one but with the delay I decided to pick up a new hox in the meantime...does anyone know what firmware the newer devices ship with? I'm not too concerned with flashing roms at this time, but I will want root...thanks....sorry coming from Samsung phones, rooting and flashing seemed too easy....I'm really getting lost on all the *s-off* stuff
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
lunercrab said:
Sorry to ask but I was waiting to get the HTC one but with the delay I decided to pick up a new hox in the meantime...does anyone know what firmware the newer devices ship with? I'm not too concerned with flashing roms at this time, but I will want root...thanks
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Really depends on what they had in stock some ship still with 1.85 kinda just luck of the draw on what you get.
ronnie498 said:
Really depends on what they had in stock some ship still with 1.85 kinda just luck of the draw on what you get.
Click to expand...
Click to collapse
Well the last one I got back in October that I sold had I think 2.20...at that time there was no root...if I've been searching the forums correctly u can root 2.20 now correct?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit
Have a look at this thread
ronnie498 said:
[ROOT] HTC One X AT&T 2.20 Firmware - X-Factor root exploit
Have a look at this thread
Click to expand...
Click to collapse
Sweet...so I'm guessing 2.20 is the most recent firmware then...
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
lunercrab said:
Sweet...so I'm guessing 2.20 is the most recent firmware then...
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
The lastest is 3.14 but if you have not ran the OTA then you will have one of the others
Sorry one last question that I'm a bit confused on...if I update it to jelly bean once I get it...can I still root?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
lunercrab said:
Sorry one last question that I'm a bit confused on...if I update it to jelly bean once I get it...can I still root?
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
DON'T DO ANYTHING YET!
Latest firmware for AT&T is 3.18, which comes with the JB 4.1 Sense update. This firmware is not rooted, so if you were lucky enough to get an older HOX (2.20 or 1.85 firmware, neither of which is Jelly Bean), then you can root it, which you must do before you take the OTA update (in which case there's no reason to take it afterwards anyways). :good:
jeffwyeh said:
DON'T DO ANYTHING YET!
Latest firmware for AT&T is 3.18, which comes with the JB 4.1 Sense update. This firmware is not rooted, so if you were lucky enough to get an older HOX (2.20 or 1.85 firmware, neither of which is Jelly Bean), then you can root it, which you must do before you take the OTA update (in which case there's no reason to take it afterwards anyways). :good:
Click to expand...
Click to collapse
Gotcha that's what I wanted to know....well hopefully I won't get the 3.18...should know on Tuesday....so if its 2.20 or less then I root and once I ota to jb the root will stay....now should this all pan out this way and down the line I want to try some rooms out, can I unlock the boot loader even if I updated to jb? Honestly I don't mind staying on ics if need be
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
lunercrab said:
Gotcha that's what I wanted to know....well hopefully I won't get the 3.18...should know on Tuesday....so if its 2.20 or less then I root and once I ota to jb the root will stay....now should this all pan out this way and down the line I want to try some rooms out, can I unlock the boot loader even if I updated to jb? Honestly I don't mind staying on ics if need be
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
On 2.20, you can use the X-Factor root exploit or hasoon's all-in-one kit. Afaik, perm root requires you to unlock your bootloader, which in turn requires SuperCID (country ID? carrier ID? I can't remember). If you try to run the OTA with superCID, it will fail and entirely brick your phone.
However, with an unlocked bootloader, you can install a custom recovery and flash the updated ROM manually with no problems.
jeffwyeh said:
On 2.20, you can use the X-Factor root exploit or hasoon's all-in-one kit. Afaik, perm root requires you to unlock your bootloader, which in turn requires SuperCID (country ID? carrier ID? I can't remember). If you try to run the OTA with superCID, it will fail and entirely brick your phone.
However, with an unlocked bootloader, you can install a custom recovery and flash the updated ROM manually with no problems.
Click to expand...
Click to collapse
Not quite. You can still lose root if you update to a newer firmware. You need to s-off after rooting and unlocking. It's s-on + supercid + 3.18 that causes the brick.
To OP:
Assuming you get a 2.20 phone, you should run the toolkit to root, supercid, and unlock, then s-off (link to thread is in my sig). A lot of people have gotten bricked by upgrading to 3.18 because they didn't think they needed s-off.
Once you're s-off, you can never lose root because it turns off all security restrictions on your phone.
iElvis said:
Not quite. You can still lose root if you update to a newer firmware. You need to s-off after rooting and unlocking. It's s-on + supercid + 3.18 that causes the brick.
To OP:
Assuming you get a 2.20 phone, you should run the toolkit to root, supercid, and unlock, then s-off (link to thread is in my sig). A lot of people have gotten bricked by upgrading to 3.18 because they didn't think they needed s-off.
Once you're s-off, you can never lose root because it turns off all security restrictions on your phone.
Click to expand...
Click to collapse
Not to derail the thread, but for my own knowledge, is it possible to get into a permanently rooted state without supercid?
jeffwyeh said:
Not to derail the thread, but for my own knowledge, is it possible to get into a permanently rooted state without supercid?
Click to expand...
Click to collapse
You need supercid to get s-off, but after that, you can return to stock cid without issues. With s-off, you can change your cid to whatever you want.
iElvis said:
You need supercid to get s-off, but after that, you can return to stock cid without issues. With s-off, you can change your cid to whatever you want.
Click to expand...
Click to collapse
Last question for now, I promise, and I'll return the thread to it's rightful owner. Are there any advantages to going back to stock cid, outside of wanting the take the OTA update without bricking?
jeffwyeh said:
Last question for now, I promise, and I'll return the thread to it's rightful owner. Are there any advantages to going back to stock cid, outside of wanting the take the OTA update without bricking?
Click to expand...
Click to collapse
Once you're s-off, I don't think it makes a difference, unless you lost your unlock token and need another one. Then you've got to assign 22222222 as your cid (supercid no longer works on htcdev).
Ok so I got my package from UPS....opened it and noticed the tamper seal was already broken....since it was sold as a new unit that seal should have been sealed....i call ATT and and going to go to a store to swap it out for another one...good thing too cause the one I got had the 3.18 firmware so I couldn't root....here's to hoping I luck out on the next one
ok so lucked out and got a 2.20....anyways i unlocked the bootloader and rooted...i'm attempting s-off...not successful yet....but phone is trying to update....i turned off all data to the phone temp...how do i stop the phone from downloading the update??? i don't wanna brick it...can i let it update once i get s-off?
lunercrab said:
ok so lucked out and got a 2.20....anyways i unlocked the bootloader and rooted...i'm attempting s-off...not successful yet....but phone is trying to update....i turned off all data to the phone temp...how do i stop the phone from downloading the update??? i don't wanna brick it...can i let it update once i get s-off?
Click to expand...
Click to collapse
Just keep declining the update. It won't force it for a few days.
iElvis said:
Just keep declining the update. It won't force it for a few days.
Click to expand...
Click to collapse
yeah but it shows system update downloading inside the notification window....how do i stop that...i mean will it download and install if i let it continue?
3.18
I just bought a new One X from a local AT&T store and it has firmware 3.18 with JB 4.1.1. It's the greatest phone I've ever had. Sucks that I can't root it though. I've been trying to think of ways to unlock the bootloader, but I guess it's the encryption that's the real deal.
I was thinking about trying the xfactor exploit just for kicks, although I read that they killed that with 3.18, not to mention the CID block on HTCdev.
I recieved yet another refurbished replacement from t-mobile today, which came loaded With ICS.... I popped my sim in and set it up and after connecting to wifi, i got a system update notice for JellyBean. I made the mistake of not rooting and changing the cid while it was on ICS so now, after the update, im on JellyBean and cannot change the cid for s-off.
I've already unlocked the bootloader and rooted with CWM Recovery installed....and cannot update OTA....
I want to unroot and relock the bootloader and return to stock jellybean so i can do the OTA update from today June 26 2013. I don't care for rooting without s-off and JellyBean is running great as it is. I'm unable to find the RUU for Tmous TMO010. where can i find this ruu or what are my options for installing this update manually?
Why cant you change the CID ?
Jacob3o5 said:
I recieved yet another refurbished replacement from t-mobile today, which came loaded With ICS.... I popped my sim in and set it up and after connecting to wifi, i got a system update notice for JellyBean. I made the mistake of not rooting and changing the cid while it was on ICS so now, after the update, im on JellyBean and cannot change the cid for s-off.
I've already unlocked the bootloader and rooted with CWM Recovery installed....and cannot update OTA....
I want to unroot and relock the bootloader and return to stock jellybean so i can do the OTA update from today June 26 2013. I don't care for rooting without s-off and JellyBean is running great as it is. I'm unable to find the RUU for Tmous TMO010. where can i find this ruu or what are my options for installing this update manually?
Click to expand...
Click to collapse
Try here: http://www.androidfiles.org/ruu/get..._10.30.50.08L_release_309489_signed_ICS_2.exe
Uwe303 said:
Why cant you change the CID ?
Click to expand...
Click to collapse
I have no idea why, something about the jb ota not letting the cid save after the change, I've tried many times with no success, no matter what value I put, it just reverted back to tmo010.
Sent from my HTC VLE_U using Tapatalk 4 Beta
elbee222 said:
Try here: http://www.androidfiles.org/ruu/get..._10.30.50.08L_release_309489_signed_ICS_2.exe
Click to expand...
Click to collapse
Ok I downloaded the RUU from the link and while it was downloading, I found a link on the support.htc.com with the RUU from the JB update from April. I don't know enough about MD5 and checking them, the checksum isint provided with the download from the HTC site so I wouldn't know what to check.
Which one would you guys suggest?
This is the link to the RUU that I found.
https://support.htc.com/en-us/080-H...TC_One_S™_for_T-MOBILE_ROM_Update_|_4.19.2013
File Name - RUU_Ville_U_JB_45_S_TMOUS_3.14.531.11_Radio_1.13.50.05.31_10.30.50.08L_release_309489_signed_ICS_2.exe
Sent from my HTC VLE_U using Tapatalk 4 Beta
With your CID, the RUU you identified should be the correct one.
Dont you mean T_MOB010 as cid, not tmo010
Verstuurd van mijn HTC One S met Tapatalk