[Matt Devo]

Ok, I'll be back later. Thank you.

fixed, scripted updated

Hey Matt, thanks for the suggestions. Removing the parens and & didn't really change anything. Updating to the latest Legacy Boot payload didn't either. A different cable had already been tried. I did make progress, however. I enabled "HDMI UHD Color" on the Samsung 4k TV and the Chromebox will now boot up upon reboot. Here's the 3 scenarios I've tried on the 4k Samsung:

1) UHD Color Disabled -- Will not boot upon power on/reboot
2) UHD Color Enabled & autostart.sh set to 1080p -- boots up, blank screen until my Kodi skin shows up (no OS Verif, no BIOS, no OE logo, no Kodi logo), but works fine. This is what I'm using for now.
3) UHD Color Enabled & autostart.sh removed -- boots up, but blank screen. I ssh in and run xrandr and see that current res is 4096x2160 @ 24Hz.
4) Ctrl-D at boot to ChromeOS is a blank screen all the time (but works on my older 1080p monitor's HDMI)

So I'm halfway there, was just hoping to find a way to be able to see the boot screens and ChromeOS. I'm wondering if there's a way to prevent the Chromebox from attempting to connect at 4k from the get go (I'm assuming the autostart.sh only kicks in when OE starts to boot.)

Excellent wiki, btw. I hadn't read it in a while and it is one of the most solid out there.

Any other guidance would be appreciated. Not sure where to go from here. Thanks.

there's no reason the ChromeBox shouldn't work properly at 2160p24/30 - in fact I've set up several that way for friends/customers. Unfortunately I don't have a whole lot of experience with 4K TVs, and none with the Samsungs, but it sure sounds like a glitch on their end. Have you tried googling for others having similar issues with that particular model or series set? The only thing I can think of to try and work around the issue from this end would be to blacklist the 4K modes in the video BIOS, forcing it to output 1080p60 max, but I'm not sure I can do that, nor do I have any way of testing it.

thanks for the kind words on the wiki. It's far from where I'd like, but we're dealing with a lot of highly technical firmware-related issues, and distilling that down into something functional for users with a wide range of technical knowledge is a tough job indeed. I'd love to have more input from the community, but that's been hard to come by.

My first time posting here and was wondering if anyone could help. I have an Asus Chromebox and earlier in the year was experimenting with loading Ubuntu and Windows on it which I was successful in doing. Now I would like to turn ON the OS verification so that the device boots in Chrome OS without pausing. Currently when I press the space bar it does nothing but beep and eventually shows the bios version to the top left, then shows the boot screen, then goes blank. I think I have the original firmware backed up, I see the files on my share but not sure how to load it. I don't mind manually nuking the device back to its original state. Does any one have alternate steps to Turn OS verification back on or steps for restoring the original firmware? Thanks in advance.

when you use the 'Set Boot Options' feature of the script, it sets a firmware flag to lock developer mode on, to prevent accidentally disabling it via the space bar. If you're looking to have it boot ChromeOS immediately, you can either set the boot delay to 1s, or set the boot options back to default (which removes the dev mode lock) and then re-enable verified boot mode. Either way, run the script and set the boot options as desired.