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

[anit77]

Got it. Thanks guys. Was hope to avoid HTCdev... At$t M8

 

[ffforce]

Any way to turn it back to s-on?

Sent from my HTC One_M8 using Tapatalk

 

[scotty1223]

Any way to turn it back to s-on?

Sent from my HTC One_M8 using Tapatalk

Yes,but don't. Even for warranty.

Sent from my HTC PG09410 using Tapatalk 2

 

[ffforce]

Yes,but don't. Even for warranty.

Sent from my HTC PG09410 using Tapatalk 2

Could you explain why?

Sent from my HTC One_M8 using Tapatalk

 

[scotty1223]

Could you explain why?

Sent from my HTC One_M8 using Tapatalk

It's unnecessary,and potentially just causes more prollems,especially for vzw users who can't htcdev unlock.

Phones did legitimately come s off,so finding it does not indicate you have messed with it.

All that's needed for warranty work,or just to be stock and get ota updates,is to restore stock cid/mid,reset lock status to locked,and run a stock release keys ruu(or restore a stock unrooted rom and stock recovery in the event no ruu available and other firmware has not been altered)

I a lot of folks turn s on and screw it up. From being locked into bootloader with a security warning,to tampered banner reappearing,to hard bricks. My advice is dont do it.

Sent from my HTC PG09410 using Tapatalk 2

 

[ffforce]

It's unnecessary,and potentially just causes more prollems,especially for vzw users who can't htcdev unlock.

Phones did legitimately come s off,so finding it does not indicate you have messed with it.

All that's needed for warranty work,or just to be stock and get ota updates,is to restore stock cid/mid,reset lock status to locked,and run a stock release keys ruu(or restore a stock unrooted rom and stock recovery in the event no ruu available and other firmware has not been altered)

I a lot of folks turn s on and screw it up. From being locked into bootloader with a security warning,to tampered banner reappearing,to hard bricks. My advice is dont do it.

Sent from my HTC PG09410 using Tapatalk 2

I see. I thought s-off would screw up warranty. Thanks for the information!

Sent from my HTC One_M8 using Tapatalk

 

[kman79]

Awesome work

Can I use this to lock/unlock an HTCDev unlocked M8?

 

[scotty1223]

Awesome work

Can I use this to lock/unlock an HTCDev unlocked M8?

As long as it is s off

Sent from my HTC One VX using Tapatalk

 

[Darkseth]

So, this definitely works on the M8?
Did anyone tried yet to "relock" the bootloader after unlocking it from htcdev in order to get the 50GB Drive space?

 

[Captain_Throwback]

So, this definitely works on the M8?
Did anyone tried yet to "relock" the bootloader after unlocking it from htcdev in order to get the 50GB Drive space?

Yes, I got the Drive space once I relocked.

 

[Darkseth]

Yes, I got the Drive space once I relocked.

Thank you for confirming!
i just did it, and it worked perfectly.
But, setting the bootloader back on locked will not give you back the drive. You also have to remove tampered flag. After i did this, i now also got it Now i am 100% pleased with my device

Edit: It says up to 65gb...
But i still have the +10 gb bonus from Quickoffice. Will i now get only 40gb up to a max of 65gb, or will i land at 75gb? You also got experience with that?

 

[rustykwak]

Thank you for confirming!
i just did it, and it worked perfectly.
But, setting the bootloader back on locked will not give you back the drive. You also have to remove tampered flag. After i did this, i now also got it Now i am 100% pleased with my device

Edit: It says up to 65gb...
But i still have the +10 gb bonus from Quickoffice. Will i now get only 40gb up to a max of 65gb, or will i land at 75gb? You also got experience with that?

Yes my drive has jumped to 75gb

 

[Jump1ng]

Also want to confirm that locking it and having the tampered flag removed made me able to claim my G-Drive offer, so for any one that forgot to claim before unlocking the your phone with HTC Dev just get it locked as per the guide claim your offer and then you can unlock again.

Big thanks @scotty1223

 

[itzjonjon69]

guys i need your help i relocked my phone last night after trying to flash the new firmware and now i can't unlock it for some reason. I've tried getting a new token and i've also tried this method but it keeps saying this:

1|[email protected]_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|[email protected]_m8:/ $
C:\Users\haswell\Desktop\platform-tools>

I've come to realize that my recovery is no longer working as well as super SU... Can someone please help me?

 

[c5satellite2]

guys i need your help i relocked my phone last night after trying to flash the new firmware and now i can't unlock it for some reason. I've tried getting a new token and i've also tried this method but it keeps saying this:

1|[email protected]_m8:/ $ echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
lock/mmcblk0p2 bs=1 seek=33796 <
/dev/block/mmcblk0p2: cannot open for write: Permission denied
1|[email protected]_m8:/ $
C:\Users\haswell\Desktop\platform-tools>

