Smartphone targets:
List of kernels corresponding to officially supported devices:
The kernel/google/marlin repository is for the Pixel and Pixel XL, the
- kernel/google/wahoo repository is for the Pixel 2 and Pixel 2 XL and the
- kernel/google/crosshatch repository is for the Pixel 3 and Pixel 3
- XL.
For the first generation Pixel (sailfish) and Pixel XL (marlin), signed - releases require building the verity public key into the kernel so the keys need to be - generated per the instructions below before building the kernel.
+The kernel/google/wahoo repository is for the Pixel 2 and Pixel 2 XL
+ and the kernel/google/crosshatch repository is for the Pixel 3 and Pixel
+ 3 XL.
The Pixel and Pixel XL use Android Verified Boot 1.0. The Pixel 2, Pixel 2 XL, - Pixel 3, Pixel 3 XL, Pixel 3a and Pixel 3a XL use Android Verified Boot 2.0 (AVB). - Follow the appropriate instructions below.
- -For the first generation Pixel (sailfish) and Pixel XL (marlin), signed - releases require building the verity public key into the kernel, so this needs to be - done before building the kernel.
- -To generate keys for marlin (you should use unique keys per device variant):
- -mkdir -p keys/marlin -cd keys/marlin -../../development/tools/make_key releasekey '/CN=GrapheneOS/' -../../development/tools/make_key platform '/CN=GrapheneOS/' -../../development/tools/make_key shared '/CN=GrapheneOS/' -../../development/tools/make_key media '/CN=GrapheneOS/' -../../development/tools/make_key networkstack '/CN=GrapheneOS/' -../../development/tools/make_key verity '/CN=GrapheneOS/' -cd ../..- -
Generate the verity public key:
- -make -j20 generate_verity_key -out/host/linux-x86/bin/generate_verity_key -convert keys/marlin/verity.x509.pem keys/marlin/verity_key- -
Generate verity keys in the format used by the kernel for the Pixel and Pixel XL:
- -openssl x509 -outform der -in keys/marlin/verity.x509.pem -out kernel/google/marlin/verifiedboot_marlin_relkeys.der.x509- -
The same kernel and device repository is used for the Pixel and Pixel XL. There's - no separate sailfish kernel.
- -To generate keys for crosshatch (you should use unique keys per device variant):
diff --git a/static/index.html b/static/index.html index e15dec64..1f85822b 100644 --- a/static/index.html +++ b/static/index.html @@ -105,7 +105,7 @@ Device supportIn the current early stage of the project, GrapheneOS provides production releases - for the Pixel, Pixel XL, Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a and Pixel + for the Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a and Pixel 3a XL. The recommended devices with the best hardware, firmware and software security along with the longest future support time are the Pixel 3a, Pixel 3a XL, Pixel 3 and Pixel 3 XL. It will support other devices in the future, but diff --git a/static/install.html b/static/install.html index a1717290..4440735f 100644 --- a/static/install.html +++ b/static/install.html @@ -256,9 +256,7 @@ TMPDIR="$PWD/tmp" ./flash-all.sh
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 - (AVB) like the Pixel 2, Pixel 2 XL, Pixel 3, Pixel 3 XL, Pixel 3a and Pixel 3a XL. It - isn't necessary for devices with legacy verified boot like the Pixel and Pixel XL.
+ the device to a clean factory state.The GrapheneOS factory images flash a non-stock Android Verified Boot key which needs to be erased to fully revert back to a stock device state. After flashing the stock factory images and before locking the bootloader, you should erase the custom diff --git a/static/releases.html b/static/releases.html index c9eff7db..5506bd74 100644 --- a/static/releases.html +++ b/static/releases.html @@ -57,8 +57,6 @@
Version: QP1A.191005.007.A1.2019.10.07.21
- -Version: QP1A.191005.007.A1.2019.10.07.21
- -Version: QP1A.191005.007.A1.2019.10.07.21
- -Version: QP1A.191005.007.A1.2019.10.07.21
- -