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'm running Scott's ROM ICS S-ON. I'm not looking to S-OFF unless absolutely necessary; I don't prefer messing up with a bricked phone.
I want to update to the official ICS OTA distributed by Verizon. I haven't found a post that has any information on how to do this with S-ON Relocked and a Relocked Bootloader.
In my bootloader, the information at the top is
Code:
***RELOCKED***
***SECURITY WARNING***
VIGOR PVT SHIP S-ON RL
HBOOT-2.11.0000
RADIO-0.95.00.1118r/0.95.00.1223r
OpenDSP-v10.6.0.7611.00.0919
eMMC-boot
Oct 6 2011, 15:43:22
Any help would be appreciated. Thanks!
Download the latest RUU. If you locked your bootloader after using htc dev, all you would have to do is flash the new global RUU as normal and unlock (If you want) the bootloader again.
HTC Rezound
luis86dr said:
Download the latest RUU. If you locked your bootloader after using htc dev, all you would have to do is flash the new global RUU as normal and unlock (If you want) the bootloader again.
HTC Rezound
Click to expand...
Click to collapse
Is the new RUU the one from the Android Police website? Yes, I unlocked the bootloader via HTC Dev, and I just relocked "fastboot oem lock".
I have it rooted, so I guess now it can't boot, as it only boots into bootloader.
QuintonS said:
Is the new RUU the one from the Android Police website? Yes, I unlocked the bootloader via HTC Dev, and I just relocked "fastboot oem lock".
I have it rooted, so I guess now it can't boot, as it only boots into bootloader.
Click to expand...
Click to collapse
I downloaded the RUU from Nils Sense 4 thread. First page, third post.
http://forum.xda-developers.com/showthread.php?t=1757357
Since your relocked, just place it on root sd as PH98IMG.zip and reboot into bootloader to flash.
HTC Rezound
Alright, I'll try that. If I come up with any errors (I'll be sure if it's one), I'll come back and talk of it.
...As soon as I'm about to type what was going wrong, it decided to fix itself SOMEHOW and continue.
...Well, so far, it has appeared to be working fine! Not sure if this will fix the blue screen problem, but all I was really hoping for was to get the stock Rezound ICS update.
Thanks so much! You've been really helpful. It was much simpler than I was expecting. I'll see about rooting at a later date
Not sure how it works or the slang around here but "bump"? or "thanks" button pressed xD
QuintonS said:
...As soon as I'm about to type what was going wrong, it decided to fix itself SOMEHOW and continue.
...Well, so far, it has appeared to be working fine! Not sure if this will fix the blue screen problem, but all I was really hoping for was to get the stock Rezound ICS update.
Thanks so much! You've been really helpful. It was much simpler than I was expecting. I'll see about rooting at a later date
Not sure how it works or the slang around here but "bump"? or "thanks" button pressed xD
Click to expand...
Click to collapse
Lol. No problem.
HTC Rezound
luis86dr said:
Lol. No problem.
HTC Rezound
Click to expand...
Click to collapse
I am in a similar state and I have one follow up question. I read in another thread that before relocking my bootloader, I would need to Flash stock recovery because I have Amon-Ra installed. Is flashing the stock recovery absolutely required before relocking and flashing the new global ruu?
Thanks in advance.
layneja said:
I am in a similar state and I have one follow up question. I read in another thread that before relocking my bootloader, I would need to Flash stock recovery because I have Amon-Ra installed. Is flashing the stock recovery absolutely required before relocking and flashing the new global ruu?
Thanks in advance.
Click to expand...
Click to collapse
No, you don't need to flash stock recovery. The RUU will do that for you. Just make sure you're locked before you flash the RUU. Unlock and re flash your choice of recovery after RUU is complete.
HTC Rezound
I have just got an evo 3d, previosuly owned one, and stupid me forgot to make a back up of my stock rom before i rooted and flashed an ICS rom.
Im in Australia on OPTUS, the CID is OPTUS001 and i cannot chnage this.
Im S-on, with Hboot 1.53.007 and htcdev unlocked
I have tried lots of things but cant for the life of me figure this one out.
I want to S-off and downgrade the hboot. But to do this i need s-off and need to change the cid, which i cant right now
Where can i get the OPTUS RUU for ICS? I have tried the asia RUU but it fails with incorrect CID
I have 4ext recovery and also have fastboot access
Or what can i do?
many thanks in advance
ajoesmith said:
I have just got an evo 3d, previosuly owned one, and stupid me forgot to make a back up of my stock rom before i rooted and flashed an ICS rom.
Im in Australia on OPTUS, the CID is OPTUS001 and i cannot chnage this.
Im S-on, with Hboot 1.53.007 and htcdev unlocked
I have tried lots of things but cant for the life of me figure this one out.
I want to S-off and downgrade the hboot. But to do this i need s-off and need to change the cid, which i cant right now
Where can i get the OPTUS RUU for ICS? I have tried the asia RUU but it fails with incorrect CID
I have 4ext recovery and also have fastboot access
Or what can i do?
many thanks in advance
Click to expand...
Click to collapse
Okay. You are S on and have a custom recovery. Why can't you s off then? Do the wire trick. Unlimited.io has everything you need to know. After s off downgrade hoot and change cid if you need to. Hboot downgrade -> http://forum.xda-developers.com/showthread.php?t=1906172
MrJyrks said:
Okay. You are S on and have a custom recovery. Why can't you s off then? Do the wire trick. Unlimited.io has everything you need to know. After s off downgrade hoot and change cid if you need to. Hboot downgrade -> http://forum.xda-developers.com/showthread.php?t=1906172
Click to expand...
Click to collapse
Yes but im not on stock
I thought you MUST be on stock to do the wire trick?
ajoesmith said:
Yes but im not on stock
I thought you MUST be on stock to do the wire trick?
Click to expand...
Click to collapse
Not that I know of. Any one else hear different?
Soff with wire trick works ONLY on stock rom from ruu. Not even a flashed one that says stock... His only chance is to find a ruu compatible with his cid (sorry bro, cant help you there, i searched a bit but no good results).
Other case, you can enable Smartflash in 4ext tools and use custom ics roms, but only sense roms. On that bootloader you cannot flash anything else other than sense based.
Just as a question, did you by chance try the european ruu? I have a feeling it might work...
I'd like to restore my phone to its absolute default. I would like to return my phone tomorrow. Can you help explain to me how a rooted phone can be restored?
WARNING: If you have flashed a custom bootloader make sure you flash it back to a stock bootloader before you do S-ON or you WILL brick.
First read the revone one thread on how to lock everything back up. First and second post have all the info you need to make it look untouched.
http://forum.xda-developers.com/showthread.php?t=2314582
Then flash the RUU after you have S-ON and Locked in the bootloader.
http://dl3.htc.com/application/tmo/....20_10.40.1150.04_release_324846_signed_2.exe
designgears said:
WARNING: If you have flashed a custom bootloader make sure you flash it back to a stock bootloader before you do S-ON or you WILL brick.
First read the revone one thread on how to lock everything back up. First and second post have all the info you need to make it look untouched.
http://forum.xda-developers.com/showthread.php?t=2314582
Then flash the RUU after you have S-ON and Locked in the bootloader.
http://dl3.htc.com/application/tmo/....20_10.40.1150.04_release_324846_signed_2.exe
Click to expand...
Click to collapse
I currently have "unlocked" and "tampered," so do I just need to flash the RUU?
hammettorchandler said:
I currently have "unlocked" and "tampered," so do I just need to flash the RUU?
Click to expand...
Click to collapse
Do you have hboot version 1.44? If so run this from bootloader:
fastboot oem lock
Then run the ruu. If you're s-off check the thread designgears just shared with you and go s-on last.
Sent from my HTC One using xda premium
mikeyinid said:
Do you have hboot version 1.44? If so run this from bootloader:
fastboot oem lock
Then run the ruu. If you're s-off check the thread designgears just shared with you and go s-on last.
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
He should use revone first to make it look untouched because the motochopper root method is blocked. Otherwise he will have to go back to the state he is in now and do it all in the right ordered
designgears said:
He should use revone first to make it look untouched because the motochopper root method is blocked. Otherwise he will have to go back to the state he is in now and do it all in the right ordered
Click to expand...
Click to collapse
ah, you are correct.
Many thanks to you both. Mission accomplished. I re-rooted too afterwards.
Sorry for the newbish questions, but if I'm getting a replacement phone because my screen cracked and I need to send my current phone back to Asurion. I'm currently on the 1.54 hboot from the international firmware, so do simply need to flash back to the stock 1.44 hboot, use REVONE to revert to S-On, lock the bootloader and then flash the RUU? Also, can I flash the decrypted RUU zip instead of the RUU.exe after I've relocked the bootloader? I'm a Linux user and would prefer not having to install Windows to bring the phone back to stock.
RobBull69 said:
Sorry for the newbish questions, but if I'm getting a replacement phone because my screen cracked and I need to send my current phone back to Asurion. I'm currently on the 1.54 hboot from the international firmware, so do simply need to flash back to the stock 1.44 hboot, use REVONE to revert to S-On, lock the bootloader and then flash the RUU? Also, can I flash the decrypted RUU zip instead of the RUU.exe after I've relocked the bootloader? I'm a Linux user and would prefer not having to install Windows to bring the phone back to stock.
Click to expand...
Click to collapse
Insurance doesn't care what state you are in. Because you are paying them a deductible. No need to go through a that
Sent from my HTC One using xda app-developers app
I have an HTC one that has been bootloader unlocked and running CM for some time. The bootloader version is currently 1.55 and S-ON. I'm hoping to revert to a rom that will work with rumrunner and allow S-OFF to happen.
Can anyone point me in the right direction? I've been looking for about an hour and can only find a leaked dev build of a rom for this phone that is flashable via recovery, the rest are all RUU files and I'm not familiar enough with RUU to know whether or not I'll take an permanent step in the wrong direction if I use one to upgrade.
Edit: please move to the right forum, I just realized I should have put this in another section instead of dev.
bruor said:
I have an HTC one that has been bootloader unlocked and running CM for some time. The bootloader version is currently 1.55 and S-ON. I'm hoping to revert to a rom that will work with rumrunner and allow S-OFF to happen.
Can anyone point me in the right direction? I've been looking for about an hour and can only find a leaked dev build of a rom for this phone that is flashable via recovery, the rest are all RUU files and I'm not familiar enough with RUU to know whether or not I'll take an permanent step in the wrong direction if I use one to upgrade.
Edit: please move to the right forum, I just realized I should have put this in another section instead of dev.
Click to expand...
Click to collapse
Since you are S-ON you will need to do the following:
Relock your bootloader
Leave your phone in FASTBOOT USB
Run this RUU 3.24.531.3 in Windows and follow the prompts
Follow rumrunner's OP instructions
The RUU will reset your phone back to stock and since your hboot is 1.55 this is the RUU which corresponds to that hboot.
majmoz said:
Since you are S-ON you will need to do the following:
Relock your bootloader
Leave your phone in FASTBOOT USB
Run this RUU 3.24.531.3 in Windows and follow the prompts
Follow rumrunner's OP instructions
The RUU will reset your phone back to stock and since your hboot is 1.55 this is the RUU which corresponds to that hboot.
Click to expand...
Click to collapse
Thank you for the quick reply, it worked beautifully. Now that I am S-OFF, if I am to run an RUU, will they set the device back to S-ON? Or do they leave that flag alone?
bruor said:
Thank you for the quick reply, it worked beautifully. Now that I am S-OFF, if I am to run an RUU, will they set the device back to S-ON? Or do they leave that flag alone?
Click to expand...
Click to collapse
No, RUU will not set the flag to S-ON.
I keep getting error 155 during the RUU process. I have been researching and trying a bunch of different things but I cannot update the RUU
I'm running SkyDragon GPE 7.2 Android 5.1.1 hboot 1.61 with S-ON. I error saying RRU is older and errors.