OKAY so this might be an odd question, mods can delete as soon as I get an answer that's ok but I have this situation:
I live in South Africa, where the HTC One S has not yet been released. On holiday in the Netherlands I decided to buy a SIM lock free HTC One S. With my old South African SIM card cut to size, the roaming features worked fine but I received the first OTA system update via a Dutch WiFi Network while still on holiday. This brought my device to software version 1.78.401.2 with Android 4.0.3. However I am now back in South Africa and although the HSDPA works fine here and such, I've seen the new 2.21 Android 4.0.4 update has since been released for Euro devices. I have checked my CID which is HTC__E11 or similar but checking under settings doesn't show any updates. Will the update become available to my device and can I receive the OTA update from South Africa?
I'm stock unrooted.
Thanks in advance. If suggested ideas include checking HBOOT please advise as I don't know how to check on this device, just came from an HTC Wildfire with CM.
AFAIK you'll get OTA updates based on your CID and it doesn't matter which carrier you're on. I'd imagine you'll get your OTA soon even if you pull your SIM out and move to Antarctica as long as you have Wifi. Never mind your hboot version it doesn't matter if you're on stock software, but if you want to check hold volume down for a while when powering on
Matt,
If the CID is HTC__E11 it means it is Europe unbranded. You should receive the OTA soon. But if you're like me and you're impatient, you can run the 2.21 RUU. But this will update your HBOOT and is currently not rootable. Checking for the HBOOT is the same as the Wildfire - Vol Down + Power.
Sent from pixels to more pixels
usaff22 said:
Matt,
If the CID is HTC__E11 it means it is Europe unbranded. You should receive the OTA soon. But if you're like me and you're impatient, you can run the 2.21 RUU. But this will update your HBOOT and is currently not rootable. Checking for the HBOOT is the same as the Wildfire - Vol Down + Power.
Sent from pixels to more pixels
Click to expand...
Click to collapse
Not true, I ran the RUU and rooted it. It's what I'm running on my phone at the moment.
T-MobileUS HTC One S running Stock Rooted 2.21.
fmedrano1977 said:
Not true, I ran the RUU and rooted it. It's what I'm running on my phone at the moment.
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
But your phone was also rooted before the HBOOT upgrade? Other people have said they can't root it after the upgrade, if they haven't rooted before.
usaff22 said:
But your phone was also rooted before the HBOOT upgrade? Other people have said they can't root it after the upgrade, if they haven't rooted before.
Click to expand...
Click to collapse
The first thing I did with my new device was run the 2.21 RUU followed by unlocking the bootloader and rooting it.
The only problem I had was running CWM recovery (probably my error) but no problems at all with TWRP recovery.
usaff22 said:
But your phone was also rooted before the HBOOT upgrade? Other people have said they can't root it after the upgrade, if they haven't rooted before.
Click to expand...
Click to collapse
Correct, but isn't root system related and not firmware related?
T-MobileUS HTC One S running Stock Rooted 2.21.
usaff22 said:
Matt,
If the CID is HTC__E11 it means it is Europe unbranded. You should receive the OTA soon. But if you're like me and you're impatient, you can run the 2.21 RUU. But this will update your HBOOT and is currently not rootable. Checking for the HBOOT is the same as the Wildfire - Vol Down + Power.
Sent from pixels to more pixels
Click to expand...
Click to collapse
Hey Usaff
Thanks for the advice, was slow to realize it was vol down+ power until the softkey lights flash
The RUU flashes and wipes the phone, correct? Strangely I remember using an RUU to get Froyo on my old Wildfire when it was still stock and somehow that functioned like an OTA and never wiped my data, might be remembering incorrectly, was a long time ago...
EDIT
Correct, but isn't root system related and not firmware related?
Click to expand...
Click to collapse
Is that the distinction between S-OFF and rooting? I know rooting gains access to Android system files and stuff, then is S-OFF just a security flag for HTC devices? Noob questions I know...
fmedrano1977 said:
Correct, but isn't root system related and not firmware related?
T-MobileUS HTC One S running Stock Rooted 2.21.
Click to expand...
Click to collapse
It is system related but firmware also greatly affects rooting, especially if a firmware upgrade upgrades your HBOOT version.
Sent from pixels to more pixels
Related
Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J
y2jdmbfan said:
Guys,
I have found a definite issue regarding trying to debrand and flash the 2.3.4 OTA update to my Bell debranded sensation...Here are my steps and results...
1. Performed Revolutionary on shipping Bell Canada Sensation
2. Changed CID to 11111111 via fastboot.
3. Flashed generic UK 1.35.401.1 software via RUU file.
4. Downloaded 2.3.4 OTA update.
5. Try to install the OTA update.zip from recovery, it errors out with Status 7 error. No matter what CID I use, I always get this error status 7.
6. Change CID to HTC__E11 to try and get the OTA update automatically, Downloads and then gives me a "variant system software" error when it goes to install. I've never heard of or seen this error before.
7. Run Revolutionary again and then flash the update.zip. It appears to successfully flash, but when the phone reboots, all I get is a black screen. the phone makes noises and appears to be functioning somewhat, but screen is black.
8. I am now thinking, great, I just bricked my phone...
9. Reboot into hboot. It still shows Bootloader of 1.17.0011, which is strange because the OTA is supposed to update it to 1.18.0000.
10. I then change the CID to 11111111 and reflash with the 1.35.401.1 RUU and thank god the phone is back to working condition.
It appears that there is either a hardware difference or something really low level that is being changed with this new update and it might not work properly with the different radio from the Bell Canada version with the 850/1900 radio, but I don't understand why flashing to the 1.35.401.1 RUU works fine. If anyone else can shed any light on this or give me any hints, I would appreciate. I thought my experiences might help the devs out there further understand the new OTA and the Sensation software/hardware. My end goal is to have the most up to date stock unbranded software installed on my Sensation. I am using with AT&T if anyone is wondering.
Y2J
Click to expand...
Click to collapse
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.
Something has changed...revolutionary now supports the new "locked" bootloader!
Hoggles said:
I would venture to guess you're not aware that you should probably not (at least not now), do an official FOTA/OTA on an unauthorized S-OFF Sensation.
The official HTC 2.3.4 OTA that came out a few days ago, LOCKS your device. It puts it back into an S-ON state.
Unless something has changed, if you have S-OFF via Revolutionary....stay far away from official HTC updates.
Click to expand...
Click to collapse
I'm well aware that the the official HTC 2.3.4 OTA locks the device. As long as I have a debranded Sensation running the latest and greatest firmware/software, that is all I am looking for. And now that Revolutionary works on the new HBOOT there shouldn't be much trouble getting back to the original shipping software. I still am curious as to what is causing this "Error Status 7" error code.
So how can I update my sensation with s-off?
A bug in me from being updated.
That would really interest me too! don't want to be S-ON again to make this update. Another question (maybe off topic): how can i update to new S-OFF version 04pre4? I'm now on 03pre7.
Hi
I have the exact same problem as yours, what can we do to update it?
Same on Swisscom-branded phone
I tried the OTA on my swisscom phone, it reboots and I get an exclamation mark with a blue droid. Waited 10 minutes just in case, but no change.
Removed battery and rebooted. Phone still ok, but not updated obviously.
I'm not sure it will remove S-OFF, but I don't care, HTC provides an official procedure for that and we have what we need.
But I need this update to work on my rooted, S-OFF stock sensation. Will try again anyway...
EDIT: I tried going into recovery and manually flashing the OTAxx.zip file, but it gave me an assert_failed: check_cid!? Though I never changed the phone CID! So why propose me an update on my phone if it's the wrong one??? Not sure I want to change the CID of my phone now.
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
Hello
I've got a rooted One S, i'm trying to get the sense 4.1 OTA update but with no luck. I currently have the stock rom and just yesterday flashed a stock recovery. I managed to download the update but about a quarter of the way through the installation I got a red triangle. About five minutes later the phone reboots and i'm back to square one. I've also tried looking for an ruu for tmobile uk but to no avail.
Have you tried pressing VOL UP on the triangle?
Check for updates by going into the dialer and typing *#*#2432546#*#* (numbers stand for CHECKIN). Stay with the update the whole way through. Or better yet, since you're rooted change your CID to HTC__001 and run the 2.38 unbranded RUU.
Red triangle
usaff22 said:
Have you tried pressing VOL UP on the triangle?
Check for updates by going into the dialer and typing *#*#2432546#*#* (numbers stand for CHECKIN). Stay with the update the whole way through. Or better yet, since you're rooted change your CID to HTC__001 and run the 2.38 unbranded RUU.
Click to expand...
Click to collapse
What does vol up do? I just tried it but nothing happened, and also do you know where i can find the ruu?
I'm also with T-Mobile UK and unfortunately there are no RUUs. Which is why I suggested de-branding. How about holding the VOL UP button? I think that was it.
Sent from my locked, tampered ville
I just tried VOL UP it went into the bootloader, then i went to recovery and i got the same red triangle again
Hmm. At this stage I think the best option would be to de-brand yourself, run an unbranded RUU and then change your CID to T-MOB005 to receive the update. Then that should work.
usaff22 said:
Hmm. At this stage I think the best option would be to de-brand yourself, run an unbranded RUU and then change your CID to T-MOB005 to receive the update. Then that should work.
Click to expand...
Click to collapse
Do you know where i can find the RUU?
Quick question!!
If I change Cid to HTC__001 will it change the radio or anything of the sort that will make it not work with my network in Canada. What are the benefits of keeping your Cid from the network? Sorry for the noob question!
Sent from my HTC One S using xda app-developers app
Changing ur cid Will not mess anything up I changed mine through my phone. As for finding unbranded ruus I b have been looking for about a week and havemt found one and also I think the only way to use jb on one s is with a custom Rom right now
siqbudz said:
Changing ur cid Will not mess anything up I changed mine through my phone. As for finding unbranded ruus I b have been looking for about a week and havemt found one and also I think the only way to use jb on one s is with a custom Rom right now
Click to expand...
Click to collapse
You have been looking for an unbranded RUU for a week and found nothing? They're everywhere! Shipped-ROMS, HTCRUU, Sneakyghost's Dropbox, Footballs links...
Hi guys, my one s was bricked because it had super cid and I installed the jellybean ota. My device has now been fixed and it came back with a vodafone rom on there :S the CID was vodap001 or something like that. It must be because the guy who I bought the device off of must of bought a vodafone device. Anyway I changed the cid to HTC_001 and succesfully ran the jellybean RUU so does that mean that my phone is now unbranded and seen as an unbranded device? Am I now safe to install otas or will they brick my phone? I'm hoping changing my CID to HTC_001 is enough.
Anybody? Man it's quiet here in the One s forums, coming form a N4!
yes.
device is now unbranded.
only the supercid and ota combo = brick as fas as is know.
htc__001 devices where able to do the ota.
but always look for user experience when doing a future ota, you never know.
real187 said:
yes.
device is now unbranded.
only the supercid and ota combo = brick as fas as is know.
htc__001 devices where able to do the ota.
but always look for user experience when doing a future ota, you never know.
Click to expand...
Click to collapse
That's good to know, thanks. When the next ota is ready I'll ask people who changed their cid if the update went ok
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