has two officially supported installation methods. You can either use the WebUSB-based installer recommended for most users or the command-line installation guide aimed at more technical users.

We strongly recommend using one of the official installation methods. Third party installation guides tend to be out-of-date and often contain misguided advice and errors.

If you have trouble with the installation process, ask for help on the official GrapheneOS chat channel. There are almost always people around willing to help with it. Before asking for help, make an attempt to follow the guide on your own and then ask for help with anything you get stuck on.

The command-line approach offers a way to install GrapheneOS without trusting our server infrastructure. This requires being on an OS with proper fastboot and signify packages along with understanding the process enough to avoid blindly trusting the instructions from our site. For most users, the web-based installation approach is no less secure and avoids needing any software beyond a browser with WebUSB support.

grapheneos.org/install/

Now is interesting. It's based on , not like /e/OS technically is. The developers for Graphene have gone to ridiculous lengths to harden the system against security threats. I'll be honest, some of the stuff goes over my head. It only works on Pixels, so I pulled out the Pixel 5 I rescued from the /e/OS installation fiasco and tried it out.
tomsguide.com/features/i-tried

GrapheneOS boosted
GrapheneOS boosted

GrapheneOS is a privacy and security focused mobile OS with Android app compatibility developed as a non-profit open source project. It's focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. It was founded in 2014 and was formerly known as CopperheadOS.

improves the privacy and security of the OS from the bottom up. It deploys technologies to mitigate whole classes of vulnerabilities and make exploiting the most common sources of vulnerabilities substantially more difficult. It improves the security of both the OS and the apps running on it. The app sandbox and other security boundaries are fortified. GrapheneOS tries to avoid impacting the user experience with the privacy and security features. Ideally, the features can be designed so that they're always enabled with no impact on the user experience and no additional complexity like configuration options. It's not always feasible, and GrapheneOS does add various toggles for features like the permission, Sensors permission, restrictions when the device is locked (USB peripherals, camera, quick tiles), etc. along with more complex user-facing and features with their own UX.

grapheneos.org/

GrapheneOS boosted

Using a modern comes with some and concerns. GrapheneOS aims to solve some of those problems. It’s a custom version of Android that puts privacy and security above all else.

Custom ROMs are not as prevalent in the Android world as they used to be, but there are still some solid ones kicking around. is one such . Let’s look at this privacy and security-focused take on .

howtogeek.com/790266/what-is-g

GrapheneOS boosted
GrapheneOS boosted

GrapheneOS has official production for the following devices:

Pixel 6a (bluejay)
Pixel 6 Pro (raven)
Pixel 6 (oriole)
Pixel 5a (barbet)
Pixel 5 (redfin)
Pixel 4a (5G) (bramble)
Pixel 4a (sunfish)
Pixel 4 XL (coral)
Pixel 4 (flame)

The following devices are end-of-life, no longer receive full security updates and are supported via extended support releases of :

Pixel 3a XL (bonito)
Pixel 3a (sargo)
Pixel 3 XL (crosshatch)
Pixel 3 (blueline)

We provide extended support releases as a stopgap for users to transition to the far more secure current generation devices.

The release tags for these devices have official builds and updates available. These devices meet the stringent privacy and security standards and have substantial upstream and downstream hardening specific to the devices.

GrapheneOS has official production for the following devices:

Pixel 6a (bluejay)
Pixel 6 Pro (raven)
Pixel 6 (oriole)
Pixel 5a (barbet)
Pixel 5 (redfin)
Pixel 4a (5G) (bramble)
Pixel 4a (sunfish)
Pixel 4 XL (coral)
Pixel 4 (flame)

The following devices are end-of-life, no longer receive full security updates and are supported via extended support releases of :

Pixel 3a XL (bonito)
Pixel 3a (sargo)
Pixel 3 XL (crosshatch)
Pixel 3 (blueline)

We provide extended support releases as a stopgap for users to transition to the far more secure current generation devices.

The release tags for these devices have official builds and updates available. These devices meet the stringent privacy and security standards and have substantial upstream and downstream hardening specific to the devices.

Using a modern comes with some and concerns. GrapheneOS aims to solve some of those problems. It’s a custom version of Android that puts privacy and security above all else.

Custom ROMs are not as prevalent in the Android world as they used to be, but there are still some solid ones kicking around. is one such . Let’s look at this privacy and security-focused take on .

howtogeek.com/790266/what-is-g

GrapheneOS is a privacy and security focused mobile OS with Android app compatibility developed as a non-profit open source project. It's focused on the research and development of privacy and security technology including substantial improvements to sandboxing, exploit mitigations and the permission model. It was founded in 2014 and was formerly known as CopperheadOS.

improves the privacy and security of the OS from the bottom up. It deploys technologies to mitigate whole classes of vulnerabilities and make exploiting the most common sources of vulnerabilities substantially more difficult. It improves the security of both the OS and the apps running on it. The app sandbox and other security boundaries are fortified. GrapheneOS tries to avoid impacting the user experience with the privacy and security features. Ideally, the features can be designed so that they're always enabled with no impact on the user experience and no additional complexity like configuration options. It's not always feasible, and GrapheneOS does add various toggles for features like the permission, Sensors permission, restrictions when the device is locked (USB peripherals, camera, quick tiles), etc. along with more complex user-facing and features with their own UX.

grapheneos.org/

Mastodon Zone

We are a free speech and censorship-free zone. As long as your comments are appropriate and respectful, you won't be banned from the server. Feel free to discuss anything you want and to say whatever you want.