Daniel Micay
Daniel Micay
You'll need to rebase this since a gradle-verification metadata error had to be fixed.
If the newly flashed firmware fails to boot, the device will switch back to the other slot. It only gets bricked when there's invalid firmware flashed to both slots. Only...
https://github.com/GrapheneOS/fastboot.js/commit/e7a940378ccb570a3765b16c30d318cf87674ae8 mostly resolves this but results in higher storage usage which isn't exactly great but it's much better than the current memory usage overall.
It has significantly lower memory usage than Google's flashing tool but dramatically higher storage use.
The storage usage was already quite high before this change but it does increase the peak storage. Worth noting that the browser can and does choose to store the blobs...
Ideally it would partially store the blobs in memory instead of it being all or nothing but Chromium doesn't support that.
There's a first run job to get the initial pairing done with extremely high priority so users don't need to wait for it to appear even if they're in battery...
Did you connect to the internet already? Try clearing Auditor data and trying again. This looks like a firmware issue rather than something GrapheneOS specific.
Not directly, but an internet connection is needed for remote key provisioning to update the the hardware attestation keys. It can work without that but perhaps not after a factory...
One of these 4 depending on GeoIP: https://grapheneos.org/articles/grapheneos-servers#grapheneos.network