Fairphone - FP3 - FP3+ Documentation Suggestions

eOSWiki Documentation Suggestions
62

I get an error while flashing with fastboot:

fastboot: error: cannot load ‘/home/hirntot/Schreibtisch/modem.img’: No such file or directory

ERROR: Could not flash the modem_a partition on device

… but the modem.img is not included in the zip file I downloaded. (dev-2.7)

63

Take an older one (more complete), then update to latest

64

An alternative script was proposed here Week 3, 2025: Development and Testing Updates - #2 by Manoj

2 Likes
65

the only one available older one was also not containign that file, i tried before. anyway, @aibd’s link helped. thanks.

1 Like
66

I had a look at the flashing scripts in the /e/OS 2.8 releases for FP3, and I don’t see any command trying to lock the bootloader.
While that might be just me and my untrained eye, it is backed up by the issue description above.

@Manoj … Is there a documentation issue in this regard, or an issue with the current flashing scripts?

67

The instructions in the install guide mention this step

image
image1649×428 64.8 KB

Are you not getting this message while running the script

68

@techminimalism apparently didn’t get this message …

69

Relocking bootloader is possible only on official builds. It does not work on community builds

70

Would it be possible to add such a disclaimer on the install instructions, people are not aware of that.

Would be also great to have it for other devices.

2 Likes
71

I was using the script of an Official build. Specifically, IMG-e-2.8-t-20250219470165-official-FP3.

image

1 Like
72

A disclaimer has been added on the install guides specifically mentioning that bootloader locking is not available for community builds.

1 Like
73

Hi , Question from one of my client with FP3 ( which I don’t own )

Is there an official upgrade path from 1.20-S-stable to 2.X-T-official ?

If not , do some of you dirty flash it with success ?

74
  • yes, use the install script of latest version (S,T,U) → it will erase user data on the phone.
  • one can try to modify the script to not format data (CLEAN_FLASH=true to false).
    (i could share a modified one)

#!/usr/bin/env bash

Target device info

PRODUCT=“Fairphone 3”
PRODUCT_ID=“FP3”

Target Flashing Images info

FLASH_AB_FW_IMGS=“modem sbl1 rpm tz devcfg dsp aboot mdtp lksecapp cmnlib cmnlib64 keymaster”
FLASH_AB_IMGS=“boot dtbo system vbmeta vendor”
FLASH_A_IMGS=“userdata”

Target flash process behavior

CLEAN_FLASH=true
VIRTUAL_AB=true

source factory.common

Common flashing function

flash_factory

No update possible /e/ OS v.1.14

FP3 shows no OTA update since v1.13

75

1.20-s-stable is marked as upgradable on the OTA server, so upgrading should work via the updater.
The next available build from there would be 2.4.1-t-official, but newer builds are available, too.

76

@freechelmi if not already did, try to clean the updater app cache

1 Like
77

Well it seems this OTA upgrade is not possible :

due to the service outage that the service has faced, versions older than 2.2 were affected and that is why there is no option to update in settings > updates.

is there " local update " on 1.20-S ? I don’t think so …

78

Where do you quote this from? This was true for a while after the outage.

But if you look at the dates of the last S, R and Q builds now, the /e/OS build system (re-)built them quite recently, and they are all marked as upgradable.
This wouldn’t make much sense if the goal would not be to restore the ability to update and upgrade old versions via the updater.

Of course the updater might still fail, there were updater hickups in the past, but I would at least first really try the updater.