Which Screw Remove Allow Write Firmware Hp Chromebook 14 Atheros

Which Screw Remove Allow Write Firmware Hp Chromebook 14 Atheros

Which Screw Remove Allow Write Firmware Hp Chromebook 14 Atheros These pages are maintained by the community and should non be considered an endorsement or recommendation. Device pages are made when there’s a agglomeration of useful data for a particular device, and someone takes the fourth dimension to make that folio. Keep in mind, some devices only don’t need a page of specific data, but are withal excellent devices.

*
Chromebox

Asus chromebox.jpg
Released 2014-03-xiv (US)
Os ChromeOS
CPU Intel® Celeron 2955U/2957U

Intel® Core i3-4010U/4030U

Intel® Core i7-4600U
Storage 16GB internal SSD (M.2 SATA)
RAM 2GB/4GB/8GB standard, 16GB max

Dual Aqueduct DDR3L-12800
Graphics Intel® HD Graphics/GT1 (Celeron)

Intel® HD Graphics 4400/GT2 (i3/i7)
Connectivity HDMI 1.4a

DisplayPort 1.2a

Bluetooth 4.0

USB 3.0 (4x)

802.11 abgn/AC wifi

10/100/grand Ethernet

2 -in-1 Card Reader
3.5mm headphone plug
Dimensions four.88 ten four.88 ten 1.65 inch (WxDxH)



Asus Chromebox Rear Ports



Asus Chromebox Side/Front Ports

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

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


Notation:
This page was originally written for the Haswell-based ASUS Chromebox, simply the information herein is valid for all Haswell/Broadwell-based Chromeboxes. Model-specific features are enumerated below.


1
ChromeBox Overview

Chromeboxes are small, lightweight x86-64 PC that natively runs ChromeOS, but with a few simple tweaks, has the capability to run any Linux-based OS (some models tin also run Windows 8.1+). They use customized open up-source firmware components (mainly
coreboot) to boot ChromeOS in a secure/verified way. By putting it in Developer Style, we disable the verified boot restriction, and let the ChromeBox to boot in “legacy mode” (via a Legacy Kicking payload,
SeaBIOS), which enables other operating systems (eg: LibreELEC, GalliumOS) to be installed / dual booted. If ChromeOS isn’t needed, and then custom firmware can be installed to straight boot the legacy BIOS. A simplified overview of the ChromeBox boot procedure is shown here (click for full-size):


ChromeBox boot process.png

This wiki page will guide you through the steps necessary to put the ChromeBox into Developer Mode and prepare Kodi in either a dual kick or standalone (non-ChromeOS) configuration. The majority of the process has been automatic via the ChromeBox Kodi Due east-Z Setup Script, making it rubber and (relatively) piece of cake to run Linux/Kodi on your ChromeBox.


1.1
Generations and Models


1.i.1
SandyBridge

There is but one SandyBridge based Chromebox — the Samsung Serial 3 Chromebox — though information technology was bachelor with Celeron and Core-i5 mobile CPUs. It’s not recommended for Kodi use due to the limitations of the integrated GPU (24p bug, no advanced deinterlacing), and the availability of the significantly more capable Haswell/Broadwell-based boxes, usually at a lower cost. It’s besides not capable of dual-booting ChromeOS + Kodi, due to lack of Legacy Boot way in the stock firmware.


i.1.2
Haswell

Haswell Chromeboxes were first released in March 2014, and quickly became the low-cost x86 platform of choice due to the combination of the speed U-series Celeron CPU and capable integrated GPU.

Capability wise, the Haswell ChromeBoxes fully support hardware accelerated H.264/MPEG-2/VC-ane video playback at up to 2160p24/p30 (4K), proper 24p output, and full 7.1/HD audio bitstream output. 3D playback is supported (HSBS/HTAB), though the decoding of MVC streams (equally used in 3D Blu-ray ISOs) is not supported under Linux at this time; the hardware itself is capable. Hi-10P (H.264) playback is software decoded, but works well with few exceptions. 4K (2160p) output is limited to 30Hz via both the DisplayPort and HDMI one.4a outputs. H.265/HEVC is software (CPU) decoded, and then playback is express to 1080p max and low/moderate flake-rates. From a purely Kodi/media playback standpoint, there’s no advantage to the Cadre i3/i7 models over the Celeron model (outside of non-GPU decoded formats, like Hi-10P and HEVC); dual channel retentivity (two identical capacity modules) can provide a decent performance boost in some situations merely certainly non needed for a standard OpenELEC/LibreELEC/Kodi setup.

