[Arse4life]

Matt, would I have to press ctrl+alt f2 to accomplish "sudo reboot" in the Chome OS sign in window? Thanks!

[Leclair]

Is there a specific brand/size that you could suggest?

I have tried 2 different SD cards and 3 different USB sticks.

Also, if it is the USB install media causing the issue, can I assume the HP keyboard that worked during the dual-boot install should work once I find a USB stick that is compatible?

Thanks for all the help thus far.

that really seems unlikely that all those different keyboards and USB/SD media aren't compatible. I've only had one keyboard that wouldn't work (an older wired logitech mini) and no USB/SD media that were problematic. I use a Logitech K360 keyboard and Sandisk, Patriot, and Silicon Power USB sticks (and Sandisk and Lexar SD cards).

After a lot of trial and error, I decided to read the wiki really carefully again. Turns out I wasn't hitting Ctrl-D early enough to get to the ChromeOS.

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.

Anyways, I was able to run the EZ-script for a dual-boot and everything is working great again! And this time, I set the delay to 30s.

Thanks again for the assistance.

[ashman70]

I am having the same problem and have tried five different flash drives, of different sizes 4GB, 8GB, 16GB and an 8GB microSD card in a SD adapter, the results are the same everytime, on boot to the flash drive, it has a kernel panic.

Help I need to restore this chrome box back to factory settings.

[Matt Devo]

Matt, would I have to press ctrl+alt f2 to accomplish "sudo reboot" in the Chome OS sign in window? Thanks!

If you're not already signed in, then yes. If you are, then CTRL-T in a browser window will give you a prompt as well

I am having the same problem and have tried five different flash drives, of different sizes 4GB, 8GB, 16GB and an 8GB microSD card in a SD adapter, the results are the same everytime, on boot to the flash drive, it has a kernel panic.

Help I need to restore this chrome box back to factory settings.

RTFW and first post plz

[HarryMohan]

I am new to this form, I am 61 years old. I think did everything as per guide

1. I have firmware backup
2.Created Kodi OS on USB

After rebooting I saw kodi running. Did not ask me if wanted to install OS. When I reboot again there is blank screen. I an not able to restore
ChromiumOS , Nothing happens. Black screen.

What did I do wrong? How can UN Brick my Asus Chrome box. I am completely lost.

Please HELP!!!

[Matt Devo]

I am new to this form, I am 61 years old. I think did everything as per guide

1. I have firmware backup
2.Created Kodi OS on USB

After rebooting I saw kodi running. Did not ask me if wanted to install OS. When I reboot again there is blank screen. I an not able to restore
ChromiumOS , Nothing happens. Black screen.

What did I do wrong? How can UN Brick my Asus Chrome box. I am completely lost.

Please HELP!!!

for #2, did you create the Kodibuntu or OpenELEC installer? I assume the former. The current custom Kodibuntu installer has some issues, I meant to pull it until it gets updated. But either way, you haven't provided enough info to help troubleshoot:

1) standalone or dual boot setup
2) display and type of connection used
3) any output when booting without the USB connected?

I'd create an OpenELEC USB installer (using another PC, follow directions in wiki) and see if that will boot for you.

[HarryMohan]

Hi Matt,
I created Kodibuntu set up,
I did back up original firmware.
standalone set up.
HDMI connected to 720p Samsung TV.
Wired keyboard & Mouse
Scandisk 8GB Flash Drive.


Thank you.

[Matt Devo]

Unless there's something Kodibuntu does that OpenELEC doesn't and you need, that's the route I'd recommend you go. It's nearly fool-proof

Also the custom Kodibuntu version used by the script has an issue with displays that aren't 1080p (since it tries to force the output resolution to that)

[HarryMohan]

Unless there's something Kodibuntu does that OpenELEC doesn't and you need, that's the route I'd recommend you go. It's nearly fool-proof

Also the custom Kodibuntu version used by the script has an issue with displays that aren't 1080p (since it tries to force the output resolution to that)

When I installed coreboot, I think I might have selected boot from hard drive, now it wont allow me update with OpenELEC, even with esc.
Nothing happens, unit is on. Any suggestions.

[azzurri13]

I am trying to install a dual-boot system - When I go to download the recovery utility, it says "Not compatible - requires chrome version of at least 38"

