(2014-12-29, 00:23)Matt Devo Wrote: [ -> ] (2014-12-25, 00:15)clvc Wrote: [ -> ]Yes, dual boot Chrome / Ubuntu. I followed the instructions / script for boot setup, without error messages.
(2014-12-28, 21:45)Cubbies2166 Wrote: [ -> ]I've tried to set up my Asus Chromebox using the script to dual boot ChromeOS and Ubuntu. I've used the scripts and everything seems to have gone through fine, but when I try and boot Ubuntu all I get is a black screen. I've tried two different TVs thinking maybe it was a display issue, but both had the same black screen.
I set it to install 14.10 and Ubuntu desktop. I've also tried running the script the second time twice and get the same problem.
Any advice?
fixed, re-run the dual boot setup (2nd phase) and you should be good to go
Everything worked great that time! Thank you for your help and your EZ setup, it made everything really easy!
I am hoping someone can help me out. I think I may have (somehow) soft bricked my Asus Chromebox when I tried to do the dual boot configuration with openelec.
Here is what I did:
1. Disabled the Firmware write protect (Removed the screw)
2. Put the Chromebox in developer mode
3. ***Missed the Factory Reset***
4. Ran the EZ Setup Script (First Time)
5. Re Partitioned to 8GB for Chrome OS and 8GB
6. Rebooted and Chrome OS repaired itself
7. Re-ran the EZ Setup script for a dual boot w/ openelec
8. Set boot options for short boot w/ openelec as default
9. Rebooted and was stuck on the boot screen ... (this is where I realized my error in missing the factory reset)
10. Re-ran the EZ Setup script and set the default boot option (Long Boot w/ Chrome OS default)
11. Attempted the factory reset. This is where I am stuck.
Right now my Chromebox successfully completes the recovery, then after the reboot it immediately goes back to the Chrome OS is missing screen.
I am hoping that someone here can point me in the right direction for recovering the box.
Any help is apreciated!
how did you create the recovery media for the factory reset? It shouldn't matter since the recovery process completed successfully, but apparently something didn't go right
I used the recovery app on my MacBook to create the media. It seemed to pass all of the checks during the flashing process. What would the symptoms be if the boot option wasn't set correctly before the factory recovery? Could it be possible that this caused an issue?
(2014-12-29, 08:15)jbrowncgy Wrote: [ -> ]I used the recovery app on my MacBook to create the media. It seemed to pass all of the checks during the flashing process. What would the symptoms be if the boot option wasn't set correctly before the factory recovery? Could it be possible that this caused an issue?
if the boot flags/options were set to something other than the default, you'd see some text in the upper left corner of the dev boot screen, and it would likely just boot the legacy BIOS rather than ChromeOS; I can't think of how the boot flags would cause it to stay in a recovery loop.
(2014-12-29, 00:01)nickr Wrote: [ -> ]I am obviously not fritsch but try this:
Put the 5.0 tar file into /storage/.update/
reboot
hard reset.
Should be the same as a fresh install, but without having to boot from usb.
Nick,
I read the WIKI and then followed your procedure and did the OpenElec 4.0 to 5.0 update without a hitch. Many thanks.
Typing my chromebox ip //192.168.1.5 into my windows search bar and it's not detecting it any other way i can acess /storage/.update
should be \\192.168.1.5 (and not //)
BHH
(2014-12-29, 15:08)buzzqw Wrote: [ -> ]should be \\192.168.1.5 (and not //)
BHH
Still won't work. I get the message Windows cannot access \\192.168.1.5
Use winscp and scp the relevant file to the target location ... it's no rocket science.
Hello,
Can someone tell me how well Kodi runs on Linux please?
I was thinking of maybe just installing this on it itself.
Thanks.
(2014-12-29, 22:12)Jpopgt Wrote: [ -> ]Hello,
Can someone tell me how well Kodi runs on Linux please?
I was thinking of maybe just installing this on it itself.
Thanks.
Kodi runs very well on Linux. OpenElec is a Linux-based setup and many of us are very happy with Kodi under OpenElec on our Chromeboxes. It also works well under Ubuntu Linux in my experience - but you have a bit more configuration and setup to think about.
Thank's for the reply!
I would rather dual boot OpenElec and Chrome OS but the torrent client does not work well on it and have to use it alongside my windows PC installed in an old Revo RL70 which is so slow to use.
I will give Ubuntu a whirl.
Cheers.
Openelec has an rtorrent addon
I've upgraded to openelec 5 but all I see is the kodi symbol for a few sec and then again ina loop how can I come out of this loop? I had version 4.2 working before
I have a standalone OE setup, I copied the 4 files to the upgrade directory and then rebooted the Chromebox, afterwards it detected the files in the upgrade folder, but I had a black screen, so I hard powered down the chromebox and when I powered it back on it started to flicking the Kodi symbol with the mouse cursor showing on the screen in a endless loop. So now I am stuck and don't know how to reset this, any help is appreciated.