Chromebox



The Chromebox is an inexpensive small form-factor PC which runs Google's ChromeOS; it is the desktop variant of a Chromebook laptop. Although Kodi does not run natively under ChromeOS, the Chromebox can easily be made to run Linux (or Windows) and.

This page is a collection of links, information, tips, and guides related to running on Chromebox mini PCs.

ChromeBox Overview
The Haswell Celeron-based Chromebox is small, lightweight x86-64 PC that natively runs ChromeOS, but with a few simple tweaks, has the capability to run any Linux-based OS. It features HDMI and DisplayPort video outputs (which can be used simultaneously), 4x USB 3.0 ports, gigabit Ethernet, an SD card slot, and built-in 802.11a/b/g/n wireless and Bluetooth 4.0.

Capability wise, the ChromeBox fully supports hardware accelerated H.264/MPEG-2/VC-1 video playback at up to 2160p24/p30 (4K), proper 24p output, and full 7.1/HD audio bitstream output (Linux only). 3D playback is supported (HSBS/HTAB), though the decoding of MVC streams (as used in 3D Blu-ray ISOs) is not supported under Linux at this time; the hardware itself is capable. Hi10 H.264 1080p playback is software decoded, but works well with few exceptions. 2160p60 is available only via DisplayPort (and only for UI/desktop functionality - the Celeron GPU doesn't have the horsepower for 2160p60 video playback), as HDMI 1.4a is limited to 2160p30. H.265/HEVC is software (CPU) decoded, so playback is limited to 1080p and low/moderate bit-rates. From a purely Kodi/media playback standpoint, there's no advantage to the Core i3/i7 models over the Celeron model (outside of 2160p60 video playback, which the i3/i7's HD4400 GPU can handle), or to upgrading the RAM or SSD.

The ChromeBox uses customized open-source firmware components (mainly coreboot) to boot ChromeOS in a secure/verified manner. By putting it in developer mode, we disable the verified boot restriction, and allow the ChromeBox to boot in "legacy mode" (via a legacy boot payload, SeaBIOS), which enables other operating systems (eg: OpenELEC, Ubuntu/Kodibuntu) to be installed / dual booted. If ChromeOS isn't needed, then custom firmware can be installed to directly boot the legacy BIOS. A simplified overview of the ChromeBox boot process is shown here (click for full-size):



This wiki page will guide you through the steps necessary to put the ChromeBox into developer mode and set it up in either a dual boot or standalone (non-ChromeOS) configuration. The majority of the process has been automated via the ChromeBox EZ Setup Script, making it safe and easy to run Linux/Kodi on your ChromeBox.

Disable Firmware Write Protect
Disabling the firmware write protect will allow us to shorten the timeout on the developer boot screen (from 30s to ~1s) in a dual boot configuration, and optionally boot directly in "legacy mode" (and into Ubuntu or OpenELEC). Disabling the write protect is also necessary for standalone setups so that the stock firmware can be replaced with a custom version.

With the device powered off and unplugged:


 * 1) Remove (4) rubber feet from bottom of unit
 * 2) Remove (4) screws under rubber feet
 * 3) Separate two halves of unit.
 * Tip: Thread a screw (or screws) into the VESA mounting holes, use to pull/separate bottom cover.
 * 1) Remove write-protect screw circled below:
 * Asus/HP/Dell: Inside-chrome1.jpg
 * Acer: Acer wp screw.png
 * Notes:
 * -- The write-protect screw on the Acer model is under the heat pipe, which needs to be removed to access it. Be sure to smooth out (or replace) the heatsink grease before reinstallation of the heatsink / heat pipe.
 * -- On some boxes (this is rare, but seems to be most common on the Dells), even after removing the write-protect screw, there is still connectivity between the two semi-circles, in which case you may need to use a small flathead screwdriver (eg) to lightly scrape away the excess material which is causing continuity. You can verify with a DMM.
 * 1) Reassemble in reverse order
 * 1) Reassemble in reverse order

