"No Fairphone 4 found in fastboot mode" error message

croy · January 6, 2025, 12:12am

Process of installing e/OS on FP4. Dell laptop has Fedora 41 on it. Fairphone is ungraded to Andoid 13. Have completed steps through #4 Installing e/OS in below link
https://doc.e.foundation/devices/FP4/install

Have confirmed the following
Device attached and listed, google 18d1:4ee1 (ran command lsusb)
bootloader is unlocked (ran reboot to bootloader, USB-C cord inserted, press vol +)
fastboot_critical enabled (ran adb>fastboot oem device_info)

Inconsistently I see no devices listed or my device (764XXX4d) listed after running adb devices or fastboot devices. The first time I went through the procedure my device was listed both times. This last attempt at installation I sometimes get

CXXX@fedora:~$ adb devices
list of devices attached

CXXX@fedora:~$ fastboot devices
764XXX4d fastboot [where 764XXX4d is my smartphone with FP4 OS on it]

Other times it is flipped, fastboot nothing and adb lists my device. Yes, I do make sure the USB-C cord is securely connected to phone and computer.

Last step I completed was entering
ccXXX_1@fedora: /[file path]$ chmod +x flash_FP4_factory.sh && ./flash_FP4_factory.sh

screen spit out
*** Fairphone 4 flashing script ***
INF: The procedure will start soon. Please wait…
Note that this will detect and flash only n FP4 device.
Info: you are using a Linux distribution.
Info: Looking for connected devices(s)
./flash_FP4_factory.sh: line 40: /home/ccXXX_1/[file path]/fastboot: Permission denied

WARNING: No Fairphone 4 found in fastboot mode.
Warning: Make sure that a Fairphone 4 is connected.

I have tried inserting USB cord in different USB ports on my Dell laptop. Each time I attempted to have terminal “look for a Fairphone 4 again?” by entering Y for yes.

I have tried going through the part of procedure at the link relating to abd devices and fastboot devices (steps 5-10 in “Unlocking the bootloader” section. My phone says

FastBoot Mode
Product Name FP4
Variant - SM_ UFS
Bootloader version -
Baseband Version -
Serial Number - 764XXX4d
Secure Boot - yes
etc
etc
etc
Device State - unlocked

I have spent weeks on this and would very much welcome any assistance in finishing this installation. I have not turned off bootloader. I will not until either eOS installation is done or I just do a system recovery to get back to where I was. . . . Just OS system.
Added Bash history
timedatectl set-local-rtc 1 --adjust-system-clock
exit
sudo dnf install grub-customizer
exit
sudo nano /ect/default/grub
sudo nano /etc/default/grub
sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
sudo grub2-mkconfig -o /boot/grub2/grub.cfg
exit
curl -fsS https://dl.brave.com/install.sh | sh
exit
snap install easy-installer --channel=latest/beta
snapd install easy-installer --channel=lastest/beta
sudo snap install easy-installer --channel=latest/beta
sudo snapd install easy-installer --channel=lastest/beta
sudo dnf install snapd
sudo ln -s/var/lib/snapd/snap /snap
sudo 1n -s/var/lib/snapd/snap /snap
sudo ln -s/var/lib/snapd /snap
ln --help
sudo dnf install snapd
sudo ln -s /var/lib/snapd/snap /snap
sudo snap install easy-installer --beta
sudo ln -s /var/lib/snapd/snap /snap
sudo snap install easy-installer --beta
mediawriter
export PATH= “$HOME/.cache/fedoraproject.org/MediaWriter:$PATH”
sysconfig
/etc/xdg.autostart/mediawriter.desktop
~/.local/share/autostart/mediawriter.desktop
adb devices
/Home/platform-tools/
Home/platform-tools/
/home/platform-tools/ ./adb devices
home/platform-tools/ ./adb devices
cd /home/platform-tools/
cd /home/
dir
/platform-tools$ ./adb devices
/ccoffice_1/platform-tools$ .adb devices
cd /ccoffice_1/
cd…
cd
cd /home/office_1/platform-tools/
cd /home/office_1/desktop/platform-tools/
sudo dnf install gnome-terminal-nautilus
./adb devices
./fastboot devices
adb devices
cd
~/.bashrc
adb devices
fastboot devices
dir
adb
adb reboot bootloader
fastboot flashing unlock
adb reboot bootloader
fastboot flashing unlock_critical
chmod + flash_FP4_factory.sh && ./flash_FP4_factory.sh
chmod + flash_FP4_factory.sh
adb reboot bootloader
fastboot flashing unlock
chmod +x flash_FP4_factory.sh && ./flash_FP4_factory.sh
chmod + flash_FP4_factory.sh && ./flash_FP4_factory.sh
adb devices
iadb devices
adb devices
fastboot devices
adb devices
adb reboot bootloader
fastboot devices
fastboot oem unlock
adb>fastboot getvar unlocked
adb reboot bootloader
fastboot flashing unlock
Fastboot flashing unlock critical
adb>fastboot oem device_info
C:
fastboot oem device-info
fastboot flashing unlock critical
fastboot oem lock
D
fastboot flashing unlock_critical
adb reboot bootloader
adb devices
fastboot devices
lsusb
/etc/udev/rules.d/51-android.rules
/platform_tools/
adb
fastboot devices
adb> fastboot devices
adb> adb devices
sudo fastboot devices
fastboot devices
adb devices
sudo adb devices
sudo
sudo $fastboot devices
fastboot -i 18d1:4ee1
fastboot -i 0x18d1:4ee1
fastboot 18d1:4ee1
fastboot
adb
adb devices
sudo adb devices
sudo devices
abd devices
devices
sudo adb
adb
adb devices
fastboot
fastboot devices
adb devices
adb
adb devices
fastboot
sudo fastboot
sudo
sudo adb
sudo adb devices
adb
adb devices
adb reboot bootloader
adb devices
fastboot devices
adb devices
list devices
lsusb
dmidecode
sudo su
usb-devices | grep -i “imei”
history -a > terminal_history_dir.text
chmod +x flash_FP4_factory.sh && ./flash_FP4_factory.sh
history -a > terminal_history_FP4Dir
sudo dnf install clamav
gio trash ~/.local/share/keyrings
gnome-session-quit --logout

aibd · January 6, 2025, 12:29am

adb and fastboot are different languages.

With your phone in Normal mode or Recovery you can use

adb devices

With the phone in Bootloader or fastboot mode then you use

fastboot devices

When you unlocked the phone USB debugging would have got reset off again, so you would have to go back and do it again.

It has happened that users have confused fastbootd with fastboot – the install script expects the phone in fastboot mode, so your test with

fastboot devices

is the right thing to do.

croy · January 6, 2025, 1:41am

Thank you for the fast reply. What about

"Last step I completed was entering
ccXXX_1@fedora: /[file path]$ chmod +x flash_FP4_factory.sh && ./flash_FP4_factory.sh

screen spit out
*** Fairphone 4 flashing script ***
INF: The procedure will start soon. Please wait…
Note that this will detect and flash only n FP4 device.
Info: you are using a Linux distribution.
Info: Looking for connected devices(s)
./flash_FP4_factory.sh: line 40: /home/ccXXX_1/[file path]/fastboot: Permission denied

WARNING: No Fairphone 4 found in fastboot mode.
Warning: Make sure that a Fairphone 4 is connected."

I tried rebooting phone back into fastboot (power button + volume button) and then ran flash again. Same message or the message wait for device Y or N.

(I saw online that some techies recommended updating drivers for phone through device manager in Windows. Relevant?)

aibd · January 6, 2025, 6:58am

My reply before coffee

Absolutely … Install fastboot drivers.

… and

made me think of

Caution: The default adb installation on OS like Ubuntu can be outdated and can cause errors. We would recommend that linux distribution users ensure they use the installation process given here … and
is “add the path to your PC configuration” done correctly … from
Installing adb and fastboot on a Linux PC

EDIT … but, to satisfy yourself and especially when asking for help always

fastboot devices

at any change you make and show the result if / when you ask again.

However you did manage to unlock … please confirm this

In light of

You also say

Well which … or both (??) … it will help if you show your actual output.

I would suggest that it is not a good way forward to attempt to start the script again if you cannot immediately before get the device to self identify with

fastboot devices

You might possibly have a variation of this Flashing script wrongfully claims the phone is still locked - #15 by Maryn which was part of my thinking behind having adb / fastboot correctly installed.

croy · January 7, 2025, 1:22am

I again see USB debugger on, OEM unlocking says boatloader is already unlocked. I found adb devices produces no devices found if I leave the USB transfer as no transfer. I changed it to TRANSFER DATA and then the adb listed my phone under LIST OF DEVICES.

New error messages
Entered into terminal
adb reboot bootloader [Got out]
No devices/ emulators found

Also went back to verify adb devices by entering
Adb devices

Daemon not running; starting now at tcp:5037
Daemon started successfully
List of devices attached
123456(my device) device

Attached is history. I keep trying to put phone in fastboot mode and nothing seems to work … Yet bootloader says Fastboot mode? See pic

—Image removed—

Part of history log (don’t see a way to attach text file… Wish there was a way to list terminal commands and results that were produced.)

172 adb devices
173 fastboot devices
174 adb reboot bootloader
175 fastboot devices
176 adb devices
177 isusb
178 lsusb
179 adb kill-server
180 adb start-server
181 lsof -i :5037
182 lsusb
183 adb reboot bootloader
184 adb
185 fastboot flashing unlock
186 fastboot devices
187 adb devices
188 adbd
189 adb devices
190 adb>fastboot oem device_info
191 adb…
192 adb>
193 fastboot getvar unlocked
194 fastboot devices
195 adb devices
196 fastboot devices
197 adb reboot bootloader
198 android-sdk-platform-tools-common
199 history > history.txt

Last stand

croy · January 7, 2025, 1:24am

I again see USB debugger on, OEM unlocking says boatloader is already unlocked. I found adb devices produces no devices found if I leave the USB transfer as no transfer. I changed it to TRANSFER DATA and then the adb listed my phone under LIST OF DEVICES.

New error messages
Entered into terminal
adb reboot bootloader [Got out]
No devices/ emulators found

Also went back to verify adb devices by entering
Adb devices

Daemon not running; starting now at tcp:5037
Daemon started successfully
List of devices attached
123456(my device) device

Attached is history. I keep trying to put phone in fast ook mode and nothing seems to work …

—image removed—

Part of history log (don’t see a way to attach text file… Wish there was a way to list terminal commands and results that were produced.)

172 adb devices
173 fastboot devices
174 adb reboot bootloader
175 fastboot devices
176 adb devices
177 isusb
178 lsusb
179 adb kill-server
180 adb start-server
181 lsof -i :5037
182 lsusb
183 adb reboot bootloader
184 adb
185 fastboot flashing unlock
186 fastboot devices
187 adb devices
188 adbd
189 adb devices
190 adb>fastboot oem device_info
191 adb…
192 adb>
193 fastboot getvar unlocked
194 fastboot devices
195 adb devices
196 fastboot devices
197 adb reboot bootloader
198 android-sdk-platform-tools-common
199 history > history.txt

aibd · January 7, 2025, 8:52am

So this sounds like you are interrogating the phone in Normal mode, ok.

Back to basics! There are two more modes where the user has to have full control.

Recovery
Bootloader or Fastboot mode.

Also one has to learn to navigate the Menus withinin these modes.

Your image is headed Recovery mode. Does this mode “self identify” with adb devices ?

Here is an image taken from the Fairphone forum of Bootloader mode.

If you find this screen, does the phone “self identify” with fastboot devices ?

It should be possible to do this.

Does this demo help?

Here is Fairphone forum answer, to a question similar to yours: Fairphone 4 Bootloader doesn't communicate anymore with PC - Fairphone 4 - Fairphone Community Forum

msp · January 7, 2025, 9:55am

Mathematical spoken

recovery mode ≠ fastboot

croy · January 7, 2025, 3:02pm

did get fastboot to show devices by running
sudo /[file path]/fastboot devices

Also showed my device name by running lsusb and saw my device name and then (FASTBOOT)

To get this to work I had to modify udev rules through commands

echo ‘SUBSYSTEM==“usb”, ATTR{xxxx:d00d}==“xxxx:d00d”, MODE=“0666”, GROUP=“plugdev”’ | sudo tee /etc/udev/rules.d/51-android.rules
[sudo] password for ccoffice_1:
SUBSYSTEM==“usb”, ATTR{xxxx:d00d}==“xxxx:d00d”, MODE=“0666”, GROUP=“plugdev”
ccoffice_1@fedora:~$ sudo udevadm control --reload-rules
ccoffice_1@fedora:~$ sudo udevadm trigger
ccoffice_1@fedora:~$ sudo fastboot devices
sudo: fastboot: command not found
ccoffice_1@fedora:~$ sudo /home/ccoffice_1/platform-tools/fastboot devices
7xxxxx4d fastboot

and reapplied changes by reboot to bootloader/fastboot

END copy of commands

Most recent attempt at running flash since device in fastboot

ccoffice_1@fedora:~/FP4_eOs_SP110824_Of446629_img$ sudo chmod +x flash_FP4_factory.sh && .flash_FP4_factory.sh
[sudo] password for ccoffice_1:
bash: .flash_FP4_factory.sh: command not found…
ccoffice_1@fedora:~/FP4_eOs_SP110824_Of446629_img$ sudo chmod +x flash_FP4_factory.sh && ./flash_FP4_factory.sh

*** Fairphone 4 flashing script ***

INFO: The procedure will start soon. Please wait…
Note that this will detect and flash only on FP4 device.
INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)…
./flash_FP4_factory.sh: line 40: /home/ccoffice_1/FP4_eOs_SP110824_Of446629_img/bin-linux-x86/fastboot: Permission denied

