Database Users

[FIX] DM-Verity Warning (no flashing required) - OnePlus 3T Guides, News, & Discussion

Hey all, I think many of you have already seen my post in the other thread, but in an effort to make it more visible to anyone that didn't see it and to new users, here it is again.
If a mod wants to make it a sticky, feel free.
Make sure you have fastboot working properly in your environment.
Code:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
TWRP was already installed, and dm-verity had been tripped at some point. After poking around the firmware, I discovered there are these commands.. after both, the warning is gone - didn't need to flash any firmware.
Here is a link to my original post in the other thread, replies following that have confirmation. Some folks have mentioned using only the enable command alone worked for them, but I haven't tried that myself. Also some oneplus 3 users have confirmed it works there as well.
** And the usual disclaimer.. I'm not responsible for any damage, issues, or your phone attacking you in your sleep due to the information I have provided **

th3g1z said:
Hey all, I think many/most of you have already seen my post in the other thread, but in an effort to make it more visible to anyone that didn't see it and to new users, here it is again.
If a mod wants to make it a sticky, feel free.
Make sure you have fastboot working properly in your environment.
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
TWRP was already installed, and dm-verity had been tripped at some point. After poking around the firmware, I discovered there are these commands.. after both, the warning is gone - didn't need to flash any firmware.
Here is a link to my original post in the other thread, replies following that have confirmation. Some folks have mentioned using only the enable command alone worked for them, but I haven't tried that myself. Also some oneplus 3 users have confirmed it works there as well.
http://forum.xda-developers.com/showpost.php?p=70698410&postcount=112
And the usual disclaimer.. I'm not responsible for any damage, issues, or your phone attacking you in your sleep due to the information I have provided.
Click to expand...
Click to collapse
Worked a treat. Brilliant now we just need a way to remove the bootloader message and bobs your uncle.

That was easy! Thank you so much

