View Single Post
Old 06-30-2024, 06:59 AM   #20
DanyDanman
Connoisseur
DanyDanman began at the beginning.
 
Posts: 51
Karma: 10
Join Date: Jun 2024
Device: Boox Go 10.3
I have been hard at work to find a solution. No luck yet.

I have checked
Code:
build.prop
ro.boot.verifiedbootstate: Set to orange. This indicates that your device's verified boot state is less secure, generally associated with an unlocked bootloader in a development setting.

ro.boot.flash.locked: Set to 0. This correctly reflects that the bootloader is unlocked, aligning with the ro.boot.verifiedbootstate being orange.

sys.oem_unlock_allowed: Set to 0. This seems contradictory given the bootloader status is unlocked. Normally, this would be set to 1 if the bootloader unlocking is permissible. If your intention is for the device to allow OEM unlocking, this property should be set to 1.

The property ro.oem_unlock_supported, which you mentioned should be set based on the device's support for flashing unlock, is not listed in your output. If your device supports this feature, you should ensure this property is explicitly defined in your system configuration with the appropriate value (1 for support, 0 for no support).

This what I got from it tnx to my second brain. Posting here just incase.

I have tried a different fastboot driver the google instead xaomi
I have chosen a different fastboot and bogus one no luck

I really hope we can crack this togher.
DanyDanman is offline   Reply With Quote