Skip to content

Commit ef4b286

Browse files
Charlesthestinger
authored andcommitted
install: add supported devices link
1 parent 7a82318 commit ef4b286

File tree

2 files changed

+20
-20
lines changed

2 files changed

+20
-20
lines changed

static/install/cli.html

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -149,16 +149,16 @@ <h2><a href="#prerequisites">Prerequisites</a></h2>
149149
from Android, ChromeOS and GrapheneOS itself since it can run anywhere with a
150150
browser with working WebUSB support.</p>
151151

152-
<p>You need one of the officially supported devices. To make sure that the device can
153-
be unlocked to install GrapheneOS, avoid carrier variants of the devices. Carrier
154-
variants of Pixels use the same stock OS and firmware with a non-zero carrier id
155-
flashed onto the persist partition in the factory. The carrier id activates
156-
carrier-specific configuration in the stock OS including disabling carrier and
157-
bootloader unlocking. The carrier may be able to remotely disable this, but their
158-
support staff may not be aware and they probably won't do it. Get a carrier agnostic
159-
device to avoid the risk and potential hassle. If you CAN figure out a way to unlock a
160-
carrier device, it isn't a problem as GrapheneOS can just ignore the carrier id
161-
and the hardware is the same.</p>
152+
<p>You need one of the <a href="/faq#supported-devices">officially supported
153+
devices</a>. To make sure that the device can be unlocked to install GrapheneOS,
154+
avoid carrier variants of the devices. Carrier variants of Pixels use the same stock
155+
OS and firmware with a non-zero carrier id flashed onto the persist partition in the
156+
factory. The carrier id activates carrier-specific configuration in the stock OS
157+
including disabling carrier and bootloader unlocking. The carrier may be able to
158+
remotely disable this, but their support staff may not be aware and they probably
159+
won't do it. Get a carrier agnostic device to avoid the risk and potential hassle.
160+
If you CAN figure out a way to unlock a carrier device, it isn't a problem as
161+
GrapheneOS can just ignore the carrier id and the hardware is the same.</p>
162162

163163
<p>It's best practice to update the device before installing GrapheneOS to have
164164
the latest firmware for connecting the device to the computer and performing the

static/install/web.html

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -147,16 +147,16 @@ <h2><a href="#prerequisites">Prerequisites</a></h2>
147147
prevent the web installer from having enough storage space to extract the
148148
downloaded release.</p>
149149

150-
<p>You need one of the officially supported devices. To make sure that the device can
151-
be unlocked to install GrapheneOS, avoid carrier variants of the devices. Carrier
152-
variants of Pixels use the same stock OS and firmware with a non-zero carrier id
153-
flashed onto the persist partition in the factory. The carrier id activates
154-
carrier-specific configuration in the stock OS including disabling carrier and
155-
bootloader unlocking. The carrier may be able to remotely disable this, but their
156-
support staff may not be aware and they probably won't do it. Get a carrier agnostic
157-
device to avoid the risk and potential hassle. If you CAN figure out a way to unlock a
158-
carrier device, it isn't a problem as GrapheneOS can just ignore the carrier id
159-
and the hardware is the same.</p>
150+
<p>You need one of the <a href="/faq#supported-devices">officially supported
151+
devices</a>. To make sure that the device can be unlocked to install GrapheneOS,
152+
avoid carrier variants of the devices. Carrier variants of Pixels use the same stock
153+
OS and firmware with a non-zero carrier id flashed onto the persist partition in the
154+
factory. The carrier id activates carrier-specific configuration in the stock OS
155+
including disabling carrier and bootloader unlocking. The carrier may be able to
156+
remotely disable this, but their support staff may not be aware and they probably
157+
won't do it. Get a carrier agnostic device to avoid the risk and potential hassle.
158+
If you CAN figure out a way to unlock a carrier device, it isn't a problem as
159+
GrapheneOS can just ignore the carrier id and the hardware is the same.</p>
160160

161161
<p>It's best practice to update the device before installing GrapheneOS to have
162162
the latest firmware for connecting the device to the computer and performing the

0 commit comments

Comments
 (0)