I have been locked out of my fairphone 5 murena after a failed update

Hi,

I have a really big problem and hope someone can help me. My Fairphone 5 did an update on the eos murena software today and it has locked me out and the only way to get back in is when I would set it to factory settings which I don’t want to do. Has anyone have this problem. I don’t want to lose all my data. I don’t have back-ups (I know, please don’t tell me). I don’t want to lose all my photo’s and signal messages. Help please!

When you start the phone what do you get?

I get a recovery page with options:
reboot system now (doesn’t work)
apply update (doesn’t work)
factory reset (I don’t want to do, because I don’t want to lose my data)
advanced

I also tried connecting it to my laptop to get my data off, but I can’t seem to access it and trying to download ADB, but not getting much further with this

Just a hince.
What happens if at the recovery page you go to apply update and then press volume down.
It could be that it should be volume up.

Nothing happens it stays green on apply from adb. if I click on that nothing happens

Do you get the recovery page on the phone?

Try to reboot into system at least 7 times in a row, it could tbis way fall back to the other slot/previous install, or does it not at all try to reboot into system?

Yes I get the recovery page

Please try @yvmuell advise.

I’ve tried rebooting more than 7 times now. It goes back to the same page saying: Can’t load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.

Which is what I want to avaid.

Have you tried to flash the same update manually from recovery on top?

I see the recovery page and it says in green letters: Can’t load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.

Underneath that it gives two options: Try again or Factory data reset.

I’ve tried again and then I get the same page.

If I then click on the error to go back I can try four options:

Reboot system now

Apply update

Factory reset

Advanced

I tried reboot system now and Apply update, but it brings be back to the same page that I mentioned above

If I go to advance its says:

Enter fastboot (I tried that, nothing)

reboot to bootloader (I tried that, nothing)

reboot to recovery (I tried that, nothing)

mount/unmount system (I tried that, nothing)

view recovery logs (I tried that and I don’t understand)

enable adb ( I tried that and I tried downloading an adb on my laptop, but I can’t quite figure it out)

power off (tried that, brings me back to the same page)

Can somebody please help me???

Fairphone 5 running /e/OS. Recovery reports “Invalid f2fs superblock on /userdata”. Userdata partition exists and is visible in fastboot. Bootloader locked. No factory reset performed.

I need an: official e/OS 2.7 FP5 OTA package. Does anyone know more about this?

Why would you need such an old version?

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?

Can you help?

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?