From 9372abec9a1ca2b9a7dc96321ddcd546b7d51bbe Mon Sep 17 00:00:00 2001 From: ThangNN99 Date: Sun, 26 Jul 2026 22:12:54 +0700 Subject: [PATCH] Set androidboot.verifiedbootstate=orange to allow adb remount adb remount and adb disable-verity require ro.boot.verifiedbootstate to equal "orange" (bootloader unlocked), otherwise fs_mgr_remount refuses with "Device must be bootloader unlocked" even on userdebug builds. This board has no real bootloader/AVB enforcement (TARGET_NO_BOOTLOADER := true), so the property was never set and adb remount always failed. Same fix as applied upstream for hikey/hikey960: https://android.googlesource.com/device/linaro/hikey/+/fa66979a87e53d92dc717fd524f7958af20eb9f3 Tested on real Raspberry Pi 4 hardware: after this change, ro.boot.verifiedbootstate=orange is reported and "adb root && adb remount" succeeds (remounts / and /vendor as RW). --- BoardConfig.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/BoardConfig.mk b/BoardConfig.mk index d746b2f..ef21bc1 100644 --- a/BoardConfig.mk +++ b/BoardConfig.mk @@ -55,7 +55,7 @@ BOARD_AVB_ENABLE := false # Kernel BOARD_CUSTOM_BOOTIMG := true BOARD_CUSTOM_BOOTIMG_MK := $(DEVICE_PATH)/mkbootimg.mk -BOARD_KERNEL_CMDLINE := console=ttyS0,115200 androidboot.hardware=rpi4 +BOARD_KERNEL_CMDLINE := console=ttyS0,115200 androidboot.hardware=rpi4 androidboot.verifiedbootstate=orange # Boot devices — our fstab mounts partitions via /dev/block/by-name/*, and # first-stage init only creates those symlinks for partitions on a declared