reset your "lock status" flag - HTC Rezound

i happened across this thread inthe gsm evo 3d forum: http://forum.xda-developers.com/showthread.php?t=1970252 and found it to work on the rezound.
this does NOT mean you can unlock your bootloader without going thru htcdev. all this means,is that if you accidentally unlocked your bootloader after s-off,you can get rid of the relocked watermark and get back to 100% locked prior to s-on for warranty purposes,without having to s-on and re-s off.
ive always been unlocked. for S&Gs,i dumped mmcblk0p3 and found the described "HTCU" at 0x8404. changed it to 0x00000000 and voila! back to locked
afterward,relfashed my origianl mmcblk0p3,wich brought me back to unlocked with no getting or flashing tokens.
this is NOT a patched or hex edited hboot.again,this is ONLY to get back your original ***locked*** status.
2 ways to do it:
1)old school
this assumes you to have drivers,adb/fastboot,a hex editor,a fair understanding about what youre doing,and the ability to follow directions on the linked thread
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Scott>[COLOR="Red"]cd c:\mini-adb_vigor[/COLOR]
c:\mini-adb_vigor>[COLOR="red"]adb devices[/COLOR]
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
HTxxxxxxxxxx device
c:\mini-adb_vigor>[COLOR="Red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3[/COLOR]
dd if=/dev/block/mmcblk0p3 of=/sdcard2/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 9.519 secs (3481858 bytes/sec)
[email protected]:/ # [COLOR="red"]exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb pull /sdcard2/mmcblk0p3[/COLOR]
2292 KB/s (33143808 bytes in 14.116s)
[COLOR="Blue"]*modify mmcblk0p3 with a hex editor[/COLOR]
c:\mini-adb_vigor>[COLOR="Red"]adb push mmcblk0p3mod /sdcard2/mmcblk0p3mod[/COLOR]
2478 KB/s (33143808 bytes in 13.059s)
c:\mini-adb_vigor>[COLOR="red"]adb shell[/COLOR]
[email protected]:/ $ [COLOR="red"]su[/COLOR]
su
[email protected]:/ # [COLOR="red"]dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3[/COLOR]
dd if=/sdcard2/mmcblk0p3mod of=/dev/block/mmcblk0p3
64734+0 records in
64734+0 records out
33143808 bytes transferred in 18.937 secs (1750214 bytes/sec)
[email protected]:/ #[COLOR="red"] exit[/COLOR]
exit
[email protected]:/ $ [COLOR="red"]exit[/COLOR]
exit
c:\mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR]
c:\mini-adb_vigor>
2)noob friendly
-download the appropriate zips,place on sd card.
-boot to recoverywipe cache/dalvik
-flash in recovery. i recomend to run query first,to make sure its working. tested on my personal rezound.
query:http://www.mediafire.com/download.php?jg8v4ady8nyc8bu
query_bootloader.zip f335f78f9f46469c823da0c671026de5
unlock:http://www.mediafire.com/download.php?il51rl2j1m8417b
unlock_bootloader.zip f335f78f9f46469c823da0c671026de5
lock:http://www.mediafire.com/download.php?05ow9uhw540p6jy
lock_bootloader.zip f335f78f9f46469c823da0c671026de5
a little bit of explanation. yes,the md5s are all the same. its the same file,just named differently. the script behaves based on the name of the zip. i knew if i only included 1 download and instructed folks to change the name there would be confusion,so this is my attempt to keep it simple. feel free to download one file and just change the name to make the other zips.
it also works to make your phone relocked if for some reason you want it that way(rename relock_bootloader.zip). i didnt include a zip for that because i figued there would be no demand.
before:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after:
sure,i could have easily faked the above photos,but i dint.
again,all credit goes to s trace on the above thread. all i did was remove the device check per his instruction. DO NOT flash on other devices without checking for the proper location of the lock flag first.
DISCLAIMER:this is not my work. i have tested it on my own device,but use it at your own risk. if it melts your phone into a lil pile of goo,its not my fault.
enjoy

---

If your S-off and run the global RUU , your Hboot will say "locked" and not "relock". That's what mine says anyway.

---

mclass55 said:
If your S-off and run the global RUU , your Hboot will say "locked" and not "relock". That's what mine says anyway.
Click to expand...
Click to collapse
you were locked in the first place. running ruus does not change the lock status flag. ive run it several times as unlocked(along with may other ruus)

---

Nice find my friend
Sent from my ADR6425LVW using xda app-developers app

---

There are several modified (hexedited) HBoots in these forums that you can flash and they can say basically whatever you want them to say. I'm S-Off but mine says S-On Locked, IIRC. Have not been in recovery in a while to look.
Here: http://forum.xda-developers.com/showthread.php?t=1853871

---

ClockerXP said:
There are several modified (hexedited) HBoots in these forums that you can flash and they can say basically whatever you want them to say. I'm S-Off but mine says S-On Locked, IIRC. Have not been in recovery in a while to look.
Here: http://forum.xda-developers.com/showthread.php?t=1853871
Click to expand...
Click to collapse
Yea, but this is for the people who dont want to change the bootloader and want to keep it stock, but want it locked aswell.

---

Nice find, imma run it thanks!
Sent from my ADR6425LVW using xda app-developers app

---