Make / Model Asus Chromebox CN60 HP Chromebox CB-ane Acer Chromebox CXI Dell Chromebox 3010
CPU/GPU Celeron 2955U (HD Graphics / GT1)
Cadre i3-4010U, Core i7-4600U (Hard disk drive Graphics 4400 / GT2)
Celeron 2955U (HD Graphics / GT1) Celeron 2957U (Hard disk drive Graphics / GT1)
Core i3-4030U (Hard disk Graphics 4400 / GT2)
Celeron 2955U (Hard disk drive Graphics / GT1)
Core i3-4010U, Core i7-4600U (Hard disk Graphics 4400 / GT2)
RAM Dual-channel DDR3 1333/1600 MHz
2x SO-DIMMs, 2/4GB stock, 16GB full max.
Unmarried-channel DDR3 1333/1600 MHz
1x SO-DIMMs, 2/4GB stock, 8GB full max.
Dual-aqueduct DDR3 1333/1600 MHz
2x SO-DIMMs, 2/4GB stock, 16GB total max.
Display Outputs 1x
HDMI 1.4a

1x
DisplayPort 1.2
Internal storage m.ii SATA SSD, 42mm (2242) MiniPCIe slot, 16GB stock
Ethernet 1x RJ45, ten/100/g Mbps
WiFi / BT Atheros AR9462 802.11 abgn + BT iv.0 Intel 7260 802.11 ac + BT four.0
Audio 7.1 digital sound (bitstream or PCM) via
HDMI
and
DisplayPort

Rear-panel 3.5mm headset jack
USB Ports USB iii.0: 2x rear, 2x forepart
Carte du jour Reader Internal USB 2.0-fastened full-size SD menu slot
Model Notes Quietest fan
SSD/RAM easily attainable for upgrading
Loudest fan
SSD/RAM require a few extra screws to disassemble chassis
unmarried RAM slot
Medium fan dissonance
Upright chassis design
SSD/RAM require removing the unabridged board every bit slots are on the underside
Medium fan dissonance
SSD/RAM easily accessible for upgrading
merely model with -Air conditioning WiFi.

All Haswell model Chromeboxes are fully supported by the ChromeBox Kodi E-Z Setup Script.


1.1.3
Broadwell

Broadwell Chromeboxes were announced in the Bound of 2015, but not available to purchase until the Autumn. Fifty-fifty now, their availability is all the same limited to the Haswell boxes, which have displayed remarkable staying ability given the release of replacement models. Broadwell CPUs are ~fifteen% faster than Haswell, like for like, but GPU performance is nigh identical, and for Kodi use they are probable duplicate.

Capability wise, the Broadwell ChromeBoxes are essentially identical to the Haswell Chromeboxes, with the add-on of supporting 4K (2160p) at 60Hz via DisplayPort. HEVC is yet software decoded, making 4K output a spec-sheet checkmark for the nigh part.

Brand / Model Asus Chromebox CN62 Acer Chromebox CXI2 Lenovo ThinkCentre Chromebox
CPU/GPU Celeron 3205U (HD Graphics / GT1)
Core i3-5005U, Cadre i7-5500U (Hard disk drive Graphics 5500 / GT2)
Celeron 3205U (Hd Graphics / GT1)
Cadre i3-5005U, Core i7-5500U (HD Graphics 5500 / GT2)
Celeron 3205U (HD Graphics / GT1)
Core i3-5005U (HD Graphics 5500 / GT2)
RAM Dual-aqueduct DDR3 1333/1600 MHz
2x SO-DIMMs, 2/4GB stock, 16GB max.
Celeron model: Single-channel DDR3 1333/1600 MHz
1x Then-DIMMs, 2/4GB stock, 8GB max.
Display Outputs 1x
HDMI 1.4a

1x
DisplayPort 1.2
Internal storage g.2 SATA SSD, 42mm (2242) MiniPCIe slot, 16GB stock
Ethernet 1x RJ45, 10/100/1000 Mbps
WiFi / BT Intel 7260 802.eleven ac + BT 4.0
Audio 7.1 digital audio (bitstream or PCM) via
HDMI
and
DisplayPort

Rear-panel 3.5mm headset jack
USB Ports USB 3.0: 2x rear, 2x front
Menu Reader Internal USB 2.0-attached full-size SD bill of fare slot None
Model Notes Quietest fan
SSD/RAM easily attainable for upgrading
Medium fan noise
Upright chassis design
SSD/RAM require removing the unabridged board as slots are on the underside
Medium fan noise
SSD/RAM crave a unmarried screw to admission
unmarried RAM slot (Celeron model)
no SD card reader
external WiFi antenna

All Broadwell model Chromeboxes are fully supported by the ChromeBox Kodi Eastward-Z Setup Script.


1.1.4
Kabylake

