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?
I have hboot 1.53, htcdev bootloaderunlocked, and i'm following this thread http://forum.xda-developers.com/showthread.php?t=1743466 to get S-OFF Method D, Im stuck at step 18, whenever i run ControlBear this message does not disappear "No Juopunutbear boot image found"... and I cant continue. did I do something wrong? I reflashed already and yet same problem. Please help.
Please advice, anyone? Thank you. I have reflashed the third time. Am I missing something?
i dont know how i got it, i became hopeless so i flash ThemeGenesis ROM and used the wiretrick method, it worked! Im now S-Off, glad that I didnt brick my Shooter:silly:
So I was trying to root my CDMA EVO 3d earlier and failed. It kept sticking on the sprint loading screen no matter what rom I flashed to it. I unlocked the bootloader through HTCDev. I then loaded the teamwin recovery and tried to flash a rom through that. I'm guessing I missed a few steps (first time messing with a droid) and locked it up. Now I got it relocked and tried to load the:
RUU_Shooter_S_Sprint_WWE_2.08.651.3_Radio_0.97.10.0808_NV_SPCS_1.31_003_release_219445_signed.zip
but it was the wrong version appearently and I'm out of ideas as I've been working on this all day long. I just want to be able to use my phone again but if I could obtain a full root in the process that would be nice! I hope someone here can help because you guys are my last hope! I've done lots of reading and searching but nothing that has really explained my situation. Thanks in advance for any help!
Specs:
RELOCKED
shooter xc ship s-on rl
hboot 1.58.0000
radio 1.09.00.0706
OpenADSP v02.6.0.226.00.0217
eMMc-boot
Did you try the 2.17 one?
Save the Drama for your Mama with Tapatalk 2
Yes I did try that one along with the newt rom, mikrom and a few others to no avail. :crying: I'm at a loss, I loaded the teamwin recovery back on, every time I flash a rom it gets stuck on the loading screen and never fully boots.
I just read that apparently, none of the old ruu work in the new hboot if s-on. I recommend you get s-off.
Edit: Not sure if that'strue as I've heard conflicting information.
Save the Drama for your Mama with Tapatalk 2
Okay I'll try that next, thanks for the input!
I tried getting s-off by the Live CD method, booted it from a flash drive, locked it back up and when I went to brick it, it said the ruu was the wrong version. I used the version listed in the guide so I'm not too sure which version I need.
So I was told there is nothing that supports hboot 1.58? Is this correct? Can anyone confirm this? Guess I just have to wait for someone to put something together that supports it?
Fixed thanks to this thread: http://forum.xda-developers.com/showthread.php?t=1813818&highlight=hboot+1+58
I hate to post a new thread on this, but I need help and quick (also, I literally have read through about 20 different threads and have tried numerous solutions)...
CDMA HTC EVO 3d
I originally was on Hboot 1.4, rooted using Revolutionary, updated to ENG Hboot and unlocked bootloader.
1. I flashed a stock ROOTED rom for 1.13.651.7
2. Switched backed to Ship Hboot 1.40 ( I saw that was required before relocking bootloader) [Something went wrong here I guess; although it appeared to work but got stuck at HTC white screen afterwards]
3. Ran RUU for 1.13.651.7 for Hboot 1.40 - appeared to work but still stuck
4. Relocked bootloader: Read somewhere I had to relock bootloader to run RUU properly
5. Ran RUU for 1.13.651.7 for Hboot 1.40 again - again it went through the whole process and said success but still stuck on htc white screen after reboot
6. Flashed thru bootloader 2.17.xxx.5 Hboot 1.5: Felt like I was out of options and saw a post to update to 2.17.xxx.5 Hboot 1.5
7. After doing #6, I ran the RUU for 2.17.xxx.5 Hboot 1.5 - ran successfully and after reboot still stuck at htc white screen then bootloops
Here is what phone currently shows:
***LOCKED***
SHOOTER XC SHIP S-ON RL
HBOOT-1.50.0000
RADIO-1.06.00.1216
eMMC-boot
Aug 7 2011, 10:21:40
I need to turn this phone back in to work - I am at a loss - any help is appreciated! To top it off, my battery won't charge and I have to keep asking a friend at work with same phone to switch batteries and charge it for me.
Maybe try running the latest ICS ruu exe.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Since it doesn't say RElocked on the bootloader is there anyway to tell that I messed with it?
I don't think so. I would try running the latest ICS ruu exe just to see if it fixes things. If not, just play dumb when you turn it in.
Read, Search, Read again, ... Then Ask with Tapatalk 2
I guess I can give it a go...is this the latest:
RUU_Shooter_ICS_35_S_Sprint_WWE_2.89.651.2_Radio_1.09.00.0706__NV_NV_SPCS_1.43_release_271101_signed.exe
Yes. Connect your phone to your computer and boot into bootloader. It should say fastboot USB. Run the ruu and hopefully you'll be set.
Read, Search, Read again, ... Then Ask with Tapatalk 2
Run over it with your car and tell them it fell off your lap while getting gas.....
sudo passwd root
Odd...newest RUU won't run - it says USB connection error, although I have ran the older RUU's without issue. I am going to run the one prior to ICS again and if it doesn't work turning it in as is. I will just say did factory reset and after that it no longer will boot... Thx for your help
No luck - I'm done...very surprised the RUU's even after successfully updating and running didn't resolve the issue - I have never seen something like this before. Oh well, hopefully it doesn't happen to anyone else. I switched to the S3 so I won't be visiting the Evo 3d forums anymore.