ClockerXP said:
There are several modified (hexedited) HBoots in these forums that you can flash and they can say basically whatever you want them to say. I'm S-Off but mine says S-On Locked, IIRC. Have not been in recovery in a while to look.
Here: http://forum.xda-developers.com/showthread.php?t=1853871
Click to expand...
Click to collapse
using a patched hboot is IMO,a fraudulent way to sent your phone in for warranty. it may make it back out into circulation in this manner,and casue issues for the next users.
patched hboot is fine for a trip to the vzw store if youre paranoid about a vzw empooyee checking your hboot,but its so easy now to to return the phone to 100% out of the box stock i have no idea why anyone would not do it.

---

I am s-on and back to factory.. But RELOCKED status.. Can I rename the lock zip and flash in bootloader?
Sent from my ADR6425LVW using xda app-developers app

---

dudebro0325 said:
I am s-on and back to factory.. But RELOCKED status.. Can I rename the lock zip and flash in bootloader?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Unfortunately,no. Mmcblk0p3 is write protected while s on. At this point ,you will need to re-s off(which will also reset the lock flag)
Even if you were s off,this can ONLY be flashed via recovery. Its not something hboot can install.
Sent from my ADR6425LVW using xda app-developers app

---

scotty1223 said:
you were locked in the first place. running ruus does not change the lock status flag. ive run it several times as unlocked(along with may other ruus)
Click to expand...
Click to collapse
I have unlocked, relocked and run the Global RUU many times and it returns me back to "Locked" also I am S-off and couldn't get that by being locked to start with

---

mclass55 said:
Take a look at my picture.It says the same thing as yours. I have unlocked, relocked and run the Global RUU many times and it returns me back to "Locked" also I am S-off and couldn't get that by being locked to start with
Click to expand...
Click to collapse
The s off jpbear tool reset your lock flag. Go ahead and unlock,Relock,and run your ruu again.
Running ruus will NOT changed your relocked to locked
Sent from my ADR6425LVW using xda app-developers app

---

scotty1223 said:
The s off jpbear tool reset your lock flag. Go ahead and unlock,Relock,and run your ruu again.
Running ruus will NOT changed your relocked to locked
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
Maybe I am missing something about your post. What's the difference between my Hboot screen and yours? If the jpbear tool resets lock flag, why do we need the fix that was posted? And the only way to get S-off is by using jpbear to start with.
Sorry, not trying to start anything, but I am not seeing the need for this
scotty1223 said:
Unfortunately,no. Mmcblk0p3 is write protected while s on. At this point ,you will need to re-s off(which will also reset the lock flag)
Even if you were s off,this can ONLY be flashed via recovery. Its not something hboot can install.
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse

---

mclass55 said:
Maybe I am missing something about your post. What's the difference between my Hboot screen and yours? If the jpbear tool resets lock flag, why do we need the fix that was posted? And the only way to get S-off is by using jpbear to start with.
Sorry, not trying to start anything, but I am not seeing the need for this
Click to expand...
Click to collapse
Because some people have unlocked their bootloader after s-off without realizing there was no need.

---

mclass55 said:
Maybe I am missing something about your post. What's the difference between my Hboot screen and yours? If the jpbear tool resets lock flag, why do we need the fix that was posted? And the only way to get S-off is by using jpbear to start with.
Sorry, not trying to start anything, but I am not seeing the need for this
Click to expand...
Click to collapse
This tool is for people who have already S-OFF'd and then subsequently unlocked (like me). In the event that I want to sell my Rezound, this makes it easy: I run an RUU, flash this zip, and fastboot oem write secureflag 3 to return to S-ON. Conversely, without this tool, after flashing the RUU I'd have to S-ON, run JuopunutBear S-OFF again (which is just a hassle to have to do more than once, with the paperclip and all), then re-S-ON.
It just makes things a little simpler, and I'm grateful for it. Nice find, scotty.

---

El Schisne said:
without this tool, after flashing the RUU I'd have to S-ON, run JuopunutBear S-OFF again (which is just a hassle to have to do more than once, with the paperclip and all), then re-S-ON.
Click to expand...
Click to collapse
After S-off and flashing the Global RUU, I have never ever, S-on or rerun the S-off jpbear again , And my Hboot looks the same as the original poster's Hboot

---

mclass55 said:
After S-off and flashing the Global RUU, I have never ever, S-on or rerun the S-off jpbear again , And my Hboot looks the same as the original poster's Hboot
Click to expand...
Click to collapse
Not sure how to say this any simpler than this: If you run HTCDev unlock after you are S-OFF, you will get the relocked status if you relock your bootloader. If you don't unlock with HTCDev unlock, you won't. This is for people who have HTCDev unlocked after S-OFF

---

mclass55 said:
After S-off and flashing the Global RUU, I have never ever, S-on or rerun the S-off jpbear again , And my Hboot looks the same as the original poster's Hboot
Click to expand...
Click to collapse
Because jpbeat reset your lock flag for you,and you have not re-unlocked.
Sent from my ADR6425LVW using xda app-developers app

---

What about the TAMPERED flag?

---

MajikUF said:
What about the TAMPERED flag?
Click to expand...
Click to collapse
Once you're s off you won't see the tampered banner. Even if you're s on,it will go away naturally when you relock and run a signed ruu
Sent from my HTC Flyer P510e using xda app-developers app