I think /e/OS is released too soon for the FP6. It’s not available on LineageOS, iodeOS, CalyxOS yet.
I’m thinking to back to FairphoneOS before move to iodeOS or CalyxOS.
CalyxOS is on hold for a few months … A letter to the CalyxOS community
Yeah i saw it. I go to their website everyday. I just hope one day it will be compatible.
In the download section the docs say the official build is based on the 2025-08-01 security patch:
https://doc.e.foundation/devices/FP6/install#downloads-for-fp6
But when you click the link, the latest version is 3.0.4:
https://images.ecloud.global/official/FP6/
Which is actually based on the june 2025 security patch:
I assumed the value in the docs was correct, which led me to install the old version, which caused issues with the anti-rollback stuff. Luckily I could reinstall the original android version, but it was quite annoying.
Is the august version for the fairphone 6 already released, or is it a mistake in the docs?
Hi @Mr_LiamT wellcome to the /e/ forum; I can see this is an annoying first experience.
Yes it has been there for ~48 hours but I see it missing right now.
I cannot explain this. I suggest to check again in 12 - 24 hours.
The previous presence of the build is confirmed by many fp6 posts in the Feedback for v3.1.1 thread.
1 Like
Hello. I successfully installed /e/os on the Fairphone 6 (from a Windows 10 OS computer), albeit with some difficulty (I am not tech savvy with phones). I suggest some evolutions in the " Install /e/OS on a Fairphone The Fairphone (Gen. 6) - “FP6” " procedure.
- The information from this post should appear in the guide. Despite installing all the drivers for Windows specified in the guide and linked documentation, I still encountered the issue “FP6 is not seen by fastboot command line”, which will be encountered by anyone like me (i.e. who never installed/used adb, fastboot or android related software on his computer). How about adding the following text in the section " Unlocking the bootloader > step 6.Run
fastboot flashing unlock" ?
If the command does not have any effect (while executed from a computer running Microsoft Windows OS), this might be a fastboot driver problem. To confirm this issue and fix it, follow these steps while the FP is connected in fastboot mode to the PC (this point is important : it will inform the computer that a new “peripheral/device” requires a new driver and incite him to look for it actively when the computer checks for updates in the next steps):
- Go to Windows Updates
- Check for updates manually
- Go to Optional Updates and Drivers and install everything regarding Google/Bootloader (e.g. Kedacom/LeMobile).
I do not have the perfect screenshot for this step but this one shows the result after installation in the update history :
-
Adding a mention somewhere on how to confirm if adb and fastboot are working and connected to the phone at any point of the tutorial (with the commands “adb devices” and “fastboot devices” for example). This topic can also be offloaded in a separate post, with the FP6 installation procedure having a link to it.
-
This post provides useful general knowledge (for beginners) on what it takes to install android, how to handle bricking (by user or by paying professional support). How about adding a link to the post at the end of the introduction (after “The /e/OS project and its project members deny any and all responsibility about […] /e/OS services.” and before “Requirements” section) ?
From my point of view, the first suggestions is very important because it removes a roadblock. The 2 other suggestions are less important but useful.
3 Likes
I’d suggest adding how to enter the fastboot? mode (idk, the mode where you can run fastboot commands) after unlocking/locking the bootloader → disconnecting from usb and pressing volume down + power button when device is shut off.
Also to tell people to sign out of google accounts before installing a custom rom, otherwise frp is locked and you cant set a lock screen.
Maybe add that for macos it’s the same way of installation as for linux.
Another suggestion from me as it bit me: Add a note at the fastboot lock/lock_critical steps that it will wipe the system again.
1 Like
English translation below
Sur la page Install /e/OS on a Fairphone The Fairphone (Gen. 6) - “FP6”
Au paragraphe
- Installing /e/OS
- nous avons la commande
chmod +x flash_FP6_factory.sh && ./flash_FP6_factory.sh
Pourquoi faire compliqué quand on peut faire plus simple
- sudo : inutile car vous êtes le propriétaire du fichier
- chmod +x flash_FP6_factory.sh : inutile car le fichier est déjà exécutable
- && : inutile car il ne reste plus qu’une commande sur la ligne
Donc la commande simplifiée est
./flash_FP6_factory.sh
====================================================================
On the page Install /e/OS on a Fairphone The Fairphone (Gen. 6) - “FP6”
In the paragraph
- Installing /e/OS
- we have the command
chmod +x flash_FP6_factory.sh && ./flash_FP6_factory.sh
Why make things complicated when they can be simpler?
- sudo: unnecessary because you are the owner of the file
- chmod +x flash_FP6_factory.sh: unnecessary because the file is already executable
- &&: unnecessary because there is only one command left on the line
So the simplified command is
./flash_FP6_factory.sh
Translated with DeepL.com (free version)
Where is the problem when we copy and paste this command line into the terminal?
Les deux commandes ci-dessus font la même chose sur le FP6
chmod +x flash_FP6_factory.sh && ./flash_FP6_factory.sh
./flash_FP6_factory.sh
- Ce que je veux dire
- en mathématique une fraction ou une équation on simplifie
- pour atteindre une cible on ne prend ne suit pas un chemin tortueux on prend la ligne droite si elle existe
- en informatique c’est pareil on choisit si possible une seule commande qui fait le travail au lieu de lancer plusieurs commandes
Oui tout à fait, mais si la commande proposée est celle-ci, c’est qu’il doit y avoir une raison, enfin je pense.
1 Like
First of all thank you @Kras 
Without the input I would have lost hours searching for the drivers.
And thanks to @fp31, too Unfortunately, I have seen your input too late 
Adding this to the official guide would have been great.
I think another tip would be of use. After locking/unlocking the bootloader I had to re-enable the developer mode and the USB debugging.
1 Like
If you plan to relock the bootloader after the installlation
(not mandatoty, only available with Official version, why relocking ?)
Most important thing to take care about is the Stock OS “android Security Patch Level” already installed on your device before you start the install process.
It must be OLDER than the “android Security Patch Level” included in the /e/ build you want to install, otherwise you risk to change your device into Brick.
only Android Security Update count, not the build date
if FairphoneOS is 2025-10-05 and /e/OS is 2025-10-01
DO NOT RELOCK THE BOOTLOADER !
You can install /e/OS but not relocking until the next /e/OS update release
(relocking will erase /data where installed apps and personnalisations are stored)
or
Wait the next /e/OS update release to install and relock
Hey guys,
i got my new Fairphone6 and i like to install e/OS official image on it and close the bootloader after.
The flash from the linux commandline works well.
After install i boot and setup system, which works normally.
After that i rebooted one time and it works flawlessly.
If i switch into the bootloader then to lock and critical_lock the device the lock_critical work.
Then the device asks me if i like to lock the bootloader, i choose no (cause the flash lock is missing.
If i turn the phone now off and restart into bootloader then again i flash lock and lock the bootloader.
On the next boot my device is corrupt and can’t boot anymore.
In ca reinstall e/OS without problems - but - how can i fix the corrupt device ? 
Thanks alot and have a nice day
check bootloader status by running :
fastboot oem device-info
fastboot flashing get_unlock_ability
After pressing volume and power i’m getting a new screen if i want to unlock the bootloader or not.
If I’m right i need to wait for e/OS 3.3 and then i can relock it, right ?
Thanks alot
1 Like
Sadly this is what I did. I really believed that the /e/OS version of October would be the same as the one from FairphoneOS, not counting the 4 days. Really frustrating! Can’t boot anything now.
Can I throw away the device now, or is there any rescue mode? I can’t really believe I’m the first one experiencing this?
Hello @layost, Welcome to the /e/ users forum.
.
did you tried first to unlock again ?
if not possible for you to unlock again,Fairphone Repair Services ask for 30-60 € to restore the device.