Important: The write-protect screw should be left out permanently.

Put in Developer Mode
Putting the ChromeBox in developer mode will disable verified boot mode, and allow you to access the underlying Linux operating system features necessary for installing/running Kodi (via OpenELEC/Ubuntu).

WARNING: This will erase all user data on the device.

With the device powered off:
 * 1) Insert a paperclip into the hole left of the SD card slot and press the recovery button
 * Recoverybutton.png
 * 1) Power on the device, then remove the paper clip
 * 2) When greeted with the recovery screen, press [CTRL-D] to enter developer mode
 * 3) Press the recovery button (with paperclip) to confirm.

After confirming, the device will reboot and wipe any existing user data - this will take ~5 minutes. Afterwards, the ChromeBox will be in developer mode (vs verified boot mode), and the developer boot screen (shown below) will be displayed at each boot.



The developer boot screen has a warning about OS verification being off. Do not hit [SPACE], as it will return the device to verified boot mode. The ChromeBox must remain in developer mode, else you will potentially have to redo the setup from the beginning. The developer mode boot screen has a ~30s timeout, followed by two beeps, before booting. You can skip the delay by pressing [CTRL-D] to immediately boot into ChromeOS.

Perform a Factory Reset
A factory reset is not needed for a standalone setup, but must be performed prior to any dual-boot (re)install.


 * 1) Create recovery media using step 2 of Google's instructions here: https://support.google.com/chromebook/answer/1080595?hl=en or use the ChromeBook Recovery Utility from the Chrome web store.

Note: Google's recovery tool can be picky about what kind/size of USB/SD media you use. If one USB stick doesn't work, try another.


 * 1) With the device powered off, use a paperclip to press the Recovery button and power on the device
 * 2) Insert the recovery media (USB or SD) when prompted

Note that this will re-partition the internal hard drive and restore the original copy of ChromeOS, erasing anything else on the drive. The ChromeBox will still be left in developer mode, and if you changed the Boot Options they will still be set - so be sure to reset them back to the 'ChromeOS + 30s default' option before performing a factory reset. If you forget to do that, you'll need to press [CTRL-D] on the developer boot screen (or before the legacy boot/SeaBIOS boot screen) in order to boot ChromeOS after performing the recovery.

If you're having trouble creating the recovery media using Google's recovery tool above, you can manually download the recovery image and write it to a USB stick:
 * Download Recovery image:
 * Asus: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_6812.88.0_panther_recovery_stable-channel_mp.bin.zip
 * HP: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_6812.88.0_zako_recovery_stable-channel_mp-v2.bin.zip
 * Acer: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_6812.88.0_mccloud_recovery_stable-channel_mp.bin.zip
 * Dell: https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_6812.88.0_tricky_recovery_stable-channel_mp.bin.zip
 * Download Win32 Disk Imager: http://sourceforge.net/projects/win32diskimager/
 * Unzip the recovery image; the file should be ~1.5 GB
 * Rename the recovery image extension from .bin to .img
 * Write the image to your USB media using Win32 Disk Imager

OS and Kodi Installation
Kodi can be installed on the ChromeBox in a variety of ways. The two most common are via OpenELEC or Ubuntu+Kodi, in either a standalone or dual boot configuration. This is accomplished via the ChromeBox E-Z Setup script, which must be run (at least initially) from ChromeOS.

The EZ setup script will facilitate everything needed to install either a dual boot setup, or install a custom firmware which allows the installation of any Linux-based OS in standalone mode.

To run the ChromeBox E-Z Setup script, perform the following steps:


 * 1) Power on and boot to ChromeOS.  Do not log in, but ensure a network connection is established.
 * 2) Hit [CTRL][ALT][F2] to open a command prompt ([CTRL][ALT][<--] for ChromeOS keyboards)
 * 3) Login with user chronos (no password required)
 * 4) Download and run the ChromeBox setup script using the following two commands (hit enter after typing each command):
 * curl -L -O http://goo.gl/3Tfu5W
 * sudo bash 3Tfu5W

