[how to]reset your lock status flag - HTC Amaze 4G

with the rezound,some folks unknowingly re-unlocked after s off to regain use of fastbooot commands,after running ruus that replaced the patched jpbear hboot. i thot i would bring this here,in case there ever becomes a need.
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,inc 4g,sensation 4g,cdma evo 3d,MT4GS,Amaze 4g,and prolly several others.
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.
*this is for s-off phones only
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 amaze,jetstream,rezound,inc 4g,sensation,MT4GS,and gsm evo 3d.
query:query_bootloader.zip
query_bootloader.zip f335f78f9f46469c823da0c671026de5
unlock:unlock_bootloader.zip
unlock_bootloader.zip f335f78f9f46469c823da0c671026de5
lock:lock_bootloader.zip
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,be sure to click the thanks button on his post. 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
special thanks
-brian for unlocking his bootloader,then dumping mmcblock0p3 to make sure it would work for cdma evo3d phones too
-brian and donb for fearless testing of the zip files on evo3d cdma

---

Thank you. This looks really useful for the future possibly.

---

SnapplerX said:
Thank you. This looks really useful for the future possibly.
Click to expand...
Click to collapse
your welcome. its not my work,so make sure to thank s trace on the original thread in the gsm 3d forum. i know alot of folks will find it useful

---

Not sure if i missed somthing but if i never did S-off and im currently s-on will this still work?

---

dntipwn said:
Not sure if i missed somthing but if i never did S-off and im currently s-on will this still work?
Click to expand...
Click to collapse
no,it will not. mmcblk0p3 is write protected while s on(or s off would have come alot sooner )
if youre s on,and want to get rid of relocked im afraid youll need to s off.

---

There's a easier way to do it. I was thinking of making a tutorial howto thread but was lazy. All you have to do is be s-off with juopunutbear's hboot. Then go on bootloader and connect through USB. Ensure fastboot usb is there then run adb and run command "fastboot oem lock". It should say that the bootloader is already locked. Then run adb command "fastboot oem writesecureflag 3" (this command will turn your phone back to s-on in case you didn't know), install stock ruu and your phone should be s-on with ***locked*** status. If your somebody looking to return your phone for warranty reasons or for whatever desire you want, or just want lock status as everyone wants to know how to do, then this'll work reverting you back to stock completely. You'll look like you've never tampered your phone

---

After I S-Off'd I flashed an RUU and achieved **Locked** status.
I didn't have to unlock my bootloader after that. Just flashed a recovery using fastboot and flashed a ROM.

---

nulcon said:
There's a easier way to do it. I was thinking of making a tutorial howto thread but was lazy. All you have to do is be s-off with juopunutbear's hboot. Then go on bootloader and connect through USB. Ensure fastboot usb is there then run adb and run command "fastboot oem lock". It should say that the bootloader is already locked. Then run adb command "fastboot oem writesecureflag 3" (this command will turn your phone back to s-on in case you didn't know), install stock ruu and your phone should be s-on with ***locked*** status. If your somebody looking to return your phone for warranty reasons or for whatever desire you want, or just want lock status as everyone wants to know how to do, then this'll work reverting you back to stock completely. You'll look like you've never tampered your phone
Click to expand...
Click to collapse
you have completely missed the point. what you said is true of one has never left a jpbear hboot,or re-unlocked.
however...
if one has re-unlocked after s-off,then they cannot get back to locked with fastboot oem lock,they will be relocked just like before s-off.
in addition,this gives you the freedom to use an unlocked hboot rather than a jpbear hboot if youve run an ruu that overwrote it. you can easily lock and unlock simply by flashing the zip.
Double0EK said:
After I S-Off'd I flashed an RUU and achieved **Locked** status.
I didn't have to unlock my bootloader after that. Just flashed a recovery using fastboot and flashed a ROM.
Click to expand...
Click to collapse
part of the jpbear s off process is doing exactly what the zips are doing- resetting the lock flag status back to 00000000 at 0x8400. alot of folks dont realize this becasue they continue to use the jpbear hboot. this is why running an ruu that overwrites the jpbear hboot gives you a stock locked hboot.
you are correct,you dont need to unlock(or reinstall jpbear) in order to install a recovery. however alot of noobs did not realize this,and unknowingly unlocked in order to fastboot flash a recovery. until now,the best these folks could do wasrelocked,unless they were willing to turn s on,then run jpbear again. simply flahsing a zip in recovery is a lil easier

---

big thanks man, but do you only have to download the first file?

---

amazeboy said:
big thanks man, but do you only have to download the first file?
Click to expand...
Click to collapse
yes. all 3 are the same. just change the name to create the other files,the script behaves based on the name of the zip. again,i recomend to run query first,then lock or unlock.
you can change the zip to achieve relocked but i dint htink there would be demand for that