After the web installer didn’t work for me, I did the manual install.
After starting up flash_FP6_factory.sh about a half an hour ago, nothing seems to happen:
chmod +x flash_FP6_factory.sh && ./flash_FP6_factory.sh INFO: You are using a Linux distribution. INFO: Looking for connected device(s)… INFO: One Fairphone 6 in fastboot mode found (serial number: da******). Info: Your phone is in regular bootloader mode. Sending ‘bluetooth_a’ (812 KB)
piero@HP-p6-2038fr:~/Téléchargements/IMG-e-3.2-a15-20251022539003-official-FP6/bin-linux-x86$ ./fastboot --version
fastboot version 33.0.3-8952118
Installed as /home/piero/Téléchargements/IMG-e-3.2-a15-20251022539003-official-FP6/bin-linux-x86/fastboot
piero@HP-p6-2038fr:~/Téléchargements/platform-tools$ ./fastboot --version
fastboot version 36.0.0-13206524
Installed as /home/piero/Téléchargements/platform-tools/fastboot
I would also associate this with (perhaps) something in the USB hardware link.
So perhaps look at the whole USB chain. It has been reported that certain USB will not carry fastboot commands (or complex fastboot commands ??). You will need a good quality (full capacity) data cable, so not a thin, skinny cable. Avoid USB hubs including any USB hub that might be hidden in the PC / laptop; for best results check, if necessary with a manual, that you are connecting to a USB-2 port soldered to the motherboard.
Hello there, I did get into the same situation as kees while trying to flash a Fairphone 5 through the Bash script on a Fedora 43 Workstation system. Before writing how I got around it, I would say that I do not know the implications of what I tryed and therefore I would advise that at least another more experienced user review this before recommending it.
I followed the flashing instructions via command line and got to the point of having the smartphone into bootloader mode, and tryed from there to run the script flash_FP5_factory.sh, however it hangs right at the first file bluetooth_a and never uploads it to the device.
After checking the state of my sistem with fastboot devices command and looking online, I found that the Fairphone 5 should have a “fastbootd” mode: I got into that by booting android, then connecting the smartphone to the PC and running the command adb reboot fastboot.
The “fastbootd” screen is different from the bootloader and from there it is possible, without selecting anything, to run the flashing script and it would upload all the files.
The catch for me was that the latest command of the script failed in this mode, with an error regarding the inability to select partition A.
I manually rebooted the phone into bootloader, and now the fastboot commands succeded even from this mode. So I re-run the entire flashing script, and this time it succeeded all the way through its commands.
The smartphone did automatically reboot into e/OS 3.2 (the latest official I could choose at the time of writing)
Congratulations on your success. Perhaps I could say @procsiab that fastbootd does form a part of the expert install method. However it is not documented here.
Following readers, I would suggest, would need to follow your lead and do some reading in advance as potential paths_to_error differ from more conventional systems with fixed partitions.
I did a ./flash_FP6_factory.sh
and it started immediately downloading files.
At the end I got the following error:
Sending sparse ‘super’ 18/18 (31804 KB) OKAY [ 0.941s]
Writing ‘super’ OKAY [ 0.080s]
Finished. Total time: 121.900s
Erasing ‘misc’ FAILED (remote: ‘Erasing failed’)
fastboot: error: Command failed
ERROR: Could not erase the misc partition on device da4d3846.
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).
I removed the USB cable and tried to reboot into fastboot, however, I saw the fastbootmenu flash by and the phone got into Murena and I got into the reovery window
to be safe and finish the method shared by @procsiab with a success message,
please reboot to bootloader (the first you have) and redo the ./flash_FP6_factory.sh
I;m in the fastboot menu, but the script doesn’t see the phone, although fastboot does
# fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.001s]
Finished. Total time: 0.001s
# ./flash_FP6_factory.sh
INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)…
WARNING: No Fairphone 6 found in fastboot mode.
WARNING: Make sure that a Fairphone 6 is connected.
Do you want to look for a Fairphone 6 again? [(Y)es/(n)o]: n
Retried everything.
Thie ${FASTBOOT_BIN} is called by factory.common but never gets set, I places an echo to display it, but does not display anything, so I explicitly set it, but that made no difference.
If I start flash_FP6_factory.sh when I see results when executing fastboot oem device-info, then the FP6 goes from the fastboot menu to “Press any key to shutdown” in very small characters.
So again I did an `adb reboot fastboot` and now got into the actual fastbootd screen, instead of what I posted yesterday
the flash script script continued as before, including the same error.
And trying to execute it again from the fastboot menu resulted again in Press any key to shutdown”.
After starting again /es/OS started unchanged, all my settings were still there.
The only problems I have with /e/OS is that
I cannot set the screenlock, I found in the forum that it has to do with FRP, so I will have to solve that.
Back in the day FRP would prevent reinstall. Recent user stories (with the current a15 behaviour) have hashtag frp (previously mentioned). One has to go back to working Google Fairphone Android to remove
I got the same problem from my desktop (using front case USB), so I tried from my laptop (with the exact same OS) and it worked perfectly. I think this is related to USB stability, and not at all because of the script.
