Kodi Community Forum

Hi Matt,

I picked up a Chromebox and started going through the steps to dual boot ChromeOS and Openelec. I got the Chromebox into developer mode. I then removed the write protection screw. I am having major difficulties getting the Chromebox to read the recovery USB. I've tried four different USB drives (2 4Gb's, 1 8GB, and 1 16GB) and I can't get the Chromebox to detect the recovery USB drive. Any ideas as to what I can do to solve this? Thanks.

(2014-12-05, 08:07)ajcast5201 Wrote: [ -> ]Hi Matt,

I picked up a Chromebox and started going through the steps to dual boot ChromeOS and Openelec. I got the Chromebox into developer mode. I then removed the write protection screw. I am having major difficulties getting the Chromebox to read the recovery USB. I've tried four different USB drives (2 4Gb's, 1 8GB, and 1 16GB) and I can't get the Chromebox to detect the recovery USB drive. Any ideas as to what I can do to solve this? Thanks.

On the recovery screen, what happens when you insert the recovery media? what method did you use to create the recovery media?

I'm currently running a standalone openelec build and I have a 128gb usb 3.0 stick and a 128gb ssd (currently waiting on my usb 3.0 enclosure) lying around.

I would like to install window on one of them, which one should I choose? Also, how would I be able to boot from the usb/ssd, do I have to modify my standalone instal or only select the other boot drive when the chromebox power up?

Thanks!

This is perhaps a very silly question, but I don't own a Chromebox Once it's set up to dual boot, how does the dual boot process actually work? When you power it up, do you see two "gateway" icons, one to each OS? Is it selectable via remote button press? I'm just trying to get my head around how dual booting actually occurs.

Matt, i used putty to get into the box that i wasn't sure if i updated the bios on. after type the 2 commands on page one i am getting this error:

OpenELEC (official) Version: 4.2.1
OpenELEC:~ # curl -L -O http://goo.gl/3Tfu5W
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 260 0 260 0 0 3267 0 --:--:-- --:--:-- --:--:-- 3291
0 0 0 383 0 0 914 0 --:--:-- --:--:-- --:--:-- 0
100 33537 100 33537 0 0 48603 0 --:--:-- --:--:-- --:--:-- 48603
OpenELEC:~ # sudo bash 3Tfu5W

There is no working 'sudo'.

On debian/ubuntu/all general purpose linux distributions 'sudo'
allows a permitted user to execute a command as the superuser
or another user, as specified by the security policy

With OpenELEC you have root access by default, so you dont need 'sudo'

I have used putty before but not a pro, what do i need to do here?

Thanks

(2014-12-05, 08:35)Matt Devo Wrote: [ -> ]

(2014-12-05, 08:07)ajcast5201 Wrote: [ -> ]Hi Matt,

I picked up a Chromebox and started going through the steps to dual boot ChromeOS and Openelec. I got the Chromebox into developer mode. I then removed the write protection screw. I am having major difficulties getting the Chromebox to read the recovery USB. I've tried four different USB drives (2 4Gb's, 1 8GB, and 1 16GB) and I can't get the Chromebox to detect the recovery USB drive. Any ideas as to what I can do to solve this? Thanks.

On the recovery screen, what happens when you insert the recovery media? what method did you use to create the recovery media?

Nothing happens while I'm on the recovery screen. I know the USB port is working because the USB flash drive light is on. I can also scroll through the language using my keyboard's cursor.

I've used the chrome recovery tool on my Chromebox. I've also downloaded the recovery, unzipped it, changed the extension to .IMG, and used the recommend image writer to write the file to the flash drive. Neither of these methods got a response from my Chromebox.

(2014-12-05, 13:43)canadave Wrote: [ -> ]This is perhaps a very silly question, but I don't own a Chromebox Once it's set up to dual boot, how does the dual boot process actually work? When you power it up, do you see two "gateway" icons, one to each OS? Is it selectable via remote button press? I'm just trying to get my head around how dual booting actually occurs.

From the first page of this thread.... a default 1sec or 30sec boot delay can be set before autoboot commences into ChromeOS or Openelec (user configurable)
during this time and with a Wired keyboard only....