Full instructions and a detailed explanation of the script's functions and usage can be found at the following forum thread: http://forum.kodi.tv/showthread.php?tid=194362

Note: If installing a Linux-based OS other than OpenELEC (eg, Ubuntu/Kodibuntu), you will most likely need to manually update the kernel for optimal operation. Kernel version 3.18.4 is the minimum recommended, as it has a fix for an Intel GPU bug that can cause hanging during video playback. Updating the kernel is OS-specific and beyond the scope of this wiki, but instructions are easily found by googling.

Dual Boot OS Selection
When dual booting with ChromeOS and OpenELEC/Ubuntu, due to the ChromeBox's firmware setup, there is no conventional boot menu. Instead, the OS selection is made via keyboard shortcuts on the developer mode boot screen (shown above): [CTRL-D] boots directly ChromeOS; [CTRL-L] boots the legacy BIOS (and whatever secondary OS is installed). The default OS and boot timeout are set using the 'Set Boot Options' feature of the EZ Setup Script.

OpenELEC
The Chromebox is, at its core, a standard x86_64 Intel system (albeit, like the NUC, with an ultra low power processor). The standard OpenELEC builds - labeled 'Generic x86_64' - work perfectly well, and it is recommended to use OpenELEC's auto-update feature (System --> OpenELEC --> System --> Automatic Updates: auto). If that doesn't work for some reason, or you want to update to a nightly/beta/RC build, you can manually update using the instructions on the OpenELEC wiki.

Kodi General

 * System-->Settings-->System: Settings Level:Expert
 * System-->Settings-->System-->Video Output: Vertical blank sync:Enabled during video playback (or just 'Enabled' if you experience UI tearing)
 * System-->Settings-->System-->Power Saving: Shutdown function:Suspend (sets IR power toggle to suspend)
 * System-->Settings-->Videos-->Acceleration: Enable HQ Scalers for scalings above:20%
 * System-->Settings-->Videos-->Acceleration: Use VC-1 VAAPI:Selected (de-select if you have interlaced VC-1 content)
 * System-->Settings-->Videos-->Acceleration: Prefer VAAPI render method:Selected

Also see the video playback settings as shown in the screenshots below. Change as needed, then hit 'Set as default for all videos' to save.

OpenELEC Specific

 * System-->OpenELEC-->System: Automatic Updates:Auto
 * System-->OpenELEC-->Network: Wireless Networks/Active:Selected (if using WiFi)
 * System-->OpenELEC-->Network: Wait for network before starting Kodi:Selected (if using a external mysql database)
 * System-->OpenELEC-->Services: Enable Bluetooth:Selected (if using Bluetooth)

Switching between Standalone and Dual Boot configurations
If you have a dual boot setup and wish to switch to a standalone setup, the steps are no different than installing on a "fresh" system, though you can obviously skip the steps you have already performed (removing the write-protect screw, putting the box in developer mode). If you have an OpenELEC dual boot setup and are switching to an OpenELEC standalone setup, then you can backup your settings etc using the built-in tools, copy to another PC/USB, and restore after performing the standalone setup.

If you have a standalone setup and wish to switch to a dual boot setup, you need to first restore the stock firmware, then perform a factory reset, after which you can continue with the dual boot setup.

Recommended Accessories / Hardware Upgrades
For most users, there's no need to upgrade the ChromeBox's RAM or HDD; OpenELEC uses minimal RAM and disk space, and there's no benefit to upgrading. However, users who opt for a full Ubuntu/Kodibuntu setup, and plan on running lots of background processes etc, may find it beneficial to install additional RAM or upgrade to a larger SSD.

