First I only want to rule it out, secondly some comments, like [1], have suggested that the script is failing through failing to connect to fastboot.
So I an referring to this from install page Install /e/OS on a Fairphone FP5 - “FP5”
- Confirm that extracted directory contains following content:
- bin-linux-x86 directory - which contains linux tools including fastboot and adb
- bin-msys directory - which contains Windows tools including fastboot and adb.
- .img files - The .img files that are to be flashed onto the device.
- flash_FP5_factory.sh - The installer script.
On my machine versions are as
$ cd platform-tools
~/platform-tools$ ./fastboot --version
fastboot version 35.0.2-12147458
Installed as /home/iain/platform-tools/fastboot
~$ cd test-fp5/
~/test-fp5$ cd IMG-e-2.5-t-20241108446629-official-FP5/
~/test-fp5/IMG-e-2.5-t-20241108446629-official-FP5$ cd bin-linux-x86/
~/test-fp5/IMG-e-2.5-t-20241108446629-official-FP5/bin-linux-x86$ ./fastboot --version
fastboot version 33.0.3-8952118
Installed as /home/iain/test-fp5/IMG-e-2.5-t-20241108446629-official-FP5/bin-linux-x86/fastboot
To be clear I am only making the point in case that your (successful) unlocking may be happening in a way different from the script.
I don’t know Fairphone in “hands on detail”, but they are different hence the reason for the install method being a Fastboot ROM (all_in_one).
[1]
Edit. If using Windows then this applies
Windows users, we advise to use Git Bash. For more info about Downloads and Installation see Official Documentation
and fastboot will be your equivalent of
/home/iain/test-fp5/IMG-e-2.5-t-20241108446629-official-FP5/bin-msys/fastboot.exe