[nickr]

Did you update the firmware?

[Matt Devo]

My chromebox has been behaving super weird lately. Nothing wrong with it at all, just being really strange, let me explain.

Running the latest firmware and 6.0.98 like I have been for weeks. Just yesterday, whenever I boot the chromebox (from power off). It turns on SUPER QUICK, no boot flash screen to select boot from USB or anything, just boots directly in to kodi at lightning speed, like as it was waking from suspend.

I tried powering off and on the chromebox like 10 times throughout the day yesterday to see if the behavior would persist, and it does lol. Only one time out of like 10 did the flash screen at boot up pop up, every other time, directly in to Kodi lol.

Lol yeah, I'm not really complaining, since I never boot from USB and this is even better, but super weird none the less. Right? Or wrong?

that's normal when no USB device is attached, or the attached device doesn't init properly. With OpenELEC, on a cold boot, from pressing the power button to the Kodi GUI should take about 6s. It won't pause at the boot screen if there's only one boot device.

[camshaft]

Thank you for your help.

I have rebooted using the power switch and still no joy. My screen reads two lines:

SeaBios (version rel-1.9.0-56-gc76f23e-20160103-MattDevo)
Booting from Hard Disk
_

I have tried the three keyboards in my house. No Joy.

Is there something else I may try?

[Matt Devo]

Thank you for your help.

I have rebooted using the power switch and still no joy. My screen reads two lines:

SeaBios (version rel-1.9.0-56-gc76f23e-20160103-MattDevo)
Booting from Hard Disk
_

I have tried the three keyboards in my house. No Joy.

Is there something else I may try?

try a different USB stick. It's possible that the USB stick is preventing the keyboard from initing properly. Also try using a front and rear USB port, rather than both front ports

[camshaft]

Got my keyboard working...

Going through the trouble shooting section of the wiki. copied my files to another usb. Got it to "select boot device" When I choose the usb drive i get the following message:


Booting from USB device...

invalid system disk
replace the disk, and then press any key

This is the second usb i have tried. Should I start over? Where?

edit update: I have now copied the files from the original usb onto two others and may be having some success. Stayed tuned...

[ilovethakush]

My chromebox has been behaving super weird lately. Nothing wrong with it at all, just being really strange, let me explain.

Running the latest firmware and 6.0.98 like I have been for weeks. Just yesterday, whenever I boot the chromebox (from power off). It turns on SUPER QUICK, no boot flash screen to select boot from USB or anything, just boots directly in to kodi at lightning speed, like as it was waking from suspend.

I tried powering off and on the chromebox like 10 times throughout the day yesterday to see if the behavior would persist, and it does lol. Only one time out of like 10 did the flash screen at boot up pop up, every other time, directly in to Kodi lol.

Lol yeah, I'm not really complaining, since I never boot from USB and this is even better, but super weird none the less. Right? Or wrong?

that's normal when no USB device is attached, or the attached device doesn't init properly. With OpenELEC, on a cold boot, from pressing the power button to the Kodi GUI should take about 6s. It won't pause at the boot screen if there's only one boot device.

OMFG, that's exactly what it is!

Yesterday I was booting the chromebox with no USB HD (storage) attached, which prior to I ALWAYS had the HD attached, 100% of the time.

Gotta say though, it doesn't feel like 6 seconds to boot, feels like 1 second at most. I'd say it's closer to the 6 seconds when you do see the boot screen.

[Matt Devo]

Got my keyboard working...

Going through the trouble shooting section of the wiki. copied my files to another usb. Got it to "select boot device" When I choose the usb drive i get the following message:


Booting from USB device...

invalid system disk
replace the disk, and then press any key

This is the second usb i have tried. Should I start over? Where?

edit update: I have now copied the files from the original usb onto two others and may be having some success. Stayed tuned...

you can't just copy the files from one USB to another and expect it to work - for one, the resulting media won't be bootable. Here again, the wiki has instructions for properly creating install media in the case that the media created by the script / your USB stick doesn't work

[camshaft]

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?

[Matt Devo]

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:

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

[giant25]

Hey Matt, thanks for all your help. I got it all set up *phew*. On my Samsung 4K I'm getting no signal I saw it in the wiki but is there any other fix for this problem for the dual boot setup besides unplugging the HDMI and turning on the chromebox and plugging in the HDMI? My regular Samsung LED TV it works flawless.

eLMushi,
I have an ASUS Chromebox plugged into a Samsung UN65JU6500 4k TV. I had to turn on HDMI UHD Color in the Picture Options menu on HDMI 1, where my Chromebox is plugged in. I also had to force 1080p 60hz using xrandr. Hopefully you can ssh into the Chromebox/Openelec already. Read back a few pages of this thread and see my posts. If you're still not getting there, let me know.

[nickr]

Hi Matt

I bought a second hand asus chromebox and am attempting to set it up. I have done 3 before and am generally familiar with the process. I have removed the write protect screw and am attempting to get into developer mode.

If I just turn it on, it boots to chromeOS.

If I press the recovery button, turn it on and release the recovery button it comes up with a "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card" and in the top left is a text message:

gbb.flags is nonzero: 0x00000039
read-only firmware id: Google_Panther.4920.24.21
active firmware id: Google Panther.4920.24.21

I press tab (as suggested by you to a similar problem earlier in the thread) and get some lines of error message, which I can get for you if necessary.

Where to from here?

[Matt Devo]

Hi Matt

I bought a second hand asus chromebox and am attempting to set it up. I have done 3 before and am generally familiar with the process. I have removed the write protect screw and am attempting to get into developer mode.

If I just turn it on, it boots to chromeOS.

If I press the recovery button, turn it on and release the recovery button it comes up with a "Chrome OS is missing or damaged. Please insert a recovery USB stick or SD card" and in the top left is a text message:

gbb.flags is nonzero: 0x00000039
read-only firmware id: Google_Panther.4920.24.21
active firmware id: Google Panther.4920.24.21

I press tab (as suggested by you to a similar problem earlier in the thread) and get some lines of error message, which I can get for you if necessary.

Where to from here?

nothing there sounds out of the ordinary, though the boot flags being 0x39 means someone restored the stock firmware using my script before resale. It also means it's already in developer mode, so you should be able to just open a terminal from the login screen via CTRL-ALT-F2 and proceed from there.

[nickr]

Well that was easy, thanks. I'd never struck that before and was afraid I'd bought a dud, or would brick it.

[eLMushi]

Hey Matt, thanks for all your help. I got it all set up *phew*. On my Samsung 4K I'm getting no signal I saw it in the wiki but is there any other fix for this problem for the dual boot setup besides unplugging the HDMI and turning on the chromebox and plugging in the HDMI? My regular Samsung LED TV it works flawless.

eLMushi,
I have an ASUS Chromebox plugged into a Samsung UN65JU6500 4k TV. I had to turn on HDMI UHD Color in the Picture Options menu on HDMI 1, where my Chromebox is plugged in. I also had to force 1080p 60hz using xrandr. Hopefully you can ssh into the Chromebox/Openelec already. Read back a few pages of this thread and see my posts. If you're still not getting there, let me know.

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.

[marcfrisa1]

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