Installing GrapheneOS on a Pixel phone

Installing GrapheneOS on a Pixel phone is the process of replacing the stock operating system on a supported Google Pixel device with GrapheneOS, a free and open source mobile operating system built on the Android Open Source Project with a focus on privacy and security. The project offers a browser-based web installer that most people can complete in under an hour with a computer, a USB-C cable, and a compatible phone. This page explains what the system does, what is needed, how the installation works step by step, how to verify the result, and how to set up the phone for daily use afterward.

This page is a general overview of the installation process for readers who want to understand what is involved. For an actual installation, follow the official GrapheneOS install guide, because steps, supported devices, and requirements change often. Last checked against the official documentation in October 2026.

Why people choose GrapheneOS

Most phones ship with an operating system that includes privileged vendor services. GrapheneOS removes that privileged layer and adds controls that give the owner more say over what each app can reach. Examples documented by the project include:

• A Network permission toggle that can block an app from all network access, including access to the device-local network.
• A Sensors permission toggle that blocks access to sensors such as the accelerometer, gyroscope, and compass that standard Android does not gate behind a permission. Apps that are denied receive zeroed data.
• Storage Scopes and Contact Scopes, which let an app run as if it had storage or contacts access while only seeing the specific files or contacts the user chooses.
• Sandboxed Google Play, an optional compatibility layer that runs the official Google Play apps as ordinary sandboxed apps with no special privileges, installed only in the profile where the user wants them.

The practical result is that a person can keep using most mainstream apps while deciding app by app what data and hardware each one may touch. For students, journalists, small business owners, and anyone who handles sensitive client work on a phone, this is a concrete way to reduce exposure without giving up a modern smartphone.

What you need before starting

A supported device

GrapheneOS supports a specific list of recent Pixel phones and tablets, because the project relies on hardware security features such as a secure element, verified boot with user-installable keys, and long-term firmware updates. The supported list changes as new models are added and old ones reach end of support, so check the official FAQ before buying.

Buy a carrier-agnostic (unlocked) model. The installer guide warns that carrier variants of Pixels can have bootloader unlocking disabled by the carrier, which can block installation entirely. A used phone can be a cost-effective option, as long as it is a supported model, is not a carrier-locked variant, and has OEM unlocking available.

A computer, browser, and cable

The web installer runs in a Chromium-based browser that supports WebUSB, such as Google Chrome, Chromium, Microsoft Edge, or Brave with Shields turned off. Official guidance at the time of writing calls for a computer with at least 2 GB of free memory and 32 GB of free storage, running a current version of Windows, macOS, ChromeOS, or a mainstream Linux distribution. The installer can even run from another Android device.

Two common causes of failure are worth planning around:

• Cables and hubs. Use a good USB-C cable, ideally the one that came with the phone, and plug directly into the computer rather than into a hub or a desktop front panel.
• Browser modes. Do not use Incognito or private browsing, and avoid Snap or Flatpak versions of browsers, because these often lack the storage space or USB access the installer needs.

A backup

Installation wipes all data on the phone more than once. Before starting, copy photos, documents, and any two-factor authentication codes somewhere safe. Moving authenticator codes is the step people most often forget, and it can lock someone out of accounts.

Step-by-step installation

The following summarizes the official web installer flow. Keep the official page open while working, because it contains the buttons that drive each step and may have updates.

1. Update the stock OS. Install the latest stock updates first so the phone has current firmware for the early flashing process.
2. Enable OEM unlocking. Go to Settings, then About phone, and tap Build number repeatedly until developer mode is enabled. Then go to Settings, System, Developer options, and turn on OEM unlocking. On some models this requires an internet connection so the phone can check whether it was sold carrier-locked.
3. Prepare Linux, if used. On Debian or Ubuntu, install the android-sdk-platform-tools-common package, and on Arch Linux install android-udev, so the browser can talk to the phone without root. If an error says the device is already claimed, temporarily stop the fwupd service.
4. Boot into the bootloader. Turn the phone off, then power it on while holding the volume down button. The step is complete when a red warning triangle and the words Fastboot Mode appear. Do not press Start.
5. Connect and unlock. Connect the phone to the computer, press Unlock bootloader on the installer page, and confirm on the phone using the volume keys and power button. This wipes the device.
6. Download the release. Press Download release. The installer fetches the factory images for the connected model.
7. Flash the release. Press Flash release and do not touch the phone until the process finishes. It flashes firmware, reboots into the bootloader, and flashes the operating system automatically.
8. Lock the bootloader. Press Lock bootloader and confirm on the phone. Locking matters because it enables full verified boot, which detects modifications to the operating system, and it prevents anyone from reflashing partitions over USB.
9. Boot and finish setup. Press the power button with Start selected. During first setup, leave the final toggle checked so that OEM unlocking is disabled again.

