(2017-04-05, 17:47)sixburgh Wrote: Can someone please help me?

I want to reset my asus chromebox cn60 back to chromeos.

I am getting this message when the machine boots

gbb.flags is nonzero: 0x00000039
read-only firmware id: Google_Panther.4920.24.21
active firmware id: Google_Panther.4920.24.21

chrome os is missing or damaged.
Please insert a recovery USB stick or SD card.

I created a recovery disk through the Chromebook Recovery Utility, using a 8GB USB stick
Rebooted with the stick in it, it still keeps showing the above message.

How do I fix this?
All I have is a USB stick.
If you say that I have to reset any flags, how do I do that?
I can't even boot another OS, can I?

Worried if I have bricked my chromebox

(2017-04-05, 17:52)Matt Devo Wrote:

(2017-04-05, 17:47)sixburgh Wrote: Can someone please help me?

I want to reset my asus chromebox cn60 back to chromeos.

I am getting this message when the machine boots

gbb.flags is nonzero: 0x00000039
read-only firmware id: Google_Panther.4920.24.21
active firmware id: Google_Panther.4920.24.21

chrome os is missing or damaged.
Please insert a recovery USB stick or SD card.

I created a recovery disk through the Chromebook Recovery Utility, using a 8GB USB stick
Rebooted with the stick in it, it still keeps showing the above message.

How do I fix this?
All I have is a USB stick.
If you say that I have to reset any flags, how do I do that?
I can't even boot another OS, can I?

Worried if I have bricked my chromebox

All you need to do is reload ChromeOS via the Recovery Utility, then use my script to reset the flags back to stock/factory defaults.

Right now the Chromebox is booted to Recovery Mode - that's normal/expected with the stock firmware and not having ChromeOS installed. You said you've created the Recovery media using the utility - you need to insert the USB after it boots to Recovery Mode. If it doesn't recognize it, then try another port, or another USB/SD card. That's the only thing you can or need to do right now.

You box isn't bricked, it just doesn't have a bootable OS installed.

(2017-04-05, 17:55)sixburgh Wrote:

(2017-04-05, 17:52)Matt Devo Wrote:

(2017-04-05, 17:47)sixburgh Wrote: Can someone please help me?

I want to reset my asus chromebox cn60 back to chromeos.

I am getting this message when the machine boots

gbb.flags is nonzero: 0x00000039
read-only firmware id: Google_Panther.4920.24.21
active firmware id: Google_Panther.4920.24.21

chrome os is missing or damaged.
Please insert a recovery USB stick or SD card.

I created a recovery disk through the Chromebook Recovery Utility, using a 8GB USB stick
Rebooted with the stick in it, it still keeps showing the above message.

How do I fix this?
All I have is a USB stick.
If you say that I have to reset any flags, how do I do that?
I can't even boot another OS, can I?

Worried if I have bricked my chromebox

All you need to do is reload ChromeOS via the Recovery Utility, then use my script to reset the flags back to stock/factory defaults.

Right now the Chromebox is booted to Recovery Mode - that's normal/expected with the stock firmware and not having ChromeOS installed. You said you've created the Recovery media using the utility - you need to insert the USB after it boots to Recovery Mode. If it doesn't recognize it, then try another port, or another USB/SD card. That's the only thing you can or need to do right now.

You box isn't bricked, it just doesn't have a bootable OS installed.

Thanks!
That was a quick reply!
Yes: I think I need to try different USB sticks. 64GB usb3, and a 8GB usb2 stick hasnt worked.
I will go get a 4GB USB stick and see if that helps.

(2017-04-05, 22:49)sixburgh Wrote: Yay! Your guidance helped me and I realized what was happening.
The 64GB USB stick used to create the recovery disk always ended up showing so many partitions when I looked at it through disk management on my windows computer.
I used command prompt in administrator mode, ran diskpart and removed all existing partitions on the USB stick.
DID NOT create any new partitions and ran the chrome recovery utility, which probably ended up doing the CORRECT thing.
Because after that point on, the Chromebox was able to detect it.
It put the chrome OS back and everything okay now.

The reason I ended up in that bad situation was.
I had a dedicated single boot openelec kodi which I wanted to upgrade.
and i just did not know how to switch to libreelec.
So I thought why not remove everything, even put chrome OS back, switch to dual boot.
I ended up removing the OS, I also was able to remove the SEABIOS, but I just could not put chrome os back.

Finally I got the USB stick to work!
I then ran the libreelec with dual boot to work and now I have kodi 17.1 !!
Yay!

Thank you!

(2017-04-06, 00:48)fisherman55 Wrote: I'm trying to update my Chromebox from current openelec to libreelec 17.1. i can't seem to find out, or figure out the proper steps to do this. I have tried the update through usb IMG file, but just get black screen after it attempts to update. Any guidance for a proper way to intall?

(2017-04-06, 18:02)Matt Devo Wrote:

(2017-04-06, 00:48)fisherman55 Wrote: I'm trying to update my Chromebox from current openelec to libreelec 17.1. i can't seem to find out, or figure out the proper steps to do this. I have tried the update through usb IMG file, but just get black screen after it attempts to update. Any guidance for a proper way to intall?

LibreELEC has a wiki page on doing exactly that: https://wiki.libreelec.tv/index.php?title=HOW_TO:Update_LibreELEC#Migration_from_OpenELEC_to_LibreELEC

(2017-04-06, 22:17)fisherman55 Wrote: I was able to update from Openelec to LibreElec 7.0.3, I ran the backup from Openelec, everything works fine. When I try and do a manual update to LibreElec 8.0.1, it shows that its updating, but when finally done, screen remains black and unable to do anything?

(2017-04-06, 22:54)Matt Devo Wrote:

(2017-04-06, 22:17)fisherman55 Wrote: I was able to update from Openelec to LibreElec 7.0.3, I ran the backup from Openelec, everything works fine. When I try and do a manual update to LibreElec 8.0.1, it shows that its updating, but when finally done, screen remains black and unable to do anything?

Kodi upgrade bug; solution is to delete addons27.db and reboot. Easiest way to do so is via Samba (like you did for the manual update), just navigate to the UserData\Database folder on the Chromebox and delete the file (but *only* that file) then reboot

(2017-04-09, 19:02)cyrusalmighty Wrote: I am having a problem where my Asus Chromebox gets stuck on Kodi v 17.0-Krypton screen. I had this happen twice now and I'm thinking it is due to running out of space on the dual boot setup. I have Openelec 8.0.1 on default partition and Chrome OS on other (Where I hit Control-D to go to Chrome). I had this problem only 1 time where I had to rerun the EZ Script and reinstall Kodi before Kodi updated to 17 and I thought it was because I had unofficial addons (tvaddons installer) which I never installed again. Does anyone else have this problem and has this bee discussed anywhere? I can't find this by searching here.

Edit* I mean Libreelec NOT Openelec.

(2017-04-11, 17:10)HarryMohan Wrote: HI Matt, I have been running your E-Z Script now for over a year. no problems, except I wanted Kodi fresh start so I can install different kodi build. I tried to do a fresh start from "Fusion" it dint work, so I tried to manual update LE hoping it will do fresh install.. but now after LE logo splash and unpacking all I see is cursor and black screen...I am still connected samba Please help.