From cd20a10536745366784d5ba49007a3f473f69426 Mon Sep 17 00:00:00 2001
From: Daniel Micay 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 build has to be done from bash as envsetup.sh is not compatible with other @@ -260,6 +264,41 @@ mv vendor/android-prepare-vendor/DEVICE/BUILD_ID/vendor/google_devices/* vendor/ sample certificate subject can be replaced with your own information or simply left as-is.
+The Pixel and Pixel XL use Android Verified Boot 1.0. The Pixel 2, Pixel 2 XL, + Pixel 3 and Pixel 3 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 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/verity_user.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):