Kabylake Chromeboxes were released in the Leap of 2018, and feature a few notable improvements over the previous Haswell/Broadwell models (which are effectively identical). The Kabylake SoC provides a dainty speed bump, but more than chiefly the GPU features total 10-chip HEVC/VP9 decoding, too equally 4Kp60 output (via USB-C DisplayPort alt-manner).

Unfortunately, the GPU in the Kabylake SoC still doesn’t natively support HDMI 2.0 output. This means that 4Kp60 output yet requires the use of a DisplayPort to HDMI ii.0 adapter (via the USB-C port), and thus a LSPCON (level shifter/protocol converter). The use of a LSPCON ways that Hd sound bitstreaming well-nigh certainly won’t piece of work (due to driver limitations), so one must choose between using the HDMI 1.4 output with HD audio, or the USB-C output with 4K output.

Too, although the Kabylake SoC is HDR capable, Intel has not implemented HDR capability nether Linux. Because of this and the above factors, it’southward hard to recommend a Kabylake Chromebox at this fourth dimension, unless yous simply want a faster, HEVC/VP9 capable device and the aforementioned limitations do not bother you lot. Even all the same, there likely better options available at a lower toll point.

Make / Model Asus Chromebox 3 / CN65 Acer Chromebox CXI3 HP Chromebox G2 CTL Chromebox CBx1
SoC/GPU Kabylake-U / HD610 (Celeron, i3/i5-7xxx)
Kabylake-R / UHD620 (i5/i7-8xxx)
CPU Celeron 3865U, Cadre i3-7100U, Core i5-8250U, Core i7-8550U Celeron 3865U, Cadre i3-7130U, Core i5-8250U, Core i7-8550U Celeron 3865U, Cadre i5-7300U, Cadre i7-8560U Celeron 3865U, Cadre i7-8550U
RAM Dual-channel DDR4 2133, 2x SODIMMs, 32GB max.
Brandish Outputs 1x
HDMI 1.4a

1x
USB-C
Internal storage m.2 SATA SSD, 42mm (2242); 80mm drives tin can exist used as well

Core-i models support NVMe drives (PCIe x4)
Ethernet 1x Realtek RT8169, RJ45, ten/100/1000 Mbps
WiFi / BT Intel 7265 802.11 ac + BT 4.0
Audio vii.1 digital sound (bitstream or PCM) via
HDMI
and
DisplayPort

Forepart-panel 3.5mm headset jack (non functional under Linux currently due to driver issues)
USB Ports USB 3.0: 3x rear, 2x front
USB 3.1 Gen i Type-C: 1x rear
Bill of fare Reader Forepart internal micro-SD card slot
Model Notes
Read:  How to Install Older Firmware on Dolphinbar

All Kabylake model Chromeboxes are fully supported by the ChromeBox Kodi E-Z Setup Script. Currently, Legacy Boot Fashion is broken in Google’s stock firmware, then dual booting is non functional at this time.


2
Device Training


ii.1
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 kick configuration, and optionally boot directly in “legacy manner” (and into GalliumOS/LibreELEC). Disabling the write protect is as well 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 (four) rubber anxiety from lesser of unit
  2. Remove (four) screws nether rubber anxiety
  3. Take off the lesser cover.
    Tip: Thread two of the screws that you lot simply removed into the VESA mounting holes, and apply them to pull/separate bottom encompass.
  4. Remove write-protect screw circled beneath:
    Asus CN60,CN62/HP CB-1/Dell 3010:

    Inside-chrome1.jpg
    Acer CXI,CXI2:

    Acer wp screw.png
    Lenovo Thinkcenter Chromebox:

    Lenovo wp.jpg
    2018 (Kabylake) Chromeboxes (Asus CN65, Acer CXI3, CTL CBx-1, HP CB G2):

    Cbox3 wp.jpg
    Notes:
    — The write-protect screw on the Acer model is under the heat piping, which needs to exist removed to access it. Be sure to smooth out (or replace) the heatsink grease earlier reinstallation of the heatsink / heat pipe.
    — On some boxes (this is rare, merely seems to exist most common on the Dells), even after removing the write-protect spiral, there is nonetheless connectivity betwixt the two semi-circles, in which case you may need to utilise a small flathead screwdriver (eg) to lightly scrape away the excess material which is causing continuity. You lot can verify with a DMM.
  5. Reassemble in contrary club

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

Note without the spiral there was
a case registered
with bootloop when powering from USB-C Power Delivery. Your mileage may vary.


2.ii
Put in Developer Way

Putting the ChromeBox in developer mode volition disable verified boot manner, and allow yous to access the underlying Linux operating system features necessary for installing/running Kodi (via LibreELEC/GalliumOS).

