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
Hello,
Can you please help me?I had my EVO 3D repaired( speaker issue). It was rooted, had a downgraded and unlocked HBoot 1.490.. and s_off and running Leedroid 5.4 GB rom. Before sending it I unrooted , restored to stock, re-locked and got it back on S-on. I then did the OTA ICS update.
The phone has been returned it is now on HBOOT 1.530, locked and S-ON and I am trying to unlock using HTCDEV, however when I flash the unlock_code.bin sent to me by HTC, it gets stuck at ' sending unlocktoken'. I have done everything possible and googled no end but inspite of my efforts it still gets stuck at the same point.
I have restarted my computer many times, started from scratch several times and generated a new device identifier token each time but still no joy. I have even flashed the RUU of the ICS OTA.
Please help me.
Thanks
ZINXYX said:
Hello,
Can you please help me?I had my EVO 3D repaired( speaker issue). It was rooted, had a downgraded and unlocked HBoot 1.490.. and s_off and running Leedroid 5.4 GB rom. Before sending it I unrooted , restored to stock, re-locked and got it back on S-on. I then did the OTA ICS update.
The phone has been returned it is now on HBOOT 1.530, locked and S-ON and I am trying to unlock using HTCDEV, however when I flash the unlock_code.bin sent to me by HTC, it gets stuck at ' sending unlocktoken'. I have done everything possible and googled no end but inspite of my efforts it still gets stuck at the same point.
I have restarted my computer many times, started from scratch several times and generated a new device identifier token each time but still no joy. I have even flashed the RUU of the ICS OTA.
Please help me.
Thanks
Click to expand...
Click to collapse
why would you apply the ota ics update when you could have kept it on hboot 1.5 and did the Juopunutbear S-OFF method, the wire trick literally toke me 5 minutes and now I am s-off with the cusotm Juopunutbear hboot, I love it, going from being hboot 1.5 s-on to s-off makes a world of difference, I love those geniuses who came up with Juopunutbear
I restored everything to stock befoe sending it off to HTC for repairs. I had heard that sometimes HTC refused to repair when they find out unlocked bootloader and S-off.
ZINXYX said:
I restored everything to stock befoe sending it off to HTC for repairs. I had heard that sometimes HTC refused to repair when they find out unlocked bootloader and S-off.
Click to expand...
Click to collapse
Have you tried reinstalling the HTC Drivers?
Yes, I have.Still no joy. I guess I may have to wait for revolutionary to get to grips with Hboot 1.53.
Any other suggestions please?
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
Hey all,
so I've been running ARHD on firmware 127.538.8 for awhile. I saw the RUU come out for 4.3 on Tmob, so obviously I was all like, **** yeah! So I flashed a stock ROM (based on 127.538.11) and then tried to run the RUU. Unlocked, S-OFF. For some reason, the RUU flashed Hboot (I'm currently stuck at 1.55.00) and then decided to throw an error 155 at me. So I tried relocking the bootloader, with a command I found browsing the forums that sets the status to Locked. Flashing the RUU here didn't work either. Re-unlocked the bootloader (I have no user data at all... it's sad). I realized, okay, I'm Unlocked and have a custom recovery installed (TWRP). Even if I relock, the RUU doesn't flash. My idea right now is to flash the 127.538.11 RUU to get Hboot 1.44, as well as a working non-hacked firmware. I'm not sure if that RUU will work, though I'm hoping it does. If it does, then I can OTA update without a problem.
Do any of you have any ideas as to how to do this? I can RUU to 127.538.11, then downgrade to x.8 and use revone to lock my bootloader and attempt an OTA. I'm not sure what to do here... I can also reflash ARHD 30 and stick with that for awhile. I can do basically anything recommended, as I have S-OFF and TWRP.
Thanks!
I don't mind being stuck on stock, however I do want to be able to warranty my phone in the future -- will having hboot 1.55.00 with 127.538.8 firmware be a problem? Can I downgrade my hboot since I'm S-Off? Any help here would be absolutely wonderful...
I have had this phone for 9 months in this state.. i had Negalite Blue 1.09 installed. it messed up and started to bootloop. so i did my normal fix. SetMainVerLOW and flashed the stock 2.89 RUU. but this time rather than fix my problem, it has stayed with a bootloop. i searched high and low, and ANY fix i found involved getting S-OFF. unfortunately i CAN'T because i cannot boot. I relocked, then unlocked. i tried CWM, 4EXT, TWRP recoveries. tried stock rooted ROM, MeanROM, negalite, and nothing... EVERYTHING bootloops.. I DON'T want to get rid of the phone as it is the best i have been able to afford, but i am afraid that it may not have any fix..:crying: PLEASE tell me,HOW CAN I FIX THIS???.... Again, currently Relocked, S-ON, HBOOT 1.58 and freshly flashed 2.89 RUU.
Use Ultimate recovey tool, downgrade hoot to 1.4, install ruu 1.13. Then s-off with revolutionary. Then install ruu 2.89 when s-off
Sent from my PG86100 using Tapatalk