Some commands which I found from aboot.img.
Code:
oem boot_mode rf/wlan/ftm/normal
oem console
oem unconsole
oem dump
oem kmemleak detect
oem kmemleak undetect
oem reboot-shutdown
oem reboot-bootloader
oem boot_mode
oem disable_dm_verity
oem enable_dm_verity
oem force_training
oem unforce_training
oem datafs
oem unlock
oem lock
flashing unlock
flashing lock
flashing lock_critical
flashing unlock_critical
flashing get_unlock_ability
oem device-info preflash
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge
oem select-display-panel
oem run-tests
Dump --->
Code:
aboot.img: OEM panel override:%s
aboot.img: OEM ID: 0x%x
aboot.img: Verified boot.img with oem keystore
aboot.img: Verification with oem keystore failed. Use embedded certificate for verification
aboot.img: If you don't want to see this screen, please lock your device by "fastboot oem lock" and erase userdata.
aboot.img: androidboot.ftm_mode=ftm_at ftm_console_silent androidboot.ftm_mode=ftm_wlan androidboot.ftm_mode=ftm_mos androidboot.ftm_mode=ftm_rf androidboot.ftm_mode=ftm_recovery mos fastboot add_pcba_number_cmdline add_console_cmdline add_rf_version_cmdline add_project_name_cmdline add_oem_dm_verity_cmdline_len add_battery_absent_cmdline add_reboot_mode_cmdline ˆ‘ ˆ‘(ˆ‘0ˆ‘4ˆ‘8ˆ‘Lˆ‘Tˆ‘`ˆ‘`ˆ‘`ˆ‘lˆ‘tˆ‘xˆ‘€ˆ‘ˆˆ‘add_pwron_reason_cmdline add_ddr_info_cmdline add_oem_angela_cmdline_len add_battery_absent_cmdline_len add_kmemleak_cmdline add_oem_secboot_cmdline_len add_rpmb_enable_status_cmdline_len ˆ‘œˆ‘Ü{ˆ‘¤ˆ‘¬ˆ‘´ˆ‘¼ˆ‘ȍˆ‘add_pwron_reason_cmdline_len add_rpmb_enable_status_cmdline add_hw_version_cmdline_len add_hw_version_cmdline add_oem_angela_cmdline add_oem_secboot_cmdline add_selinux_cmdline_len add_reboot_mode_cmdline_len add_selinux_cmdline add_oem_dm_verity_cmdline add_rf_version_cmdline_len userdata fs type: %s enable force training
aboot.img: Kmemleak detect close default Kmemleak detect open Use 'fastboot oem boot_mode rf/wlan/ftm/normal' unlock device to dump keystore Dump partition: %s Partition table doesn't exist
aboot.img: platform/oneplus/op_cmdline.c dumpaddr failed to dump partition %02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X partition table doesn't exist unknown partition name oem console oem unconsole oem dump oem kmemleak detect oem kmemleak undetect oem reboot-shutdown oem reboot-bootloader oem boot_mode oem disable_dm_verity oem enable_dm_verity oem force_training oem unforce_training oem datafs COLD WARM androidboot.startupmode=pwrkey androidboot.startupmode=usb_charger androidboot.startupmode=dc_charger androidboot.startupmode=rtc androidboot.startupmode=unknow androidboot.startupmode=pon1 androidboot.startupmode=hard_reset androidboot.startupmode=SMPL true false %s: enter. cmdline_len=%d
aboot.img: unlocked! locked! Device already : %s oem unlock is not allowed yes recoveryfs androidboot.bootdevice= app/aboot/aboot.c boot_dev_buf androidboot.serialno= androidboot.verifiedbootstate= Devinfo paritition possibly corrupted!!!. Please erase devinfo partition to continue booting
aboot.img: oem_project_name product serialno Invalid partition index
aboot.img: flash: erase: continue oem unlock oem lock flashing unlock flashing lock flashing lock_critical flashing unlock_critical flashing get_unlock_ability oem device-info preflash oem enable-charger-screen oem disable-charger-screen oem off-mode-charge oem select-display-panel oem run-tests sbl sdi xbl hyp pmic green orange yellow red logging enforcing boot_linux_from_flash :ÿ&í p=c ÁÊ õò p=c H1 1 8 H1
aboot.img: ffbm- cmd_oem_runtests Running LK tests ...
Have fun.
I'm not responsible for any bricked devices
~LampunVarjostin

th3g1z said:
Hey all, I think many of you have already seen my post in the other thread, but in an effort to make it more visible to anyone that didn't see it and to new users, here it is again.
If a mod wants to make it a sticky, feel free.
Make sure you have fastboot working properly in your environment.
TWRP was already installed, and dm-verity had been tripped at some point. After poking around the firmware, I discovered there are these commands.. after both, the warning is gone - didn't need to flash any firmware.
Here is a link to my original post in the other thread, replies following that have confirmation. Some folks have mentioned using only the enable command alone worked for them, but I haven't tried that myself. Also some oneplus 3 users have confirmed it works there as well.
** And the usual disclaimer.. I'm not responsible for any damage, issues, or your phone attacking you in your sleep due to the information I have provided **
Click to expand...
Click to collapse
Is it work for rooted ob 2?

'fastboot oem disable_dm_verity' did not worked on my phone.

ozzyville said:
'fastboot oem disable_dm_verity' did not worked on my phone.
Click to expand...
Click to collapse
You need to enter both commands. Disable and enable.

Thanks. It worked on Oneplus 3T but did not work on Oneplus 3.

Thanks
th3g1z said:
Hey all, I think many of you have already seen my post in the other thread, but in an effort to make it more visible to anyone that didn't see it and to new users, here it is again.
If a mod wants to make it a sticky, feel free.
Make sure you have fastboot working properly in your environment.
Code:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
TWRP was already installed, and dm-verity had been tripped at some point. After poking around the firmware, I discovered there are these commands.. after both, the warning is gone - didn't need to flash any firmware.
Here is a link to my original post in the other thread, replies following that have confirmation. Some folks have mentioned using only the enable command alone worked for them, but I haven't tried that myself. Also some oneplus 3 users have confirmed it works there as well.
** And the usual disclaimer.. I'm not responsible for any damage, issues, or your phone attacking you in your sleep due to the information I have provided **
Click to expand...
Click to collapse
It Worked On My 3T. Thanks Mate

Thanks, worked!

Same for oneplus 3?

lace79 said:
Same for oneplus 3?
Click to expand...
Click to collapse
It worked for my OP3

LampunVarjostin said:
Some commands which I found from aboot.img.
Code:
oem boot_mode rf/wlan/ftm/normal
oem console
oem unconsole
oem dump
oem kmemleak detect
oem kmemleak undetect
oem reboot-shutdown
oem reboot-bootloader
oem boot_mode
oem disable_dm_verity
oem enable_dm_verity
oem force_training
oem unforce_training
oem datafs
oem unlock
oem lock
flashing unlock
flashing lock
flashing lock_critical
flashing unlock_critical
flashing get_unlock_ability
oem device-info preflash
oem enable-charger-screen
oem disable-charger-screen
oem off-mode-charge
oem select-display-panel
oem run-tests
Dump --->
Code:
aboot.img: OEM panel override:%s
aboot.img: OEM ID: 0x%x
aboot.img: Verified boot.img with oem keystore
aboot.img: Verification with oem keystore failed. Use embedded certificate for verification
aboot.img: If you don't want to see this screen, please lock your device by "fastboot oem lock" and erase userdata.
aboot.img: androidboot.ftm_mode=ftm_at ftm_console_silent androidboot.ftm_mode=ftm_wlan androidboot.ftm_mode=ftm_mos androidboot.ftm_mode=ftm_rf androidboot.ftm_mode=ftm_recovery mos fastboot add_pcba_number_cmdline add_console_cmdline add_rf_version_cmdline add_project_name_cmdline add_oem_dm_verity_cmdline_len add_battery_absent_cmdline add_reboot_mode_cmdline ˆ‘ ˆ‘(ˆ‘0ˆ‘4ˆ‘8ˆ‘Lˆ‘Tˆ‘`ˆ‘`ˆ‘`ˆ‘lˆ‘tˆ‘xˆ‘€ˆ‘ˆˆ‘add_pwron_reason_cmdline add_ddr_info_cmdline add_oem_angela_cmdline_len add_battery_absent_cmdline_len add_kmemleak_cmdline add_oem_secboot_cmdline_len add_rpmb_enable_status_cmdline_len ˆ‘œˆ‘Ü{ˆ‘¤ˆ‘¬ˆ‘´ˆ‘¼ˆ‘ȍˆ‘add_pwron_reason_cmdline_len add_rpmb_enable_status_cmdline add_hw_version_cmdline_len add_hw_version_cmdline add_oem_angela_cmdline add_oem_secboot_cmdline add_selinux_cmdline_len add_reboot_mode_cmdline_len add_selinux_cmdline add_oem_dm_verity_cmdline add_rf_version_cmdline_len userdata fs type: %s enable force training
aboot.img: Kmemleak detect close default Kmemleak detect open Use 'fastboot oem boot_mode rf/wlan/ftm/normal' unlock device to dump keystore Dump partition: %s Partition table doesn't exist
aboot.img: platform/oneplus/op_cmdline.c dumpaddr failed to dump partition %02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X%02X partition table doesn't exist unknown partition name oem console oem unconsole oem dump oem kmemleak detect oem kmemleak undetect oem reboot-shutdown oem reboot-bootloader oem boot_mode oem disable_dm_verity oem enable_dm_verity oem force_training oem unforce_training oem datafs COLD WARM androidboot.startupmode=pwrkey androidboot.startupmode=usb_charger androidboot.startupmode=dc_charger androidboot.startupmode=rtc androidboot.startupmode=unknow androidboot.startupmode=pon1 androidboot.startupmode=hard_reset androidboot.startupmode=SMPL true false %s: enter. cmdline_len=%d
aboot.img: unlocked! locked! Device already : %s oem unlock is not allowed yes recoveryfs androidboot.bootdevice= app/aboot/aboot.c boot_dev_buf androidboot.serialno= androidboot.verifiedbootstate= Devinfo paritition possibly corrupted!!!. Please erase devinfo partition to continue booting
aboot.img: oem_project_name product serialno Invalid partition index
aboot.img: flash: erase: continue oem unlock oem lock flashing unlock flashing lock flashing lock_critical flashing unlock_critical flashing get_unlock_ability oem device-info preflash oem enable-charger-screen oem disable-charger-screen oem off-mode-charge oem select-display-panel oem run-tests sbl sdi xbl hyp pmic green orange yellow red logging enforcing boot_linux_from_flash :ÿ&í p=c ÁÊ õò p=c H1 1 8 H1
aboot.img: ffbm- cmd_oem_runtests Running LK tests ...
Have fun.
I'm not responsible for any bricked devices
~LampunVarjostin
Click to expand...
Click to collapse
how to get that's all list command?

Jeez, that was ridiculously easy. Thanks for finding this!!

not work on oneplus 3

It works on my Oneplus 3 A3000. Thanks. It was a little annoying.

zainifame said:
Some commands which I found from aboot.img.
Dump --->
how to get that's all list command?
Click to expand...
Click to collapse
https://www.google.fi/amp/s/www.xda...dden-fastboot-commands/amp/?client=ms-unknown

Thanks, worked on my oneplus 3.

well successfully disabled that dm verify message now one last thing can the disable bootloader unlock msg be disabled ..

Well, that was easy.
thanks

Related

Plz give the cmd code for checking details of bootloader locked or unlocked

Here you go
fastboot -i 0x1ebf oem device-info

jogson said:
Plz give the cmd code for checking details of bootloader locked or unlocked
Click to expand...
Click to collapse
**************************WARNING****************************************
Please not that unlocking and re-locking boot loader in CM12 (Lollipop) Would ERASE USER DATA!
So first make sure that your device (yureka) is detected fastboot -i 0x1ebf devices
fastboot -i 0x1ebf oem lock
Please hit Thanks! if it worked!

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

Here is a adb log↓↓↓
C:\>...>fastboot flashing unlock
...FAILED(remote：oem is not allowed)
(But im unlocked OEM in developer options,
so is there anyone can unlock it?)

INFoahh said:
Here is a adb log↓↓↓
C:\>...>fastboot flashing unlock
...FAILED(remote：oem is not allowed)
(But im unlocked OEM in developer options,
so is there anyone can unlock it?)
Click to expand...
Click to collapse
the command also is
flashboot oem unlcok

two types of command Available
try any one command
fastboot oem unlock
fastboot flashing unlock
Did you enable unlocking within the Developer Options? You must enable that prior to "fastboot oem unlock"

was able to get it working on another pc thanks

You can't relock BL - there isn't the newest flashable stock rom. Read again thread you linked and find in OP this:
"...then follow the above commands, but the following commands in place of the "lock" commands in the list above:
fastboot oem fb_mode_set instead of fastboot oem lock begin
fastboot oem fb_mode_clear instead of fastboot oem lock
..."
You can flash: 24.49.18-8 and after it install ota update.

Hi
I am trying to relock the BL for warranty.
I did a EDL-FULL-Nougat, then found out that Nougat does not boot into bootloader.
So I downloaded A2017G_NrollbackM from ZTE, which worked nicely. I'm in bootloader now and see
Code:
C:\>fastboot getvar unlocked
unlocked:
finished. total time: 0.008s
which was expected.
... just I don't understand, why I can't lock or get oem device-info
Code:
C:\>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.001s
please help, thanks alex

did you enable 'oem unlock' on the developer settings?

yes, sorry forgot to add

lxlx said:
yes, sorry forgot to add
Click to expand...
Click to collapse
so i guess you have been able to lock it?

No, I mean I forgot to add that info in my first post.
I can not run device-info or lock, log posted.
Cheers :/

your Fastboot.exe is too old

Choose an username... said:
so i guess you have been able to lock it?
Click to expand...
Click to collapse
but you didn't even respond to my question
did you enable 'oem unlock' on the Developer settings?

skdubg said:
your Fastboot.exe is too old
Click to expand...
Click to collapse
that sounds promising, where to get the up-to-date fastboot.exe?
Choose an username... said:
but you didn't even respond to my question
Click to expand...
Click to collapse
I tried, but my non-native english failed apparently.
So to be clear:
Choose an username... said:
did you enable 'oem unlock' on the Developer settings?
Click to expand...
Click to collapse
yes I had oem unlock in dev-options enabled. Then I tried
Code:
C:\>fastboot oem device-info
...
FAILED (remote: unknown command)
finished. total time: 0.004s
C:\>fastboot oem lock
...
FAILED (remote: unknown command)
finished. total time: 0.001s

Post deleted. Didn't notice you are on mm.

lxlx said:
that sounds promising, where to get the up-to-date fastboot.exe?
Click to expand...
Click to collapse
The 15 seconds ADB installer should install the newest fastboot available. But be sure to get rid of the old installation

How to be sure?
Uninstall all related driver programs, check usbdeview on connected device and uninstall accordingly.
Connect and axon does not get fully installed, yellow ? In device manager. Install with local google usb_driver does not work.
Only with ZTE driver I got adb device. Then adb devices and fastboot devices works. But still can not lock.
I found my old aboot_lock.img from unlocking backup... But it's getting more scary step by step.
Not sure what I did wrong along the way.
EDL FULL then original MMrollback. Shouldn't this be all stock ZTE everywhere? Why fastboot does not like me...

lxlx said:
How to be sure?
Uninstall all related driver programs, check usbdeview on connected device and uninstall accordingly.
Connect and axon does not get fully installed, yellow ? In device manager. Install with local google usb_driver does not work.
Only with ZTE driver I got adb device. Then adb devices and fastboot devices works. But still can not lock.
I found my old aboot_lock.img from unlocking backup... But it's getting more scary step by step.
Not sure what I did wrong along the way.
EDL FULL then original MMrollback. Shouldn't this be all stock ZTE everywhere? Why fastboot does not like me...
Click to expand...
Click to collapse
This hasn't got anything to do with the drivers. I mean, delete the fastboot.exe and adb.exe that you have, then download the "15 seconds ADB installer" and install it, and try again

OK, a bit more digging.
I have 15sec-adb installed systemwide in C:\adb>
Code:
C:\adb>dir /B
aboot.img
aboot_lock.img
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
strings.exe
as you can see, I put my aboot dumps there as well, and a strings-linux-like tool - after
reading this thread.
so, I got the ZTE driver to have my Axon7 visible to adb/fastboot (otherwise no device) ... and I have the latest 15sec adb here.
Code:
C:\adb>fastboot devices
823b48f5 fastboot
... but that's the only thing that works. not even easy things like this do
Code:
C:\adb>fastboot continue
resuming boot...
FAILED (remote: unknown command)
finished. total time: 0.015s
quoting the other thread
What’s missing in this list are fastboot oem commands. These commands are specific to Android device manufacturers, and there is no comprehensive list or documentation anywhere for what fastboot oem commands are available.
Click to expand...
Click to collapse
so I'm not sure if my fastboot version is the problem. I rather think that the Nougat->MM stock thingy, overwrite my Axon7 aboot.img with only a small set of fastboot commands available.
in my backup I see
Code:
C:\adb>strings aboot* | findstr /i oem
C:\adb\aboot.img: 04 0004 OEM_ID1
C:\adb\aboot.img: oem unlock is not allowed
C:\adb\aboot.img: oem unlock
C:\adb\aboot.img: oem unlock-go
C:\adb\aboot.img: oem lock
C:\adb\aboot.img: oem device-info
C:\adb\aboot.img: is_oem_unlock_allowed
C:\adb\aboot_lock.img: 04 0004 OEM_ID1
C:\adb\aboot_lock.img: oem unlock is not allowed
C:\adb\aboot_lock.img: oem unlock
C:\adb\aboot_lock.img: oem unlock-go
C:\adb\aboot_lock.img: oem lock
C:\adb\aboot_lock.img: oem device-info
C:\adb\aboot_lock.img: is_oem_unlock_allowed
so in old and new aboot I had oem-commands available, back then...
I'm not an expert, but do you guys really know that my problem is related to the PC-config I have, and not to the device-config?
I can not check aboot on device, as I'm not root.

update...
I did not succeed with fastboot commands, see above.
But, I flashed the A2017G B10_FULL_EDL package, and have no more 'not-verified-boot-screen-warning' ...
After miflash android greeted me with 'enter-android-password' ... I wiped cache/data again, now all good and -it seems- BL locked.
so, if you have access to EDL mode, try different EDL packages, you may end up like I did, full stock locked (at least it seems so)... good luck

lxlx said:
update...
I did not succeed with fastboot commands, see above.
But, I flashed the A2017G B10_FULL_EDL package, and have no more 'not-verified-boot-screen-warning' ...
After miflash android greeted me with 'enter-android-password' ... I wiped cache/data again, now all good and -it seems- BL locked.
so, if you have access to EDL mode, try different EDL packages, you may end up like I did, full stock locked (at least it seems so)... good luck
Click to expand...
Click to collapse
Pretty sure miflash cannot lock your bl.

Technically I would not know why it should not be possible.
If it flashes block wise, it can update anything... for me the purpose of EDL.

lxlx said:
Technically I would not know why it should not be possible.
If it flashes block wise, it can update anything... for me the purpose of EDL.
Click to expand...
Click to collapse
I think it is still unlocked. I read something weird about the message not appearing after having a full stock system
But if you're gonna sell it/claim warranty, who cares?

update, ZTE repaired the display

lxlx said:
update, ZTE repaired the display
Click to expand...
Click to collapse
Did you lock the bootloader after all?
I guess they wouldn't even notice if the 5 sec screen didn't show up lol

BL still unlocked.
I sent it with MM-B10-FULL-EDL, where 5sec screen was not displayed.
And got it back with MM-B06 ... with 5sec screen
so I guess what happened:
- ZTE turns on, does not see 5sec, repairs display, does usual EDR 'update' which is actually a downgrade to MM-B06, then sees 5sec-warn and thinks of what to do now, but as screen is repaired, what else than return
OR
- ZTE repairs screen (VIP) although bootloader unlocked
either way, all good.
what I learned is
- fastboot parameters need to be in aboot.img
- I can't do getvar or oem-lock until I flash another aboot.
Anyone with A2017G and unlocked BL who needs to send back:
EDL to A2017G_B10_FULL_EDL.zip
and hope you also have hidden 5sec screen (BL still unlocked)