Just a quick question. I have a One S on T-mobile and Ive unlocked the bootloader, rooted the stock rom, changed the the CID, sim unlocked the device, relocked the bootloader and ran the the stock RUU. Its totally unbranded now and running just fine.
However in the bootloader it shows **Relocked** Is there a way to show **Locked** again? Ive tried searching, but cant find a definitive answer. Help is appreciated.
Not without S-OFF as far as I am aware. However, for HTC warranty purposes, relocked should be fine.
Thanks, not really an issue as such, but it would of rounded off my unbranding adventure nicely
Can't change it back to locked until we get s=off and ability to flash a custom hboot
Sent from my HTC VLE_U using xda premium
Related
Please please forgive the newb question, but once the bootloader is officially unlocked by HTC's method (basically entering a token you pull from your phone, and then flashing a .bin file they send you based on that token), is it reversible? I.E. is it possible to re-lock it back to factory status? I'm assuming not, but can't find any hard evidence one way or the other...
Apparently someone has said you can re-lock it but I've not used it. Better using Revolutionary IMO
Well you can do a "simple" re-lock just to ensure noone else can make changes to it with "fastboot oem lock" - but it's not the factory lock. The bootloader simply says "re-locked" instead of "unlocked", or compared to the factory "locked".
But I was thinking in terms of reverting it truly back to factory status. Again, I don't think it's possible (without HTC's intervention anyway), given the nature of how it was locked, but need someone smarter than me to confirm that suspicion.
So basically, using Super CID, you can run the RUU.exe from the bootloader only, and get your phone back to 100% stock, but it'll still be unlocked. So I'm guessing there is no way to reverse HTC's unlock process.
jntdroid said:
So basically, using Super CID, you can run the RUU.exe from the bootloader only, and get your phone back to 100% stock, but it'll still be unlocked. So I'm guessing there is no way to reverse HTC's unlock process.
Click to expand...
Click to collapse
I flashed the android revolution rom with my device unlocked through htc website, I cannot flash back to stock, I tried the RUU to bring me back to 1.27 and 1.29 and error'd on both of those. I am not sure how to get back to stock. I tried several times. I also cannot get my security to turn off in the bootloader after I unlocked through htc. Has anyone figured out how to do this? I tried the revoltionary.io tool and successfully used the tool only to reboot and see the S-ON in bootloader mode. CRAZY I suggest for anyone to turn their S-OFF using revolutionary.io before they ever attempt to unlock the bootloader through htc. What I am experiencing is error under the wifi switch I cannot seem to get wifi working with any of the roms, probably due to the kernel or not having s-off in bootloader. I tried different and stock kernels only to have the same problem.
Read this if you want more info: http://forum.xda-developers.com/showthread.php?t=1290395
Has ANYBODY tried the goldcard method to reflash to stock? Take the rom.zip from RUU and flash in bootloader
So ive gone back to stock htc orange ROM with the CID ORANG001 and i am now also S-On after being on ARHD, after probelms with the phone in case i need to send it back, so by the looks of what you are saying I am not actually back to factory status? So will HTC be able to tell in the case that i have to send it back fro repair or whatever? If so i also need to know how to re lock and get back to complete factory status!?
EDIT: im pretty sure bootloader was already available on the phone, and my firends incredible s, he is able to access bootloader without doing anything to his phone
Gold card doesn't work, otherwise we could've used it before S-OFF
gtcalder said:
So ive gone back to stock htc tmobile ROM with the CID ORANG001 and i am now also S-On after being on ARHD, after probelms with the phone in case i need to send it back, so by the looks of what you are saying I am not actually back to factory status? So will HTC be able to tell in the case that i have to send it back fro repair or whatever? If so i also need to know how to re lock and get back to complete factory status!?
EDIT: im pretty sure bootloader was already available on the phone, and my firends incredible s, he is able to access bootloader without doing anything to his phone
Click to expand...
Click to collapse
Where is this CID ORANG001 you are referring to? Do you have a link? And as far as I know you can unlock the bootloader but there is currently no true relock.
droiddv said:
Where is this CID ORANG001 you are referring to? Do you have a link? And as far as I know you can unlock the bootloader but there is currently no true relock.
Click to expand...
Click to collapse
Hi, list of CIDs for each ROM..
http://forum.xda-developers.com/showthread.php?t=1195475
OK, so I am learning android (using HD2 now) and from what I understand when you use the htc boot loader unlocker you end up with a "tampered" warning somewhere that will let htc or your carrier know that you have unlocked your bootloader.
Does having s-off help you to be able to trick the phone from knowing that you have been into it if you flash it back to stock?
I am just worried about keeping insurance on the phone if once I unlock or s-off they will no longer cover it.
Sent from my NexusHD2 using XDA
I think that particular device will say, tampered. Soff is like security off you can fash roms and do many things with soff but no it does not trick the device into thinking its not tampered. With my device I can s on return to stock but I'm not sure about yours.
It might have tampered marked on it.
Sent from my HTC Sensation Z710e using xda premium
Yes that will void warentee
Sent from my HTC Sensation Z710e using xda premium
tobiascrystal said:
OK, so I am learning android (using HD2 now) and from what I understand when you use the htc boot loader unlocker you end up with a "tampered" warning somewhere that will let htc or your carrier know that you have unlocked your bootloader.
Does having s-off help you to be able to trick the phone from knowing that you have been into it if you flash it back to stock?
I am just worried about keeping insurance on the phone if once I unlock or s-off they will no longer cover it.
Sent from my NexusHD2 using XDA
Click to expand...
Click to collapse
It doesn't set a "tampered" flag. The stock bootloader has a caption at the top of *locked*. When you use htcdev to unlock the bootloader it will change that caption to *unlocked* and it cannot be undone.
S-off, on the other hand, does not notify HTC or your carrier of what you have done. It is also reversible if you really need to set things back to full stock.
realsis said:
Yes that will void warentee
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
GROGG88 said:
It doesn't set a "tampered" flag. The stock bootloader has a caption at the top of *locked*. When you use htcdev to unlock the bootloader it will change that caption to *unlocked* and it cannot be undone.
S-off, on the other hand, does not notify HTC or your carrier of what you have done. It is also reversible if you really need to set things back to full stock.
Click to expand...
Click to collapse
When you use HTC Dev to unlock your bootloader it does show Unlocked on the Hboot screen. But if you re lock the bootloader it displays re locked on the Hboot screen and not locked as it is originally. S-off can be reversed with out any trace of it being S-off. And now that the unbricking project has come up with a way to recover your de ice if going S-on soft bricks your device it is way less dangerous now.
At realsis, think about S-off as being like HSPL for the HD2.
I believe someone has figured out what was being set differently, and you can in fact return to "locked"
ziddey said:
I believe someone has figured out what was being set differently, and you can in fact return to "locked"
Click to expand...
Click to collapse
Go on........
Don't know if this works for the Sensation, but if someone is trying to go back to locked hboot, give it a try.
Go back to totally stock. Flash a RUU, preferably GB so that you have an earlier hboot that can be easily S-OFFed again.
fastboot oem write secureflag 3
Reboot and you should be S-ON again. AGAIN, MAKE SURE YOU ARE TOTALLY STOCK WITH A SHIP HBOOT OR YOU WILL BRICK.
Use revolutionary to S-OFF again. Hopefully, you will be locked at this point.
If not, repeat, but use JuopunutBear to S-OFF.
If you're still unlocked, this method doesn't work on the Sensation.
I have read various guides, and eventually taken the plunge to downgrade my bootloader.
htcDev Unlock
Goldcard
Install oldest RUU
S-OFF using revolutionary
Flash CWM recovery
Backup Stock 2.33 ROM with Sense
Install CM9
Feeling quite pleased with myself, even though you guys have really done all the hard work, I've just followed the steps!
What I can't find is this;
If I go back to the Stock ROM and updates are offered OTA, if I accept, will this, not only bring me back to 2.3.5 with Sense 3.0, but also change my bootloader back to 2.00.0002 Locked and S-ON ?
Unfortunately it will be *RELOCKED* and S-ON
Sent from my HTC Desire S
amidabuddha said:
Unfortunately it will be *RELOCKED* and S-ON
Click to expand...
Click to collapse
What he said. If you wanted to remain "locked" and not "relocked" - you should have avoided unlocking the bootloader, and should have used temp-root for misc_version.
Ok, what are the inplications of being 'RE-LOCKED'
Like CM9, but get the feeling development stalled, also certain apps won't work Nat West being one, though I suspect that is to do with their development.
Thinking about going back to Stock. If I do this via OTA, my bootloader will be upgraded back to 2.00.0002, 'RE-LOCKED' and S-ON, then wait for official OTA upgrade to ICS, which seems not to be happening as per HTC announcements. Even then I may have issues with apps that haven't been coded to deal with it.
If I am 'RE-LOCKED' can I not use htcDev again, or am I stuck with the Official bootloader etc and unable to load other ROMS, or can I just repeat the processes I have been through already?
I have also been reading about unlocking with an XTC Clip, where would I get this done, Is this a better solution? etc etc..
No issues with RELOCKED except that your warranty is gone.
If you have no warranty you can go for XTC Clip, since permanent S-OFF will give you more freedom in terms of modifications. Personally I consider flashing boot.img separately each time as annoying.
As per the unlock again, it should be possible, but I am not sure if this can be done by a fastboot command or the unlock token has to be flashed again.
Sent from my HTC Desire S
When I unlocked mine I remember reading somewhere that the token would need to be used again if the phone was re locked. So I kept it just in case
Hi guys, I wanna ask something. I hope you explain very well
My previous DS UNLOCKED with htcdev and S-ON. Then I downgrade and S-OFF but now LOCKED. Do I have to unlock it again? If yes, why? If not why?
Sent from my HTC Desire S
LOCKED or UNLOCKED marks the bootloader state.
UNLOCKED S-ON bootloader allows flashing ROM, recovery and kernel (with some limitations). LOCKED S-ON bootloader allows nothing.
When you have S-OFF, this mark doesn't have any meaning. S-OFF bootloader allows flashing whatever you want.
Since all HTC phones use the same marking from a long time ago, you can look for a thousand guides on the internet that will explain it much better. If you want to know things - search more, ask less. Until you get to the point when you search and can't find any answers.
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!