WARNING: This will erase all user information 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
  2. Ability on the device, then remove the newspaper clip
  3. When greeted with the recovery screen, press [CTRL-D] to enter programmer mode
  4. Printing the recovery push button (with paperclip) to confirm.

Later confirming, the device will reboot and wipe any existing user data – this volition have ~5 minutes. Afterwards, the ChromeBox volition be in developer fashion (vs verified boot fashion), and the developer boot screen (shown below) will be displayed at each boot.

Note:
The recovery button (and booting to recovery manner) are a part of the stock firmware. If you’ve flashed a custom firmware on your box (either as office of a standalone setup or otherwise), the recovery push has no function and the ChromeOS recovery mode doesn’t exist.


ChromeBox dev boot.jpg

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


2.3
Perform a Manufacturing plant Reset

A manufacturing plant reset is not needed for a standalone setup, but must exist performed prior to any dual-boot (re)install.

  1. Create recovery media using step ii of Google’s instructions here:
    https://back up.google.com/chromebook/answer/1080595?hl=en
    or use the
    ChromeBook Recovery Utility from the Chrome web shop.

Annotation: Google’due south recovery tool tin can be picky about what kind/size of USB/SD media you utilize. If ane USB stick doesn’t work, try another.

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

Note that this will re-partitioning the internal hard drive and restore the original copy of ChromeOS, erasing annihilation else on the bulldoze. The ChromeBox volition yet be left in developer manner, and if you changed the Boot Options they will withal be prepare – and then be certain to reset them back to the ‘ChromeOS + 30s default’ choice
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 kick ChromeOS after performing the recovery.

Notation:
The recovery media created using Google’due south recovery tool works only when the ChromeBox is booted into recovery mode, which only exists when using the stock firmware. If you’ve flashed a custom firmware on your box (either as part of a standalone setup or otherwise), ChromeOS recovery style doesn’t exist, and attempting to boot the recovery media from SeaBIOS will not piece of work (it will boot y’all into a non-functional version of ChromeOS).



iii
Installation, Configuration, and Updating


3.1
OS and Kodi Installation

Kodi tin can exist installed on the ChromeBox in a multifariousness of ways. The two about common are via LibreELEC or GalliumOS+Kodi, in either a standalone or dual kick configuration. This is accomplished via the ChromeBox Kodi 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 kicking setup, or install a custom firmware which allows the installation of any Linux-based OS in standalone mode.

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

  1. Ability on and boot to ChromeOS. Do non log in, but ensure a network connectedness is established.
  2. Hitting [CTRL][ALT][F2] to open a control prompt ([CTRL][ALT][<–] for ChromeOS keyboards)
  3. Login with user chronos (no countersign required)
  4. Download and run the ChromeBox Kodi E-Z Setup Script using the following control (hit enter later on):
    curl -L -O https://mrchromebox.tech/setup-kodi.sh && sudo fustigate setup-kodi.sh

Full instructions and a detailed explanation of the script’due south functions and usage tin can exist institute at the following forum thread:
http://forum.kodi.tv/showthread.php?tid=194362

Older Kernels:
If installing a Linux-based OS other than LibreELEC non via the E-Z Setup Script (eg, Kodibuntu), you may need to manually update the kernel for optimal operation. Kernel version iii.eighteen.4 is the minimum recommended, every bit it has a prepare 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.

Ubuntu fifteen.10:
Ubuntu Wily Werewolf (15.10) ships with Linux kernel 4.two.0, which immediately panics upon kicking on Chromeboxes. To fix this, you tin boot by calculation ‘acpi=off’ as a Grub kernel boot parameter, then manually update to kernel 4.three (or later) afterwards the OS is installed/booted.

If the LibreELEC install media created by the script doesn’t work (or you forget to create it before rebooting, or just want to do a fresh install), and then you can create install media by using the
LibreELEC USB/SD creator tool, which is available for Windows/Mac/Linux.


3.2
Dual Boot OS Selection

When dual booting with ChromeOS and LibreELEC/GalliumOS, due to the ChromeBox’s firmware setup, there is no conventional boot menu. Instead, the OS option is made via keyboard shortcuts on the programmer mode boot screen (shown to a higher place): [CTRL-D] boots directly ChromeOS; [CTRL-Fifty] boots the legacy BIOS (and any secondary OS is installed). The default Os and kick timeout are set using the ‘Set Boot Options’ feature of the EZ Setup Script.


3.three
Updating Kodi


3.3.1
LibreELEC

The Chromebox is, at its cadre, a standard 64-bit x86 system (albeit, like the NUC, with an ultra low power processor). The standard LibreELEC builds – labeled ‘Generic’ for x86_64 PCs – piece of work perfectly well, and it is recommended to use LibreELEC’s motorcar-update feature (System –> LibreELEC –> System –> Automated Updates: auto). Automatic updates won’t update from a stable to a beta release, merely will update stable->stable, beta->beta, and beta->stable within the same major version. If the automatic update doesn’t work for some reason, or yous want to update to a test/nightly/beta/RC build, you tin can manually update using the instructions on the
LibreELEC wiki.

