[NxtGenCowboy]

It seems that the USB recovery process is iffy. It didn't like 3 of my usb drives. I am attempting to go back to 100% stock from Stand Alone. When I attempt to do the recovery, I just keep kernel panic and devices sits.

[Matt Devo]

It seems that the USB recovery process is iffy. It didn't like 3 of my usb drives. I am attempting to go back to 100% stock from Stand Alone. When I attempt to do the recovery, I just keep kernel panic and devices sits.

I don't know how to be more clear on this topic: you can't use the recovery media created with Google's recovery tool without first re-flashing your stock firmware. To do that, you need boot from a Chromium USB stick and then manually re-flash your stock firmware. There's plenty of instructions out there on how to do that; I'll be adding some to the OP when I have time to do so.

[NxtGenCowboy]

It seems that the USB recovery process is iffy. It didn't like 3 of my usb drives. I am attempting to go back to 100% stock from Stand Alone. When I attempt to do the recovery, I just keep kernel panic and devices sits.

I don't know how to be more clear on this topic: you can't use the recovery media created with Google's recovery tool without first re-flashing your stock firmware. To do that, you need boot from a Chromium USB stick and then manually re-flash your stock firmware. There's plenty of instructions out there on how to do that; I'll be adding some to the OP when I have time to do so.

Yup totally overlooked that.. Sorry. Soon as I find them, I'll post them here for other users like myself.

[Matt Devo]

Yup totally overlooked that.. Sorry. Soon as I find them, I'll post them here for other users like myself.

no worries, I need to post instructions on this at some point

edit: added instructions to restore the stock firmware to the wiki:
http://wiki.xbmc.org/index.php?title=ASU...k_Firmware

[Kietunes]

Legend, Thanks Matt

[live4ever]

Was the stock firmware ever updated (through official channels) to fix the dev-mode USB booting issue that John Lewis patched?
http://johnlewis.ie/asus-chromebox-owners-rejoice/

[Matt Devo]

Was the stock firmware ever updated (through official channels) to fix the dev-mode USB booting issue that John Lewis patched?
http://johnlewis.ie/asus-chromebox-owners-rejoice/

The source code repositories were, which both John and I used to build our firmware updates. But Google currently has no mechanism in place to update the firmware along with ChromeOS, nor do there appear to be any plans to do so.

[NxtGenCowboy]

Thanks for the instructions!

Damn this box is picky on flash drives. Tried 4 different ones after I wrote the Camd64OS daily image. Doesn't see it yet. :\



So Escape never brought up the boot menu.... mashing down the number 1 got the USB to boot.

[Matt Devo]

Thanks for the instructions!

Damn this box is picky on flash drives. Tried 4 different ones after I wrote the Camd64OS daily image. Doesn't see it yet. :\

So Escape never brought up the boot menu.... mashing down the number 1 got the USB to boot.

hitting 1 on the menu is the same as letting it boot without pressing anything - which, if it detects a bootable USB device, is the USB device.

I'm baffled by people having issues with USB devices not being detected though. Every USB stick I've tried works:

[NxtGenCowboy]

Odd.. Wasn't the case for me. None of the USB I tired, booted automatically. I had to mash the number 1. Even hitting ESC with the USB devices inserted did nothing.

[Matt Devo]

the thing is, if there aren't multiple boot devices, then it completely skips showing the menu, and the part where it looks for keyboard input.

If there are multiple boot devices and you hit something other than ESC, then it boots the first USB device, which is the best explanation for what happened to you. It doesn't explain why your USB device isn't being detected reliably though.

[tetsuya]

the thing is, if there aren't multiple boot devices, then it completely skips showing the menu, and the part where it looks for keyboard input.

If there are multiple boot devices and you hit something other than ESC, then it boots the first USB device, which is the best explanation for what happened to you. It doesn't explain why your USB device isn't being detected reliably though.

I just used your script to install the new seabios and firmware and it will not read any of my USBsticks anymore. Do you happen to know the
correct command to flash the previous files from flashrom in linux?

Edit: I copied cros_installer, crossystem, and futility from chromiumos

Code:

cd /mount_point/ROOT-A/usr/bin
sudo cp -av cros_installer crossystem futility /usr/bin
sudo cp -avr ./old_bins/ /usr/bin
sudo cp /mount_point/usr/sbin/flashrom /usr/sbin/flashrom-google

I was able to flash coreboot-panther-20140521_143421-md.rom, but when I flashed asus-chromebox-SeaBIOS-new.bin,
ROM image contains too many regions
FAILED

Do you know what I should do to fix this.

Edit 2: It seems everything works now, but do you know what that output from the SeaBIOS flash was about.

Edit 3: It would probably be a better idea to make directories for these files in your home directory and add them to your path, if you want
to be able to flash back when you can't boot from a USB stick.

Code:

~/usr/bin
~/usr/bin/old_bins
~/usr/sbin
ln -s ~/usr/bin/old_bins /usr/bin/old_bins

[Matt Devo]

I just used your script to install the new seabios and firmware and it will not read any of my USBsticks anymore. Do you happen to know the
correct command to flash the previous files from flashrom in linux?

Edit: I copied cros_installer, crossystem, and futility from chromiumos

I was able to flash coreboot-panther-20140521_143421-md.rom, but when I flashed asus-chromebox-SeaBIOS-new.bin,
ROM image contains too many regions
FAILED

Do you know what I should do to fix this.

well first, you shouldn't try to install both the Coreboot firmware and an updated legacy BIOS/SeaBIOS that's intended for the stock firmware - that's going to break all kinds of stuff. My script / the OP make it pretty clear that the two don't mix. Plus, it's not necessary, as the Coreboot firmware includes the same legacy BIOS/SeaBIOS as the separate version installed in a dual boot setup - they're just loaded into different memory addresses (which is why you shouldn't flash John Lewis' original updated legacy BIOS/SeaBIOS onto my Coreboot firmware).

---

on a better note, I've updated the script with a fix for anyone having issues installing OpenELEC in a dual boot setup. Not sure why some people were having issues and not others, but it's fixed now.

[stewartgp]

on a better note, I've updated the script with a fix for anyone having issues installing OpenELEC in a dual boot setup. Not sure why some people were having issues and not others, but it's fixed now.

many thanks for your time helping me resolve this issue Matt, much appreciated!

[gixie]

Hi everybody,
First off, thanks for the effort Matt
Unfortunately I hit a wall. I followed the steps to install OpenELEC in a dual boot config with chromeOS but I am stuck at booting from hard disk...
I ran the script three or four times but to no avail.
I tried installing OE manually but when I did it only showed the entire ssd as target for the install and I did not want to wipe my ChromeOS installation.
Any advice for me please?
Thanks

---

Oh, and one more thing, assuming that it won't work or I won't like it, how do you go back to leaving the whole 16gb to the ChromeOS install? Thanks