RAM:
 * The ChromeBox has two (2) 204-Pin SODIMM slots (HP models only have one), which accept 1.35V DDR3-1600 (PC3-12800) modules. Known working modules include:
 * Crucial CT25664BF160B (2GB, 1.35v/1.5v)
 * Crucial CT2CP51264BF160B (8GB [4GB x2] 1.35v/1.5v)
 * Crucial CT2KIT102464BF160B (16GB [8GB x2] 1.35v/1.5v)
 * Hynix HMT351S6CFR8C-PB (2GB, OEM)
 * HP H6Y75AA (4GB, 1.35v)


 * Crucial also has a list of 1.35v-only compatible modules here: http://www.crucial.com/usa/en/compatible-memory-for/ASUS/chromebox

SDD:
 * The ChromeBox uses a single 2242 M.2 SATA SSD (22mm x 42mm); stock is a 16GB unit (usually Sandisk or Kensington). Any M.2 SATA 2242 replacement drive should work without issue.

Remote Controls:
 * The ChromeBox does not have a built-in IR sensor, and must therefore use a USB IR receiver (or a Bluetooth remote). In general, any remote/receiver listed on the Kodi wiki as fully working under Linux should be fine, though some have issues when connected to USB3 ports.  A Microsoft eHome compatible remote/receiver is one of the most compatible, subject to the limitations listed in the 'Known Issues' section above.  Specific models tested as working include:
 * Flirc
 * Flirc users need to set the "sleep detection" bit and program a wake key when setting it up, otherwise absolutely any IR signal will wake up your box from sleep.
 * HP IR receiver model 5188-1667 (MCE/eHome)
 * HP IR receiver model 5187-4593 (MCE/eHome)
 * Microsoft IR receiver model 1040 (MCE/eHome)
 * Sony IR receiver model PCVA-IR8U (MCE/eHome)
 * HP IR remote/receiver kit OVU400102/71 (MCE/eHome, includes 5187-4593 receiver)
 * Ortek IR remote/receiver kit VRC-1100 (MCE clone, receiver also works well w/Logitech Harmony remotes)
 * Rosewill RHRC-11002 remote (MCE clone, includes receiver model IR605)
 * Rosewill WMC RRC-127 remote/receiver
 * Microsoft XBOX 360 IR remote (with MCE/eHome receiver or Flirc)
 * Microsoft XBOX One IR remote (with MCE/eHome receiver or Flirc)
 * Logitech Harmony remotes (programmed as Microsoft Media Center Extender - not as a keyboard - with MCE/eHome receiver; not recommended for use with a Flirc)
 * Sony Playstation 3 (PS3) Bluetooth remote (works with built-in BT receiver)
 * press/hold START + ENTER to pair, choose 'Trust and Connect', then hit Ok and Enable Standby after connecting
 * Logitech Harmony Smart Hub (via Bluetooth, works with built-in BT receiver, see forum post here)
 * Measy RC11 Android Monitor Wireless Keyboard Air Mouse Remote Controller With Gyroscope (cannot wake up Chromebox but works otherwise nicely, with keys as well as with mouse pointer at both OpenELEC and ChromeOS)
 * Amazon FireTV / Fire Stick remotes (Bluetooth)
 * NOTE: If you need to re-map remote buttons, you can use the Keymap Editor Add-on to do so.


 * Currently non-working:
 * HP IR receiver model 5070-2584 (MCE/eHome)
 * AVS Gear HA-IR01SV (MCE/eHome)
 * All Topseed manufactured MCE IR receivers

USB Audio Devices:
 * As the ChromeBox only has HDMI and analog audio outputs, if you need SPDIF, then either a converter or external/USB device must be used. The following devices have been tested/confirmed working:
 * Turtle Beach Audio Advantage Micro II (plug/play in both OpenELEC and Win8.1)
 * ASUS Xonar U3 USB (OpenELEC: requires un-muting the SPDIF line, see this forum post)

HDMI-CEC:
 * The ChromeBox does not support HDMI-CEC natively, but support can be added using an external USB CEC adapter from Pulse-Eight. The USB CEC Adapter needs power to the USB port BEFORE there is any video out, or it simply will not pass through any video signal. There are several ways to work around this:


 * Either always leave your Chromebox on, or just put it into standby; never turn it off
 * Use an externally powered source (eg, USB hub, TV set) to power the adapter (rather than the ChromeBox itself), so it always has power
 * If you have a spare HDMI port, you actually can split video in and control in for one HDMI channel using two physical HDMI ports. The video will be connected to the main port, and that's the port you use in the HDMI config settings in, and then you simply connect the USB CEC adapter to a spare HDMI port, does not appear to matter which.

Troubleshooting, Known Issues, Fixes/Workarounds
Installation, Dual Booting, USB booting:
 * Some keyboards seem to have issues working on the ChromeOS developer boot screen (before the OS is booted), and therefore cannot be used to setup/install Kodi on a ChromeBox, or to select between OSes in a dual boot setup. The Logitech K400 is one of these, so use another keyboard to install if yours doesn't appear to be working.  Most Bluetooth keyboards will not work due to the fact that they require the OS to be loaded in order to reconnect to the ChromeBox.
 * An effort is underway on the forums to catalog which keyboards work (and which do not); the thread (which is being updated regularly) can be found here: http://forum.kodi.tv/showthread.php?tid=211797
 * Help! I'm stuck on the black SeaBIOS boot screen, with the "booting from hard disk" text displayed (and possibly a bunch of nonsensical text afterwards).
 * This happens because SeaBIOS is trying to boot from the internal hard drive, but no bootable OS (or only ChromeOS) is installed.
 * If you have a dual boot setup, 99% of the time this is due to not having performed a factory reset prior to running the EZ Setup Script, as listed in the Device Prep section above. Simply perform the factory reset, then redo the dual boot setup using the script as before.
 * If you have a standalone setup:
 * If you see the 'Press ESC for boot menu' text but pressing it doesn't work, then the issue is your keyboard, so try using a different one.
 * If you don't see the 'Press ESC for boot menu' text, then the issue is with your boot media, so try using a different USB flash drive.
 * If the install media created by the script doesn't work (or you forget to create it before rebooting), then you can simply download the latest stable version (or beta/RC if you'd like) from OpenELEC's website here. The ChromeBox runs the Generic 64-bit version of OpenELEC, and it's recommended that you download the diskimage version, and create the install media, as per the instructions on the OpenELEC wiki.
 * Some TVs/displays are not able to show the developer boot screen due to the resolution it uses (1024x768 @ 60Hz), in which case you'll need to use a different display to complete the initial setup steps.
 * Many TVs have overscan enabled by default, which will cut off the text display of the ChromeOS shell. Be sure to set your TV to a mode which does not overscan (varies by manufacturer - often called 'just scan', 'exact' 'pixel perfect'; some TVs require you to label the input as a PC).
 * Using a passive DisplayPort-->HDMI cable/adapter is often problematic, and can cause the video output drop out after booting. Use either a straight DP cable or straight HDMI/HDMI-->DVI cable; if you have to use a DisplayPort-->HDMI adapter, be sure it is the active type.

Color Range Selection:
 * This topic is a bit of a minefield, but this post on the forums is a good read. It's for a NUC, but it applies to the ChromeBox as well. On some displays, the display and Intel video driver are not able to automatically sync up (in terms of which color space is being used), leading to incorrect black/white levels.  You can download/play the following video clip to test: Grayscale Ramp test (file courtesy of avsforum.com).  The correct output will show the grayscale ramp having a smooth transition (rather than stair steps) from 16-235, with solid black/white past the dots at the ends.  See: correct grayscale ramp.
 * Solution: add the following line to the autostart script and reboot the device:
 * xrandr --output HDMI1 --set "Broadcast RGB" "Full"
 * Use 'DP1' instead of 'HDMI1' if connected via the DisplayPort output. See the OpenELEC Autostart wiki page for more info.
 * You may also need to select the Kodi option 'Used limited color range' under Settings-->System-->Video Output. Use the video clip and image above as a guide.
 * Note: If you want to output Limited color range, you are required to do the following setting as well: Settings-->Video-->Acceleration-->Prefer VAAPI Rendering: disabled/de-selected.

