Related
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
Hey!
Well im about to send my old phone back and ran the RUU then did the s-on procedure. i relocked my bootloader and says relocked.... i ran ruu again and says the same thing! any suggestion?
Do you think verizon would charge me for this?
ryclegman said:
Hey!
Well im about to send my old phone back and ran the RUU then did the s-on procedure. i relocked my bootloader and says relocked.... i ran ruu again and says the same thing! any suggestion?
Do you think verizon would charge me for this?
Click to expand...
Click to collapse
i've never heard of a returned phone being rejected for any reason other than physical damage. and if you are super worried about it there is a link to hex edited hboots.http://forum.xda-developers.com/showthread.php?t=1853871 you already s-on'd so you might have to s-off again. not sure about that part though
cslingerland said:
i've never heard of a returned phone being rejected for any reason other than physical damage. and if you are super worried about it there is a link to hex edited hboots.http://forum.xda-developers.com/showthread.php?t=1853871 you already s-on'd so you might have to s-off again. not sure about that part though
Click to expand...
Click to collapse
I haven't either so i think i may just send it out! chances are they wont see or care
ryclegman said:
I haven't either so i think i may just send it out! chances are they wont see or care
Click to expand...
Click to collapse
I think you might have to s-off. Downgrade to GB or a lower ICS RUU. Lock it. s-on. then do the ICS RUU. Should be back to locked and s-off.
^^
Flyhalf205 said:
I think you might have to s-off. Downgrade to GB or a lower ICS RUU. Lock it. s-on. then do the ICS RUU. Should be back to locked and s-off.
Click to expand...
Click to collapse
Won't his hboot still show relocked after that...
Sent from my ADR6425LVW using xda app-developers app
cslingerland said:
Won't his hboot still show relocked after that...
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Other poster is correct. Have to run s-off. Rerun RUU to unroot and then write s-on flag. Will remove all tags and be box stock.
prdog1 said:
Other poster is correct. Have to run s-off. Rerun RUU to unroot and then write s-on flag. Will remove all tags and be box stock.
Click to expand...
Click to collapse
Thats sweet. I didn't think that was possible which is why we have the hboots that are edited.good to know though!
Sent from my ADR6425LVW using xda app-developers app
prdog1 said:
Other poster is correct. Have to run s-off. Rerun RUU to unroot and then write s-on flag. Will remove all tags and be box stock.
Click to expand...
Click to collapse
But won't the hboot technically say relocked once you relock it after running the RUU?
[email protected] said:
But won't the hboot technically say relocked once you relock it after running the RUU?
Click to expand...
Click to collapse
Not of after you S-OFF. When you do, the bootloader locks automatically, and says LOCKED not RELOCKED.
Sent from my ADR6425LVW using Tapatalk 2
shrike1978 said:
Not of after you S-OFF. When you do, the bootloader locks automatically, and says LOCKED not RELOCKED.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
So I am already s-off. Can I run the latest ICS RUU, then s-on? Will that send me back to a totally looking stock phone?
Why not just flash one of the missed hboots that says locked and s-on when you're actually s-off? I had mine unlocked and s-off and then made it s-on and sent it back in to Verizon and they sent me another one, no questions asked. Don't worry about it.
Sent from my Nexus 7 using Tapatalk 2
Look, even my hex edited hboots wont fool a tech. They can still tell.
HTC tech, yea that is if they even care to look. Verizon Tech? I doubt they even know what S-Off means or what HBOOT even is lol.
Sent from my Nexus 7 using Tapatalk 2
Just follow instructions:
http://forum.xda-developers.com/showthread.php?t=
Sent from my ADR6425LVW using xda app-developers app
Phaded said:
Just follow instructions:
http://forum.xda-developers.com/showthread.php?t=
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Invalid link.
Try this
http://forum.xda-developers.com/showthread.php?p=25167284#post25167284
Sent from my ADR6425LVW using xda app-developers app
Might help to think of HTC Dev Unlock and JuopunutBear S-Off as the two "gatekeepers", the two tools in the Rezound's current arsenal that affect the security flag. The security flag starts off as "locked" on a stock phone.
HTC Dev Unlock will alter the security flag to show "unlocked", and running the code to lock it back will now show it as "relocked".
JuopunutBear S-Off will reset the security flag back to "locked" no matter what the flag reads, and alter the "S-On" flag to "S-Off".
So to get back to a stock "S-On/Locked" from any of these states:
"S-On/Unlocked or Relocked"
If you are S-On and have used HTC Dev Unlock, you will need to do S-Off to get the "Locked" message back. Run a RUU, then do S-On procedure.
"S-Off/Locked"
If you are S-Off but have *not* used HTC Dev Unlock after the S-Off procedure, you should just need to run a RUU and do S-on.
"S-Off/Unlocked or Relocked"
If you are S-Off and have used HTC Dev Unlock since the S-Off procedure, you must run a RUU, re-lock the bootloader if you have not done so before, and do S-On. Then, do the S-off procedure (keep the stock bootloader, do not flash a modded one) and do S-on again.
PhantasmRezound said:
Might help to think of HTC Dev Unlock and JuopunutBear S-Off as the two "gatekeepers", the two tools in the Rezound's current arsenal that affect the security flag. The security flag starts off as "locked" on a stock phone.
HTC Dev Unlock will alter the security flag to show "unlocked", and running the code to lock it back will now show it as "relocked".
JuopunutBear S-Off will reset the security flag back to "locked" no matter what the flag reads, and alter the "S-On" flag to "S-Off".
So to get back to a stock "S-On/Locked" from any of these states:
"S-On/Unlocked or Relocked"
If you are S-On and have used HTC Dev Unlock, you will need to do S-Off to get the "Locked" message back. Run a RUU, then do S-On procedure.
"S-Off/Locked"
If you are S-Off but have *not* used HTC Dev Unlock after the S-Off procedure, you should just need to run a RUU and do S-on.
"S-Off/Unlocked or Relocked"
If you are S-Off and have used HTC Dev Unlock since the S-Off procedure, you must run a RUU, re-lock the bootloader if you have not done so before, and do S-On. Then, do the S-off procedure (keep the stock bootloader, do not flash a modded one) and do S-on again.
Click to expand...
Click to collapse
So I was s-off and unlocked. I just flashed the latest ICS RUU. Now you are saying I need to lock my bootloader and then s-on? Then s-off with the wire trick again, then s-on one more time? Will this all work with the latest RUU I have installed?
It sounds too complicated to get rid of the "RELOCKED" sign...
WARNING!!!
DO NOT attempt this process unless you are on a STOCK, HTC HBOOT.
S-ON with an ENG HBOOT will BRICK your device!!!
In other words, Only attempt this AFTER flashing back to a STOCK RUU. (as this will flash the STOCK HBOOT.)
I know the process JUST came out, but I'm sure this will eventually come in to use.
Instructions:
1) Download and run an RUU. Found HERE
2) Open a cmd window. Plug in phone, charge only mode, usb debugging on.
3) Run the following:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Disclaimer:
I am not responsible for anything harmful that happens to your phone. Use at your OWN risk. Thank you.
http://forum.xda-developers.com/showthread.php?p=35437335
reserved.
reserved. 2.
Do these steps clear the "relocked" flag?
Sent from my ADR6410LVW using Tapatalk 2
mdmower said:
Do these steps clear the "relocked" flag?
Sent from my ADR6410LVW using Tapatalk 2
Click to expand...
Click to collapse
Whatever it said when it was S-ON is my understanding. but since I haven't yet tested this for our phone I can't say 100%
From the looks of your post, I guess you sourced the information from http://forum.xda-developers.com/showthread.php?t=1612937, which I also had bookmarked for my future reference. From that thread, here's how I understand it:
If we S-OFF then unlock, we can expect RELOCKED after S-ON.
If we S-OFF but keep bootloader locked, we can expect LOCKED after S-ON.
It doesn't look like we can expect a custom tag to stick around after S-ON.
Source post (different phone, so may not be the same for us)
scotty1223 said:
correct. only way to get locked back,is to turn s-on,then re unlock and re-s-off. and then,do not unlock after s-off. your hboot will stay locked and you can s-on again,if you need to. just keep in mind that turning s-on should only be done for warranty purposes.
Click to expand...
Click to collapse
mdmower said:
From the looks of your post, I guess you sourced the information from http://forum.xda-developers.com/showthread.php?t=1612937, which I also had bookmarked for my future reference. From that thread, here's how I understand it:
If we S-OFF then unlock, we can expect RELOCKED after S-ON.
If we S-OFF but keep bootloader locked, we can expect LOCKED after S-ON.
It doesn't look like we can expect a custom tag to stick around after S-ON.
Source post (different phone, so may not be the same for us)
Click to expand...
Click to collapse
Yes Sir, indeed.
Andy real quick question flashing ruu well eliminate soff correct
No, hence post 1. I'm guessing this relates to your MIUI adventure. You can have S-OFF and LOCKED bootloader.
Sent from my ADR6410LVW using Tapatalk 2
no this command, and this command only is what I know to get to S-ON
fastboot oem writesecureflag 3
andybones said:
WARNING!!!
DO NOT attempt this process unless you are on a STOCK, HTC HBOOT.
S-ON with an ENG HBOOT will BRICK your device!!!
In other words, Only attempt this AFTER flashing back to a STOCK RUU. (as this will flash the STOCK HBOOT.)
I know the process JUST came out, but I'm sure this will eventually come in to use.
Instructions:
1) Download and run an RUU. Found HERE
2) Open a cmd window. Plug in phone, charge only mode, usb debugging on.
3) Run the following:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Disclaimer:
I am not responsible for anything harmful that happens to your phone. Use at your OWN risk. Thank you.
Click to expand...
Click to collapse
your link to ruu's doesn't point to RUU's for the HTC Evo 4G LTE. Here is the correct link http://shipped-roms.com/index.php?category=android&model=Jewel
IXVash said:
your link to ruu's doesn't point to RUU's for the HTC Evo 4G LTE. Here is the correct link http://shipped-roms.com/index.php?category=android&model=Jewel
Click to expand...
Click to collapse
Erm, wrong forum IXVash?
andybones said:
WARNING!!!
DO NOT attempt this process unless you are on a STOCK, HTC HBOOT.
S-ON with an ENG HBOOT will BRICK your device!!!
Click to expand...
Click to collapse
andybones refers to this, but to clarify, the DirtyRacun hboot is an engineering hboot. If going s-on, make sure to run the RUU first.
Sent from my Fireball using Xparent Blue Tapatalk 2
IXVash said:
your link to ruu's doesn't point to RUU's for the HTC Evo 4G LTE. Here is the correct link http://shipped-roms.com/index.php?category=android&model=Jewel
Click to expand...
Click to collapse
that's because this is the HTC DROID INCREDIBLE 4G LTE FORUM... NOT THE EVO 4G LTE.
I know my RUU's point to the correct thread... because I made it!
Do I need to flash the dirty racun hboot from their page? Is having the dirt racun hboot important? Mine says 1.15.000 I have since gaining s-off have had to flash our ruu.
*Edit* I went ahead flashed it now I'm back to where I was after the s-off tool right where I needed to be
sent from my all powerful INC4G
mdmower said:
Erm, wrong forum IXVash?
Click to expand...
Click to collapse
well crap. Sorry It was a long night /facepalm
prairiedogn said:
Do I need to flash the dirty racun hboot from their page? Is having the dirt racun hboot important? Mine says 1.15.000 I have since gaining s-off have had to flash our ruu.
*Edit* I went ahead flashed it now I'm back to where I was after the s-off tool right where I needed to be
sent from my all powerful INC4G
Click to expand...
Click to collapse
The ENG HBOOT has different options. Glad you got it back.
sent from my DINC4 using Tapatalk 2
Hi,
I need stock "Locked" bootloader.
I've RUU the DirtyRacun Phone by advice as an attempt to fix (SIM failed) and now the Phone is S-OFF with stock Hboot "RELOCKED". Had to unlock the device again for last fix attempts.
Will flashing with S-OFF with stock signed Hboot clear bootloader security flags changing "RELOCKED" back to "LOCKED"?
Now RUU doesn't deliver "Locked" bootloader status. Should I next Flash signed stock Hboot first? Or should I Flash a DR Hboot then RUU again?
Last I would do your posted above for S-ON from Fastboot down since OS locks (no ADB).
Don't want to brick my phone.
Thanks In Advance!
mpeg3s said:
Hi,
I need stock "Locked" bootloader.
I've RUU the DirtyRacun Phone by advice as an attempt to fix (SIM failed) and now the Phone is S-OFF with stock Hboot "RELOCKED". Had to unlock the device again for last fix attempts.
Will flashing with S-OFF with stock signed Hboot clear bootloader security flags changing "RELOCKED" back to "LOCKED"?
Now RUU doesn't deliver "Locked" bootloader status. Should I next Flash signed stock Hboot first? Or should I Flash a DR Hboot then RUU again?
Last I would do your posted above for S-ON from Fastboot down since OS locks (no ADB).
Don't want to brick my phone.
Thanks In Advance!
Click to expand...
Click to collapse
To get back to truly LOCKED, check this post:
http://forum.xda-developers.com/showthread.php?p=35437335
Sent from my Kindle Fire using Xparent Blue Tapatalk 2
junkmail9 said:
To get back to truly LOCKED, check this post:
http://forum.xda-developers.com/showthread.php?p=35437335
Sent from my Kindle Fire using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
nice find man, I made this based off of his post anyway, so his thread would be the place to go, I'll add it to the OP.
Pretty much subject says everything. But here's is my situation.
What I did earlier:
Unlocked Bootloader
Tried S-on with Firewater - didn't work - gave up- didn't spend money for getting S-off via moonshine
Installed TWRP
Installed custom roms
NOW, I need to go back to slock and claim some warranty issue (speakers too harsh)
Here's is an at&t RUU
http://forum.xda-developers.com/showthread.php?t=2757462
Can I go back to stock from here? Do I certainly need S-off? Do I just run RUU exe?
Please help!!
Thanks!
Since you are S-On I believe you have to relock your bootloader in order to run the AT&T RUU
Sent from my HTC One_M8 using Tapatalk
Jano342000 said:
Since you are S-On I believe you have to relock your bootloader in order to run the AT&T RUU
Click to expand...
Click to collapse
That's correct.
Also to the OP, note that AT&T only voids warranty for physical or water damage. They don't care about software mods, although it is a good idea to return to as close to stock as possible before requesting warranty exchange.
RUU is a good way to do so. S-on is fine, but you have to relock the bootloader. The bootloader will then say RELOCKED instead of UNLOCKED or LOCKED. No other evidence of modding should remain after the RUU.