diff options
| author | Mattijs Korpershoek <mkorpershoek@baylibre.com> | 2025-01-08 15:38:42 +0100 |
|---|---|---|
| committer | Mattijs Korpershoek <mkorpershoek@baylibre.com> | 2025-01-23 15:23:05 +0100 |
| commit | 6745cbed6edc06fae7fbc4b360e39c3963d57b13 (patch) | |
| tree | 840a49791a161a7b57965278f27e2e502dbb1d07 /common/bloblist.c | |
| parent | ae58cd7b39207175c8696d7bf38321b1a4c9957a (diff) | |
bootstd: android: Allow boot with AVB failures when unlocked
When the bootloader is UNLOCKED, it should be possible to boot Android
even if AVB reports verification errors [1].
This allows developers to flash modified partitions on
userdebug/engineering builds.
Developers can do so on unlocked devices with:
$ fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
In such case, bootmeth_android refuses to boot.
Allow the boot to continue when the device is UNLOCKED and AVB reports
verification errors.
[1] https://source.android.com/docs/security/features/verifiedboot/boot-flow#unlocked-devices
Fixes: 125d9f3306ea ("bootstd: Add a bootmeth for Android")
Reviewed-by: Julien Masson <jmasson@baylibre.com>
Link: https://lore.kernel.org/r/20250108-avb-disable-verif-v2-2-ba7d3b0d5b6a@baylibre.com
Signed-off-by: Mattijs Korpershoek <mkorpershoek@baylibre.com>
Diffstat (limited to 'common/bloblist.c')
0 files changed, 0 insertions, 0 deletions