No Audio and/or corrupted video on Wakeup from Suspend:
 * Some displays/AVRs don't successfully handshake when resuming from suspend, leading to no audio output and/or corrupted video output until the Chromebox is rebooted.
 * Solution: If using a universal remote, such as a Harmony, ensure that you are turning off (suspending) the ChromeBox before your AVR/TV, and turning it on (resuming) after the AVR/TV.
 * Solution: download/enable a script that will force the ChromeBox to reset the audio/video output on resume from suspend. Use an SSH client like Putty to connect to the ChromeBox, and execute the following commands:
 * mkdir -p /storage/.config/sleep.d
 * cd /storage/.config/sleep.d
 * curl -L -O https://dl.dropboxusercontent.com/u/98309225/01-cbox_resume.power
 * chmod +x 01-cbox_resume.power
 * Then reboot the ChromeBox
 * Note: If connected via the DisplayPort output, use a text editor (eg, nano) to edit the script and replace references to 'HDMI1' with 'DP1'.

Video Playback:
 * An Intel Linux video driver bug causes intermittent freezes where the video locks up but audio keeps playing.
 * Solution: This issue is fixed as of OpenELEC 5.0.0; users running a different Linux distro should be sure to update their kernel to 3.18.4 or 3.19.0 (or newer).

Remote Controls:
 * Most MCE IR receivers work properly now when connected to USB3 ports under Linux with kernel 3.16+ (older kernels will require a patch/fix); OpenELEC 4.0+ is fully up to date. The version of Ubuntu installed by the ChromeBox EZ setup script in a dual boot setup also includes an up-to-date kernel.  However, some buggy MCE receivers still do not work properly (at all), as noted below in the Hardware/Remotes section.


 * For standalone Ubuntu (or any other distro) installs, you will need to update to a 3.16 (or later) kernel.

Unreliable Wireless Devices attached to USB 3.0 ports:
 * Use a USB extension cable to move the device as far away from the USB port as possible. USB 3.0 can cause wireless interference. Intel has released a whitepaper documenting the issue.

Power Management:
 * Suspend/resume is generally problematic with the stock firmware (dual boot setups - OpenELEC will reboot on resume), but works reliably in standalone setups running the coreboot firmware. Resume via IR remote (USB) and wake-on-lan (eg, via YATSE) work perfectly well.
 * Note: WOL only works when the ChromeBox is suspended, not fully powered off, and requires the MAC address of the box to be set (eg, in YATSE)

Windows 8/8.1/10:
 * (Updated 2015/06/08) HDMI audio works, but requires specific drivers (Intel HD graphics 9.18.10.3220 and Intel Display Audio 6.16.0.3112), otherwise HDMI audi is non-functional.
 * Drivers are mirrored here for your convenience:
 * Windows 8/8.1/10 32-bit
 * Windows 8/8.1/10 64-bit
 * Bluray disc playback doesn't work, as PowerDVD and WinDVD report that the video drivers are not supported, even though they report the hardware is capable.
 * The CPU fan will shut down at boot and not come back on unless a utility like SpeedFan is used to start it. After manually starting the fan (set PWM1 to 50%), set Speedfan for automatic control and then create a shortcut for it to run at startup.
 * Windows 7 doesn't install/work, so don't ask for help with it.
 * Discussion of running Windows on a ChromeBox can be found on this forum thread: http://forum.kodi.tv/showthread.php?tid=203040

Linux Video Tearing:
 * Some users may experience screen tearing under the Linux desktop, or when watching video (e.g., Netflix). The fix for this is documented on the Arch Wiki, and copied here for convenience.


 * from a terminal/shell prompt:
 * sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf


 * copy/paste the following:


 * Section "Device"
 * Identifier "Intel Graphics"
 * Driver     "intel"
 * Option     "TearFree"    "true"
 * EndSection


 * then save, exit, and reboot.

