Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Supported devices #299

Open
chenxiaolong opened this issue May 31, 2024 · 13 comments
Open

Supported devices #299

chenxiaolong opened this issue May 31, 2024 · 13 comments
Assignees

Comments

@chenxiaolong
Copy link
Owner

chenxiaolong commented May 31, 2024

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

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).

Nothing

Sony

Xiaomi

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 one device (listed above) is known to support it.
@PsikoBlock
Copy link

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

@chenxiaolong
Copy link
Owner Author

Thanks, added!

@joeyoropesa-dev
Copy link

So, Xiaomi cannot use selfsigned platform keys?

@pixincreate
Copy link

So, Xiaomi cannot use selfsigned platform keys?

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

@joeyoropesa-dev
Copy link

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
Copy link

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
Copy link
Owner Author

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
Copy link

image

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

@pascallj
Copy link
Contributor

image

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
Copy link

alexceltare2 commented Nov 9, 2024

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

@fuengfah
Copy link

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?

LittleChest added a commit to OctopusROM/device_xiaomi_sm8250-common that referenced this issue Nov 17, 2024
* Most Xiaomi devices do not support avb_custom_key.
* chenxiaolong/avbroot#299 (comment)
LittleChest added a commit to OctopusROM/device_xiaomi_sm8250-common that referenced this issue Nov 18, 2024
* Most Xiaomi devices do not support avb_custom_key.
* chenxiaolong/avbroot#299 (comment)
@crnisamuraj
Copy link

crnisamuraj commented Nov 22, 2024

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
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants