# ChromeOS ## Identification [[SeaBIOS|SeaBIOS]] is a legacy BIOS-compatible payload that can run on Coreboot. [[ChromeOS|ChromeOS]] uses the Blink rendering engine and provides `crosh`; historical developer-mode/legacy-boot workflows used keyboard shortcuts to reach alternate boot paths. USB-to-RS-232 adapters provide serial-console access for low-level diagnosis. ## Notebook evidence - [[Scanned_20260730-1719#PDF page 32 — SeaBIOS/Coreboot on Chromebook-class hardware|PDF page 32: SeaBIOS/Coreboot on Chromebook-class hardware]] — The page captures a Chromebook conversion workflow: enable a lower-level shell, install or use alternate firmware, then boot Parrot/GRUB or diagnose by serial. It is the clearest bridge so far from consumer appliance to general-purpose computer. ## Relationships and overlays The source places this note in a shared evidence cluster with [[Scanned_20260730-1706|Scanned_20260730-1706]] · [[SeaBIOS|SeaBIOS]]. Within the larger collection, this evidence extends [[Vendor-Agnostic Recovery|vendor-agnostic recovery]] and [[Continuity Architecture|continuity architecture]] by showing how software, hardware, identity, and pre-OS control depend on recoverable interfaces. ## Evidentiary status and open leads Determine exact board name, firmware write-protect state, recovery image, backup ROM, and rollback procedure before any flash operation. ## Source - [[Scanned_20260730-1719|Scanned_20260730-1719]] ## Scanned_20260730-1314 overlay [[Scanned_20260730-1314#Scanned_20260730-1314.pdf — PDF page 29|Pages 29]]: ChromeOS kernel partitions appear in a GPT and boot-layout comparison, extending the notebook’s concern with canonical partition roles. **Relationship overlay:** [[GUID Partition Table]] · [[Unified Extensible Firmware Interface]].