Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Android boot chain: independent gates

An offline kernel build does not establish Android bootability. Each layer below is a separate check with its own evidence class.

LayerVerified or missing
Raw ARM64 Imagesource-built (C23/C26)
Image.lz4LZ4 legacy framing and decompression roundtrip verified; follows Kbuild’s lz4 -l -12 --favor-decSpeed
boot headerdevice scaffold records stock header v4; not independently validated as a new boot image
platform DTB / trusted overlaysource-built, hashes equal the C21 evidence
DTBO partition imagenot produced; table layout, IDs and stock contract remain to be verified (stock dtbo.img shipped unchanged)
vendor ramdiskauthorized vendor_boot, modules.load, first-stage placement and bootconfig missing
trusted board descriptionincomplete; pending wiring stays disabled
AVBproject keys and a verified chain absent; see AVB and trust
module signingpackaged modules signed with the development key; runtime acceptance unverified
hardwarenot tested

UFS first-stage dependency requirement

CONFIG_SCSI_UFSHCD=y and platform glue are built in, but the MediaTek host is ufs-mediatek-mod.ko. Its built-module dependency closure, ordered before the consumer, is:

aee_aed -> irq-dbg -> mrdump -> ufs-mediatek-dbg -> blocktag -> rpmb -> ufs-mediatek-mod

This is one valid topological order, not an authenticated modules.load list. The seven modules exist with matching vermagic. Without authorized vendor-ramdisk evidence their early availability and placement remain UNKNOWN. A module only present in later vendor_dlkm cannot be assumed available before UFS is mounted.

Three-stage module load order

OrderStageMechanismMount point
1vendor_boot platform ramdiskfirst-stage init / libmodproberamdisk
2system_dlkminit.insmod.sh loop, first entry/system_dlkm/lib/modules
3vendor_dlkmsame loop, second entry/vendor_dlkm/lib/modules
4init triggersinsmod / modprobe -a -d in vendor rc filesafter post-fs-data / boot

system_dlkm must load before vendor_dlkm: vendor_dlkm’s bluetooth, cfg80211 and mac80211 consume rfkill symbols exported by system_dlkm. Details in DLKM partitions.

What is still separate

Link closure, first-stage placement and runtime behaviour are three different checks. Closing rpmb’s symbols does not reconstruct stock RPMB transfer-sizing behaviour, and a closed module set does not prove Android starts.

Hazard: do not treat this chain as a flashing procedure. See Boot package for why the current package is not deployable.