Please let us know how it worked out. I am also still waiting a bit and just using the phone with FPOS and trying things out.
1 Like
Yes, V2 came out a few days ago and (at least on my FP5) seems to work very well indeed 
I hope your install goes smoothly - please do let us know that it’s all gone well.
1 Like
Still reading docs and forum posts. I don’t want to risk this anti-rollback thing (I have the most recent FPOS updated on it. So my security patch level is not that old. It’s rather new). And seeing all sorts of other funky issues (recent apps not working, if one switches ti launcher) makes me still think, I should wait for 2.1 or whatever the next one after 2.0 is (or at least the next month or so).
(
- This one started to make me fill less unsure: Anti-rollback issue misunderstanding - #5 by Olivier
)
That sounds very wise if you have a recent security update on it. I haven’t seen anything about the timescale for 2.1, but it probably isn’t too far away.
FYI, in relation to the link in your last post - I did managed to successfully go from android to e/os/ and lock the bootloader, so it certainly can be done.
1 Like
There’s actually a thread on whether relocking the bootloader is safe:
After reading https://www.reddit.com/r/LineageOS/comments/n7yo7u/a_discussion_about_bootloader_lockingunlocking/ I will anyway likely not relock my bootloader.
1 Like
Intresting read! If you scroll through the feedback for V2.0 elsewhere in this forum, there does seem to be a lot of people who leave it unlocked
1 Like
To get a second opinion on that, what exactly is the SPL shown in the Settings app.
Maybe Settings > About phone > Android version … tap on Android version, or use the search feature od Settings,
The release notes https://gitlab.e.foundation/e/os/releases/-/releases state
This /e/OS v2.0 version includes the Android security patches available until April 2024.
I am still on Stock… that’s the reason I was fearing a straight update to current /e/OS, because the SPL is the same as on /e/OS.
My Stock has: 2024-04-05
As I wasn’t yet brave enough for flashing to /e/OS, I don’t know, what /e/OS for FP5 really has, despite the " This /e/OS v2.0 version includes the Android security patches available until April 2024.".
The text coloured blue is a hyperlink, revealing the exact detail, but states 2024-04-05, so the two are the same.
Technically, as I understand it, this is not a downgrade. (But I can understand why some would wait a month to be sure !)
More fully explained in the “Detail” dropdown.
To check the security patch level on your phone with a locked bootloader, prior to installing /e/OS, open your phone
Settings»About Phone»Android Version»Android Security Patch Level.Then compare it against the level of the security patch on the /e/OS build as visible in the Downloads for FP5 section below.
The following values control whether anti-rollback features are triggered on FP5:
- Rollback protection errors trigger if you install an update whose version number is
LESSthan the rollback index’s value stored on device. - The value of rollback index is
UPDATEDto matchro.build.version.security_patch’s value of the currently installed version, but only if the bootloader isLOCKED. - The value of rollback index is
NOTdependent on the currently installedANDROID VERSION. - The value of rollback index can
NEVERbeDOWNGRADED. - Rollback protection errors are
FATALwhen the bootloader isLOCKED. - Rollback protection errors are
IGNOREDwhen the bootloader isUNLOCKED.
Here are some examples to help you understand how anti-rollback features work:
Example 1
- Your FP5 with Google Android has a Security Patch Level saying June 5, 2022
- The /e/OS build available says: /e/OS build : R stable (Security patch: 2022-05-05)
- In this example, the /e/OS build has an older Security Patch level than the origin, so the anti-roll back protection will trigger, and you will brick your phone
Example 2
- Your FP5 with Google Android has a Security Patch Level saying June 5, 2022.
- The /e/OS build available says: /e/OS build : R stable (Security patch: 2022-06-05)
- In this example, the /e/OS build has the same Security Patch level than the origin, so the anti-roll back protection will pass, and you will be able to install /e/OS with no issues.
Example 3
- Your FP5 runs Google Android -R while /e/OS is now available based on AOSP -S.
- Your FP5 with Google Android has a Security Patch Level saying 2022-10-03 or October 3rd, 2022.
- The /e/OS build available says: /e/OS build : S stable (Security patch: 2022-06-05)
- In this example, the /e/OS build has an older Security Patch level than the origin, so the anti-roll back protection will trigger, even if the /e/OS version runs on a more recent version of AOSP. In this example, you will brick your phone.
2 Likes
Hi,
I updated using my Linux computer. It went smoothly, except I got a small glitch: I started the process with :
$ ./flash_FP5_factory.sh
INFO: One Fairphone 5 in fastboot mode found (serial number: xx123456).
Sending 'bluetooth_a' (3356 KB) OKAY [ 0.110s]
Writing 'bluetooth_a' OKAY [ 0.027s]
Finished. Total time: 0.144s
Sending 'bluetooth_b' (3356 KB) OKAY [ 0.130s]
Writing 'bluetooth_b' OKAY [ 0.025s]
Finished. Total time: 0.160s
Sending 'devcfg_a' (52 KB) OKAY [ 0.003s]
Writing 'devcfg_a' OKAY [ 0.005s]
[...]
Erasing 'userdata' OKAY [ 0.144s]
Finished. Total time: 0.146s
Erasing 'metadata' OKAY [ 0.004s]
Finished. Total time: 0.007s
Setting current slot to 'a' FAILED (remote: 'Unable to set slot')
fastboot: error: Command failed
I started it again, and it worked fine the second time :
$ ./flash_FP5_factory.sh
...
Setting current slot to 'a' OKAY [ 0.013s]
Finished. Total time: 0.015s
-----------
INFO: Done. The device will reboot now.
Rebooting OKAY [ 0.001s]
Finished. Total time: 0.051s
INFO: You can unplug the USB cable now.
So far, I’ve spotted 2 issues:
- Signal App : I installed it fine. Then I wanted to transfer my account from my temporary phone to the FP5. Apparently, Signal on the temporary phone was automatically updated on May 13, and even though the version number 7.6.2 is apparently the same on both the temporary phone and the FP5, it refuses to transfer my account to an “older version”. I disabled autoupdate on the temporary one, and I’m waiting for a new version to come in the App Lounge.
- Netflix refuses to start with a network error. I disabled the “hide my location” feature, but I still get the same error “Sorry we could not reach the Netflix service, please check Network Settings to connect to an available network and use Netflix (15001). (-93)”
Nice work !
Flavien.
1 Like
I have seen this error a number of times on this forum already. I start to wonder what’s going on.
Did you just rerun? Or have you done anything in between?
You might try…
- Aurora instead of the App Lounge. I have seen mentions of older versions on the App Lounge somewhere.
- Extracting the APK from your old phone
- There’s a straight download of the current version at https://signal.org/android/apk/.
Is it really at “install time”? Or at “(next) boot time” I would expect the boot being the problem?
… well actually the anti-rollback protection kicks in (or not) under these conditions:
People have reported bricking their phone at the moment of locking. As far as I know there is no documented way for the user the recover the phone (and it has to be returned for some advanced “reimaging” probably using an Emergency Download Mode method).
1 Like
Hi! Quick question from a beginner, I’m currently waiting for the next /e/OS release to avoid triggering the anti-rollback feature on my new FP5.
I’m wondering if this webpage will be updated with the new SPL at every new version of /e/OS : Install /e/OS on a Fairphone FP5 - “FP5” in the “Download for FP5” section ?
Also since I’m here, does anyone have a good guess for when the next version will be out?
I’m coming from a “only apple phone” life and I can’t wait to try /e/OS 
The v2.2 which should come out next week 
should have the June 2024 security patch
So it seems like 2.2 is out (from what I’ve seen here: Releases · e / os / 🚀 Releases · GitLab) and I have a few questions:
- As far as I’ve understand, the webpage Install /e/OS on a Fairphone FP5 - “FP5” has not been updated with latest security patch, is it supposed to be updated soon?
- From the same page, links to T community and T stable are confusing me (I still have to understand the differences) one of these two links has a 2.2-t zip file while the other doesn’t. Is it expected?
- What is the right place to look for new version? is it directly the gitlab release page I posted?
- Are there any links between date of release for /e/OS and date of release of the easy installer ? (my questionning is: should I wait a bit because a new release of the easy installer is about to be released?)
Thanks for giving me any info you think might help a noob 
We should hope so.
But as you found already, Releases · e / os / 🚀 Releases · GitLab gives the correct info for the respective /e/OS version.
https://doc.e.foundation/build-status
Yes.
Usually “official”/stable will come a few days later, when “community”/dev users have “test-run” the respective release a little.
More lag between the two may be experienced with major Android version upgrades, but in this case stable is on the same Android version already (Android 13 T), so this doesn’t play a role in this case currently.
The release page will show new releases, of course.
In the forum releases get announced in the weekly posts here … Topics tagged development-updates … and there will be a new feedback topic per release here … Topics tagged build-feedback.
For regular /e/OS updates based on the same major Android version you should get an update notification from the updater on your phone when it’s your turn. Releases are staggered (aka staged rollout). If you know the new version should be out there for you and you don’t want to wait, you can force your way to the update notification by refreshing the updater multiple times until it’s offering the update.
No.
Currently the Easy Installer doesn’t support the Fairphone 5 anyway … Releases · e / devices / Easy Installer · GitLab … see release 0.20.1.