sebanc/brunch
Brunch
Brunch is a boot framework and hardware adaptation layer designed to run ChromeOS on non-native x86_64 PCs. It utilizes a custom EFI bootloader and kernel injection to enable the operating system to function on Intel and AMD processors not originally supported by official images.
The framework distinguishes itself by transforming official recovery images into generic bootable versions through the use of custom kernels and EFI partition bootstrapping. It allows for the importation of security keys into system firmware to support secure boot and provides tools to toggle hardware patches and feature flags for specific wireless cards, audio devices, and touchscreens.
The project provides capabilities for deploying ChromeOS as a primary single-boot system, as a dual-boot installation on a dedicated disk partition, or as a bootable USB medium. It includes a graphical installation interface and a verbose debug mode to diagnose boot failures.
Features
- OS Hardware Adaptation - Adapts ChromeOS to function on non-native x86_64 laptops and desktops using custom kernels and hardware patches.
- Custom Firmware Bootloaders - Implements a custom EFI bootloader that handles firmware key importation and kernel parameter injection.
- Custom Hardware Kernels - Provides modified operating system kernels with hardware patches to enable ChromeOS on unsupported x86_64 hardware.
- EFI Boot Loaders - Implements a custom EFI bootloader and partition to manage the initial boot sequence on non-native PCs.
- Hardware Compatibility Spoofers - Patches system components and adjusts kernel parameters to enable hardware support for specific wireless cards, audio devices, and touchscreens.
- Bootable Image Creation - Generates bootable disk images containing a custom kernel and EFI partition for hardware execution.
- Recovery Image Transformations - Transforms official recovery images into generic bootable versions by altering partition structures and bootloaders.
- x86_64 Device Support - Provides a set of kernel patches and configuration tools to enable ChromeOS hardware support for x86_64 Intel and AMD processors.
- Non-Native OS Booting - Creates bootable images and USB drives to run ChromeOS on hardware not originally supported by official images.
- OS Boot Frameworks - Provides a boot framework for running ChromeOS on non-native x86_64 PCs through custom kernels and EFI bootstrapping.
- Hardware-Specific Boot Configurators - Provides tools to toggle hardware patches and feature flags for specific wireless, audio, and touchscreen devices.
- Kernel Parameter Tuning - Uses boot-time command line arguments to toggle hardware patches and driver flags for device compatibility.
- Dual-Boot Partitioning - Configures disk partitions to allow ChromeOS to coexist with other operating systems via a boot manager.
- Kernel Image Selections - Enables the selection of specific precompiled kernels to ensure compatibility with the target hardware.
- Bootable USB Creators - Flashes generic images to USB drives to create bootable installation or live media for non-native hardware.
- Multi-Boot OS Installers - Deploys ChromeOS as a primary single-boot system, a dual-boot installation on a partition, or as a bootable USB medium.
- Operating System Installers - Provides a guided process to install a generic ChromeOS image onto a specific disk partition.
- Single-Boot Installers - Deploys the operating system to a disk as the primary and only boot option using a bootable medium.
- Firmware Security Key Importations - Allows the execution of the boot framework on locked hardware by importing necessary security keys into the system firmware.
- Secure Boot Key Management - Enables the enrollment of security keys into system firmware to allow the boot framework to run with Secure Boot active.
Star history
How this analysis was created: This summary and feature list are AI-generated from collected project material and can contain mistakes. Stars, license and language are imported from GitHub. Inclusion does not mean that we have tested or audited this project. Check the source documentation for any feature you depend on. Learn more on our About page.
