Command line install of IMG-e-2.6.3-u-20241218455570-community-FP3.zip

[Mothboy]

Mothboy@fedora:~/Downloads/IMG-e-2.6.3-u-20241218455570-community-FP3$ chmod +x flash_FP3_factory.sh && ./flash_FP3_factory.sh

*** Fairphone 3 flashing script ***

INFO: The procedure will start soon. Please wait…
Note that this will detect and flash only on FP3 or FP3+ devices.
INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)…
INFO: One Fairphone 3 in fastboot mode found (serial number: A209JH7E0201).

WARNING: Flashing this image wipes all user data and settings on the phone.
Are you sure you want to wipe data and continue?

Type “Yes” (case sensitive) and press enter to wipe data and continue. Else, just press enter: Yes

WARNING: You typed “Yes”, proceeding with data wipe.
fastboot: error: cannot load ‘/home/Mothboy/Downloads/IMG-e-2.6.3-u-20241218455570-community-FP3/modem.img’: No such file or directory

ERROR: Could not flash the modem_a partition on device A209JH7E0201.

ERROR: Please unplug the phone, take the battery out, boot the device into
ERROR: fastboot mode, and start this script again.
ERROR: (To get to fastboot mode, press Volume-Down and plug in the USB-C)
ERROR: (cable until the fastboot menu appears.)

ERROR: Aborting now (press Enter to terminate).^C
Mothboy@fedora:~/Downloads/IMG-e-2.6.3-u-20241218455570-community-FP3$

This is what i get when is try to install Android 14 via the command line. I think something is missing in the install file.
I can install the Android 13 official whitout a problem but the community Android 14 always give the above error.

[aibd]

@Mothboy

fastboot: error: cannot load ‘/home/Mothboy/Downloads/IMG-e-2.6.3-u-20241218455570-community-FP3/

Please can you ls -al the contents of the extracted folder, or use a file manager, does modem.img appear to be missing ??

and / or did you check the sha256sum of your download ?

@aibd

Updated method, this image is of the unzipped folder extracted from IMG-e-1.10-s-20230412278810-stable-FP3.zip, May 2023.

[piero]

hello @Mothboy

@Mothboy

I can install the Android 13 official whitout a problem but the community Android 14 always give the above error.

what is the current version installed ?

[HOWTO] Give complete /e/OS version info easily for support, answers, comparison etc

If you read just the start of this text because it gets cited in the forum: There are screenshots here, please have a look at them before assuming you know what this is about. Thank you! As they say, every hint has its history . Where were we? Ah, yes … You are running /e/OS on your device and want to give info about your version to get support, or a simple answer to a question, or anybody else to confirm whether they can observe the same behaviour you observe? Sure … Your device will …

[AnotherElk]

@AnotherElk

I had a quick look at IMG-e-2.6.3-u-20241218455570-community-FP3.zip (available here), considering a new install from scratch instead of staying on Android 13 (T) for now (which I’ve done, see post before) or doing a “dirty” upgrade without wiping user data …

There are fewer partitions to flash here than previously on Android 13 (T).
However, the install script seems to attempt to flash more partitions than are available to flash, and it seems to be set up to abort with a failure if it can’t flash a partition.

I feel neither confident about the number of partitions nor about the probability of the install script running through successfully without editing it beforehand.

Can anybody confirm that a new install from scratch of IMG-e-2.6.3-u-20241218455570-community-FP3.zip actually works?

Guess not, then.
You could compare the images in the ZIP file with the images the script is trying to flash and delete or comment out the script lines trying to flash images which aren’t there.

The overall size of the data still checks out compared to prior builds, so it could well be nothing is really missing, just that the partitions and what they contain got rearranged and the script didn’t get adapted accordingly, but I don’t know.

Pinging @Manoj … IMG-e-2.6.3-u-20241218455570-community-FP3.zip seems to fail to install via command line.

[Mothboy]

Checksum is OK.
Mothboy@fedora:~/Downloads$ md5sum IMG-e-2.6.3-u-20241218455570-community-FP3.zip
262cc1f3c022e965bd192ddc65844699 IMG-e-2.6.3-u-20241218455570-community-FP3.zip

