(2020-05-14, 07:28)Matt Devo Wrote:

(2020-05-14, 07:24)petecat1 Wrote: I have one that I haven't tried your firmware on for over a year.  Would anything have changed in that time, or is there some way to update the chromebox and try?  Or is it unlikely to make a difference?

if you have one that's in Developer Mode, or you don't mind wiping to put in Developer Mode, then please do flash the RW_LEGACY firmware and see if SeaBIOS will boot (optionally try to boot a USB). Whatever is/was broken was on Google's end so quite possible it got fixed since you last tried  

(2020-05-25, 14:23)petecat1 Wrote: I boot the CN65 in Developer Mode and get the rabbit, hit escape and get your Boot screen. 

Quote:I select to boot from an SD card with a newly installed chrome recovery.  I get the chrome logo, and then it gets stuck on Your system is repairing itself. Please wait.  Eventually it returns to the boot screen.

Quote:1. Do you know how to get past that screen?

Quote:2. If I forget about trying to restore chrome, can I flash the RW Legacy firmware from a USB at the boot screen?  Or can it only be installed via the shell?
Thanks 

(2015-07-01, 16:11)Matt Devo Wrote:

(2015-07-01, 12:35)pvagner Wrote: Quick and maybe stupid question. I have skimmed the thread, read some 10 pages but I must have missed it.
Is disabling Firmware Write Protect absolutelly necessary or do I correctly understand with it enabled I might still be able to have dual boot setup with 30 s boot delay? I don't feel capable of dissassembling my HP ChromeBox and I just would like to test this out before trying to find someone who can do that part for me.

You do not need to remove the write protect screw for a dual boot setup if you're not going to change the boot options, though I recommend doing it at the beginning so you don't have to open up the box down the road. And even if you don't want to change the boot delay, you should use the script option to set it anyway, since it will prevent accidentally leaving developer mode (via spacebar) on the boot screen.

(2020-09-09, 01:53)imagamer2k Wrote: If the write protect screw was removed upon initial setup, is there an easy option for recovering from accidentally hitting spacebar during bootup, and leaving developer mode? Asking for a friend  :doh!:

(2020-09-09, 09:22)Matt Devo Wrote:

(2020-09-09, 01:53)imagamer2k Wrote: If the write protect screw was removed upon initial setup, is there an easy option for recovering from accidentally hitting spacebar during bootup, and leaving developer mode? Asking for a friend  :doh!:

assuming a dual boot setup -- simply re-enter Developer Mode, and re-set the dev_boot_legacy flag. Your dual-booted Kodi/Linux OS will be fine as long as you didn't perform a ChromeOS recovery

(2020-09-09, 18:44)imagamer2k Wrote: Success...Thanks Matt!!

Another question. I am currently running dual boot ChromeOS and OpenELEC v6.0.3/Kodi v15.2...If I wish to update to the latest LE/Kodi, I understand I need to do this manually, but can I still use your E-Z Setup Script to do it? Should I create install media using option 7 (is this usb or sd media?), and then follow that up by running option 2, to retain my dual boot?

Thanks!

(2020-10-11, 21:05)rodddogg Wrote: It's been a while since I've upgraded my kodi box or even touched this script (~4+ years).. I'm not sure I remember how to boot back into the E-Z setup script mode or even remember the hotkeys. My issue is trying to upgrade to latest libreelec but my system partition FAT size is too small to upgrade so not sure if I should just blast this thing or use gparted; any insight would be appreciated.

(2020-10-11, 21:12)Matt Devo Wrote:

(2020-10-11, 21:05)rodddogg Wrote: It's been a while since I've upgraded my kodi box or even touched this script (~4+ years).. I'm not sure I remember how to boot back into the E-Z setup script mode or even remember the hotkeys. My issue is trying to upgrade to latest libreelec but my system partition FAT size is too small to upgrade so not sure if I should just blast this thing or use gparted; any insight would be appreciated.

there's no reason to use the EZ Setup script at this point, unless you have a dual-boot setup and want to start fresh -- in which case you'd need to do a full reset first.

on a standalone setup, either do a fresh install from USB, or boot a live USB and use gparted to resize the partitions to make the 1st partition (KERNEL) 1GB

(2020-10-11, 21:16)rodddogg Wrote: Thanks for quick reply Matt. Question is to boot from live USB, do I need to intervene with any keys or it just boots directly after power up?

(2020-10-11, 21:25)Matt Devo Wrote:

(2020-10-11, 21:16)rodddogg Wrote: Thanks for quick reply Matt. Question is to boot from live USB, do I need to intervene with any keys or it just boots directly after power up?

 assuming you did a standalone setup a few years ago, you likely need to press ESC for the boot menu when prompted, then select the USB from the list. What I would recommend though is probably to boot a Linux USB, update to the latest UEFI firmware using my script, and then reboot / do a clean install of LE. You can always back up your userdata before / restore it after using the built-in LE backup/restore function.

(2020-10-11, 21:36)rodddogg Wrote: It is a standalone LE build. I also thought it was ESC but it just skips and boots straight into LE so not sure that's it. Yeah I don't mind blasting the whole config and starting with latest Kodi build; it's why I started doing this anyway.

(2020-10-11, 22:00)Matt Devo Wrote:

(2020-10-11, 21:36)rodddogg Wrote: It is a standalone LE build. I also thought it was ESC but it just skips and boots straight into LE so not sure that's it. Yeah I don't mind blasting the whole config and starting with latest Kodi build; it's why I started doing this anyway.

 if there's no 'Press ESC for Boot Menu' prompt, either it's happening before the display comes on (in which case you need to hit it earlier), or it's not showing because your USB stick isn't being detected (in which case, try another USB stick or USB port -- it is **NOT** related to what is on the USB drive, re-writing it will not change the outcome)