diff options
Diffstat (limited to 'static')
| -rw-r--r-- | static/install/cli.html | 24 | ||||
| -rw-r--r-- | static/install/web.html | 22 | ||||
| -rw-r--r-- | static/js/redirect.js | 2 |
3 files changed, 25 insertions, 23 deletions
diff --git a/static/install/cli.html b/static/install/cli.html index ee45e772..dd6aae20 100644 --- a/static/install/cli.html +++ b/static/install/cli.html @@ -71,7 +71,7 @@ <li><a href="#checking-fastboot-version">Checking fastboot version</a></li> <li><a href="#flashing-as-non-root">Flashing as non-root</a></li> <li><a href="#booting-into-the-bootloader-interface">Booting into the bootloader interface</a></li> - <li><a href="#connecting-phone">Connecting the phone</a></li> + <li><a href="#connecting-device">Connecting the device</a></li> <li><a href="#unlocking-the-bootloader">Unlocking the bootloader</a></li> <li><a href="#obtaining-signify">Obtaining signify</a></li> <li><a href="#obtaining-factory-images">Obtaining factory images</a></li> @@ -156,7 +156,7 @@ 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 phone to the computer and performing the + the latest firmware for connecting the device to the computer and performing the early flashing process. Either way, GrapheneOS flashes the latest firmware early in the installation process.</p> </section> @@ -166,7 +166,7 @@ <p>OEM unlocking needs to be enabled from within the operating system.</p> - <p>Enable the developer options menu by going to Settings ➔ About phone and + <p>Enable the developer options menu by going to Settings ➔ About phone/tablet and repeatedly pressing the build number menu entry until developer mode is enabled.</p> @@ -294,32 +294,32 @@ Installed as /home/username/platform-tools/fastboot</pre> <pre>sudo apt install android-sdk-platform-tools-common</pre> <p>The udev rules on Debian and Ubuntu are very out-of-date but the package has - the rules needed for Pixel phones since the same USB IDs have been used for many + the rules needed for Pixel devices since the same USB IDs have been used for many years.</p> </section> <section id="booting-into-the-bootloader-interface"> <h2><a href="#booting-into-the-bootloader-interface">Booting into the bootloader interface</a></h2> - <p>You need to boot your phone into the bootloader interface. To do this, you need - to hold the volume down button while the phone boots.</p> + <p>You need to boot your device into the bootloader interface. To do this, you need + to hold the volume down button while the device boots.</p> - <p>The easiest approach is to reboot the phone and begin holding the volume down + <p>The easiest approach is to reboot the device and begin holding the volume down button until it boots up into the bootloader interface.</p> - <p>Alternatively, turn off the phone, then boot it up while holding the volume + <p>Alternatively, turn off the device, then boot it up while holding the volume down button during the boot process. You can either boot it with the power button or by plugging it in as required in the next section.</p> </section> - <section id="connecting-phone"> - <h2><a href="#connecting-phone">Connecting the phone</a></h2> + <section id="connecting-device"> + <h2><a href="#connecting-device">Connecting the device</a></h2> - <p>Connect the phone to the computer. On Linux, you'll need to do this again if + <p>Connect the device to the computer. On Linux, you'll need to do this again if you didn't have the udev rules set up when you connected it.</p> <p>On Linux, GNOME has a bug causing compatibility issues with the installation - process. It wrongly detects the phone in fastboot mode or fastbootd mode as being + process. It wrongly detects the device in fastboot mode or fastbootd mode as being an MTP device and claims exclusive control over it. This will block the install process from proceeding. You can run the following command to work around it:</p> diff --git a/static/install/web.html b/static/install/web.html index 1cf32f12..2a2f4727 100644 --- a/static/install/web.html +++ b/static/install/web.html @@ -55,7 +55,7 @@ <li><a href="#enabling-oem-unlocking">Enabling OEM unlocking</a></li> <li><a href="#flashing-as-non-root">Flashing as non-root</a></li> <li><a href="#booting-into-the-bootloader-interface">Booting into the bootloader interface</a></li> - <li><a href="#connecting-phone">Connecting the phone</a></li> + <li><a href="#connecting-device">Connecting the device</a></li> <li><a href="#unlocking-the-bootloader">Unlocking the bootloader</a></li> <li><a href="#obtaining-factory-images">Obtaining factory images</a></li> <li><a href="#flashing-factory-images">Flashing factory images</a></li> @@ -151,7 +151,7 @@ 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 phone to the computer and performing the + the latest firmware for connecting the device to the computer and performing the early flashing process. Either way, GrapheneOS flashes the latest firmware early in the installation process.</p> </section> @@ -161,7 +161,7 @@ <p>OEM unlocking needs to be enabled from within the operating system.</p> - <p>Enable the developer options menu by going to Settings ➔ About phone and + <p>Enable the developer options menu by going to Settings ➔ About phone/tablet and repeatedly pressing the build number menu entry until developer mode is enabled.</p> @@ -190,25 +190,25 @@ <section id="booting-into-the-bootloader-interface"> <h2><a href="#booting-into-the-bootloader-interface">Booting into the bootloader interface</a></h2> - <p>You need to boot your phone into the bootloader interface. To do this, you need - to hold the volume down button while the phone boots.</p> + <p>You need to boot your device into the bootloader interface. To do this, you need + to hold the volume down button while the device boots.</p> - <p>The easiest approach is to reboot the phone and begin holding the volume down + <p>The easiest approach is to reboot the device and begin holding the volume down button until it boots up into the bootloader interface.</p> - <p>Alternatively, turn off the phone, then boot it up while holding the volume + <p>Alternatively, turn off the device, then boot it up while holding the volume down button during the boot process. You can either boot it with the power button or by plugging it in as required in the next section.</p> </section> - <section id="connecting-phone"> - <h2><a href="#connecting-phone">Connecting the phone</a></h2> + <section id="connecting-device"> + <h2><a href="#connecting-device">Connecting the device</a></h2> - <p>Connect the phone to the computer. On Linux, you'll need to do this again if + <p>Connect the device to the computer. On Linux, you'll need to do this again if you didn't have the udev rules set up when you connected it.</p> <p>On Linux, GNOME has a bug causing compatibility issues with the installation - process. It wrongly detects the phone in fastboot mode or fastbootd mode as being + process. It wrongly detects the device in fastboot mode or fastbootd mode as being an MTP device and claims exclusive control over it. This will block the install process from proceeding. You can run the following command to work around it:</p> diff --git a/static/js/redirect.js b/static/js/redirect.js index 8bc575e0..ce5f682c 100644 --- a/static/js/redirect.js +++ b/static/js/redirect.js @@ -68,6 +68,8 @@ const redirects = new Map([ ["/install/#disabling-oem-unlocking", "/install/cli#disabling-oem-unlocking"], ["/install/#replacing-grapheneos-with-the-stock-os", "/install/cli#replacing-grapheneos-with-the-stock-os"], ["/install/#further-information", "/install/cli#further-information"], + ["/install/web#connecting-phone", "/install/web#connecting-device"], + ["/install/cli#connecting-phone", "/install/cli#connecting-device"], ]); function handleHash() { |