Hey Guys. I have a slight problem. Or you can call it curiosity.
When i got my GSM Evo 3D, it had everything stock on it. Locked, S-ON, 1.53.0007 Hboot. I unlocked the bootloader using HTCdev, S-OFF with wire trick, downgraded Hboot to 1.49.0007, installed 4EXT recovery and proceded to flashing roms.
Today, after briefly trying Mwakious's ROM, i noticed in the bootloader that it sais " ***LOCKED*** ". The Hboot version and S-OFF remained the same. How is this possible? Can it get Locked just like that? I never had any problems with flashing any ROM, and i still don't.
Can (or should I, considering i can still flash any ROM/kernel without issues) unlock it again with the HTCdev method? Or do i have to flash the stock RUU first? Will it take me back to the Locked, S-ON and 1.53.0007 Hboot if i do that?
Thanks in advance.
It's not a problem. It's always locked after wire trick, if I remember it right....
Benik3 is right. I'm sure if you had checked the bootloader immediately after wire trick it would have showed locked
Thank you. I considered that it might have been like that since after the wire trick, but i just didn't notice it.
Just "panicked" a bit when i saw it, because i thought an unlocked bootloader was a must when flashing custom roms.
Kind of the same problem here, but mine showed unlocked until after i did the update. I had switched to hboot 1.50 for a rom, so not sure if that did it? But i flashed the eng hboot 1.04, and now it doesnt say locked or unlocked?? I am cdma..
whbisondtr said:
Kind of the same problem here, but mine showed unlocked until after i did the update. I had switched to hboot 1.50 for a rom, so not sure if that did it? But i flashed the eng hboot 1.04, and now it doesnt say locked or unlocked?? I am cdma..
Click to expand...
Click to collapse
You're still unlocked, but the custom hboots like ENG just mask that status on the top line of the bootloader screen.
If you want to verify that and set your bootloader back to the "locked" status, the information and tools you need are in this post.
ramjet73
Related
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
I had my HTC amaze unlocked with s-off and a modded hboot I then updated to a new ICS firmware to run ICS however when the firmware flashed to my phone it locked my phone and reset my hboot but still kept s-off. Is there anyway to unlock my phone again? If anyone has any help please let me know I already tried to unlock it through HTdev website and it did not work!!!
If you are s=off, then you don't need to unlock your bootloader. I'm assuming you have eng bootloader, and with that, you don't need to unlock anything.
Sent from my HTC_Amaze_4G using xda premium
pharmhand said:
I had my HTC amaze unlocked with s-off and a modded hboot I then updated to a new ICS firmware to run ICS however when the firmware flashed to my phone it locked my phone and reset my hboot but still kept s-off. Is there anyway to unlock my phone again? If anyone has any help please let me know I already tried to unlock it through HTdev website and it did not work!!!
Click to expand...
Click to collapse
HTC dev website is the way i did it, and it worked perfect for me. What method did you use that didn't allow you to unlock your phone?
Sent from my HTC_Amaze_4G using Tapatalk 2
If any of you read correctly, he said he unlocked it before, therefore, all he has to do is place the unlock_code file in hasoon's tool's data folder and run the unlock bootloader option, voila he's back to being unlocked, though the relocking sounds kind of odd, but it could probably be due to the hboot he was using, I'm guessing was Juopunutbear's or something.
Dark Nightmare said:
If any of you read correctly, he said he unlocked it before, therefore, all he has to do is place the unlock_code file in hasoon's tool's data folder and run the unlock bootloader option, voila he's back to being unlocked, though the relocking sounds kind of odd, but it could probably be due to the hboot he was using, I'm guessing was Juopunutbear's or something.
Click to expand...
Click to collapse
I did read it, the old unlock bin does not work with new ics so he has to redo everything once more....
Sent from my HTC_Amaze_4G using Tapatalk 2
Well my old unlock bin worked fine for me re-unlocking on ICS, guess I was lucky, okay cool, my bad.
Yes I had hboot from Juopunutbear when I did the s-off it asked to install his hboot but after I upgraded it changed my hboot back to 1.93.0002 and it is SHIP s-off not eng which I am not totally sure what the difference is but is there a way to change SHIP back to ENG????? I am going to give HTCdev another chance and see what happens... thanks for the input and help
ok so I just tried HTCdev again and it unlocked my phone however it did a hard reset the only thing I have to do now is to have eng s-off instead of ship s-off.
pharmhand said:
ok so I just tried HTCdev again and it unlocked my phone however it did a hard reset the only thing I have to do now is to have eng s-off instead of ship s-off.
Click to expand...
Click to collapse
Just flash the eng hboot via bootloader, though you don't need to, unless you plan to do fastboot commands, which the average user doesn't have much need for, hasoon's tool does everything you need, recovery, root, etc, though I do recommend 4EXT recovery, which you can easily install after obtaining root.
So I bought a phone from a guy on Craigslist, while it works fine, there's something weird here. What I want to do is have it S-OFF, but here's whats up:
Bootloader is HBOOT 2.21.0000. It says ***UNLOCKED*** but also it says ***TAMPERED***. Also it says VIGOR PVT SHIP S-ON RL.
Everything seems to be working fine; it currently has CleanROM 4.3 on it. I'm afraid to start doing anything until I know where to start. I *THINK* what I need to do is the following:
1. fastboot oem lock the bootloader
2. Flash latest ICS leak RUU twice.
3. Follow the Juopounut guide for S-OFF using the 2.21.0000 modified HBOOT
Does this sound right? Thanks for your help!
If its already unlocked, stay unlocked. Relocking it is going backwards toward s-off. Once s-off you will have a locked bootloader. I did not install the jbear modified hboot. I installed Amon ra as a ph img after s-off and ics ruu
You should just follow the jbear s-off instructions since you already have unlock
S-off prior to ics is my preferred method, if something goes wrong with the ruu, you're stuck.
Also, no need to unlock once you have s-off
I got it. I wanted to go back to the newest leak and then proceed. I flashed the latest leak RUU and then re-unlocked.
The ***TAMPERED*** appears once I flashed the amon-ra recovery. Guess thats normal on the ICS builds...
Mine does not show tampered. I am s-off, locked, ics 3.14 firmware with ruu hboot, amon ra recovery, running newts one xxx
in_retrospekt said:
Mine does not show tampered. I am s-off, locked, ics 3.14 firmware with ruu hboot, amon ra recovery, running newts one xxx
Click to expand...
Click to collapse
Yep mine doesn't either. I'm just guessing but I think it might only been the 3.11.605.22 leak that did that.
Sent from my Sense4 ICS Rezound
Mine doesn't show it now that its truly S-OFF. Thanks all!
Guys, I didn't find any explanation for this here, and I still have a problem. I have HTC EVO 3D GSM..
I was on 1.53 hboot and I unlocked bootloader via HTCdev.com. After that I wanted to do s-off with "wire trick"..I successfully made it. I wanted to install Disarmed Toaster ROM, but I had a bootloop. So, I downloaded new PG86IMG.zip, downgraded hboot, and now I have 2.3 GB android, with LOCKED BL and S-OFF..now..How do I get UNLOCKED bootloader..I tried with htcdev.com again, but failed..There is error failed: remote not allowed
Hope you can help me..
This post explains the situation you are describing on the CDMA version, and I suspect it is very much the same on the GSM model. If you want to read the original explanation by Unknownforce it is here.
You should be able to use the JBear hboot for your phone instead on unlocking the bootloader, or if you need an older version I think I read there is a GSM version of the Revolutionary bootloader.
ramjet73
You just installed JBear again and you will gain UNLOCKED. Or you should Unlocked again w/ HTCdev.
Sent from my PG86100 using xda premium
I dont think locked should be a problem as long as you are s-off. Someone correct me if i'm wrong but i believe you can flash roms/kernels etc now.
why do you need it to be unlocked?
EM|NEM said:
I dont think locked should be a problem as long as you are s-off. Someone correct me if i'm wrong but i believe you can flash roms/kernels etc now.
why do you need it to be unlocked?
Click to expand...
Click to collapse
This is correct. You do not need boot loader unlocked I'd you are s-off.
Sent from my PG86100 using xda app-developers app
EM|NEM said:
I dont think locked should be a problem as long as you are s-off. Someone correct me if i'm wrong but i believe you can flash roms/kernels etc now.
why do you need it to be unlocked?
Click to expand...
Click to collapse
raptoro07 said:
This is correct. You do not need boot loader unlocked I'd you are s-off.
Click to expand...
Click to collapse
Some people still seem to unlock the bootloader after gaining S-OFF so they can run fastboot commands like "flash" and "erase". If you try to run those commands with a locked bootloader you will get the "failed: remote not allowed" error even with radio S-OFF.
The wire trick leaves the bootloader locked, but choosing the JBear hboot or flashing another custom version (engineering or Revolutionary) is a better way to get access to those commands than unlocking the bootloader again.
ramjet73
Thank you all..I did what had to be done..Now, I have s-off with Jpbear hboot..mwakious rom..and it works like charm ..This is my first ROM installed on HTC EVO 3D..and I hope I will get used to install new ones ..
ramjet73 said:
Some people still seem to unlock the bootloader after gaining S-OFF so they can run fastboot commands like "flash" and "erase". If you try to run those commands with a locked bootloader you will get the "failed: remote not allowed" error even with radio S-OFF.
The wire trick leaves the bootloader locked, but choosing the JBear hboot or flashing another custom version (engineering or Revolutionary) is a better way to get access to those commands than unlocking the bootloader again.
ramjet73
Click to expand...
Click to collapse
what would we do without you sir. I learn something new here everyday
In an effort to upgrade bootloader and software to be compatible with cm11.. I used vipeRUU to go from 1.12 bootloader to 2.09 bootloader with the 3.17.651.471 software, whats confusing me is bootloader still says ..Unlocked ..and S-off after running ruu ..bootloader has changed and so has the software... (i was Previously s-off via Lazy panda).. i was under the impression that this would un root and lock bootloader again.. i know that i now have lost root i know how to check that .. question is , is bootloader locked now as well?..tried rumrunner and moonshine to no avail, to get S-OFF .. and it needs to be unlocked for those exploits to work.. any ideas?
It will lock your bootloader and return the phone S-on if you chose those options in the menu when you first ran VipeRUU. If you're still S-off, then all you need to do is unlock the bootloader again unless it's showing unlocked. An easier route than what you chose would have been to update your Hboot to the Rumrunner Hboot, which takes less than a minute to do. You'll still need to update your firmware, since VipeRUU is a version behind what's currently out there. If you're S-on now, you'll need to unlock the bootloader and run Moonshine.
Sent from my HTC EVO 4G LTE
ok .. i see what you're saying .... i just ran rum runner... and it seemed to do the trick im currently S-OFF hboot 2.09 with the 3.17.651.4 71 software.. was able to install twrp>>>..I think im good to go!?..>>>>> i shall now...FOAF..lol...btw Thanks!!!
Yep, you should be good to go now. Just make sure that you have Superuser privileges and all should be right with the world:thumbup:
Sent from my HTC EVO 4G LTE