Vendor Name: Google
Device name: Pixel 4a5G
Device CodeName: bramble
Version of /e/OS: e-1.20-t-20240222382228-dev-bramblep
Version of e-Recovery: recovery-IMG-e-1.20-t-20240222382228-dev-bramble
Device is Not rooted
| Pixel 4 (flame) | Pixel 4a5G (bramble) | Pixel 5 (redfin) |
|---|---|---|
| abl (1.0 MB) | abl (1.0 MB) | abl (1.0 MB) |
| aop (205 kB) | aop (197 kB) | aop (197 kB) |
| boot (67 MB) | boot (101 MB) | boot (101 MB) |
| devcfg (53 kB) | devcfg (45 kB) | devcfg (45 kB) |
| dtbo (8.4 MB) | dtbo (17 MB) | dtbo (17 MB) |
| n/a | featenabler (90 kB) | featenabler (90 kB) |
| hyp (528 kB) | hyp (528 kB) | hyp (414 kB) |
| keymaster (270 kB) | keymaster (250 kB) | keymaster (270 kB) |
| modem (85 MB) | modem (153 MB) | modem (85 MB) |
| product (619 MB) | product (594 MB) | product (619 MB) |
| qupfw (74 kB) | qupfw (57 kB) | qupfw (74 kB) |
| system (1.5 GB) | system (1.5 GB) | system (1.5 GB) |
| system_ext (442 MB) | system_ext (473 MB) | system_ext (442 MB) |
| tz (3.2 MB) | tz (3.0 MB) | tz (3.2 MB) |
| uefisecapp (127 kB) | uefisecapp (127 kB) | uefisecapp (127 kB) |
| vbmeta (4.1 kB) | vbmeta (8.2 kB) | vbmeta (4.1 kB) |
| vbmeta_system (4.1 kB) | vbmeta_system (4.1 kB) | vbmeta_system (4.1 kB) |
| vendor (905 MB) | vendor (781 MB) | vendor (905 MB) |
| n/a | vendor_boot (101 MB) | vendor_boot (101 MB) |
| xbl (3.4 MB) | xbl (3.6 MB) | xbl (3.4 MB) |
| ______________________ | ________________________ | ______________________ |
| Locking the bootloader | No binding specification | Locking the bootloader |
| /e/OS documentation | /e/OS documentation | /e/OS documentation |
According to the /e/OS documentation, the bootloader can be locked again on the Google Pixel 4 (flame) and Pixel 5 (redfin) - but not on the Pixel 4a5G (bramble).
The /e/OS*.zip for the Pixel 4a5G (bramble) contains the same part structure / file name as the Pixel 5 (redfin). Nevertheless, the bootloader cannot be locked again according to the /e/OS documentation.
The /e/OS*.zip for the Pixel 4 (flame) does not contain two files (featenabler, vendor_boot), but according to /e/OS documentation the bootloader can still be relocked.
Questions
-
Why can’t the bootloader be relocked on the Google Pixel 4a5G (bramble) with /eOS?
-
Is it just a question of the /e/OS documentation, i.e. has it just been neglected to specify “Locking the bootloader” here as well or is it not possible for the /e/-dev-team to lock the bootloader again for technical reasons?