WARNING: No Fairphone 4 found in fastboot mode.
WARNING: Make sure that a Fairphone 4 is connected.

Do you want to look for a Fairphone 4 again? [(Y)es/(n)o]: y
./flash_FP4_factory.sh: line 40: /home/ccoffice_1/FP4_eOs_SP110824_Of446629_img/bin-linux-x86/fastboot: Permission denied

WARNING: No Fairphone 4 found in fastboot mode.
WARNING: Make sure that a Fairphone 4 is connected.

Do you want to look for a Fairphone 4 again? [(Y)es/(n)o]: y
./flash_FP4_factory.sh: line 40: /home/ccoffice_1/FP4_eOs_SP110824_Of446629_img/bin-linux-x86/fastboot: Permission denied

WARNING: No Fairphone 4 found in fastboot mode.
WARNING: Make sure that a Fairphone 4 is connected.

Do you want to look for a Fairphone 4 again? [(Y)es/(n)o]: y
./flash_FP4_factory.sh: line 40: /home/ccoffice_1/FP4_eOs_SP110824_Of446629_img/bin-linux-x86/fastboot: Permission denied

WARNING: No Fairphone 4 found in fastboot mode.
WARNING: Make sure that a Fairphone 4 is connected.

Do you want to look for a Fairphone 4 again? [(Y)es/(n)o]:
END copy of commands

chance adb still being blocked by phone USB file transfer having to manually be put to DATA TRANSFER? (also, any way to blot out my device info from previous posts in this thread??) What other permission keep Fedora 41 from finding FP4?

croy · January 7, 2025, 3:50pm

BTW I did get my device listed when I ran adb, when USB transfer on phone is set to data transfer. Would it help to have adb ran in sudo?

piero · January 7, 2025, 3:56pm

Hello @croy, welcome to this forum…

have you checked :

fastboot oem device-info

also have a try using another computer…

aibd · January 7, 2025, 4:26pm

You say:

:~$ sudo fastboot devices
sudo: fastboot: command not found
~$ sudo /home/ccoffice_1/platform-tools/fastboot devices
7xxxxx4d fastboot

So this tells us that you do not have the benefit of platform-tools in your $PATH.

Please can you read this Installing adb and fastboot on a Linux PC, and I suggest you Add the path to you PC configuration. This was found to be necessary for some to help deal with

The “non function” of bin-linux-x86/fastboot is mentioned in the above “Flashing script wrongfully …” thread, now you reveal

./flash_FP4_factory.sh: line 40: /home/ccoffice_1/FP4_eOs_SP110824_Of446629_img/bin-linux-x86/fastboot: Permission denied

It should not be necessary, it is sometimes required when the user is not in GROUP=plugdev; this I see you have now done.

croy · January 7, 2025, 9:03pm

I followed the suggestion about OEM device info. Computer waiting for any device. (I left phone attached to computer with USB cord and phone in RESTART BOOTLOADER screen while I left home and did errands. Just got back and tried suggestion.). See pic of directory

Is there harm in closing terminal since still it’s looking for any device? Thanks piero

Lastly, yes I first tried this entire process on my Windows 11. Didn’t work. This was back in beginning of Dec so I don’t remember the error message/problem.

croy · January 7, 2025, 9:12pm

Aibd, thanks

Also in pic is platform tools directory on top right of screen and then the contents of that directory in bottom right. These directories have remained unchanged. I used to be able to type fastboot or adb at terminal prompt and then see text/code printed out on screen. Using sudo before fastboot devices worked usually so that my device was listed on screen. I understand your statement about platform-tools as suggesting I did not make directory where “be able to access adb and fastboot by typing only the below commands in a console
Adb devices
Or
Fastboot devices” from attached pic of directions INSTALLING ADB AND FASTBOOT IN A LINUX PC. Even though files are clearly listed in directory, are you saying it is necessary to do step six of these and and fastboot instructions again? Thanks for the clarification

croy · January 7, 2025, 9:14pm

Excuse me, step 7 of and and fastboot install procedure

croy · January 7, 2025, 9:19pm

As I see it, the code was added during my original attempt…

aibd · January 7, 2025, 9:29pm

Please show the output from your terminal when you type

$PATH

croy · January 7, 2025, 9:38pm

aibd · January 7, 2025, 9:43pm

So I now see “No such file or directory” against platform-tools and / or you have multiple PATH (??)

Edit while the earlier image of ~/.bashrc is incomplete or difficult to comprehend and does not look exactly like the line mentioned in “Add the path to you PC configuration” which is:

export PATH="$HOME/platform-tools:$PATH"

croy · January 7, 2025, 10:16pm

So are you saying that what the terminal printed out should look more like

export PATH=“$HOME/platform-tools:$PATH”?

What is listed in the pic above in bashrc is

quote
PATH=$PATH:$HOME/platform-tools:$HOME/tools
export PATH

PATH=$PATH:$HOME/platform-tools
export PATH
[end of quoted commands]

solution?