diff options
| author | Charles <c4a@monocles.eu> | 2025-04-15 12:58:12 -0400 |
|---|---|---|
| committer | Daniel Micay <daniel.micay@grapheneos.org> | 2025-04-15 12:58:55 -0400 |
| commit | ef4b2867827208f4b276d96632aed391213ba1ed (patch) | |
| tree | 03f163c42bc3153000e525cae659c3e03f6c420a /static/install/web.html | |
| parent | 7a82318fbeb2848d3ab807db14a44452fadcecdf (diff) | |
install: add supported devices link
Diffstat (limited to 'static/install/web.html')
| -rw-r--r-- | static/install/web.html | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/static/install/web.html b/static/install/web.html index eaa9d655..9836d20d 100644 --- a/static/install/web.html +++ b/static/install/web.html @@ -147,16 +147,16 @@ prevent the web installer from having enough storage space to extract the downloaded release.</p> - <p>You need one of the officially supported devices. To make sure that the device can - be unlocked to install GrapheneOS, avoid carrier variants of the devices. Carrier - variants of Pixels use the same stock OS and firmware with a non-zero carrier id - flashed onto the persist partition in the factory. The carrier id activates - carrier-specific configuration in the stock OS including disabling carrier and - bootloader unlocking. The carrier may be able to remotely disable this, but their - support staff may not be aware and they probably won't do it. Get a carrier agnostic - device to avoid the risk and potential hassle. If you CAN figure out a way to unlock a - carrier device, it isn't a problem as GrapheneOS can just ignore the carrier id - and the hardware is the same.</p> + <p>You need one of the <a href="/faq#supported-devices">officially supported + devices</a>. To make sure that the device can be unlocked to install GrapheneOS, + avoid carrier variants of the devices. Carrier variants of Pixels use the same stock + OS and firmware with a non-zero carrier id flashed onto the persist partition in the + factory. The carrier id activates carrier-specific configuration in the stock OS + including disabling carrier and bootloader unlocking. The carrier may be able to + remotely disable this, but their support staff may not be aware and they probably + won't do it. Get a carrier agnostic device to avoid the risk and potential hassle. + If you CAN figure out a way to unlock a carrier device, it isn't a problem as + GrapheneOS can just ignore the carrier id and the hardware is the same.</p> <p>It's best practice to update the device before installing GrapheneOS to have the latest firmware for connecting the device to the computer and performing the |