Hi. I want to return a SIM unlocked, S-OFF Vivid (AT&T) completely to stock, using the instructions in step 6 from the superguide for warranty purposes.
I've searched for a while but haven't found a definitive answer about whether or not this method (whether with the RUU or the zip file) will turn S-ON and relock the sim card. Can someone confirm or deny this for me? Thanks.
rohit275 said:
Hi. I want to return a SIM unlocked, S-OFF Vivid (AT&T) completely to stock, using the instructions in step 6 from the superguide for warranty purposes.
I've searched for a while but haven't found a definitive answer about whether or not this method (whether with the RUU or the zip file) will turn S-ON and relock the sim card. Can someone confirm or deny this for me? Thanks.
Click to expand...
Click to collapse
Flashing stock RUU will not return you to S-ON nor relock SIM Card...
Read this [HOW-TO] Return Your Device to S-ON after S-OFF to return to S-ON
Related
So my One is having issues charging, something is up with the USB port. Called TMO and they sent me a replacement phone and a return label. I'm rooted and my bootloader was unlocked (voiding my warranty apparently). So I went to re-lock the bootloader and it was successful HOWEVER now it states in the bootloader that it's been re-locked and tampered. Any way to make it seem as if it was never unlocked? Am I going to have to worry about them not accepting my device? Am I totally screwed here?
take a look here
http://forum.xda-developers.com/showpost.php?p=42598117
i hope there is a other htc Care poit how has the right zip file for your HTC One. That goes by CID or part number.
i only can provide t-mobile germany
voltigeur said:
take a look here
http://forum.xda-developers.com/showpost.php?p=42598117
i hope there is a other htc Care poit how has the right zip file for your HTC One. That goes by CID or part number.
i only can provide t-mobile germany
Click to expand...
Click to collapse
Thanks for the response, I'm on TMO in the US. I haven't gone the S-Off route yet either so I'm not sure this applies to me...and my CID doesn't match the thread. Appreciate the input though...
You need the official file form a HTC Care point over there i the states.
Follow the guid to get Never locked and the state tamperd away.
Do the soff .follow the guide remove tampered and to relock bootloader without it saying relocked it would say locked. Then return to s on. But please follow the guide to the letter.
atrako1973 said:
Do the soff .follow the guide remove tampered and to relock bootloader without it saying relocked it would say locked. Then return to s on. But please follow the guide to the letter.
Click to expand...
Click to collapse
Ok I'll give it a shot but I don't have S-Off right now, S is still ON so not sure if that is a problem.
i think you need to do soff first to be able to do the rest . but please read and read and read before prociding to soff , see all the requirement and so on
its easy .... little comon sense
Get S-off with revone relock bootloader remove tampered act like nothing has ever happened (shhhhhh dont tell HTC) :good:
Can I debrand my phone without s-off or without unlocking my bootloader or can I relock bootloader so it says "locked" and no "tampered"/""relocked"/"unlocked" because i want to still have my warranty.
adammo666 said:
Can I debrand my phone without s-off or without unlocking my bootloader or can I relock bootloader so it says "locked" and no "tampered"/""relocked"/"unlocked" because i want to still have my warranty.
Click to expand...
Click to collapse
I'm assuming you have a carrier branded device so without unlocking the bootloader you are stuck with your carrier rom..... there's not much else you can do.
Without unlocking the bootloader, you can't really do anything to your phone.
You can relock the bootloader so it says "locked" but you need s-off.
You could always unlock the bootloader, get s-off, change what you want, relock to "locked", and then back to s-on.
Just be really reeeeeaaaaaaaallly~ careful not to brick your device when tampering with s-off. Don't go back to s-on with modified/unsigned hboot, etc.
OP can't S-OFF. 1.54 HBOOT and S-ON.
http://forum.xda-developers.com/showthread.php?t=2387163
Pretty much screwed for now.
cee43ja1 said:
OP can't S-OFF. 1.54 HBOOT and S-ON.
http://forum.xda-developers.com/showthread.php?t=2387163
Pretty much screwed for now.
Click to expand...
Click to collapse
Im gonna post a follow up on this one, as I am in the same boat. Have unfortunately bought a One with a very weak wifi antenna, and suffer from dropouts and short distance. I bought this one yesterday, but I have already rooted to get my titanium backups back.
Is there any ETA for S-OFF on Hboot 1.54? Im not asking for a specific eta, but will it take days, weeks or months before they will break it? Just asking out of curiousity, I'll guess ill have to wait anyway.
Can I go s-on with the latest 3.62 firmware or do I need to go back to 2.24.401.1 first?
Better one more stupid question then a bricked phone.Do I need s-on to send it to repairing the camera?
jaypeg123 said:
Can I go s-on with the latest 3.62 firmware or do I need to go back to 2.24.401.1 first?
Better one more stupid question then a bricked phone.Do I need s-on to send it to repairing the camera?
Click to expand...
Click to collapse
Nope. Just lock your bootloader using revone (it just shows the locked tag) and remove Tampered flag, you won't lose any data (I used Hasoon2000 toolkit for revone). This makes the phone look like it was bought that way.
Besides HTC doesn't pay so much attention to S-OFF, it's just the unlocked bootloader and tampered flag that may void your warranty
Once you S-OFF, I don't see a reason why you will S-ON again.
HussainQ said:
Nope. Just lock your bootloader using revone (it just shows the locked tag) and remove Tampered flag, you won't lose any data (I used Hasoon2000 toolkit for revone). This makes the phone look like it was bought that way.
Besides HTC doesn't pay so much attention to S-OFF, it's just the unlocked bootloader and tampered flag that may void your warranty
Once you S-OFF, I don't see a reason why you will S-ON again.
Click to expand...
Click to collapse
Ok thank's I have read about people sending it in with s.off and get it s-on in return. But do you know the drill about the s-on, Is it nessesery to have the original 2.24.401 installed to get it right. I did update it OTA so It is 100% now, just forgot about the s-off.
jaypeg123 said:
Ok thank's I have read about people sending it in with s.off and get it s-on in return. But do you know the drill about the s-on, Is it necessary to have the original 2.24.401 installed to get it right. I did update it OTA so It is 100% now, just forgot about the s-off.
Click to expand...
Click to collapse
I don't really know if they S-ON the device or not. OTA is fine since it is official. Just in-case, I would check rumrunner S-Off compatibility with your firmware. And check your HBOOT version as well.
So my phone was S-OFF, superCID, custom firmware, running ARHD with TWRP recovery. I carried out the procedure to revert to 100% stock, I have a Rogers HTC One but a Rogers RUU doesn't exist, however I was able to get OTA updates after reverting to stock so I'm assuming the hboot, bootloader, recovery, stock ROM are all Rogers based.
However, when reverting to stock, I used an AT&T RUU to go down to 1.26 firmware and then Rogers OTA updates took me from 1.26 to 1.29 to finally 3.22 firmware. Everything at this point is stock and hopefully Rogers based, only modification that remains is S-OFF.
I need to S-ON for warranty purposes, I know how to S-ON, but I was wondering if it safe to S-ON considering I used a non-Rogers RUU to downgrade in the first place. I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
My bootloader is locked, no tampered flag, hboot 1.55, CID is no longer superCID but ROGER001 (specific to my carrier)
Your good
Ali812 said:
So my phone was S-OFF, superCID, custom firmware, running ARHD with TWRP recovery. I carried out the procedure to revert to 100% stock, I have a Rogers HTC One but a Rogers RUU doesn't exist, however I was able to get OTA updates after reverting to stock so I'm assuming the hboot, bootloader, recovery, stock ROM are all Rogers based.
However, when reverting to stock, I used an AT&T RUU to go down to 1.26 firmware and then Rogers OTA updates took me from 1.26 to 1.29 to finally 3.22 firmware. Everything at this point is stock and hopefully Rogers based, only modification that remains is S-OFF.
I need to S-ON for warranty purposes, I know how to S-ON, but I was wondering if it safe to S-ON considering I used a non-Rogers RUU to downgrade in the first place. I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
My bootloader is locked, no tampered flag, hboot 1.55, CID is no longer superCID but ROGER001 (specific to my carrier)
Click to expand...
Click to collapse
If you have changed your CID back to your carrier specific code you should be OK.
However, with the 4.4 update, there have been a few issues with the Bootloader not unlocking again, if you are sending your phone back under warranty for repair or replacement then your good to S-On, if you just want to set S-on for the hell of it (like me) I would hold fire for now.
Its will be your only remaining access to unlock the phone in one way or another.
Ali812 said:
I read somewhere that if I try to S-ON after using RUU that isn't the same as my carrier I will brick my phone, which is something I don't want to do. So is it safe to S-ON or am I at risk of bricking my phone?
Click to expand...
Click to collapse
Like I said, no bricks involved, but read below too.
zeushacker said:
if you are sending your phone back under warranty for repair or replacement then your good to S-On
Click to expand...
Click to collapse
if he tries to go s-off to s-on on hboot 1.55, then there is a high probability, that after a few reboots "tamper detected - rebooting" -> and the TAMPERED sign is back.
I wrote the guide in a specific order 1, then 2, then 3, etc, because of that reason.
If the OP wants to give it a shot, he can go ahead, maybe the "tamper detected" won't happen; if it does, he will have to s-off using rumrunner, and start the procedure again.
s-on is not needed on waranty, there are always some devices shiped from factory with s-off. my advice is to keep s-off.
Hi,
I was going to update the rom on my HTC One and add the most recent luna kernel but when i download it i didn't look at where the thread was coming from and i think i downloaded to another device. Now, im still able to flash any rom but the SIM Card isn't detected. I've tried a nadroid backup but when i flash the rom i had i get the same issue, no SIM card.
Terramoto said:
Hi,
I was going to update the rom on my HTC One and add the most recent luna kernel but when i download it i didn't look at where the thread was coming from and i think i downloaded to another device. Now, im still able to flash any rom but the SIM Card isn't detected. I've tried a nadroid backup but when i flash the rom i had i get the same issue, no SIM card.
Click to expand...
Click to collapse
Try flashing latest radio and maybe firmware, this will generally fix. Worst case you would need to backup and ruu.
Sent from my HTC One on some Awesome Rom..
Hey,
I was able to S-ON my device but now i don't know what to do. My HBoot is 1.44 could someone point me in the right direction? Im currently downloading RUU 3.04.651.2 which is the one i get from getvar version-main.
Terramoto said:
Hey,
I was able to S-ON my device but now i don't know what to do. My HBoot is 1.44 could someone point me in the right direction? Im currently downloading RUU 3.04.651.2 which is the one i get from getvar version-main.
Click to expand...
Click to collapse
... buddy why did you go for s-on is out of my understanding. people yearn to get s-off and you did the opposite. its ok. you can s-off later. Now relock your bootloader and run RUU. your phone will be up and running. then again go for s-off after unlocking bootloader and flashing custom recovery and root ...
Devilish_Angel said:
... buddy why did you go for s-on is out of my understanding. people yearn to get s-off and you did the opposite. its ok. you can s-off later. Now relock your bootloader and run RUU. your phone will be up and running. then again go for s-off after unlocking bootloader and flashing custom recovery and root ...
Click to expand...
Click to collapse
Its all good now , I did S-Off because i read on flashing RUU tutorials that i needed to be S-Off before i run RUU
Terramoto said:
Its all good now , I did S-Off because i read on flashing RUU tutorials that i needed to be S-Off before i run RUU
Click to expand...
Click to collapse
.. you got it all wrong. its not necessary to be s-on to run RUU. RUU will do good on both s-on and s-off. its the bootloader which matters and that too when s-on. In simple words, if device is s-on you HAVE to relock bootloader to RUU and if device is s-off, no need to bother about bootloader status ...
Devilish_Angel said:
.. you got it all wrong. its not necessary to be s-on to run RUU. RUU will do good on both s-on and s-off. its the bootloader which matters and that too when s-on. In simple words, if device is s-on you HAVE to relock bootloader to RUU and if device is s-off, no need to bother about bootloader status ...
Click to expand...
Click to collapse
Yeah! I just learned something today, thanks!!