Manual update file:
LibreELEC 8.0.i / Kodi 17.i

Notation:
LibreELEC versions 7.0 and in a higher place now crave a larger system segmentation than previous versions. Attempting to upgrade may neglect with a ‘system size cheque’ error. In this case, the easiest resolution is to fill-in (using LE’southward born backup tool), doing a fresh install (from USB) of whatever version you’re looking to run, and then restore the backup (which you saved to USB or otherwise copied elsewhere).


3.4
Recommended Settings


3.4.ane
Kodi General


For the nearly part, the default / out-of-the-box settings are correct/optimal for the ChromeBox, though the following changes are suggested:

  • Arrangement–>Settings–>System: Settings Level:
    Adept
  • Organisation–>Settings–>System–>Power Saving: Shutdown function:
    Suspend
    (sets remote power toggle to suspend)
  • System–>Settings–>Videos–>Playback: Accommodate brandish refresh charge per unit:
    On start / stop
  • System–>Settings–>Videos–>Playback: -Pause during refresh rate change: fix equally needed depending on your display (0.0s – 0.5s is usually adequate)
  • System–>Settings–>Videos–>Acceleration: Enable HQ Scalers for scalings higher up:
    xx%
  • System–>Settings–>Videos–>Dispatch: Allow hardware acceleration (VDPAU):
    Off
  • System–>Settings–>Videos–>Acceleration: Allow hardware acceleration (VAAPI):
    On
    (default)
  • Arrangement–>Settings–>Videos–>Acceleration: -Use MPEG-2 VAAPI:
    On
    (default)
  • System–>Settings–>Videos–>Acceleration: -Use MPEG-iv VAAP):
    On
    (default)
  • System–>Settings–>Videos–>Acceleration: -Use VC-1 VAAPI:
    On
    (default)
  • System–>Settings–>Videos–>Acceleration: -Adopt VAAPI render method:
    On
    (default)
  • System–>Settings–>System–>Video Output: Vertical bare sync:
    Let driver choose
    (default)
  • System–>Settings–>Organisation–>Video Output: Use limited colour range (16-235): ready as needed to attain proper black levels; users of PC monitors will demand to deselect this, otherwise blacks will be washed out. (Intel-EGL builds only)
Read:  Samsung Galaxy S6 Edge Plus Sm-g928a Firmware

Also encounter the video playback / deinterlacing settings as shown in the screenshots below. These settings are accessed during video playback by bringing up the card and selecting video playback options (the movie reel icon). Modify every bit needed, so striking ‘Set as default for all videos’ to salve.


3.iv.two
LibreELEC Specific

  • Organization–>LibreELEC–>System: Automatic Updates:
    on
  • System–>LibreELEC–>Network: Wireless Networks/Active:
    On
    (if using WiFi)
  • System–>LibreELEC–>Network: Await for network before starting Kodi:
    On
    if using a external mysql database; otherwise
    Off
    (breaks Wi-Fi, only use for wired/ethernet connections)
  • System–>LibreELEC–>Services: Enable Bluetooth:
    On
    if using a Bluetooth remote, otherwise leave off


3.5
Switching between Standalone and Dual Boot configurations

If you lot 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 tin obviously skip the steps yous have already performed (removing the write-protect screw, putting the box in programmer mode). The easiest fashion to do this is to boot ChromeOS ([CTRL+D] from Developer Mode boot screen / before SeaBIOS loads) and re-run the Eastward-Z Setup Script as before. If you can’t boot ChromeOS for any reason, and then simply create/kick a Linux ISO from USB (I apply/recommend GalliumOS) and run the script from a concluding there.

If you have an LibreELEC dual boot setup and are switching to an LibreELEC standalone setup, then you tin can backup your settings etc using the congenital-in tools, copy to another PC/USB, and so restore after performing the standalone setup.

If you have a standalone setup and wish to switch to a dual kick setup, you need to outset restore the stock firmware, then perform a manufacturing plant reset, later which you can continue with the dual boot setup.



4
Recommended Accessories / Hardware Upgrades

For most users, there’southward no demand to upgrade the ChromeBox’s RAM or HDD; LibreELEC uses minimal RAM and disk space, and at that place’s no benefit to upgrading. All the same, users who opt for a total Linux + Kodi setup, and programme on running lots of background processes etc, may discover information technology beneficial to install additional RAM or upgrade to a larger SSD.

RAM:

