I decided to upgrade my fairphone experience with buying a new fp5 over my fp3+.
I remembered how I set up /e/os on my fp3+ with the easy installer, found out it’s depricated, but there is a new thing called the web installer.
After some medium hickups like the missing windows update, the installer finally said installation completed, my phone should now boot into /e/os.
It however does not. It boots into bootloader mode. No matter if I choose “Start”, “reload bootloader” or “recovery mode”, it will just boot into bootloader mode. The only thing I can choose that behaves different is “power off”, which the device will do, but when I reboot - same old behaviour, only bootloader mode.
While searching for a solution I tried:
holding volume up and power buttons - still bootloader mode, not recovery
when I connect my phone via USB, I cant connect to it (or am I doing it wrong? How do I do it correctly?)
of course, before starting the installation process, I updated Android to the latest version
I read that you can brick your device when the security levels dont match, but I only read that after using the web installer, which did not give a warning… at least I guess my bootloader is unlocked, so there is hope?
Here is a screenshot of the bootloader screen of my phone (taken with my old pf3 camera):
Yeah, keep your hair, use the command line instructions. The web installer can be unreliable.
The web installer looks simple enough and it is if you don’t run into a problem. If you do, give up on it at that point. You’ll pull way more hair out trying to get the web installer to work than if you just fall back to the manual instructions.
You are wise to read this carefully but this will not affect the phone until it is relocked (so that is not the problem right now).
Your description would fit with the installer having run the install script but not to successful completion … the current installer seems not to produce a log where you could find the state of play.
From your image your phone looks to be safely waiting in Fastboot mode. Your PC will “see” it again with the command
fastboot devices
after you install platform tools. Once you know that you have working Fastboot mode you will be able to follow the CLI manual instructions.
There are many examples of recovery from web installer failure in threads with hashtag Web Installer or eosinstaller …
from user feedback in another post, i am suspecting the web “fail-installer” to attempt to flash the recovery-e on the device, that is not expected on this device install process…
sorry for letting you wait that long. I had a busy day!
Long story short: I made it work and now have /e/os running on my fp5.
I think I should have been more precise with my description yesterday! I did in fact run “fastboot devices”, which, although being in fastboot mode, did not return a device.
Today, however, it did, thus i could complete all the steps to install /e/os. I dont know if it was a problem with adb/fastboot 's path not having been added correctly, or if i hadnt been in the udev group, or if it was just a necessary reboot of my pc - but today it worked.
I deciced to not lock the bootloader, as I had various versions of android and probably different versions of security patch, so in order to really not brick my device, i decided to wait until security patch is coming out on a day later than today.
Hello, I have the same problem.
Though my android version was not the most recent.
Can i with no risk install /e/os manually even though the security patch level says
/e/OS build : U community (Security patch: 2025-05-01)
And my security patch level was 2025-05-05 ?
Thanks in advance …
BOOTLOADER VERSION - FP5.UT2P.B.122.20250422
BASEBAND VERSION - 13
