Project
- Stars
- Started
- Issues
- License
Turn it into a normal PC that boots Linux or Windows
MrChromebox firmware is coreboot-based firmware for Chromebooks with an edk2 UEFI payload, so the machine boots Linux or Windows the way a regular PC does. You install it by running the project's Firmware Utility Script, which detects your board name, backs up the current firmware and flashes the image. It comes in two kinds: RW_LEGACY, which sits beside the stock firmware to dual-boot ChromeOS and Linux, and UEFI Full ROM, which replaces the stock firmware and prevents ChromeOS from booting.
It runs on Intel and AMD x86_64 Chromebooks only, and ARM Chromebooks aren't supported. Support is decided by the board name shown on the recovery or developer-mode screen, not by brand, model or CPU, and a board that isn't on the supported devices list isn't supported. On devices past Google's Auto Update Expiration the script offers UEFI Full ROM and blocks restoring the stock firmware. Firmware doesn't guarantee a working OS: audio, touchscreens and other parts depend on the distro and Chromebook platform.
Full ROM flashing needs hardware write-protect disabled; RW_LEGACY does not. The method varies by board: a write-protect screw, battery disconnection, SuzyQ cable or, on newer Ti50 boards, a gsctool command from ChromeOS. A wrong flash can leave the device unbootable, and a backup is the way back.
How did it go? Tips, problems, questions…
Turn it into a normal PC that boots Linux or Windows
MrChromebox firmware is coreboot-based firmware for Chromebooks with an edk2 UEFI payload, so the machine boots Linux or Windows the way a regular PC does. You install it by running the project's Firmware Utility Script, which detects your board name, backs up the current firmware and flashes the image. It comes in two kinds: RW_LEGACY, which sits beside the stock firmware to dual-boot ChromeOS and Linux, and UEFI Full ROM, which replaces the stock firmware and prevents ChromeOS from booting.
It runs on Intel and AMD x86_64 Chromebooks only, and ARM Chromebooks aren't supported. Support is decided by the board name shown on the recovery or developer-mode screen, not by brand, model or CPU, and a board that isn't on the supported devices list isn't supported. On devices past Google's Auto Update Expiration the script offers UEFI Full ROM and blocks restoring the stock firmware. Firmware doesn't guarantee a working OS: audio, touchscreens and other parts depend on the distro and Chromebook platform.
Full ROM flashing needs hardware write-protect disabled; RW_LEGACY does not. The method varies by board: a write-protect screw, battery disconnection, SuzyQ cable or, on newer Ti50 boards, a gsctool command from ChromeOS. A wrong flash can leave the device unbootable, and a backup is the way back.
MrChromebox and 15 others
1,122 followers · joined Jul 2011
Feedback
How did it go? Tips, problems, questions…