Problem with Fairphone 5 running official /e/OS 2.7 (Android 13).

Using /e/OS Troubleshooting
,
1

Fairphone 5 running official /e/OS 2.7 (Android 13).

Build:
e_FP5-user 13 TQ3A.230901.001 eng.root.20250111.181155

Symptoms:

  • Phone boots to Fairphone logo

  • Then /e/OS (Murena) logo

  • Then returns to recovery

  • Recovery version 2.7

  • Bootloader locked

  • Apply update from ADB is available

I have already made full userdata and metadata images and preserved the encryption metadata.

Can someone provide the correct signed OTA ZIP for recovery sideload, or confirm the correct package and procedure to repair the installation without wiping userdata?

2

I successfully sideloaded the package:

e-2.7-t-20250111460957-official-FP5.zip

The installation completed successfully with:

“Install completed with status 0”

However, after rebooting, the device still does not boot into Android. The boot sequence is:

Fairphone logo → Murena boot animation (bouncing white dot) → repeats several times → returns to recovery.

I also reviewed the recovery logs and found messages indicating:

  • Failed to mount /data

  • Invalid f2fs superblock on userdata

In addition, fsck.f2fs reports that it cannot find a valid F2FS superblock on the userdata partition.

Before attempting the sideload, I created complete images of userdata and metadata partitions and copied the metadata encryption files.

Could you please advise whether there are any further non-destructive recovery options available before considering a factory reset?

4

I’m not confident the fsck route yields anything, the recovery logs an be misleading. One can’t see the non-recovery bootup log. Only if pstore is enabled (you can check this, but usually it’s debug builds that do).

What I’m aware of is users ending up in bootloops when space was scarce. Freeing some up helped then. Is that likely?

1 Like
5

https://ota.ecloud.global/api/v1/FP5/official/

[HOWTO] Upgrade my /e/OS to major Android version without loosing /data