[Matt Devo]

Matt, I have the Asus Chromebox and did the stand alone install Openelec about a year ago. I wonder if I have to do the BIOS upgrade all over again?

I'm not sure what you are asking. To update OpenELEC, follow the instructions on the wiki. To upgrade the firmware, there is a special script for OpenELEC users that gets run via ssh.

Hi Guys first time poster here so go easy.

I have had an Asus Chromebox set up for about 6 months but recently somehow I wiped Kodi of it so I've went through the setup process again and got as far as entering the scripts. I've selected Number 2 for dual boot Kodi/ Chrome OS which is what I had before but this is were i come unstuck!!! My TV screen I have it connected up to needs calibrated once i get into Kodi so I am having problems seeing what the next option is and what I need to select. Can anyone help me out please :-)

as per the wiki, you need to disable the overscan via a setting on your TV, or use a computer monitor for the setup. Trying to guess your way thru the setup without being able to see the full text is a recipe for trouble.

Okay, if anyone is still looking for a tester of the Lenovo Broadwell i3, I just pulled the trigger, and should have it just before xmas.
I originally had the most common box on here, the m004u, running 4GB RAM, 64GB SSD, and Linux mint, and was nonplussed by the video performance on streaming sites, etc....
Also, things could get pretty choppy after some use with my subsonic music server.

Sold that several months ago, and am just now getting back into the game; we really miss our setup!
I bought the 10h30000us model, with 4GB onboard
I was really encouraged by the updates made in the last couple days, and why I think I'll really be happy with the bigger, newer, and faster processor, but more importantly, a dedicated 5500 GPU

I read the arguments on whether the new gen is cost-effective; hey, i just had some gift cards to cash in, so it's whatever

- Looking forward to locating\removing the write protect screw
- Anxious to see how much better wifi reception is with the external antenna
- I plan to do coreboot, run the script, and follow instructions for SEABOOT, with the 16GB SSD, and then after I get all that, drop my 64GB SSD back into the new unit, and go from there

don't bother welcoming me tho, I've been lurking for a loooooooong time, and I check Matt's updates on his G+ page daily.

I don't have a standalone firmware yet for the Lenovo Broadwell ChromeBoxes (board name: Tidus), since they appear to be a bit different than the Asus and Acer models (which are nearly identical firmware-wise, despite being different form factors). Hit me up via hangouts or email once you have your box and we can test a few things out, before I make anything available via the script.

[Thehub42]

Ignore or remove my post sorted it

[fvlserevere]

I can confirm the trouble is fixed, so much appreciated. Thank you, Matt. Cheers.

[dnko]

this might be a simple question but i'd appreciate your help.
I picked up an ASUS Chromebox last week. The celerion cn60 and started to the the standalone install.
i got the:
'Press ESC for boot menu'
and pressed ESC but no joy.

so i finally found another keyboard that activates when the Chromebox is turned on but now i have nothing on the display - a black screen.
i take out the usb disk and same thing.
tried multiple thumb drives with same response.
I'm using a HDMI to VGA adapter and wondering if that could be the problem.
was thinking of getting a displayport to vga and try again.

your thoughts please.

[Matt Devo]

this might be a simple question but i'd appreciate your help.
I picked up an ASUS Chromebox last week. The celerion cn60 and started to the the standalone install.
i got the:
'Press ESC for boot menu'
and pressed ESC but no joy.

so i finally found another keyboard that activates when the Chromebox is turned on but now i have nothing on the display - a black screen.
i take out the usb disk and same thing.
tried multiple thumb drives with same response.
I'm using a HDMI to VGA adapter and wondering if that could be the problem.
was thinking of getting a displayport to vga and try again.

your thoughts please.

how do you know the "new" keyboard works if there's nothing on the display? what changed in your setup between when it worked and when it didn't? There's likely no difference between a HDMI->VGA adapter and a DP->VGA one, since both are active adapters (ie, actually convert one signal to the other)

[dnko]

I originally setup the chromebox thru a kvm. keyboard/mouse, video worked.
got down the press ESC and keyboard didnt respond. light on the keyboard was not on at that point either. at that point nothing had changed.
connected a couuple of other keyboards into the box thru usb and their lite didnt come on when i rebooted the box.
found another keyboard that the light came on when i rebooted.
but no video out thru this whole scenario.

[Matt Devo]

I originally setup the chromebox thru a kvm. keyboard/mouse, video worked.
got down the press ESC and keyboard didnt respond. light on the keyboard was not on at that point either. at that point nothing had changed.
connected a couuple of other keyboards into the box thru usb and their lite didnt come on when i rebooted the box.
found another keyboard that the light came on when i rebooted.
but no video out thru this whole scenario.

try directly connecting the box to a display via HDMI or DP without any converters, adapters, etc

