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
Related
hello i just changed my cid from HTC__203 to HTC__E11 (dutch), do i still receive ota updates and what about warranty does it affect it???
btw I live in the Netherlands and dit try to search but without any significant results.
edit: after a hardreset i see that i do get OTA updates from HTC so that part is ok.
Now just for the warranty part....
lexuz said:
hello i just changed my cid from HTC__203 to HTC__E11 (dutch), do i still receive ota updates and what about warranty does it affect it???
btw I live in the Netherlands and dit try to search but without any significant results.
edit: after a hardreset i see that i do get OTA updates from HTC so that part is ok.
Now just for the warranty part....
Click to expand...
Click to collapse
the ota works i just know that i don't know if it invalidates the warranty...but if you flash the right RUU (always do it before sending it to HTC) you will get your CID back
matt95 said:
the ota works i just know that i don't know if it invalidates the warranty...but if you flash the right RUU (always do it before sending it to HTC) you will get your CID back
Click to expand...
Click to collapse
Hi, how do i know witch ruu to use? (Old cid was htc__203)
Off topic: beautiful city u come from.
here you can find all the RUUs but you have to be registered and pay however you can find which is your RUU and google it
matt95 said:
here you can find all the RUUs but you have to be registered and pay however you can find which is your RUU and google it
Click to expand...
Click to collapse
If if download a ruu and then flash it, don't i keep de cid that i now have? I know that after a hardreset the cid stays the same.
I can confirm flashing a RUU NOT gives you your CID back.. I flashed 1.45 RUU and my CID is still 111111
Sent from my Pyramid-T using xda premium
BurnRubber90 said:
I can confirm flashing a RUU NOT gives you your CID back.. I flashed 1.45 RUU and my CID is still 111111
Sent from my Pyramid-T using xda premium
Click to expand...
Click to collapse
just like i thought, how the h#ll do i change my cid back to original?
If someone can confirm that Cid change doesn't affect warranty then this thread can be closed
If you want to change your Cid back just use the same process you used to change it, and if you don't know your Cid look here...
http://forum.xda-developers.com/showthread.php?t=1195475
Zylograth said:
If you want to change your Cid back just use the same process you used to change it, and if you don't know your Cid look here...
http://forum.xda-developers.com/showthread.php?t=1195475
Click to expand...
Click to collapse
I do know that thread but i'm still s-on and it seems that i can't change my cid back. ( i thought i saw someone else with the same problem in this forum.)
It seems i could only change it once with s-on.
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
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...
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.
[Background]
HTc One S (S4), CID changed from T-MOB005 to 11111111, Version 4.0.3, relocked. s-off.
RUU (4.0.4) update passed and it can power on . then i open the WLAN to receive the OTA update, then download, update... then can not power on, can not boot into HBOOT , the power indicator led can not lighting when connect to PC.
[Question]
how can it lose the power, and can not boot to HBOOT or OS? just do the OTA update...
how to fix it ?
lvdouw said:
[Background]
HTc One S (S4), CID changed from T-MOB005 to 11111111, Version 4.0.3, relocked. s-off.
RUU (4.0.4) update passed and it can power on . then i open the WLAN to receive the OTA update, then download, update... then can not power on, can not boot into HBOOT , the power indicator led can not lighting when connect to PC.
[Question]
how can it lose the power, and can not boot to HBOOT or OS? just do the OTA update...
how to fix it ?
Click to expand...
Click to collapse
You didn't read up properly. Taking an OTA with with SuperCID (11111111) results in a hard brick. You'll have to contact Tecardo to unbrick, or if you have insurance, you better look for excuses.
kylepont said:
You didn't read up properly. Taking an OTA with with SuperCID (11111111) results in a hard brick. You'll have to contact Tecardo to unbrick, or if you have insurance, you better look for excuses.
Click to expand...
Click to collapse
Thanks for ur reply, i think i need to find some guys to help me unbrick.
before this, someone told me theere is no affect about change CID to 11111111 at OTA update.. so , i did it
lvdouw said:
Thanks for ur reply, i think i need to find some guys to help me unbrick.
before this, someone told me theere is no affect about change CID to 11111111 at OTA update.. so , i did it
Click to expand...
Click to collapse
Whoever told you was wrong. OTA with supercid saddens the phone.
khan.orak said:
Whoever told you was wrong. OTA with supercid saddens the phone.
Click to expand...
Click to collapse
Do you have S4 version mainboard photo? i wanna make sure there is no short circuit(solder short..) in JTAG interface.