(2017-11-25, 07:20)Matt Devo Wrote: then just go to LibreELEC's site, download their USB creator utility, run it, create the USB media, boot the Chromebox with it, and install

(2017-12-10, 21:01)Boulder Wrote: I ran into an interesting problem while trying to revert my HP Chromebox back to the original state to then just install a basic LibreELEC setup on it with the script. I know that I could do it without going back to the very beginning but I wanted to test it as I'm selling my other CB soon, and I plan to sell it in its original state.

The box had the latest UEFI firmware version and Win10 installed. I proceeded by restoring the stock firmware which went fine. Then I rebooted to recover ChromeOS, but an error message appears:

"The connected power supply does not have enough power to run this device. Blahblahblah.."

Well, the box has worked fine with the original HP 19,5V/3,33A/65W power supply on Win10 and also had no issues when it ran Chrome OS while I upgraded the firmware with the script.

Is there anything that I could do but buy a new power supply?

(2017-12-10, 21:28)Matt Devo Wrote:

(2017-12-10, 21:01)Boulder Wrote: I ran into an interesting problem while trying to revert my HP Chromebox back to the original state to then just install a basic LibreELEC setup on it with the script. I know that I could do it without going back to the very beginning but I wanted to test it as I'm selling my other CB soon, and I plan to sell it in its original state.

The box had the latest UEFI firmware version and Win10 installed. I proceeded by restoring the stock firmware which went fine. Then I rebooted to recover ChromeOS, but an error message appears:

"The connected power supply does not have enough power to run this device. Blahblahblah.."

Well, the box has worked fine with the original HP 19,5V/3,33A/65W power supply on Win10 and also had no issues when it ran Chrome OS while I upgraded the firmware with the script.

Is there anything that I could do but buy a new power supply?

 that's a generic error generated by the firmware when it can't validate that a genuine HP power supply is being used (something only the HP box does).  What backup did you restore -- a backup generated by the script when you flashed the UEFI firmware originally, or one provided by the script at the time of restore? 

(2017-12-10, 21:43)Boulder Wrote: That's an interesting check, it's a surprise a simple Google search didn't bring up any results explaining the issue.

I restored the backup generated by the script when I flashed the UEFI firmware. 

(2017-12-11, 17:52)Boulder Wrote: Nope, not working. It gives the same error even when the reset button is held down when powering the device on.

(2017-12-11, 17:52)Boulder Wrote: Nope, not working. It gives the same error even when the reset button is held down when powering the device on.

(2017-12-12, 00:10)Matt Devo Wrote:

(2017-12-11, 17:52)Boulder Wrote: Nope, not working. It gives the same error even when the reset button is held down when powering the device on.

 unfortunately I don't have a good answer then.  If it is really a PSU issue, then replacing it should help, but I suspect that the firmware is just confused somehow, and I don't have a good suggestion on how to reset it. 

(2017-12-15, 22:24)Boulder Wrote: Forgot to come here to tell that I was able to resolve the situation. I did buy a new power supply and tested it to work OK. For some reason, I started looking at the plugs of the two PSUs and soon noticed that the "broken" PSU just had a bent pin in the center of the plug. I managed to straighten it and fortunately, it works   I don't know why they have chosen such a vulnerable thing as the ASUS doesn't seem to have one. 

(2017-12-20, 06:26)digitalgimpus Wrote: So looking to update the firmware for some of the new stuff like the boot screen. I tried running a few live distro's, but keep running into memory issues. IIRC it's only 2GB.

So what OS is recommended for running the firmware-util script? Anyone do this before and have a recommendation?

Thanks!