- Decision
- ADR-102
- Date
- 2026-09-26
- Status
- ProposedProposed.
- Mentions
- ADR-100, ADR-101
- Mentioned by
- ADR-101
1Decision
Use the existing, already-proven sign-baseline-images.sh to sign candidate 2026092501 as a direct-flash image bundle instead of an OTA package, and flash it with fastboot flashall (no -w) instead of through the Updater app. Supersedes ADR-101's approach; ADR-100's channel/data decisions (internal alpha, decoy wiped first, owner's normal profile preserved) are unchanged.
2Why and evidence
Same underlying reason as ADR-101 (OTA re-verification OOMs on the signing host), but the fix is to use the tool this project already has instead of building a new one. sign-baseline-images.sh requires the same vault and the same dual-hash gate as sign-ota.sh, unmodified.
Its produced bundle (confirmed via unzip -l on the real 2026-08-25 artifact) contains exactly the set docs/devices/lynx-metadata-bootloop-incident.md's proven flash procedure expects: boot.img, init_boot.img, dtbo.img, vendor_kernel_boot.img, pvmfw.img, vendor_boot.img, vbmeta.img, system.img, system_dlkm.img, system_ext.img, product.img, vendor.img, vendor_dlkm.img, super_empty.img, android-info.txt, fastboot-info.txt — no userdata.img, so the bundle itself cannot wipe data by inclusion.
3Consequences
Every prior physical flash this project has done used fastboot -w flashall; omitting -w to preserve the owner's normal profile (per ADR-100) has not been hardware-validated in this project before now. If the device fails to boot after a non--w flash, re-check whether an if-wipe conditional in fastboot-info.txt needed a wipe this time for an unrelated reason before assuming the candidate itself is bad.
4Review when
The flash fails to boot, or avbtool verify_image / the otacerts.zip check inside sign-baseline-images.sh fails on this candidate.
Read from docs/governance/decision-log.md, entry ADR-102.