- Vendor Name: Google
- Device name: Pixel 4 (Mod. G020M (Global, International))
- Device CodeName: flame
- Version of Stock which existed previously: 13.0.0 (TP1A.221005.002.B2, Februar 2023)
- My device is Not rooted
Android T (13)
-
recovery-IMG-e-2.1-t-20240605406922-dev-flame.zip
dtbo-e-2.1-t-20240605406922-dev-flame.img
dtbo-e-2.1-t-20240605406922-dev-flame.img.sha256sum
recovery-e-2.1-t-20240605406922-dev-flame.img
recovery-e-2.1-t-20240605406922-dev-flame.img.sha256sum -
Locking the bootloader: 2. Download the avb custom key
Relocking failed (three attempts)
Can’t find valid operating system.
The device will not start.
Locking the bootloader
In /e/OS recovery main screen:
- Select
Advanced - Select
Reboot to bootloader
Once the device is in fastboot mode:
- Verify your PC finds it by typing:
fastboot devices
Tip:* If you see no permissions fastboot while on Linux or macOS, try running fastboot as root.
- Download the avb custom key
- Erase the previous key
fastboot erase avb_custom_key - Flash the new key previously downloaded
fastboot flash avb_custom_key pkmd_pixel.bin - Lock the device
fastboot flashing lock - Use the volume key to select
Lock the bootloader
Reboot the device
- Use power button to
Startthe device
The installation was carried out step-by-step according to the /e/Documentation. Relocking was carried out as described above (quoted from the /e/Documentation)
Relocking failed (three attempts)
The avb custom key blocks the reboot. After I had unlocked the bootloader again, /e/OS-T started without failure.
INFO
Then I installed iodéOS 5.2 (7/2024) on the same device. There, the avb custom key is integrated in the CustomROM and does not have to be installed separately. The Pixel 4 (flame) started flawlessly with iodéOS 5.2 and the bootloader locked again - just as it should be.