[phdlincoln]

Hi Matt,

Thanks for quick response. I followed your steps. I am able to get out of developer mode. I still got frequent shutdown issues/not booting at all.It rarely boots to Chrome OS. I tried to do factory reset. It never enters recovery mode. If I tried to press recovery port with Pin.. it goes all the way in. Did I break the recovery port?

Any other way to get the message “Chrome OS is missing or damaged” other than recovery port?

Is there is anyway to recover it?

Tx
PHD
ASUS Chromebox M075U with keyboard and mouse

[Matt Devo]

Hi Matt,

Thanks for quick response. I followed your steps. I am able to get out of developer mode. I still got frequent shutdown issues/not booting at all.It rarely boots to Chrome OS. I tried to do factory reset. It never enters recovery mode. If I tried to press recovery port with Pin.. it goes all the way in. Did I break the recovery port?

Any other way to get the message “Chrome OS is missing or damaged” other than recovery port?

Is there is anyway to recover it?

Tx
PHD
ASUS Chromebox M075U with keyboard and mouse

That really sounds like a hardware issue (or maybe firmware, but not likely). The simplest solution is probably to have the box repaired/replaced under warranty. If you're out of warranty and in the US, I can take a look at the box for you, but can't promise anything

[Matt Devo]

I am dual booting (though I have never booted into ChromeOS after day 1). I was referring to the beep beep before the 30 second delay to boot.

Are you able to boot ChromeOS via CTRL-D on the device mode boot screen?

[phdlincoln]

Hi Matt,

Thanks for lightning response. I appreciate that. Its still under warranty. As I opened the box, is ASUS normally accept for warranty?

There is no other way to reset the device using keyboard?


Thanks alot
PHD

[Matt Devo]

Hi Matt,

Thanks for lightning response. I appreciate that. Its still under warranty. As I opened the box, is ASUS normally accept for warranty?

There is no other way to reset the device using keyboard?


Thanks alot
PHD

Just put the write protect screw back in if you removed it and you'll be fine. The only real way to forcibly boot recovery mode is via the recovery button. You can always open your box up and see if/why the button isn't engaging.

[TychoCaine]

Hi Matt,

I am troubleshooting an issue with my (previously very reliable) Chromebox and just wondering if you can suggest the appropriate / correct way to effective do a clean reinstall of OpenElec? My plan is to just put the box back into developer mode and then just follow the install process as per the instructions at the beginning of this post as if it was a new install but I want to make sure that's not going to catastrophically break anything?

Appreciate any advice or pointers you could offer.

TC

[Matt Devo]

Hi Matt,

I am troubleshooting an issue with my (previously very reliable) Chromebox and just wondering if you can suggest the appropriate / correct way to effective do a clean reinstall of OpenElec? My plan is to just put the box back into developer mode and then just follow the install process as per the instructions at the beginning of this post as if it was a new install but I want to make sure that's not going to catastrophically break anything?

Appreciate any advice or pointers you could offer.

TC

OpenELEC is designed such that the OS itself exists as a read-only image file, therefore it's nearly impossible for the OS itself to become corrupted to the point of necessitating a reinstall. Instead, you can simply wipe the user data using the hard reset function under OpenELEC settings, which will produce the same result as a reinstall.

If you're not able to utilize the built-in reset functionality, then for a dual boot setup you would just re-run the script from ChromeOS; for a standalone setup, just reinstall from USB (creating fresh install media using the disk image version of OpenELEC and following the instructions on their wiki). There's rarely a need to go as far as restoring/resetting ChromeOS.

[ogpimpster]

I'm having a heck of a time installing Kodi on my new Asus Chromebox. I used the wiki and removed the write protect screw, entered developer mode, and ran the script. I chose the OpenELEC standalone and used a flash drive to back up my firmware and another to use as a bootable install media. First problem is I never got the boot menu, only booting from hard drive. Checked the faq and decided to try a different flash drive. But I don't think I can run the script again, can I? So I try downloading OpenELEC installer. Try multiple flash drives and while I can get it to boot to USB, I can't get the install to work. So I tried downloading the .img and using Win32 Disk Imager. No go either. I can get to the OpenELEC boot screen and select install or run live, but I always get an error. Usually a mounting issue. I don't understand why I'm having such a hard time. I can view files on all my flash drives in Windows 10, but I can't successfully use them for an install. Sometimes the Chromebox just won't recognize them as bootable media. No matter if I use the OpenELEC installer or write the .img, I can't seem to get it to work. I can always view the files written to the flash drive(s) under Windows. And I've tried renaming the volume to OPENELEC, but that doesn't seem to help either. Can anyone point me in the right direction?

[Matt Devo]

I'm having a heck of a time installing Kodi on my new Asus Chromebox. I used the wiki and removed the write protect screw, entered developer mode, and ran the script. I chose the OpenELEC standalone and used a flash drive to back up my firmware and another to use as a bootable install media. First problem is I never got the boot menu, only booting from hard drive. Checked the faq and decided to try a different flash drive. But I don't think I can run the script again, can I? So I try downloading OpenELEC installer. Try multiple flash drives and while I can get it to boot to USB, I can't get the install to work. So I tried downloading the .img and using Win32 Disk Imager. No go either. I can get to the OpenELEC boot screen and select install or run live, but I always get an error. Usually a mounting issue. I don't understand why I'm having such a hard time. I can view files on all my flash drives in Windows 10, but I can't successfully use them for an install. Sometimes the Chromebox just won't recognize them as bootable media. No matter if I use the OpenELEC installer or write the .img, I can't seem to get it to work. I can always view the files written to the flash drive(s) under Windows. And I've tried renaming the volume to OPENELEC, but that doesn't seem to help either. Can anyone point me in the right direction?

