[Matt Devo]

Hi Matt, - sorry let me start again. I followed this you tube video https://www.youtube.com/watch?v=9gQgSDdZuLY and used the links Lon suggested. I followed it to the letter. I did struggle to get out of the script page, I pressed "q" like it said but nothing happened so I turned the box off, however it seemed I had managed to install open elec, and when the box re booted, open elec was on the screen but it was just frozen I could not use it in any way. So I turned off the box when I tried to re boot, same thing. So I put in the chrome recovery disk and tried to start over again. I ran the recovery but it does not allow me to get to the chrome os, the screen is just blank. I just tried again and now I cant even run recovery.Do you think Ive bricked the box?

sigh, Lon's video is definitely not the right way to do things.

It sounds like the box is set to boot OpenELEC by default with a short timeout on the dev mode boot screen (which often isn't visible on TVs which are slow to change resolution/refresh rate). What you need to do is force it to boot ChromeOS by pressing [CTRL-D] right after power on, even before the video initializes (you can even hit it a few times - won't hurt).

Once you're in ChromeOS, re-run the script, and set the boot options back to the 'ChromeOS + 30s' option, then re-run the dual boot install (twice, as required for a dual boot setup). Only after the install is complete and you've tested OpenELEC should you change the boot default to OpenELEC (and/or shorten the timeout).