Issues flashing latest e/os on Fairphone 5

Hello,
I aquired my phone some days ago and waited for the new release.
I followed the installation guide.
https://doc.e.foundation/devices/FP5/install
db devices
List of devices attached
XXXXXX device
adb reboot bootloader
astboot flashing unlock
OKAY [ 0.035s]
Finished. Total time: 0.035s
fastboot flashing unlock_critical
OKAY [ 0.035s]
Finished. Total time: 0.035s
fastboot devices
XXXXXX fastboot
But chmod +x flash_FP5_factory.sh && ./flash_FP5_factory.sh ended with an error message:
Setting current slot to ‘a’ FAILED (remote: ‘Unable to set slot’)
fastboot: error: Command failed

The full output can be seen here:
https://gist.github.com/helmchenlord/f1fd183e040a9998f1c928f9f2f05a1f

Now my device reboots into bootloader no matter what option I choose.
It shows:
FastBoot Mode
Product_Name - FP5
Bootloader Version - FP5.TT3M.A.109.20230928
Baseband Version - 13
Serial Number
Secure Boot - Yes
IMEI
Memory Model
Memory Size
Device State - unlocked

Selecting recovering mode shows eos recovering screen
From here I managed to get the recovery.log from the device with adb:
[ 0.000685] I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 0.000714] recovery filesystem table
[ 0.000717] =========================
[ 0.000719] 0 /system ext4 system_b 0
[ 0.000720] 1 /system_ext ext4 system_ext_b 0
[ 0.000722] 2 /product ext4 product_b 0
[ 0.000723] 3 /vendor ext4 vendor_b 0
[ 0.000724] 4 /odm ext4 odm_b 0
[ 0.000725] 5 /metadata ext4 /dev/block/by-name/metadata 0
[ 0.003569] 6 /mnt/vendor/persist ext4 /dev/block/bootdevice/by-name/persist 0
[ 0.005488] 7 /data f2fs /dev/block/bootdevice/by-name/userdata 0
[ 0.007934] 8 /misc emmc /dev/block/bootdevice/by-name/misc 0
[ 0.010860] 9 /storage/sdcard1 vfat /devices/platform/soc/8804000.sdhci/mmc_host* 0
[ 0.010870] 10 /storage/sdcard1 vfat /devices/platform/soc/1da4000.ufshc_card/host* 0
[ 0.010874] 11 /storage/usbotg vfat /devices/platform/soc/.ssusb/.dwc3/xhci-hcd..auto 0
[ 0.010878] 12 /vendor/firmware_mnt vfat /dev/block/bootdevice/by-name/modem_b 0
[ 0.015002] 13 /vendor/dsp ext4 /dev/block/bootdevice/by-name/dsp_b 0
[ 0.016876] 14 /vendor/bt_firmware vfat /dev/block/bootdevice/by-name/bluetooth_b 0
[ 0.018819] 15 /mnt/vendor/qmcs vfat /dev/block/bootdevice/by-name/qmcs 0
[ 0.021038] 16 /tmp ramdisk ramdisk 0
[ 0.021192]
[ 0.021456] I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 0.022420] I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 0.023290] I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 0.024771] Loading make_device from librecovery_ui_ext.so
[ 0.025760] I:vkeys: could not open /sys/board_properties/virtualkeys.STM VL53L1 proximity sensor
[ 0.026169] I:Brightness: 2047 (50%)
[ 0.031227] Display Mode 0 resolution: 1224 x 2700 @ 60 FPS
[ 0.031265] Choosing display mode #0
[ 0.031342] Allocating buffer with resolution 1224 x 2700 pitch: 4992 bpp: 32, size: 13479936
[ 0.031401] Framebuffer of size 13479936 allocated @ 0x75a15cb000
[ 0.031445] Allocating buffer with resolution 1224 x 2700 pitch: 4992 bpp: 32, size: 13479936
[ 0.031491] Framebuffer of size 13479936 allocated @ 0x75a08f0000
[ 0.121931] erasing_text: en (488 x 48 @ 712)
[ 0.124052] no_command_text: en (560 x 48 @ 712)
[ 0.125868] error_text: en (472 x 48 @ 712)
[ 0.150801] I:Starting recovery (pid 388) on Thu Jan 1 00:08:32 1970
[ 0.150816]
[ 0.150840] I:locale is [en-US]
[ 0.152133] SELinux: Loaded file_contexts
[ 0.153651] [libfs_mgr]Invalid f2fs superblock on ‘/dev/block/bootdevice/by-name/userdata’
[ 0.153960] recovery: [libfs_mgr]Failed to mount /data: File exists
[ 0.153978] recovery: [libfs_mgr]Failed to mount for path [/data]
[ 0.245414] stage is
[ 0.245463] reason is
[ 0.249568] SELinux: Loaded file_contexts
[ 0.249910] I:[libfs_mgr]dt_fstab: Skip disabled entry for partition vendor
[ 0.272509] emulated failed to mount /dev/block/bootdevice/by-name/userdata on /mnt/staging/emulated: Invalid argumentI:VolumeManager initialized
[ 0.284137]
[ 0.284160]
[ 0.291639]
[ 0.340146] >
[ 207.973755] Enabled ADB.

I hope you can help, thank you.

What’s the output of
fastboot getvar all
in fastboot mode (which your device is anyway)?
Did you try to install the system via ./flash_FP5_factory.sh again?

I managed to install by activating adb from recovering mode and then fastboot. After running ./flash_FP5_factory.sh again it finished without any errors.

1 Like

Hello,

I get the same error above and the install is now completed with status 3
Installation aborted.

Enabled ADB:

Now send the package you want to apply
to the device with ¨adb sideload < filename>¨

The FP5 ROM needs fastboot to run the installer script flash_FP5_factory.sh found when you unzip the downloaded ROM.

Note this is a different device FP3 but shows the idea

The regular ROM from the install page requires Fastboot mode before you can run the supplied script.