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
Related
I'm currently s-offed and running 2.01.605.11 gb ruu.
Now I need to use the warranty so I need to change the status s-off/unlocked
to s-on/locked not s-on/re-locked.
How can I do that?
the fact that you are S-off doesnt matter as some devices shipped are s-off but to get to locked run the same gb ruu again but dont unlock.
but if you really care about it saying s-on follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1612937
since you are on stock hboot you'll be fine with these instructions
Po1soNNN said:
the fact that you are S-off doesnt matter as some devices shipped are s-off but to get to locked run the same gb ruu again but dont unlock.
but if you really care about it saying s-on follow the instructions in this thread
http://forum.xda-developers.com/showthread.php?t=1612937
since you are on stock hboot you'll be fine with these instructions
Click to expand...
Click to collapse
by doing this, I can get the s-on, but still I can't get locked.
I need to know how to get locked on the bootloader to use the warranty.
Find a thread that has the correct hboot for your firmware then go to fastboot and type
Code:
fastboot clear cache
fastboot oem reboot ruu
fastboot flash zip (zipnamehere).zip
Then wait a little then do
Code:
fastboot reboot bootloader
That should do it and also I'm not sure it there's a space between reboot and ruu so try both
Sent from my ADR6425LVW using XDA
1. do the s-on process
2. re s-off (this will give you locked bootloader)
3. s-on again (to get rid of s-off)
4. ruu to latest offical release
qudwis said:
by doing this, I can get the s-on, but still I can't get locked.
I need to know how to get locked on the bootloader to use the warranty.
Click to expand...
Click to collapse
Follow Scotty123 guide to s on
http://forum.xda-developers.com/showthread.php?p=25165453
Then do the jouponut s off method. Flash files as ph98img after if you choose not to change to a eng hboot.
I had to find this out the hard way since was one of the release day 1 s off users an unlocked thinking a ruu would revert back to locked.
Sent from my Rezound
RoryHe said:
1. do the s-on process
2. re s-off (this will give you locked bootloader)
3. s-on again (to get rid of s-off)
4. ruu to latest offical release
Click to expand...
Click to collapse
ericsignals said:
Follow Scotty123 guide to s on
http://forum.xda-developers.com/showthread.php?p=25165453
Then do the jouponut s off method. Flash files as ph98img after if you choose not to change to a eng hboot.
I had to find this out the hard way since was one of the release day 1 s off users an unlocked thinking a ruu would revert back to locked.
Sent from my Rezound
Click to expand...
Click to collapse
All of this going back to s-on is not necessary at all. Just flash the same hboot like I said before and you'll be fine
Sent from my ADR6425LVW using XDA
RoryHe said:
1. do the s-on process
2. re s-off (this will give you locked bootloader)
3. s-on again (to get rid of s-off)
4. ruu to latest offical release
Click to expand...
Click to collapse
What he said.... I got confused and was thinking of the steps I did to get back to locked and s off :banghead:....forgot op was inquiring about for warranty reasons. Weekend can't come soon enough LOL
Sent from my Rezound
Po1soNNN said:
All of this going back to s-on is not necessary at all. Just flash the same hboot like I said before and you'll be fine
Sent from my ADR6425LVW using XDA
Click to expand...
Click to collapse
So if I'm unlocked only, no s-off, just find my hboot somewhere, rename it, flash it, reboot and I'm factory stock?
Sent from my Rezoundizzle
Remember IF ON AN ENG OR PATCHED HBOOT YOU WILL BRICK!
Phaded said:
So if I'm unlocked only, no s-off, just find my hboot somewhere, rename it, flash it, reboot and I'm factory stock?
Sent from my Rezoundizzle
Click to expand...
Click to collapse
No you have to be s-off to be able to make it say locked
Sent from my ADR6425LVW using XDA
qudwis said:
I'm currently s-offed and running 2.01.605.11 gb ruu.
Now I need to use the warranty so I need to change the status s-off/unlocked
to s-on/locked not s-on/re-locked.
How can I do that?
Click to expand...
Click to collapse
I think this is what your looking for.
http://forum.xda-developers.com/showthread.php?t=1620211
my first post is the only way to get to 100% stock that i am aware of ... if he is unlocked he will have to s-off to get it to say locked and then s-on to get it back.
if he locks it with the fastboot command it will say lock and if he is s-on not sure but i know if you are s-off you will stay unlocked or relocked even if you flash new hboot's
Thanks if i helped
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?
I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
anonimoyque said:
I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
Click to expand...
Click to collapse
Remove/replace the battery and restart the bootloader and try flashing the RUU again. If that doesn't work you can try flashing the RUU.exe from Windows with the bootloader in "fastboot USB" mode.
ramjet73
anonimoyque said:
I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
Click to expand...
Click to collapse
one thing i have learned is when flashing roms, make sure you have the correct firmware package, and hboot.. because some Roms use the VM Firmware from the leak a few months back, while others use the Sprint Firmware, also depending on the base of the rom you may need to flash a newer or older hboot
anonimoyque said:
I am having huge Issues with HTC EVO Sprint
I tried to install MikVirgin-RC3-signed, but I got a bootloop when systen was goign to start, I did many fixes and now after I install any rom i gets stuck after a few seconds of lading and then reboots itself.
Also I tried to unroot my cell phone but I get the message relocked security warning and I am unable to install PG86IMG_Shooter_S_Sprint_WWE_2.17.651.5_Radio_1.06.00.1216_NV_NV_spcs_1.42_release_233304-signed
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
PLEASE HEELP I NEED TO FIX THIS
Click to expand...
Click to collapse
try unlocking your bootloader again and THEN flashing that gingerbread RUU best to also have s-off... but if not you should still be ok .... but the unlocked bootloader is a must... you said youre relocked...
wloftus said:
try unlocking your bootloader again and THEN flashing that gingerbread RUU best to also have s-off... but if not you should still be ok .... but the unlocked bootloader is a must... you said youre relocked...
Click to expand...
Click to collapse
I agree about being s-off, but the ruu.exe will error out if the bootloader is unlocked. You must relock the bootloader first.
coal686 said:
I agree about being s-off, but the ruu.exe will error out if the bootloader is unlocked. You must relock the bootloader first.
Click to expand...
Click to collapse
i use linux so i dont do the EXE's... i take the RUU and rename it to PG86IMG.zip and it still works unlocked or not... just different approaches depending on the OS you use i guess
wloftus said:
i use linux so i dont do the EXE's... i take the RUU and rename it to PG86IMG.zip and it still works unlocked or not... just different approaches depending on the OS you use i guess
Click to expand...
Click to collapse
That should be the same thing as long as the RUU.zip is extracted from the RUU.exe and properly signed.
But coal is right about needing the bootloader locked/relocked to flash the RUU if you are S-ON (which the OP said he is), regardless of whether you use the RUU.exe or RUU.zip.
ramjet73
ramjet73 said:
That should be the same thing as long as the RUU.zip is extracted from the RUU.exe and properly signed.
But coal is right about needing the bootloader locked/relocked to flash the RUU if you are S-ON (which the OP said he is), regardless of whether you use the RUU.exe or RUU.zip.
ramjet73
Click to expand...
Click to collapse
no he is not...ive reloaded GB and ICS manually while being unlocked you cant tell me what i have and have not done considering IM the one thats done it
wloftus said:
no he is not...ive reloaded GB and ICS manually while being unlocked you cant tell me what i have and have not done considering IM the one thats done it
Click to expand...
Click to collapse
Unlocked and S-OFF, right? That works fine but an RUU flash with S-ON and an unlocked bootloader will fail, regardless of how you do it.
If you don't believe me set your phone back to S-ON and try it.
From the OP:
I am able to go into bootloader
I have:
Shooter XC SHIP S-ON RL
Hboot-1.50.0000
Radio 1.06.00.1216
eMMC-boot
Aug 7 2011,10:21:40
Click to expand...
Click to collapse
That sure looks like S-ON to me. The reason I jumped back into this thread is that I don't want other users getting incorrect information.
ramjet73
ramjet73 said:
Unlocked and S-OFF, right? That works fine but an RUU flash with S-ON and an unlocked bootloader will fail, regardless of how you do it.
If you don't believe me set your phone back to S-ON and try it.
From the OP:
That sure looks like S-ON to me. The reason I jumped back into this thread is that I don't want other users getting incorrect information.
ramjet73
Click to expand...
Click to collapse
make up your mind you first said its the locked relocked status... now you say its the s-on , s-off status....if iive still done flashes with the s-on status and while still unlocked so i dont know what problems you all are running into
wloftus said:
make up your mind you first said its the locked relocked status... now you say its the s-on , s-off status....if iive still done flashes with the s-on status and while still unlocked so i dont know what problems you all are running into
Click to expand...
Click to collapse
I don't think so.
You really should try flashing an RUU (.exe or .zip) with radio S-ON and an unlocked bootloader before you advise other users to try that. If you can do that successfully I will admit I am wrong in this thread. Otherwise, please stop insisting that it will work.
You have been ignoring the fact that the OP is S-ON throughout this thread and that really isn't going to help him at all.
ramjet73
ramjet73 said:
I don't think so.
You really should try flashing an RUU (.exe or .zip) with radio S-ON and an unlocked bootloader before you advise other users to try that. If you can do that successfully I will admit I am wrong in this thread. Otherwise, please stop insisting that it will work.
You have been ignoring the fact that the OP is S-ON throughout this thread and that really isn't going to help him at all.
ramjet73
Click to expand...
Click to collapse
i have... i infact did it earlier with the upgrade to ICS while flashing the firmware.zip file after renameing it to PG86IMG.zip and WOW it worked... im done arguing ... this is my last post... post again if you feel you need the last word....
wloftus said:
im done arguing ... this is my last post... post again if you feel you need the last word....
Click to expand...
Click to collapse
Thank you. I will make one last post just so people are clear on the requirements for flashing an RUU with S-ON.
Here's a quote from mpgrimm2's My Running stock RUU Reference info post:
Note 3: If you previously did the HTC Unlock, you'd have to "RELOCK" BEFORE running the RUU.
To do this from fastboot type: fastboot oem lock
Click to expand...
Click to collapse
That guide has been around for a long time on XDA and another website and it has been used by a lot of people, including myself. If that information was wrong, I'm sure mpgrimm2 would have corrected it by now.
If you want to flash an RUU with S-ON and an unlocked bootloader, make sure that you relock it before flashing or you will get an error.
ramjet73
wloftus, I'm not saying you're lying since as you said, you were the one who did it and you say it worked for you. But, if one is s-on and unlocked, the ruu will error out with error 155. I google searched ruu lock bootloader error and found many sites that say the bootloader must be locked if s-on (see below). But, if one wants to try while leaving the bootloader unlocked, then be my guest. If it works, great; if not, then relock the bootloader.
Sources:
Should I relock my bootloader
[HOW TO] Flash RUU / OTA when getting ERROR 155 although phone is back to stock
And one specific to the Evo3d: http://forums.androidcentral.com/htc-evo-3d/198402-ruu-2-89-651-2-hboot-1-58-a.html#post2084625
wloftus said:
try unlocking your bootloader again and THEN flashing that gingerbread RUU best to also have s-off... but if not you should still be ok .... but the unlocked bootloader is a must... you said youre relocked...
Click to expand...
Click to collapse
Hey thanks for your comment, yes it says relocked but also Security Warning... do you know how can I remove this? so I can leave it locked again and try to reinstall the stock RUU?
ramjet73 said:
Unlocked and S-OFF, right? That works fine but an RUU flash with S-ON and an unlocked bootloader will fail, regardless of how you do it.
If you don't believe me set your phone back to S-ON and try it.
From the OP:
That sure looks like S-ON to me. The reason I jumped back into this thread is that I don't want other users getting incorrect information.
ramjet73
Click to expand...
Click to collapse
I agree with you... the probllem is that I cannot relock the cell phone... when I try I get the message relocked but also the message security warning!!
how can I remove it??
anonimoyque said:
I agree with you... the probllem is that I cannot relock the cell phone... when I try I get the message relocked but also the message security warning!!
how can I remove it??
Click to expand...
Click to collapse
There's a thread here that discusses, but people seem to have used various methods to solve it from restarting the bootloader to reflashing their unlock token. That's why I recommended in my first post of this thread that you remove/replace the battery and restart the bootoader.
ramjet73
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.
I have read pages and pages from the Android Development forum for the HTC Evo 4G LTE and I can't seem to find a solution that works for me because going S-OFF or re-locking bootloader and loading RUU does not seem feasible for my situation.
The phone has custom recovery (TWRP) and we successfully loaded Viperboy's deodexed 3.15 stock ROM.
Baseband is 1.02.12.0427 (super outdated)
This phone was bought second hand and is a HTC dev unlocked phone, S-ON
I would like to update the baseband to 1.12.11.1200 and update the firmware to 3.16
Caveats: I don't have access to the phone, my friend can reload custom ROMs through TWRP, but beyond that I don't think we can go through Dirty Racun and S-Off, I don't know how we can easily check the HBOOT version to determine if the HBOOT version is 1.12
What would happen if we accepted the Sprint OTA? Are we SOL with the baseband because we are S-ON?
Is there any way we can get on MeanBean 3 or stock rooted 3.16?
Any advise would be greatly appreciated.
I wouldnt accept the OTA update to 3.16
I actually did just that when I relocked my phone on Saturday and had all sort of problems after that. Now, I'm not too sure you would even be able to install the update being that your phone is unlocked *citation needed*.
http://forum.xda-developers.com/showthread.php?t=2135670 - talks about the 3.16 OTA problems
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
BaconMunch said:
thanks, I've definitely advised my friend to stay away from the OTA and disregard it. I think we are experiencing call/wifi issues due to the old baseband. I wonder what are the next possible steps to move forward from here...
Click to expand...
Click to collapse
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
tilltheend714 said:
1. Stay on this baseband and deal with it.
2. Relock and RUU your way up to 3.15 (stay away from 3.16)
3. S-off and Flash a couple full firmware zips.
Sadly I think those are your only option. And to check your hboot just boot into bootloader. Hold volume down when powering on.
Click to expand...
Click to collapse
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
BaconMunch said:
Thanks, I think that seems realistic, I'm concerned that if I relock through HTCDev, I read that some email/password might go to the original seller of the phone (ebay) for confirmation code, so I don't want to get stuck halfway
I am definitely crossing my fingers for HBoot v1.12, to confirm, once I check my version in the bootloader, I guess I can escape without taking any of the menu options (checking YouTube, I'll just go to recovery, enter TWRP, reboot, system).
Click to expand...
Click to collapse
Relocking the phone is done through fastboot on the computer. Nothing to do with HTC. And Dev unlocked means you get an unlock token from HTC to the email that you signed up with. So if you make your own account on HTC dev and request a token, it should send nothing to the other owner.
And sorry, but I don't understand what you mean by having Hboot 1.12. You mean only flashing the radio through recovery? If that's what you mean than I can't help with that. Not sure how that works or if there are problems with that.
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
BaconMunch said:
great news! I had someone take screen shots of the HBoot (v.1.12.0000) and TWRP (v2.2.1) menu
Bootloader shows:
Code:
*** TAMPERED ***
*** UNLOCKED ***
JEWEL PVT SHIP S-ON RL
HBOOT-1.12.0000
RADIO-1.02.12.0427
OpenDSP-v25.1.0.32.0405
eMM-boot
So as far as I know, I'm going to make sure there's nothing wrong with the TAMPERED, and then I can flash 1.12.11.1210 through Captain_Throwbacks Radio Only zip and then looks for a 3.16 custom firmware compatible with S-On since I'm on build number 3.15.651.16 CL124461.
I'd appreciate anyone to chime in if I'm going down a bad path here. Cheers!
Click to expand...
Click to collapse
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
xlxcrossing said:
You've indeed unlocked the bootloader properly but this only let's you flash recoveries and custom roms. You have to S-OFF the phone to update firmware via bootloader. You're other option would be to RUU which would upgrade the firmware and software and that CAN be done with S-ON, however there is a problem with the update which disables touch input so you should either wait for a dev to make custom 3.16 rom and forget about the firmware OR wait for a fix from HTC and run that RUU whenever it comes out.
Click to expand...
Click to collapse
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
My advice is get s-off it will save alot of headaches down the road
Sent from my PoS MoPho
BaconMunch said:
Thanks xlxcrossing! I messaged Captain for a a recovery flash for the baseband only and he said my approach is no good either. So seems like I have to RUU to get off 1.12 anyways since LazyPanda is not supported and DirtyRacun starts at 1.15
So I am looking at the UNLIMITED.IO site now
step 1) relock via fastboot
step 2) RUU 1.15 or 1.19 (so this means my firmware/software/hboot will be updated as well?)
From here if I stop, I will be S-ON so I can...
option 1) RUU 2.09 and stay on 3.15
option 2) unlock bootloader from HTCDev and stay S-ON
option 3) unlock bootloader from HTCDev and DirtyRacun S-OFF (which actually seems like a very simple process once unlocked)
Click to expand...
Click to collapse
Sent you a PM
The advice is free....the bandwidth, not so much
Just wanted to say thank you all for the support and advice.
I finally walked my friend over gtalk and successfully achieved S-OFF after relock, 1.15 RUU, unlock with HTC DEV, dirtyracun
Then updated full firmwares incrementally to 3.16
Then while trying to load MeanBean, realized we lost TWRP (and possibly root, need to confirm), I can only guess that went away with the RUU? That's not really documented anywhere unless that's a known thing.
TWRP installation via goomanager failed (maybe due to lack of root), I was able to find TWRP v2.3.1 bootloader, installed that and installed MeanBean 3.0.4
I think that makes us up to date, however we will likely install SuperSU via TWRP once we customize and ensure the phone is running smoothly.
Thanks again all!
Super su is included with the ROM
Sent from my EVO using xda premium