Just a brief hello and thank you! after I succeeded to install this on our local community’s Fairphone 3 today.
A first try on another FP3 (both devices are 2019 FP3s without a plus) kept ending up in Fast Boot Mode after the installation had appeared to be complete. Additional factory resets did not change this pattern on that FP3, unlike on the aforementioned local community FP3. fastboot -w did not work on either device.
Surprisingly, this device now shows an SPL of December, 5th 2025 despite an identical build number.
Additional information: The successful switch was on an FP3 on /e/OS-A15-community version 3.7.1 before, while the failing FP3 was on Android OS Android 13 version FP3.6.A.040.3. While – from my memory – the former at one point after the installation landed in the /e/ recovery and booted after triggering a factory reset from within the recovery, the latter ended up in Fast Boot Mode / AOSP recovery and a factory reset did not break the loop.
I wanted to give it a try but I run into this error while flashing
$ fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img
fastboot: error: Failed to find AVB_MAGIC at offset: 0
$ fastboot --version
fastboot version 37.0.0-14910828
Immediately before that I reflashed the stock ROM version 6.A.040.2 from March. I had tried iode before but always ran into the corrupted device error after locking the bootloader, even though the iode SPL was newer than the one from stock ROM.
Maybe something is wrong with my FP3 that causes the above error…
I think you all are missing a critical flashing step, which I did not document, since the FP 3 partition table changed a while ago in version 4.A.0021.0 and later. e/OS probably did not have this.
We retrofitted a new way of managing the system storage (dynamic partitions). This affects system partition and images only, it does not affect user data.
Go in to fastboot (Vol, power button combo or adb reboot fastboot)
fastboot reboot fastboot this may seem redundant, but there are two different fastboot versions that behave differently.
For your bricked devices, please Flash the stock firmware, then try this. You also need `fastboot delete-logical-partition product_a` after restoring to stock firmware.
The bootloader is lockable in official builds only.
It is mostly dependent on ROM signing signatures. They have to match whatever Fairphone expects/hardcodes into the bootloader. As such, regular community builders like me cannot produce builds with such signatures.
thank you! after I succeeded to install this on our 
