Hi there, sorry if this was answered before, I could not find it.
I have read this thread but also could not find the answer Fairphone 5 upgraded to Android 14
Does " * Rollback protection errors are IGNORED when the bootloader is UNLOCKED ." mean, if I unlock the bootloader, i can install /e/os with an older Security Patch Date?
I have a FP5 with Android 14, Security Patch Date January 5th 2025
So if I unlock the bootloader, is it possible to install current community build or official build?
/e/OS build : U community (Security patch: 2024-11-01)
/e/OS build : T official (Security patch: 2024-11-05)
Caution: The FP5 comes with an anti-rollback feature. Google Android anti-roll back feature is supposedly a way to ensure you are running the latest software version, including the latest security patches.
If you try installing a version of /e/OS based on a security patch that is older than the one on your device, you will brick your device. Click on Details below for detailed information
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 LESS than the rollback index’s value stored on device.
The value of rollback index is UPDATED to match ro.build.version.security_patch’s value of the currently installed version, but only if the bootloader is LOCKED.
The value of rollback index is NOT dependent on the currently installed ANDROID VERSION.
The value of rollback index can NEVER be DOWNGRADED.
Rollback protection errors are FATAL when the bootloader is LOCKED.
Rollback protection errors are IGNORED when the bootloader is UNLOCKED.
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 official (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 official (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 official (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.
/quote.
The instructions tell us to unlock the bootloader in order to allow to install /e/OS.
The real danger is expressed
Rollback protection errors are FATAL when the bootloader is LOCKED.
Rollback protection errors are IGNORED when the bootloader is UNLOCKED.
Rollback protection errors + user locks the Bootloader; the phone is bricked.
Rollback protection errors + user does not relock the Bootloader; the error is ignored.
leave the bootloader unlocked at least until I installed /e/os with newer Security Patch date as previous installed Android (in my case January 5th 2025)