Hey Matt/All,

Thanks for all your work on this. Can't express enough appreciation.

I've decided to get a Chromebox for my parents. They currently have an oldie by goodie ZBOX ND22 running latest Kodi OpenELEC RC. Here's my not so serious conundrum I'd like you opinion on (or anyone else that might suggest something).

The Zbox is currently using a AVS Gear HA-IR01SV. I provided this remote to my parents for the large buttons and (supposed) easier navigation. On the Wiki I noticed that this remote is currently not compatible with our beloved Chromebox (I assume it's an issue with Chromebox's USB3 ports?).

The goal was to keep the remotes consistent between setups, they're my parents after all. I assume most are thinking: "Why don't you just get them PS3 Remotes like everyone else is using!?" "Even reduces to amount of required remotes for TV + HTPC." I myself use the PS3 remote. My only knock at it is the very small buttons. Can't remember how many times I've fat fingered this remote. The directional is particularly sensitive, hitting the DOWN directional brings up Kodi's side menu inside Confluence on a frequent basis. Am I REALLY pressing the SIDE directional too??

So I guess my question is: Does the AVS Gear HA-IR01SV have any hope for Chromebox support? Is it a software thing, or really a hardware issue that's not resolvable unless AVS Gear does a revision of the remote?

If I'm SOL (I assume that to be the case). Do you have another remote you'd recommend that are "Parents Approved"?

Thanks!

If you want to reuse your remote again and do it the easy way, Five letters --> FLIRC

will learn the AVS Gear's HA-IR01SV IR commands and store them in its USB dongle.
Your current remote buttons can then be mapped to XBMC's shortcut keyboard controls using the FLIRC app to operate exactly the same as before.

Its what I use. Easy to setup. Program the USB dongle then plug into whatever XBMC box you have.

All explained on the website

https://flirc.tv/

Anyone get Airplay working on RC1? Trying to figure out if it's just my environment or a issue?

Box is wired Ethernet, phone is wireless running iOS8. I have the iOS8 compatibility mode turned on. Shows up on my phone as a Airplay device but as soon as selecting it, it deselects itself, disappears and comes back as selectable again only to repeat.

(2014-12-04, 21:10)Matt Devo Wrote: [ -> ]

(2014-12-04, 20:45)megamanwilson Wrote: [ -> ]I did not because i thought that this could not solve my problem. I did not get a signal even with the box booting from power off. The workaround with the powerd down hdmi switch is working too if i try to wake the box from sleep. If the TV is on, the HDMI switch is on and the box is in slepp the wakup results in a "No Signal" to the TV. If the Box is in Slepp and the TV and HDMI Switch on and i power down the HDMI Switch, then wake up the Box an then power on the HDMI Switch i get a signal and everything is normal. Same thing with Box completely shutted down.

you can install 14.04 + updated kernel (think Ubuntu has 3.16.5 available) and you'll be good to go. Mint 17 still requires a kernel update I believe.

(2014-12-04, 21:05)john.cord Wrote: [ -> ]I did not because i thought that this could not solve my problem. I did not get a signal even with the box booting from power off. The workaround with the powerd down hdmi switch is working too if i try to wake the box from sleep. If the TV is on, the HDMI switch is on and the box is in slepp the wakup results in a "No Signal" to the TV. If the Box is in Slepp and the TV and HDMI Switch on and i power down the HDMI Switch, then wake up the Box an then power on the HDMI Switch i get a signal and everything is normal. Same thing with Box completely shutted down.

if you're not getting a signal on a cold boot even with the TV/switch on, then my only suggestion would be to use an inline device like a Dr. HDMI (I think that's what it's called) which will store the EDID data from the TV and present it to the ChromeBox when powered on

Thanks, Matt your the best for creating such an awesome script. I install xubuntu but the web browsing experience was not great. Then I install lubuntu web browsing experience the same but xbmc was faster. Then ended up installing peppermint 5 this one gave better web browsing experience from the other two and xbmc was the same as lubuntu which was great with updated kernel 3.16.

(2014-12-05, 12:40)Netix Wrote: [ -> ]I'm currently running a standalone openelec build and I have a 128gb usb 3.0 stick and a 128gb ssd (currently waiting on my usb 3.0 enclosure) lying around.

I would like to install window on one of them, which one should I choose? Also, how would I be able to boot from the usb/ssd, do I have to modify my standalone instal or only select the other boot drive when the chromebox power up?

Thanks!

the SSD will likely be faster. When connected at boot, simply press [ESC] then select the USB/SDD from the boot menu. No changes to your existing setup are needed.

(2014-12-05, 13:43)canadave Wrote: [ -> ]This is perhaps a very silly question, but I don't own a Chromebox Once it's set up to dual boot, how does the dual boot process actually work? When you power it up, do you see two "gateway" icons, one to each OS? Is it selectable via remote button press? I'm just trying to get my head around how dual booting actually occurs.

On the ChromeBox's dev mode boot screen, you press [CTRL-D] to boot ChromeOS, or [CTRL-L] to boot OpenELEC/Ubuntu etc. There's no boot menu or easy to use GUI, that's just the way the stock firmware works.

(2014-12-05, 13:54)LilSnoop40 Wrote: [ -> ]Matt, i used putty to get into the box that i wasn't sure if i updated the bios on. after type the 2 commands on page one i am getting this error:

OpenELEC (official) Version: 4.2.1
OpenELEC:~ # curl -L -O http://goo.gl/3Tfu5W
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 260 0 260 0 0 3267 0 --:--:-- --:--:-- --:--:-- 3291
0 0 0 383 0 0 914 0 --:--:-- --:--:-- --:--:-- 0
100 33537 100 33537 0 0 48603 0 --:--:-- --:--:-- --:--:-- 48603
OpenELEC:~ # sudo bash 3Tfu5W

There is no working 'sudo'.

On debian/ubuntu/all general purpose linux distributions 'sudo'
allows a permitted user to execute a command as the superuser
or another user, as specified by the security policy

With OpenELEC you have root access by default, so you dont need 'sudo'

I have used putty before but not a pro, what do i need to do here?

Thanks

I told you what section to look at before; you can't re-run the main script under OpenELEC:

Quote:----------------------------------------
Updating the coreboot Firmware
----------------------------------------
As of version 3.0 of the script, you can simply re-download/re-run the script under any Linux distro with a full bash shell. The dual-boot related options will be disabled, but the Standalone Setup / coreboot firmware update option will be available.

If you are running a Linux distro which does not have a full bash shell, such as OpenELEC, you should use my new standalone firmware updater script from an SSH terminal. This script is only intended to update a ChromeBox already running my custom coreboot firmware, and will not work under ChromeOS/ChromiumOS.

Code:

curl -L -O http://goo.gl/HSZer4
sudo bash HSZer4

Note: the 'sudo' prefix is not required under OpenELEC, since you are always logged in as the root user.

(2014-12-05, 13:59)ajcast5201 Wrote: [ -> ]Nothing happens while I'm on the recovery screen. I know the USB port is working because the USB flash drive light is on. I can also scroll through the language using my keyboard's cursor.

I've used the chrome recovery tool on my Chromebox. I've also downloaded the recovery, unzipped it, changed the extension to .IMG, and used the recommend image writer to write the file to the flash drive. Neither of these methods got a response from my Chromebox.

what kind/size media are you using?

Matt i figured it out bios update complete.

Thanks!

delete.
problem solved

(2014-12-05, 13:59)ajcast5201 Wrote: [ -> ]Nothing happens while I'm on the recovery screen. I know the USB port is working because the USB flash drive light is on. I can also scroll through the language using my keyboard's cursor.

I've used the chrome recovery tool on my Chromebox. I've also downloaded the recovery, unzipped it, changed the extension to .IMG, and used the recommend image writer to write the file to the flash drive. Neither of these methods got a response from my Chromebox.

what kind/size media are you using?
[/quote]

I am using Lexar flash drives (8GB and 16GB). I also tried a couple generic flash drives (corporate branded, so I don't know the exact brand) that are 4GB each.