FP6: e/OS flashing executable can't find phone using fastboot on linux (asahi remix)

Help Fairphone 6
, , ,
1

Dear reader,

I am trying to flash e/OS on my Fairphone 6 (FP6) after unlocking the bootloader, but I’m encountering issues with the flashing script.

I’ve bought a FP6 with android to flash e/OS/ to. I’m following the steps on the official website: Install /e/OS on a Fairphone The Fairphone (Gen. 6) - “FP6” . I’ve managed to unlock the bootloader, unlocked critical and it rebooted. Then I went on to re-enable usb debugging and file transfer. I confirmed that the bootloader is now unlocked.

I proceeded with the next step where I run sudo chmod +x flash_FP6_factory.sh && ./flash_FP6_factory.sh. This gets stuck on the following message:

“INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)…
[binfmt_dispatcher] Using FEX with muvm
No IPv6 nameserver available for NDP/DHCPv6”

When I later (chmod +x … needs only to run once) try to just run the script with “sudo ./flash_FP6_factory.sh” I immediately get the following message:

“INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)…
[binfmt_dispatcher] Using FEX with muvm
Error: real user ID or effective user ID is 0

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

adb and fastboot seem to work when I run them manually, they can both find my phone. I’ve tried reinstalling fastboot and adb, and also giving fastboot within bin-linux-x86 executable rights, not sure if this was necessary.

I’ve also tried different data cables and usb ports. The phone shows up in the log when I run “sudo dmesg | grep usb” :

“[15349.572034] usb 3-1: new high-speed USB device number 48 using xhci_hcd
[15349.760136] usb 3-1: New USB device found, idVendor=18d1, idProduct=d00d, bcdDevice= 1.00
[15349.760152] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[15349.760156] usb 3-1: Product: Android
[15349.760160] usb 3-1: Manufacturer: Google
[15349.760163] usb 3-1: SerialNumber: myserialnumber”

Are there any oversights in my method? What steps could I try to make the .sh file connect to the phone?

Excuse my very verbose question, linux and flashing are both new to me so I’m not 100% sure what to show you. Thanks in advance.

2

Hello and welcome! Have you tried running the script without sudo?

Edit 1: After reading it again, it could also be that you are not in fastboot. If the phone has booted into the OS, you should be able to run adb reboot bootloader to enter it.

Edit 2: And as a safe reminder, do not relock the bootloader if the security patch of e/OS is lower than that of your current OS. You can check that after the flash by running the command fastboot flashing get_unlock_ability. If it returns 1, it should be doable.

3

I resolved the problem by making a simlink between the fastboot in bin-linux-x86 and fastboot from my package manager in /usr/bin/:

$ ln -s /usr/bin/fastboot bin-linux-x86/fastboot

then for good measure (not sure if necessary), I renamed the fastboot exe within the bin-linux-x86 folder to something else. This way, the flashing script would use the version of fastboot compatibale with my aarch64 machine.

1 Like
4