Does that
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 NOT dependent on the currently installed ANDROID VERSION.”</em
mean I can install the latest stable version of e/os on my fp 5 with android 14…?
This means that you do not need to be concerned about Android version … while you are considering “rollback”.
There is some compartmentalisation of thoughts required.
Hm. I am still confused.
My device is fp5 with android 14 patch 05. of march 2025.
The T-Version is (as headlined) android 13 with patch of the same date.
The U-Version is for android 14 with patchdate 01. of march 2025.
Does the T-Version downgrade my OS to android 13 with latest patchversion. And I may lock the bootloader after installing?
Or do I have to take U-Version without locking in the end?
I would prefer stabel-version. And I would prefer to lock the bootloader.
Fine … so do not think or talk about the alternatives.
Yes, of course as shown e/OS + Android OS version names and numbers? - #3 by aibd
Ok. Paranoid-mode off! When I choose to life with an unlocked bootloader, I can install “any” custom ROM for example e\os 2.9 stable, without worrying about “anti-rollback-bricking”. Did I get that right?
@aibd cited the documentation at (answered) Install /e/ on FP5 with newer Security Patches - #2 by aibd in full, the examples should give you a good intuition?
In the unlocked mode it doesn’t matter, but once you want to relock, if the patch level (android security patch date - not android version) is behind what was last recorded during the locked state, you’ll brick the phone.
Note down your patch level date and wait until /e/OS supplies a release past the patch date on any Android Version you want, then you can safely relock.
Cool cool cool! Thanx