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
Something has been bothering me for the past two days. After achieving S-Off I went ahead and unlocked the boot loader via HTCDev (Noob Tool). Now after reading some post it seems I made a mistake Hboot currently says : unlocked and S-off and I also installed JB Hboot now I kind of want to go back to locked but also S-off ,can anybody give me some good directions on how to achieve this?
Also the main reason for this is that I think i messed up my proprietary port on my rezound and might have to take it back in the future. Just moving the phone around with the USB cable attached to my PC I constantly get disconnect and connect sounds on windows and loose inter SD access and Ext also. I just want to take precautions if I really do take it back so I can replace it and just S-On again.
Also I think I twisted the port while it was attached to the USB cable cause I slept on my phone while charging
What do you mean LOCKED but s-off? LOCKED means S-On, no such thing as locked and s-off
Do this for warranty exchange http://forum.xda-developers.com/showthread.php?p=25167284#
fenixnr said:
What do you mean LOCKED but s-off? LOCKED means S-On, no such thing as locked and s-off
Do this for warranty exchange http://forum.xda-developers.com/showthread.php?p=25167284#
Click to expand...
Click to collapse
I'm locked with S-Off. So I think there is such a thing.
fenixnr said:
What do you mean LOCKED but s-off? LOCKED means S-On, no such thing as locked and s-off
Do this for warranty exchange http://forum.xda-developers.com/showthread.php?p=25167284#
Click to expand...
Click to collapse
Thats actually really wrong. S-Off is S-Off. Unlocked gives you access to additional fastboot commands (there are a couple hboots in the Dev section that do this without changing the locked status).
[edit]
Correction, you need to S-Off again to become locked. There is a thread in the dev section about setting S-On (it's easy).
CAUTION: Make sure you are on the stock hboot when you S-On. If you S-On the GB Eng hboot or the Juponutbear hboot, you WILL brick your phone.
Sent from my ADR6425LVW using Tapatalk 2
fenixnr said:
What do you mean LOCKED but s-off? LOCKED means S-On, no such thing as locked and s-off
Do this for warranty exchange http://forum.xda-developers.com/showthread.php?p=25167284#
Click to expand...
Click to collapse
Everything you just said was wrong. Normal state after achieving s-off is a locked bootloader. Locked won't matter because there are no longer any security checks. You can essentially flash whatever you want.
Sent from my Dell Streak 7 using Tapatalk 2
Just to clear this up for you, if you unlocked after achieving s-off you will not be able to lock again without returning to s-on then back to s-off. If you try to lock now using fastboot oem lock you will end up "relocked".
Sent from my ADR6425LVW using XDA
fenixnr said:
What do you mean LOCKED but s-off? LOCKED means S-On, no such thing as locked and s-off
Do this for warranty exchange http://forum.xda-developers.com/showthread.php?p=25167284#
Click to expand...
Click to collapse
Duuuude! Now you know. Learning something new every day is a good thing.
trickster2369 said:
Duuuude! Now you know. Learning something new every day is a good thing.
Click to expand...
Click to collapse
You know, in retrospect, thats a much nicer way to about it.
Sorry I was a d*ck
Sent from my ADR6425LVW using Tapatalk 2
HI! i rooted my device some time ago,when i had hboot 1.49.007 following this.after some time i had to unroot it because i had to take it into warranty(IN MY COUNTRY AN HTC PHONE IS WARRANTY VALID IF IT HAS A "LOCKED" BOOTLOADER{not relocked} AND S-ON).I simply made it "LOCKED" S-ON following this.
Now the question.My brother recently thought he wants to root but he has HBOOT 1.53.007(did the OTA).He doesn't want to lose his warranty since the phone is quite new(6 months old).As far as I seen yet there are only methods implying that you unlock the bootloader via htcdev.com .As far as I know that implies that you will have a "RELOCKED" bootloader forever.I also saw some htcdev unlock methods and after them downgrading to HBOOT 1.49.Is it possible to achive unlocked s-off and later,if he needs it,to achive locked s-on?
THANKS!
It is. Check the developement forum. Near the top there are some stickies on how to achieve s-off which is more reversible than HTCdev unlock method. Juaponutbear seems to be the easiest but that's just my opinion. As with any rooting method, these carry the risk of permanantly bricking your device. Read all the documentation before trying it.
Sent from my PG86100 using xda app-developers app
I just successfully performed S-off but my bootloader changed to "locked". Is that normal?
Also, I declined to install jp modified hboot because I was not sure what it was. Do I have to install another hboot after S-off?
S-OFF > unlocked bootloader. You don't need an unlocked bootloader when you are S-OFF.
With a stock locked bootloader you won't be able to use most fastboot commands. That's the purpose of the jpbear hboot. It allows you to use them without unlocking. However, if you ever go back S-ON, you have to have a stock bootloader or you'll brick, so you should only use a modded hboot if you need the fastboot commands. Otherwise, stock is just fine.
I read a lot about this subject in this thread last night:
http://forum.xda-developers.com/showthread.php?t=1852228
Could give you some useful info on the pros and cons of flashing the j-nut hboot or not and keeping locked or unlocking.
shrike1978 said:
S-OFF > unlocked bootloader. You don't need an unlocked bootloader when you are S-OFF.
With a stock locked bootloader you won't be able to use most fastboot commands. That's the purpose of the jpbear hboot. It allows you to use them without unlocking. However, if you ever go back S-ON, you have to have a stock bootloader or you'll brick, so you should only use a modded hboot if you need the fastboot commands. Otherwise, stock is just fine.
Click to expand...
Click to collapse
Sorry for the noob questions. I don't know much about the tech, I can only follow the instructions. So, do I need a modified bootloader if I want to flash Rom that require S-off or is the stock bootloader OK? I want to flash a Rom for which I need to be S-off and on the latest RUU.
I'd guess that 99% of people who do the jbear s-off procedure take the modified hboot as an uniformed choice. They figure if jbear provided this, then it must be great.
If you do not install the jbear hboot, you should unlock your bootloader using htcdev unlock bin file. You will have the following benefits with s-off, stock unlocked hboot:
o can ruu with unlocked bootloader. you will never need to relock before performing an ruu.
o install ROMs easier without the need to install kernels via ph98img.zip. method
o able to fastboot flash recovery and boot/kernel
o less bricking risks in the future
being s-off with the locked jbear modified hboot has the advantages of:
o displaying Locked, but can do everything an unlocked bootloader can do.
o makes it easier to lie to Verizon that you never tampered with the phone, never unlocked, never ROMed, it is not your fault the phone is bricked.
o able to fastboot flash recovery and boot/kernel
o able to fastboot flash hboot/bootloaders and some other fastboot commands that no developers are using.
One guy went so far as to hexedit his hboot to display "s-on" and "locked" to hide the fact that he is s-off and unlocked. He bricked his phone on his first attempt. got phone insurance to replace his phone. Then he got others to test his later attempts which work and didnt brick. So if you want to lie with impunity to Verizon, don't use jbear hboot, instead use this guy's hboot. you'll find it in the developer's forum.
Personally I take great care and deliberation about what changes I make to my phone because I do not plan on lieing to get someone else to pay for my mistakes.
Wendemixda said:
I just successfully performed S-off but my bootloader changed to "locked". Is that normal?
Also, I declined to install jp modified hboot because I was not sure what it was. Do I have to install another hboot after S-off?
Click to expand...
Click to collapse
Yes it is normal....see what the other guys say about jb hboot.....for me, since I haven't and don't plan on having to use fastboot commands, I just left it locked with stock hboot.
How can I reunlock mine? S off locked bootloader
An old HTC Incredible 4G
EzraDi said:
How can I reunlock mine? S off locked bootloader
An old HTC Incredible 4G
Click to expand...
Click to collapse
This is the Rezound forums. You should find the Incredible forums and ask there, although I think a lot of Rezound users used to have Incredibles, but it's pretty dead here now that the phone is 4 years old.
feralicious said:
This is the Rezound forums. You should find the Incredible forums and ask there, although I think a lot of Rezound users used to have Incredibles, but it's pretty dead here now that the phone is 4 years old.
Click to expand...
Click to collapse
Thank you
Pretty much subject says everything. But here's is my situation.
What I did earlier:
Unlocked Bootloader
Tried S-on with Firewater - didn't work - gave up- didn't spend money for getting S-off via moonshine
Installed TWRP
Installed custom roms
NOW, I need to go back to slock and claim some warranty issue (speakers too harsh)
Here's is an at&t RUU
http://forum.xda-developers.com/showthread.php?t=2757462
Can I go back to stock from here? Do I certainly need S-off? Do I just run RUU exe?
Please help!!
Thanks!
Since you are S-On I believe you have to relock your bootloader in order to run the AT&T RUU
Sent from my HTC One_M8 using Tapatalk
Jano342000 said:
Since you are S-On I believe you have to relock your bootloader in order to run the AT&T RUU
Click to expand...
Click to collapse
That's correct.
Also to the OP, note that AT&T only voids warranty for physical or water damage. They don't care about software mods, although it is a good idea to return to as close to stock as possible before requesting warranty exchange.
RUU is a good way to do so. S-on is fine, but you have to relock the bootloader. The bootloader will then say RELOCKED instead of UNLOCKED or LOCKED. No other evidence of modding should remain after the RUU.