I create arm AVDs in Android Studio Emulator on my Mac m1. Tried different images: Android 13.0, Android 12.0, Android 11.0 with Google APIs/no google apps. The behavior is the same for all.
I push my ca-certificate to /system in order to intercept decrypt HTTPS traffic. Following steps from here https://docs.mitmproxy.org/stable/howto-install-system-trusted-ca-android/
- Start it with command:
emulator -avd Pixel_4_API_33_2 -writable-system
tried to add -no-snapshot-load - no result on black screen freeze.
- Disable
avbctl disable-verification
adb root
adb shell avbctl disable-verification
adb reboot
- Remount /system as writable:
adb remount
adb push <my_cert> /system/etc/security/cacerts
adb shell chmod 664 /system/etc/security/cacerts/<my_cert>
At this point, my certificate is visible at "Settings - Security" tab, and is fully operationable. Unless Chrome started to throw error ERR_CERTIFICATE_TRANSPARENCY_REQUIRED for my certificate...
https://httptoolkit.com/blog/chrome-android-certificate-transparency/
Sad...
- Reboot after which I get freeze with black screen
adb reboot
Only starting AVD without -writable-system fixes the issue. But then my certificate is missing from system certificates. Which is not acceptable.
How to fix that black screen for -writable-system?
