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?
anyone have accomplish this? I've been trying for last few days. I run the gb ruu the latest Ota twice (yesterday I ran it 4 times) and then the s-on command trough fastboot/adb and I'm left whit stock gb, s-on and RE-LOCKED HBOOT.
Is there anyway to get it to LOCKED?
Thanks in Advance
Edit: I've been running the 2.01.605.11 Ota gb ruu.
You need to S-OFF first and then relock it. Running RUU will give you RELOCKED or TAMPERED.
Cares said:
You need to S-OFF first and then relock it. Running RUU will give you RELOCKED or TAMPERED.
Click to expand...
Click to collapse
While s-off run the fastboot commands to relock the HBOOT? Can you tell me those commands? Thanks.
Did you unlock while s-off? If you did, you need to s-off again. After s-off you will have a locked bootloader again. Than ruu to gb ota, and send the s-on commands through fastboot.
That will leave you with stock gb, s-on and lock bootloader.
Do not send the s-on command unless your are 100% sure you have an ota stock hboot. Or you will have a brick
I am pretty sure that there is no way to get it to say locked. It will just say relocked. Someone was working on a way to change that but I think they decided not to continue because they didn't want to be accused of encouraging fraud.
Cares said:
You need to S-OFF first and then relock it. Running RUU will give you RELOCKED or TAMPERED.
Click to expand...
Click to collapse
No no, just do the S-OFF. If you attempt to lock after S-OFF, it will say RELOCKED.
The S-OFF process is the only way to get back to LOCKED. If you unlock or run the fastboot command to lock again after that, it will show RELOCKED.
a.mcdear said:
No no, just do the S-OFF. If you attempt to lock after S-OFF, it will say RELOCKED.
The S-OFF process is the only way to get back to LOCKED. If you unlock or run the fastboot command to lock again after that, it will show RELOCKED.
Click to expand...
Click to collapse
I meant turning security flag on.
Alright thanks guys gonna try again tonight after work. I'll report back later.
You can definitely return to **Locked** without question if you have s-off. Just run the newest leak RUU twice and it should take it back to locked but S-OFF, did it to my girl's unlocked+s-off rezound two nights ago. I didn't even have to manually run it twice, it just keep rebooting and did the 2nd run on it's own. It's now the stock hboot, locked, s-off. Then if you want GB there shouldn't be any issue flashing the GB RUU since you'd maintain S-OFF
PhantomApollyon said:
You can definitely return to **Locked** without question if you have s-off. Just run the newest leak RUU twice and it should take it back to locked but S-OFF, did it to my girl's unlocked+s-off rezound two nights ago. I didn't even have to manually run it twice, it just keep rebooting and did the 2nd run on it's own. It's now the stock hboot, locked, s-off. Then if you want GB there shouldn't be any issue flashing the GB RUU since you'd maintain S-OFF
Click to expand...
Click to collapse
So the newest one is this one?
3.14.605.10
Kratz17 said:
So the newest one is this one?
3.14.605.10
Click to expand...
Click to collapse
right
PhantomApollyon said:
right
Click to expand...
Click to collapse
Ok gonna give a shot to that. Thanks.
Hi,
My Evo 3d GSM device was S-OFF by the Revolutionary method.
All work fine.
But for garanty purpose, l've already restored boot_signed and system.img from stock rom.zip
Can i restore original recovery with:
fastoot flash recovery recovery_signed.img ?
And Restore stock hboot with:
fastoot flash hboot hboot_SHR_U_1.53.0007_20120522_signedbyaa.nb0 ?
Thank before,
If you really want to go back to stock, run the ruu for your region/carrier. It will leave you s-off, but everything else stock. You could go 100 percent stock by going back to s-on first. EDIT: After! See ramjet's post below.
Imagika FTW... with Tapatalk 2
Running the RUU should restore the default recovery and leave you s-off if it is going in for warranty work don't forget you want to be s-on (fastboot oem lock) after running the RUU.
coal686 said:
If you really want to go back to stock, run the ruu for your region/carrier. It will leave you s-off, but everything else stock. You could go 100 percent stock by going back to s-on first.
Click to expand...
Click to collapse
ItzCrooK2UxD said:
Running the RUU should restore the default recovery and leave you s-off if it is going in for warranty work don't forget you want to be s-on (fastboot oem lock) after running the RUU.
Click to expand...
Click to collapse
That's the command to relock after doing the HTC unlock. The command to set S-ON is "fastboot oem writesecureflag 3" and should only be run after the RUU is flashed and the stock bootloader is restored. If S-ON is set while a modified bootloader such as ENG, Revolutionary, or Juopunutbear is installed it will brick the phone.
ramjet73
ramjet73 said:
That's the command to relock after doing the HTC unlock. The command to set S-ON is "fastboot oem writesecureflag 3" and should only be run after the RUU is flashed and the stock bootloader is restored. If S-ON is set while a modified bootloader such as ENG, Revolutionary, or Juopunutbear is installed it will brick the phone.
ramjet73
Click to expand...
Click to collapse
So ramjet: if s-on, you lock then run ruu. But if s-off, you run ruu then lock if you wish. Is that right? I know it's a different kind of lock, but i didn't realize order mattered going s-off to s-on.
Imagika FTW... with Tapatalk 2
coal686 said:
So ramjet: if s-on, you lock then run ruu. But if s-off, you run ruu then lock if you wish. Is that right? I know it's a different kind of lock, but i didn't realize order mattered.
Click to expand...
Click to collapse
Yes, those are separate S-OFF's. The bootloader unlock (hboot S-OFF) is different from the radio S-OFF. This post from the MeanROM ICS thread has an explanation by Unknownforce, the developer behind the the hboot 1.4 downgrade method for radio S-OFF.
The "fastboot oem lock" command will undo the bootloader S-OFF, which is required to run the RUU.exe for users that are radio S-ON. Users that are radio S-OFF can run the RUU.exe without any special considerations.
Once the RUU.exe is run and the stock bootloader is installed, the phone will be bootloader S-ON regardless of the radio S-OFF status. To run fastboot commands like "flash" and "erase" the stock bootloader needs to be unlocked by the htcdev method or a custom bootloader modified to support those commands needs to be flashed, which requires radio S-OFF.
After installing a custom bootloader, setting radio S-ON via the "fastboot oem writesecureflag 3" bricks the phone because the bootloader is not signed by HTC and that is not allowed with radio S-ON. Therefore a stock bootloader needs to be reinstalled before setting radio S-ON and the easiest way to do that is flash an RUU.exe.
Hope that makes sense.
ramjet73
Makes perfect sense. Thanks boss. Learn something new everyday. :thumbup:
Imagika FTW... with Tapatalk 2
Thank-you very much for all your post, and a special thank to ramjet73.
It's clear now, but I will try tomorow.
result
Hello,
After all your explanations, I was reassured to install "RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed.exe"
Unfortunately it did not work: probably due to the absence of CID (HTC__203) of the revolutionary HBOOT.
So I took the rom.zip file in the% temp% directory and I renamed PG86IMG.zip. I pushed on my sdcard.
A reboot in the bootloader and the EVO 3D has successfully installed the ROM with firmware radio, recovery, system ... in short, everything
Now my HBOOT is 1.53.0007 HTC, it does not show revolutionary, but it is unlocked and S-OFF
Now I think it is acceptable to send like that. What do you think?
In fact I've not said what the problem was my phone: After installing a ROM that had the good idea to turn xLOUD (I think that's it) it has blown me the speaker (communication only)
Thank you again for your help
The latest changes
fxjumper said:
Now my HBOOT is 1.53.0007 HTC, it does not show revolutionary, but it is unlocked and S-OFF
Now I think it is acceptable to send like that. What do you think?
Thank you again for your help
Click to expand...
Click to collapse
Ok, i dit it !
Code:
fastboot oem lock
relocked my phone
and
Code:
fastboot oem writesecureflag 3
put my phone S-ON ! (radio)
Everything was fine in the end? I'm in the exact same situation and I'm installing PG86IMG.zip as we speak. Did HTC see anything wrong with your phone?
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.