From d95a7fe1d5f9efafa544b6e6ac5fedac7a2b7db0 Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Thu, 9 May 2019 16:17:33 -0400 Subject: add more header ids for usage in links --- static/install.html | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) (limited to 'static/install.html') diff --git a/static/install.html b/static/install.html index 11c94ceb..53287bcc 100644 --- a/static/install.html +++ b/static/install.html @@ -33,8 +33,8 @@
-

Install

-

Prerequisites

+

Install

+

Prerequisites

You should have at least 2GB of free memory available.

You need the unlocked variant of one of the supported devices, not a locked carrier specific variant.

@@ -50,20 +50,20 @@ do not have support for current devices. Very old versions of fastboot from several years ago are still shipped by Linux distributions like Debian and lack the compatibility detection of modern versions so they can soft brick devices.

-

Enabling OEM unlocking

+

Enabling OEM unlocking

OEM unlocking needs to be enabled from within the operating system.

Enable the developer settings menu by going to Settings ➔ System ➔ About phone and pressing on the build number menu entry until developer mode is enabled.

Next, go to Settings ➔ System ➔ Advanced ➔ Developer settings and toggle on the 'Enable OEM unlocking' setting. This requires internet access on devices with Google Play Services.

-

Unlocking the bootloader

+

Unlocking the bootloader

First, boot into the bootloader interface. You can do this by turning off the device and then turning it on by holding both the Volume Down and Power buttons.

The bootloader now needs to be unlocked to allow flashing new images:

fastboot flashing unlock

The command needs to be confirmed on the device.

-

Obtaining factory images

+

Obtaining factory images

The initial install will be performed by flashing the factory images. This will replace the existing OS installation and wipe all the existing data.

You can download the factory images from the releases page.

@@ -71,7 +71,7 @@
gpg --recv-keys 65EEFE022108E2B708CBFCF7F9E712E59AF5F22A
 gpg --verify blueline-factory-2019.04.01.19.zip.sig blueline-factory-2019.04.01.19.zip

When this signing key is replaced, the new key will be signed with it.

-

Flashing factory images

+

Flashing factory images

Next, extract the factory images and run the script to flash them. Note that the fastboot command run by the flashing script requires a fair bit of free space in a temporary directory, which defaults to /tmp:

@@ -86,7 +86,7 @@ TMPDIR="$PWD/tmp" ./flash-all.sh new operating system.

You should now proceed to locking the bootloader before using the device as locking wipes the data again.

-

Locking the bootloader

+

Locking the bootloader

Locking the bootloader is important as it enables full verified boot. It also prevents using fastboot to flash, format or erase partitions. Verified boot will detect modifications to any of the OS partitions (vbmeta, boot/dtbo, product, system, @@ -99,10 +99,10 @@ TMPDIR="$PWD/tmp" ./flash-all.sh

The command needs to be confirmed on the device since it needs to perform a factory reset.

Unlocking the bootloader again will perform a factory reset.

-

Disabling OEM unlocking

+

Disabling OEM unlocking

OEM unlocking can be disabled again in the developer settings menu within the operating system after booting it up again.

-

Replacing GrapheneOS with the stock OS

+

Replacing GrapheneOS with the stock OS

Installation of the stock OS via the stock factory images is the same process described above. However, before locking, there's an additional step to fully revert the device to a clean factory state on modern devices with Android Verified Boot 2.0 -- cgit v1.3.1