Fairphone 5: the web installer failed, now about to try the manual installation but one question remains

[jerdef82]

Hi everyone,

I previously owned a Google Pixel 8 with GrapheneOS. That phone died in less than two years due to screen issues (vertical line, green screen, etc.). Google refused to repair the device under warranty even though these are known hardware issues and despite the three-year extension from the manufacturer.

Fast forward to the present moment, I am now officially tired of big corporations getting away with poor customer service, hence my recent switch to a Fairphone 5, which will hopefully last for years.

First things first, I tried the web installer but it failed with the error message below:

Error on step: connect-bootloader
Cannot execute command flashing unlock
Cannot execute command flash devcfg_a devcfg.img
error flashing file devcfg.img Bootloader error: Bootloader replied with FAIL: Flashing is not allowed for Critical Partitions

Not easily discouraged, I’m now considering the manual installation. However, I want absolute certainty that the manual installation will not brick my phone based on the Android version I have.

My Fairphone 5 is currently on the 5 January 2026 Android security update. The /e/OS build I’m looking at is IMG-e-3.5-a15-20260211580868-official-FP5.zip, released on 11 February 2026. Since this build is newer than my installed security patch, I assume it should be compatible - but I’d like confirmation before moving forward.

For context, I’m on Gentoo Linux (the same setup I used years ago to install GrapheneOS), and I have dev-util/android-tools installed with the udev USE flag enabled.

Linux nzxt 6.12.58-gentoo #5 SMP PREEMPT_DYNAMIC Tue Jan 27 23:56:11 CET 2026 x86_64 AMD Ryzen 5 5600G with Radeon Graphics AuthenticAMD GNU/Linux

$ equery u dev-util/android-tools
[ Legend : U - final flag setting for installation]
[        : I - package is installed with flag     ]
[ Colors : set, unset                             ]
 * Found these USE flags for dev-util/android-tools-35.0.2:
 U I
 - - python                    : Add optional support/bindings for the Python language
 - - python_targets_python3_11 : Build with Python 3.11
 - - python_targets_python3_12 : Build with Python 3.12
 + + python_targets_python3_13 : Build with Python 3.13
 - - python_targets_python3_14 : Build with Python 3.14
 + + udev                      : Enable virtual/udev integration (device discovery, power and storage device support, etc)

Any additional information you need to help troubleshoot, just let me know.

Thanks for the feedback.

J.

[piero]

Hello @jerdef82, Welcome to the /e/ users forum.

[HOWTO] a Clear Guide to install "IMG-e-builds" when /e/ web installer fails

[jerdef82]

Instructions unclear, I now have Windows 95 on my phone.

All jokes aside. Sorry but this is not clear.

Your Stock OS Android version, must be the latest available relative to the /e/OS build you want to install → not higher !

All I know is that the latest /e/OS build (11 February 2026) is more recent than the latest Android security update (5 January 2026) on my phone but there’s still no guarantee with regards to compatibility because the Android security update that the /e/OS build supports is not mentioned. If it did, perhaps there wouldn’t be so many questions on the subject.

And the latest release for FP5 on Releases · e / os / 🚀 Releases · GitLab tells me it’s not compatible - see screenshot below.

