Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update on device with bootloader that has been relocked #19

Open
andrewathalye opened this issue Apr 8, 2022 · 1 comment
Open

Update on device with bootloader that has been relocked #19

andrewathalye opened this issue Apr 8, 2022 · 1 comment

Comments

@andrewathalye
Copy link

andrewathalye commented Apr 8, 2022

Hello, I apologise if this is meant to be easy to resolve, but I cannot find a way to update the device if its bootloader has been relocked after installing ProtonAOSP. Is this intentional? Having to wipe data every time to update isn't a particularly user-friendly experience. If it is possible to produce OTA files like Google's, which seem to be signed with the secure boot key to allow them to be installed without unlocking, that would be ideal.

@parcelcat
Copy link

parcelcat commented May 17, 2022

The documentation on verified boot doesn't mention that re-locking the bootloader would prevent updates until the bootloader is unlocked again, which requires wiping all data. That came as a shock to me, since I had wrongly assumed that ProtonAOSP's web installer would support updates on devices with locked bootloaders (with the ProtonAOSP key).

ProtonAOSP should ideally support OTA updates on devices with locked bootloaders like GrapheneOS and CalyxOS do. It's too inconvenient for most people to wipe and set up a personal device every month. Until then, the documentation should warn the user that updates are not currently possible when the bootloader is locked. The FAQ should also be updated, since this section also does not make clear that locking the bootloader would prevent security updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants