summaryrefslogtreecommitdiff
path: root/static/install/cli.html
diff options
context:
space:
mode:
Diffstat (limited to 'static/install/cli.html')
-rw-r--r--static/install/cli.html20
1 files changed, 10 insertions, 10 deletions
diff --git a/static/install/cli.html b/static/install/cli.html
index edcf05b1..5927096b 100644
--- a/static/install/cli.html
+++ b/static/install/cli.html
@@ -149,16 +149,16 @@
from Android, ChromeOS and GrapheneOS itself since it can run anywhere with a
browser with working WebUSB support.</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