These are the files and folders in the unzipped IMG-e-2.6.3-u-20241218455570-community-FP3

[aibd]

I see no recent change in the master flash_FP3_factory.sh so I assume the script will attempt

  flash_image_ab_or_abort "${sn}" modem "${IMAGES_DIR}/modem.img"
  flash_image_ab_or_abort "${sn}" sbl1 "${IMAGES_DIR}/sbl1.img"
  flash_image_ab_or_abort "${sn}" rpm "${IMAGES_DIR}/rpm.img"
  flash_image_ab_or_abort "${sn}" tz "${IMAGES_DIR}/tz.img"
  flash_image_ab_or_abort "${sn}" devcfg "${IMAGES_DIR}/devcfg.img"
  flash_image_ab_or_abort "${sn}" dsp "${IMAGES_DIR}/dsp.img"
  flash_image_ab_or_abort "${sn}" aboot "${IMAGES_DIR}/aboot.img"

  flash_image_ab_or_abort "${sn}" boot "${IMAGES_DIR}/boot.img"
  flash_image_ab_or_abort "${sn}" dtbo "${IMAGES_DIR}/dtbo.img"
  flash_image_ab_or_abort "${sn}" system "${IMAGES_DIR}/system.img"
  flash_image_ab_or_abort "${sn}" vbmeta "${IMAGES_DIR}/vbmeta.img"
  flash_image_ab_or_abort "${sn}" vendor "${IMAGES_DIR}/vendor.img"
  flash_image_ab_or_abort "${sn}" mdtp "${IMAGES_DIR}/mdtp.img"
  flash_image_ab_or_abort "${sn}" lksecapp "${IMAGES_DIR}/lksecapp.img"
  flash_image_ab_or_abort "${sn}" cmnlib "${IMAGES_DIR}/cmnlib.img"
  flash_image_ab_or_abort "${sn}" cmnlib64 "${IMAGES_DIR}/cmnlib64.img"
  flash_image_ab_or_abort "${sn}" keymaster "${IMAGES_DIR}/keymaster.img"

from your image we can see why it always fails and aborts at the first line.

Is just as said

@AnotherElk

the install script seems to attempt to flash more partitions than are available to flash

A case for Report an issue

[piero]

IMG-e-2.5-t-20241111446827-community-FP3.zip

[jcerdan]

Hi,

I have exactly the same problem.
Have you reported the issue (so I don’t create a new one for the same…)?

Best regards,

[Mothboy]

I didn’t report the issue at the moment, so feel free to report it.
I don’t have a Gitlab account.

[jcerdan]

Hi,

I have reported the issue:

/e/OS build Image U community lacks some files, impossible to install (#8468)...

[piero]

for a new device, i would recommand to use the most complete/recent T based
IMG-e-X.X-t..........FP3.zip,
installed by using the included script…

then an upgrade to U using the latest OTA file
e-X.X-u..........FP3.zip
installed by recovery and adb sideload

.

only difference between
the IMG-e-..............FP3.zip and the e-.............FP3.zip
from the same build
is that the e-.............FP3.zip don’t embed any userdata.img to replace the existing one
so e-.............FP3.zip preserve the /data partition

[Manoj]

@Manoj

Some user with FP3 devices have reported an issue with the vbmeta.img file being missing. The issue is the /e/OS FP3 u build fetches its device files from the lineage site and the vbmeta is missing upstream.

If interested in using a script to complete the installation please check the linked post.

[Mothboy]

Downloaded IMG-e-2.7-u-20250110460550-community-FP3 and tried to install it but it gives the same error ( see my first post above) as the IMG-e-2.6.3-u-20241218455570-community-FP3.
Opened the flash_FP3_factory.sh from the IMG-e-2.6.3-u-20241218455570-community-FP3 image in my texteditor, deleted the content and copied the script code into the file as mentioned.

Did the install via the command line and it worked flawlessly.
Rebooted phone and installed the 2.7 update directly.

@Manoj Thanks for giving a quick solution and thanks to your developer.