False bootloader locked messags

[TGMGT]

What happened?

It tells a false message of bootloader getting locked even though is not some devices have bootloader unlocked but verified boot state and you checked boot state only to check if bootloader is unlocked which is a bad checker leading to me this false message

Installer version

Latest nightly

Device

Galaxy Tab S2 - gts210ltexx

Android version

11

Custom ROM

Linage 18.1 modified

Relevant log output

[ale5000-git]

Hi, this is likely a false positive when certain ROMs or Magisk modules spoof a locked state even on an actually-unlocked device.

I have added an explanation here: https://microg-unofficial-installer.readthedocs.io/en/latest/KNOWN-ISSUES.html#the-boot-loader-is-locked
You can also find the workaround on the same page.

[TGMGT]

Hi, this is likely a false positive when certain ROMs or Magisk modules spoof a locked state even on an actually-unlocked device.

I had no modules and it still said that

[TGMGT]

Is because of verified boot state getting true even though bootloader is unlocked my custom ROM does not show OEM unlocking but the device is still unlocked

[TGMGT]

I think it happens on PBRP last time I use TWRP it worked but on PBRP it didn't so that would be the issue

[DJTusheniyTapochek]

I got such issue on Realme 6 earlier. It later turned out the cause was OEM Unlocking not being set prior to unlocking the bootloader. After I got another unit and set OEM Unlocking correctly on it, there was no issue.