3 ms·

You don't want to buy a phone pre-flashed with GrapheneOS, this was the problem with CopperheadOS - they would only flash the phone if you sent it to them (unat

You don't want to buy a phone pre-flashed with GrapheneOS, this was the problem with CopperheadOS - they would only flash the phone if you sent it to them (unattended, across 2+ customs borders) - apparently that caused some internal strife. Seriously though, pick up a Pixel 6, flash it at home via Web-USB. My only qualm is that the Google bootloader doesn't show a QR code on boot to verify the kernel image being loaded, instead it simply shows a big yellow warning saying the OS is unsupported with no way of verifying if it's the GrapheneOS image you loaded or one the maid loaded while you were AFK.

616c 4y ago
Did it and on a similar pixel device and love it so much! Was super skeptical of the webusb thing as a jaded old fart (which IIRC is funded by the community) and I whistled with sheer amazement it worked perfectly the second time. First failure was BC of flakey internet with a bad download and a time crunch when another phone died. I have hated android not meeting my own personal watermark in respecting open dev and privacy forward user design at its core. This project, although not core and on the fringe, gives me a small glimmer of hope in a dark smart phone world! Been a stable daily driver for like six months now.
yellowapple 4y ago
> My only qualm is that the Google bootloader doesn't show a QR code on boot to verify the kernel image being loaded, instead it simply shows a big yellow warning saying the OS is unsupported with no way of verifying if it's the GrapheneOS image you loaded or one the maid loaded while you were AFK. Once upon a time it at least showed part of a hash or somesuch ostensibly uniquely identifying the OS, such that it would change if an Evil Maid flashed a new one.
- Schroedingersat 4y ago
  This is the type of thing that happens that happens when you make yourself dependent on someone whose goals are opposed to you by making your OS exclusively for google's phones. I honestly don't know why we can't have a system to visualise the signed image source as the default. Put any public key you want in the firmware, show a 32-64 bit fingerprint of the loaded key as an abstract pattern and only boot an image signed with that key. Manufacturer doesn't get any special treatment. Fairphone at least shows a hash on boot as well as the scary yellow text when relocked. Calyx is available, don't know about graphene.
pieresqi 4y ago
Hi, actually there is a way to verify if ROM you have installed or not is GOS. There's attestation.app which let's you remotely verify your installation.

616c 4y ago

Did it and on a similar pixel device and love it so much! Was super skeptical of the webusb thing as a jaded old fart (which IIRC is funded by the community) and I whistled with sheer amazement it worked perfectly the second time. First failure was BC of flakey internet with a bad download and a time crunch when another phone died. I have hated android not meeting my own personal watermark in respecting open dev and privacy forward user design at its core. This project, although not core and on the fringe, gives me a small glimmer of hope in a dark smart phone world! Been a stable daily driver for like six months now.

yellowapple 4y ago

> My only qualm is that the Google bootloader doesn't show a QR code on boot to verify the kernel image being loaded, instead it simply shows a big yellow warning saying the OS is unsupported with no way of verifying if it's the GrapheneOS image you loaded or one the maid loaded while you were AFK. Once upon a time it at least showed part of a hash or somesuch ostensibly uniquely identifying the OS, such that it would change if an Evil Maid flashed a new one.

Schroedingersat 4y ago
This is the type of thing that happens that happens when you make yourself dependent on someone whose goals are opposed to you by making your OS exclusively for google's phones. I honestly don't know why we can't have a system to visualise the signed image source as the default. Put any public key you want in the firmware, show a 32-64 bit fingerprint of the loaded key as an abstract pattern and only boot an image signed with that key. Manufacturer doesn't get any special treatment. Fairphone at least shows a hash on boot as well as the scary yellow text when relocked. Calyx is available, don't know about graphene.

pieresqi 4y ago

Hi, actually there is a way to verify if ROM you have installed or not is GOS. There's attestation.app which let's you remotely verify your installation.