How can I get around this? I tried manually downloading the file as listed in the wiki. I opened it on my mac and wrote it to a flash drive using ApplePi Baker. When I plugged it into the chrome box it said "No chrome os present on flash drive"

Appreciate any help or advice

[zirbenaum]

Hello Matt and thanks for the script.

I have kodibuntu installed in standalone and everything works fine except one small issue.

After i wake up the chromebox from suspend the fan blows at full speed for a random time. Sometimes it spins down after a minute or two, but normally I just reboot because I don't want to listen the noise. Any help would be appreciated.

[Matt Devo]

When I installed coreboot, I think I might have selected boot from hard drive, now it wont allow me update with OpenELEC, even with esc.
Nothing happens, unit is on. Any suggestions.

selecting the hard drive as the boot device would have no effect on the next boot. I'd try booting the OpenELEC installer blindly by hitting 'ESC' then '2' a few times in sequence

I am trying to install a dual-boot system - When I go to download the recovery utility, it says "Not compatible - requires chrome version of at least 38"

How can I get around this? I tried manually downloading the file as listed in the wiki. I opened it on my mac and wrote it to a flash drive using ApplePi Baker. When I plugged it into the chrome box it said "No chrome os present on flash drive"

Appreciate any help or advice

update ChromeOS first by going to settings/about and it should auto-update. Or write the image to USB using dd from the terminal.

Hello Matt and thanks for the script.

I have kodibuntu installed in standalone and everything works fine except one small issue.

After i wake up the chromebox from suspend the fan blows at full speed for a random time. Sometimes it spins down after a minute or two, but normally I just reboot because I don't want to listen the noise. Any help would be appreciated.

known issue. not sure if it's a firmware or OS problem. I have the firmware coded so that when it wakes from suspend, if it can't get a valid temp reading that the fans default to the lowest speed, not highest, but occasionally it still does.

[Twixs]

I'm having some serious trouble with this and I think I done messed up pretty badly and am pleading for help!~

I was following the instructions line by line...when I finally got to the install Kodi screen for a single boot Asus Chromebox. When I hit enter on Run Installer, however, it just kicked me back to the select boot screen or somewhere before that. This is where things started unraveling. Since it kept doing that, I figured I'd try the update firmware option on the script...except I hit the wrong one. I went with the dual boot one. Once that was done installing I couldn't get back to the command prompt to try anything else. There would be 2 or 3 black lines on top of the recovery screen saying something about SeaBIOS (I think) and being read only.

Then I read that you can get into the command prompt through the browser...so I tried some of that and got to do the standalone firmware update, I think I might have messed with the settings somehow because now I can't even get to the recovery screen. It just goes straight to booting from the HDD unless I have a USB drive in which case it asks me which to boot. I can't even get to the recovery screen if I push the recovery button with a paperclip.

I've installed the ChromeOS recovery image on a thumb drive and if I try to boot from it, it basically crashes to a long line of file executions and the word "panic" every so often. If I let it boot to the HDD, ChromeOS starts to load it but then it gets in an infinite loop of restarts before ChromeOS fully boots.

The furthest I've gotten with ChromeOS booting on it's own recently was after inputting my google username/password. It just sat there for 15 minutes 'thinking' about what to do next.

The SeaBIOS string I have is rel-1.8.0-11-g647b459-20150226

Have I destroyed my box? Any help would be much much appreciated as my new home theater is going to pretty much revolve around this setup.

If there's any other information I need to provide let me know, I think I got all of it from the front page...

[jwegman]

Good day Matt,

Just some feedback In the event that no one else has mentioned this; when running on the new Pixel 2015 (Broadwell), the script will automatically flash a Legacy BIOS despite this device already having one. Although I didn't leave that new Legacy BIOS in place for long, I don't think it worked correctly on the Pixel 2015...

google@pixel:~$ sudo dmidecode | grep -m1 "Product Name:" | awk '{print $3}'
Samus

By the by, the Pixel 2015 LS makes a fairly decent Kodi box

Regards,
Jake

[HarryMohan]

When I installed coreboot, I think I might have selected boot from hard drive, now it wont allow me update with OpenELEC, even with esc.
Nothing happens, unit is on. Any suggestions.

selecting the hard drive as the boot device would have no effect on the next boot. I'd try booting the OpenELEC installer blindly by hitting 'ESC' then '2' a few times in sequence

Matt, thank you. I tried your suggestion again, this time it worked. THANK YOU....Am i limited to skins or any skin would work?