(2016-01-16, 18:08)marcfrisa1 Wrote: Hi All.
I'm running OpenElec 6.0 on asus celeron chrome-box. It has been flawless until i upgraded my receiver and TV. Onkyo TX-NR545 and Vizio 65" 4K D-series. All HDMI 2.0 HDCP 2.2. Initially it played great even Dolby ATMOS. however it crashed in the movie menu area after which it will not reboot unless i plug it into a non HDMI 2.0 or HDCP 2.2 TV. but it wont work on the current setup. I have change cables the receiver and the Chromebox. Thanks

(2016-01-16, 17:22)eLMushi Wrote: Sweet I have the same TV. Will try it when I get home. Not sure what you mean when you ask if I can SSH but I'll try to figure it out. Thank's again.

(2016-01-16, 03:16)Matt Devo Wrote:

(2016-01-16, 02:56)camshaft Wrote: Hi Matt,
Thank you for your patience. Would you please do me one more favor and point me to where in the wiki the instructions you mention are?

in the troubleshooting section, here:

Quote:

• If the install media created by the script doesn't work (or you forget to create it before rebooting), then you can simply download the disk image version of OpenELEC 6.0 Intel-EGL build here; alternately, you can download the latest stable Generic 64-bit build (or beta/RC if you'd like) from OpenELEC's website here. Download the disk image version (not update file), and create the install media, as per the instructions on the OpenELEC wiki.
  

(2016-01-17, 02:55)TimPro Wrote: Noob here. TRYING to set up a chrome box to be my kodi player so that I can ditch the lackluster AppleTV2 I'm currently using for Kodi.
I thought that I followed the steps to a T on the walk-through but I guess I messed something up along the way.

I have the Asus Chromebox CN60, trying to run a standalone set up, don't really have a preference though.
And an older Macbook Pro chugging along.

I disabled firmware protect.
I put in developer mode.
I believe I performed the factory reset.
I even got to the point where I ran the Chromebox Setup Script.
The box then reset and came back with the "Press ESC for boot menu"
It won't boot from the Internal HD, and I have yet to successfully get it to boot from a USB stick. (I tried 7 different sticks)
I created a Chromebox Recovery Stick and when I boot from that, It displays the white Chrome logo and then just keeps rebooting.

Please give me some guidance here fellas.

Thanks in advance.

(2016-01-20, 07:12)GemofGod Wrote: After doing a dual boot Chrome OS/Ubuntu, can I go back and make an sd card with the OpenELEC and follow those directions also so I can try OpenELEC as well or will that change the Legacy boot so it doesn't work with ubuntu?

(2016-01-21, 18:22)KayZey78 Wrote: Anyone have any success with Tonymacx86's Unibeast? I am trying to get it on a Asus Chromebox with i7.

Here's the link to Tonymacx86

(2016-01-22, 00:11)bigcat400 Wrote: My chromebox is running kodi 14.2, I'd like to upgrade. I have a standalone install with openelec. Can anyone point me to instructions to update openelec/kodi?

thanks

(2016-01-22, 00:26)Matt Devo Wrote:

(2016-01-22, 00:11)bigcat400 Wrote: My chromebox is running kodi 14.2, I'd like to upgrade. I have a standalone install with openelec. Can anyone point me to instructions to update openelec/kodi?

thanks

They're on the wiki

(2016-01-22, 01:01)bigcat400 Wrote: Thanks. I just updated with OpenELEC-Generic.x86_64-6.0.98-fritsch.tar. I was wondering if there were openelec builds with kodi 16 (jarvis). Couldn't see in the openelec download page, though not sure why they don't show the version of kodi that's included.

(2016-01-22, 21:51)mightiK Wrote: Thanks for the great info in this forum! Searched my issue but cannot find adequate solution....

I'm replacing my Windows HTPC to this Chromebox. I hook up my dual boot Chromebox (OpenELEC) to a Vizio M-series tv HDMI port, and found that when power on the box, the developer screen will not show on the TV. It will not accept CTRL-L nor CTRL-D, nor get into default OS after 30 seconds of idle, it simple won't boot other than the power light on the box is on. If I unplug the HDMI and reboot, the box actually boot up fine, and even I then connect back to the TV during the first 30 seconds (before it auto boot into OS), the TV will show the developer screen just fine. The box is working fine with my other HDMI display.

It is obviously a device hand-shake issue, but I don't have a clue how to tackle this problem. Any recommendation please?