Supported devices

[chenxiaolong]

This is a continually updated list of devices that are known to properly support custom AVB keys. If you've personally tested avbroot on a device, please leave a comment and I'll update the list.

Google is the only OEM to officially document that avb_custom_key is supported. For other OEMs, there's no way to know if custom keys are supported without just trying it.

Supported

Fairphone

• Fairphone 4 and 5 (user report)

Google

• All Pixel devices since the Pixel 2 have bootloaders that support custom keys (official docs). However, only Pixel 4 and newer use AVB 2.0 with a compatible partitioning scheme (#274).

Motorola

• Motorola Moto G32 (user report)

Nothing

• Nothing Phone (1) (user report)
• Nothing Phone (2) (user report)

Sony

• Sony Xperia V (user report)

Xiaomi

• Xiaomi Redmi Note 10 Pro (user report)
• Xiaomi 14 (user report)

Not supported

OnePlus

• OnePlus devices are no longer compatible because newer bootloader versions no longer allow custom keys. Some devices may just fail to boot (#186, #195, #212), while others may end up bricked (#290).

Xiaomi

• Most Xiaomi devices do not support avb_custom_key. Only a couple devices (listed above) are known to support it.
• Xiaomi Redmi Note 13 Pro 5G (user report)

[PsikoBlock]

Custom keys work on Fairphone 4 and 5 with the manufacturer supporting custom ROMs and even selling devices with them preinstalled.

[chenxiaolong]

Thanks, added!

[joeyoropesa-dev]

So, Xiaomi cannot use selfsigned platform keys?

[pixincreate]

So, Xiaomi cannot use selfsigned platform keys?

No. At present, only Google and Nothing support relocking bootloader with custom avb keys

[joeyoropesa-dev]

So, Xiaomi cannot use selfsigned platform keys?

No. At present, only Google and Nothing support relocking bootloader with custom avb keys

What if the problem was just OS public certificates embedded in /system partition and vbmeta images (and maybe even embedded in dtbo and so on..)

So avb_custom_key actually worked for boot.img and that is a good sign

So, if we replace OEM's embedded signatures from fastboot images and their partitions like /system and of course vbmeta, and even repatching the meta with flag for disabling verification and signatures but signing it with custom key, it could actually boot.

(Of course, clearing caches is recommended so that system will rebuild all caches from scratch including the embedded keys from partitions and using private key from avb_custom_key correctly with every partition, not just aboot partition)

[andidevi]

Sony Xperia V can be locked again with

fastboot oem lock

This is confirmed for XQ-DQ54 but probably will additionally hold for XQ-DQ72.

You get a warning about the changed OS and a link to g.co/ABH is displayed.
So you still have to press power in the right moment/press it twice.

[chenxiaolong]

The Pixel 9 series is also compatible, as expected (tested personally). Their AVB structure is completely identical to the Pixel 7 and 8 series.

[diosvany]

i keep getting this error on my pixel 9 pro xl what am i doing wrong

[pascallj]

i keep getting this error on my pixel 9 pro xl what am i doing wrong

If you need any help, you'd be better off by opening a new issue or discussion. However in this case, you are specifying your ota zip as key-avb, key-ota and cert-ota which is definitely not right. If that is not a typo, then I'd recommend you read though the instructions again and try again.