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

Jesus, you're lucky the thing boots at all honestly. When it comes to firmware, it's really best not to go off-book when things don't work as expected - that's how you end up with a bricked device.

let's start fresh - power on the device with the recovery button depressed, then insert the recovery media and let it do it's thing. Then, follow the instructions from the step where you download/run the script for whichever setup you want (standalone or dual boot).

The recovery button doesn't even do anything anymore. By the time anything is even displayed on the screen it either says press escape for boot menu (with USB media attached) or "Booting the Kernel" or something. It's not even getting to ChromeOS anymore. Just the Chrome screen then reboots itself infinitely.

I think I've learned an expensive lesson.