change relocked to locked - 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.
again,this is ONLY to get back your original ***locked*** status.
in a few days ill try and make a "noob friendly" guide to using the hex editor,unless someone else wants to,or wants to make or modify(with proper credit) the script to flash in recovery. dont mess with this unless youre sure what youre doing,as messing up mmcblk0p3 may leave you in a "do not boot" mode that you may or may not be able to recover from.
enjoy
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>
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:
downloads added. wipe cache/dalvik and 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

---

apophis9283 has some custom hex edited hboots that will change what your phone says made and available for use:
http://forum.xda-developers.com/showthread.php?t=1853871

---

feralicious said:
apophis9283 has some custom hex edited hboots that will change what your phone says made and available for use:
http://forum.xda-developers.com/showthread.php?t=1853871
Click to expand...
Click to collapse
Hex edited hboots are NOT factory signed,and are by no means an acceptable way to "return to stock". These hboots can cause issue for future users,and their use to trick vzw into thinking the phone is stock is,IMO fraud.
The above info resets the lock status flag,enabling users to restore the device to 100% as it came from factory.
Sent from my HTC Flyer P510e using xda app-developers app

---

scotty1223 said:
Hex edited hboots are NOT factory signed,and are by no means an acceptable way to "return to stock". These hboots can cause issue for future users,and their use to trick vzw into thinking the phone is stock is,IMO fraud.
The above info resets the lock status flag,enabling users to restore the device to 100% as it came from factory.
Sent from my HTC Flyer P510e using xda app-developers app
Click to expand...
Click to collapse
So this can be flashed s-on? Or you could use this to s-on? When I say flashed I mean can it replace the hboot in an ruu and be flashed?
Sent from my ADR6425LVW using xda app-developers app

---

jon7701 said:
So this can be flashed s-on? Or you could use this to s-on? When I say flashed I mean can it replace the hboot in an ruu and be flashed?
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You are misunderstanding what this is. It's not a replacement hboot.
The "lock status flag" lives in memory block 0p3,along with the radio secure flag. It tells the hboot weather it is locked,unlocked,or relocked,just like the radio secure flag tells the hboot wether it is s on or s off. Hboot itself is in a different location.
The original 3d dev made a zip that could be flashed from recovery,hopefully someone could modify it to work with the rezound(maybe its directly compatible,since the mmcblk location is the same,I don't know)
You definately need to be s off to modify this partition,otherwise it is write protected,wich is why it took so long for us to get radio s off.
I believe the radio secure flag lives at 0x8400 in mmcblk0p3,so technically,you could change to s on with a hex edit if all your ducks were in a row,but this is not something id recommend.
if you were unlocked,s-off and your speaker quit working,necesitating return to legitimate factory stock,locked,s on,the process would be this:
-change lock flag status flag(hex edit or potential recovery flash)
-verify s off and ***locked***
-run most current ruu
-turn s-on with fastboot comment fastboot oem write secureflag 3
hopw that clears it up some
Sent from my HTC Flyer P510e using xda app-developers app

---

Oh OK so its basically just modifying the status of your existing boot loader back to locked?
Sent from my ADR6425LVW using xda app-developers app

---

BTT. recovery flashable zips added to OP. tested on my rezound

---

That's pretty frickin sweet

---

I think my issue is answered in this thread.. but I am confused.
I got an ICS rezound on ebay; no idea on the history..
I htcdev unlocked, and updated to get the 2.22 radios and now have hboot 2.27 and it says **RELOCKED** at the top.
when flashing the ruu it wiped the recovery and I am looking to get AmonRa back on there and move on to s-off'ing the device now that the radio's are 'current'..
how do I get my **RELOCKED** to **UNLOCKED** so that I can flash recovery?
fastboot flash recovery Ra3.15PH98IMG.img
sending 'recovery' (7078 KB)...
OKAY [ 1.421s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.107s
so.. to flash the 'stock RUU' and get the radios I had to 'fastboot oem lock' to get the RUU to stick..
Do I need to re htcdev unlock again?
Or is there a fastboot command that I am missing?
(I hope this makes sense..)
Thanks for taking the time to read this..

---

If you're currently s on,you will have to re-unlock the "old fasioned" way. The zips only work when you're s off.
Sent from my HTC One X using Tapatalk 2