First of I am pretty sure FP5 has vendor updates from the existence of vendor_boot.img to download from LO. here
I am not sure about the firmware.
Any of you know if the firmware on Fairphone 5 is included on vendor image, or included in the fashable zip separately?
vendor and vendor_boot is neither firmware or from the vendor
but yes, LineageOS for FP5 does include firmware updates and is currently using FP5.UT20.B.041.20240624
LineageOS also includes firmware for the FP4, and FP3.
1 Like
Thank you for the answer.
I ran “payload-dumper-go -l” on Linage zip and this is the list of images it contains for the interested:
abl (156 kB)
aop (209 kB)
bluetooth (3.5 MB)
boot (101 MB)
cpucp (188 kB)
devcfg (57 kB)
dsp (67 MB)
dtbo (25 MB)
featenabler (90 kB)
hyp (3.7 MB)
imagefv (61 kB)
keymaster (270 kB)
modem (189 MB)
multiimgoem (16 kB)
odm (1.6 MB)
product (1.7 GB)
qupfw (57 kB)
shrm (49 kB)
studybk (246 kB)
system (1.1 GB)
system_ext (525 MB)
tz (3.8 MB)
uefisecapp (127 kB)
vbmeta (8.2 kB)
vbmeta_system (4.1 kB)
vendor (964 MB)
vendor_boot (101 MB)
xbl (3.7 MB)
xbl_config (229 kB)
This is a bit different then the FairphoneOS image
they are the same just have different names: the LineageOS images and the Fairphone flashing script uses the partition names, but the Fairphone image uses custom names
for example, here is the mapping for FP3:
NON-HLOS.bin modem.img
sbl1.mbn sbl1.img
rpm.mbn rpm.img
tz.mbn tz.img
devcfg.mbn devcfg.img
adspso.bin dsp.img
lksecapp.mbn lksecapp.img
cmnlib_30.mbn cmnlib.img
cmnlib64_30.mbn cmnlib64.img
km4.mbn keymaster.img
emmc_appsboot.mbn aboot.img
1 Like
OK, got it.
Some of the images name usage is obvious, others not.
For my curiosity, do you have perchance a list that describes what each partition is? (whether in fairphoneOS or Lineage).
Or what do I need to search will do.
Thank you.