The ChromeBox has two (ii) 204-Pin SODIMM slots (HP models only have one), which use DDR3L (1.35V) 1600MHz/PC3-12800 modules. Known working modules include:

  • Crucial CT25664BF160B (2GB, 1.35v/1.5v)
  • Crucial CT2CP51264BF160B (8GB [4GB x2] i.35v/one.5v)
  • Crucial CT2KIT102464BF160B (16GB [8GB x2] 1.35v/1.5v)
  • Hynix HMT351S6CFR8C-Pb (2GB, OEM)
  • HP H6Y75AA (4GB, i.35v)
Crucial also has a list of 1.35v-but 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 of measurement (usually Sandisk or Kensington). Any M.2 SATA 2242 replacement drive should work without outcome.


Remote Controls:

The ChromeBox does non have a congenital-in IR sensor, and must therefore employ a USB IR receiver (or a Bluetooth remote). In full general, any remote/receiver listed on the Kodi wiki every bit fully working under Linux should be fine, though some accept issues when connected to USB3 ports. A Microsoft eHome uniform remote/receiver is ane of the most compatible, subject to the limitations listed in the ‘Known Issues’ section above. Specific models tested every bit working include:

  • Flirc

    Flirc users need to set the “slumber detection” flake and programme a wake cardinal when setting it upwardly, 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)
  • HP IR receiver model 5070-2584 (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 west/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 Eye Extender – not as a keyboard – with MCE/eHome receiver; not recommended for utilise with a Flirc)
  • Sony Playstation iii (PS3) Bluetooth remote (works with congenital-in BT receiver)
    printing/hold START + ENTER to pair, cull ‘Trust and Connect’, so hit Ok and Enable Standby after connecting
  • Logitech Harmony Smart Hub (via Bluetooth, works with congenital-in BT receiver,
    run into forum post here)
  • Measy RC11 Android Monitor Wireless Keyboard Air Mouse Remote Controller With Gyroscope (cannot wake up Chromebox simply works otherwise nicely, with keys as well as with mouse pointer at both OpenELEC and ChromeOS)
  • Amazon FireTV / Burn Stick remotes (Bluetooth)
Notation: If you need to re-map remote buttons, you lot can use the Keymap Editor Addition to do so.
Currently non-working:

  • AVS Gear HA-IR01SV (MCE/eHome)
  • All Topseed manufactured MCE IR receivers


USB Sound Devices:

As the ChromeBox simply has HDMI and analog audio outputs, if you demand SPDIF, then either a converter or external/USB device must be used. The following devices have been tested/confirmed working:


HDMI-CEC:

The ChromeBox does not support HDMI-CEC natively, but support can be added using an
external USB CEC adapter
from Pulse-Viii. The USB CEC Adapter needs ability to the USB port BEFORE there is any video out, or information technology simply volition not laissez passer through whatever video point. There are several ways to piece of work effectually this:
  • Either always leave your Chromebox on, or just put information technology into standby; never plow it off
  • Employ an externally powered source (eg, USB hub, Idiot box) to power the adapter (rather than the ChromeBox itself), so it always has power
  • If you take a spare HDMI port, yous actually tin split video in and command in for 1 HDMI channel using two physical HDMI ports. The video will exist continued to the principal port, and that’s the port yous use in the HDMI config settings in Kodi, then you simply connect the USB CEC adapter to a spare HDMI port, does non appear to thing which.



