Login at Kodi Home

Matt Devo · 2017-11-25, 07:20

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

tate16t · 2017-11-25, 07:26

(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

Ok thanks will try that.

Boulder · 2017-12-10, 21:01

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?

Matt Devo · 2017-12-10, 21:28

(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?

Boulder · 2017-12-10, 21:43

(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?

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.

Matt Devo · 2017-12-11, 06:14

(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.

are you able to boot to recovery mode? Press/hold the recovery button when powering on. If that works, then perform a recovery using freshly-generated media, and see if that resets things back to a sane state.

Boulder · 2017-12-11, 06:16

I think I already tried that, but it gave me the same error. I'll need to retest when I get back home from work.

Boulder · 2017-12-11, 17:52

Nope, not working. It gives the same error even when the reset button is held down when powering the device on.

Matt Devo · 2017-12-12, 00:10

(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.

bbsc · 2017-12-12, 13:22

(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.

I'd try to disconnect all new hardware: external hdd, extra memory module, probably - WLAN card and new SSD.

Ben Mooney · (This post was last modified: 2017-12-14, 13:22 by Ben Mooney.)

EDIT: Matt has contacted me separately to help!

Hi all,

I followed the EZ script to install custom (standalone firmware on my Asus CN62 i7 Chromebox. My intention was to boot windows from usb after the custom bios had installed.

My problem is now that the Chromebox won't boot at all!

I've installed the custom bios and all seemed ok...returned to the main menu of the EZ script and rebooted, now nothing!

The light comes on on the Chromebox but no video output, no beeps, no fans!

Is it an expensive brick now?

Boulder · 2017-12-15, 22:24

(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.

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 Smile

I don't know why they have chosen such a vulnerable thing as the ASUS doesn't seem to have one.

Matt Devo · 2017-12-16, 00:27

(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.

thanks for following up - and yeah, not sure why HP thought there was any value added by doing that. I think mostly to discourage use of 3rd party adapters, but really creating more problems than it's solving

digitalgimpus · 2017-12-20, 06:26

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!

Matt Devo · 2017-12-20, 06:50

(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!

unfortunately "memory issues" isn't diagnostically actionable, so hard to recommend what to use without knowing what you already tried and what exactly the issue was.

That said, use GalliumOS.