testers needed- reset your lock status flag
- Thread starter scotty1223
- Start date
-
- Tags
- development
Yes, I got same, just upload it somewhere and paste the link.
Here it is
Code:
00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00---------- Post added at 02:38 PM ---------- Previous post was at 02:38 PM ----------
That's what we need, thank you so much for helping.
---------- Post added at 02:41 PM ---------- Previous post was at 02:38 PM ----------
Flashing modified mmcblk0p3 now, will report back.
Looking forward to a brand new "looking" shiny, non tampered, hboot look lol. Hope this helps out with that issue 
Sent from my HTC6435LVW using xda premium
Sent from my HTC6435LVW using xda premium
SUCCESS!!
Modified address 0x8400 to read
I hex edited the dump, flashed it with dd through adb shell, and rebooted into bootloader which showed ***LOCKED*** at the top.
Scotty, please add a thanks to treadwayj in the OP for uploading the stock mmcblk0p3 when you update it.
Modified address 0x8400 to read
Code:
00 00 00 00 00 00 00 00 01 00 00 00 00 00 00 00I hex edited the dump, flashed it with dd through adb shell, and rebooted into bootloader which showed ***LOCKED*** at the top.
Scotty, please add a thanks to treadwayj in the OP for uploading the stock mmcblk0p3 when you update it.
Last edited:
Use ENG HBOOT and this tool to change the flag (just displays ON):
http://xdaforums.com/showthread.php?t=1786498
It also lets you changed ***Unlocked*** line to whatever you want and get rid of the HTC development disclaimer from your splash screen.
http://xdaforums.com/showthread.php?t=1786498
It also lets you changed ***Unlocked*** line to whatever you want and get rid of the HTC development disclaimer from your splash screen.
Last edited:
Thanks guys,don't flash the zips just yet since the 01 is still present in the locked phone. More later
Sent from my ADR6425LVW using Tapatalk 2
Sent from my ADR6425LVW using Tapatalk 2
That is not the same as what were doing here. This fixes things correctly,not superficially(wich is IMO fraudulent)
Sent from my ADR6425LVW using Tapatalk 2
It will actually be locked and isn't just a patched hboot, meaning it can be returned for warranty.
Here's a copy of my mmcblk0p3 I flashed after hex editing.
https://www.dropbox.com/s/73rce2sgtlb6ne1/mmcblk0p3.zip
https://www.dropbox.com/s/73rce2sgtlb6ne1/mmcblk0p3.zip
Lets say I flash this and Lock my bootloader... is it stuck like that or can I use my Unlock_code.bin to re-unlock it?
This can only be done if you are s-off, in which case the bootloader will be locked, but you will still be s-off, meaning you can flash roms etc. If necessary, you can revert it and have both s-off and an unlocked bootloader. If you lock the bootloader with this and then change it back to s-on, it will be completely locked and you can then return it for warranty. But if you need to do it now, don't flash the files because they aren't correct right now; you will have to manually copy your mmcblk0p3 partition, hex edit it with the modified data from my post on page 3, and reflash it with the commands the OP.
---------- Post added at 04:49 PM ---------- Previous post was at 04:46 PM ----------
Using the lock command will change it from ***UNLOCKED*** to ***RELOCKED***, so htc/vzw will still know that you unlocked the bootloader and possibly try to void your warranty. Using this, you can change it to ***LOCKED***, and it will appear to be the same as it was when you bought it.
Last edited:
you can unlock it. you can use your unlock code,you can flash your "unlocked" mcblk0p3,or if the zip files work,you can unlock or lock it at will with them. i personally keep my stock hboot unlocked so i can use fastboot flash and fastboot boot(tho as mentioned,you can easily install radios and recoveries while s on and locked)
OK,if some brave soul wants to test the zip files,go ahead. Run the query zip first,then the locked zip(assuming your unlocked or relocked) if queery installs with no errors and provides the correct response.
Please take a before and after bootloader pic.
Zips should be safe,but again I can't guarantee it and take no responsibility for anything bad that happens as a direct or indirect result.
Sent from my ADR6425LVW using xda app-developers app
Please take a before and after bootloader pic.
Zips should be safe,but again I can't guarantee it and take no responsibility for anything bad that happens as a direct or indirect result.
Sent from my ADR6425LVW using xda app-developers app
Did you hear back from s-trace? I'll try it out when I get home in an hour or so.
Sent from my HTC6435LVW using xda-developers app
Sent from my HTC6435LVW using xda-developers app
Yup. He seemed to think they would be safe
Sent from my ADR6425LVW using xda app-developers app
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
5since the current s-off method is not resetting your lock status flag, i figured there would be a demand for this. it all started from this thread in the gsm evo 3d section: http://xdaforums.com/showthread.php?t=1970252
*this is not a modified or hex edited hboot. this is resetting your lock flag,so that your phone will correctly display locked on the hboot screen
ive verified the lock location on just about every s3 phone jpbear supports,as well as a couple s4 dual core devices- LTEvo,inc 4g LTE,and one S.
ive had a friend dump his DNA mmcblk0p3 and the lock flag location is the same,with an extra character that ive not seen prior. he cannot test the mods,as he is dependent on his phone for work,and cant be without it.
0x8400 on his dna looked like this:
Code:03 00 00 00 48 54 43 55 01 00 00 00 00 00 00 00....HTCU........
the "01" after 48 54 43 55 i have never seen on any other device.
now that we have s off,we an explore this further. first test would be to dump mmcblk0p3, hex edit it,changing 0x8400 to 00000000,and reflash it. id like someone fairly savy to do this,as i cant gaurantee it wont melt your shiny dna into a smoldering pile of goo
dump,edit and reflash in this manner:
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] shell@android:/ $ [COLOR="red"]su[/COLOR] su shell@android:/ # [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) shell@android:/ # [COLOR="red"]exit[/COLOR] exit shell@android:/ $ [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] shell@android:/ $ [COLOR="red"]su[/COLOR] su shell@android:/ # [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) shell@android:/ #[COLOR="red"] exit[/COLOR] exit shell@android:/ $ [COLOR="red"]exit[/COLOR] exit c:\mini-adb_vigor>[COLOR="red"]adb reboot bootloader[/COLOR] c:\mini-adb_vigor>
if this is successful,some less experienced users are welcome to try flashing this zip files. see the following thread for zip file links and instructions: http://xdaforums.com/showthread.php?t=2155955
again,this has not been tested on a quad core s4 phone. i cannot gaurantee the hex edit zips wil work,fail,or brick your phone.
i just wanted to get this info to the comunity so we can figure it out3
This can only be done if you are s-off, in which case the bootloader will be locked, but you will still be s-off, meaning you can flash roms etc. If necessary, you can revert it and have both s-off and an unlocked bootloader. If you lock the bootloader with this and then change it back to s-on, it will be completely locked and you can then return it for warranty. But if you need to do it now, don't flash the files because they aren't correct right now; you will have to manually copy your mmcblk0p3 partition, hex edit it with the modified data from my post on page 3, and reflash it with the commands the OP.
---------- Post added at 04:49 PM ---------- Previous post was at 04:46 PM ----------
Using the lock command will change it from ***UNLOCKED*** to ***RELOCKED***, so htc/vzw will still know that you unlocked the bootloader and possibly try to void your warranty. Using this, you can change it to ***LOCKED***, and it will appear to be the same as it was when you bought it.2
