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
Related
I was having a problem with my screen being unresponsive so i needed to take it into a sprint store. i ran a signed 2.17 exe and now I have hboot 1.5 but still have s-off. in the bootloader screen it says locked but still shows s-off. i am confused as to what to do next. i assume i need to unlock but didn't know if i could do this via revolutionary. I tried to do a search but everything i found was related to s-on. I am trying to restore my phone to its rooted state since I have already had the repairs made. Any help and links would be greatly appreciated.
Brandon
Sent from my iPad using Tapatalk HD
brandonb8 said:
I was having a problem with my screen being unresponsive so i needed to take it into a sprint store. i ran a signed 2.17 exe and now I have hboot 1.5 but still have s-off. in the bootloader screen it says locked but still shows s-off. i am confused as to what to do next. i assume i need to unlock but didn't know if i could do this via revolutionary. I tried to do a search but everything i found was related to s-on. Any help and links would be greatly appreciated.
Brandon
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
fastboot oem writesecureflag3 or fastboot oem writesecureflag 3 , one of those will turn s-on
Edit... This might help http://forum.xda-developers.com/showthread.php?t=1578977
Thanks for the quick response. Sorry I was not more clear about what I am wanting to do. I am keeping the phone and the repairs have been made. I now have hboot 1.50 with s-off. I am wanting to flash a custom rom again and need to install a recovery. I didn't know what the process is currently for "unlocking" my phone now. When I rooted the phone originally, i was on hboot 1.4 and used revolutionary. I just do not know what to do to get my phone rooted again. I understand I have part of it with s-off still being on my phone, but the "locked" text at the top of the bootloader screen tells me I need to rectify this before I can flash a recovery. Is this correct?
Thanks.
Brandon
brandonb8 said:
Thanks for the quick response. Sorry I was not more clear about what I am wanting to do. I am keeping the phone and the repairs have been made. I now have hboot 1.50 with s-off. I am wanting to flash a custom rom again and need to install a recovery. I didn't know what the process is currently for "unlocking" my phone now. When I rooted the phone originally, i was on hboot 1.4 and used revolutionary. I just do not know what to do to get my phone rooted again. I understand I have part of it with s-off still being on my phone, but the "locked" text at the top of the bootloader screen tells me I need to rectify this before I can flash a recovery. Is this correct?
Thanks.
Brandon
Click to expand...
Click to collapse
Oh I see, well, your s-off and that locked banner means nothing because s-off should override it. Just flash a PG86IMG.zip of a recovery of your choice and you're good to go. Or you can flash it via fastboot by typing fastboot flash recovery "yourrecovery.img" once you do that, flash a rooted Rom. You could flash a lower hboot with a PG86IMG.zip if you want but its not really necessary.
If you want, I could dig up hboot 1.4 or revs hboot for ya. I think I have em in dropbox.
I got it. Thanks for all the help.
Sent from my PG86100 using Tapatalk 2
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.
I decided to run the 4.03.605.2 RUU before flashing back to Neo's Adrenaline 2.0...running the RUU reflashed a stock recovery and returned the bootloader to Locked, of course, so I went to the HTC Dev site to try to unlock it. I'm sure it's already a known issue but it appears that HTC's bootloader unlock tool is down and has been for some short time with no apparent efforts on their part to fix it.
So, I'm stuck with a locked bootloader until such time as someone can find a way to flash recovery without needing to unlock...
buh, wasn't the whole point of S-OFF so you don't have to use HTC's bootloader unlocker tool?
just s-off.
Yes, but if you flash an RUU that updates HBOOT, it will relock. Doesn't change the S flag, but it does indeed lock. I've had this happen twice.
Managed to find my original unlock_code.bin. Worked perfectly, I'm back in business...
When you unlock your phone, SAVE THE UNLOCK TOKEN!!! It can be used on your device no matter what you do.
socal87 said:
Yes, but if you flash an RUU that updates HBOOT, it will relock. Doesn't change the S flag, but it does indeed lock. I've had this happen twice.
Managed to find my original unlock_code.bin. Worked perfectly, I'm back in business...
When you unlock your phone, SAVE THE UNLOCK TOKEN!!! It can be used on your device no matter what you do.
Click to expand...
Click to collapse
I think the point he was trying to make is that if you are s-off, it overides the lock/unlock so you don't have to be unlocked anymore. S-off and locked, you can install whatever you want...
nrfitchett4 said:
I think the point he was trying to make is that if you are s-off, it overides the lock/unlock so you don't have to be unlocked anymore. S-off and locked, you can install whatever you want...
Click to expand...
Click to collapse
That's what I thought too, but I tried to flash recovery after running the RUU...got the "not allowed" error; unlocked, and had no issue.
To my knowledge, all S-off does is "break" the locks on certain partitions, such as boot, so they can be written from recovery...and allow flashing of radios and HBOOT without a valid signature. Recovery itself is what decides what you can flash in terms of ROMs...the stock recovery won't flash anything but an original signed .zip.
Next time just flash the the jupunto bear hboot it makes everything easier and all you need is the s off to flash it. I do it right after running any ruu
I ran the latest ruu,was s-off,locked bootloader,and flashed the recovery without any problems. You can try to push it through adb if anything
Sent from my ADR6425LVW using Tapatalk 2
I keep my phone unlocked all the time.
I can ruu with an unlocked bootloader because I have s-off.
The ruu process always leaves my phone in its unlocked state.
I never bother using jbear hboots, as they don't accomplish anything useful that anyone is likely to use. It gives some additional fastboot commands that nobody is using. If someday I need a jbear hboot command, then I'll flash it. Otherwise it just seems to be extra work, and it appears to have complicated your life.
---------- Post added at 06:19 AM ---------- Previous post was at 05:54 AM ----------
jayochs said:
buh, wasn't the whole point of S-OFF so you don't have to use HTC's bootloader unlocker tool?
just s-off.
Click to expand...
Click to collapse
No, the instructions at hbear's website list being htcdev unlocked as a prerequisite along with being stock and rooted, before even attempting the s-off procedure. Soff is something in addition to unlocked.
The jbear hboot acts like it is unlocked, whether the phone is locked or unlocked. Supposedly this will fool Verizon that your returned borked phone was not tampered with - well until Verizon notices jbear written on your hboot screen.
However, running a ruu will install a stock hboot.
Personally I think jbear hboots are a waste of effort. They are not going to fool anyone at Verizon because jbear is displayed on the hboot screen.
If somehow you go back to s-on with the jbear hboot still installed, then you are,oops, permanently bricked.
The additional fastboot commands one gets with the jbear hboot are not being used, not even by developers during their Rom installation procedures.
After every ruu, you need to repeat the htcdev unlock, and reflash the jbear hboot. This is extra work.
Everytime one flashes an hboot he is taking a bricking risk. if the flashing fails for any reason, like you pulled out the battery or battery runs out of power, or your file got corrupted, then you have an unrecoverable brick. That's why OTAs refuse to install on a low battery charge.
S-off + htcdev Unlocked are wonderful, but I think the concept of modified hboots should be reconsidered.
regards
Howard
HowardZ said:
I keep my phone unlocked all the time.
I can ruu with an unlocked bootloader because I have s-off.
The ruu process always leaves my phone in its unlocked state.
I never bother using jbear hboots, as they don't accomplish anything useful that anyone is likely to use. It gives some additional fastboot commands that nobody is using. If someday I need a jbear hboot command, then I'll flash it. Otherwise it just seems to be extra work, and it appears to have complicated your life.
---------- Post added at 06:19 AM ---------- Previous post was at 05:54 AM ----------
No, the instructions at hbear's website list being htcdev unlocked as a prerequisite along with being stock and rooted, before even attempting the s-off procedure. Soff is something in addition to unlocked.
The jbear hboot acts like it is unlocked, whether the phone is locked or unlocked. Supposedly this will fool Verizon that your returned borked phone was not tampered with - well until Verizon notices jbear written on your hboot screen.
However, running a ruu will install a stock hboot.
Personally I think jbear hboots are a waste of effort. They are not going to fool anyone at Verizon because jbear is displayed on the hboot screen.
If somehow you go back to s-on with the jbear hboot still installed, then you are,oops, permanently bricked.
The additional fastboot commands one gets with the jbear hboot are not being used, not even by developers during their Rom installation procedures.
After every ruu, you need to repeat the htcdev unlock, and reflash the jbear hboot. This is extra work.
Everytime one flashes an hboot he is taking a bricking risk. if the flashing fails for any reason, like you pulled out the battery or battery runs out of power, or your file got corrupted, then you have an unrecoverable brick. That's why OTAs refuse to install on a low battery charge.
S-off + htcdev Unlocked are wonderful, but I think the concept of modified hboots should be reconsidered.
regards
Howard
Click to expand...
Click to collapse
You are wrong in so many ways Howard.please everyone font bother reading this post.
Ok jbear hboot is not meant to fool Verizon. It's meant to provide fastboot commands even while the bootloader is locked.
As for op,I can confirm after running the ruu,you will still have to unlock to flash your recovery, if you still have your unlock code file you can unlock with that just like you did the first time .
Oh and the HTC website always does that just keep trying like every hour or so, if you can't find that unlock file they e mailed you
Sent from my ADR6425LVW using xda app-developers app
I am s-off and locked. And have been able to flash everything under the sun with no problems
The jb hboots are used not to fool Verizon, but to allow people to use fastboot commands like, "fastboot flash recovery (filename.img)" after s-off.
If you are s-off with stock hboot you can't run those commands.
Like Howard said, if you are on the jb hboot and you run the s-on command...then you're bricked. So those people with jb hboots are told to run a RUU first. Like Howard says, there are some risks to flashing things...its also risky to put your phone in your shirt pocket when you are around water.
Now, you can unlock your device after s-off (like Howard did) and use those commands with the stock hboot. However, if you want to return it to Verizon and you lock it, then it will read 'relocked' (i believe). I think that is the ONLY disadvantage of unlocking after s-off.
All this 'stuff' is in these threads. Some of it is personal preference and we all have a reason why our phones are configured certain ways. Just be aware of the implications.
There's no extra work on flashing jbear hboot. Right after the ruu rename the jhboot.zip to ph98img boot on hboot, flash and done. It seems you don't have a lot of knowledge when it comes into hboot stuffs.(no offense intended) And like the others guys said jbear is not to fool anyone and beside the jbear is an unlocked hboot.
socal87 said:
So, I'm stuck with a locked bootloader until such time as someone can find a way to flash recovery without needing to unlock...
Click to expand...
Click to collapse
There is a flashable amon ra you can use. You don't need to unlock. You also will need to flash supersu again too because you lost root after the ruu. If you want to stay on a stock hboot, then you run things as ph98 files.
Sent from my ADR6425LVW using xda app-developers app
dassh said:
There is a flashable amon ra you can use. You don't need to unlock. You also will need to flash supersu again too because you lost root after the ruu. If you want to stay on a stock hboot, then you run things as ph98 files.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
But he does need to be s-off...and I think he said he wasn't.
topgun1953 said:
The jb hboots are used not to fool Verizon, but to allow people to use fastboot commands like, "fastboot flash recovery (filename.img)" after s-off.
If you are s-off with stock hboot you can't run those commands.
Like Howard said, if you are on the jb hboot and you run the s-on command...then you're bricked. So those people with jb hboots are told to run a RUU first. Like Howard says, there are some risks to flashing things...its also risky to put your phone in your shirt pocket when you are around water.
Now, you can unlock your device after s-off (like Howard did) and use those commands with the stock hboot. However, if you want to return it to Verizon and you lock it, then it will read 'relocked' (i believe). I think that is the ONLY disadvantage of unlocking after s-off.
All this 'stuff' is in these threads. Some of it is personal preference and we all have a reason why our phones are configured certain ways. Just be aware of the implications.
Click to expand...
Click to collapse
with s-off and unlocked and stock hboot
one can
fastboot boot recoveryImageFile.IMG
fastboot flash recovery recoveryImageFile.IMG
fastboot flash boot kernelImageFile.IMG
I have done these, and they work.
It makes one wonder who really needs jbear hboots.
p.s. if someday I brick my phone, I don't plan to return to a Verizon store and lie to them.
HowardZ said:
with s-off and unlocked and stock hboot
one can
fastboot boot recoveryImageFile.IMG
fastboot flash recovery recoveryImageFile.IMG
fastboot flash boot kernelImageFile.IMG
I have done these, and they work.
It makes one wonder who really needs jbear hboots.
Click to expand...
Click to collapse
Yes you can flash those things. I guess that's what I was saying.
The "reason" that I know of to use jb hboots is if you ever want to return or sell your phone in a 'locked' state, you can. If you s-off, unlock, and then relock, I think it says "relocked" on the hboot screen.
topgun1953 said:
Yes you can flash those things. I guess that's what I was saying.
The "reason" that I know of to use jb hboots is if you ever want to return or sell your phone in a 'locked' state, you can. If you s-off, unlock, and then relock, I think it says "relocked" on the hboot screen.
Click to expand...
Click to collapse
ok, I suppose if you flash a stock hboot, then the hboot screen will show locked without displaying jbear.
But if Verizon sees jbear on your screen, they'll know you've done a whole lot more tampering than simply htcdev unlock.
Perhaps Verizon will be stupid enough to see unlocked and ignore the lines which say soff and jbear?
HowardZ said:
ok, I suppose if you flash a stock hboot, then the hboot screen will show locked without displaying jbear.
But if Verizon sees jbear on your screen, they'll know you've done a whole lot more tampering than simply htcdev unlock.
Perhaps Verizon will be stupid enough to see unlocked and ignore the lines which say soff and jbear?
Click to expand...
Click to collapse
I don't think verizon cares. IMHO
In my case, I'm locked, s-off, stock hboot. I can get what I want in ph98img.zip files so I don't use fastboot. I can write the s-on flag, and flash the lastest ota and my phone will be like stock, out of the box....good for some, doesn't really matter to me.
HowardZ said:
ok, I suppose if you flash a stock hboot, then the hboot screen will show locked without displaying jbear.
But if Verizon sees jbear on your screen, they'll know you've done a whole lot more tampering than simply htcdev unlock.
Perhaps Verizon will be stupid enough to see unlocked and ignore the lines which say soff and jbear?
Click to expand...
Click to collapse
Verizon don't care about s-off because there's some rezound that came out s-off out of the box.
topgun1953 said:
But he does need to be s-off...and I think he said he wasn't.
Click to expand...
Click to collapse
Yes, absolutely needs to be s-off for what i was suggesting. I may have mis-understood the op and subsequent posts. If the op doesn't want to s-off then unlock is a necessity but if s-offed, then the op has a choice to unlock or stay locked.
I chose to stay locked, like Topgun says, it's easier. The only difference is i did install a jbear hboot, but again that was because i think it's easier to use fastboot sometimes instead of trying to repackage something as a ph98.
Sent from my ADR6425LVW using xda app-developers app
---------- Post added at 01:28 PM ---------- Previous post was at 01:22 PM ----------
HowardZ said:
p.s. if someday I brick my phone, I don't plan to return to a Verizon store and lie to them.
Click to expand...
Click to collapse
If you brick, you couldn't change your hboot anyway. Using a jbear hboot is not to be deceptive.
Sent from my ADR6425LVW using xda app-developers app
I have read pages and pages from the Android Development forum for the HTC Evo 4G LTE and I can't seem to find a solution that works for me because going S-OFF or re-locking bootloader and loading RUU does not seem feasible for my situation.
The phone has custom recovery (TWRP) and we successfully loaded Viperboy's deodexed 3.15 stock ROM.
Baseband is 1.02.12.0427 (super outdated)
This phone was bought second hand and is a HTC dev unlocked phone, S-ON
I would like to update the baseband to 1.12.11.1200 and update the firmware to 3.16
Caveats: I don't have access to the phone, my friend can reload custom ROMs through TWRP, but beyond that I don't think we can go through Dirty Racun and S-Off, I don't know how we can easily check the HBOOT version to determine if the HBOOT version is 1.12
What would happen if we accepted the Sprint OTA? Are we SOL with the baseband because we are S-ON?
Is there any way we can get on MeanBean 3 or stock rooted 3.16?
Any advise would be greatly appreciated.
I wouldnt accept the OTA update to 3.16
I actually did just that when I relocked my phone on Saturday and had all sort of problems after that. Now, I'm not too sure you would even be able to install the update being that your phone is unlocked *citation needed*.
http://forum.xda-developers.com/showthread.php?t=2135670 - talks about the 3.16 OTA problems
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
BaconMunch said:
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
Click to expand...
Click to collapse
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
tilltheend714 said:
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
Click to expand...
Click to collapse
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
BaconMunch said:
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
Click to expand...
Click to collapse
Relocking the phone is done through fastboot on the computer. Nothing to do with HTC. And Dev unlocked means you get an unlock token from HTC to the email that you signed up with. So if you make your own account on HTC dev and request a token, it should send nothing to the other owner.
And sorry, but I don't understand what you mean by having Hboot 1.12. You mean only flashing the radio through recovery? If that's what you mean than I can't help with that. Not sure how that works or if there are problems with that.
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
BaconMunch said:
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
Click to expand...
Click to collapse
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
xlxcrossing said:
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
Click to expand...
Click to collapse
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
My advice is get s-off it will save alot of headaches down the road
Sent from my PoS MoPho
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
Sent you a PM
The advice is free....the bandwidth, not so much
Just wanted to say thank you all for the support and advice.
I finally walked my friend over gtalk and successfully achieved S-OFF after relock, 1.15 RUU, unlock with HTC DEV, dirtyracun
Then updated full firmwares incrementally to 3.16
Then while trying to load MeanBean, realized we lost TWRP (and possibly root, need to confirm), I can only guess that went away with the RUU? That's not really documented anywhere unless that's a known thing.
TWRP installation via goomanager failed (maybe due to lack of root), I was able to find TWRP v2.3.1 bootloader, installed that and installed MeanBean 3.0.4
I think that makes us up to date, however we will likely install SuperSU via TWRP once we customize and ensure the phone is running smoothly.
Thanks again all!
Super su is included with the ROM
Sent from my EVO using xda premium
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