Hi Forum,
i flashed LineageOS on my OP5 and I want to lock the bootloader.
I do this with "fastboot oem lock" or "fastboot flashing lock". After agree on the Phone, the Phone reboots and says that it is unsecure and will not boot any more.
How can i fix that?
Thanks
Rokasporch said:
Hi Forum,
i flashed LineageOS on my OP5 and I want to lock the bootloader.
I do this with "fastboot oem lock" or "fastboot flashing lock". After agree on the Phone, the Phone reboots and says that it is unsecure and will not boot any more.
How can i fix that?
Thanks
Click to expand...
Click to collapse
Found my fault.
I tried to lock the bootloader with recovery image from twrp.
This is not working but with the LineageOS recovery image, the lock was possible.
Related
Hi friends,zenfone 3 bootloder opened the lock.Now I want to close .Relock bootloader.
Ive tried asking this before for my Ze520kl, someone said it isn't possible to relock the bootloader
I would like to know if someone has an update about that...
When I tried to root my phone (ZE552KL Androïd 7.0) I installed an app to unlock the bootloader of my phone (ZE552KL_SIGNED_Android_M_UnlockTool_2016_0715). I used it and ever since, when I turn on my device, I get a warning screen saying "Your device software cannot be checked for corruption. Please lock the bootloader." It sends me to this link for information. The notification disappear after 10 seconds and androïd starts.
I was quite stupid to do that because I do not have to knowledge to properly root my device. So I give up, but I would like to get back my device without that security warning.
I have already flashed it from the recovery menu, with an sd card, wiping data and cache. But it didn't work.
Any advice?
my69 said:
Hi friends,zenfone 3 bootloder opened the lock.Now I want to close .Relock bootloader.
Click to expand...
Click to collapse
I found this on the bootloader source:
Code:
fastboot oem unlock
fastboot oem unlock-go
fastboot oem lock
fastboot flashing unlock
fastboot flashing lock
fastboot flashing lock_critical
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
but they're all untested, trying them would make you take the risk of
killing your phone
OR
locking the bootloader
keep in mind that Asus also keeps track of system mounts as read write changes, so if you're trying to fool them, locking the bootloader won't be enough
Commands do not work.
gkillershots said:
I found this on the bootloader source:
Code:
fastboot oem unlock
fastboot oem unlock-go
fastboot oem lock
fastboot flashing unlock
fastboot flashing lock
fastboot flashing lock_critical
fastboot flashing unlock_critical
fastboot flashing get_unlock_ability
but they're all untested, trying them would make you take the risk of
killing your phone
OR
locking the bootloader
keep in mind that Asus also keeps track of system mounts as read write changes, so if you're trying to fool them, locking the bootloader won't be enough
Click to expand...
Click to collapse
Commands do not work.
myheartloves said:
Commands do not work.
Click to expand...
Click to collapse
well, I think Asus disabled thoose ones
sorry
what i messed up?
i have installed custom official cynogen14.1 rom and twrp recovery. everything was working fine.
but i messed up with bootloader. I have locked oem from fastboot mode without enabling option for oem unlocking in developer settings.
Now as my phone have custom rom and twrp installed it went into bootloop and only shows zuk logo and again restart.
What i diid till now?
i have opened backcover so that i can turn of bootloop and phone by disconecting battery.
I can enter into fastboot mode by pressing vol.+ and vol- buttons sumultaneously and connecting usb cable.
But i cannot unlock bootloader as it says unlocking bootloader not allowed. I have tried device specific commads like "fastboot -i 0x2b4c oem unlock" and "fastboot -i 0x2b4c oem unlock-go" but nothing works.
i have stock recovery image but cannot flash while bootloader is locked.
i can enter into adb sideload by following method:
by loading stock recovery by typing "fastboot boot recovery.img" (this does not work with twrp as it says signature varification failed)
and then selecting apply update >> selecting apply fron adb
this much i can do does anyone knows how to recover from such a state.
please help me or my phone will be a waste.
is there any way to install stock recovery i think phone will boot properly if i managed to install stock recovery.
Hi,
I've tried all the following steps in the video and I got the error "flashing lock is not allowed". I've already flashed stock rom and recovery and wiped the phone so it's as stock as it gets yet I still get the same error when I enter "fastboot oem lock". Please help ASAP!!!! I'm trying to update to Android 8.0 but the update keeps failing because my bootloader is unlocked
Thanks in advanced.
https://forum.xda-developers.com/oneplus-5/how-to/lock-oneplus-5-bootloader-guide-t3651819
Go to developer settings.. check the oem unlock option. If it's off, bootloader won't relock. You need to turn it on. If it's greyed out & can't be turned on, then you need to root your firmware or flash custom rom & turn it on.
When you have this problem, only magisk will help you turn on allow bootloader unlocked when it's grayed out.
So, you have to flash magisk, turn on allow bootloader to be unlocked in devlopper settings, then flash a clean OOS, make sure there's no modification like custom recovery or root, then relock your bootloader.
Good luck!
use command "fastboot flashing lock" instead of "fastboot oem lock", this will lock your bootloader
hope this tutorial will help you....!!! https://www.youtube.com/watch?v=CQYCSdDUdAU
I had the same problem and solved using magistik, reenable unlock volta loader and After relock.
question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
[IMG="https://drive.google.com/open?id=1cAIFNdksNV9-yUEQQBzwz7S1uDxgNhGp"]
[email protected] said:
question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
[IMG="https://drive.google.com/open?id=1cAIFNdksNV9-yUEQQBzwz7S1uDxgNhGp"]
Click to expand...
Click to collapse
Can you boot to recovery and factory reset?
ktmom said:
Can you boot to recovery and factory reset?
Click to expand...
Click to collapse
no,the phone can't do this
[email protected] said:
no,the phone can't do this
Click to expand...
Click to collapse
Have you tried unlocking again in fastboot?
ktmom said:
Have you tried unlocking again in fastboot?
Click to expand...
Click to collapse
Yes,but it failed. remote is Flashing Unlock is not allowed .
[email protected] said:
Yes,but it failed. remote is Flashing Unlock is not allowed .
Click to expand...
Click to collapse
It sounds like the OEM unlock was turned off in developer settings.
If you can't get to recovery and you can't boot to be able to unlock again, you're stuck [emoji17]
This is a warning to others. Don't lock bootloader. You can leave phone unrooted, no TWRP, and bootloader unlocked. It has the annoying warning splash screen with every reboot, but a lot safer than locking bootloader
HueyT said:
This is a warning to others. Don't lock bootloader. You can leave phone unrooted, no TWRP, and bootloader unlocked. It has the annoying warning splash screen with every reboot, but a lot safer than locking bootloader
Click to expand...
Click to collapse
Exactly. This has been highlighted many times - relocking the BL after unlocking it once is a bad idea...
Shoot me a msg I May Be of help
question:
today I locked the booloader,but my PH-1 can't boot,it siad"Your devices is corrput,It can't be trusted and will not boot."
I use adb cant find devices.But it can use"fastboot decives".
"fastboot -w"is failed,the remote is "remote: Erase is not allowed in Lock State."
"fastboot flash boot.img" or "fastboot flash recovery twrp.img" also failed. the remote is "remote: Erase is not allowed in Lock State"
can anyone tell me how to get devices?
Click to expand...
Click to collapse
For "Your devices is corrput,It can't be trusted and will not boot." Press power button?
Try
fastboot oem disable_dm_verity
Then
If able boot into recovery (hard reset button combination)
adb reboot "dm-verity enforcing"
Worth a shot ...
Aimless Rambler said:
For "Your devices is corrput,It can't be trusted and will not boot." Press power button?
Try
fastboot oem disable_dm_verity
Then
If able boot into recovery (hard reset button combination)
adb reboot "dm-verity enforcing"
Worth a shot ...
Click to expand...
Click to collapse
also failed……
I am using A2017U, and for some reasons i unlocked my bootloader and flashed custom rom. Now i want to lock my bootloader but i tried several times to enter fastboot but the device is not entering fastboot through any mean, i tried through physical kepess through adb command, everything.
please help me.
teji007 said:
I am using A2017U, and for some reasons i unlocked my bootloader and flashed custom rom. Now i want to lock my bootloader but i tried several times to enter fastboot but the device is not entering fastboot through any mean, i tried through physical kepess through adb command, everything.
please help me.
Click to expand...
Click to collapse
Maybe by using Axon 7 EDL toolkit to enable fastboot first (Unlock option), then "fastboot oem lock" in fastboot mode. Refer to https://forum.xda-developers.com/showpost.php?p=78267172&postcount=200 . Warning : you need stock ROM (no changes in boot, recovery, system/root etc...) to avoid bricking your phone.