[Peentoo]

Hey Matt,

Thank you for your work on the awesome script.

I have searched all through the forms and haven't found the solution to getting the screen to work after saying yes to the headless option.

I used the script, under the standalone option to replace the firmware with the following options:
1. Backed up the firmware
2. Set the headless to yes (this is my focus)
3. Set it to boot from USB

Then I restarted and have plugged in a USB install drive (Ubuntu 15.4)

My issue:
If I select to boot from the internal drive, I get a screen that is consistently blank (but not off)
If I boot to the USB stick and tell it to install, it will look like it's starting (text flashes quickly and disappears) and then go back to the consistently blank screen.

I have tried using the ChromeOS recovery method and spamming Ctrl-D to no avail (as was suggested to another post). In short, I am unable to get back to the login in any way.

I want to know how to change back to the answer of no to the headless option so that I can install Ubuntu (assuming the headless option is the rason for the blank screen) but since I can't get anything to show up on the screen I am lost.

Please advise.

[Matt Devo]

Hey Matt,

Thank you for your work on the awesome script.

I have searched all through the forms and haven't found the solution to getting the screen to work after saying yes to the headless option.

I used the script, under the standalone option to replace the firmware with the following options:
1. Backed up the firmware
2. Set the headless to yes (this is my focus)
3. Set it to boot from USB

Then I restarted and have plugged in a USB install drive (Ubuntu 15.4)

My issue:
If I select to boot from the internal drive, I get a screen that is consistently blank (but not off)
If I boot to the USB stick and tell it to install, it will look like it's starting (text flashes quickly and disappears) and then go back to the consistently blank screen.

I have tried using the ChromeOS recovery method and spamming Ctrl-D to no avail (as was suggested to another post). In short, I am unable to get back to the login in any way.

I want to know how to change back to the answer of no to the headless option so that I can install Ubuntu (assuming the headless option is the rason for the blank screen) but since I can't get anything to show up on the screen I am lost.

Please advise.

booting from the internal drive won't work until you install a bootable OS (ChromeOS won't boot with my custom firmware)
booting from USB clearly works, there's just an issue with the Ubuntu installer setting the video mode it would seem. Have you tried another distro to see if it has the same issue?

you can't restore ChromeOS unless you restore the stock firmware first, which isn't necessary. I'm not sure that the headless option is your issue, but you can always boot another Live linux USB and re-run the script and install the firmware w/o the headless option to test that.

[TDB73]

IEverything Kodi/openelec related works beautifully the only issue I am having is actually getting it to boot into chrome os.

"having an issue" doesn't tell us what the problem is, so there's no way to help you. Tell us what the problem is, what you are doing, etc.

Here is a picture of the message I get when I press either CTL D or CTL L on boot http://screencast.com/t/eEH2Ell24

Problem is I have been able to boot into chrome os using the same CTL D or CTL L keys

Its letting me boot into chrome os about 2 out of 10 tries

[Matt Devo]

Here is a picture of the message I get when I press either CTL D or CTL L on boot http://screencast.com/t/eEH2Ell24

Problem is I have been able to boot into chrome os using the same CTL D or CTL L keys

Its letting me boot into chrome os about 2 out of 10 tries

That tells me you are pressing CTRL-D after the dev mode boot screen, which is interrupting the legacy boot. You need to press it earlier.

[TDB73]

Here is a picture of the message I get when I press either CTL D or CTL L on boot http://screencast.com/t/eEH2Ell24

Problem is I have been able to boot into chrome os using the same CTL D or CTL L keys

Its letting me boot into chrome os about 2 out of 10 tries

That tells me you are pressing CTRL-D after the dev mode boot screen, which is interrupting the legacy boot. You need to press it earlier.

Works perfectly now. I appreciate you answering my post so quickly. Thanks

[Matt Devo]

Works perfectly now. I appreciate you answering my post so quickly. Thanks

np. I added a note to the Troubleshooting section of the wiki for this issue.

[Peentoo]

Hey Matt,

Thank you for your work on the awesome script.

I have searched all through the forms and haven't found the solution to getting the screen to work after saying yes to the headless option.

I used the script, under the standalone option to replace the firmware with the following options:
1. Backed up the firmware
2. Set the headless to yes (this is my focus)
3. Set it to boot from USB

Then I restarted and have plugged in a USB install drive (Ubuntu 15.4)

My issue:
If I select to boot from the internal drive, I get a screen that is consistently blank (but not off)
If I boot to the USB stick and tell it to install, it will look like it's starting (text flashes quickly and disappears) and then go back to the consistently blank screen.

I have tried using the ChromeOS recovery method and spamming Ctrl-D to no avail (as was suggested to another post). In short, I am unable to get back to the login in any way.

I want to know how to change back to the answer of no to the headless option so that I can install Ubuntu (assuming the headless option is the rason for the blank screen) but since I can't get anything to show up on the screen I am lost.

Please advise.

booting from the internal drive won't work until you install a bootable OS (ChromeOS won't boot with my custom firmware)
booting from USB clearly works, there's just an issue with the Ubuntu installer setting the video mode it would seem. Have you tried another distro to see if it has the same issue?

you can't restore ChromeOS unless you restore the stock firmware first, which isn't necessary. I'm not sure that the headless option is your issue, but you can always boot another Live linux USB and re-run the script and install the firmware w/o the headless option to test that.

Thank you for your very good response.

Turns out the "Display Port" port was not outputting a signal (after leaving the boot menu) but the HDMI port works great for the signal. (hooked it up to my T.V. which I thought I had done before. )

Used the live boot option to install and it works great now. Thanks again!!!

[InNursery]

Hi Matt

I need some help (I'm really noobs)
I made a standalone install with Openelec and everything working fine.
I try to boot on a USB drive with no success.
I push ESC to get the boot menu and 2 for booting from the USB key.
It say booting but nothing happened.
I made my usb drive with unetbootin and I use Ubuntu 15.04 live.
I don't want to install it only to use a live version.

Have I done something wrong ?

Thanks in advance for your help.

[Matt Devo]

Don't use unetbootin, write the ISO directly or use UUI

[onizuka]

Thinking of setting up a Dual Boot (ChromeOS + OPENELEC) for my parents. ChromeOS will be the default. Took a look around at what people seem to be partitioning the M.2 SSD. Seems many people are splitting 8GB/8GB. Was thinking that favoring ChromeOS (say 12GB ChromeOS, 4GB OPENELEC) would be a safe option as who knows what Google may be planning for the future.

Anyone running OPENELEC at 4GB? Would think that's plenty of room for fanart/thumbnails....thoughts?

[afmiller]

Hey guys, I know this might be a stupid question, but how about do I go updating my chromebox which is on kodi 14.x to 15.x. I followed this guide on the initial install, but where do I start since I have Kodi installed in standalone, I don't have chrome os anymore.


Thanks

[Matt Devo]

RTFW

[afmiller]

Been poking around, I found the references about kodi with openelec, but it directs me to openelec a site on installing and upgrading. I thought openelec auto updates? I'm on 5.0.8. Any help in guiding me to the correct procedures would be nice . I can take it from there

Thanks

[Matt Devo]

I don't understand the issue - you have a standalone OpenELEC install, so follow the instructions to update OpenELEC as per the wiki. You can't/don't update Kodi separate from OpenELEC

[afmiller]

I think I get it, I'm on the stable build, but there doesn't seem to be a stable build for openelec with kodi 15.0 so I need to get on board with the beta builds. Being on 5.0.8 I'm really far behind considering the current beta 5.95.3. Is that beta build pretty stable? Thanks for straightening things out in my head Matt.