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)
• Motorola moto g52 (user report)
• Motorola moto g200 5G (user report)
• Motorola ThinkPhone (user report)
  • It may be necessary to modify the AVB rollback index to be able to boot with the bootloader locked. The bootloader is meant to reset the rollback state when unlocking and locking, but does not appear to do so.

Nothing

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

OnePlus

• OnePlus 6 and 6t (user report)
• (See below for newer devices)

Sony

• Sony Xperia V (user report)
• Sony Xperia 10 V (user report)

Xiaomi

• Xiaomi 14 (user report)
• Xiaomi POCO F5 (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).

Nothing

• Nothing Phone (2a)
  • Does not support avb_custom_key (user report)

Xiaomi

• Most Xiaomi devices do not support avb_custom_key. Only a couple devices (listed above) are known to support it.
• Xiaomi Redmi Note 10 Pro
  • Supports avb_custom_key (user report)
  • Not an A/B device (user report)
• 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.

[alexceltare2]

I can confirm that Redmi Note 10 Pro and possibly other Qualcomm-based ones do support avb_custom_key.

[fuengfah]

I can confirm that Redmi Note 10 Pro and possibly other Qualcomm-based ones do support avb_custom_key.

Do you thing Redmi Note 12 4G will support avbroot?

[crnisamuraj]

I can confirm that Xiaomi 14 does support avb_custom_key . For now I just successfully flashed and erased avb_custom_key partition. I plan to try resigning HyperOS EU and relock bootlaoader.

❯ fastboot flash avb_custom_key avb_custom_key.img
Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).
Sending 'avb_custom_key' (1 KB)                    OKAY [  0.001s]
Writing 'avb_custom_key'                           OKAY [  0.007s]
Finished. Total time: 0.041s

❯ fastboot erase avb_custom_key
Erasing 'avb_custom_key'                           OKAY [  0.010s]
Finished. Total time: 0.025s

[fuengfah]

Wow! This is great news please keep update or where can I follow you

[alexceltare2]

I can confirm that Redmi Note 10 Pro and possibly other Qualcomm-based ones do support avb_custom_key.

Do you thing Redmi Note 12 4G will support avbroot?

It may but I've heard Xiaomi is planning to terminate bootloader unlocking service. Those with unlocked bootloaders are prime real estate and relocking them will be for good.

[ABJ4403]

I can confirm that Xiaomi 14 does support avb_custom_key . For now I just successfully flashed and erased avb_custom_key partition. I plan to try resigning HyperOS EU and relock bootlaoader.

❯ fastboot flash avb_custom_key avb_custom_key.img
Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).
Sending 'avb_custom_key' (1 KB)                    OKAY [  0.001s]
Writing 'avb_custom_key'                           OKAY [  0.007s]
Finished. Total time: 0.041s

❯ fastboot erase avb_custom_key
Erasing 'avb_custom_key'                           OKAY [  0.010s]
Finished. Total time: 0.025s

How can we backup the avb_custom_key tho?

[james28909]

i have a verizon pixel 3 xl. will it be possible for this tool to support this device?

[chenxiaolong]

i have a verizon pixel 3 xl. will it be possible for this tool to support this device?

I have no idea if Verizon impacts anything, but the Pixel 3 XL is only supported if you don't use the stock OS. (For the same reason as the Pixel 3a: https://github.com/chenxiaolong/avbroot/issues/274#issuecomment-2073833455) LineageOS should work.

[pascallj]

How can we backup the avb_custom_key tho?

The avb_custom_key is just derived from a file you created on your PC. You can back it up any way you see fit.

[ghost]

Will avbroot work on Sony Xperia 5 II? And.. maybe, Xperia 1 II.

This actually looks like good phone, 3.5mm and dac, micro sd.. But it's too hard to find models(global, etc.) with support unlock bootloader in putland(russian slavery, lol.).. Is it worth wasting time searching?

The ‘sellers’ have taken over the secondary market and are selling operator-blocked(bootloader) versions from.. nippa! Although compared to russia there it is real gulag in terms of operators. Although, what is there to be afraid of?. What is fear?........ If we buy it, we plan to install LineageOS(Although, there are no alternatives lol).

Nipponia is a pretty beautiful country, but are there any delicious pancakes there? Does the bottle have freedom.... Do FURRRIs exist?

[alexceltare2]

Will avbroot work on Sony Xperia 5 II? And.. maybe, Xperia 1 II.

This actually looks like good phone, 3.5mm and dac, micro sd.. But it's too hard to find models(global, etc.) with support unlock bootloader in putland(russian slavery, lol.).. Is it worth wasting time searching?

