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 services
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/.
Addition
Pixel Tablet ( tangorpro) Download the [ avb custom key ]
https:// images.ecloud.global/stable/pkmd_pixel
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 :
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
I just did the same as @pfeiffer with my new Pixel 8 but with the latest image: MG-e-2.9-a14-20250321478214-official-shiba.zip
Ran into the exact same situation with getting the error while trying to lock. Also my output of writing the avb_custom_key is the same including the warning.
Did you find a solution to this @pfeiffer ?
Maybe OP Can update Thread title to be “Pixel 7/8 impossible to relock bootloader.”
or I can start a more targeted thread for Pixel 8 and Official.
+1 to other posters with Pixel 8…
Same here…
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.000s]
Writing 'avb_custom_key' (bootloader) avb custom key: flash done
OKAY [ 0.058s]
Finished. Total time: 0.068s
$ fastboot flashing lock
FAILED (remote: 'invalid android images, skip locking')
fastboot: error: Command failed
Bought Pixel 8 for the sole purpose of being able to relock the bootloader.
I tried with 2.7 official and 2.9 official with no lock.
Copying my post from anouther thread.
OK. I think I resolve this problem “skip copying avb_custom_key…”…
Used sudo to run the commands and was able to sudo ./fastboot flash avb_custom_key pkmd_pixel.bin and the fastboot flashing lock command.
Still get warning with Yellow Triangle and warning about “other operating system.”.
I guess this can be expected?
This sounds like one of the Google requirements of verified boot set within AOSP as
Communicate Verified Boot state to users
Verified Boot issues fall into these categories:
. YELLOW: Warning screen for LOCKED devices with custom root of trust set