(2014-05-26, 04:44)denrock Wrote: Yeah, the usb drives with all my movies and music are formatted NTFS. It's weird, in XBMC for the drives that do get recognized some of the time a message will pop up saying it was mounted but it's nowhere to be found. If I reboot sometimes it'll show up then, sometimes it will just do the same thing saying it mounted the drive but it won't show up. It seems like it's similar to problems other people were having in other comments where they mentioned certain usb drives or sticks were working and others not working.

Do you know of any walkthroughs of how to reflash the rom with the method you described? Thanks for any help.

(2014-05-26, 16:09)stewartgp Wrote: Count me as another stuck on the 'Booting from Hard Disk...' stage after completing the dual boot ChromeOS/OE setup.

If it helps I set my OE partition size as 9GB, opted for a 1s boot delay defaulting to OE and was doing a completely fresh install... will try and go through it again I guess, see if it makes any difference...

(2014-05-26, 06:04)Matt Devo Wrote: I think the issue you are having is completely unrelated to what others are seeing, but I could be wrong.

OpenELEC should actually automount NTFS drives as read-only, so if not then there's an issue somewhere. Are the drives in question USB flash drives? or external hard drives? If the latter, are they bus-powered or externally powered? USB2 or USB3?

Re-flashing the stock firmware will not let you run OpenELEC as-is, since the stock legacy BIOS/SeaBIOS is pretty hosed. You could re-flash the stock firmware, then manually update just the legacy BIOS portion (with the original fixed version from John Lewis), but even then you'd still need to re-install OpenELEC with my old custom build, as the bootloader (syslinux) included with the official OE distribution is not compatible (due to a bug in the stock firmware/SeaBIOS). And even then there's no guarantee that your drives would work, as the original SeaBIOS update didn't support USB3 drives at all.

(2014-05-25, 20:03)Matt Devo Wrote:

(2014-05-24, 16:25)Kietunes Wrote: Hi Matt,

Firstly apologies, I've tried everything I think of to sort the issue but I just haven't had any joy.

I followed the instruction in the original post, I made sure I followed the Device Prep section, downloaded & ran the script no problem.

I was then able to install the Coreboot firmware, I didn't backup a copy as I had already done so using the ChromeOS Recovery Tool.

perhaps I need to make this more clear in the OP/script. The recovery media created by the Google ChromeOS Recovery Tool will allow you to restore the ChromeBox provided you are running the stock firmware. The Recovery button operation/function is part of the stock firmware. Without it, the recovery media is useless. That's why you need to back up your stock firmware.

Now, the stock firmware is also contained within the recovery media image, but it's a bit of a pain to extract it, and it's not an exact copy since it doesn't contain your unique serial number, etc. But it's enough to get the box back running ChromeOS.

(2014-05-27, 15:49)Kietunes Wrote: Hmm sounds like I made myself a bit of a problem by not making a copy during the installation process. Could you possibly point me in the direction of an explanation of how to extract the stock firmware from the recovery media image and/or how to reflash this?

Thanks again Matt, loving my Chromebox currently, it's so much smoother/slicker than my old HTPC

(2014-05-27, 16:58)Kietunes Wrote: Thanks,

I'm happy but considering possibly running it as a Dual Boot in the future (looking at running ChromiumOS from usb for the moment, which I presume is possible?).

I guess I just wanted to have it in the even that I do want to go back to having ChromeOS on the box itself.

I'll keep my eyes peeled for any further info

(2014-05-27, 17:24)jerndl Wrote: Matt, I ran an early version of you script a couple of week ago (before the Coreboot firmware update). So I guess I am still using the original firmware. I am using a single boot to Openelec (4.0.2). Currently I am not having any specific problems. Is there any reason I should go back a re-run your script to update the firmware?

(2014-05-27, 20:12)Veronica Wrote: which version of chromium os are you using, i tried latest weekly and is not booting tried several times with a micro sdcard in a card reader, gets recognized in xubuntu but after restart or shutdown it doesnt boot from it, always boot to hard disk. What should i do. Thing is i only have a 2gb usb stick and the image is larger than that and i dont have another stick to try yet. Thanks in advance

(2014-05-27, 20:28)Searlan Wrote: Hey Matt, is there a significant difference between v1.1 and 2.0 of the script? I updated using v1.1 a few weeks ago, but in v2.0 the release notes said "updated Coreboot firmware".

Thanks