/e/OS does not support relocking in general, but only in exception for a few devices.
1 Like
What I mean by that is there seems to be a willingness to do it (as opposed to e.g. Lineage where the devs have stated they have no interest in supporting relocking). And asking if there’s a technical reason for not having it on most Pixels and OPs or if it’s just a matter of nobody having done it (yet).
The list is outdated. At least the flowing official devices are missing:
- Google Pixel 7
- Google Pixel 8
- Google Pixel Tablet
- Murena One
- Murena Two
- Both terracube 2e
Due to the official documentation the bootloader of this devices can be locked after installation.
you are probably right, it is possible that it is outdated, you are welcome to update it as you are sure of your informations …,
1 Like
Pixel 7
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
2.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
Source: Install /e/OS on a Google Pixel 7 - “panther”
Pixel 8
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
2.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
Source: Install /e/OS on a Google Pixel 8 - “shiba”
Google Pixel Tablet
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
2.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
Source: Install /e/OS on a Google Pixel Tablet - “tangorpro”
Murena One
This is an official device, but nothing found in the documentation about relocking - proberly outdated.
Murena Two
This is an official device, but nothing found in the documentation about relocking - proberly outdated.
Teracube Teracube 2e (2020)
This is an official device, but nothing found in the documentation about relocking - proberly outdated.
Teracube Teracube 2e (2021)
Locking the Bootloader
Once you have completed the above steps and before rebooting you can lock your Bootloader.
- Boot your device into bootloader if not already there, and plug it to your computer
- Lock the device with the following command
fastboot flashing lock- Approve with
Volume up
- Reboot with
fastboot reboot
Source: Install /e/OS on a Teracube Teracube 2e (2021) - “emerald”
1 Like
The list is a Wiki post.
Every forum user is allowed and very welcome to edit or add information in it to keep it as up to date as possible 
.
The Edit icon button on the bottom right of the post will let you edit, the Edit count icon button on the top right will let you view the history of edits so far.
2 Likes
How about the Google Pixel 8a (akita)?
the answer reading Install /e/OS on a Google Pixel 8a - “akita” instructions.
It does not mention anything about relocking the bootloader on that page, which is why I was asking.
Maybe I miss something, but as I see, this list makes no sense. Why Pixel phones are in the supported block, when there is no e/os official build for them (except Pixel 8) and relocking the bootloader is not possible on devices with non-official build?
Only the intersection of the set of devices in the positive list and the set of devices with an official build could be included in the positive list.
Because when the checks were done (dates are given), community builds could be relocked, too. This was changed in /e/OS builds only recently.
The list is a Wiki post, meaning you can edit and correct everything you find wrong in it. Feel free to, it’s the edit button on the bottom right of the post.
1 Like
Hi, thanks for answer. I don’t want to edit the page, as you see I had incorrect info.
Where is the howto for relocking bootloader for community builds?
I saw on a command line install page - for example for Pixel 4 - that page contains bootloader relocking steps, but it is emphasised that it is only for official builds, this is why I curious how to do it for community builds.
Thanks,
bil
Perhaps I could have been clearer, sorry. Let me word it differently …
You can’t relock community builds currently.
You could relock them earlier, before a change in the builds not too long ago started to prevent this.
At the time of the checks in the list relocking community builds was still possible, so the list is now wrong, because so far nobody corrected it.
Ah thanks. Indeed, I interpreted the other way around. Probably my bad, my english is not so good.
You wrote: “This was changed in /e/OS builds only recently.”
I would be interested whether it was because of lazyness/missing resources or intentional change.
My only reason for digging into this topic is losing Revolut app, which happened only few days ago (TBH I was expecting it). According to the news, it will be fixed in new e/os version, but will work only where bootloader can be re-locked and this is true only for very few devices.
This is not what i have read…
Should be fixed also in builds for the community !
Hi, check this:
https://community.e.foundation/t/week-26-2025-development-and-testing-updates/71070/12?u=bil
…but we will see.
1 Like