Known issues with emteria.OS on Raspberry Pi Compute Module 5 (CM5)

Device fails to boot or reboots in a loop (outdated EEPROM firmware) 

Some CM5 modules ship with outdated EEPROM bootloader firmware (notably builds from around 2024) that brings up the eMMC/SD storage inconsistently. When the storage is not ready in time, Android's init cannot find its partitions and the device reboots repeatedly.

On the serial/UART console the boot fails during the first-stage mount with messages similar to:

init: partition(s) not found ... metadata, super, vbmeta_b, vbmeta_system_
init: Failed to create devices required for first stage mount
init: InitFatalReboot: signal 6

The problem may become reproducible after enabling UART console logging (dtparam=uart0_console=on in config.txt).

Workaround: Update the CM5 EEPROM bootloader firmware to the latest version, then re-install emteria.OS:

1. Boot the module into Raspberry Pi OS (the EEPROM lives on the module itself, independent of emteria.OS).
2. Update the installed packages: sudo apt update then sudo apt full-upgrade.
3. Check the current bootloader version: sudo rpi-eeprom-update.
4. Apply the latest available firmware: sudo rpi-eeprom-update -a.
5. Reboot and confirm: sudo reboot, then run sudo rpi-eeprom-update again.
6. Re-install emteria.OS and boot as normal. The device should now boot reliably.