[Matt Devo]

Thought I would share my story in the hopes that it helps somebody with their update.

I tried to update my 2 Chromeboxes running Seabios and an older version of LibreELEC by creating the Ubuntu Live USB thumb drive.

Making a thumb drive of Ubuntu 18.04 LTS went fine, but the Chromebox really struggled to run that version.  Also the curl command did not work and the command to apt get curl failed with some error message.

Eventually I gave up with 18.04 after no luck with Google fixes for the curl problem.  Re-writing over `8.04 I re-created a bootable usb with an older version of Ubuntu (14.04).

The 14.04 version worked much better.  No problem with curl command failure even on first try, and the chromebox ran the older version with much more ease.

ctrl-alt T opened the terminal window.  I pasted the usual:  cd; curl -LO https://mrchromebox.tech/setup-kodi.sh && sudo bash setup-kodi.sh

Option 6 of the script downloaded the UEFI and gave a failure notice after install attempt.  I ran it a second time and it succeeded with UEFI install.  Exact same failure, followed by a succeed on the second chromebox.

Option 7 of the script failed to create install thumb drive of latest LibreELEC version, but worked fine for 9.0.2 slightly older version.

With 9.0.2 successfully installed, I just changed the manual update channel on LibreELEC and it pulled down the .tar to have LibreELEC update itself to latest version.

Got it back in sync with the Sybu Kodi app on my iPhone which I prefer over the Kodi Remote app.

So success in the end, though it was a little bumpy, and chewed up a good portion of a precious Saturday tinkering with all the hiccups.

I hope it will be easier to maintain UEFI firmware updates than Legacy.

Thank you Matt for all you do to make the ChromeBox such a handy piece of home theater equipment.

on newer versions of Ubuntu, curl isn't installed by default. `sudo apt-get install curl` fixes that.

the script was out of date w/r/t the latest LibreELEC version; I've updated it to 9.2.0.

not sure why you had a failure with the firmware update, but impossible to diagnose without the error msg it would show after a failure