I've come to realize that my recovery is no longer working as well as super SU... Can someone please help me?

You did not follow the directions. You needed a su # prompt. I don't know how to recover from this other than try again and follow the instructions.

Sent from my HTC One_M8 using xda app-developers app

 

[itzjonjon69]

fixed!!! forum member russellvone just SAVED my ass. So what he did was he had me download this file for my ATT M8

https://mega.co.nz/#!NUURzC5T!tCjG3n6Ztx2bCvBfAodRsiZ88h1O0c6zRAwOPZ8T2PI and told me to rename it 0P6BIMG.zip and place it in my adb fastboot folder

then he told me to run these commands:

fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 0P6BIMG.zip
fastboot reboot

then once everything was done we ran the commands from this thread and voila! i'm once again unlocked! He explained to me that when i tried to run the commands it didn't work because i had the secure boot.img and what he had me flash was a file he created which made it unsecure so i could run the command. HUGE HUGE props to this guy.

 

[redmanjoey]

As long as it is s off

Sent from my HTC One VX using Tapatalk

Hey scotty, when I try to flash the stock recovery per your instructions I get a remote: failed error. I double checked USB debugging on, set it to disk drive only, even fastbootusb shows but still no luck. any ideas?

I forgot this happened to me last time too. This time I tried on another computer and still nothing. Also tried both files and got the same error.

 

[scotty1223]

Hey scotty, when I try to flash the stock recovery per your instructions I get a remote: failed error. I double checked USB debugging on, set it to disk drive only, even fastbootusb shows but still no luck. any ideas?

I forgot this happened to me last time too. This time I tried on another computer and still nothing. Also tried both files and got the same error.

what instructions are you refering to?

in order to use fastboot flash recovery imagename.img you will need to be unlocked

if you wish to remain locked,youll need to use a properly packed zip file(recovery image and an android-info text document) and flash in the following manner:

if youre working with a booted,operational phone,you can flsh the file in the following manner:

-open a cmd window

-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )

-place the zip file you want to flash into adb/fastboot directory

-enable usb debug,disable fastboot,plug in phone

-check for connectivity
adb devices (should return serial number)

-boot to fastboot
adb reboot bootloader

-check for connectivity again
fastboot devices

-flash the file
fastboot erase cache

fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)

fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)

*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish

-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)

-reboot back to the OS
fastbooot reboot

you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices

 

[redmanjoey]

what instructions are you refering to?

in order to use fastboot flash recovery imagename.img you will need to be unlocked

if you wish to remain locked,youll need to use a properly packed zip file(recovery image and an android-info text document) and flash in the following manner:

if youre working with a booted,operational phone,you can flsh the file in the following manner:

-open a cmd window

-change to adb/fastboot directory
cd c:\foldername
(cd c:\mini-adb if youve used any of my guides )

-place the zip file you want to flash into adb/fastboot directory

-enable usb debug,disable fastboot,plug in phone

-check for connectivity
adb devices (should return serial number)

-boot to fastboot
adb reboot bootloader

-check for connectivity again
fastboot devices

-flash the file
fastboot erase cache

fastboto oem rebootRUU (will put you in ruu mode,black screen silver htc letters)

fastboot flash zip zipfilename.zip (will send and flash the file. dont interupt it while the cmd window shows its writinging,and the green status bar is moving on the phone screen)

*sometimes a file will fail with a pre-update error. this is normal,just enter again:
fastboot flash zip zipfilename.zip
and this time it will finish

-when you get "finished" and "OK"
fastboot reboot-bootloader (takes you back to fastboot)

-reboot back to the OS
fastbooot reboot

you can use this if you dont have an operational phone as well. you just need to manually put the phone in fastboot(select from hboot menu) then skip the "adb" commands and start with fastboot devices

My phone is unlocked and soff, its also operational. I just followed the instructions you just gave me, this is what happens. The instructions I am referring to were the ones that were inclided in the recovery folder.


C:\Users\Joey\Desktop\Root M8>adb devices
List of devices attached
XXXXXXXXXXXXX device


C:\Users\Joey\Desktop\Root M8>adb reboot bootloader

C:\Users\Joey\Desktop\Root M8>fastboot devices
XXXXXXXXXXXXX fastboot

C:\Users\Joey\Desktop\Root M8>fastboot erase cache (I get this error trying to do anything in fastboot)
erasing 'cache'...
FAILED (remote: not allowed)
finished. total time: 0.001s

 

[suicidal acorn]

The OP States that you can get back to 100% stock with this, but, and correct me if I'm wrong, you can't get rid of the red dev text and the "s-off" in the bootloader, correct? I know you can put a custom hboot on to get rid of that stuff, but when a ruu comes out, that will just flash the stock hboot back and the red text will be back, along with the "s-off" text if it is run. I guess I'm just asking if this is good enough to fool sprint employees when getting warranty work done.

Sent from my 831C using Tapatalk