When you click the link that says “January, 1st” (https://source.android.com/docs/security/bulletin/2026/2026-01-01), you’re taken to a page related to release dated January 5 2026 even though the URL itself mentions “2026-01-01”.

[aibd]

I see the latest build as IMG-e-3.5-a15-20260211580868-official-FP5.zip while you are quoting the previous 3.4 release. (We are in the middle of rollout, so you may need to delay if 3.5 really is not showing for you.)

• Install /e/OS on a Fairphone FP5 - “FP5”
• (answered) Install /e/ on FP5 with newer Security Patches

[jerdef82]

I used the 3.4 release as an example because it mentions bug fixes for the Fairphone 5 whereas IMG-e-3.5-a15-20260211580868-official-FP5.zip on Releases · e / os / 🚀 Releases · GitLab mentions bug fixes for the Fairphone 6 and nothing for the Fairphone 5 but I guess that’s because the software for FP5 is already pretty stable or no new bug was fixed in the 3.5 release. However, it doesn’t necessarily mean that the 3.5 release is incompatible with my latest Android security update.

Why does the web installer fail for so many people by the way? Too many different devices and too many different releases?

[piero]

@jerdef82

All jokes aside. Sorry but this is not clear.

You did not understand that it is fully unrecommended to install a e-3.5-a12 build on a Pixel phone already running latest GogolOS (android 16 based) ?

Sorry, Focus have mooved from “simple” to “safe”…

[jerdef82]

No, I understand that part. But the release notes aren’t very clear about which Android security update you’re getting from the latest /e/OS build.

And where does it say in my first post that I still use a Pixel device? My Google Pixel 8 didn’t run on /e/OS, it was on GrapheneOS. I no longer own that Pixel device. This post is about the Fairphone 5. But something tells me you used the Pixel device as an analogy.

Interesting that you need to wait a certain amount of time before being able to post a new reply.

[GabrielT]

The security patch level is written in the instructions but not anywhere else:

[ieder1]

If you can wait until the 3.6 release, then you probably don’t have to downgrade anymore.

@Manoj

OS Version Release
/e/OS - A16

Planned release along with v 3.6 in March 2026

The list of devices which will get the upgrade to A16 will be shared. Upgrades will be manual for community builds and OTA for official builds. Manual upgrades will require users to download and install the builds over existing build. A backup of data is advised in all cases.

Status: under testing.

[jerdef82]

Alright. Your screenshot shows 2026-02-01 as the latest security patch for the /e/OS build but the latest Android security update on my phone is 5 January 2026. In other words, the FP5 is lagging behind and installing /e/OS on it will more than likely brick my phone. No wonder the web installer failed.

I feel dirty running stock Android… I’m going to need soap. A lot of soap.

[piero]

@jerdef82

installing /e/OS on it will more than likely brick my phone

installing is never an issue, but relocking the bootloader…

@jerdef82

Your screenshot shows 2026-02-01 as the latest security patch for the /e/OS build but the latest Android security update on my phone is 5 January 2026.

i don’t see the issue here…

@piero

things you must take care about

Your Stock OS Android version, must be the latest available relative to the /e/OS build you want to install → not higher !

Warning: Before proceeding with the installation, log out of any accounts you may have set on the stock ROM. Also, remove any screen locks that have been set on the device.

Use a USB-A to USB-C cable on a rear USB port if possible, to avoid hub even internal

If you plan to relock the bootloader after the installlation

this is not mandatoty, and only available with Official version, why relocking ?

Most important thing to take care about is the “android Security Update" aka "Security Patch Level” date (SPL) included in the installed Operating System on your device at time of the unlock.

new version on witch you want to relock the bootloader, must included a NEWER (or the same) “android Security Update" aka "Security Patch Level” date (SPL),

otherwise you risk to change your device into Brick.

[jerdef82]

I was able to install /e/OS via the web installer - see screenshot below.

However, now my phone is stuck in a boot loop. No matter which option I choose (START / Restart bootloader / Recovery mode / Power off), the device just keeps rebooting.

I’m still able to communicate with the device using:

$ fastboot devices
00f3abbd         fastboot

[piero]

@jerdef82

I was able to install /e/OS via the web installer - see screenshot below.

do you mean ?

.

All jokes aside.

.

@jerdef82

I’m still able to communicate with the device using:

$ fastboot devices
00f3abbd         fastboot

so you are in good position to check the bootloader status :

fastboot oem device-info

fastboot flashing get_unlock_ability

[GabrielT]

No, that means you will be fine. The order of the dates is the correct one. It is even better than equal dates because your installed version is truly older than what you will install. It is possible to install when both dates are equal but one would feel more doubts

[jerdef82]

No. I don’t see the /e/OS home screen you have. The device is stuck in a permanent boot loop, no matter the option. I see the Fairphone logo appear for a very short while on screen and then the device immediately jumps back into fastboot mode. I never got the chance to see the /e/OS logo that appears on the last step of the installation process.

Below are screenshots with the four states (START / Restart bootloader / Recovery mode / Power off) I have available in fastboot mode. Again, all four options result in the device rebooting forever and taking me back to the fastboot mode.

I’m so ready to try out the manual installation at this point, provided the device can still be saved/recovered. I wanted to give the web installer one more chance but apparently that wasn’t such a bright idea…

Commands as requested by piero

$ fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [  0.001s]
Finished. Total time: 0.001s

$ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [  0.001s]
Finished. Total time: 0.001s

Screenshots

[piero]

so you are in the best situation to have a go with next step :

@piero

2. Installing /e/OS

.

On the PC, download latest build from /e/OS website,

in case here : /e/OS official FP5 download,

just extract it, not more.

• (Windows) : Use the right clic of the mouse,
  and choose open Git Bash here
• (Linux) : Use the right clic of the mouse, and choose
  open a terminal in this folder
• (macOS) : rename the newly extracted folder
  /IMG-e-3.5-a15-20260211580868-official-FP5
  into
  IMG-e,
  then copy / paste
  cd ~/Downloads/IMG-e.
  into the terminal

Then

• Copy this command and paste it into the terminal :

chmod +x flash_FP5_factory.sh && ./flash_FP5_factory.sh

you are done with installing /e/OS

[jerdef82]

I use the Fairphone 5, not the Fairphone 4. I would rather not run commands that are inadequate for my device.

Previously I had downloaded IMG-e-3.5-a15-20260211580868-official-FP5.zip and unzipped its content in a separate directory - see ls command below.

Which version do I need if IMG-e-3.5-a15-20260211580868-official-FP5.zip is not the right version? Or does it not matter which version you install as long as the phone model (in my case “FP5”) is correct?

Seriously handicapped by the inability to post replies more often… It makes interactions more complicated for new members.

😇  [ ~/Downloads/e-os ] $ ls -lah
total 4.6G
drwxr-xr-x 5 jerdef jerdef 4.0K Feb 23 21:06 .
drwxr-xr-x 6 jerdef jerdef 4.0K Feb 23 21:06 ..
-rw-r--r-- 1 jerdef jerdef 152K Feb 11 18:05 abl.img
-rw-r--r-- 1 jerdef jerdef 204K Feb 11 18:05 aop.img
drwxr-xr-x 3 jerdef jerdef  171 Feb 11 18:05 bin-darwin
drwxr-xr-x 3 jerdef jerdef  171 Feb 11 18:05 bin-linux-x86
drwxr-xr-x 2 jerdef jerdef  184 Feb 11 18:05 bin-msys
-rw-r--r-- 1 jerdef jerdef 3.4M Feb 11 18:05 bluetooth.img
-rw-r--r-- 1 jerdef jerdef  96M Feb 11 18:05 boot.img
-rw-r--r-- 1 jerdef jerdef 183K Feb 11 18:05 cpucp.img
-rw-r--r-- 1 jerdef jerdef  53K Feb 11 18:05 devcfg.img
-rw-r--r-- 1 jerdef jerdef  64M Feb 11 18:05 dsp.img
-rw-r--r-- 1 jerdef jerdef  24M Feb 11 18:05 dtbo.img
-rwxr-xr-x 1 jerdef jerdef 9.3K Feb 11 18:05 factory.common
-rw-r--r-- 1 jerdef jerdef  85K Feb 11 18:05 featenabler.img
-rwxr-xr-x 1 jerdef jerdef  500 Feb 11 18:05 flash_FP5_factory.sh
-rw-r--r-- 1 jerdef jerdef 3.6M Feb 11 18:05 hyp.img
-rw-r--r-- 1 jerdef jerdef  64K Feb 11 18:05 imagefv.img
-rw-r--r-- 1 jerdef jerdef 266K Feb 11 18:05 keymaster.img
-rw-r--r-- 1 jerdef jerdef 182M Feb 11 18:05 modem.img
-rw-r--r-- 1 jerdef jerdef  14K Feb 11 18:05 multiimgoem.img
-rw-r--r-- 1 jerdef jerdef  56K Feb 11 18:05 qupfw.img
-rw-r--r-- 1 jerdef jerdef  45K Feb 11 18:05 shrm.img
-rw-r--r-- 1 jerdef jerdef 240K Feb 11 18:05 studybk.img
-rw-r--r-- 1 jerdef jerdef 4.1G Feb 11 18:05 super.img
-rw-r--r-- 1 jerdef jerdef 3.7M Feb 11 18:05 tz.img
-rw-r--r-- 1 jerdef jerdef 123K Feb 11 18:05 uefisecapp.img
-rw-r--r-- 1 jerdef jerdef 8.0K Feb 11 18:05 vbmeta.img
-rw-r--r-- 1 jerdef jerdef 4.0K Feb 11 18:05 vbmeta_system.img
-rw-r--r-- 1 jerdef jerdef  96M Feb 11 18:05 vendor_boot.img
-rw-r--r-- 1 jerdef jerdef 3.6M Feb 11 18:05 xbl.img
-rw-r--r-- 1 jerdef jerdef 221K Feb 11 18:05 xbl_config.img

[jerdef82]

/e/OS is now installed! Thanks, piero and the others.