Security risk with official /e/OS v3.7 for Pixel 5?

[piero]

Week 17, Development and Testing Updates

UNOFFICIAL TIP : if coming from an already installed “official” /e/OS and you want to upgrade to a16 “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 …

/e/OS community redfin download

Week 17, Development and Testing Updates

@Lobster I guess you are on an FP3, so the download link would be at https://ota.ecloud.global/api/v1/FP3/community/. 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.

Week 17, Development and Testing Updates

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 !