Security Fixes / Patches - A13 - T

[Lobster]

Hi dear community,

I’ve just made the update to 3.7-t-official (FP3+). On the release note, it states “Security patches are no longer available for AOSP 13.”.

What are the implications for using this phone as my daily driver ? Is there any concerns to worry about ? Any tricks to do ?

If moving to community build in between official gets Android upgrade, will I be able to reverse to official later on ? Any data loss in any case ?

Thanks for your support !

Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services

[tcecyk]

you can move between the release channels, but it implies a user-data reset (data loss) when the phone is locked and needs to be un/relocked. You need to use the same versions / or ahead in target to hop over because of rollback protection.

implications: do you do something that anyone would spend a non trivial amount of money to target you? if not, have apps and browser updated and if you can, weed unneeded apps.

the ETA on A13-A15 of this week for official:

@Manoj

• FP3 - FP3 - A13 → A15 (ETA 1- 2 months)

(In general, I’m sceptical of the “2 more years of support for FP3” by murena as in: I don’t think this includes the firmware bits)

[piero]

UNOFFICIAL TIP :

@piero

if coming from an already installed “official” /e/OS and you want to upgrade to a15 “community” (without loosing data and locked bootloader)

• using → Settings → System updater → Local_update
• or using “recovery mode” and “adb sideload”

you will face a signature mismatch, simply choose “install anyway”
A clear guide to Upgrade your /e/OS to a new Android major version without loosing /data

Files for upgrading an existing /e/ system via local update or the /e/ recovery can be found here:

https://ota.ecloud.global/api/v1/FP3/community/

…

@urs_lesse

Here is my report of how I switched an FP3 from T-official to A15-community: https://community.e.foundation/t/feedback-for-v3-1-1/73830/46?u=urs_lesse As I remember, data was taken over and not reset – I did not need to change the (locked) bootloader, so no factory reset was triggered.

@piero

@Lobster

Is it possible to reverse to official whenever available later on ?

there is yet no feedback about reverting from “community” to “official” without data loss…
But switching back to “official” with a new install (and data loss) will be possible if the command
fastboot flashing get_unlock_ability is able to return 1.
(check the possibility to enable the “allow OEM unlock” option in “–> Settings → system → Developper Options”) NEVER DISABLE IT !

[aibd]

I would suggest change to community for this device … except it will depend if you have specific requirements of a locked bootloader and no root debugging. A discussion about bootloader locking/unlocking… AKA I want to relock my bootloader, should I?

[tcecyk]

(if the images are signed by different keys, why does it work while locked? need to download the images and find out I guess)

[piero]

Maybe @urs_lesse had chance with his starting point,

@urs_lesse

Not the recommended way

i just remember some “official” OTA builds are labeled “upgradable”

https://ota.ecloud.global/api/v1/FP3/official/

like 1.20-s