read this: the purpose of this post is to let folks know that if you htcdev unlock with s-off,your device will go back to reading unlocked until you relock it,at wich time it will read relocked,just like before you s-offed.
what does this mean?! if you dont care about getting back to a locked state for warranty purposes,then it doesnt mean anything. if one of the big reasons that you s-offed in the first place was to get back to locked,then,as the title says,dont unlock with htcdev after s-off. you can install recoveries and hboots via hboot in a PH98IMG files,or you can install available patched hboots to enable engineering commands.
i hope this helps clarify it for those who were confused by the title. my intention was not to cause panic,simply to educate folks in what id found,as i know the subject of locked/relocked is very important to some.
_______________________________________________________________________________________
ok,i have been posting in several threads that the unlocking after s-off is no big deal. i still maintain that.
however...
on my other s-off,htcdev devices,reflashing the hboot/running an RUU makes the device locked again. after more discussion with con,i decided i better test if i was gonna keep saying it.
i stand corrected!
i started by flashing back the 2.11.000 hboot and unlocking it. i flashed it again. still unlocked.. hmmm. so i flashed jp patched hboot,now juopunutbear flashed 2.11 back. still unlocked. hmmm.
so i relocked. reflashed 2.11. still relocked. uh oh. flashed the eng hboot. now relocked eng 2.11.20005,lol... relocked engineering hboot. flashed the 2.05.0000 ship hboot. still relocked.
at this point i ran the entire RUU for 2.01.605.11. still relocked
i plan to try flashing the leak ruu,then 2.01.605.11 again,but for now,im tired. 6am comes very shortly.
i should have known this phone would somehow be different
moral of the story is that if you are one of the folks whom care about your hboot saying locked,dont unlock it
sorry for any misconceptions based on my experiences with other devices
scotty1223 said:
ok,i have been seen posting in several threads that the unlocking after s-off is no big deal. i still maintain that.
however...
on my other s-off,htcdev devices,reflashing the hboot/running an RUU makes the device locked again. after more discussion with con,i decided i better test if i was gonna keep saying it.
i stand corrected!
i started by flashing back the 2.11.000 hboot and unlocking it. i flashed it again. still unlocked.. hmmm. so i flashed jp patched hboot,now juopunutbear flashed 2.11 back. still unlocked. hmmm.
so i relocked. reflashed 2.11. still relocked. uh oh. flashed the eng hboot. now unlocked eng 2.11.20005,lol... unlocked engineering hboot. flashed the 2.05.0000 ship hboot. still relocked.
at this point i ran the entire RUU for 2.01.605.11. still relocked
i plan to try flashing the leak ruu,then 2.01.605.11 again,but for now,im tired. 6am comes very shortly.
i should have known this phone would somehow be different
moral of the story is that if you are one of the folks whom care about your hboot saying locked,dont unlock it
sorry for any misconceptions based on my experiences with other devices
Click to expand...
Click to collapse
I am betting you can s-on the phone then re s-off and have it say locked. Or someone could edit an hboot to just say locked.
Sent from my ADR6425LVW using XDA
nosympathy said:
I am betting you can s-on the phone then re s-off and have it say locked. Or someone could edit an hboot to just say locked.
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
im sure it can be edited,im sure thats how we became locked again after s-off. and yeah im certain re-s-off-ing would do it too
i dont personally care,my device has no mfg warranty and its kinda neat to me that it appears to stay unlocked thru up/downgrades,and if i want to run the eng or patched hboots,i still can.
i just wanted to prevent others who do care from becoming entrapped back in the situation because of other advice i may have given. should have tested first,spoke later
When I did my S-OFF I was on 2.11 hboot and the ICS firmware. I flashed the juonoptioeefianwefo hboot and then the ENG hboot and old firmware patch. My end result was it saying "locked" in hboot.
I was rather pissed off since I the reason I flashed the ENG hboot was so that it would say "unlocked" instead of juonoptionaofewhf.
My warranty is voided several times over in other ways* so it doesn't matter much to me and after the huge amount of time getting the darn wire trick to work I was rather proud to have my phone say S-OFF and "unlocked".
*apparently living in a high humidity area is enough to trigger the wetness seals.
jefffeely said:
When I did my S-OFF I was on 2.11 hboot and the ICS firmware. I flashed the juonoptioeefianwefo hboot and then the ENG hboot and old firmware patch. My end result was it saying "locked" in hboot.
I was rather pissed off since I the reason I flashed the ENG hboot was so that it would say "unlocked" instead of juonoptionaofewhf.
My warranty is voided several times over in other ways* so it doesn't matter much to me and after the huge amount of time getting the darn wire trick to work I was rather proud to have my phone say S-OFF and "unlocked".
*apparently living in a high humidity area is enough to trigger the wetness seals.
Click to expand...
Click to collapse
Yeah high humidity trips em lol. I had an iPhone 3G back in the day trip both the headphone Jack and charging port water markers on a 70% humidity day.
Sent from my ADR6425LVW using XDA
The number of things that can happen to invalidate your warranty really is annoying. My cousin has a completely stock Inspire that is stuck on hboot but AT&T won't touch it because it has a small ding in the case from when she dropped it.
After S-OFF (GB stock, amon ra, rooted system), I erroneously thought I needed to unlock. Then I locked the bootloader for any future OTA update and it showed Relocked.
I reinstalled the ENG hboot, but it still shows Relocked.
I asked in the sbear chat room, and the answer was
there is no simple way to get the ENG hboot to change from displaying Relocked to display just plain Locked.
But...It is just cosmetic and doesn't really matter.
Howard
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
I don't know what any of this means...
I just think this makes it more confusing for people..
Mine said 'Locked' after S-Off so I just unlocked it and everything seemed better..
Irieone said:
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
Click to expand...
Click to collapse
That is because you kept the stock hboot which doesn't allow for fastboot commands without being unlocked. By choosing one of Jp's hboot's or the eng hboot you could have installed recovery without unlocking. I did the same thing. So I went back to s-on and redid the s-off procedure and installed jb's hboot. Now I am s-off and locked again. Whew!
Sent from my ADR6425LVW using Tapatalk 2
Irieone said:
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
Click to expand...
Click to collapse
I second this. I had to unlock before I could flash recovery. I don't care that my phone says unlocked, just wanted to point out that for one reason or another some have had to unlock again.
Good usage of Smileys.
I agree with scotty, my hboot says locked and I have s-off so far I have flashed everything except for ruu's. Even recoveries worked.
Sent from my ADR6425LVW using xda premium
I was on the latest firmware and RezROM ICS. Performed S-OFF and never seen an option to install JB-Hboot so I didnt. At that time mine said UNLOCKED/TAMPERED.
Then after a couple of days of reading and trying to decide what to do next I decided to RUU down to the latest official and as soon as that was finished I went back to boot loader and it said LOCKED / S-OFF. I flashed the ENG Hboot with no issues and Now it says LOCKED / VIGOR PVT ENG S-OFF RL.
I also made a backup of RezROM before all this. Restored my backup, flashed the firmware patch, flashed PH that came with RezROM and rebooted and have had no issues at all.
I am not in a 4G area so I might actually have the issue others were having with 4G dropping out. Will have to wait and see.
zone23 said:
I don't know what any of this means...
I just think this makes it more confusing for people..
Mine said 'Locked' after S-Off so I just unlocked it and everything seemed better..
Click to expand...
Click to collapse
Ditto
I was/am on the stock GB firmware, completed S-OFF, phone said locked (still on stock GB HBOOT), I unlocked it ... no problems since.
HowardZ said:
After S-OFF (GB stock, amon ra, rooted system), I erroneously thought I needed to unlock. Then I locked the bootloader for any future OTA update and it showed Relocked.
I reinstalled the ENG hboot, but it still shows Relocked.
I asked in the sbear chat room, and the answer was
there is no simple way to get the ENG hboot to change from displaying Relocked to display just plain Locked.
But...It is just cosmetic and doesn't really matter.
Howard
Click to expand...
Click to collapse
I saw you sign on. Did they ever answer my question about running the tool multiple times?
Sent from my ADR6425LVW using XDA
Irieone said:
No offense to OP, but can you change the title of this thread? It scared me.
I ran the S-OFF method yesterday in 7 minutes with no issues. I was on the new firmware and BAMF 2.1. I chose to keep the 2.21 HBOOT. I had to unlock via HTC in order to flash recovery after performing the S-OFF method. Some folks are saying that you to do not need to unlock once you have S-OFF. All I can say is that I could not flash recovery without unlocking the phone.
Click to expand...
Click to collapse
No,I won't change the title. To some folks its important to stay locked. I will try and clarify the op later today.
You don't need to unlock to install a recovery. It's easily permanently flashed via a PH98IMG,or fastboot booted via the jpbear patched hboots.
Sent from my ADR6425LVW using XDA
dmoses1969 said:
I was on the latest firmware and RezROM ICS. Performed S-OFF and never seen an option to install JB-Hboot so I didnt. At that time mine said UNLOCKED/TAMPERED.
Then after a couple of days of reading and trying to decide what to do next I decided to RUU down to the latest official and as soon as that was finished I went back to boot loader and it said LOCKED / S-OFF. I flashed the ENG Hboot with no issues and Now it says LOCKED / VIGOR PVT ENG S-OFF RL.
I also made a backup of RezROM before all this. Restored my backup, flashed the firmware patch, flashed PH that came with RezROM and rebooted and have had no issues at all.
I am not in a 4G area so I might actually have the issue others were having with 4G dropping out. Will have to wait and see.
Click to expand...
Click to collapse
I'm in the same situation. There's a thread here on how to fix it but I guarantee your 4G is whacked. I flashed back to a GB stock ROM then flashed an ICS ROM. Seemed to work okay when in my 3G only area but I visited a 4G area yesterday and it was just messed up. I flashed the latest GB RUU and did a reset from the stock hboot, flashed JuopunutBear hboot for GB, then AmonRa 3.15 and CleanROM DE. I'm going back to a 4G area tomorrow so if it doesn't work I'll post in that thread. Could just be me but everything about the phone seems better/cooler/faster after the RUU.
TheEnzyteGuy said:
I agree with scotty, my hboot says locked and I have s-off so far I have flashed everything except for ruu's. Even recoveries worked.
Sent from my ADR6425LVW using xda premium
Click to expand...
Click to collapse
I've flashed JuopunutBear hboot (GB and ICS), eng hboot, stock hboot, AmonRa, a nandroid, and a few roms after locked/s-off and have had no problem. Just flash eng or juopunutbear hboot before flashing recovery and you're good to go.
Edit: I was on the appropriate firmware when flashing the GB and ICS hboots.
Recovery can still be flashed as a PH file on the regular HBOOT.
D
HTC having last laugh?
Sent from my ADR6425LVW using xda premium
Not to sound like a complete noob, but I have a few concerns that I cannot find the answer to.
Regarding the leak. I wanted to load is as a IMG file through stock hboot. However, will I be able to unlock, root and s-off the device on the ICS leak, or does this all need to be done before I load the leak. Reason I'm asking is because I dont want to S-off if I dont have to, however I want to be able to go back to stock if I need to. I know I need to be s-off to get back to GB from ICS.
Does unlock root and s-off need to be done before I load the leak?
You cannot downgrade without S off. It's a one way street if you upgrade and stay S on. You'll be able to unlock still though if you upgrade now.
ok, just to be clear..
I do not need to s-off before I upgrade to the leak? S-off, root, and unlocking can be done while running the leak, correct?
I am only going to s-off, unlock and root if I happen to run into issues on the leak and need to downgrade.
you should s-off before loading the leak, while the s-off procedure does work on the leak... you'll cover your ass by s-offing now, in case something happens during the leak install.
once s-off on GB, upgrading to the 3.14 leak is a snap. you can also leave the phone **locked** after doing the s-off procedure too, once you are s-off you can flash whatever and still be locked.
the 3.14 leak can be rooted. Just re-install amonRA after flashing the leak, and install su/superuser there, just like with GB.
come to irc in my sig if you need real-time help.
You are correct in your assumptions but like it was mentioned...I would highly recommend that you S-OFF before flashing the firmware.
Is there anyway to remove the "Tampered" sign in flashboot?
I followed this guide after s-offing:
http://forum.xda-developers.co/showthread.php?p=25167284#post25167284
But it's still there after I rebooted into fastboot.
EDIT: After a little bit of thinking I realized the reason why it says Tampered is because I'm on the ICS leak. Is there a stock RUU I can install that will get rid of the Tampered?
2.01.605.11 stock RUU will get you back to stock locked bootloader GB with S-OFF
http://www.filefactory.com/f/c2e320ee1d5c7886/
If I remember correctly that's a thing with ICS it happened on the .22 leak but I'm on the newest leak and on amon ra 3.15 and mine doesn't say tampered anymore. If you want to be on ICS try flashing the newest one.
Sent from my ICS Rezound
z0mghii said:
Is there anyway to remove the "Tampered" sign in flashboot?
I followed this guide after s-offing:
http://forum.xda-developers.co/showthread.php?p=25167284#post25167284
But it's still there after I rebooted into fastboot.
EDIT: After a little bit of thinking I realized the reason why it says Tampered is because I'm on the ICS leak. Is there a stock RUU I can install that will get rid of the Tampered?
Click to expand...
Click to collapse
Ah, got a URL typo, you have .co instead of .com
Assuming your ultimate goal is total stock appearance for warranty, not just eliminating Tampered flag? No real reason to hassle with S-on or care about the flag otherwise.
Use the latest "officially" released build in the guide, which is indeed the 2.01.605.11 GB OTA. Going to PM Scotty to clarify that, stress it must be an "official" RUU in the wording of that step.
You need to do the S-off procedure again, then redo S-on guide with the proper RUU. Then you're good
FWIW, I flashed the latest leaked ICS RUU after S-off and the "tampered" flag is no longer on.
douger1957 said:
FWIW, I flashed the latest leaked ICS RUU after S-off and the "tampered" flag is no longer on.
Click to expand...
Click to collapse
Ah, retracted my statement on ICS hboots and edited last post... Y'all are right, 2.25 stock hboot doesn't have the flag
Still hardly any good reason to S-on except for warranty, the goal and methods of the post conflict with the thread title lol
Thanks guys. Yep I was just trying to go back to warranty status. Appreciate the help!
I would just slam the phone into the pavement and just return it that way, or say it ws stolen
Hello everyone
Sorry for a newb question, but, how can I unroot so that I can take all the OTA updates and get the official ICS update from Sprint/HTC. I dont care about losing root as I will be replacing the phone come October. I just want it back to stock and running on stable factory ICS.
I currently am Revolutionary HBOOT-1.40.110 / S-OFF / RADIO 1.06.00.1216.
Thanks!
Well you can first do a search, as this has been answered probably at least a hundred times on here. After you do that, you would realize you need to run a stock RUU to relock the bootloader.
http://forum.xda-developers.com/showthread.php?t=1194053
you just have to find the zip file but follow those steps did it a while back
Is there an unroot method for hboot 1.5 with s-off? I used Juopunutbear to get s-off.
I relocked the bootloader then ran the stock RUU and that did the trick
Sent from my PG86100 using xda premium
Thanks guys. I ran the RUU, then did all the OTA updates. Im now on official stock ICS, bootloader 1.58, relocked, and still S-OFF
is it possible to unroot but keep s-off? i want to sell my phone but i would prefer it to be kinda pseudo-unrooted so i can easily revert back to s-off. I should probably just completely unroot though.
Is possible to reunlock the 1.58 hboot after we take the OTA using HTC dev method?
Current: JBear, S-off, HBoot 2.21.2121, Radio 1.22.10.0310r, Running 3.14.605.12 71ORD.
I don't want to brick. What are the steps needed from this starting point to get to a global rom? Came from Moto phones where we didn't seem to have so many options. Will being JBear cause issues? Will I lose s-off?
cawaller said:
Current: JBear, S-off, HBoot 2.21.2121, Radio 1.22.10.0310r, Running 3.14.605.12 71ORD.
I don't want to brick. What are the steps needed from this starting point to get to a global rom? Came from Moto phones where we didn't seem to have so many options. Will being JBear cause issues? Will I lose s-off?
Click to expand...
Click to collapse
I was in your same state two days ago I just downloaded and ran the global ruu twice and everything went fine. Just make sure after you run the ruu twice before the first boot of the phone make a factory reset from within hboot
No you wont get s on after the global ruu. You stay s off but locked but all you have to do is flash the jbear hboot and you are unlocked and s off.