(2017-01-30, 19:46)Haws Wrote:

(2017-01-30, 18:21)Matt Devo Wrote:

(2017-01-30, 17:23)Haws Wrote: Long time user, no real problems. Thank you Matt.

Somehow messed up last update i was doing on one of my boxes. Normally just running a standalone setup. Firmware update went well.

Boots to shell command device mapping table now.

Not wanting to mess up more so figured i would ask the experts before i pushed more buttons.

Thank you in advance

When you install the standalone firmware via the EZ setup script, it now installs the UEFI firmware, rather than the older Legacy Boot firmware previously used. There's not a good way (read: automated) to migrate an installed OS between the two, because they use different partition layouts (MBR vs GPT) among other reasons. The easiest thing for you to do will be to boot a Linux USB, run my Firmware Utility Script, and install the Legacy Boot firmware instead. Run the script, choose 'u' to unlock all functions, choose option 3 (Install Full ROM firmware), then choose 'L' for legacy boot when prompted. When done, simply exit/reboot.

Flawless and Easy Fix.
Great support and thank you for all your hard work.

(2017-02-19, 19:59)mxmerc Wrote: I apologize for my ignorance (and for replying to an old post on the thread), but I am having the same exact issue this user had. I attempted to use the EZ setup script and it installed the UEFI firmware over the legacy boot firmware. The chromebox now boots into a shell prompt. I have created a Linux usb, but am unable to get it to boot. How do I get from the shell prompt to the Linux usb so that I can run the firmware utility script?

(2017-02-19, 20:26)Matt Devo Wrote:

(2017-02-19, 19:59)mxmerc Wrote: I apologize for my ignorance (and for replying to an old post on the thread), but I am having the same exact issue this user had. I attempted to use the EZ setup script and it installed the UEFI firmware over the legacy boot firmware. The chromebox now boots into a shell prompt. I have created a Linux usb, but am unable to get it to boot. How do I get from the shell prompt to the Linux usb so that I can run the firmware utility script?

type 'exit' to get to the UEFI firmware settings, then select Boot Manager then your USB. If it doesn't boot, it's because the ISO/image wasn't written properly to the USB. Assuming your writing it from Windows, use Win32DiskImager or Rufus, and make sure the partition layout is set to 'GPT for UEFI' after selecting the ISO

(2017-02-19, 23:25)mxmerc Wrote: Thank you sir. Worked like a charm. I had the partition layout set incorrectly to MBR.

(2017-02-19, 02:02)Matt Devo Wrote:

(2017-02-19, 00:33)SandmanUT Wrote: Well..waded in and got as far as the UEFI flash.

From Ubuntu 16 on a stick, all went well, made it to the end and chose "P" to power down while I went to make a Steam install stick. When I came back and restarted, it powers up but there is now no video output. Tried it with hdmi, with the DP, two different monitors, with a boot disk in, without, steam, ubuntu...just blackness. No prompt, no response to any keys.

Thought I'd stop right there before doing any additional damage and check on thoughts here. A reminder that the box is the Asus M004U, it's got 4 gigs of ram in, a wired keyboard and mouse and wired net connection. I ran the firmware utility script as outlined on your site and it looked like it did everything it was supposed to do..while I was using the terminal from Ubuntu.

** Additional info: I used the Full rom (3) option and created a backup on a separate usb stick. It was running OpenElec and Kodi under a dual boot with ChromeOS using your script until today.

some users have reported video output/handshaking issues after flashing/before an OS is installed. I'd give it a try with another HDMI cable / on a different display if you can. I can count on one hand (with digits to spare) the number of boxes actually bricked when flashing firmware over the past ~3 years

(2017-02-22, 02:12)SandmanUT Wrote: Well, you were right about it not being bricked. When I took it to a monitor (instead of the 2 tvs in that room) I was able to get into and install the OS, even using the same hdmi cable that wasn't in a working scenario. I finally got SteamOS all configured and Kodi loaded into it, etc, but when I moved it back to the original room, no video on my older plasma (same HDMI cable from working) and still no output on the dp (via dp-hdmi) that were both working with openelec/chromeos/your script.

What's missing to make these handshakes work again?

(2017-02-19, 04:17)nickr Wrote: There is an androidx86 project, and also a commercial version for PC hardware I think.

I would only try it if you are really desperate to run android apps though.

(2017-02-22, 02:30)Matt Devo Wrote:

(2017-02-22, 02:12)SandmanUT Wrote: Well, you were right about it not being bricked. When I took it to a monitor (instead of the 2 tvs in that room) I was able to get into and install the OS, even using the same hdmi cable that wasn't in a working scenario. I finally got SteamOS all configured and Kodi loaded into it, etc, but when I moved it back to the original room, no video on my older plasma (same HDMI cable from working) and still no output on the dp (via dp-hdmi) that were both working with openelec/chromeos/your script.

What's missing to make these handshakes work again?

it's really hard to say, but I'd try another cable or two if you have them handy. I'm also pushing a firmware update later today which may help, so I'd recommend updating to that and then retrying

(2017-02-22, 16:16)bolmsted Wrote:

(2017-02-19, 04:17)nickr Wrote: There is an androidx86 project, and also a commercial version for PC hardware I think.

I would only try it if you are really desperate to run android apps though.

Is it possible for me to boot this or another version of Android off of a USB (flash) drive instead of dual booting from the internal flash drive of the Chromebox for the rare instances that I would run Android for example?

Quote:BTW, does the Chromebox support 4K resolution over HDMI?