5
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 utilize 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 guild to reconnect to the ChromeBox.

    An effort is underway on the forums to catalog which keyboards piece of work (and which do non); the thread (which is existence updated regularly) can be found here:
    http://forum.kodi.television receiver/showthread.php?tid=211797
  • Assistance! I’m stuck on the black SeaBIOS kicking 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 take a dual boot setup, 99% of the time this is due to non having performed a manufacturing plant reset prior to running the EZ Setup Script, as listed in the Device Prep department higher up. Simply perform the factory reset, so redo the dual boot setup using the script as earlier.
  • If you lot have a standalone setup, and are trying to boot from USB:
    If you meet the ‘Press ESC for boot carte du jour’ text only pressing it doesn’t work, then the event is your keyboard, so endeavor using a different one.
    If you
    don’t
    run across the ‘Press ESC for boot carte’ text, then the outcome is with your boot media, so try using a unlike USB flash drive.
  • Ok, I have an OS installed, but I can’t boot from USB – information technology boots also fast!
    This ways your USB boot media isn’t being recognized, otherwise you lot would have 5s to press ESC and bring up the boot carte. Re-create your kick media, possibly using a different USB stick. If y’all’re trying to kicking a Linux ISO, write the ISO directly to USB (using Win32DiskImager or dd), don’t utilize a tool like unetbootin (eg).
  • If you’re getting an error similar to “It appears your computer only has 639K of low (“DOS”) RAM.”, then you’re pressing the dual boot selection keys (CTRL-D/CTRL-L) too belatedly in the kicking sequence – they demand to be pressed on the developer fashion boot screen, before information technology boots either ChromeOS or the Legacy BIOS (SeaBIOS). On some displays, this may mean pressing them earlier the display comes on, especially if yous’ve set the boot delay to 1s.
  • If the install media created by the script doesn’t work (or you lot forget to create it earlier rebooting), so you can simply download the disk image version of LibreELEC as per the instructions above.
  • Some TVs/displays are non able to show the ChromeOS developer boot screen due to the resolution information technology uses (1024×768 @ 60Hz), in which case you’ll demand to employ a different brandish to complete the initial setup steps.
  • Many TVs have overscan enabled past default, which volition cut off the text display of the ChromeOS shell. Exist sure to set your TV to a mode which does not overscan (varies by manufacturer – oftentimes chosen ‘just scan’, ‘exact’ ‘pixel perfect’; some TVs require yous to label the input equally a PC).
  • Using a
    passive
    DisplayPort–>HDMI cable/adapter is oft problematic, and can cause the video output drop out after booting. Employ either a straight DP cable or directly HDMI/HDMI–>DVI cablevision; if yous have to utilise a DisplayPort–>HDMI adapter, exist sure it is the
    active
    type.
Read:  Removal and Unlock of the Bios Efi/firmware Passwords

No Audio and/or corrupted video on Wakeup from Suspend:

  • Some displays/AVRs don’t successfully handshake when resuming from suspend, leading to no sound output and/or corrupted video output until the Chromebox is rebooted.
    Solution: If using a universal remote, such as a Harmony, ensure that y’all are turning off (suspending) the ChromeBox
    earlier
    your AVR/TV, and turning it on (resuming)
    after
    the AVR/Television receiver.
    Solution: download/enable a script that will force the ChromeBox to reset the audio/video output on resume from suspend. Apply an SSH client like Putty to connect to the ChromeBox, and execute the following commands:

    For Openelec:

    mkdir -p /storage/.config/sleep.d
    cd /storage/.config/sleep.d
    curl -50 -O https://mrchromebox.tech/files/kodi/01-cbox_resume.power
    chmod +x 01-cbox_resume.power
    For Ubuntu:

    cd /lib/systemd/organization-slumber
    sudo wget https://mrchromebox.tech/files/kodi/01-cbox_resume.ability
    sudo chmod +x 01-cbox_resume.power
    Then reboot the ChromeBox
  • Annotation: If connected via the DisplayPort output, employ a text editor (eg, nano) to edit the script and replace references to ‘HDMI1’ with ‘DP1’.

Remote Controls:

  • About MCE IR receivers work properly at present when continued to USB3 ports under Linux with kernel 3.16+ (older kernels volition require a patch/ready); OpenELEC 4.0+ is fully upwardly to date. The version of Ubuntu installed past the ChromeBox EZ setup script in a dual boot setup also includes an up-to-date kernel. Nevertheless, some buggy MCE receivers even so practice not work properly (at all), as noted below in the Hardware/Remotes section.
For standalone Ubuntu (or whatsoever other distro) installs, you will need to update to a 3.16 (or later) kernel.


Unreliable Wireless Devices attached to USB 3.0 ports:


Power Management:

  • Suspend/resume is generally problematic with the stock firmware (dual boot setups – OpenELEC will reboot on resume), just 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 merely works when the ChromeBox is suspended, not fully powered off, and requires the MAC accost of the box to exist set (eg, in YATSE)


Windows 8/8.1/10:

  • (Updated 2016/11/17) HDMI sound now works OOTB using the custom UEFI firmware from
    https://mrchromebox.tech.
  • Bluray disc playback doesn’t work, equally PowerDVD and WinDVD report that the video drivers are non supported, even though they report the hardware is capable.
  • (Updated 2016/11/17 — now fixed in custom UEFI firmware) The CPU fan will shut down at boot and not come back on unless a utility similar SpeedFan is used to start it. After manually starting the fan (set PWM1 to l%), set Speedfan for automated control and so create a shortcut for it to run at startup.
  • Windows 7 doesn’t install/work, and so don’t ask for assist with it.
  • Discussion of running Windows on a ChromeBox tin can be establish on this forum thread:
    http://forum.kodi.boob tube/showthread.php?tid=203040

Linux Video Tearing:

  • Some users may feel screen tearing nether the Linux desktop, or when watching video (e.chiliad., Netflix). The fix for this is
    documented on the Curvation Wiki, and copied here for convenience.
from a final/trounce prompt:

sudo nano /usr/share/X11/xorg.conf.d/20-intel.conf
copy/paste the following:
Section “Device”

Identifier “Intel Graphics”
Commuter “intel”
Option “TearFree” “true”
EndSection
so relieve, get out, and reboot.


High CPU usage at Idle:

  • When running a Linux setup, in that location is loftier idle CPU usage with some older kernels which do non 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, information technology may likewise be necessary to add together the following kernel boot parameters to disable the TPM: tpm_tis.strength=ane tpm_tis.interrupts=0


No HDMI Audio on 2018/Kabylake Chromeboxes:

  • the snd_soc_skl audio driver is breaking things, and then we need to blacklist information technology. Open up the ‘configfiles’ network share on your Chromebox, then the modprobe.d folder. If information technology doesn’t already exist, create a new text file blacklist.conf and add together the line ‘blacklist snd_soc_skl’ to it. Save and reboot the Chromebox.

Deadening Ethernet performance with LibreELEC 9.0/9.01 (or kernel 4.19+):

Note: this consequence is stock-still in LibreELEC 9.0.2/kernel 4.19.36

  • A regression was introduced in kernel 4.19 which severely cripples the Realtek rt8169 Ethernet throughput on Haswell/Broadwell/Kabylake Chromeboxes (this just affects the born rt8169 Ethernet, and not wifi nor USB to Ethernet adapters). This outcome tin exist mitigated past the addition of the kernel control-line parameter ‘pcie_aspm.policy=functioning’.
On LibreELEC setups:

ssh
[email protected]<ip address>
<enter password, default is ‘libreelec’>
mount -o remount,rw /dev/sda1 /flash
(Note: use /dev/sda6 for dual-kick setups)
nano /flash/syslinux.cfg
(Annotation: will be ‘/flash/extlinux.conf’ on dual kick/legacy boot setups)
<add together ‘ pcie_aspm.policy=functioning’ subsequently ‘tranquility’>
<save and quit: CTRL+o CTRL+x>
reboot


LibreELEC Fails to kick:

  • 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:
***Mistake in check_disks: could not repair filesystem, dropping to debug crush, try to run ‘fsck’ manually: ***
### Starting debugging shell… blazon exit to quit ###
sh: tin’t access tty; job control turned off
#_

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

For a standalone setup:

fsck /dev/sda1
fsck /dev/sda2


For a dual-boot setup:

fsck /dev/sda6
fsck /dev/sda7

Afterward the fsck is run, type ‘reboot’ and so hitting [enter] and the system should boot normally.



vi
Firmware/BIOS Updating

As depicted in the overview section above, the ChromeBox’southward firmware consists of 2 master 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, equally information technology contains an updated SeaBIOS payload (which tin can non exist updated separately).

Annotation: Nether normal conditions, the ChromeBox’s firmware does not need to be updated after the initial install/update via the EZ Setup Script. Equally the former saying goes: if it ain’t bankrupt, don’t ready it. Only update if you are having an upshot that is specifically noted in the changelog as being addressed past a newer version.


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

Standalone users should likewise re-download/re-run the setup script, but instead choosing the
coreboot firmware install/update
option nether the Standalone heading. The script can be run under whatever version of Linux with a full bash vanquish; as LibreELEC does not have a full fustigate beat out, OE users will need to boot a live Linux USB (like GalliumOS or Ubuntu), every bit described near the end of
the EZ Setup Script forum postal service.


7
Resetting to Stock

If y’all take a dual boot setup, but perform a factory reset, then hit [infinite] on the developer manner boot screen to revert to verified boot mode. Done. (Notation: 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 manufactory reset to reload ChromeOS.

In order to do this, you will need to download/run the ChromeOS Firmware Utility script and select the advisable option from the menu. The script volition give you the choice 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 exist run from a Linux terminal with a full fustigate shell; OpenELEC users will demand to boot a Linux Live USB (Ubuntu 16.04 64-chip
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).

  • Boot the Linux live USB, then open a terminal/crush window
  • Download and run the ChromeOS device Firmware Utility script using the following command (striking enter later on):
    cd; curl -L -O https://mrchromebox.tech/firmware-util.sh && sudo bash firmware-util.sh
  • Select choice nine, Restore Stock Firmware
  • Choose whether to restore from a backup file on USB or non
    If not, select your ChromeBox model so the advisable firmware can be downloaded

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


8
External Links



Which Screw Remove Allow Write Firmware Hp Chromebook 14 Atheros

Check Also

How to Upgrade Firmware on Linksys Ea6700 Router

How to Upgrade Firmware on Linksys Ea6700 Router

How to Upgrade Firmware on Linksys Ea6700 Router Yous have a Linksys Etherfast Cablevision / …