High CPU at Idle:
 * When running a Linux setup, there is high idle CPU usage with some older kernels which do not fully support the Haswell platform; be sure to update to the latest kernel available (at least 3.18.4). On some (mostly dual boot) setups, it may also be necessary to add the following kernel boot parameters to disable the TPM: tpm_tis.force=1 tpm_tis.interrupts=0

OpenELEC Fails to boot:
 * If the OS isn't shutdown cleanly, sometimes a filesystem check (fsck) will be automatically performed. In some cases, the automatic repair is unsuccessful, and an error will show:
 * ***Error in check_disks: could not repair filesystem, dropping to debug shell, try to run 'fsck' manually: ***


 * ### Starting debugging shell... type exit to quit ###


 * sh: can't access tty; job control turned off


 * #_

In this case, simply run fsck manually as instructed, using the following commands, hitting [enter] after each:

For a standalone setup:
 * fsck /dev/sda1


 * fsck /dev/sda2

For a dual-boot setup:
 * fsck /dev/sda6


 * fsck /dev/sda7

After the fsck is run, type 'reboot' then hit [enter] and the system should boot normally.

Firmware/BIOS Updating
As depicted in the overview section above, the ChromeBox's firmware consists of two main parts: the main firmware (coreboot), and the Legacy BIOS payload (SeaBIOS). Users running a dual-boot configuration only need to update the Legacy BIOS portion. Users running a standalone setup should update the custom coreboot firmware only, as it contains an updated SeaBIOS payload (which can not be updated separately).

NOTE: Under normal conditions, the ChromeBox's firmware does not need to be updated after the initial install/update via the EZ Setup Script. As the old saying goes: if it ain't broke, don't fix it. Only update if you are having an issue that is specifically noted in the changelog as being addressed by a newer version.

Dual-boot users should simply boot to ChromeOS and re-download/re-run the EZ Setup Script, choosing the Update Legacy BIOS option under the Dual Boot heading.

Standalone users should also re-download/re-run the setup script, but instead choosing the coreboot firmware install/update option under the Standalone heading. As of v3.0, the script can be run under any version of Linux with a full bash shell. As OpenELEC does not have a full bash shell, OE users will need to use the (separate) standalone firmware update script, as described near the end of the EZ Setup Script forum post.

Resetting to Stock
If you have a dual boot setup, simply perform a factory reset, then hit [space] on the developer mode boot screen to revert to verified boot mode. Done. (Note: be sure to use the Kodi EZ Setup Script to reset the boot options to default before doing this, or you may not be able to exit developer mode)

If you have standalone setup, it is necessary to restore the stock firmware before performing a factory reset to reload ChromeOS.

In order to do this, you will need to download/run the ChromeOS device Firmware Utility script and select the appropriate option from the menu. The script will give you the option to restore from either a backup file from USB (which you created before originally flashing the custom coreboot firmware) or from a generic copy extracted from Google's recovery image. Like the Kodi EZ Setup Script, this script must be run from a Linux terminal with a full bash shell; OpenELEC users will need to boot a Linux Live USB (Ubuntu 14.04.2 64-bit works fine) from which to run the script. Just download the ISO of and write it to USB using Win32DiskImager (from Windows) or dd (Linux/MacOS).


 * Download and run the ChromeOS device Firmware Utility script using the following two commands (hit enter after typing each command):
 * curl -L -O https://goo.gl/1hFfO3
 * sudo bash 1hFfO3


 * Select option 3, Restore Stock Firmware
 * Choose whether to restore from a backup file on USB or not
 * If not, select your ChromeBox model so the appropriate firmware can be downloaded

After restoring the stock firmware, reboot, and proceed to Perform_a_Factory_Reset above to restore/reload ChromeOS.