Windows users on current versions of Windows 10 or 11 normally do not need an extra driver for recent Pixels. If the browser cannot see the phone, the guide explains how to get the bootloader driver through Windows Update optional updates.

Verifying the installation

After installing an alternate operating system, a supported Pixel shows a yellow notice at boot with an identifier derived from the verified boot public key. On 6th generation Pixels and newer, the full hash is displayed and can be compared against the official values published on the installer page.

For a stronger check, GrapheneOS provides the Auditor app, which uses hardware-based attestation to confirm that the hardware, firmware, and operating system are genuine. Auditor needs a second Android device to scan a QR code from the phone being checked, and an optional remote monitoring service is also offered. Verification is optional for daily use, but it is a good learning exercise in how chains of trust work in modern hardware.

Setting up for daily use

A fresh installation contains a small set of core apps, including the Vanadium browser and a camera app. A practical setup plan looks like this:

• Decide on Google Play. Install sandboxed Google Play from the built-in App Store only if needed apps depend on it. Many banking and transit apps do, and the usage guide explains that setting up sandboxed Google Play in the same profile is often enough for them.
• Use profiles to separate life areas. Secondary user profiles and a work profile can isolate apps. A common pattern is an owner profile with privacy-respecting apps and a second profile that holds Google Play and apps that require it.
• Review permissions when installing each app. Turn off Network for offline tools such as a calculator, notes app, or offline maps, and deny Sensors unless an app clearly needs them.
• Configure location. The usage guide describes a network location option that can use a GrapheneOS proxy, which helps faster location fixes without relying on Google services.
• Keep updates on. GrapheneOS ships updates over the air and lists them on its releases page. Installing them promptly is the single most effective security habit.

Limits and tradeoffs

GrapheneOS is not a magic shield, and an informed choice includes knowing the costs:

• Hardware choice is narrow. Only supported Pixel models can be used.
• Some apps will not run. A minority of apps, especially some banking apps with anti-tampering checks, refuse to work on alternate operating systems. The usage guide discusses known workarounds, but none are guaranteed.
• Some Google features are missing. Features that depend on privileged Google integration may be absent or limited.
• Behavior still matters. An app that is granted broad permissions can still collect what it is given. The operating system gives control; the owner has to use it.

Learning and career value

Installing and running GrapheneOS teaches transferable skills: reading official technical documentation carefully, understanding bootloaders, firmware, verified boot and attestation, practicing safe backups, and applying the principle of least privilege to everyday software. These are the same concepts used in mobile device management, security operations, and IT support roles. Someone who can explain why a locked bootloader matters, or set up a separated work profile for a small team, has a skill that employers and clients value. Writing up the process as a short guide or offering setup help to local businesses is a realistic way to turn the knowledge into income or a portfolio piece.

The same mindset of owning one's tools connects to running software locally, as described in local AI as a public library, and to keeping knowledge in durable, user-controlled places, as covered in permaweb basics and local-first wikis.

See also

• Privacy
• Open source
• Linux
• Local AI as a public library
• Local-first wiki and Git mirrors
• Permaweb basics

Discussion questions, essay ideas, and learning related AI prompt ideas

Discussion questions

• Why does locking the bootloader after installation improve security, and what would an attacker be able to do if it stayed unlocked?
• What are the tradeoffs between installing sandboxed Google Play and going without it?
• How should a person decide which apps deserve network access or sensor access?
• Why might buying a carrier-locked phone block a privacy-focused installation?

Essay ideas

• Compare the trust model of a stock smartphone with the trust model of GrapheneOS, using verified boot and attestation as examples.
• Write a practical guide for a small office that wants separated work and personal profiles on staff phones.
• Discuss how owning and controlling personal devices relates to broader goals of freedom technology and digital self-reliance.

Learning related AI prompt ideas

• Explain verified boot and hardware attestation to me as if I were a beginner, then quiz me with five questions.
• Help me make a checklist for backing up a phone before wiping it, including two-factor authentication codes.
• Walk me through deciding which permissions to grant to a list of apps I use, asking me what each app needs to do.
• Suggest a study plan that uses GrapheneOS setup as a starting point for learning mobile security for an IT support career.