security/hakurei.app
security/hakurei.app
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 4 Wiki Activity

install: add supported devices link

Browse Source
This commit is contained in:
Charles 2025-04-15 12:58:12 -04:00 committed by Daniel Micay
parent 7a82318fbe
commit ef4b286782
2 changed files with 20 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
static/install/cli.html
View File

@ -149,16 +149,16 @@
from Android, ChromeOS and GrapheneOS itself since it can run anywhere with a from Android, ChromeOS and GrapheneOS itself since it can run anywhere with a
browser with working WebUSB support.</p> browser with working WebUSB support.</p>
<p>You need one of the officially supported devices. To make sure that the device can <p>You need one of the <a href="/faq#supported-devices">officially supported
be unlocked to install GrapheneOS, avoid carrier variants of the devices. Carrier devices</a>. To make sure that the device can be unlocked to install GrapheneOS,
variants of Pixels use the same stock OS and firmware with a non-zero carrier id avoid carrier variants of the devices. Carrier variants of Pixels use the same stock
flashed onto the persist partition in the factory. The carrier id activates OS and firmware with a non-zero carrier id flashed onto the persist partition in the
carrier-specific configuration in the stock OS including disabling carrier and factory. The carrier id activates carrier-specific configuration in the stock OS
bootloader unlocking. The carrier may be able to remotely disable this, but their including disabling carrier and bootloader unlocking. The carrier may be able to
support staff may not be aware and they probably won't do it. Get a carrier agnostic remotely disable this, but their support staff may not be aware and they probably
device to avoid the risk and potential hassle. If you CAN figure out a way to unlock a won't do it. Get a carrier agnostic device to avoid the risk and potential hassle.
carrier device, it isn't a problem as GrapheneOS can just ignore the carrier id If you CAN figure out a way to unlock a carrier device, it isn't a problem as
and the hardware is the same.</p> 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 <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 the latest firmware for connecting the device to the computer and performing the

20
static/install/web.html
View File

@ -147,16 +147,16 @@
prevent the web installer from having enough storage space to extract the prevent the web installer from having enough storage space to extract the
downloaded release.</p> downloaded release.</p>
<p>You need one of the officially supported devices. To make sure that the device can <p>You need one of the <a href="/faq#supported-devices">officially supported
be unlocked to install GrapheneOS, avoid carrier variants of the devices. Carrier devices</a>. To make sure that the device can be unlocked to install GrapheneOS,
variants of Pixels use the same stock OS and firmware with a non-zero carrier id avoid carrier variants of the devices. Carrier variants of Pixels use the same stock
flashed onto the persist partition in the factory. The carrier id activates OS and firmware with a non-zero carrier id flashed onto the persist partition in the
carrier-specific configuration in the stock OS including disabling carrier and factory. The carrier id activates carrier-specific configuration in the stock OS
bootloader unlocking. The carrier may be able to remotely disable this, but their including disabling carrier and bootloader unlocking. The carrier may be able to
support staff may not be aware and they probably won't do it. Get a carrier agnostic remotely disable this, but their support staff may not be aware and they probably
device to avoid the risk and potential hassle. If you CAN figure out a way to unlock a won't do it. Get a carrier agnostic device to avoid the risk and potential hassle.
carrier device, it isn't a problem as GrapheneOS can just ignore the carrier id If you CAN figure out a way to unlock a carrier device, it isn't a problem as
and the hardware is the same.</p> 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 <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 the latest firmware for connecting the device to the computer and performing the