[mxlance]

i will try again

[mxlance]

i have no idea what is happening.
but the 6th try it has worked. i am in.

the only thing i did differently this time was rather than wait at the white verification off screen i hit ctrl-d

i have another box to do also for a friend hope it works better.

thank you for the help and the script

[Matt Devo]

i have no idea what is happening.
but the 6th try it has worked. i am in.

the only thing i did differently this time was rather than wait at the white verification off screen i hit ctrl-d

i have another box to do also for a friend hope it works better.

thank you for the help and the script

That's the first and only time I've seen anyone report that error in the 2+ years the script has existed, so chances of a repeat are likely slim. Whether or not you use the keyboard shortcut to skip the dev boot screen has no effect on anything at all

[mxlance]

hello matt,
well it did the exact same thing on the other hp chromebox i am setting up.
i had to reboot 5, 6 or 7 times re-entering the script download each time.
i made sure to do everything the same each time and suddenly it worked.
very strange!
the only thing i though of is these are both refurbished units. who knows?
thanks again for the support.

[Matt Devo]

hello matt,
well it did the exact same thing on the other hp chromebox i am setting up.
i had to reboot 5, 6 or 7 times re-entering the script download each time.
i made sure to do everything the same each time and suddenly it worked.
very strange!
the only thing i though of is these are both refurbished units. who knows?
thanks again for the support.

I'm guessing it's an issue with the server redirecting http to https, and perhaps the error is due to the box being fresh and not having synchronized time/date yet, which would result in the certs being invalid.

either way, the boxes being refurbs isn't a contributing factor

[mxlance]

it is a crazy computer kind of day.
galliumos is installed and running smooth on both and kodi is installing on one as i write.
thanks again hopefully i will not bug you any further.
i truly am grateful for all you do for us kodi/chromebox noobs.

[guymarc]

Hello matt and all,

I have an Asus Chromebox-M036U (intel haswwel celeron 2955U @ 1.40GHz)
I installed with your ez-setup in april 2015

I have run it with openelec and now I have a debian jessie with kodi 15.2 from backports

Under both OSes
* some video playback may stutter a bit (you never kown if the problem comes from the box or from a bad encoding of the video)
* some rare times, I can hear the fan starting

I noticed in the release history some upgrades of the video bios and a tweak on fan speeds tresholds.
There are the seabios and coreboot updates as well.

2015-06-04
------------------------------------------------------------------
- tweaked fan speeds/temp thresholds for coreboot firmware for Haswell ChromeBoxes
2015-06-10
------------------------------------------------------------------
- updated video BIOS for Haswell ChromeBoxes
2016-04-18
------------------------------------------------------------------
- Update VBIOS to v1040 on hsw/bdw Chromeboxes

You recommend "if it's not broken, don't fix it" and I am always a bit worried when it comes to flashing a box.
Do you think it is worth the trouble upgrading my box, and btw, is cbox-firmware-update.sh the right script to use and can it be done from a ssh shell?

[Matt Devo]

I have run it with openelec and now I have a debian jessie with kodi 15.2 from backports

Under both OSes
* some video playback may stutter a bit (you never kown if the problem comes from the box or from a bad encoding of the video)
* some rare times, I can hear the fan starting

a firmware update won't do anything for video playback issues, which could be anything - impossible to tell without the debug log (and other info) requested in the OP when reporting issues. It's normal to hear the fan at boot and if the system is under load for an extended period of time

[movie78]

I have a Standalone setup and i can figure out to get back to factory Default.

This the instruction that i am using.

2.3 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.
Create recovery media using step 2 of Google's instructions here: https://support.google.com/chromebook/an...0595?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.
With the device powered off, use a paperclip to press the Recovery button and power on the device
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:
Haswell Boxes:
Asus CN60: https://dl.google.com/dl/edgedl/chromeos...mp.bin.zip
HP CB1: https://dl.google.com/dl/edgedl/chromeos...v2.bin.zip
Acer CXI: https://dl.google.com/dl/edgedl/chromeos...mp.bin.zip
Dell 3010: https://dl.google.com/dl/edgedl/chromeos...mp.bin.zip
Broadwell Boxes:
Asus CN62: https://dl.google.com/dl/edgedl/chromeos...mp.bin.zip
Acer CXI2: https://dl.google.com/dl/edgedl/chromeos...mp.bin.zip
Lenovo: https://dl.google.com/dl/edgedl/chromeos...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

[Matt Devo]

I have a Standalone setup and i can figure out to get back to factory Default.

This the instruction that i am using.

2.3 Perform a Factory Reset

you should start with section 7, Resetting to Stock. You have to restore the stock firmware before using the recovery media to reinstall ChromeOS

[jmhenry5150]

I am getting the same handshake error. Any ideas?

SSL23_GET_SERVER_HELLOslv3 alert handshake failure.

[movie78]

I have a Standalone setup and i can figure out to get back to factory Default.

This the instruction that i am using.

2.3 Perform a Factory Reset

you should start with section 7, Resetting to Stock. You have to restore the stock firmware before using the recovery media to reinstall ChromeOS

OK Matt I am trying section 7, created the recovery USB boot drive, but on boot kodi start automatically.

What is the key press option to boot from USB or what I m doing wrong?

[teki4u]

Press ESC key and select the number of your USB drive , if it still doesn't boot then its your USB drive's fault and you should try others (this has been mentioned several times, everything's on the wiki, I suggest you to read the whole Chromebox wiki page).

[movie78]

What ever i do, it boot straight to Kodi....

I am running a Standalone setup..

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).

Boot the Linux live USB, then open a terminal/shell window
Download and run the ChromeOS device Firmware Utility script using the following two commands (hit enter after typing each command):
curl -L -O http://mrchromebox.tech/firmware-util.sh
sudo bash firmware-util.sh
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.

[robca]

What ever i do, it boot straight to Kodi....

I am running a Standalone setup..

What keyboard are you using? Many wireless keyboard do not properly send ESC. If at all possible, use a wired USB keyboard, that is guaranteed to work