I tried it and for me it didn't work it doesn't get pass the boot logo. Can someone else verify it doesn't work or perhaps the contrary-that would be awesome. And i also thought it should work on theory, that's why such things as generics gets implemented in the first place. But... Feels bad
OK, I've been able to flash and boot GSI using a mix of official instructions (
https://source.android.com/setup/build/gsi) and Pixel 3 XL GSI guide
https://forum.xda-developers.com/pixel-3-xl/how-to/guide-how-to-install-gsi-rom-pixel-3-xl-t3892685
Steps:
- Download "Gapps" ARM64-AB from
https://forum.xda-developers.com/pr...e-development/havoc-os-3-3-gsi-archs-t4076903
- Download Android 11 GSI )aosp_arm64-exp-QJR1.191112.001-6004257.zip) from
https://developer.android.com/topic/generic-system-image/releases to get vbmeta.img mentioned in the official guide of
https://source.android.com/setup/build/gsi
- Download latest factory image from
https://developers.google.com/android/images
- BACKUP ALL DATA on the phone.
Now, actual flashing:
1. Flash factory image as usual (flash-all.bat)
2. Flash stock (from factory) boot.img into both slots:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
3. Go to fastboot mode:
fastboot reboot fastboot
4. Flash vbmeta.img from Android 11 GSI:
fastboot flash vbmeta_b vbmeta.img
fastboot flash vbmeta_a vbmeta.img
5. Flash the ROM into both slots:
fastboot erase system_a
fastboot erase system_b
fastboot flash system_a Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img
fastboot flash system_b Havoc-OS-v3.7-20200709-Official-GApps-arm64-ab.img
if you get an error:
Resizing 'system_b' FAILED (remote: 'Not enough space to resize partition')
- erase product_b as described in official docs:
fastboot delete-logical-partition product_b
6. Wipe data and reboot
fastboot -w
fastboot reboot
As a result I've got functional GSI Havoc OS on the phone.
Magisk fails to install however - investigating that now.
UPDATE: Also, this definitely does not look as a Pixel phone: "Google Camera" from Play Store is some ancient version 4.4 from 2017 with no features, etc.
So, as a result - going back to rooted stock.