Is for this Phone actually not possible to relock the bootloader, because the AVB Key in the manual doesn’t work for me.
Documentation: Info about Google Pixel 4 - flame
I’ve already noticed similar inconsistencies:
Ah i see. Could it be that the AVB custom key only works with the official eOS Build and not with the community version? Then the AVB custom key is a relict of it, because there is only a community version anymore. Is it possible to create a AVB custom key for the community version or how does that work?
Hello , i am new here but know about android OS somewhat . Regarding using AVB custom key for locking the bootloader , the build installed should actually be signed by the private keys corresponding to these avb keys , so verified boot can comapre the OS hash against the set avb key hash.
Therefore the official build avb keys won’t work with the community edition.
So for this to work you can create another set of keys with which you need to sign the build and then create a public key convert it into a AVB public key metadata format ( a bin format).
I personally don’t have an experience in signing builds as the proper steps needs to be followed.
Probably you should contact the community dev who built this and ask him to sign the same.
idealy person compiling the build should sign the build.
There are plenty resources available on the web for signing builds and creating avb public key.
I found an old guide https://xdaforums.com/t/guide-re-locking-the-bootloader-on-the-oneplus-6t-with-a-self-signed-build-of-los.4113743/ but please do your own research before attempting lock on any key.
I share your assumption. In addition, the /e/documentation is not always up to date. At least two other reputable CustomROM distributions allow you to relock the “flame” bootloader.