Fairphone 4 is not booting in the last step

Hello, I was trying to install Murena via the Easy Installer beta in Google Chrome. The last step isn’t working.

‘While your phone is booting, you should see the logo below. This takes time, please be patient.’

On my Fairphone 4 I’ve got a screen with START (green letters) on top.
Fastboot Mode
PRODUCT_NAME_FP4
VARIANT - SM_ UFS
BOOTLOADER VERSION -
BASEBAND VERSION -
SERIAL NUMBER - …
SECURE BOOT- yes
INTERNAL STORAGE SIZE - 240GB
MAIN MEMORY SIZE AND VENDOR - 8GB UNKNOWN
DISPLAY PANEL NAME - …
DEVICE STATE - unlocked

I don’t know what to do. Could you please assist me?

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online servicesphone

This is the bootloader (fastboot mode).
You can navigate with Vol+ and Vol- to select the boot mode and confirm with the Power-Button.

Thanks for your reply. I tried to restart the bootloader but it brings me back to the bootloader. It doesn’t open the boot with the Murena Icon.

Try the installation method using adb tools and shell script.

Did the installer advise you or lead you to deal with these two steps

  • Your device requires a code to unlock the bootloader. Get the code here before proceeding with the next steps
  • Enable USB debugging on your device. You can find the instructions here

Source: Install /e/OS on a Fairphone FP4 - “FP4”

Yes I went true all the steps the installer asked me till the end… now I cannot get out the FastBoot Mode.

Does the web installer tell you if or where it keeps a log? This might tell you what went wrong.

Check the state of the bootloader by typing (android tools requied):

$ fastboot oem device-info
(bootloader) 	Device tampered: false
(bootloader) 	Device unlocked: true
(bootloader) 	Device critical unlocked: true
(bootloader) 	Charger screen enabled: true
(bootloader) 	Display panel: 
(bootloader) 	Adb enabled: true
OKAY [  0.069s]
Finished. Total time: 0.070s

If Device unlocked and Device critical unlocked still true, you can repeat the installation.

Error on step: device-detection

Cannot execute command connect adb
The device is not connected Cannot read properties of null (reading ‘name’)
Proposal: Check connection and that no other program is using the phone and retry.

adb commands are not available while the phone is in fastboot mode.

You must use fastboot commands only. Check with

fastboot devices

first then follow the advice above.

Sorry can you help me a bit more. How do I check with fastboot devices. On my desktop I’ve got a folder platform-tools prepared.

I’ve got this

./fastboot devices
55146dce fastboot

Now type

./fastboot oem device-info

(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.001s]
Finished. Total time: 0.001s

The bootloader is still unlocked. You can use the script to install using the fastboot mode:
https://doc.e.foundation/devices/FP4/install

You start at

Installing /e/OS

.
.

because your bootloader is already unlocked.

INFO: The procedure will start soon. Please wait…
Note that this will detect and flash only on FP4 device.
INFO: You are using MacOS.
INFO: Looking for connected device(s)…
./flash_FP4_factory.sh: line 33: /Users/eltoneerkens/Desktop/IMG-e-2.7-t-20250112460980-community-FP4/bin-darwin/fastboot: No such file or directory
WARNING: No Fairphone 4 found in fastboot mode.
WARNING: Make sure that a Fairphone 4 is connected.

fastboot should be found in this subdirectory.

Is the any reason, why your use the community build ? Maybe some files (e.g. fastboot) are missing in the community build.

I copied it from the platform-tools folder so I can continue…

Wauw I think I did it. But I didn’t lock the Bootloader.

Before you lock the bootloader, you should read the section about the rollback protection:

Caution: The FP4 comes with an anti-rollback feature.
.
.