aosp-part-kernel-and-boot

The Android boot sequence traces from bootloader handoff through first and second stage init to Zygote. You can map this flow to concrete AOSP source paths like system/core/init to understand each transition phase.

GKI separation decouples the core kernel from vendor modules, enforcing a KMI stability contract. This ensures vendor modules remain compatible across kernel updates without altering the core kernel interface.

AVB and dm-verity secure the Android boot path by verifying the integrity of the boot images and system partitions. They prevent unauthorized modifications during the boot flow before the OS fully loads.

System properties and SELinux contexts are initialized during early boot stages by loading property_contexts and SELinux policies. Reference paths like bionic/system_properties map this handling in the AOSP source.

The binder mechanism transitions from ashmem to memfd for memory management during Android boot. This shift aligns with GKI architecture requirements and kernel module separation in the AOSP source tree.