Difference between revisions of "Supported Devices"

Revision as of 05:28, 2 January 2020

^{[1] [2] [3]}

Determining Device Support

What's in a name? All ChromeOS devices have a board/device name, which determines which firmware, OS build, etc a device uses. The board name is listed at the bottom of both the Recovery Mode and Developer Mode screens, as part of the hardware ID (HWID). Your device's board name is what determines if it's supported or not -- not the make, model, CPU, or anything else. The only thing that matters is the name, so use that when determining support in the table below (or for anything else really).

The chart below provides a full, authoritative list of all ChromeOS devices currently supported by the Firmware Utility Script, the firmware types available for each, and the hardware write-protect method used. In most cases, all of the devices in a given platform/family are supported identically, but sometimes there are outliers (esp with older or newer devices). The goal is to offer both RW_LEGACY and UEFI Full ROM firmware for all devices wherever possible, so you have the option of dual booting ChromeOS, or liberating your device completely :)

OS Support

A device having firmware available (either RW_LEGACY or UEFI Full ROM) does not imply any level of functionality when running an OS other than ChromeOS. Some devices/platforms are better supported in some Linux distros vs others. Some devices/platforms are better supported under Windows than others.

The best resource for running Linux is the GalliumOS Hardware Compatibility List.
The best resource for running Windows is the ChrUltrabook subreddit (Read the stickied top post!)

Notes

1. STUMPY: The DisplayPort outputs don't seem functional under Windows, but work fine pre-OS and under Linux.
   VGA output (via DVI port) is not functional.
2. CELES: Running Windows on CELES requires a post-install workaround.
   CELES can be a highly problematic device running OSes other than ChromeOS. Highly recommended to avoid.
3. AMD: StoneyRidge devices currently can only boot via external media; eMMC is currently inaccessible in the bootloader. Some devices may not currently have functional Legacy Boot Mode due to bugs in Google's firmware.