Hello everyone,
I tried to install the latest official build for Fairphone 5:
IMG-e-3.0.4-a14-20250708507308-official-FP5.zip
The flashing process using the flash_FP5_factory.sh script works fine.
Flashing completes successfully, and I can boot and use the system without issues as long as the bootloader is left unlocked.
However, once I run fastboot flashing lock_critical (which always works) and then fastboot flashing lock, the device shows a “your device is corrupt” message on boot and drops into fastboot mode again. It will not boot into the system anymore.
I always locked the bootloader before the first boot (as recommended) and never booted the system once before locking. I also tried wiping userdata and even using a custom vbmeta.img with flags to disable verification (--disable-verity and --disable-verification) as an alternative approach, but it didn’t help.
I also manually flashed all relevant images (boot, vendor_boot, dtbo, super, vbmeta, etc.) using fastboot flash, and wiped partitions like userdata, system, cache – but the result is the same: locking the bootloader prevents the system from booting.
Locking only the critical partition works, but locking the full bootloader breaks the boot process.
The previous stock manufacturer build had a Security Patch Level of 2025-05-05, and the eOS version I flashed has 2025-06-01.
So anti-rollback should not be the issue here.
Does anyone else have this issue with the current build? Or has someone successfully locked the bootloader after flashing eOS 3.0.4 on the Fairphone 5?
Any suggestions or insights are very welcome.
Best regards,
Niklas