"No Fairphone 4 found in fastboot mode" error message

Try to remove the wrong lines from ~/.bashrc

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

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

and replace with

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

You should run

source ~/.bashrc

in order to update the result of

$PATH

or

echo $PATH

can produce a nicer output. Of course I do not know how you got into this situation, maybe Fedora does things differently!

I saved bashrc file modifications you advised and ran

source .bashrc

(Fedora uses .bashrc as correct configuration file for Bash shell. Located in my Home directory)

But before I did I took pic of entire .bashrc

I did confirm contents of .bashrc match what originally came with Fedora 41 (except the line I added today.)

I also ran $PATH

and

echo $PATH

I do observe a change. The result has fewer lines of code listed…

When you can, it maybe you’re on the right track… Thank you for your help because I am at a loss what else to do.

So I think we still need to consider if there might be another residual install of platform-tools. When I said

it would have included you reading the opening

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.

Fedora can be a bit “different” in how it likes cross-platform stuff setup.

What am I saying ? Only … “we still need to consider if there might be another residual install of platform-tools.”

The last thing we did was to try to ensure you could access a recent copy of platform-tools system wide. From your home directory please show the output of

fastboot --version

Now in order to follow the install page we have to move to the directory with the downloaded image. We are told

  1. Confirm that extracted directory contains following content:

Now please change to that directory show the output of

fastboot --version

If both are identical, with your phone connected in Bootloader (big green START at the top), then what is the output of

fastboot devices

If then the the phone “self identifies”, perhaps you can try to run the script.

I would be interested to know what prevents you from copying text from your terminal to the forum as suggested

The leading triangle indicates that you press on the link to unroll the content.


Finally, you have read and taken into account

Caution: The FP4 comes with an anti-rollback feature. Google Android anti-roll back feature is supposedly a way to ensure you are running the latest software version, including the latest security patches.
If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device. Click on Details below for detailed information.

This will only be an issue if you have recently updated FairphoneOS.

1 Like

From Terminal (which is at /Home/ccoffice_1/)

ccoffice_1@fedora:~$ fastboot --version
fastboot version 35.0.2-12147458
Installed as /home/ccoffice_1/platform-tools/fastboot

From platform-tools (which I found in /Home/ccoffice_1/ and right click using a mouse on platform-tools and selected OPEN IN TERMINAL) out put

ccoffice_1@fedora:~/platform-tools$ fastboot --version
fastboot version 35.0.2-12147458
Installed as /home/ccoffice_1/platform-tools/fastboot

Version numbers match, so next step

Phone connected in Bootloader with big START at top (BTW is this start being at top critical because sometimes I had Restart Bootloader at top?) And the output was

ccoffice_1@fedora:~$ fastboot devices
no permissions; see [हार्डवेयर डिवाइस पर ऐप्लिकेशन चलाएं  |  Android Studio  |  Android Developers] fastboot

I have seen "no permissions; see [https:. … ] before and went to website. I found little benefit.

Did not try running script, but appreciate your help. Will wait to hear. . . and also Build number of FP4 on my phone is 20241030. The build that I want to flash to FP4 is 20241101. As I understand this will NOT brick my phone…

This would indicate that the problem is on the device … but it is unfortunate that you did not eliminate the PC side first. :slight_smile:

Here I refer to the Fairphone 4 install page, which directs us to move into the folder where we downloaded and unzipped the ROM.

Yes it is critical.

I mentioned before that you should learn also to navigate the menus within Bootloader, perhaps consult the Fairphone forum. The install page gives directions how to boot into Bootloader.

I would advise to check both the security patches as indicated in the install page to be certain.

As I did not specifically ask already, please can you confirm that you requested, received and applied the Unlock code from Fairphone ?

yes, directory on my HOME called FP4_eOs_SP110824_Of446629_img and files are included

About the START being at top of Bootloader, this detail I assure I followed for the last two attempts to run the script.

I will look at security patches again but as I remember I looked at those also and verified previously that they were okay.

“confirm that you requested, received and applied the Unlock code from Fairphone?” As I understand you refer to the boot unlock code that I got when I entered into their website the IMEI and Serial number of my phone. Then I put (applied) that boot unlock code into ENABLE OEM UNLOCK in Developer options. I received no error messages.

I did confirm just now that the phone/device is still in USB debugging mode and that OEM unlocking is still grayed out saying “Bootloader is already unlocked” (debugging mode and OEM unlocking accessed in the Developer Options menu.)

OK … so that was the line that introduces:

Greyed out does not sound right … we expect to see something that would suggest OEM unlocking is Active. This is what it looks like on FP3

I understood the request about FP4 directory as Now please change to that directory and show the output of
fastboot --version
I right clicked on FP4 director. chose OPEN IN TERMINAL and typed

fastboot --version

at ccoffice_1@fedora:~/FP4_eOs_SP110824_Of446629_img$
prompt

Output

fastboot version 35.0.2-12147458
Installed as /home/ccoffice_1/platform-tools/fastboot

So I believe that (we have established that) the problem is on your FP4; this seems wrong to me.

1000001406

Please can you show the output of

fastboot devices

then


fastboot flashing get_unlock_ability

then

fastboot oem device-info

Maybe you might try

fastboot getvar all
1 Like

Phone attached via USB cord and phone in bootloader mode (green START at top of screen.)

Could not complete 3rd and 4th (OEM and getvar) because Terminal in “Waiting for device” mode.

I tried several times to reply to post but kept getting

I don’t know why the forum is doing that but …

The point of running

fastboot devices

first … then other commands is to let others to see progress and where things break down.

Could not complete 3rd and 4th

So please show what you can do.

Perhaps restart PC or device is required (??).

Here is what I tried to send
Screenshot From 2025-01-09 13-12-54

sudo fastboot devices

How do I get out of waiting for any device mode??

By correctly enabling “OEM unlock”

you forget the word devices in