Just to add, I executed this command in termux and gave me May’s security patch
~ $ getprop ro.build.version.security_patch
2025-05-05
1 Like
Checking with the build team. Will respond ASAP.
Waiting for what?
Unfortunately you can add me to the list of bricked devices 
…
I double check everything followed the suggestions provided here and in FP’s wiki
I installed the stock OS back and double check the security level is the same before locking the bootloader, and indeed it was the same 2025-05-05 but the phone still won’t boot now.
When I said this needs clearing up first what I really meant was that this needs clearing up first.
Damage is done on a Friday afternoon… let’s see what can be done on Monday
As of now, and as suggested in the Fairphone community forum, the solution would be to contact Fairphone support.
1 Like
We will be releasing v3.0.3 which will have June patch for A13,14 and 15. The current patch is from May. v3.0.3 should be available this coming week. Besides the patches it has the critical security patch for the browser as mentioned here. Will have the guide updated.
2 Likes
Does version 3.0.3 correct the zoom problem, which is not working? And have you also planned to integrate the official fairphone camera photo application, as you have already done for previous models?
1 Like
It would be really great if the guide mentioned, that locking the bootloader erases all data on the device. Much more so, since if you were to use the device for a bit, potentially already migrating some data, which were not recoverable due to how some messengers only allow a single primary device that they migrate data to.
1 Like
Hello,
Thank you very much for the /e/OS support on the Fairphone 6 
Installation worked fine for me. I have a few suggestions as proposed in Install /e/OS on a Fairphone The Fairphone (Gen. 6) - “FP6”
I would recommend adding a global warning for the whole process stating that several factory reset will occur during bootloader unlocking and locking (4 if I properly recall). I think that the warning on « Unlocking the bootloader » is good but not enough. And there is no warning in the « Locking the Bootloader » part. If we’re keen to test /e/OS on first boot, we may forget to immediately relock the bootloader. At best, we’ll realize it afterwards, but we’ll lose all our configuration in the locking process. So I think it would be better to strongly encourage the user to complete all the operations without stopping.
Unlocking the bootloader
Point 8) I would explain here that it is necessary to go through the Android configuration again in order to activate adb with adb reboot bootloader even if it is redundant with point 5)
I would add that each unlock and unlock_critical operations will run a factory reset and that they will require to configure Android, enable Developer mode and then adb.
Installing /e/OS
Point 2)
directory - which contains linux tools including fastboot and adb
I searched for adb in bin-linux-x86 directory and I didn’t find it. I didn’t stop, but this one intrigued me.
-rwxr-xr-x 1 yoann yoann 1645440 juin 27 12:48 e2fsdroid*
-rwxr-xr-x 1 yoann yoann 2417136 juin 27 12:48 fastboot*
drwxr-xr-x 2 yoann yoann 4096 juin 27 12:48 lib64/
-rwxr-xr-x 1 yoann yoann 262728 juin 27 12:48 make_f2fs*
-rwxr-xr-x 1 yoann yoann 262712 juin 27 12:48 make_f2fs_casefold*
-rwxr-xr-x 1 yoann yoann 879656 juin 27 12:48 mke2fs*
-rwxr-xr-x 1 yoann yoann 1157 juin 27 12:48 mke2fs.conf*
-rwxr-xr-x 1 yoann yoann 1701544 juin 27 12:48 sload_f2fs*
-rw-r--r-- 1 yoann yoann 38 juin 27 12:48 source.properties
It may require a small modification to avoid worrying the person installing /e/OS, insofar as you are asked to “Confirm” the content.
Locking the bootloader
Like mentioned before
- it would be good to know 2 factory reset will occur.
- it would be good to mention that Developer + adb are required each time to be able to reboot into the bootloader (or with shortcuts)
And finally, I think it’s missing the fact that in developer options, we need to disable OEM unlock to finalize the operation (which requires a last reboot)
That was to make the installation easier for other people. Otherwise it worked very well for me and I’m delighted to finally be able to test /e/OS.
Thanks a lot!
1 Like
Worked amazing! Thanks. Awesome community love this
Hey everyone !
Just got the FP6 and wanted to flash /e/os on it. I look at both the Community build and the Official build and tried to find the ro.build.version.security_patch key to be sure I could continue with one of them.
In the FP6 Doc it is mentioned that for both builds :
(Security patch: 2025-06-05)
But I wanted to check myself. I thus convert the super.img from a sparse Image to a raw Image using simg2img, utilized lpunpack to extract it and then mounted the system_a.img image (because what is the system_b?). Looking at the pathtofolder/system/build.prop I got 2025-06-01 which is not what I expected from the Doc. Is this process not the correct way to check the security patch level ?
I thank you for your time and consideration.
PS : First time flashing, I hope you accept my apologies for any inaccuracies or misunderstanding I may have made.
2 Likes
After a long afternoon, trying to figure out why it was impossible to flash the OS, I found this [post](https://community.e.foundation/t/install-e-os-on-fairphone-6/71230/59) which suggests to use USB 2.
Besides that, the documentation and the comments made by @yoann where very helpful.
It is my first Fairphone and my first use of e/OS, I’m looking forward to discovering what it can do! Thanks
3 Likes
@akitzu I’ve got 3.0.4 installed so here is the patch level information from android settings:
@onestacked cool ! thanks a lot for the info ! I should be ok to go. I am still a bit worried, isn’t there a way to check the patch level directly from the zip file we get online and that should match the one you have ?
Edit : I didn’t check correctly, It is not ok for me to continue ! The Android security update is June 1 2025 (but on the doc is says June 5 so why is so ?)
I have the same question.
I have FP6.QREL.15.105.0 (05 June 2025 security update) official now.
Is it safe for me to install IMG-e-3.0.4-a15-20250708507307-official-FP6?
Thanks!