-
Notifications
You must be signed in to change notification settings - Fork 42
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
Comments
Custom keys work on Fairphone 4 and 5 with the manufacturer supporting custom ROMs and even selling devices with them preinstalled. |
Thanks, added! |
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) |
Sony Xperia V can be locked again with
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. |
The Pixel 9 series is also compatible, as expected (tested personally). Their AVB structure is completely identical to the Pixel 7 and 8 series. |
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. |
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? |
* Most Xiaomi devices do not support avb_custom_key. * chenxiaolong/avbroot#299 (comment)
* Most Xiaomi devices do not support avb_custom_key. * chenxiaolong/avbroot#299 (comment)
I can confirm that Xiaomi 14 does support ❯ 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
|
Wow! This is great news please keep update or where can I follow you |
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
Nothing
Sony
Xiaomi
Not supported
OnePlus
Xiaomi
avb_custom_key
. Only one device (listed above) is known to support it.The text was updated successfully, but these errors were encountered: