[how to] lock/unlock your bootloader without htcdev(s-off required)

pacificnw · Dec 1, 2014

ian.anindya said:
The easiest way is you install sunshine soof apk. Run it until get temporary root and then exit. Your device with get temp root. After that you can use scotty code to get unlock bootloader via adb. Try that.

Great idea! I was able to get temp root and send the scotty code via adb to unlock bootloader. Thank you, very much appreciated!

mlin · Dec 2, 2014

Thanks, confirmed working on VZW!

treIII · Dec 2, 2014

So my son's phone is s off and the boot loader is unlocked. Will this work without root? He cracked his screen and he is accepted for the HTC advantage program. Thanks
His phone is completely stock other than using sunshine to unlock boot loader and get soff. After that he had never done a thing to alter anything

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2

pacificnw · Dec 3, 2014

treIII said:
So my son's phone is s off and the boot loader is unlocked. Will this work without root? He cracked his screen and he is accepted for the HTC advantage program. Thanks
His phone is completely stock other than using sunshine to unlock boot loader and get soff. After that he had never done a thing to alter anything

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2

I don't think you'll be able to without root, one of the requirements listed on the initial post is to have superuser installed, which is synonymous with having root in this case.

If all that has been done is getting the bootloader unlocked and achieving s-off, all you may need to do is send the command "fastboot oem lock" through command prompt in fastboot to lock the bootloader again. From what I've read time and time again on these forums, HTC doesn't really seem to mind if the phone is S-Off when it's sent in for repairs.

Hopefully someone else can confirm this, and I would also recommend personally searching online to double-check if "fastboot oem lock" will do the job.

Antagonist42 · Dec 3, 2014

treIII said:
So my son's phone is s off and the boot loader is unlocked. Will this work without root? He cracked his screen and he is accepted for the HTC advantage program. Thanks
His phone is completely stock other than using sunshine to unlock boot loader and get soff. After that he had never done a thing to alter anything

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2

You need to be rooted (SU installed) to run the command :-

su (if needed to get a # prompt)

echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)

Sent from my B1-730HD using XDA Free mobile app

ian.anindya · Dec 3, 2014

treIII said:
So my son's phone is s off and the boot loader is unlocked. Will this work without root? He cracked his screen and he is accepted for the HTC advantage program. Thanks
His phone is completely stock other than using sunshine to unlock boot loader and get soff. After that he had never done a thing to alter anything

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2

Use sunshine as explain previous thread to get temporary root. Just need temporary root to get # on adb.
Then you can apply scotty code to get Lock / Unlock Bootloader as what you need.

treIII · Dec 3, 2014

ian.anindya said:
Use sunshine as explain previous thread to get temporary root. Just need temporary root to get # on adb.
Then you can apply scotty code to get Lock / Unlock Bootloader as what you need.

I already locked the Bootloader and turned the phone s-on. But the h boot still says software status modified. So they will not be doing any repairs. His phone was completely stock other than using sunshine. I didn't even think about the software status modified in the h boot. I made a mistake. Sunshine will not gain temporary root either now.

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2

ian.anindya · Dec 3, 2014

If you are looking to clean tempered flag and red text, you should flash modified Hboot. Go to santod40 thread. Find at xda Santod40 name.

russellvone · Dec 3, 2014

ian.anindya said:
If you are looking to clean tempered flag and red text, you should flash modified Hboot. Go to santod40 thread. Find at xda Santod40 name.

he's already back S-ON....can't

ian.anindya · Dec 3, 2014

Yeah.... Right. Why you go S-On?
Soff not void your warranty right?

treIII · Dec 3, 2014

I ran the ruu while s on. That removed the software status modified. It was clear in the disclosure that the phone MUST be the way it is intended or no warranty work. There's another thread and a gentleman said his boot loader was locked but phone was s off and they sent it back to him with no work done. So to get the screen replaced I had to make it stock. That's why s on. But HTC made it very clear on the phone before making the advantage ticket. Only thing I wish I'd have done before turning the phone son is running an ruu to and older software then I'd be able to achieve s off again. It's my son's phone he said he'd rather have his screen replaced and be s on.

Sent from my HTC One_M8 using Xparent Blue Tapatalk 2

Jena-HtcOneM8 · Dec 7, 2014

scotty1223 said:
this thread will let you unlock your bootloader without htcdev,or let you change your hboot watermark from relocked or locked back to stock.

originally,we used a zip file flashable in recovery. i have found it to work on gsm devices with 1.44 hboot and CW recovery. it did not work with twrp. if the following is too scary,feel free to test the zip files. that thread,info,and downloads can be found here. since not all recoverys are working,these values can be changed with simple adb commands.

advantages
-no hassle with htcdev,tokens,or unlock codes
-no submitting your phones personal info to htc
-the ability to get back to 100% stock without any visual traces or records of having been s off or unlocking your bootloader.

you do NOT need to downgrade your hboot. this simple adb command works without any scary hboot downgrades.

*you must be s off.
*you must have superuser installed

read this:
this will not work if your s on. its not a way to magically unlock

the usual disclaimers:
use this info at your own risk. if it melts your phone into a little pile of aluminum goo,its not my fault.

credits
-beaups for schooling me on echo comand protocol
-strace for originally discovering the location of the lock status flag(check out this thread for more info)
-kdj67f for fearlessly testing on vzw m7_wlv and putting up some screenshots in post 2. thanks!
-matthew0776 for fearlessly testing for sprint m7_wls
*i dont have m8. let me know if it works and ill add you to the credits.

IF you are an advanced user with adb/fastboot set up and some basic knowlede of the cmd window,you can skip to #2
1)set up adb(windows 7 and older)

-download this file
-install drivers: if you have htc sync installed,you should allready have drivers. if not,you can install htc sync,or install these modified htc drivers from revolutionary (driver mirror)
-unzip your miniadb_v1031.zip file. this is native funtionality in windows 7. you otherwise may need a utility such as "7-zip" to extract,or unzip it. place the unzipped folder onto the root of your C drive on your PC. root means the top level,not inside any folders. so just copy and paste,or drag and drop the folder onto C with everything else that is there. you may want to rename it to "miniadb_m7" since youll be putting some device specific files in here.
-open a command window. on windows 7,click the start bubble in the lower left and type "command" in the search box. xp i believe is similar or the same. doing this should open a small black command window.
-change to your miniadb_m7 directory. type the following at the prompt in your cmd window:

cd c:\miniadb_m7

your command promt should change to "c:miniadb_m7>" provided you: 1)unzipped the miniadb_v1031 zip file,and 2)put the folder on your c drive,and 3)entered the name of the folder correctly ("miniadb_m7" in this case)

-now make sure usb debugging is checked in developer options(you will need to turn it on first),and plug your phone into your PC with a usb cable
-make sure your phone is being recognized- type:

adb devices

if your drivers are installed correctly,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.

if you get your serial number back,then enter this command:
adb reboot bootloader

this should take your phone to the "fastboot" screen,wich is white with colored letters. this is one mode of your bootloaders interactive modes. at the top youll see fastboot devices as confirmation youre in fastboot.

now enter:
fastboot devices
again,this should return your phones serial number. you should hear the "found device" noises when you plug your phone in. if it starts installing drivers,wait for it to finish before typing the adb devices command.

if you get your serial number back,you can enter the following to boot back to the phones OS:
fastboot reboot

and now,youve installed adb/fastboot and tested youre phones drivers. if at either spot,you have trouble and dont get your serial number back,there is some sort of connection issue. use these steps to troubleshoot:

this process,in your cmd window,should look something like this:

Code:

Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\Scott>[COLOR="red"]cd c:\miniadb_m7[/COLOR] c:\miniadb_m7>adb devices * daemon not running. starting it now on port 5037 * * daemon started successfully * List of devices attached FAxxxxxxxxxx device c:\miniadb_m7>[COLOR="red"]adb reboot bootloader[/COLOR] c:\miniadb_m7>[COLOR="red"]fastboot devices[/COLOR] FAxxxxxxxxxx fastboot c:\miniadb_m7>[COLOR="red"]fastboot reboot[/COLOR] rebooting... finished. total time: 0.037s c:\miniadb_m7>

2)reset your "lock status flag"

to LOCK your bootloader,enter the following:

adb devices

adb shell

su (if needed to get a # prompt)

echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)

exit
(exit a second time if you need to to get back to a normal > prompt)

adb reboot bootloader

verify you are now locked
_____________________________________________________________________________________________

to UNLOCK your bootloader,enter the following:

adb devices

adb shell

su (if needed to get a # prompt)

echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
(i would very strongly recomend you copy/paste this)

exit
(exit a second time if you need to to get back to a normal > prompt)

adb reboot bootloader

verify you are now unlocked

*i have tested this on my gsm htc one. if someone wants to test on vzw,ill add you to the credits

(yes this is m7. i dont have an m8 yet)

other useful threads:
remove tampered banner: http://xdaforums.com/showthread.php?t=2708565
change mid without an eng bootloader: http://xdaforums.com/showthread.php?t=2708581

Hi @scotty1223 I got permission denied error in step 2 while locking.

shell@htc_m8:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
d of=/dev/block/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied

Please can you help?

Captain_Throwback · Dec 7, 2014

Jena-HtcOneM8 said:
Hi @scotty1223 I got permission denied error in step 2 while locking.

shell@htc_m8:/ $ echo -ne '\x00\x00\x00\x00' | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
d of=/dev/block/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied

Please can you help?

You don't have root. Did you "su" first?

Jena-HtcOneM8 · Dec 7, 2014

Captain_Throwback said:
You don't have root. Did you "su" first?

Yes but that didn't work. It didn't bother me as this step was optional.

shell@htc_m8:/ $ su
su
/system/bin/sh: su: not found

In the pre-requisite it said s-off which I have (screen attached). Sorry I'm a newbie.

Thanks

scotty1223 · Dec 8, 2014

Jena-HtcOneM8 said:
Yes but that didn't work. It didn't bother me as this step was optional.

shell@htc_m8:/ $ su
su
/system/bin/sh: su: not found

In the pre-requisite it said s-off which I have (screen attached). Sorry I'm a newbie.

Thanks

The su step was not optional. As stated in the parenthesis,you need to enter su if the initial adb shell command does not get you a # prompt.

You've also ignored the second pre-requisite,wich was: *you must have superuser installed

You do not really need your boot loader to be unlocked. You can install a recovery as a zip file from fastboot/ruu mode,or from hboot/sd card.

You can then install superuser,or your Rom of choice.

Once you're properly rooted,you can use these commands to lock/unlock your boot loader

Sent from my HTC0P3P7 using Tapatalk

djhixson88 · Dec 13, 2014

FIrst off sorry for my stupidity lol I converted my AT&T M8 to a Google Play Edition. S-Offed with Sunshine. Not caring for Lollipop right now, so I went back to Sense by flashing the 1.54 firmware and splash image. Which wiped the Google Play RUU due the system partitions changing. So I couldn't boot up. I flashed the latest TWRP recovery, but once in recovery it said I had 0MB, therefore I couldn't flash any ROMs. Or sideload. I read somewhere that the only way I could get the partitions to actually change was by running an RUU. So I figured by doing this I could just redo the bootloader unlock process and root, flash custom ROMs, etc. I never had any issues with my M7 by doing this, so I figured it would apply here. Obviously I was wrong. I locked the bootloader then ran the RUU. Worked fine, but when I went to unlock the bootloader it said FAILED (remote: unlock token check failed) I only wanted to go back to Sense because I wanted to try ARHD again. Anyway, I downloaded the Sunshine apk after I had locked the bootloader and ran the RUU and ran it to try getting temp root. All it does is tell me my device is already S-Off and reboots my phone. I'm aware you can flash a recovery when the bootloader is locked so I can root it the proper way. But I'm not sure how to flash a recovery other than through fastboot. I keep getting FAILED (remote: not allowed). So I'm stuck. The phone's still usable, the CID is CWS__001 (only way the RUU would run) but still S-Off. Again, sorry for my stupidity, any help would be appreciated. Most definitely will not be locking my bootloader again.

scotty1223 · Dec 13, 2014

djhixson88 said:
FIrst off sorry for my stupidity lol I converted my AT&T M8 to a Google Play Edition. S-Offed with Sunshine. Not caring for Lollipop right now, so I went back to Sense by flashing the 1.54 firmware and splash image. Which wiped the Google Play RUU due the system partitions changing. So I couldn't boot up. I flashed the latest TWRP recovery, but once in recovery it said I had 0MB, therefore I couldn't flash any ROMs. Or sideload. I read somewhere that the only way I could get the partitions to actually change was by running an RUU. So I figured by doing this I could just redo the bootloader unlock process and root, flash custom ROMs, etc. I never had any issues with my M7 by doing this, so I figured it would apply here. Obviously I was wrong. I locked the bootloader then ran the RUU. Worked fine, but when I went to unlock the bootloader it said FAILED (remote: unlock token check failed) I only wanted to go back to Sense because I wanted to try ARHD again. Anyway, I downloaded the Sunshine apk after I had locked the bootloader and ran the RUU and ran it to try getting temp root. All it does is tell me my device is already S-Off and reboots my phone. I'm aware you can flash a recovery when the bootloader is locked so I can root it the proper way. But I'm not sure how to flash a recovery other than through fastboot. I keep getting FAILED (remote: not allowed). So I'm stuck. The phone's still usable, the CID is CWS__001 (only way the RUU would run) but still S-Off. Again, sorry for my stupidity, any help would be appreciated. Most definitely will not be locking my bootloader again.

3 things come to mind:
1)change cid back to whatever so that your token works
2)get a new token
3)zip your recovery image up with an android info text document and install it via hboot/sd card or fastboot/ruu mode.

djhixson88 · Dec 13, 2014

scotty1223 said:
3 things come to mind:
1)change cid back to whatever so that your token works
2)get a new token
3)zip your recovery image up with an android info text document and install it via hboot/sd card or fastboot/ruu mode.

We're good, I did the first two steps and bootloader is now unlocked. It crossed my mind to try a new token before, don't know why I didn't. Oh well thank you very much! Should be all good now

ugrifja · Dec 16, 2014

Is this thread and files still ok for a vzw htc one m8 running 4.4.4? I am s-off currently and running the gpe rom on it.

Thanks!

cesar.peru · Jan 1, 2015

Lock bootloader with s-on?

Hi, I have my HTC One M8 Unlocked and S-ON. I try to s-off my phone with Firewater but it didn't work. Is there another way to s-off it, or any way to lock the bootloader again with s-on?
Thanks!!

[how to] lock/unlock your bootloader without htcdev(s-off required)

Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Recognized Developer

Member

Attachments

Inactive Recognized Contributor

Senior Member

Inactive Recognized Contributor

Senior Member

ugrifja

Guest

New member

Attachments

Similar threads

Top Liked Posts