Help relocking bootloader

[needhelp4]

I can't relock my bootloader no matter what I do, I always get this message:

command: fastboot oem lock begin
(bootloader) Check 'Allow OEM Unlock' in Android Settings > Developer
(bootloader) Options
OKAY [ 0.004s]
Finished. Total time: 0.006s

Why is this happening? I'm not trying to unlock it, it's already unlocked. I was able to relock it once before today but now I can't. I've tried wiping everything on twrp and installing different firmware but still get the same message. Before this I used to get a message saying "Please fully flash the signed build before locking phone" when I tried locking.

 

[ninjakira]

Why are you trying to relock it? Unlocking a bootloader does not cause performance issues or anything wrong and there is simply no point in relocking it. If your wanting to relock it before sending it in to Motorola don't even bother. They will know if it's been unlocked and relocking it doesn't magical get your warranty back. If selling it simply tell the person that the performance of the phone is not affected at all.

 

[Spaceminer]

Why are you trying to relock it? Unlocking a bootloader does not cause performance issues or anything wrong and there is simply no point in relocking it. If your wanting to relock it before sending it in to Motorola don't even bother. They will know if it's been unlocked and relocking it doesn't magical get your warranty back. If selling it simply tell the person that the performance of the phone is not affected at all.

I really don't understand why this comes up so much. The answer is almost always the same too, warranty, sale, or return. None of which are good reasons to lock it.

This is a bit off topic but I'm going to share it anyways because I think it's hilarious. I once rooted and installed twrp on my neighbors phone to debloat it. Now, he's not tech savvy in the least bit. A few days later, he accidentally boots into twrp while turning his phone on. I wasn't home so he couldn't ask me what to do. In his anger and frustration, he dunked it right in the toilet. It still worked after that so he went to Best Buy to return it. The geek squad in all their wisdom... thought that twrp was special software designed to break into government servers. They call the police. The police show up and don't know what it is, or what to do with it. After 2.5hrs of head scratching and a nice chat with the FBI, he finally got his phone replaced. (The FBI knew exactly what it was.) If anyone had bothered to read what twrp's menus say, they would've understood what it was for in like 1-2min.

Tales from the tech department...

 

[ninjakira]

Right like I guess I understand the logic behind the thought process though so I don't mind it to much lol. and that was the best story about geek squad I've ever heard ??? leave up to them to think it's for hacking stuff lmfao this would go great ona Reddit geek squad encounters post

 

[jrebmontana]

go to "developer options" and check again "oem unlock" and try again

 

[needhelp4]

Why are you trying to relock it? Unlocking a bootloader does not cause performance issues or anything wrong and there is simply no point in relocking it. If your wanting to relock it before sending it in to Motorola don't even bother. They will know if it's been unlocked and relocking it doesn't magical get your warranty back. If selling it simply tell the person that the performance of the phone is not affected at all.

Takes longer to boot and reboot. Stays stuck on bad key for a little while before it actually boots.

 

[needhelp4]

go to "developer options" and check again "oem unlock" and try again

I can't, it's grayed out.

 

[needhelp4]

I really don't understand why this comes up so much. The answer is almost always the same too, warranty, sale, or return. None of which are good reasons to lock it.

This is a bit off topic but I'm going to share it anyways because I think it's hilarious. I once rooted and installed twrp on my neighbors phone to debloat it. Now, he's not tech savvy in the least bit. A few days later, he accidentally boots into twrp while turning his phone on. I wasn't home so he couldn't ask me what to do. In his anger and frustration, he dunked it right in the toilet. It still worked after that so he went to Best Buy to return it. The geek squad in all their wisdom... thought that twrp was special software designed to break into government servers. They call the police. The police show up and don't know what it is, or what to do with it. After 2.5hrs of head scratching and a nice chat with the FBI, he finally got his phone replaced. (The FBI knew exactly what it was.) If anyone had bothered to read what twrp's menus say, they would've understood what it was for in like 1-2min.

Tales from the tech department...

Takes longer to boot.

 

[Spaceminer]

Takes longer to boot.

That's not true. An unlocked device actually boots up slightly faster. The reason why is; when you unlock the bootloader it skips verifying the boot.img signature. Meaning there's actually less work for the cpu to do before startup. The difference is extremely minimal though and probably not noticable without timing it in milliseconds.

 

[needhelp4]

That's not true. An unlocked device actually boots up slightly faster. The reason why is; when you unlock the bootloader it skips verifying the boot.img signature. Meaning there's actually less work for the cpu to do before startup. The difference is extremely minimal though and probably not noticable without timing it in milliseconds.

You can see why in my reply to ninjakira. The screen displays 'bad key' on boot and only after a while restarts and actually boots.

 

[Spaceminer]

You can see why in my reply to ninjakira. The screen displays 'bad key' on boot and only after a while restarts and actually boots.

It's actually not restarting. That's the bootloader handing off control to the boot.img. The bad key screen, is actually the boot logo screen. The bootloader is just designed to show that instead of the logo if you're unlocked. The boot animation has it's own splash screen that perfectly matches the one in the boot logo. So when you're still locked and the hand-off occurs, it looks seamless. When you're unlocked it goes from black to the Moto logo, so you end up seeing the transition. The current brightness setting also kicks in at the boot animation, which makes it look even worse when unlocked. You can fix that by flashing one of my boot logos from here.