Is it possible to build it on WSL? ive did sync whole over WSL but not sure about it!
WSL Support
- Edited
A rootless Linux container is spossible with Termux. "WSL" means "running Linux on Windows".
If you mean "running Windows on Android", so to say "ASW", @GrapheneOS mentioned this would be possible.
(Modern) Pixels have virtualisation support.
I am just wondering how their performance can be compared to a regular Laptop.
alexandro Is it possible to build it on WSL? ive did sync whole over WSL but not sure about it!
Here is an a step by step guide (it's a bit dated but simple enough to follow and make any necessary adjustments/modifications):
https://akc3n.page/posts/grapheneos-wsl/
I've managed somehow to build it on WSL after 6 times of fails,
Now I have flashed pixel 7a lynx, But i couldn't get to fix test-key issue and bootloader lock issue,
Here is method i followed document, Thanks for your time, Ive spend a lot energy days and hours couldn't get fix it
mkdir grapheneos-14
cd grapheneos-14
repo init -u https://github.com/GrapheneOS/platform_manifest.git -b 14
repo sync -j8
cd .repo/manifests
git config gpg.ssh.allowedSignersFile ~/.ssh/grapheneos_allowed_signers
git verify-tag $(git describe)
cd ../..
repo sync -j8
yarn install --cwd vendor/adevtool/
source build/envsetup.sh
m aapt2
source build/envsetup.sh
lunch lynx-user
export OFFICIAL_BUILD=true
m vendorbootimage vendorkernelbootimage target-files-package
mkdir -p keys/lynx
cd keys/lynx
CN=GrapheneOS
../../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 sdk_sandbox "/CN=GrapheneOS/"
../../development/tools/make_key bluetooth "/CN=GrapheneOS/"
openssl genrsa 4096 | openssl pkcs8 -topk8 -scrypt -out avb.pem
../../external/avb/avbtool.py extract_public_key --key avb.pem --output avb_pkmd.bin
cd ../..
signify-openbsd -G -n -p keys/lynx/factory.pub -s keys/lynx/factory.sec
script/encrypt_keys.sh keys/lynx
script/release.sh lynx
m otatools-package
You need to flash the key you generated for verified boot,
fastboot erase avb_custom_key
fastboot flash avb_custom_key /path/to/avb_pkmd.bin
Yes erased, This command already was in flash-all.bat and .sh, Here is output, There is might be error in to this output
fastboot erase avb_custom_key
Erasing 'avb_custom_key' (bootloader) avb custom key: erase done
OKAY [ 0.027s]
Finished. Total time: 0.031s
fastboot flash avb_custom_key avb_pkmd.bin
Warning: skip copying avb_custom_key image avb footer (avb_custom_key partition size: 0, avb_custom_key image size: 1032).
Sending 'avb_custom_key' (1 KB) OKAY [ 0.000s]
Writing 'avb_custom_key' (bootloader) avb custom key: flash done
OKAY [ 0.031s]
Finished. Total time: 0.039s