I Put GrapheneOS on a Pixel. Here’s Why It Matters.
Phone Repair Guru · Software & Privacy
The red phone in my video looks pretty ordinary. What makes it interesting is the software running on it and how much control it gives back to the person holding it.
It's called GrapheneOS. In my Short, I show it running on a Pixel and demonstrate how it can be installed through a browser. I also explain why its future raises bigger questions about phone ownership. There's a lot packed into those 37 seconds, so here's the longer version.
What Even Is GrapheneOS?
GrapheneOS is an operating system focused on privacy and security. It's built on the Android Open Source Project (AOSP) and replaces the operating system on a supported device. It's much more than installing a privacy app or changing your home screen.
The project dates back to late 2014 when security researcher Daniel Micay founded it. Since then, it has focused on strengthening the software that runs beneath the apps we use every day. You can learn more about its origins in the official project history.
The Security Features Are the Interesting Part
What catches my attention is the extra control. GrapheneOS includes protections designed to make software vulnerabilities harder to exploit. It also provides tools that let you decide what your apps can access.
GrapheneOS gives users greater control over permissions such as camera and microphone access.
- Network controls: Prevent individual apps from accessing the internet using a dedicated permission toggle.
- Storage and Contact Scopes: Allow apps to access selected files or contacts instead of giving them access to everything.
- Sandboxed Google Play: Install Google Play as regular sandboxed apps without granting them the special system privileges they normally receive.
These features are explained in the official GrapheneOS documentation. No phone is impossible to hack, but GrapheneOS aims to make attacks harder while giving users more control over their devices.
Yes, You Can Install It From a Browser
In the video, I demonstrate the web installation process. The official installer allows you to install GrapheneOS using a compatible browser and a USB connection.
You'll need a supported device with an unlockable bootloader. Keep in mind that a phone being SIM unlocked doesn't necessarily mean its bootloader can be unlocked.
The official web installer guides users through installing GrapheneOS on a supported device.
One important detail deserves more attention. Unlocking the bootloader is part of the installation process, but relocking it is just as important.
According to the official instructions, relocking the bootloader enables full verified boot. This helps verify the integrity of the operating system when the phone starts.
The bootloader is unlocked during installation and relocked afterward to restore full verified boot.
Installing GrapheneOS replaces the existing operating system and erases the phone's data. Before starting, back up anything important and check the official supported device list.
Device support can change over time, so don't assume every Pixel model is compatible.
Why I Said Its Future Could Be Under Threat
This is where things get interesting. In the video, I mention Google removing Pixel support from AOSP. I'm referring to the device support materials developers use to build operating systems for Pixel hardware.
GrapheneOS has documented its efforts to reimplement Pixel support following that removal. You can find details in the project's official release notes.
Changes to Pixel support in AOSP have created additional work for developers of alternative Android operating systems.
This creates additional work for the project, but it doesn't mean GrapheneOS has stopped working or that every Pixel bootloader has been locked down. The project continues to publish installation instructions and a list of supported devices.
My concern is how much alternative operating systems depend on hardware manufacturers allowing users to install different software. Having that freedom is an important part of owning a device.
The Duress PIN Controversy
At the end of my Short, I mention a federal case involving a phone wipe.
In July 2026, Ars Technica reported that Samuel Tunick faced a federal charge after allegedly giving border agents a GrapheneOS duress code that erased his phone.
It's important to distinguish the allegation from a finding of guilt.
GrapheneOS includes a duress PIN and password feature that irreversibly wipes the device when entered. The case has brought legal scrutiny to this privacy feature, but it doesn't establish that GrapheneOS itself is banned.
Why This Matters to Me
I spend a lot of time showing what's possible when we open up our devices. Software deserves that same curiosity. Choosing what runs on a phone is another way to take ownership of it.
I want the option to change the software on a phone I own to remain available.
GrapheneOS makes that conversation tangible. In my video, it's a red Pixel on a repair bench. Behind it is a much bigger question: How much say should we have over the devices we buy?