Repository navigation
Replies: 1 comment
|
Good shout, cheers - it's in now (#140). Device pages say whether the phone itself takes a custom key, next to the bootloader answer, and the ROM rows still say what each ROM's own builds do. Here's the Razer Phone 2, linked to your avbroot report: https://android-rom-compat.peng.ly/devices/razer/phone-2/ Both of your sources went in, plus Google's docs for the Pixels, so 82 phones that still get builds have an answer so far. A "no" comes with a warning where locking bricks the phone, which covers a fair few Xiaomis. Thanks for the idea :) |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
For example, #114 , Razer Phone 2 (aura) supports bootloader relocking, but the two distributions for it do not. However, end users could re-sign the OTA package with their own key by avbroot to enable bootloader relocking.
Device support for bootloader relocking could be collected from device page of former Divestos, and the dedicate issue of avbroot.
All reactions