/e/OS installation problems on FP6

/e/OS Devices Fairphone
,
1

I have been following the installation instructions for my new Fairphone 6, all has gone well until it is time to run the script using

chmod +x flash_FP6_factory.sh && ./flash_FP6_factory.sh

and i get the following error

chmod +x flash_FP6_factory.sh && ./flash_FP6_factory.sh

INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)...
factory.common: line 78: /home/dobbo/Downloads/IMG-e-3/bin-linux-x86/fastboot: Permission denied

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]:

Using fastboot devices, I can see the device in fastboot mode however the install script does not seem to be able to detect it.

I have also tried running the install script as sudo, to no avail.

Any advice?

2

With apologies for such a simple suggestion, have you tried using different USB cables, or different ports? I’ve encountered a number of weird problems that were fixed this way. Worth a shot if you haven’t tried it!

2 Likes
3

I did try this, originally I used a USB-C to USB-C cable and I also tried using a USB-A to C cable too, no luck :frowning:

I’m currently downloading the build again to see if something was corrupted in my original download

4

Make sure you have the latest Linux ADB & Fasboot drivers on your P:

sudo apt-get install adb fastboot

If the version is still not enough up to date for the Fairphone 6, try this package:

sudo apt-get install android-tools-adb android-tools-fastboot
1 Like
5

This instance of fastboot is perhaps not executable. Edit strange use of “perhaps”, better “not executable or otherwise wrong”; please check if is is marked executable, change if not:

$ cd FP6/IMG-e-3.0.2-a15-20250627504414-official-FP6/bin-linux-x86/
$ ls -l
-rwxr-xr-x   e2fsdroid
-rwxr-xr-x   fastboot
drwxr-xr-x   lib64
-rwxr-xr-x   make_f2fs
-rwxr-xr-x   make_f2fs_casefold
-rwxr-xr-x   mke2fs
-rwxr-xr-x   mke2fs.conf
-rwxr-xr-x   sload_f2fs
-rw-r--r--    source.properties

… or a fresh download may not have the issue.

1 Like
6

This was the solution. I checked for the permissions of these files and they were not executable. A simple chmod +x solved this

7

I am however now having another problem, the flashing of the ROM seems to be stuck at the first step,

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: 1be3fe07).
Info: Your phone is in regular bootloader mode.
Sending 'bluetooth_a' (812 KB)
8

factory.common: line 78 contains this “bundled” use of fastboot

$("${FASTBOOT_BIN}" devices

The problem also occurred here Install e on fairphone 4 - #15 by florent.wehrli. The install seemed problematic even after eliminating that error. (User error ?? – strange “flow” in that thread ??)

At your new “fail point” the actual flashing depends on “flash or abort” so there is no error message in the event any one partition fails to flash. Very often a fail to flash like this will resolve on a second or third attempt.

… or something else is wrong ! Did you check the sha256sum of your download?

With two odd errors I would download again and be sure to check the sha256sum.

Meanwhile there have been comments, a forum search of ${FASTBOOT_BIN finds for instance Flashing script wrongfully claims the phone is still locked - #8 by Maryn.

I have to say that I am unsure and this accounts for my uncertainty when I first said

Please, perhaps, also confirm that you had met this in the Requirements section of the install page Install /e/OS on a Fairphone The Fairphone (Gen. 6) - “FP6”.

Check that adb and fastboot are enabled on your PC. If not you can find the setup instructions here

… and the old one … check the full USB chain … best data cable, (for better transmission maybe “high capacity” ??) , generally avoid hubs (unless known and tested) beware the possibility of a hub hidden in a laptop, try to connect the USB cable to the PC/ laptop USB port soldered to the motherboard.

In this post Install e/OS on Fairphone 6 - #62 by poog72 use of correct USB port seemed to correct a problem where the install script started fine but then failed repeatedly to flash one partition and aborted.

9

None of these suggestions helped unfortunately. However I did notice something. In other posts where they posted the log of flashing the ROM, theirs said Your phone is in fastbootD mode whereas mine says Your phone is in regular bootloader mode.

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: 1be3fe07).
Info: Your phone is in regular bootloader mode.
Sending 'bluetooth_a' (812 KB)

Is this normal?

I was also thinking of trying to flash it on a windows PC rather than my Arch Linux laptop to see if this helps.

EDIT : I also checked the sha256sum and it seemed to be correct. The above errors happened with both the official and community builds.

10

The initial echo from “find device” in the script is as you show. The phone is booted into fastbootD during the script run. You could check the script to see the relation as it might correctly appear in the output in case this is a part of the problem.

About the “bundled use of fastboot” I found no helpful fix just pointers.

A different machine is probably a good idea.

11

It would be very interesting to hear @dobbo what you felt was your solution. Many Fairphone install problems which start like this seem to have ended without a documented fix.

12

I would say you need sudo in front of tha chmod… factory.sh

That is the way I did it.

13

To be completely honest I have no idea how this was solved. I used the same Arch linux machine but opened and checked the flash_FP6_factory.sh and factory.common scripts then tried again and it seemed to work no problem.

I did try uninstalling and re-installing the android-tools package however before checking the scripts this seemed to make no difference.

1 Like
14

There is no installation of android tools needed because it is in the zip already

15

I was having this problem (Stuck at “Sending ‘bluetooth_a’ (812 KB)”) when using a cable for charging via USB-C (100 Watt). It worked when I used an USB-C cable for my SSD.