The ‘sellers’ have taken over the secondary market and are selling operator-blocked(bootloader) versions from.. nippa! Although compared to russia there it is real gulag in terms of operators. Although, what is there to be afraid of?. What is fear?........ If we buy it, we plan to install LineageOS(Although, there are no alternatives lol).

Nipponia is a pretty beautiful country, but are there any delicious pancakes there? Does the bottle have freedom.... Do FURRRIs exist?

WTF did I just read?

[lucasmz-dev]

Tested on a Moto G32 "devon". It's probably fine on the Moto G52 "rhode" as well and G42 "hawao", but I didn't test it, I do have a G52 I use personally.

I should still test if I can return to officially signed CalyxOS properly, see if I get any issues with rollback indexes, but I wouldn't expect so, right? The only problem would be if I flashed an image with a number higher than the one Motorola ships by latest, as long as avbroot doesn't modify it, it's fine;

[chenxiaolong]

I should still test if I can return to officially signed CalyxOS properly, see if I get any issues with rollback indexes, but I wouldn't expect so, right? The only problem would be if I flashed an image with a number higher than the one Motorola ships by latest, as long as avbroot doesn't modify it, it's fine;

AVB 2.0 rollback indices only matter while the bootloader is locked. If you unlock the bootloader again, the indices are ignored/reset. It should never prevent you from switching between OS's, as long there's a bootloader unlock and relock somewhere in that process.

[lucasmz-dev]

AVB 2.0 rollback indices only matter while the bootloader is locked. If you unlock the bootloader again, the indices are ignored/reset. It should never prevent you from switching between OS's, as long there's a bootloader unlock and relock somewhere in that process.

Not in these devices, unfortunately. Similar thing happens on the Fairphones (though there I believe it's literally like, a check on the security patch) You can't for example get an older build of CalyxOS and flash it and have Verified Boot, it has to match the latest stock's number (because putting a higher number would cause it to not be possible to flash stock again, or possibly another OS with AVB),

[chenxiaolong]

Not in these devices, unfortunately. Similar thing happens on the Fairphones (though there I believe it's literally like, a check on the security patch) You can't for example get an older build of CalyxOS and flash it and have Verified Boot, it has to match the latest stock's number (because putting a higher number would cause it to not be possible to flash stock again, or possibly another OS with AVB),

Oh wow, I had no idea. That's a pretty awful implementation.

[lucasmz-dev]

Well, reinstall worked fine :)

[Cup0fTea]

I can confirm that Xiaomi 14 does support avb_custom_key . For now I just successfully flashed and erased avb_custom_key partition. I plan to try resigning HyperOS EU and relock bootlaoader.

❯ fastboot flash avb_custom_key avb_custom_key.img Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032). Sending 'avb_custom_key' (1 KB) OKAY [ 0.001s] Writing 'avb_custom_key' OKAY [ 0.007s] Finished. Total time: 0.041s

❯ fastboot erase avb_custom_key Erasing 'avb_custom_key' OKAY [ 0.010s] Finished. Total time: 0.025s

Did you get the bootloader relock? Your answer is essential for my decision to buy a Xiaomi 14.

[iceQookie]

I want to know realme phones‘ support, maybe it the same as oneplus

[deinferno]

Sony Xperia 10 V (pdx235) can be locked by patching official LineageOS with --clear-vbmeta-flags, LineageOS recovery patching also works allowing sideload custom signed and unsigned (with warning and ofc ruining integrity) update zips.

Stock ROM IMGs can also be resigned and used (didn't try to patch original recovery).

GSIs can also be applied if avb footer from original system.img used as base.

[sequekento108]

I can confirm that Redmi Note 10 Pro and possibly other Qualcomm-based ones do support avb_custom_key.

Has anyone actually tested relocking this device or was it just a test that the avb_custom_key flashes with OKAY's what was done here? It seems like most Xiaomis have a very broken implementation of the avb_custom_key from this repo, but this one is still listed on the supported devices list for some reason - is the reason that its one of the few ones that actually do work, or did just noone check it properly?

[alexceltare2]

I can confirm that Redmi Note 10 Pro and possibly other Qualcomm-based ones do support avb_custom_key.

Has anyone actually tested relocking this device or was it just a test that the avb_custom_key flashes with OKAY's what was done here? It seems like most Xiaomis have a very broken implementation of the avb_custom_key from this repo, but this one is still listed on the supported devices list for some reason - is the reason that its one of the few ones that actually do work, or did just noone check it properly?

Redmi Note 10 Pro is NOT a A/B device, thus it will not work with avbroot.