[Android Q&A, Help & Troubleshooting] EmilWestergren:
I have built the android-11.0.0_r1 branch for Pixel 2 and successfully managed to flash the system build. Everything seems to work fine, but when I try to disable verity so I can get write access to partitions, I get a crash during boot.

I run the following commands after flashing the system images:

adb root

adb disable-verity

adb reboot

During boot, I get stuck in a loop with the following crash:

09-23 10:05:55.521 1809 1809 F DEBUG : Build fingerprint: 'Android/aosp_walleye/walleye:11/RP1A.200720.009/eng.eweste.20200909.110018:userdebug/test-keys'

09-23 10:05:55.521 1809 1809 F DEBUG : Revision: 'MP1'

09-23 10:05:55.521 1809 1809 F DEBUG : ABI: 'arm64'

09-23 10:05:55.521 1809 1809 F DEBUG : Timestamp: 2020-09-23 10:05:55+0200

09-23 10:05:55.521 1809 1809 F DEBUG : pid: 1801, tid: 1801, name: surfaceflinger >>> /system/bin/surfaceflinger <<<

09-23 10:05:55.521 1809 1809 F DEBUG : uid: 1000

09-23 10:05:55.521 1809 1809 F DEBUG : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------

09-23 10:05:55.521 1809 1809 F DEBUG : Abort message: 'eglQueryStringImplementationANDROID(EGL_VERSION) failed'

09-23 10:05:55.521 1809 1809 F DEBUG : x0 0000000000000000 x1 0000000000000709 x2 0000000000000006 x3 0000007fd98b0aa0

09-23 10:05:55.521 1809 1809 F DEBUG : x4 fefefefefefefeff x5 fefefefefefefeff x6 fefefefefefefeff x7 7f7f7f7f7f7f7f7f

09-23 10:05:55.521 1809 1809 F DEBUG : x8 00000000000000f0 x9 00000075de4667f8 x10 ffffff80ffffffdf x11 0000000000000001

09-23 10:05:55.521 1809 1809 F DEBUG : x12 0000007fd98b0a70 x13 0000000000000038 x14 0000007fd98b0c40 x15 001e3838963d3b74

09-23 10:05:55.521 1809 1809 F DEBUG : x16 00000075de4ffc80 x17 00000075de4e0f20 x18 00000075df930000 x19 00000000000000ac

09-23 10:05:55.521 1809 1809 F DEBUG : x20 0000000000000709 x21 00000000000000b2 x22 0000000000000709 x23 00000000ffffffff

09-23 10:05:55.521 1809 1809 F DEBUG : x24 0000000000000002 x25 0000000000000001 x26 0000000000000000 x27 0000000000000000

09-23 10:05:55.521 1809 1809 F DEBUG : x28 0000000000000000 x29 0000007fd98b0b20

09-23 10:05:55.521 1809 1809 F DEBUG : lr 00000075de4940c4 sp 0000007fd98b0a80 pc 00000075de4940f4 pst 0000000000000000

09-23 10:05:55.534 1809 1809 F DEBUG : backtrace:

09-23 10:05:55.535 1809 1809 F DEBUG : #00 pc 000000000004e0f4 /apex/com.android.runtime/lib64/bionic/libc.so (abort+180) (BuildId: c78cdff5b820a550771130d6bde95081)

09-23 10:05:55.535 1809 1809 F DEBUG : #01 pc 0000000000006334 /system/lib64/liblog.so (__android_log_default_aborter+12) (BuildId: c92329feece7a2d7fa4d9fb6acc815f9)

09-23 10:05:55.535 1809 1809 F DEBUG : #02 pc 0000000000006ec8 /system/lib64/liblog.so (__android_log_assert+336) (BuildId: c92329feece7a2d7fa4d9fb6acc815f9)

09-23 10:05:55.535 1809 1809 F DEBUG : #03 pc 000000000018b900 /system/lib64/libsurfaceflinger.so (android::renderengine::gl::GLESRenderEngine::create(android::renderengine::RenderEngineCreationArgs const&)+4000) (BuildId: ec25c5bad8ba139118d5f31ae1ba154c)

09-23 10:05:55.535 1809 1809 F DEBUG : #04 pc 000000000018a808 /system/lib64/libsurfaceflinger.so (android::renderengine::RenderEngine::create(android::renderengine::RenderEngineCreationArgs const&)+168) (BuildId: ec25c5bad8ba139118d5f31ae1ba154c)

09-23 10:05:55.535 1809 1809 F DEBUG : #05 pc 000000000010a280 /system/lib64/libsurfaceflinger.so (android::SurfaceFlinger::init()+184) (BuildId: ec25c5bad8ba139118d5f31ae1ba154c)

09-23 10:05:55.535 1809 1809 F DEBUG : #06 pc 00000000000021a8 /system/bin/surfaceflinger (main+352) (BuildId: 90f19aac502ae7e05183738dd9ef97d1)

09-23 10:05:55.535 1809 1809 F DEBUG : #07 pc 00000000000495b4 /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: c78cdff5b820a550771130d6bde95081)

If I enable verity again (using adb enable-verity) I can successfully boot the device.

Does anyone know how I can get past this?