Missing Partition xbl_b

Help Fairphone 5
, , , ,
1

Hi folks,
Since the day I received my FP5, I’m still not able to update the system software (see Can't use updater for eOS 2.6.3).
As you can see in the linked thread, I tried reinstalling, but no luck.
Yesterday I tried to install LineageOS, but this didn’t work, so I tried CalyxOS, which worked, but I had to change the install script:
Instead of flashing xbl_a and xbl_b images, I had to remove the b-slots, since it always gave the error: Partition not found.
I had a similar error when installing e/OS. The system updater of CalyxOS is also not working, so this is probably related.

Does anyone know, how I can restore the xbl_b and xbl_config_b partitions?

adb shell ls /dev/block/by-name/ just gives me:

ALIGN_TO_128K_1
ALIGN_TO_128K_2
abl_a
abl_b
aop_a
aop_b
apdp
bluetooth_a
bluetooth_b
boot_a
boot_b
catecontentfv
catefv
cdt
connsec
cpucp_a
cpucp_b
ddr
devcfg_a
devcfg_b
devinfo
dip
dsp_a
dsp_b
dtbo_a
dtbo_b
featenabler_a
featenabler_b
fpconfig
fpconfig_persist
frp
fsc
fsg
hyp_a
hyp_b
imagefv_a
imagefv_b
keymaster_a
keymaster_b
keystore
limits
limits-cdsp
logdump
logfs
mdcompress
mdtp_a
mdtp_b
mdtpsecapp_a
mdtpsecapp_b
metadata
misc
modem_a
modem_b
modemst1
modemst2
multiimgoem_a
multiimgoem_b
oembin
persist
qmcs
quantumsdk
qupfw_a
qupfw_b
qweslicstore_a
qweslicstore_b
rawdump
rtice
sda
sdb
sdc
sdd
sde
sdf
secdata
shrm_a
shrm_b
splash
ssd
storsec
study
studybk_a
studybk_b
super
swversion
toolsfv
traceability
tz_a
tz_b
tzsc
uefisecapp_a
uefisecapp_b
uefivarstore
userdata
vbmeta_a
vbmeta_b
vbmeta_system_a
vbmeta_system_b
vendor_boot_a
vendor_boot_b
vm-data
xbl_a
xbl_config_a
2

Even in the script provided by Fairphone to restore the Stock ROM, I had to comment out the regarding lines:

    flash_image_or_abort xbl_a "${IMAGES_DIR}/xbl.elf"
    # flash_image_or_abort xbl_b "${IMAGES_DIR}/xbl.elf"
    flash_image_or_abort xbl_config_a "${IMAGES_DIR}/xbl_config.elf"
    # flash_image_or_abort xbl_config_b "${IMAGES_DIR}/xbl_config.elf"
3

Did you ask in the e/OS forum? And when you bought it from Murena, contact their support to get it fixed, as it seems to be from the beginning and rather an intlation error at their end?

4

No, I didn’t asked in the e/OS forum, since it’s not (solely) an e/OS specific problem, but more a general problem with my phone apparently.
I’m hoping that some dev, or someone with a deeper knowledge regarding android/FP5 partitioning will read this thread and gives me some guidance :smile:
Also I bought the phone directly from Fairphone, so I’ll probably contact the support, but we all know this will take ages :expressionless: