[loki131]

Hi Matt,

Just to let you know I wasn't able to get my USB 3.0 flash drive to be recognized, regardless of reboots and power cycles. I did dig out a 2.0 drive that works just fine so no problems here.

I also turned on automatic updates and let it update to the latest stable version of OpenELEC and so far everything looks good. Thanks again for all of your hard work on this!

[Matt Devo]

Updated the OP with version 2.0 of the script, hopefully it simplifies things for people.

As always, feedback is appreciated.

[CruzinFX4]

Same boat, Tried Dual boot Chrome/OE and get the Booting from Hard Disk. I did make the OE as 7gb fyi. OE set to default with a 1s delay.

[Matt Devo]

Same boat, Tried Dual boot Chrome/OE and get the Booting from Hard Disk. I did make the OE as 7gb fyi. OE set to default with a 1s delay.

I'm at a loss to explain this - I've reset my box to stock/non-developer mode several times and started from scratch, and each time the dual boot / OE setup works flawlessly.

If you have time, PM me or hit me up on G+/hangouts and I can walk you thru a few things to check. I'd really like to figure this out since I can't reproduce this myself.

[mdumont1]

I ran into an issue when flashing the coreboot firmware with version 1.1 of the script. When I chose yes to the do a firmware backup to a USB 2.0 FAT32 formatted stick I had connected there was a mounting error and the coreboot firmware was flashed without a backup being taken. Is there any way I will be able to flash back to the stock firmware?

Matt, you may want to update your script to abort the flash if the backup option is selected and the backup doesn't occur. It would probably also be a good idea to do a verify of the backup before moving on to flashing.

[CruzinFX4]

Same boat, Tried Dual boot Chrome/OE and get the Booting from Hard Disk. I did make the OE as 7gb fyi. OE set to default with a 1s delay.

I'm at a loss to explain this - I've reset my box to stock/non-developer mode several times and started from scratch, and each time the dual boot / OE setup works flawlessly.

If you have time, PM me or hit me up on G+/hangouts and I can walk you thru a few things to check. I'd really like to figure this out since I can't reproduce this myself.

Would have loved to help, but opted for Standalone OE. With the updated Firmware. Can't go back now.

[uomiarz]

You can always go back.
Google offers ChromeOS restore image (in case you don' t have backup of your original)
You can also bootup from USB with ChromiumOS.

I just don't get a point of dual boot with ChromeOS
Xbuntu with XBMC autostart takes 10seconds to boot up.

If the boot menu would not hang there for 5 seconds it will be 5 seconds to boot up full operating system !!!
--

@matt
Can you offer Coreboot firmware version with 1 sec boot menu delay (Hit ESC for boot menu) ?
For users that just want to bootup to OpenELEC its wast of time IMO.
For more advance users that want to boot up from USB devices 1 sec delay is more than enough.
thx

[Matt Devo]

I ran into an issue when flashing the coreboot firmware with version 1.1 of the script. When I chose yes to the do a firmware backup to a USB 2.0 FAT32 formatted stick I had connected there was a mounting error and the coreboot firmware was flashed without a backup being taken. Is there any way I will be able to flash back to the stock firmware?

Matt, you may want to update your script to abort the flash if the backup option is selected and the backup doesn't occur. It would probably also be a good idea to do a verify of the backup before moving on to flashing.

edit: firmware backup failure check added in v2.1 of script

The SeaBIOS boot wait / press for boot menu only occurs when you have a USB/SD device connected, otherwise it boots directly to the hard drive without delay. In the case that a USB/SD device is connected, it will boot that by default if you don't press [ESC] and select otherwise within the 5s timeout.

I'd prefer not to have multiple versions of the firmware to manage. Everyone is going to have their own preference on how long of a boot delay, which device has priority, etc. It's honestly pretty easy to modify the firmware file (doesn't require re-compiling) to change those things yourself

Would have loved to help, but opted for Standalone OE. With the updated Firmware. Can't go back now.

you can extract the stock firmware from google's recovery image, then flash it via a Chromium USB stick.

You can always go back.
Google offers ChromeOS restore image (in case you don' t have backup of your original)
You can also bootup from USB with ChromiumOS.

just to be clear, with the Coreboot firmware you can no longer use the recovery button and google's recovery image to restore the ChromeBox to its factory state. You'd first have to re-flash the original firmware (as I mentioned above), as it contains the recovery process.

@matt
Can you offer Coreboot firmware version with 1 sec boot menu delay (Hit ESC for boot menu) ?
For users that just want to bootup to OpenELEC its wast of time IMO.
For more advance users that want to boot up from USB devices 1 sec delay is more than enough.
thx

see above - you only get a boot menu/boot delay with USB/SD devices connected.

[Netix]

A 2gb usb flash drive would be enough to backup the current firmware?

[Matt Devo]

A 2gb usb flash drive would be enough to backup the current firmware?

it's 8MB, so yes

[Netix]

Another quick question, how would I be able to dual boot ubuntu and steam os?

[Matt Devo]

Another quick question, how would I be able to dual boot ubuntu and steam os?

I don't think the 16GB internal HDD is bit enough for that, but in general you would follow any dual booting procedure for installing 2 different versions of linux

[Netix]

When I try to sudo bash 3Tfu5W it gives me a syntax error near unexpected token.. And when I retry it it says no such file or directory.

The file downloaded correctly 260 on 260 and 23779 on 23779

[Matt Devo]

sounds like a bad download, I just verified it here after reading your post

[Netix]

sounds like a bad download, I just verified it here after reading your post

So I was able to get to the script and when I try to backup the firmware on a 2gb usb key, I chose the available drive /dev/sdb and it says :

Wrong fs type, bad option, bad superblock on /dev/sdb, missing codepage or helper program, or other error.

Edit : just tried with a 2gb sd card. Same error.