Final on Nostr: > If graphene messes up a build, you can't even return to stock because you turned ...
> If graphene messes up a build, you can't even return to stock because you turned that switch off.
The devices we support use two separate system partitions (A / B) and updates are installed on the other and then swapped to the other when restarted, if the update fails/is corrupt then it rolls back to the previous working install on the last-used partition. Same method is used when Google saves their users with corrupt updates.
We would want the bootloader locked else anyone can flash malicious updates on any OS. Unauthorised person factory resetting by recovery is good for us as that means the user's sensitive data is destroyed. We prefer this data destruction over the Factory Reset Protection the Stock OS wants to have.
The devices we support use two separate system partitions (A / B) and updates are installed on the other and then swapped to the other when restarted, if the update fails/is corrupt then it rolls back to the previous working install on the last-used partition. Same method is used when Google saves their users with corrupt updates.
We would want the bootloader locked else anyone can flash malicious updates on any OS. Unauthorised person factory resetting by recovery is good for us as that means the user's sensitive data is destroyed. We prefer this data destruction over the Factory Reset Protection the Stock OS wants to have.