Hi guys,
I've done S-OFF the Rezound and still on Stock Leaked ICS HBOOT (there is no Juopuntu/Bear on top of the screen in Bootloader like most of the people here have).
Could you please sum up the differences in all the HBOOT here ? What is it for ? (Engineered HBOOT posted by con, Leaked ICS HBOOT , Gingerbread HBOOT, ICS HBOOT with Juopuntu/Bear on top of the screen......).
Thank you
Did you flashed the jb_hboot.zip in fastboot?
I had that issue and did as follows:
Booted into fastboot and ran these commands in command prompt:
fastboot oem rebootRUU
fastboot flash zip jb_hboot.zip
fastboot reboot
Sent from my Htc Rezound
Follow me on twitter @lmrtech
luis86dr said:
Did you flashed the jb_hboot.zip in fastboot?
Sent from my Htc Rezound
Follow me on twitter @lmrtech
Click to expand...
Click to collapse
I haven't flashed any jb_hboot.zip after getting S-OFF. Should I be flashing the zip file posted in you Thread ?
http://forum.xda-developers.com/showthread.php?t=1613309
Thanks
This is what I have gathered so far.
GB Firmware Info:
Stock:
Refuses fastboot flashes
Allows PH98IMG.zip flashes of anything
Allows normal S-OFF activites, except not via fastboot unless you htcdev.com unlock again
Engineering:
You can do whatever the hell you want
Allows fastboot and PH98IMG.zip to flash anything
Looks badass having ENG S-OFF in the tag
Extra Engineering Commands
ICS Firmware Info:
Stock:
Refuses fastboot flashes
Allows PH98IMG.zip flashes of anything
Allows normal S-OFF activites, except not via fastboot unless you htcdev.com unlock again
JuopunutBear Modified:
Says JuopunutBear in Purple
Allows fastboot and PH98IMG.zips like an ENG hboot
con247 said:
This is what I have gathered so far.
GB Firmware Info:
Stock:
Refuses fastboot flashes
Allows PH98IMG.zip flashes of anything
Allows normal S-OFF activites, except not via fastboot unless you htcdev.com unlock again
Engineering:
You can do whatever the hell you want
Allows fastboot and PH98IMG.zip to flash anything
Looks badass having ENG S-OFF in the tag
Extra Engineering Commands
ICS Firmware Info:
Stock:
Refuses fastboot flashes
Allows PH98IMG.zip flashes of anything
Allows normal S-OFF activites, except not via fastboot unless you htcdev.com unlock again
JuopunutBear Modified:
Says JuopunutBear in Purple
Allows fastboot and PH98IMG.zips like an ENG hboot
Click to expand...
Click to collapse
Thank you very much.
This is extremely helpful
nbhnohome said:
I haven't flashed any jb_hboot.zip after getting S-OFF. Should I be flashing the zip file posted in you Thread ?
http://forum.xda-developers.com/showthread.php?t=1613309
Thanks
Click to expand...
Click to collapse
If your on ICS Leak, yes.
Sent from my Htc Rezound
Follow me on twitter @lmrtech
con im on juopunutbear and i can't flash in fastboot ... do you also have to be unlocked?
sorry if it seems obvious this s off thing made this a lot different (confusing)
---------- Post added at 11:03 PM ---------- Previous post was at 10:29 PM ----------
... now it work's ive been messing around and im not sure what fixed it but i can fastboot flash and stuff now ....
**** has been wonky
Has anybody tried the JB hboot on Gingerbread? If so does it work and were there any problems?
RoryHe said:
con im on juopunutbear and i can't flash in fastboot ... do you also have to be unlocked?
sorry if it seems obvious this s off thing made this a lot different (confusing)
---------- Post added at 11:03 PM ---------- Previous post was at 10:29 PM ----------
... now it work's ive been messing around and im not sure what fixed it but i can fastboot flash and stuff now ....
**** has been wonky
Click to expand...
Click to collapse
How did you mess with it to get it flash Juopunutbear HBOOT ? Put it in freezer for hours jk.
Thanks
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
Hello,
I've got a problem with an htc evo 3d gsm with this features:
***Relocked***
Shooter_U PVT SHIP S-ON RL
HBOOT-1.53.0007
RADIO-11.25.3504.06_M
OpenDSP-v02.6.0.2226.00.0202
eMMC-boot
May 22 2012
and i've tryed to root this device by this guide.
but it entered on bootloop, so on point 7) -3 there is a note by tell if you get on bootloop you have to do the procedure again but i do it and nothing changes...Also, before flashing a new rom, everything was ok...
so i decided to restore a previously backup but the bootloop continue .
My next step was to restore the Original state of the phone with RUU.exe by this guide but it doesn't work ....now i havn't got any idea how to restore phone....
so please help me , and sorry sorry for my BAD english.
You have to flash the boot.img using fastboot commands. In that guide he doesnt tell you that. It is required for s-on devices.
first of all extract the boot.img file located in the rom zip file (usually in the kernelshooteru folder) and transfer it to the folder on your pc where you have adb/fastboot. then on your phone:
1) wipe data/factory reset
2) wipe cache
3) wipe delvik
4) flash rom from sdcard
5) connect your usb then reboot to bootloader and choose fastboot. It should say "fastboot usb"
6) go to cmd(navigate to your fastboot/adb directory) and type "fastboot flash boot boot.img"
7) reboot
---------- Post added at 09:35 PM ---------- Previous post was at 09:29 PM ----------
As for the RUU are you sure you didnt download a cdma ruu? cause that guide is certainly for a cdma device, the link to the RUUs is for cdma
get gsm RUU from here:
http://forum.xda-developers.com/showthread.php?t=1208485
Nothing but now it show for a few second the label "HTC" and after he reboot I'm trying to redownload a different RUU version
I have the same issue...
Bootlooping after I did a ROM update.
I only have access to the SD card and there is nothing on it such as a rom.zip file or any system files like that. I need to get a new bootloader I think. Where do I find one for the 3D?
I have tried to use a couple I found but they did not work.
Thanks.
First of all relock your bootloader. Then download your RUU from the apppropriate place. If you are a gsm user get it from here: http://forum.xda-developers.com/showthread.php?t=1208485
Which evo 3d do you have? brand country of purchase etc. If its unbranded you should run the European ICS RUU
connect your phone in bootloader mode and run the RUU exe file from pc
EM|NEM said:
First of all relock your bootloader. Then download your RUU from the apppropriate place. If you are a gsm user get it from here: http://forum.xda-developers.com/showthread.php?t=1208485
Which evo 3d do you have? brand country of purchase etc. If its unbranded you should run the European ICS RUU
connect your phone in bootloader mode and run the RUU exe file from pc
Click to expand...
Click to collapse
Thank you for the reply,
I have a U.S. based Sprint EVO 3D which is CDMA I think.
EM|NEM said:
First of all relock your bootloader. Then download your RUU from the apppropriate place. If you are a gsm user get it from here: http://forum.xda-developers.com/showthread.php?t=1208485
Which evo 3d do you have? brand country of purchase etc. If its unbranded you should run the European ICS RUU
connect your phone in bootloader mode and run the RUU exe file from pc
Click to expand...
Click to collapse
Where does one find RUU.exe? I have unzipped a stock rom file and I don't see an executable anywhere.
This is a good guide to flashing RUUs for your CDMA sprint
http://forum.xda-developers.com/showpost.php?p=22489299&postcount=3
He has linked all the RUU's
How do i unroot my Sprint HTC EVO 3D AND RETURN TO STOCK..
UNLOCKED
SHOOTER XC SHIP S-OFF RL
HBOO1.58.0000
THANKS!
Follow one of the multiple guides.
sent from MY BAD A$$ ET4G
patrao_n said:
Follow one of the multiple guides.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
what multiple guildes?
I myself just run the RUU when I want stock. It's simple.
Sent from my shooter using xda premium
Unroot Help
If you want to unroot, first find the Stock Hboot 1.58, then install it.
Then run the RUU for your device.
Lastly, in fastboot (adb), run "reboot bootloader" then run "fastboot oem writesecureflag 3".
Congrats, you will now be unrooted with bootloader *LOCKED*.
If you need any more help, feel free to PM me.
Boris Spektor said:
then run "fastboot oem writesecureflag 3".
Click to expand...
Click to collapse
DON'T RUN THIS.........
What are you trying to do?
Boris Spektor said:
If you want to unroot, first find the Stock Hboot 1.58, then install it.
Then run the RUU for your device.
Lastly, in fastboot (adb), run "reboot bootloader" then run "fastboot oem writesecureflag 3".
Congrats, you will now be unrooted with bootloader *LOCKED*.
If you need any more help, feel free to PM me.
Click to expand...
Click to collapse
raptoro07 said:
DON'T RUN THIS.........
What are you trying to do?
Click to expand...
Click to collapse
He said to run the RUU before issuing that command so it should be fine if the intent is to return to 100% stock, including S-ON. It's not really necessary to flash the stock bootloader before flashing the RUU but it might save having to restart the RUU if it hangs after flashing the bootloader. The OP said he was already on hboot 1.58 anyway.
You will also need to to lock the bootloader with a zip file in recovery since flashing the RUU doesn't do that. I have a guide here that includes everything you need.
Good luck!
ramjet73
ramjet73 said:
He said to run the RUU before issuing that command so it should be fine if the intent is to return to 100% stock, including S-ON. It's not really necessary to flash the stock bootloader before flashing the RUU but it might save having to restart the RUU if it hangs after flashing the bootloader. The OP said he was already on hboot 1.58 anyway.
You will also need to to lock the bootloader with a zip file in recovery since flashing the RUU doesn't do that. I have a guide here that includes everything you need.
Good luck!
ramjet73
Click to expand...
Click to collapse
When i reinstalled the stock Hboot manually (via bootloader) it showed *LOCKED* for me.
Just wondering, how does flashing a zip file in recovery, (which doesn't touch the Hboot) turn it *LOCKED*?
Boris Spektor said:
When i reinstalled the stock Hboot manually (via bootloader) it showed *LOCKED* for me.
Just wondering, how does flashing a zip file in recovery, (which doesn't touch the Hboot) turn it *LOCKED*?
Click to expand...
Click to collapse
That's because you were locked already and it just wasn't showing because the custom hboot masks that status.
There's a link to a thread that explains how the lock zip file works in this post.
ramjet73
Thanks guys for all your help....
Back to stock.
But my HBOOT is still showing S-OFF
SHOOTER XC SHIP S-OFF RL
How do iget S-OFF TO S-ON...
PSid not run this command yet..(fastboot oem writesecureflag 3)
I have my HTC One M8 running on the GPE firmware, and I'm trying to get back to stock. I tried with an unlocked bootloader, locked bootloader, ran the RUU as an admin, changed the CID to SuperCID and CWS__001 with no success. What confuses me is I've used this utility before to restore back to stock under the same circumstances with no problem. Hope someone can help, thanks
-John Carter
carterjohn21 said:
I have my HTC One M8 running on the GPE firmware, and I'm trying to get back to stock. I tried with an unlocked bootloader, locked bootloader, ran the RUU as an admin, changed the CID to SuperCID and CWS__001 with no success. What confuses me is I've used this utility before to restore back to stock under the same circumstances with no problem. Hope someone can help, thanks
-John Carter
Click to expand...
Click to collapse
The GPE changes the partition layout and thus makes it more interesting to get back to stock. Just running a RUU won't do it. It could be not so hard, and it could be a nightmare as it was for me. Read, read, and read some more on this post, you will get it.
http://forum.xda-developers.com/showthread.php?t=2733523
hack14u said:
The GPE changes the partition layout and thus makes it more interesting to get back to stock. Just running a RUU won't do it. It could be not so hard, and it could be a nightmare as it was for me.
Click to expand...
Click to collapse
You posted the opposite information here (RUU will convert back to Sense from GPE) in Post #73: http://forum.xda-developers.com/showthread.php?t=2721435&page=8
What difficulties did you encounter with the RUU?
RUU should in theory re-write all partitions, so the fact the partition layout is different in GPE should not in itself make the RUU fail.
Also, the OP's error 159 is just wrong CID, so again I don't think its related to partition layout being different.
---------- Post added at 11:05 AM ---------- Previous post was at 11:03 AM ----------
carterjohn21 said:
changed the CID to SuperCID and CWS__001 with no success. What confuses me is I've used this utility before to restore back to stock under the same circumstances with no problem.
Click to expand...
Click to collapse
S-on or S-off (I assume s-on if you are messing with the CID in the first place). Also, you relocked the bootloader before running the RUU?
Did you make sure the CID was actually changed by doing adb getvar all?