(2016-05-13, 22:18)docsuess84 Wrote: Good to know. It asked if I wanted to back it up again. So it must not have worked.

(2016-05-14, 07:33)docsuess84 Wrote: I never thought it would be this hard. Now it says "coreboot firmware download checksum fail; download corrupted, cannot flash

(2016-05-14, 08:36)Matt Devo Wrote:

(2016-05-14, 07:33)docsuess84 Wrote: I never thought it would be this hard. Now it says "coreboot firmware download checksum fail; download corrupted, cannot flash

That's not hard, that's called protecting you from bricking your device

(2016-05-14, 17:33)darebee Wrote: Oops. I wasn't paying attention with my updates today and I accidentally dropped the RPI3 version of LibreELEC in the update folder. Now the kernel won't boot and displays Booting Kernel failed:Invalid argument. What steps do I need to take to get the correct LibreELEC installed again on my Chromebox?

Thanks in advance.

(2016-05-14, 17:38)docsuess84 Wrote: No I get it, and I'm grateful that I didn't brick my device, I just didn't think I'd run into so many stumbling blocks. How do I resolve this one? Start the script all over again?

(2016-05-14, 20:12)bbsc Wrote: @matt Devo, great product, thank you very much.

Dell Chromebox, working fine with Openelec now. Single-boot, the system is on the internal SSD.
I have a 1TB 2,5' HDD connected for media.
It was connected via SATA-USB2.0 adapter and ntfs-formated.
Seabios was set to boot from USB (for personal reasons) and the system booted normally as the HDD was not bootable. There was no 5s delay.

Now I've got an USB3.0 enclouser, repartitioned the HDD and formated the only primary partition to ext4.
Boot flag is not set.
But the system always tries to boot from the HDD now and I had to set Seabios to boot always from the internal SSD.
There's 5s dalay always now, despite the HDD is not bootable.

Is there anything to do with this problem?

(2016-05-15, 02:03)Matt Devo Wrote: your old SATA->USB2 adapter wasn't registering properly

(2016-05-15, 07:04)bbsc Wrote: Thank you for the explanation. Seems you're right. I returned the old USB2.0 adapter and the delay is gone.
Pity, it was more convenient when the bios did not try to boot from USB with external storage present.

(2016-05-15, 07:23)Matt Devo Wrote: You can always remove/adjust the boot menu delay

(2016-05-15, 13:53)bbsc Wrote: It's a good idea.
Can you tell me how to configure it? I don't see show-boot-menu or boot-menu-wait variables in the script
Thank you in advance.

(2016-05-15, 18:31)docsuess84 Wrote: Ok, I've rebooted, and re-run the script and I'm still getting the same corrupted download checksum error for the firmware. Any thoughts?

(2016-05-15, 19:59)docsuess84 Wrote: Is the firmware necessary?

Quote:I wonder if it would make a difference to log in as a guest and open a terminal the other way you mentioned. Could you write the commands with the extra stuff you were talking about?

• Log in as a guest
  
• press CTRL-ALT-T to open a terminal tab
  
• type 'shell' to get a chronos shell
  
• type 'cd ~; curl -L -O http://mrchromebox.tech/setup-kodi.sh; sudo bash setup-kodi.sh'
  

Quote:Is there an alternate method to download the firmware and update it without downloading it directly? My thought was I could download it somewhere with a faster more reliable internet connection and bring it back home.