writing the image version of the OE installer is the correct way to go (I recommend the 5.95.5 beta). If you get an error booting that, post the error. Using the installer contained within the update version is deprecated (and should be removed). Given that you're having issues with multiple USBs, it is possible that your keyboard is causing some issues with USB init - I'd try another, with properly created OE install media.

FWIW, being able to view the USB stick contents from Windows has no bearing on its ability to function as bootable media.

[movie78]

When the Chromebox is completely Shutdown,does wake-up over LAN or MCE/Flirc remote work?

[ogpimpster]

I'm having a heck of a time installing Kodi on my new Asus Chromebox. I used the wiki and removed the write protect screw, entered developer mode, and ran the script. I chose the OpenELEC standalone and used a flash drive to back up my firmware and another to use as a bootable install media. First problem is I never got the boot menu, only booting from hard drive. Checked the faq and decided to try a different flash drive. But I don't think I can run the script again, can I? So I try downloading OpenELEC installer. Try multiple flash drives and while I can get it to boot to USB, I can't get the install to work. So I tried downloading the .img and using Win32 Disk Imager. No go either. I can get to the OpenELEC boot screen and select install or run live, but I always get an error. Usually a mounting issue. I don't understand why I'm having such a hard time. I can view files on all my flash drives in Windows 10, but I can't successfully use them for an install. Sometimes the Chromebox just won't recognize them as bootable media. No matter if I use the OpenELEC installer or write the .img, I can't seem to get it to work. I can always view the files written to the flash drive(s) under Windows. And I've tried renaming the volume to OPENELEC, but that doesn't seem to help either. Can anyone point me in the right direction?

writing the image version of the OE installer is the correct way to go (I recommend the 5.95.5 beta). If you get an error booting that, post the error. Using the installer contained within the update version is deprecated (and should be removed). Given that you're having issues with multiple USBs, it is possible that your keyboard is causing some issues with USB init - I'd try another, with properly created OE install media.

FWIW, being able to view the USB stick contents from Windows has no bearing on its ability to function as bootable media.

Well, I got it working. Using the same flash drive that I had written the .img to with Win32 Disk Imager previously, I verified it was bootable with MobaLiveCD. Put it back in the chromebox and was able to boot to it and install. Perhaps I was having so much trouble initially because I was relying on the installer within the update...if it doesn't work why hasn't it been removed yet? That probably would've saved me some grief. Thanks for the help!

[Matt Devo]

Well, I got it working. Using the same flash drive that I had written the .img to with Win32 Disk Imager previously, I verified it was bootable with MobaLiveCD. Put it back in the chromebox and was able to boot to it and install. Perhaps I was having so much trouble initially because I was relying on the installer within the update...if it doesn't work why hasn't it been removed yet? That probably would've saved me some grief. Thanks for the help!

it does work, just a lot less reliably. I'll have to talk to the OE dev team about removing it, but I think the way they have the files labeled on the download page makes it pretty clear to use the image file for installation and the update file for updating

[ogpimpster]

Well, I got it working. Using the same flash drive that I had written the .img to with Win32 Disk Imager previously, I verified it was bootable with MobaLiveCD. Put it back in the chromebox and was able to boot to it and install. Perhaps I was having so much trouble initially because I was relying on the installer within the update...if it doesn't work why hasn't it been removed yet? That probably would've saved me some grief. Thanks for the help!

it does work, just a lot less reliably. I'll have to talk to the OE dev team about removing it, but I think the way they have the files labeled on the download page makes it pretty clear to use the image file for installation and the update file for updating

I guess the differences listed on the download page weren't obvious to me and when the update files included a usb installer, I assumed it would be bootable. After checking their wiki and reading the installation instructions, I do see that they recommend using the .img and Win32 Disk Imager.... Guess I should pay a bit more attention next time to save myself some time!

[Mikey08]

I got my Asus when they were first released and followed the instructions to dual boot to Chrubuntu and had a working system for what, a year or two now? A few nights ago, I watched a movie and XBMC crashed at the end. I tried to open it again, and the menu bar disappeared, then tried to restart and the top bar disappeared and I was left with my background image, unable to do anything. After holding the power button to power down and then start up again, I haven't been able to get back into Chrubuntu. Upon restarting, the Chrubuntu load screen comes up, then a black screen and the light on the box blinks blue. I've done the paper clip to get to developer screen & get nowhere after that (keyboard will change language on this screen, so it does work). Furthermore when I first set up the system, I got a 64gb ssd drive and never altered the one that came with the box, I put it back in & still can't get the machine to boot. Any ideas?

[Matt Devo]

I got my Asus when they were first released and followed the instructions to dual boot to Chrubuntu and had a working system for what, a year or two now? A few nights ago, I watched a movie and XBMC crashed at the end. I tried to open it again, and the menu bar disappeared, then tried to restart and the top bar disappeared and I was left with my background image, unable to do anything. After holding the power button to power down and then start up again, I haven't been able to get back into Chrubuntu. Upon restarting, the Chrubuntu load screen comes up, then a black screen and the light on the box blinks blue. I've done the paper clip to get to developer screen & get nowhere after that (keyboard will change language on this screen, so it does work). Furthermore when I first set up the system, I got a 64gb ssd drive and never altered the one that came with the box, I put it back in & still can't get the machine to boot. Any ideas?

you can either troubleshoot your current install - I'd ask over on ubuntuforums since your problem is with Ubuntu - or you can boot ChromeOS via CTRL-D and reinstall using the script.