As I had the unfortunate pleasure of receiving my phone with 1.5 already on it I had used HTC's unlock method. However now, I was able to downgrade my HBoot to 1.40 with this amazing guide by Unknownforce and was able to finally attain S-OFF.
To get back to the latest radios and everything I ran the 2.17 RUU knowing I'd keep S-OFF through it and would downgrade my HBoot afterwards. However, I noticed that I still have the mark of *** RELOCKED *** above S-OFF (I had to relock it to use the RUU to brick).
I downgraded (again) back to 1.40 HBoot but I'm curious if it's possible to hide the fact that I've unlocked in case I ever have to turn my phone back into Sprint.
I would have thought that replacing the HBoot partion with the stock 1.40 image with the emmc_recover tool would have overwritten that. I take it that means that the locked/unlocked/relocked flag is stored elsewhere?
If you did HTC unlock then sprint has your serial numbers on file that you did it so dont worry about it
Sent from my PG86100 using Tapatalk
These steps will get you completely back to stock.
I want to first say thanks to the unlimited.io team for making S-OFF possible.
Secondly, by following these instructions you are acknowledging that should something go wrong and you brick your device, I am not at fault nor are the developers of the S-OFF method for the HTC RUBY. Follow these instructions at your own risk! I am NOT a dev, just stupid enough to be the first one (I think) To try this. I am not going to give instructions on how to use fastboot, if you are S-Off, then you should already know.
Third, you WILL be able to re-unlock your bootloader and regain S-OFF after you have followed these instructions. If you want to do so, there are other threads on how to do that.
And 4th, I have only tried this on a tmobile branded device. I have no idea if this works on any other device. I think it should, but I don't know for sure. If anybody wants to give it a try and let me know, then i will update the OP.
Now to the steps.
1. Download the stock ruu from here
2. Lock your bootloader by using the fastboot command "fastboot oem lock"
3. Reboot to system
4. Flash the stock RUU you downloaded by placing it in the root of your external sd card and renaming it PH85IMG.zip and rebooting to bootloader.
5. Once you have the stock rom reinstalled, set the security lock by using fastboot command " fastboot oem writesecureflag 3"
6. Profit?
That's it!
Special thanks to frodoboy for the idea and to krook6023 for posting the stock RUU's.
If this helped you at all, please remember to hit the thanks button!
Security lock by using fastboot command (S-ON) requires a stock RUU beforehand?
interesting
kaabob said:
Security lock by using fastboot command (S-ON) requires a stock RUU beforehand?
interesting
Click to expand...
Click to collapse
I should have clarified, the steps are if you want to go completely stock, will update the OP.
Will it read "relocked" or "locked"? I thought being "completely stock" was not totally possible because it would always say "relocked".
Sent from my HTC_Amaze_4G using XDA
bjcolema said:
Will it read "relocked" or "locked"? I thought being "completely stock" was not totally possible because it would always say "relocked".
Sent from my HTC_Amaze_4G using XDA
Click to expand...
Click to collapse
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
kishon120 said:
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
Click to expand...
Click to collapse
That's good to know. Thanks.
Sent from my HTC_Amaze_4G using XDA
kishon120 said:
No it wont. Sometimes when you flash ROMs after the ics leak it'll go back to locked . Only if you do it manually through fast boot it will say re-locked.
Click to expand...
Click to collapse
Thanks for replying.
This is correct, my phone said locked, not relocked.
I would like to stress that YOU NEED A FULL RUU, not a stock nandroid backup. Otherwise, you are going to need that link on my sig
Sent from my HTC Sensation using XDA
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Thaxtonator said:
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Click to expand...
Click to collapse
You can't downgrade back to GB once you've updated to ICS, if that's what you're trying to do. At least not very easily.
electronicrice said:
You can't downgrade back to GB once you've updated to ICS, if that's what you're trying to do. At least not very easily.
Click to expand...
Click to collapse
If you are S-Off, then following this guide will put you back to stock gingerbread.
Thaxtonator said:
Quick question- I want to send my Amaze back for warranty exchange, and I already tried following this but it said my HBOOT was too new to flash the RUU. I am S-On so I think this is the problem. Do you know of any way around this?
Click to expand...
Click to collapse
I dont know a way for going back to stock without being s=off. You could possibly flash the newest official release (ics, one that hasnt been modified) then relock your bootloader, but i think that it will show relocked rather than locked. Worth a try though.
Okay thanks for the input guys. It isn't a huge deal, I just didn't think there was enough "goodies" rom-wise for ICS, but there are some hardworking devs on here. Looking forward to the Sense 4.0 rom.
dcmtnbkr said:
Special thanks to frodoboy for the idea and to krook6023 for posting the stock RUU's.
If this helped you at all, please remember to hit the thanks button!
Click to expand...
Click to collapse
Thanks for the "thanks" dcm. Question though. I'm sure you've gone back to S-Off so did you have to do the wire trick again or just try the fastboot oem writesecureflag 0 or whatever it needs to be to go S-Off again?
frodoboy said:
Thanks for the "thanks" dcm. Question though. I'm sure you've gone back to S-Off so did you have to do the wire trick again or just try the fastboot oem writesecureflag 0 or whatever it needs to be to go S-Off again?
Click to expand...
Click to collapse
When s-on, you can't go back to s-off by writing the security flag again . You have to do again the juopunutbear procedure including the wire trick
Sent from my HTC Sensation Z710e
Just curious which RUU one should flash if returning to stock?
RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14. 550L.17DC_30.78.550L.15_release_257469_signed.zip
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip
PH85IMG_Ruby_TMOUS_1.36.531.6_Radio_1.07.550L.04DC _30.64.550L.07_release_219373_signed.zip
3oudreaux said:
Just curious which RUU one should flash if returning to stock?
RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
OTA_RUBY_ICS_35_S_TMOUS_2.14.531.3-1.43.531.3_release_259660ggzpa27mj01s2ayu.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.3_Radio_1.14. 550L.17DC_30.78.550L.15_release_259626_signed.zip
PH85IMG_RUBY_ICS_35_S_TMOUS_2.14.531.1_Radio_1.14. 550L.17DC_30.78.550L.15_release_257469_signed.zip
PH85IMG_Ruby_TMOUS_1.43.531.3_Radio_1.08.550L.19DC _30.66.550L.08D_release_228638_signed.zip
PH85IMG_Ruby_TMOUS_1.36.531.6_Radio_1.07.550L.04DC _30.64.550L.07_release_219373_signed.zip
Click to expand...
Click to collapse
This one would be best: RUBY_ICS_35_S_TMOUS_2.14.531.3_R2_Radio_1.14.550L. 17DC_30.78.550L.15_release_262141_signed.zip
I spent 3 hrs trying to solve the relocked and locked issue until finally I got it resolved. with the manual option to lock with hasoon tool, places *** RELOCKED *** in hboot, which clearly and obvious for any technician to see you tampered with the hboot files from stock. my reason for doing this to get my warranty back.
how did i fixed "RELOCKED" to show as *** LOCKED *** ? after the hasoon tool 3.2 relocked the bootloader i was challenged, but decided the first step would be switching the security off and on (s-off/ s-on)
first return to stock RUU through boot loader, then adb command fastboot oem writesecureflag 3 to enable s-on. *toggled it on
i reinstalled juopunutbear s-off again carefully following the instructions. with a paperclip grounding the phone and selecting for juopunutbear's modified files "y" enter.
then your *** RELOCKED *** shows as *** juopunutbear *** in hboot. (at first i thought I dig myself a bigger hole)
I used Hasoon tool 3.2 again to RELOCK bootloader, with the intention of reinstall the stock RUU again. however it still showed as *** juopunutbear *** with the message its already locked.
Now I installed the the Stock RUU again from bootloader. once complete back to the hboot, to show *** LOCKED *** and s-off Progress!!!
repeat enable s-on instructions by writing adb: fastboot oem writesecureflag 3,
now shows
*** LOCKED ***
RUBY PVT SHIP S-ON RL
HBOOT-1.93.0002
OpenADSP-02.6.0.2226.00.0202
eMMC-boot
a step closer for the warranty being back to the device, without a dispute with the warehouse/ carrier
how do we delete the line -OpenADSP-02.6.0.2226.00.0202?
it was added with the juopunutbear s-off hboot files, without that file the hboot would be 100 percent legit for the warranty!
aoakes said:
how do we delete the line -OpenADSP-02.6.0.2226.00.0202?
it was added with the juopunutbear s-off hboot files, without that file the hboot would be 100 percent legit for the warranty!
Click to expand...
Click to collapse
No need to get rid of that. New phone from T-Mobile with HBOOT 1.93 and it had that line it . It looks like 1.90 is the one that doesn't have that line. Because my wife's phone is on 1.90 and she doesn't have it.
I'm going to be following the method in a few days. Can you guys confirm this all works as it should?
is there a way to get the bootloader back to a pure "locked" designation?!?!
Yes, but it requires performing the S-Off method. Only way it can be done.
rezin said:
is there a way to get the bootloader back to a pure "locked" designation?!?!
Click to expand...
Click to collapse
only if youre s-off
Edit: ninja'd lol
rezin said:
is there a way to get the bootloader back to a pure "locked" designation?!?!
Click to expand...
Click to collapse
Do S-off procedure. That procedure changes the bootloader back to "locked" whenever you go through it as well. You can observe this on an hboot other than JuopunutBear's modded one.
If you want it stock, you have to re-flash a stock RUU and do S-on procedure; check the guide in the Development section.
okay i just ran the newest ruu and noticed it when i rebooted to bootloader...so all i gotta do is run it one more time...then when its fully s-off and labeled "locked" just run the secureflag 3 command again?!?!
rezin said:
okay i just ran the newest ruu and noticed it when i rebooted to bootloader...so all i gotta do is run it one more time...then when its fully s-off and labeled "locked" just run the secureflag 3 command again?!?!
Click to expand...
Click to collapse
Yes you writesecureflag on
So does that mean that you can do the following?
1. S-Off
2. Bootloader shows and "locked" instead of "relocked".
3. S-On
4. Run RUU
5. Warranty replacement with no worries
Nevermind I didn't read the op right :/
das0527 said:
So does that mean that you can do the following?
1. S-Off
2. Bootloader shows and "locked" instead of "relocked".
3. S-On
4. Run RUU
5. Warranty replacement with no worries
Click to expand...
Click to collapse
Then run the RUU *before* S-On... all else before S-On. You must make sure that is stock bootloader and not JuopunutBear or else you risk bricking when writing the security flag command.
And be sure to run the RUU twice to ensure a complete flash.
Also note the JuopunutBear bootloader, if flashed, will read "JuopunutBear" instead of Locked and indeed performs similar to an unlocked stock bootloader. But that JB version is simply hacked; once you flash a stock bootloader over that, it will read Locked.
http://forum.xda-developers.com/showthread.php?t=1612937
Note with that article you may want to do the ICS OTA RUU instead now that it is out.
Hi Everyone. Now I'm on stock hboot 1.53.0007 S-ON and I'd like to do S-OFF. I understand that i should unlock via HTC Dev, then root and after that S-OFF. But my question is how does the bootloader looks after S-OFF via JuopunutBear? Does it make LOCKED and S-OFF? If not what should I do (if it's possible) to go back for a locked bootloader (not relocked)? And if JuopunutBear makes bootloader LOCKED i should be able to flash RUU, than use fastboot oem writesecure flag 3 to make S-ON and that's all? Cheers
c000ler said:
Hi Everyone. Now I'm on stock hboot 1.53.0007 S-ON and I'd like to do S-OFF. I understand that i should unlock via HTC Dev, then root and after that S-OFF. But my question is how does the bootloader looks after S-OFF via JuopunutBear? Does it make LOCKED and S-OFF? If not what should I do (if it's possible) to go back for a locked bootloader (not relocked)? And if JuopunutBear makes bootloader LOCKED i should be able to flash RUU, than use fastboot oem writesecure flag 3 to make S-ON and that's all? Cheers
Click to expand...
Click to collapse
You are most correct sir. After you perform the wire trick the end result is a "locked" bootloader with s-off. With s-off you can flash any version of your carrier and regions ruu. Definetely right after you flash ruu you would fastboot and use that command to get back on s-on. I hope I answered your questions. Please don't hesitate to ask if you need more help. Peace.
Please hit the thank you button if I helped you in anyway.
One more thing. When it comes to the end of S-OFF via JuopunutBear there is a question: Do you want to install juopunutbear modified hboot? What will happen when I'm going to choose No? I will be on stock locked hboot with S-OFF? What pros are with Juopunutbear modified hboot? And I understand that if I want to get rid of Juopunutbear hboot I must flash RUU? Cheers
With s-off you can flash any hboot you desire by renaming the file PG86IMG.zip, place it on root of sd, reboot bootloader.
Jbear hboots accept more adb commands than stock.
sudo passwd root
This is probably a very noob question, but I wanted to know what the purple **Locked** icon meant at the top of the bootloader. When I first got S-Off using juopunutbear that actually read juopunutbear, but to get supercid I reverted hboot SPH 1.93.0002 using the s-off toolkit to flash the hboot After getting supercid the bootloader gives me the purple locked icon. I tried to flash the ENG 1.90.2005 hboot with the s-off tookit also but I'm still on 1.93.0002. id just like to know what the locked icon means and if it's something that will prevent me from flashing roms (I currently on Dark Glass ONE 0.6.) Thanks in advance for any assistance
My bootloader reads as such
*** LOCKED ***
RUBY PVT SHIP S-OFF RL
HBOOT-1.92,0002
OpenADSP-v02. 6. 0.2226.00.0202
eMMC-boot
Mar 15 2012,21:46:51
(don't know if that's needed but i included it)
**Edit**
I think the locked is referring to my bootloader being locked? i seem to remember when i rooted with the root toolkit I used the htcdev method to unlock the bootloader. Is my bootloader locked again?
Pauler1 said:
This is probably a very noob question, but I wanted to know what the purple **Locked** icon meant at the top of the bootloader. When I first got S-Off using juopunutbear that actually read juopunutbear, but to get supercid I reverted hboot SPH 1.93.0002 using the s-off toolkit to flash the hboot After getting supercid the bootloader gives me the purple locked icon. I tried to flash the ENG 1.90.2005 hboot with the s-off tookit also but I'm still on 1.93.0002. id just like to know what the locked icon means and if it's something that will prevent me from flashing roms (I currently on Dark Glass ONE 0.6.) Thanks in advance for any assistance
My bootloader reads as such
*** LOCKED ***
RUBY PVT SHIP S-OFF RL
HBOOT-1.92,0002
OpenADSP-v02. 6. 0.2226.00.0202
eMMC-boot
Mar 15 2012,21:46:51
(don't know if that's needed but i included it)
**Edit**
I think the locked is referring to my bootloader being locked? i seem to remember when i rooted with the root toolkit I used the htcdev method to unlock the bootloader. Is my bootloader locked again?
Click to expand...
Click to collapse
Bootloader is locked again. But with s-off, the unlockng of the bootloader is no longer neccesary
aj_2423 said:
Bootloader is locked again. But with s-off, the unlockng of the bootloader is no longer neccesary
Click to expand...
Click to collapse
Thanks! exactly what I was looking for