Pixel 7 impossible to relock bootloader

Hello
I followed the entire /e/os panther installation procedure without any problems, but at the end it was impossible to relock the bootloader on Pixel 7 SKU-GQML3 (after installing e-2.7-u). I get the following problem:
fastboot flashing lock > FAILED (remote: ‘invalid android images, skip locking’)
Maybe the pkmd_pixel.bin file isn’t up to date for the Pixel SKU-GQML3?
Any ideas?

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online servicesphone

It’s strange that an device-specific ‘avb custom key’ of the Google Pixel 8 (shiba), Pixel 7 (panther), Pixel 5 (redfin) is identical to that of the Google Pixel 4 (flame) und Pixel 4 XL (coral):

identical file name, identical download URL

Pixel 7 (panther) Download the [avb custom key ]
https:// images.ecloud.global/stable/pkmd_pixel

Pixel 8 (shiba) Download the [avb custom key ]
https:// images.ecloud.global/stable/pkmd_pixel

Other custom ROM Android distributions designate their ‘avb custom key’ device-specifically and not uniformly like /e/.

1 Like

Addition


Pixel Tablet ( tangorpro) Download the [ avb custom key ]
https:// images.ecloud.global/stable/pkmd_pixel

1 Like

Hello,
good news.
I try to uninstall e-2.7-u community and then install e-2.7-t official. I was able to lock the bootloader as describe installation procedure.

Interesting news!
In the /e/OS documentation there is no mention that the bootloader can only be locked again with the official /e/OS-T version, but not with the /e/OS-T community or /e/OS-U community versions.

I’m having the same issue with my Pixel 8 tying to relock the latest e-2.7-u version.

If another build works, can you reference where to download it ?

@pfeiffer
Try installing /e/OS build :

U official

Locking the bootloader

Download the avb custom key

Thanks for the reply @Xxpsilon, however that is exactly what I did.

I installed: https://images.ecloud.global/official/shiba/IMG-e-2.7-u-20250109460370-official-shiba.zip
Then followed the instructions to lock, overwriting with the avb custom key properly, but when trying to lock I get the error.

During write of the avb_custom_key I do get a warning however, perhaps it is related to that ?

Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 520).
Sending 'avb_custom_key' (0 KB)                    OKAY [  0.001s]
Writing 'avb_custom_key'                           (bootloader) avb custom key: flash done
OKAY [  0.059s]
Finished. Total time: 0.062s

If I need to create a separate issue for this, just let me know.

@pfeiffer
I already wrote above that I find it confusing that one and the same avb_custom_key is used for all Pix/e/l devices. Since I don’t have a Pixel 8 (shiba), I can’t verify the process.

Maybe you can find more help and answer if describe the bug again here … Feedback for v2.7