nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq9zsljfx8tjyzplququr9xmqctclx0qc2mw5xydzx0udqzrfade4qmtrtl5 (nprofile…rtl5) nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq8ms44c64c3nvvxgx0wvlm7djwur43w58872epgf2k7m5gvyr7wlsyypkaf (nprofile…pkaf) nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqum3rezpjzv76kzeyawsf5plw8fp7l9gysd34gdncvxyfm0qhu5ws0zulnl (nprofile…ulnl) Firmware anti-rollback can't be tripped without either having the device unlocked in fastboot mode or having an OS exploit.
The firmware and OS images are stored in dedicated partitions on the SSD. There are 2 of each partition for A/B updates. Only the inactive partitions are written by updates. After updating, the device attempts to boot the new firmware/OS images and automatically and automatically rolls back if it doesn't boot. Post-update boot is very safe.
GrapheneOS
npub123…g0ht5
2026-08-03 21:14:56 UTC
in reply to nevent1q…fvrz
Author Public Key
npub1235tem4hfn34edqh8hxfja9amty73998f0eagnuu4zm423s9e8ksdg0ht5Seen on
wss://relay.ditto.pubPublished at
2026-08-03 21:14:56 UTCEvent JSON
{
"id": "86680d43af889bb9d207b6e064a70739cfe1aedf513e271f81527874128f962f",
"pubkey": "5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed",
"created_at": 1785791696,
"kind": 1,
"tags": [
[
"p",
"28a1f924c75c8820fc1c0706536c185e3e67830adba86234467f1a010d3d6e6a",
"wss://relay.ditto.pub"
],
[
"p",
"3ee15ae355c466c619067b99fdf9b2770758ba873f9590a12ab7b7443083f3bf",
"wss://relay.ditto.pub"
],
[
"p",
"e6e23c8832133dab0b24eba09a07ee3a43ef9504836354367861889dbc17e51d",
"wss://relay.ditto.pub"
],
[
"p",
"e97cafa82a7dd144bb2ec1089abea1190be419346e906bf69f0bc243f01586fc",
"wss://relay.ditto.pub"
],
[
"p",
"0f8f8ac2c2ead9c28aae0bcc5ddaadbf7a47aeb06aa4126d7f43d6cd8dd3c5c3",
"wss://relay.ditto.pub"
],
[
"p",
"f937d30ae108b539348c9ef330cf2a89684c28999acb01956c87367ecdd07cc7",
"wss://relay.ditto.pub"
],
[
"e",
"76675b6900e9fcb8618cbc97dc4a1e90048a076ac82501df819983ea217c1fe9",
"wss://relay.ditto.pub",
"reply"
],
[
"proxy",
"https://grapheneos.social/users/GrapheneOS/statuses/117033644627557088",
"activitypub"
],
[
"client",
"Mostr",
"31990:6be38f8c63df7dbf84db7ec4a6e6fbbd8d19dca3b980efad18585c46f04b26f9:mostr",
"wss://relay.ditto.pub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq9zsljfx8tjyzplququr9xmqctclx0qc2mw5xydzx0udqzrfade4qmtrtl5 nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpq8ms44c64c3nvvxgx0wvlm7djwur43w58872epgf2k7m5gvyr7wlsyypkaf nostr:nprofile1qy2hwumn8ghj7un9d3shjtnyd968gmewwp6kyqpqum3rezpjzv76kzeyawsf5plw8fp7l9gysd34gdncvxyfm0qhu5ws0zulnl Firmware anti-rollback can't be tripped without either having the device unlocked in fastboot mode or having an OS exploit.\n\nThe firmware and OS images are stored in dedicated partitions on the SSD. There are 2 of each partition for A/B updates. Only the inactive partitions are written by updates. After updating, the device attempts to boot the new firmware/OS images and automatically and automatically rolls back if it doesn't boot. Post-update boot is very safe.",
"sig": "ffe109c350ee9e19b7b1efad74e37c2297b138e009fb57ae67ba74e49667a397140a032d4c162970733d5878a1214130b583f5ed9827e6aed20c3a6a47b56753"
}