GalliumOS: historical downloads and Chromebook checks
English edition published on .
Project resources — opens a new tab
Check the project status before using archived installation media.
GalliumOS was designed for selected Chromebooks and Chromeboxes. This page preserves an outline of its historical installation process. Before considering an installation, check project maintenance, your exact device and its firmware requirements; an available ISO is not evidence of current security support.
Step 1: obtain the appropriate GalliumOS ISO
Start with the official GalliumOS website and its linked download and hardware documentation. Select an image for the exact device model, not simply for the Chromebook or Chromebox product name.
Older instructions distinguish processor families including Bay Trail, Braswell and Apollo Lake. Do not treat those examples as a complete compatibility list or assume that every device in a processor family can use the same procedure. Verify the device’s board and documented support before proceeding.
Step 2: prepare USB media
After obtaining and checking a suitable ISO, write it to USB with an image-writing tool. The older guidance specified at least 4 GB; ensure the actual image fits your drive. Back up the drive first because writing replaces its existing contents, and verify the destination before confirming.
Step 3: check developer-mode and firmware requirements
Historical Chromebook installation procedures may require developer mode or firmware changes. Enabling developer mode can erase local data. These are device-specific operations: read the exact model’s instructions, back up local files and prepare a recovery method before making changes. Developer mode alone does not establish that a device can boot or install GalliumOS.
Step 4: installation on supported hardware
Only after verifying compatibility and completing the documented preparation should you boot the selected USB image. Follow the project’s model-specific installation procedure rather than assuming a universal boot sequence.
The installation process includes choices such as language, keyboard, target partitions and user accounts. Check the target disk and any partitions to preserve before accepting changes.
Assess suitability before everyday use
A completed installation does not establish current maintenance or complete hardware compatibility. Check networking, suspend, peripherals, application needs and available security updates before entrusting important data to a system. Keep an independent backup and a recovery route for the original environment.