[dnko]

Connected everything directly to ChromeBox.
everything is working.
tyvm

[Boulder]

To upgrade the firmware, there is a special script for OpenELEC users that gets run via ssh

Hi Matt,

can you please tell me how to do this? For some reason, I cannot get to boot to ChromeOS as I only get the "low memory error". Thus, I need to update the firmware in OpenELEC.

[Matt Devo]

To upgrade the firmware, there is a special script for OpenELEC users that gets run via ssh

Hi Matt,

can you please tell me how to do this? For some reason, I cannot get to boot to ChromeOS as I only get the "low memory error". Thus, I need to update the firmware in OpenELEC.

the "low memory error" you're referring to is likely a result of hitting CTRL-D on the SeaBIOS boot screen, rather than the ChromeOS dev boot screen before it. If you're running a dual boot setup, then hit CTRL-D before the SeaBIOS screen (before the screen inits, if needed). You can then run the EZ Setup Script and update the legacy boot payload (SeaBIOS).

If you're running a standalone setup, then obviously you can't boot ChromeOS, since you're running the standalone firmware. Open up a ssh session to OpenELEC, and run the standalone firmware update script as directed near the end of the first post.

Of course, if everything is working fine, there's no need whatsoever to update the firmware or legacy boot payload.

[AMiGAmann]

I want to switch from single (OpenELEC) to dual boot. But I cannot get to the recovery screen again. I have a HP Chromebox but I am unable to open the recovery screen: device is switched off, paperclip is in the hole, device is powered on, paperclip is removed after some time, OpenELEC is booting...

Is it possible to run EZ Setup from OpenELEC shell when logged in via SSH?

[Matt Devo]

I want to switch from single (OpenELEC) to dual boot. But I cannot get to the recovery screen again. I have a HP Chromebox but I am unable to open the recovery screen: device is switched off, paperclip is in the hole, device is powered on, paperclip is removed after some time, OpenELEC is booting...

Is it possible to run EZ Setup from OpenELEC shell when logged in via SSH?

no, read the wiki page. It tells you exactly what you need to do to restore to stock, after which you can use the script for a dual boot setup.

[AMiGAmann]

In the wiki I read: "If you have a standalone setup and wish to switch to a dual boot setup, you need to first restore the stock firmware". The link "restore the stock firmware" leads to a dead link.

I pretend I have to do a factory reset. To do that I have to:

- 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

But as I described, I cannot get to the recovery screen...

EDIT: Okay, I finally found the section.

Nevertheless the dead link in the Wiki should be adjusted!

It leads to http://kodi.wiki/view/Chromebox#Restorin...k_Firmware but should probably lead to 7 Resetting to Stock
7 Resetting to Stock

[Boulder]

To upgrade the firmware, there is a special script for OpenELEC users that gets run via ssh

Hi Matt,

can you please tell me how to do this? For some reason, I cannot get to boot to ChromeOS as I only get the "low memory error". Thus, I need to update the firmware in OpenELEC.

the "low memory error" you're referring to is likely a result of hitting CTRL-D on the SeaBIOS boot screen, rather than the ChromeOS dev boot screen before it. If you're running a dual boot setup, then hit CTRL-D before the SeaBIOS screen (before the screen inits, if needed). You can then run the EZ Setup Script and update the legacy boot payload (SeaBIOS).

If you're running a standalone setup, then obviously you can't boot ChromeOS, since you're running the standalone firmware. Open up a ssh session to OpenELEC, and run the standalone firmware update script as directed near the end of the first post.

Of course, if everything is working fine, there's no need whatsoever to update the firmware or legacy boot payload.

I've been trying to hit CTRL-D quite a few times right after powering on the box but still it gives me the same error. Does it hurt to hit it many times or should I just try it once early enough?

[Matt Devo]

In the wiki I read: "If you have a standalone setup and wish to switch to a dual boot setup, you need to first restore the stock firmware". The link "restore the stock firmware" leads to a dead link.

I pretend I have to do a factory reset. To do that I have to:

- 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

But as I described, I cannot get to the recovery screen...

EDIT: Okay, I finally found the section.

Nevertheless the dead link in the Wiki should be adjusted!

It leads to http://kodi.wiki/view/Chromebox#Restorin...k_Firmware but should probably lead to 7 Resetting to Stock
7 Resetting to Stock

wiki link fixed, sorry about that.

I've been trying to hit CTRL-D quite a few times right after powering on the box but still it gives me the same error. Does it hurt to hit it many times or should I just try it once early enough?

are you sure you didn't flash the standalone firmware at some point? If powering on the box with the recovery button pressed (via paperclip) doesn't bring you to the recovery screen, then you have the standalone firmware installed. But again, not sure what you're trying to do exactly, other than update for the sake of having the latest