Related
has anybody succesfully gotten rid of ***RELOCKED*** on the 3d after rooting? i went back to stock so i am s-on again but want to get rid of the relocked message.
I have a gsm model. Reflashed ruu via pg86img to older version from my carrier. Then fastboot command 'fastboot oem writesecureflag 3' and then I was back to s-on showing lock not relock
I was revolutionary s-off
Sent from my HTC EVO 3D X515m using Tapatalk 2
healer82 said:
I have a gsm model. Reflashed ruu via pg86img to older version from my carrier. Then fastboot command 'fastboot oem writesecureflag 3' and then I was back to s-on showing lock not relock
I was revolutionary s-off
Sent from my HTC EVO 3D X515m using Tapatalk 2
Click to expand...
Click to collapse
Same here got the ruu from xda then run the ruu then head to %TEMP% folder in windows and copy the rom.zip then rename it to PG86IMG.zip place it on sd , boot into bootloader on phone and update. this makes your phone like brand new from factory then connect to pc open command prompt and type "fastboot oem writesecureflag 3" this turns s-off too s-on after this reboot bootloader and you will see ***locked*** s-on
But to do that, you have to be s-off first.
Otherwise there's no way to flash the img via bootloader if i'm not mistaken.
I just tried it (s-on / relocked) and neither the flashing or the fastboot command works unfortunately
KrewsialNL said:
But to do that, you have to be s-off first.
Otherwise there's no way to flash the img via bootloader if i'm not mistaken.
I just tried it (s-on / relocked) and neither the flashing or the fastboot command works unfortunately
Click to expand...
Click to collapse
cant you use the revolutionary method to s-off then flash the ruu zip? then use the command to s-on again. worked for me on hboot 1.4.9.0018 this gives you ***locked*** not relocked!
sonya chin said:
cant you use the revolutionary method to s-off then flash the ruu zip? then use the command to s-on again. worked for me on hboot 1.4.9.0018 this gives you ***locked*** not relocked!
Click to expand...
Click to collapse
I have no clue, i have never been s-off
Sent from my HTC EVO 3D X515m using xda premium
and after you do this LOCKED thing if I go with the phone for warranty they will never know that I had root,will they?
johnmarshton said:
and after you do this LOCKED thing if I go with the phone for warranty they will never know that I had root,will they?
Click to expand...
Click to collapse
Warranty with who? If sprint, they don't even care, you don't need to do all this...
Sent from my PG86100 using XDA
Im having the issue when I put the zip file on my sd card it shows no image in bootloader. I renamed it correctly and im relocked with s-on. im trying to root my 3d.
jamexman said:
Warranty with who? If sprint, they don't even care, you don't need to do all this...
Sent from my PG86100 using XDA
Click to expand...
Click to collapse
HTC Warranty.I'm from Europe
ok i do have sprint...i want the locked message...not relocked.
For me on Sprint version, no matter what I did it would show relocked if I was on hboot 1.50. If i was on hboot 1.40 it was fine. So I stayed 1.40 on went s-on. But HTC may actually upgrade it and check. Not sure.
so if im hboot 1.50 and root, i could downgrade to 1.40 then flash a ruu to loose root and it will show locked in stead of relocked?
does this work if i unlocked the bootloader with the HTCDev method instead of revolutionary?? my evo 3d is GSM
Hey!
Well im about to send my old phone back and ran the RUU then did the s-on procedure. i relocked my bootloader and says relocked.... i ran ruu again and says the same thing! any suggestion?
Do you think verizon would charge me for this?
ryclegman said:
Hey!
Well im about to send my old phone back and ran the RUU then did the s-on procedure. i relocked my bootloader and says relocked.... i ran ruu again and says the same thing! any suggestion?
Do you think verizon would charge me for this?
Click to expand...
Click to collapse
i've never heard of a returned phone being rejected for any reason other than physical damage. and if you are super worried about it there is a link to hex edited hboots.http://forum.xda-developers.com/showthread.php?t=1853871 you already s-on'd so you might have to s-off again. not sure about that part though
cslingerland said:
i've never heard of a returned phone being rejected for any reason other than physical damage. and if you are super worried about it there is a link to hex edited hboots.http://forum.xda-developers.com/showthread.php?t=1853871 you already s-on'd so you might have to s-off again. not sure about that part though
Click to expand...
Click to collapse
I haven't either so i think i may just send it out! chances are they wont see or care
ryclegman said:
I haven't either so i think i may just send it out! chances are they wont see or care
Click to expand...
Click to collapse
I think you might have to s-off. Downgrade to GB or a lower ICS RUU. Lock it. s-on. then do the ICS RUU. Should be back to locked and s-off.
^^
Flyhalf205 said:
I think you might have to s-off. Downgrade to GB or a lower ICS RUU. Lock it. s-on. then do the ICS RUU. Should be back to locked and s-off.
Click to expand...
Click to collapse
Won't his hboot still show relocked after that...
Sent from my ADR6425LVW using xda app-developers app
cslingerland said:
Won't his hboot still show relocked after that...
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Other poster is correct. Have to run s-off. Rerun RUU to unroot and then write s-on flag. Will remove all tags and be box stock.
prdog1 said:
Other poster is correct. Have to run s-off. Rerun RUU to unroot and then write s-on flag. Will remove all tags and be box stock.
Click to expand...
Click to collapse
Thats sweet. I didn't think that was possible which is why we have the hboots that are edited.good to know though!
Sent from my ADR6425LVW using xda app-developers app
prdog1 said:
Other poster is correct. Have to run s-off. Rerun RUU to unroot and then write s-on flag. Will remove all tags and be box stock.
Click to expand...
Click to collapse
But won't the hboot technically say relocked once you relock it after running the RUU?
[email protected] said:
But won't the hboot technically say relocked once you relock it after running the RUU?
Click to expand...
Click to collapse
Not of after you S-OFF. When you do, the bootloader locks automatically, and says LOCKED not RELOCKED.
Sent from my ADR6425LVW using Tapatalk 2
shrike1978 said:
Not of after you S-OFF. When you do, the bootloader locks automatically, and says LOCKED not RELOCKED.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
So I am already s-off. Can I run the latest ICS RUU, then s-on? Will that send me back to a totally looking stock phone?
Why not just flash one of the missed hboots that says locked and s-on when you're actually s-off? I had mine unlocked and s-off and then made it s-on and sent it back in to Verizon and they sent me another one, no questions asked. Don't worry about it.
Sent from my Nexus 7 using Tapatalk 2
Look, even my hex edited hboots wont fool a tech. They can still tell.
HTC tech, yea that is if they even care to look. Verizon Tech? I doubt they even know what S-Off means or what HBOOT even is lol.
Sent from my Nexus 7 using Tapatalk 2
Just follow instructions:
http://forum.xda-developers.com/showthread.php?t=
Sent from my ADR6425LVW using xda app-developers app
Phaded said:
Just follow instructions:
http://forum.xda-developers.com/showthread.php?t=
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Invalid link.
Try this
http://forum.xda-developers.com/showthread.php?p=25167284#post25167284
Sent from my ADR6425LVW using xda app-developers app
Might help to think of HTC Dev Unlock and JuopunutBear S-Off as the two "gatekeepers", the two tools in the Rezound's current arsenal that affect the security flag. The security flag starts off as "locked" on a stock phone.
HTC Dev Unlock will alter the security flag to show "unlocked", and running the code to lock it back will now show it as "relocked".
JuopunutBear S-Off will reset the security flag back to "locked" no matter what the flag reads, and alter the "S-On" flag to "S-Off".
So to get back to a stock "S-On/Locked" from any of these states:
"S-On/Unlocked or Relocked"
If you are S-On and have used HTC Dev Unlock, you will need to do S-Off to get the "Locked" message back. Run a RUU, then do S-On procedure.
"S-Off/Locked"
If you are S-Off but have *not* used HTC Dev Unlock after the S-Off procedure, you should just need to run a RUU and do S-on.
"S-Off/Unlocked or Relocked"
If you are S-Off and have used HTC Dev Unlock since the S-Off procedure, you must run a RUU, re-lock the bootloader if you have not done so before, and do S-On. Then, do the S-off procedure (keep the stock bootloader, do not flash a modded one) and do S-on again.
PhantasmRezound said:
Might help to think of HTC Dev Unlock and JuopunutBear S-Off as the two "gatekeepers", the two tools in the Rezound's current arsenal that affect the security flag. The security flag starts off as "locked" on a stock phone.
HTC Dev Unlock will alter the security flag to show "unlocked", and running the code to lock it back will now show it as "relocked".
JuopunutBear S-Off will reset the security flag back to "locked" no matter what the flag reads, and alter the "S-On" flag to "S-Off".
So to get back to a stock "S-On/Locked" from any of these states:
"S-On/Unlocked or Relocked"
If you are S-On and have used HTC Dev Unlock, you will need to do S-Off to get the "Locked" message back. Run a RUU, then do S-On procedure.
"S-Off/Locked"
If you are S-Off but have *not* used HTC Dev Unlock after the S-Off procedure, you should just need to run a RUU and do S-on.
"S-Off/Unlocked or Relocked"
If you are S-Off and have used HTC Dev Unlock since the S-Off procedure, you must run a RUU, re-lock the bootloader if you have not done so before, and do S-On. Then, do the S-off procedure (keep the stock bootloader, do not flash a modded one) and do S-on again.
Click to expand...
Click to collapse
So I was s-off and unlocked. I just flashed the latest ICS RUU. Now you are saying I need to lock my bootloader and then s-on? Then s-off with the wire trick again, then s-on one more time? Will this all work with the latest RUU I have installed?
It sounds too complicated to get rid of the "RELOCKED" sign...
WARNING!!!
DO NOT attempt this process unless you are on a STOCK, HTC HBOOT.
S-ON with an ENG HBOOT will BRICK your device!!!
In other words, Only attempt this AFTER flashing back to a STOCK RUU. (as this will flash the STOCK HBOOT.)
I know the process JUST came out, but I'm sure this will eventually come in to use.
Instructions:
1) Download and run an RUU. Found HERE
2) Open a cmd window. Plug in phone, charge only mode, usb debugging on.
3) Run the following:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Disclaimer:
I am not responsible for anything harmful that happens to your phone. Use at your OWN risk. Thank you.
http://forum.xda-developers.com/showthread.php?p=35437335
reserved.
reserved. 2.
Do these steps clear the "relocked" flag?
Sent from my ADR6410LVW using Tapatalk 2
mdmower said:
Do these steps clear the "relocked" flag?
Sent from my ADR6410LVW using Tapatalk 2
Click to expand...
Click to collapse
Whatever it said when it was S-ON is my understanding. but since I haven't yet tested this for our phone I can't say 100%
From the looks of your post, I guess you sourced the information from http://forum.xda-developers.com/showthread.php?t=1612937, which I also had bookmarked for my future reference. From that thread, here's how I understand it:
If we S-OFF then unlock, we can expect RELOCKED after S-ON.
If we S-OFF but keep bootloader locked, we can expect LOCKED after S-ON.
It doesn't look like we can expect a custom tag to stick around after S-ON.
Source post (different phone, so may not be the same for us)
scotty1223 said:
correct. only way to get locked back,is to turn s-on,then re unlock and re-s-off. and then,do not unlock after s-off. your hboot will stay locked and you can s-on again,if you need to. just keep in mind that turning s-on should only be done for warranty purposes.
Click to expand...
Click to collapse
mdmower said:
From the looks of your post, I guess you sourced the information from http://forum.xda-developers.com/showthread.php?t=1612937, which I also had bookmarked for my future reference. From that thread, here's how I understand it:
If we S-OFF then unlock, we can expect RELOCKED after S-ON.
If we S-OFF but keep bootloader locked, we can expect LOCKED after S-ON.
It doesn't look like we can expect a custom tag to stick around after S-ON.
Source post (different phone, so may not be the same for us)
Click to expand...
Click to collapse
Yes Sir, indeed.
Andy real quick question flashing ruu well eliminate soff correct
No, hence post 1. I'm guessing this relates to your MIUI adventure. You can have S-OFF and LOCKED bootloader.
Sent from my ADR6410LVW using Tapatalk 2
no this command, and this command only is what I know to get to S-ON
fastboot oem writesecureflag 3
andybones said:
WARNING!!!
DO NOT attempt this process unless you are on a STOCK, HTC HBOOT.
S-ON with an ENG HBOOT will BRICK your device!!!
In other words, Only attempt this AFTER flashing back to a STOCK RUU. (as this will flash the STOCK HBOOT.)
I know the process JUST came out, but I'm sure this will eventually come in to use.
Instructions:
1) Download and run an RUU. Found HERE
2) Open a cmd window. Plug in phone, charge only mode, usb debugging on.
3) Run the following:
adb devices
adb reboot bootloader
fastboot devices
fastboot oem writesecureflag 3
fastboot reboot-bootloader
*verify you are locked s-on
fastboot reboot
Disclaimer:
I am not responsible for anything harmful that happens to your phone. Use at your OWN risk. Thank you.
Click to expand...
Click to collapse
your link to ruu's doesn't point to RUU's for the HTC Evo 4G LTE. Here is the correct link http://shipped-roms.com/index.php?category=android&model=Jewel
IXVash said:
your link to ruu's doesn't point to RUU's for the HTC Evo 4G LTE. Here is the correct link http://shipped-roms.com/index.php?category=android&model=Jewel
Click to expand...
Click to collapse
Erm, wrong forum IXVash?
andybones said:
WARNING!!!
DO NOT attempt this process unless you are on a STOCK, HTC HBOOT.
S-ON with an ENG HBOOT will BRICK your device!!!
Click to expand...
Click to collapse
andybones refers to this, but to clarify, the DirtyRacun hboot is an engineering hboot. If going s-on, make sure to run the RUU first.
Sent from my Fireball using Xparent Blue Tapatalk 2
IXVash said:
your link to ruu's doesn't point to RUU's for the HTC Evo 4G LTE. Here is the correct link http://shipped-roms.com/index.php?category=android&model=Jewel
Click to expand...
Click to collapse
that's because this is the HTC DROID INCREDIBLE 4G LTE FORUM... NOT THE EVO 4G LTE.
I know my RUU's point to the correct thread... because I made it!
Do I need to flash the dirty racun hboot from their page? Is having the dirt racun hboot important? Mine says 1.15.000 I have since gaining s-off have had to flash our ruu.
*Edit* I went ahead flashed it now I'm back to where I was after the s-off tool right where I needed to be
sent from my all powerful INC4G
mdmower said:
Erm, wrong forum IXVash?
Click to expand...
Click to collapse
well crap. Sorry It was a long night /facepalm
prairiedogn said:
Do I need to flash the dirty racun hboot from their page? Is having the dirt racun hboot important? Mine says 1.15.000 I have since gaining s-off have had to flash our ruu.
*Edit* I went ahead flashed it now I'm back to where I was after the s-off tool right where I needed to be
sent from my all powerful INC4G
Click to expand...
Click to collapse
The ENG HBOOT has different options. Glad you got it back.
sent from my DINC4 using Tapatalk 2
Hi,
I need stock "Locked" bootloader.
I've RUU the DirtyRacun Phone by advice as an attempt to fix (SIM failed) and now the Phone is S-OFF with stock Hboot "RELOCKED". Had to unlock the device again for last fix attempts.
Will flashing with S-OFF with stock signed Hboot clear bootloader security flags changing "RELOCKED" back to "LOCKED"?
Now RUU doesn't deliver "Locked" bootloader status. Should I next Flash signed stock Hboot first? Or should I Flash a DR Hboot then RUU again?
Last I would do your posted above for S-ON from Fastboot down since OS locks (no ADB).
Don't want to brick my phone.
Thanks In Advance!
mpeg3s said:
Hi,
I need stock "Locked" bootloader.
I've RUU the DirtyRacun Phone by advice as an attempt to fix (SIM failed) and now the Phone is S-OFF with stock Hboot "RELOCKED". Had to unlock the device again for last fix attempts.
Will flashing with S-OFF with stock signed Hboot clear bootloader security flags changing "RELOCKED" back to "LOCKED"?
Now RUU doesn't deliver "Locked" bootloader status. Should I next Flash signed stock Hboot first? Or should I Flash a DR Hboot then RUU again?
Last I would do your posted above for S-ON from Fastboot down since OS locks (no ADB).
Don't want to brick my phone.
Thanks In Advance!
Click to expand...
Click to collapse
To get back to truly LOCKED, check this post:
http://forum.xda-developers.com/showthread.php?p=35437335
Sent from my Kindle Fire using Xparent Blue Tapatalk 2
junkmail9 said:
To get back to truly LOCKED, check this post:
http://forum.xda-developers.com/showthread.php?p=35437335
Sent from my Kindle Fire using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
nice find man, I made this based off of his post anyway, so his thread would be the place to go, I'll add it to the OP.
Ok here is the skinny on the situation:
I began with an unlocked bootloader & S-OFF using the wire trick & 4ext
After loading the borked CM9 yesterday, to recover I used the RUU for T-Mobile
Originally Posted by dcmtnbkr
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"
Now my bootloader displays:
***LOCKED***
RUBY PVT SHIP S-OFF RL
HBOOT-1.93.0002
eMMC-boot
Mar 15 2012.21:46:51
When attempting to flash a recovery with latest Hasoon 5.1 toolkit
or
using the recovery.zip from dcacklam
I'm presented with:
C:\ADB\fastboot flash recovery c:\adb\recovery.zip
seding 'recovery' <6320 KB>... OKAY [ 1.513s]
writing 'recovery' ... FAILED <remote: not allowed>
Finished. total time: 1.839s
So I attempted to unlock via HTCdev bootloader procedures and I'm presented with an the following error:
Unlocking Bootloader Failed!
Sorry it didn't work out. Here's why:
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: 173.
Error Reason: Check Rule Fail with exception.
After attempting at least 5 times (I had read HTCdev has given a similar error as a false answer) the other error was that the token id was to long
I've searched for over 2 hours after a 12 hour day & a 3 hour drive this evening. Anyone with advice I would welcome it.
Do I attempt to S-OFF the phone again?
Keeping trying the HTCdev site (its incredibly slow with IE 9 & Chrome)?
Thanks again.
My bootloader sayes *unlocked* and S-ON wel it cares only aboved the S-*** i think.
Sent from my HTC EVO 3D X515m using xda app-developers app
Do you need to be unlocked if you use jbear hboot?
I mean don't you just need a eng hboot or jbear hboot,to flash recovery?
Sent from my HTC Ruby using xda app-developers app
You don't need to unlock your bootloader. You need either JB HBOOT or ENG HBOOT. Flash either HBOOT and then flash the recovery.
So wouldn't it be less of a headache to just flash jbear hboot then try to re-unlock bootloader if it just errors repeatedly.
Sent from my HTC Ruby using xda app-developers app
gideo said:
So wouldn't it be less of a headache to just flash jbear hboot then try to re-unlock bootloader if it just errors repeatedly.
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
Just need another HBOOT. He has s-off. That's the point. You don't need to unlock the bootloader since s-off is an unlocked bootloader.
Sent From My HTC Amaze 4G via Someone's Room
hasoon2000 said:
Just need another HBOOT. He has s-off. That's the point. You don't need to unlock the bootloader since s-off is an unlocked bootloader.
Sent From My HTC Amaze 4G via Someone's Room
Click to expand...
Click to collapse
I think you and I said the same thing.
Sent from my HTC Ruby using xda app-developers app
gideo said:
I think you and I said the same thing.
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
You said he may need to reunlock the boot loader. I'm saying he doesn't need to, unless I misunderstood what you wrote.
gideo said:
Do you need to be unlocked if you use jbear hboot?
I mean don't you just need a eng hboot or jbear hboot,to flash recovery?
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
No,I dident
I was just trying to help without being totally certain if I was totally correct...thankfully you having more knowledge than me could confirm it.
Sent from my HTC Ruby using xda app-developers app
gideo said:
No,I dident
I was just trying to help without being totally certain if I was totally correct...thankfully you having more knowledge than me could confirm it.
Sent from my HTC Ruby using xda app-developers app
Click to expand...
Click to collapse
No worries. We are here to help as well
Thanks for the suggestions I will try the HBOOT in a few minutes and report back.
Sent from my HTC_Amaze_4G using xda app-developers app
Thanks everyone.
I flashed the HBOOT from
http://forum.xda-developers.com/showthread.php?t=1611977
Then my recovery of choice and have a unlocked & S-OFF phone again
I ruu'd this morning and install all the otas (as well as newest)
I tried to unlock the bootloader with "fastboot.exe oem unlock" but just gets an error but on the bootloader it says "relocked"
I might just be incorrect about being able to unlock or i might not
bootloader info
hboot 1.54.0000
cid vzw_001
also says MONARUDI PVT SHIP S-OFF RH
Thanks
Did you attempt to load a custom recovery? You should be able to do this s-off via hboot fastboot commands. Then flash the unlock zip via custom recovery.
Sent from my DNA using my mind.
Uzephi said:
Did you attempt to load a custom recovery? You should be able to do this s-off via hboot fastboot commands. Then flash the unlock zip via custom recovery.
Sent from my DNA using my mind.
Click to expand...
Click to collapse
Nope only tried Unlocking
You have to have the original unlock bin file or use the unlock flashable zip.
http://forum.xda-developers.com/showthread.php?p=38325198
Sent from my DNA using my mind.
I don't know the command off the top of my head but set your CID to 22222222 then unlock via htcdev.com.
Sent from my HTC6435LVW using xda app-developers app