Cyanogen Mod CM11 and the Ouya.

Cyanogen mod the Ouya.

Why Cyanogen Mod (sometimes refered to at CM11) you ask? The future of Ouya and the news of the most recent acquisition of the company to Razer has made a lot of Ouya owners such as myself feel rather uneasy with the consoles business as a whole. Couple this with an aging OS to the point where some favorite applications such as Kodi no longer work under android 4.1 due to programming issues. Razer is now stating that they will keep the Ouya servers up for another year. But then what? I guess they pull the plug and tell console owners such as myself to buy the next latest/greatest razer box. To which I will probably laugh and buy an Nvidia shield if I were to ever get an android box again. But that’s not the point of this blog entry.

previously

The point of this blog entry is to keep Ouyas running. Because both Ouya Inc. and Razer Gaming cannot tell users like me when my little silver box is dead. That is up to me to decide when my little silver box is truly dead. And Cyanogen modding is an alternative. By heavily software modding your Ouya you can continue to use your box well after the servers for Ouya are long gone.

Video tutorial fallback mirrors:

In case you have no-script enabled or for some reason cannot see the title video on this website. I have provided direct links for these videos.

  • WebM – Link – This is the newest video standard, works great on Opera, Firefox, Chrome, and newer android phones, not good for Safari, IE, Apple.
  • MP4 – Link – The most compatible codec but also rather large in file size. Make take a while to download.
  • OGV – Link – The fallback codec for older PC’s and Linux USB stick OS’s. 1st generation web video streaming based on Ogg-Vorbis encoding.

What the hell is Cyanogen?

For those that have never touched an android device in their entire life; Cyanogen is open source firmware which is typically modded onto cell-phones. Many cell-phone companies do not like people loading their own custom firmware onto their phones and will in fact go as far as to void the warranty on said phone if you upgrade it as a scare tactic to keep users far away from Cyanogen.

Is this procedure even legal?

Short answer is “yes.”

Unlike the original Xbox and its soft-modding and homebrew community where Microsoft would go after ANYONE making a .xbe file. Ouya Founder Julie Uhrman stated in their kick starter video on youtube indexed at 2:21 that “Their console is open for hackers who want to tweak the box and make it their own.” So it almost makes sense for lovers of Cyanogen mod to port the software over to this game-console. As for the new company Razor they are only interested in the Ouya Dashboard with the “discover” store where all of the devs have signed up to have their games published. Razor has no direct interest over the legacy Ouya hardware.

Pic not relevant, We just like that “Pause face” on 2:21. :)

Why even install Cyanogen mod to the Ouya?

Like any decision that you make with your device there is always advantages and disadvantages towards installing a new firmware onto a device. Lets go through some of them.

The good of Cyanogen mod:

  • Kodi – At the time of this posting Kodi is moving away from Android 4.1 and onward to Android 4.2 for their latest release of Kodi v15 which makes it much easier to develop for what they need. This of course created a bit of a backlash in the Ouya community as the default firmware for Ouya is still sitting at Android 4.1 . Kodi v14 is a perfectly fine video player that works brilliantly side-loaded onto the Ouya! But anyone who has witnessed the Kodi/XBMC progression will tell you that the moment the latest version gets released suddenly plugin development sort of stops on the previous versions. So Kodi is now telling Ouya users to upgrade to Cyanogen to experience v15 or to stay behind on v14.
  • Google PlayI have published articles in the past on how to get google play working on your Ouya. But over time Google has gotten more and more obnoxious with the way it decides to update itself. That sometimes on the Ouya OS google doesn’t really update properly . The end result is getting a lot of 921 errors when downloading apk’s of your favorite utilities and games off of Google Play.
  • Side Loading – There always will be compatibility issues with side loading any game or application on any android device as it’s just with going to a newer version of android it opens up the doors on games that otherwise would’ve crashed on the Ouya before. Once again, it gets back to how newer android operating systems can handle older apk’s as well as some of the newly compiled apk’s.

The bad of Cyanogen Mod:

  • Ouya Discover Store – If you like Ouyas Discover and do not want to screw around with getting your console working with weird controls or have to occasionally hook and keyboard or mouse to exit an application this can be awfully problematic.
  • Don’t want google play – You’ve never rooted your Ouya and have no intention to.
  • ROM flashing risks – Like anything there is a danger of hard-bricking your Ouya
  • Kodi v14 sideloaded on your Ouya – It’s perfectly fine for what you do and have no reason/intention of going to Kodi v15.x and above.
  • Hardware based compatibility issues – see blow.

Then Cyanogen mod will not be for you and you can stop reading right now.

Ouya Compatibility chart with Cyanogen Mod CM11:

All Ouya consoles can accept CyanogenMod. However, there is some compatibility issues in terms of Wi-Fi and Bluetooth.

1/8/2016 – I have decided to provide a compatibility chart to help decide if CM11 is right for your Ouya.

  • All ouya systems with the BCM4330 chipset are compatible with CM11 for Wi-Fi and Bluetooth. This includes the development edition clear, kickstarter bronze, and retail silver.
  • All ouya systems with the BCM4334 chipset are not compatible with CM11. Although it will load fine activating Wi-Fi and Bluetooth will not work. Someone on the XDA forums made a patch to at least get Bluetooth working for these models of Ouya however Wi-Fi is still crippled. This affects the Anthracite, Ninja Black, and Christmas White edition Ouya consoles.

3rd party controller compatibility in Cyanogen:

The good:

  • Ouya controller for the most part works. Home button behaves as a minimize command in Cyanogen. Touchpad does work so long as you do not plug a USB mouse into the Ouya. For some reason when you plug in a mouse for playing FPS games like quake it knocks out the controller touchpad functionality. You can temporarily get it back by un-pairing and re-pairing your Ouya controller via Bluetooth. But on reboot it’s gone again until you reload Cyanogen.
  • Xbox 360 controllers both wired and wireless work. I have taken the notes from the Ouya chinesse receiver and merged it into the keylayouts zip file.
  • A lot of your moble based controllers such as Moga and Nvidia all work.

The Bad:

  • PS3 controllers only work wired they do not work wireless. This was something that the original Ouya dev team actually worked on a bit with their variant of android 4.1.
  • It has been reported that Wii-Motes may not work as well. Same reason.

Disclaimers about software and Cyanogen mod:

S-Config or anyone on the internet for that matter is not responsible for any damages that occur both physical, financial, mental, or psychological when hacking of modifying the software of your console. If you have an issue with this then stop immediately and purchase a different android based console that can better suit you for applications such as Kodi v15.

Hardware prerequisites:

Basic hardware prerequisites for Ouya Cyanogen are as follows:

  1. USB male “A” to female “micro A” cable. In this tutorial we will not even be logging into our Ouya account which makes this cable a requirement.
  2. USB Keyboard – This will be essential during the installation process as Bluetooth will not be active when we go through the boot-loader nor will it be active during initial configuration of Cyanogen 11
  3. USB Mouse – Not nearly as essential during the bootloader process of but very handy when doing your initial configuration. Update 1/17/2016: You may want to skip the mouse all together on this installation if you want the track-pad of your Ouya Controller working. I have not figured out how to reset mouse control back after i plug a USB mouse into CM11 yet.
  4. USB Hub – It does not have to be self-powered unless you are hooking large external storage such as a portable hard drive to your Ouya.

Acquire the software:

I have setup a link for all of the Cyanogen mod to take place onto your Ouya known as “cyanouya.zip”. Click here or on the Download icon to the right to begin downloading the .zip file (approximately 314mb in size).

 02/26/16 – Due to too much hot-linking from other sites then my own the dropbox mirrors kept getting suspended and taken offline. Files are now being hosted locally through Anubianhost.

Extract files from the archive:

Use your favorite file extraction utility on the zip file you just downloaded. We’re using WinRAR but you can use anything. For this tutorial we will be extracting to C:\cyanouya which we will be using as a reference point throughout this tutorial. If you extract it elsewhere or if you are on a MAC of linux box make note of where you extract it to and make adjustments accordingly.

The files that are in cyanouya.zip are as follows:
  • adb.exe as well as the two DLL’s required to run adb
  • fastboot.exe which will be required to upload the recovery-clockwork-6.0.4.8-ouya.img via the micro-USB cable.
  • zip folder containing the following: cm-11-20160312-NIGHTLY-ouya.zip (Ouya nightly build of the Cyanogen OS) gapps-kk-20140105.zip (Google Play Apps) ouyabootmenu-mlq-v2.0.4.zip (required for Ouyas bootmenu) ouya-keylayouts.zip (which contains .kl files for the Ouya controller as well as a few other genetic controllers) recovery-clockwork-6.0.4.8-ouya.zip (This version of clockworks gets installed onto your Ouya bootloader and does not get removed). Please note: At the time of article this was the most currently nightly build. Newer versions can be acquired here.
  • driver folder containing files that allow you to access your Ouya in both “ADB” mode and “Fastboot” mode. The android_winusb.inf is already modified to find an ouya on USB device USB\VID_2836&PID_0010 .
  • apk folder which although we will not be using any apks during the installation of Cyanogen mod they are exceptionally handy to have after you have installed everything as I shall show you later.

 

Lets begin installing.

We’re going to power up our ouya and leave it on the welcome screen. These instructions do not require your Ouya to be rooted or even logged into your Ouya account. If you had a mint Ouya still wrapped in plastic and opened it up and plugged and powered it up. Then that’s all you need to do for now on your Ouya.

Now if you are already logged into your ouya and you want to start fresh you can always do a factory reset to get the “welcome” screen. Just go under MANAGE > FACTORY RESET to continue.. Just keep in mind when you do factory reset your Ouya all data such as XBMC/KODI profiles, save games, and settings for your emulators may be lost.

Once we are at the welcome screen on the Ouya now is the time that you will be plugging in your micro-USB cable into the back of your Ouya, and the other end to the PC.

Now lets go over to the PC side to see if we can find our Ouya in device manager (screenshots are all windows 7 and may vary between OS’s). If this is your first time plugging your Ouya in via USB you should see something like my device manager where the Ouya is in the Other Devices catagory. That’s not going to work with ADB in the state it is in . So we are going to update the driver.

Note: I have received a few users stating that they do not receive the “OUYA” underneath other devices catagory but instead only have the Ouya MTP underneath the “Portable Devices” catagory. If you are already logged into your Ouya do a factory reset as depending on what is going on with your Ouya the ADB function may or may not be disabled on it.

Right-Click on the Ouya in Other Devices and click Update Driver Software to continue.

Also, if you are running windows XP, 7, 10(32-bit-edition) and you do not see the word “Ouya” or something similar but instead see the words “Unknown Device” underneath other devices then your system has not properly detected your Ouya ADB port. The biggest cause of this problem is due to a bad or faulty USB data cable. Try a different data cable and try again.

I can’t find the unknown device catagory on my windows 10 x64 bit edition box! Help!

You are not going crazy if you do not see “Ouya” under “Unknown Devices”. We do however need to talk. Click here to learn how to correct driver issues with ADB inside of windows 10 64-bit for the Ouya. Do not worry, this will open another tab so you can pick up right from this section the moment your driver is straightened out.

Continuing onward if you did find “OUYA” in “unknown devices”

We are not going to let the OS choose the driver we want to use. We are going to pick it ourselves. Click “Let me pick from a list of drive drivers on my computer” and click next to continue.

Click on “Show All Devices” and click Next to continue.

Click on the Have Disk button.

We are going to browse where our ADB drivers are. Since I extracted my cyanouya.zip file right to the root of C:\ I can simply type in C:\cyanouya\driver . If you placed your drivers elsewhere or you are using the Android SDK instead of the ADB binary included in the zip file. You will then have to click the Browse button to find where your ADB drivers are at.

Click OK to continue.

Windows should have already determined that the best driver is “Android Composite ADB Interface” if not or if this is blank, uncheck the “Show compatible hardware” box and select your Android Composite ADB Interface from there.

Click Next to proceed with driver installation.

Windows does not like drivers it does not know about or where they come from. This is normal. Click “Install this driver software anyways.”

It should begin installing the driver. This may take around 10-30 seconds on your first time installing it.

If everything went well then you will get a message like the window above. If for some reason there is an error code. Then there is something wrong with your Ouyas connection. Click close to continue.

Your Other Device and your Ouya will disappear from device manager. You should now have a new catagory called “Android Device” and the device known as “Android Composite ADB Interface” . Your PC will now understand what your Ouya is whenever you connect it to your PC. From This point you can now close out of device manager.

Installing the adb_usb.ini file:

This file exists in your user profile folder underneath a section called .android and it has a very simple one line comment which tells ADB where to look for your Ouya in your devices. For example if your username in windows is “skippy” then the logical path for this file will be C:\Users\skippy\.android\adb_usb.ini . What is in that ini file is as follows:

0x2836

now you can either open up a command prompt and type in the following:

mkdir %USERPROFILE%\.android\
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"

Say that your username in “Penguin” for logging into windows. This will make the folder C:\users\penguin\.android\ and inside of that folder it will make a very small text file called adb_usb.ini . The reason why we must create this file in a very particular area is without it the adb.exe file has no idea what vendor to look for in device manager and it will come up blank in the next few steps.

Working with ADB to transfer data to your Ouya for Cyanogen mod upgrade.

We can continue going to the command prompt by clicking “Start” and “Run” and typing in “cmd” to pull up a command prompt. Once you are there you will want to do the following.

cd C:\cyanouya
adb start-server

It should respond with the following:

* daemon not running. starting it now on port 5037 *
* daemon started successfully *

Next lets see if adb can actually see our Ouya.

adb devices

It should respond with:

List of devices attached
015d49062a501415 device

If it does not have anything underneath “List of devices attached” then adb is not properly talking to the USB driver. Make sure your device is installed in device manager and the adb_usb.ini file exists underneath your %userprofile%\.android\ folder.

Unlike the ADB screen capture blog I did a while back there is no need to pass the adb connect command. You will be already connected via hard wire. The adb connect command is only required if you are connecting to a remote source over the network.

now we are ready to push all of the .zip files to the Ouya /sdcard/ folder at once. Unlike previous documentation where they wanted you to adb sideload each zip file in the recovery bootloader. We’re going to push them all at once and then let the ClockWorkMod bootloader handle it from there.

adb push zip /sdcard/

If you are in your C:\cyanouya folder then it should report something like this:

push: zip/recovery-clockwork-6.0.4.8-ouya.zip -> /sdcard/recovery-clockwork-6.0.4.8-ouya.zip
push: zip/ouyabootmenu-mlq-v2.0.4.zip -> /sdcard/ouyabootmenu-mlq-v2.0.4.zip
push: zip/ouya-keylayouts.zip -> /sdcard/ouya-keylayouts.zip
push: zip/gapps-kk-20140105.zip -> /sdcard/gapps-kk-20140105.zip
push: zip/cm-11-20150727-UNOFFICIAL-ouya.zip -> /sdcard/cm-11-20150727-UNOFFICIAL-ouya.zip
5 files pushed. 0 files skipped.
1291 KB/s (306718311 bytes in 231.945s)

Yes, it will take around 4 minutes to complete the transfer because of how much data we are sending.

So far, everything we’ve done could’ve been easily done by an ADB network connection instead of going through the headache of USB connections. The next command is where ADB network will fail you.

adb reboot bootloader

This will place the Ouya into the bootloader state otherwise known as “fastboot” as your device manager will start chiming in finding unknown devices once again.

Note: At this time your Ouya will only have a power light and a pitch black screen. This is normal as we have not given the Ouya any instruction as to what to load yet. If you reset your Ouya right now it will break out of the boot-loader and return you to the Ouya welcome screen. We have written nothing to the boot-loader of the Ouya as of yet. Make sure the keyboard is plugged into your Ouya at this time.

Working with fastboot:

Just like with ADB when you first plugged it into your machine. Device manager now detect a new unknown device in the Other Devices catagory known as Fastboot . We need to install the driver for this as well in order for us to push the ClockWorkMod over USB to the Ouya. Without ClockWorkMod the rest of the Cyanogen mod installation will not work.

Note: If you do not see the word “Fastboot” under the “Other devices” catagory but instead see the words “Unknown Device” underneath other devices then your system has not properly detected your Ouya ADB port. The biggest cause of this problem is due to a bad or faulty USB data cable. Try a different data cable and try again.

2nd Note: On some operating systems “Fastboot” may not show underneath “unknown devices” but in fact may automatically install itself under the “Android Device” catagory. This is due to updating the .inf drivers so that Windows XP users to perform this hack as well. If it does indeed install you may skip all the way down to passing the fastboot commands down below.

Once again we are going to select “Let me pick from a list of device drivers on my computer” and click Next to continue.

Click “Show All Devices” and click Next to continue.

Click the Have Disk button to continue.

We are going back to the C:\cyanouya\driver like the ADB driver install. Click OK to continue.

Unlike the ADB driver windows isn’t quite sure what is going on as it cannot identify the correct driver. Click on Android Bootloader Interface and click the Next Button to continue.

Windows is really not sure what you are doing. This is normal. Click Yes to continue.

If everything goes well you should receive a screen like the one above indicating that the Android Bootloader Interface has been successfully installed. Click close to continue.

Device manager will be happy once again and we can go back to our command prompt. Instead of ADB we will be using the other executable in the cyanouya.zip folder called fastboot.

Pass the Fastboot commands to your Ouya.

To test to make sure fastboot can see your Ouya type in the following:

fastboot devices

Just like before it will report back if it can see your Ouya or not.

015d49062a501415        fastboot

If returns with a statement similar to the above then everything is good. The next command you will be typing in will be the following:

fastboot boot recovery-clockwork-6.0.4.8-ouya.img

It will report back the following at the same time you will notice your Ouya come back to life with a signal on your TV.

downloading 'boot.img'...
OKAY [ 1.594s]
booting...
OKAY [ 0.264s]
finished. total time: 1.861s

Clockwork Mod loading Cyanogen Mod into your Ouya:

At this time you should see your Ouya come back to life but instead of the typical Ouya splash screen you will be greeted with something new. You will be welcomed to the ClockWorkMod splash screen.

Out of interest of saving bandwidth and readability. I shall focus on just the upper-left hand corner of the screen which is where all of the action of ClockWorkMod is at. There will be information text with each step we do and if the screen changes to much I’ll make a full-screen shot. But Lets begin.

Using your keyboard, arrow down to “install zip” and hit enter.

Arrow to “chose zip from /sdcard” and hit enter.

Arrow down to “recovery-clockwork-6.0.4.8-ouya.zip” and press enter to install. This will make ClockWorkMod your permanent bootloader recovery partition on your Ouya which is essential for Cyanogen mod to work properly.

Arrow down to Yes and hit enter. This should only take about 10 seconds to install.

The next section we are going to install is the Ouya Boot Menu which is a partial install that makes it a lot easier to return to ClockWorkMod in the event you wish to revert back to stock.

Arrow to “chose zip from /sdcard” and press enter.

Arrow down to ouyabootmenu-mlq-v2.0.4.zip and press enter.

Arrow down to Yes and press enter.

The next section we are going to install is the the Cyanogen Mod nightly build which is the core of our OS.

Arrow to “chose zip from /sdcard” and press enter.

Arrow down to cm-11-20160312-NIGHTLY-ouya.zip and press enter

Note: the dates will always change which is normal for nightly releases.

Arrow down to Yes and press enter.

This process can take anywhere from 4-5 minutes to install as it has to unpack 300+ megs onto your Ouya.

The next section we are going to add Google Play functionality to our Cyanogen mod.

Arrow to “chose zip from /sdcard” and press enter.

Arrow down to gapps-kk-20140105.zip and press enter.

Arrow down to Yes and press enter. Installation should take around 30 seconds.

The final selection that we will install is the keylayout files or .KL files that are required to attempt to make not only your Ouya Controller compatible with Cyanogen but other controllers such as the PS3 controller and the Xbox Controller.

Arrow to “chose zip from /sdcard” and press enter.

Arrow down to ouya-keylayouts.zip and press enter.

Arrow down to Yes and press enter.

After all of these partial installs, you should have a complete Cyanogen Mod now loaded onto your Ouya. Now before we reboot there is one last thing we need to do.

Clearing cache and wiping user data in ClockWorkMod for Cyanogen Mod first-time boot.

Clearing all user data and cache from your Ouya is very important because if you do not. Cyanogen may simply sit and do nothing on the first time you boot it because it’s reading data from a previous launcher that it really should not read. So lets begin.

If you are still updating zip files. We need to back out of this menu. Simply arrow down to Go Back and press enter.

Arrow down to “wipe data/factory reset” and press enter.

Arrow down to Yes and press enter.

Next we will wipe the cache partition. Arrow down to “Wipe cache partition” and press enter.Arrow down to Yes and press enter.

The last section requires us to go into advanced mode. Arrow down to advanced and press enter.

Arrow down to “Wipe dalvik cache” which is what google play likes to use and press enter.

Arrow down to Yes and press enter.

We are going to back out of the advanced menu now. Arrow down to “Go Back” and press enter.

Finally, we are all done with CWM we can now reboot system now to begin booting your new Cyanogen mod OS.

Welcome to Cyanogen Mod OS on your Ouya.

The very first thing you’ll be greeted with is the Ouya Bootmenu. You do not have to touch anything and it will disappear in about 3 seconds. But if you want to go back to the recovery partition you can simply click your Ouya power button to cycle through the menus on this screen.

Once your let it go into Normal Boot mode it may take up to 3 minutes before Cyanogen Mod launches for the first time after the splash screen appear.

Your installation is successful if you get the Welcome to Cyanogen Mod screen asking for language. That means it was able to setup its profile and didn’t encounter anything strange that would otherwise crash the first-time startup screen such as erroneous cache or user data left behind from another launcher.

This is where having a mouse as well as the keyboard is super-handy since Bluetooth has not been enabled yet.

From here you will be asked a series of questions such as your Wi-Fi (if you are already hard-wired then it will not ask you) as well as your Google Play account so that you can begin downloading from the new marketplace.  As well as basic questions as if you are on a new tablet or phone device. you can leave all of the settings default if you wanted.

From here you can customize your desktop by simply click-dragging widgets where you want. I personally get rid of everything including the backdrop because it saves some bandwidth when recording video. You may want to wait about 5 minutes to begin using Cyanogen Mod as it will be in the process of updating Everything such as all of the google plugins as well as the play-store marketplace to the latest version. If you already downloaded items with the google marketplace you can re-download them again by launching the Play Store and going into Apps.

Enabling bluetooth in Cyanogen Mod.

One of the first things you may want to do is get Bluetooth working ASAP so you can ditch the keyboard/mouse and go back to your Ouya Controller.

You will want to click the icon that is right above the default home screen of your Cyanogen which is where all of your installed applications are. From there find settings and click on that.

You should be approaching familiar territory for those Ouya people that have played in their advanced menu to get controllers working. And it even found my stock Ouya as I keep the bluetooth running all of the time in my house. Click SEARCH FOR DEVICES in the upper right-hand corner to place the Bluetooth chip in discovery mode. While it is scanning. Hold the power button of your Ouya controller down until both lights are flashing.

It will find your controller relatively fast in contrast to how Stock Ouya finds the controller. But it shows it bluetooth network address instead of actual name. This will straighten out the moment you click on it.

After you pair your controller and give it permission to pair. It will actually show the proper name. As well as player assignment on your Ouya Controller. You can now navigate around the menus with your analog or digital D-pad as well as use your mouse track-pad (depending if you have a USB mouse hooked up to your Ouya or not).

Overscan issue with CyanogenMod.

Flat panel televisions are designed a little differently then regular computer LCDs. Sometimes the picture falls off of the screen known as overscan . to correct this problem you can either go back into adb shell or launch the shell program in the applications folder of Cyanogen and type the following commands:

su
setprop persist.sys.hdmi.overscan 1

setprop persist.sys.hdmi.overscan.val [example: 0.0 – 0.2]

The value is a minimum of 0.0 and a maximum of 0.2 for overscan compensation. As an example. My 32″ Vizio my overscan settings are as follows:

setprop persist.sys.hdmi.overscan.val 0.02

And my Apex 27″ is as follows:

setprop persist.sys.hdmi.overscan.val 0.13

The value of your flat panel TV may be different then mine so adjust accordingly.

reboot

you will have to reboot in order for your adjusted overscan values to take effect.

Special thanks and credits:

XDA Developers – and Milaq for all of his work on the CM11 nightly builds. These people deserve the real credit. All I did was write up a user guide.:)

Kodi – For giving reasons why Ouya is still alive in 2016 and beyond.

Ouya Forums – For kicking me in the ass to actually write this documentation.

Related Articles:

Don’t like Cyanogen? Follow this tutorial on how to uninstall it.

Are you a Kodi user and your MP4s and MKV are not showing sub-titles or On Screen Display? Click here to fix that problem.

 Want to access Ouya Discover through Cyanogen? This link is for you!

That’s what server said.

END OF LINE+++

174 thoughts on “Cyanogen Mod CM11 and the Ouya.

  1. Thanks for the In-depth guide. Worked great for me. One thing I would like to point out is If you are Running Windows 8.1 or 10 you have to disable the driver signature enforcement in order to install these drivers. This can be done by holding shift down while you select reboot from the start menu, then selecting it in the menu options.
    Thanks again for the great guide.

  2. @1st thx for the tutorial.

    Actually I did the ouya upgrade a year ago and it was messy. Could you briefly describe howto do an update. Do I have to use adb to get the files over or is there an easier way? Where do I start.

    More important is the following. I try to use it for Netflix, Twitch and Spotify.

    In Netflix I don’t see any controls. I can’t get the progress bar so I can’t really jump to a certain position which makes it difficult to use.
    Spotify didn’t start at at 1st or went into a endless loop play a video so I could not login. I think I had to change some gpu settings.
    Twitch could run for ours but mostly it loses the stream after some minutes.

    I has sevearl other android devices where I don’t have those issues. Any ideas?

    Using the controller is also messy. Sometimes it gets stuck going to one direction. The borders around the current selected tile in twitch os so thin it’s almost invissible.

    Any suggestion?

    • Hello,

      To answer your questions, If a brief description was made like what I’ve seen on forums in the past steps would be missed and you would end up soft-bricking your Ouya. This is why the presentation for this tutorial is the way it is. We remember doing it the hard way too jumping between five tabs on the XDA developers forums. They’re good guys and I thank them for all the links they compiled but documentation was lack-luster at best.

      You can do it without ADB, but you will be adding A LOT more steps to the process. Transferring all files to usb stick and onto your /sdcard/ . Playing with dangerous programs like KingRoot to actually gain root access, using outdated programs like the old ClockWorkMod.apk files to get it booted into CWM only to be forced to update again.

      It comes down this. Until someone makes a OneClickCyanogen.apk file. ADB is probably the safest and most effective way of doing cyanogen.

  3. Thank you very much for your easy-to-understand guide. I started by bouncing back and forth between numerous forums and blogs, many of which were out-of-date and/or vague, in my initial attempts to perform the upgrade, and somehow stumbled upon your excellent walk-thru and comprehensive collection of respective apps.

  4. This tutorial was spot on and awesome. I always enjoyed the ouya project. Once we had a way or porting over xmbc/kodi. Before this tutorial the older versions of Kodi would conflict with the Ouya updates. I was ready to move away from the ouya on to another device. Thanks for all the hard work you’ve put in here. Hopefully, It doesn’t stop here. Would be nice to remove in with third party software like teamviewer instead of adb. Remote downloads. Do you any info on this?

  5. feel like banging my head against a wall. I’m a newbie and cannot install adb_usb.ini because windows won’t let me name a folder .android

    • you have to install sdk tools/developers kit first in order to have windows create a .android map for you automatically.
      in order to install sdk it will ask you to install jaja as well.

    • I had issues with poor quality cables myself. I liked using gamestik USB charging cables because I thought it was kind of ironic to use and all of the pins were present. What I found out what resistance on the cable was too high and kept showing my device as “Unknown Device” with no hardware class.

      There’s also cables that are simply charging cables, just two wires going through it and that’s it. Best bet to ensure it’s not your data cable is hook up another device that takes microUSB to see if the device manager can detect that one. The Ouya OTG port can get really sensitive sometimes.

  6. Hi,
    The install process is vrey simple, and so are the inscructions, Thanks :)

    QUestion, for some reason my video quality is very low, Pictures are pixelated and any video I try are appears low res (yoytube, Netflix). Do you know what could be hapening and if there is a fix for that?

    Thanks

    • Hello,

      A little out of scope of this tutorial, but I can answer it quickly.

      Video quality in both twitter and Netflix rely heavily on your bandwidth connection as well as your wireless connectivity. Because both youtube and Netflix will auto-adjust to prevent buffering. You can check your wireless connectivity with this app. From there you can then test your bandwidth connection with this app.

      I made a quick demo of how my YouTube operates as well as XBMC and even some gaming like BombSquad just to show people that performance on the Ouya is indeed good and you can check out the YouTube link here. Now the default YouTube player only plays back files at 720p which is crap-tastic but nowhere near pixelated. . But if you override compatibility and get the youtube player for GoogleTV that one will allow you to play 1080p. and just to show you the Ouya can handle the 60fps video. I launched XBMC and played the same video from my UPNP server.

  7. This was the best tutorial I have ever used. Thank you, you saved me hours of XDA forum read through that was getting me no where. I’m a beginner that is new so your steps were very nice and thorough.

  8. Thank you so much for this guide, I managed to install Cyanogen perfectly with this tutorial but this this for one reason only and that’s to install a newer version of Kodi on my Ouya.

    I’ve searched everywhere via google but can’t find any tutorials on how to install say Kodi version 15. or later on my new Ouya running CM11

    Could you please tell me how?
    I can’t seem to install it via the playstore, it keeps saying installing for over half an hour now.
    Thanks

    • You should be able to just go into the Google Play store and download Kodi . If you got your google account setup with your CM11 Ouya you can even tell Google Play to push the app for you over to your Ouya from say a PC. The really good thing about using Google Play to install Kodi is that it will keep it up to date for you (i’ve gone through 8 updates already).

      Alternatively, you can download the android-arm APK version right off of the Kodi downloads on their homepage in case you didn’t install Google Play onto your CM11.

      Update: Noticed you are having issues with google play. try to reboot your Ouya and try again, I had that happen once when i first launched google play and I didn’t let it update its dashboard which can take about 3-5 minutes on first launch. after it updates it will be fine.

  9. Good morning and a happy new year.

    First of all I would like to thank you for your effort to make a guide so simple and thorough that even I have managed to upgrade the Ouya and extend it’s life as an Kodi dedicated player.
    Kudos sir,your help was priceless for me.It took me less than half an hour to upgrade.Normally when I mess with stuff of this kind it takes me couple of days and a long of read-search combination.

    I got a couple of questions if that is ok for you and you can help me.
    I wanted to set on Ouya a static ip through ethernet so as to set Yatse on my mobile and control it from there.Unfortunately I haven’t find a way to do that.There was no section I could find for ethernet tweaking on CM11 setings.
    Also the track-touch pad on my Ouya isn’t working in both interfaces,CM 11 UI and Kodi UI.I have installed all the packs through your guide.

    Lastly,is there any other uprade available-necessary that needs to be done besides the one already done?Or there is another CM edition available higher than 4.4.4?

    Thank you in advanve for your time and help to newbies like me…

    • First question about the Ethernet. Good news on that front the ifconfig command has been transferred over to cyanogen for hard-lined Ethernet connections. Click here to be taken over to a a site that has some excellent examples of how to do that in the android shell.

      Another way of dealing with this issue because I have my Ouya set for a specific IP all the time for things like bombsquad is if your router can handle reserving static IP leases for specific MAC addresses. That way everytime your Ouya comes online your router will not give it a normal address pool but a special IP that you reserved for it. DD-WRT and Open-WRT support this feature. Some Netgear OEM routers support this feature as well.

      Second question: Touchpad issue- It’s something I was noticing too. At first I thought it was just a question of too many launcher. But it has to deal with bluetooth pairing because if you unpair your controller and re-pair it trackpad works until next reboot. I’ll have to see if there’s a script that can be run to correct this issue.

      Third question: currently the nightly builds of CM11 for Ouya are the only ones being maintained. Now this doesn’t stop someone who’s really good with compiling android from taking the CM12 branch for android 5.0 and attempt to add the device libraries/recompile for Ouya. So far, that has not happened yet.

      • I must admit that this was quick like Lucky Luke…
        Thank you sir…

        I will try the first answer later, after work, at home and will give you feedback.
        My router is a TP-Link,quite new,so I will check if the trick with the ip can be done.

        I didn’t notice that with the trackpad I am going to check if it works after pair-unpair.It’s just that you need also a mouse in many points. (Ok I can always take a bluetooth keyboard with touchpad on it but for argument’s sake and conversation favor).I ll check and come again.

        As far as the third point concerns me,I do have the will to do things like that but unfortunately that requires skills and knowledge that I don’t have. :p
        Nevertheless so far the Ouya took a deep breath and that’s quite good cause it’s very handy small piece of hardware (maybe not the one that kickstarted so much,but that’s another story).
        If somenone eventually ports a higher CM then the small Ouya will be outstanding VFM.

        Greetings my friend from Corfu,Greece.

        Thank you for your time and have a nice day

        • Checking the XDA forums it seems we’re not the only ones with the trackpad issue. link.

          But the problem is easily reproducible by removing the Bluetooth profile for the joystick and re-adding it. So it may just be a firmware bug that needs to be addressed by milaq.

      • I might have spoken a little too soon on question number 3. XDA forums if you look at the door of the Ouya thread you’ll see that people are actually doing Ports of CM12 as well as the Android-TV. A lot of it is released as of two months ago so it’s still super-beta. However! This is good news espechally since a lot of the Android TV apps have moved on-wards to jellybean 5.0 and beyond.

        • Great news indeed…Hope it goes well…

          Let’s keep an eye on this,looks quite promising.
          Wish I had an extra Ouya for testing purposes but this is out of question…

          I ll make a bookmark of that,so as to be in touch…

          Glad that I also made you learn something today…hehehe…

  10. Hello, whenever I boot into the system, the WiFi wont turn of and keeps saying, “Turning WiFi on…”. Is there any fix to this, I factory rest it a couple of times but nothing seems to work. Please Help!!!

    • Whenever it does “turning wifi on” or “turning bluetooth on” ether or really. That’s not a happy message. CM11 is having difficulty activating your WI-fi chip. I’m going to assume that you have an Ouya Silver/launch-retail edition with a metal finish and you don’t have the darker “Ouya Anthracite” version with a plastic look as Anthracite Ouya WI-fi is incompatible with CM11.

      Have you tried reverting your Ouya back to Stock ROM just to see if anything changes on that side?

      • I do have the Ouya Anthracite. I am already in the cyanogen mod, so what should I do? Should I follow your other tutorial to revert it, or is there a different cyanogenmod for the Anthracite?

        • Anthracite, ninja black edition and white christmas edition ouyas have a BCM4334 chip-set versus kick-starter bronze and silver ouyas with a BCM4330 chip-set. the closest ROM you will get for anthracite/black/white Christmas edition ouyas is http://forum.xda-developers.com/ouya/development/rom-cm-11-black-edition-t3110134 which at least gets you Bluetooth support back onto your anthracite model Ouya. Unfortunately,no one in the XDA scene has taken it a step further by correcting the WI-fi issues . So at that level you’re stuck with either hard-wiring your Ouya, or reverting back to the Original stock ROM.

          • Yes, ethernet via RJ-45 works fine. if for some reason you are unable to activate your Ethernet card after you’ve loaded CM11 you can “ADB shell” into your Ouya via USB and pass the following commands.

            netcfg eth0 up
            netcfg eth0 dhcp

            I didn’t need those commands on my test anthracite ouya. I simply plugged it in and it worked. If for some reason the custom ROM for bluetooth doesn’t work for you. You can get a xbox wireless receiver for most of the android games and be fine.

  11. I did the whole thing and it works! Thanks a lot! Saves me a lot of jumping between tabs on the XDA forum.

    Now is there a way to use a PS3 controller without leaving it plugged in? Ive tried but cant get it to work. I did the whole plug in usb, turn off OUYA, turn on while pressing the home button on the sixaxis, and it doesnt sync it.

    • That’s actually a really good question. I tried my PS3 controllers here and pulled logcat. didn’t really find a whole lot of information there. When I hardwired my PS3 controllers they acknowledge as being an input device. but bluetooth still shows blank. I tried a utility known as “Sixaxis controller” and it did assign a device ID to it and got partial control. But it was not complete. I didn’t like the commercial apk SixAxis Controller as it cripples your bluetooth for only PS3 devices rather then being passive about it like the Ouya was.

      The only i can think of is hid-sony.ko is not installed into Cyanogen properly and thus no bluetooth detection for special sony devices are not installed. Not sure how to fix.

      Thanks for bringing this up as I shall revise this blog accordingly.

      • Thanks! I’ll keep an eye open. In the meantime i’ll use it wired in.

        I tried the Wii controllers too and no success, it wants to sync up, but asks for a pin…

  12. Successfully upgraded to CM 11 and kodi 15 but I have a few questions:

    1) anyway of changing CM resolution – it’s stretched (this is not mandatory but would be nice)

    Kodi resolution was easily fixed

    2) Shutdown options – only getting Exit – any way of restoring the Sleep mode or the double U button to enable the shutdown/sleep options.

    3) startup – although BT works with Ouya pad…I noticed I have to select it from CM BT otherwise it won’t connect…Once I select it, it’s paired.

    Hopefully 2 and 3 can be fixed.

    • question 1 is easy.

      either ADB shell OR use the terminal emulator app within CM11 and type in the following.

      su
      setprop persist.sys.hdmi.overscan 1
      setprop persist.sys.hdmi.overscan.val [0.0 - 0.2]

      on my apex monitor i set it to setprop persist.sys.hdmi.overscan.val 0.1 and everything now fits in the trebuchet launcher. you can move in increments of 0.01 to get the perfect fit.

      2. Pressing the ouya power button once seems to put it into this quasi-sleep mode.. doesn’t turn off the ouyas power or none of that. but the annoying thing about CM11’s sleep is once the controller goes to sleep it doesn’t re-pair until you power it back on again. Usually when i’m done with the Ouya for the night I just launch a free app from google play called ‘quick boot’ and just shut it down.

      3. well in CM 11 trebuchet launcher the BT icon comes up right away for me. So I’m not sure what to say. and my ouya controller (tested with both 0x0103 and 0x0104 versions), keyboards, etc all pair without issue minus the track pad.

  13. Hi i tried your tutorial but my ouya is not listed as an unknow device but as an usb device, and when i follow your steps, i get a error saying that the inf file is corrupted. plz help

    • I encountered this problem where it loads up as a generic USB device with no device ID. First thing I would try is getting another micro-USB cable. Apparently the Micro-USB port on the Ouya does not have any line conditioning on it so if the cable is too long or poorly insulated it’ll just read as a unrecognized or blank USB device.

      As for the INF I did an integrity check and everything is okay with it.

  14. Thank you for the great instructions. They worked perfectly.

    For those of you that had problems creating the .android folder, just open a dos window and “mkdir .android”

    I am having 1 issue. My Wifi starts with a link speed of 55Mbps, but after a few seconds of wifi use, it drops down to 5Mbps. Is there a fix for this ?

    • That’s a weird one with the speed dropping to 5Mbs. On my DD-WRT when my Ouya is not transmitting anything it will naturally drop it’s rate down to 1-5Mbs, but when i jump on chrome with it it’ll spike anywhere from 35-55Mbs again. So according to my Netgear running DD-WRT it seems the traffic is always variable. Have you checked your signal strength with the wi-fi analytic software on google play?

  15. My DD-WRT is fine. My laptop and tablet don’t have speed issues and they are further away from my AP compared to my Ouya.

    I did manage to get 26Mbps by rotating the Ouya box so that the HDMI port side is facing the living room instead of the back wall behind my tv. Not sure if this is a real fix or a coincidence. But so fare the speed has stayed constant and I can use iptv without any buffering/stalling. Of course, that doesn’t explain why every time it would connect at 56Mbps and then drop to 5Mbps after a few seconds of video streaming.

    I will try the wifi analytics program if the problem comes back.

    What speed is everyone getting with their Ouya box ?

    • I should state that there has been many complaints in the past about the wi-fi connectivity within the Ouya community. And how it’s not as awesome as it should be. Some users also tipped their Ouya over because even though a metal finish case looks cool, it doesn’t do much for wi-fi and bluetooth transmission. Early on there was an article done to one of the Ouyas demonstrating some drastic measures that I did by mounting an external antenna and getting very good results from it.

      I’d be interested to hear about speed results from other users on CM11 as well.

  16. Hello,

    yes, I think the weak wifi issue on the Ouya box is either the hardware or the plastic covering. I doubt it is caused by the OS. Rotating the box 90 degrees can make the difference of 0Mbps or 26Mbps. So it sure seems like a hardware issue.

    Thanks for posting the mod to add the antenna. It looks a bit difficult & risky. For now, I’ll try to position my Ouya for optimal wifi reception. I guess my other option would be to use the ethernet connection.

  17. Dear friend

    Thanks a million ton for your easy to configure my dumb ouya TV to new cyangn OS & it worls great.

    Regards,
    Ummar Shaikh
    Mumbai, India.

  18. +1 to say thanks… not only thanks, but a BIIIIIIIIIIG thank you for all this friendly guide “how to install Cyanogen on OUYA”.
    I presume that what I have installed ccm-11-20151221-UNOFFICIAL-ouya.zip (Ouya nightly build of the Cyanogen OS it’s from 12st of last december of 2015.
    Do you have any news about to install a new CM12?
    So far so good, but just wondering….
    Once again, many thanks ;)

    • There is actually an image out there. But I was going to wait a little bit before talking about it because CM12 is very super-beta on the Ouya. But progress is being made and I know a lot of people are eager to get a stable CM12/android 5 as that’s where all of the cool android TV apps are at.

  19. Frustrated!
    It won’t find anything under ADB devices. Tried at least 5 cables.
    May try to get my hands on another computer and try with it.
    Anything else I might have done wrong? If the .android folder and directory are wrong womehow, would this result?
    Sich….

    • I guess first thing is first. Does it find your Ouya under device manager. And you were able to load the driver up as the ADB composite device? If the driver is not loading, or even if you are using a different driver such as one of the nvidia ADB drivers, then the ADB bridge will not detect your Ouya.

      If everything seems okay in device manager, and it is showing up as a ADB Composite Device after loading the driver. THEN I would start looking at your %user%/.android folder .

      • Thanks… and thanks for the guide. I should have said that first!
        OUYA detected as such, after driver install it showed up as Android Composite ADB Device. Starting ADB server worked as expected.
        ADB Devices returned no results.
        I did have two other files added to .android folder, with the .Ini file. That led me to believe it was probably done right, but I will try it again.
        Thanks again for the guide, and the follow up support – it is greatly appreciated!

      • So I installed and ran Android SDK, then command prompt to create ini file and all went well! Very thorough, simple process to follow to install.
        My only issue now is: Should I have been able to check my version of OUYA for wireless/bluetooth (other than outside visual) for proper chipset?
        I have the black/silver standard OUYA retail box and wireless connects, obtains IP, then shows as disabled, and bluetooth won’t connect. It’s no big deal – I will work around. I just assumed that, based on the info, that it should have worked.
        Thanks again for the great guide. Just loading up KODI now and am looking forward to testing it out.
        Cheers!

        • woo! glad everything is working out for you!

          Sorry about not getting back to you faster about the driver issues. When I was writing up the documentation I did encounter issues where you had to use the exact version of the ADB Composite device driver AND the adb.exe version at the same time. Found this out the hard way when my SDK only updated my platform tools but didn’t update the driver.

  20. Good morning to all,

    I came up with a strange situation after upgrading from Kodi Isengard to Kodi Jarvis.
    Suddenly I can’t make the On Screen Controls appear during playback.
    You know the ones that you can fetch with the Blue U button and make settings,subs etc appear on screen.

    I have also uninstall completely Kodi and reinstall.Same thing happens either on local playback or streaming.Bit frustrating because I haven’t done anything to cause it.

    It crossed my mind to be a controller problem but I had no luck with using also Yatse from my android phone.

    Did anyone came across something similar?

    Thanks in advance

    • A little bit out of the scope of this blog entry but it does have to deal with a setting within CM11 so I can answer this. Took me a little bit to replicate the problem you are having.

      The way they programmed Kodi is they’re trying to bounce as much off of the GPU as possible. In jarvis this a little problematic because certain codecs will enable 3-d pushing all of the 2d into the background. You can see this if you load an AVI which has not been developed as much and the On screen Menus work just fine. but mp4’s it dies on.

      The way to fix this is as follows:

      First you have to enable developer options so you can modify how CM11 renders videos.

      1. Go into the settings of CM11 by going to the gear icon on your desktop.
      2. Scroll all the way down to “About tablet”
      3. Scroll again down to “build number” and tap that 5 times to enable the Developer Options menu.

      then:

      4. Go into Developer Options.
      5. Scroll down to “Hardware Accelerated Rendering” and check the boxes “Force GPU rendering” and the really important one is “Disable HW overlay” which will force the GPU to do everything!

      re-launch XBMC and try out your mp4’s when I tick the “Disable HW overlays” off the subtitles and menus go away, turn it back on and they re-appear in all mp4’s, and mkv’s in my library.

      Sorry for the delay and hope it helps you out.

      • Thank you S…your answer was quite quick…

        It happens also to find the solution to the problem from another side and I was coming to reply and let u know.

        I accidentally found that on .avi the bar was there but this wasn’t happening on .mkv files.So after a long shot and tricky thought I decided to go to Kodi settings and untick the Hardware accelaration from both codecs and voila…

        The bar was back…too bad that I had completely uninstall everything.

        I hope yours and secondly my solution give all others the ability to avoid frustration…

        nice evening everybody…

    • I just answered the OP on this question. It’s -kinda- a XBMC problem but also a CM11 setting. Check out the response to Pavlos. I may publish a separate entry about this since this is popping up with Jarvis.

  21. Just one thing, I check force gpu rendering and disable hw overlay, however, after a restart of Ouya, the “disable hw overlay” keep unchecked… Only happens with this second option.

    • Okay, the ‘disable hw overlay – and make it permanent’ problem is something that plagues all of android, not just CM11. This bug is popping up because a lot of android people are using google play to update Kodi so many have jumped from 15 isenguard to 16 jarvis and we may just be finding out that there is more bugs out there. Until Jarvis or the newest version Krypton fixes this problem. I found this article on XDA Forums talking about how to do this and it involves injecting a script into CM11 to shut down the overlay upon startup. It’s not an overly friendly fix. But I just installed it onto mine and it seems to work.

      You can download it here.

      Credit for this script goes towards titanic_fanatic

      Here’s how to install it.

      1. unzip the file 91fixoverlays. assuming that you have dropped the script to the root of C:\ from here on out.
      2. ADB into your ouya, you can do this via cable or over the network underneath developer options and then you can adb connect x.x.x.x into your ouya over network.
      3. type in the following:

      adb push C:\91fixoverlays /sdcard/downloads/

      then after the file is transferred:

      adb shell

      now we need to unlock the system file, move the file into /etc/init.d and give it execution rights.

      su
      mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
      cat /sdcard/downloads/91fixoverlays > /etc/init.d/91fixoverlays
      chmod 777 /etc/init.d/91fixoverlays
      reboot

      I tested this on my Ouya and now on every reboot the disable HW Overlay is checked. Also note that you don’t HAVE to ADB into your Ouya. I just do it this way assuming nothing is installed on your CM11 Ouya. If you have a good Root explorer or file copy program that grants SU access to write to system files and change permission to files and give them execute status then you may use that as well.

  22. Many many thanks “S”

    One little thing, on mine ouya

    adb push C:\91fixoverlays /sdcard/downloads/ it’s

    adb push C:\91fixoverlays /sdcard/download/

    download – without s

    May help others

    Once again, you are the MAN – looking forward to CM12 ;)

    • Thanks for the correction on that! I should make a seperate article dealing with this since I know there’s a lot of traffic from Kodi about CM11. Good to hear everything is working! And I’m kind of excited about the CM12 coming for Ouya as well!

  23. First off, I am so glad I found this post. I was having the hidden overlay issue as well. I noticed that when I stopped the video, I would see the osd for a split second before going back to the menu. I figured it had to do with layering, kinda like a z-index issue in CSS. Awesome job figuring out that it was a 3d/2d thing, and even better job figuring out the work around! Worked like a charm for me.

    I also only had the issue when updating to Jarvis. It may just be in my head, but the menus now seem to be a bit more sluggish than before. Regardless, I would take this over no osd any day! As for the reboot issue, I basically keep my ouya on 24/7, so in the rare instance I reboot, it’s not the end of the world to need to redo that setting

    What could cm12 do to fix this for us? Anything?

    Huge thanks for this, and I agree, you should totally name this its own post. I had a lot of trouble even finding this page, and I would think everyone on ouya with kodi Jarvis will have this problem.

    • You got it. I just made a new article talking about the Kodi bug and placed it at the bottom of the article. Also link here.

      As for CM12, I think a lot of people are looking forward to it because it gives your Ouya more capability with android TV functionality. To my knowledge the only Android TV app you can use with CM11 is an older version of YouTube you can find by googling “com.google.android.youtube.tv-1.2.7-10207100” unlike the standard youtube player for android that one works beautifully with the Ouya Joystick. with CM12 you can Netflix, HBOgo, and all of the really fun ones that other Android TV people get to have.

      For all I know it may not even be a problem with the OS but rather a programming issue with Tegra chipsets and Kodi. Which we can hope that the next version “Krypton” will fix.

  24. Your ‘i’ key is sticking so the link doesn’t work, but by putting in all the ‘i’s’ found it.
    A couple things that may confuse and confound some (like it did me!) that could be put into the fantastic guide:
    – In this guide, we named the folder ‘cyanouya’ (that contains adb, files, etc). In that guide you extracted overlay disble script to ‘cyanogen’. Obviouly adb did not load for me there – and once I figured out that is should be extracted to ‘cyanouya’ all was good. Also, for us copy/paste code people, it would be good if pushing the file to download folder reflected that.

    – I could not initially get su access. I googled and read that root access by default is only set to apps. By changing that in developer options to apps and adb, it granted me access and everything was perfect from there.

    Thanks again for everything you do. The fix works perfectly and is really easy to do, despite my newbie stumbles.

    Cheers

    • Hello!

      First off, I apologize for all of the errors on the Kodi bug entry. I am glad you got it figured out and I totally agree with you.

      1. All references to C:\cyanogen are gone. It’s synced to C:\cyanouya just like this blog entry. I want each guide to be as copy/paste friendly as possible as I am fully aware not everyone likes to hang out inside the ADB shell.:)

      2. I also added screenshots of “Apps and ADB” Root access to avoid the ‘su’ lockout that happens on stock CM11 loads. Thanks for that!

      The only thing I am having a hard time finding is the link with the lack of “i”s in it. Usually WordPress warns me if i made a link to a 404 error. I’m just curious as to which link this is.

      Again, Thanks for checking everything! It’s always appreciated!

      – S

  25. Ha – must have been some ridiculous glitch on my end. I could have sworn the link you left in your post above mine led no where, but it’s perfectly linked. Please ignore that part.
    And thanks again for all you do. I would never be able to do anything like this without the great community: The people who write the code/scripts and, as importantly for me, people like you who take the time to make it possible for guys like me to do these things with your fantastic, easy to follow guides.
    Cheers

  26. Hi, thanks for the upgrade files and guide! I tried the upgrade as outlined in your guide using Windows XP. However I can’t find the driver to update FASTBOOT under the Device Manager.

    Everything went fine including pushing the 5 specified files on to the Ouya. I then rebooted the ADB Bootloader and proceeded to update the driver for FASTBOOT under Other Devices. I couldn’t get the driver folder to show any Android Bootloader Interface” to select.

    I used the same driver location that was used for ADB, for FASTBOOT (C:\cyanouya\driver). However no FASTBOOT driver is found.

    Can this be a driver problem with Windows XP, or am I doing something wrong?

    Thanks
    G

    • It’s not your fault. I never tested this under XP until today. Apparently Windows XP isn’t as nice about letting you choose whatever driver you feel like for FASTBOOT like windows 7, 8, and 10 are. I have modified the android_winusb.inf which you can download here and extract this file into your C:\cyanouya\drivers\ folder . It includes Fastboot underneath hardware ID USB\VID_0955&PID_7000 into both 32-bit and 64-bit installations and XP will then accept this driver naturally. This will be merged with the cyanouya.zip file in a few days.

      the code I added to android_winusb.inf is as follows in case you want to open up notepad++ and read along or if you wish to make the mods yourself:

      Line 63 for x86:

      %SingleBootLoaderInterface% = USB_Install, USB\VID_0955&PID_7000

      Line 103 for x64:

      %SingleBootLoaderInterface% = USB_Install, USB\VID_0955&PID_7000

      Thanks for letting me know about this bug in windows XP!
      -S

      • Success! The updated android_winusb.ini file that you have linked above in your reply worked flawlessly with my Windows XP 32 bit system. The whole upgrade is now complete.

        P.S. I wouldn’t say that the omission of support for Windows XP (that is now about 15 years old) is a bug on your part though. I guess that I should plan to upgrade to a newer computer with Win 10 or something, or get left behind in the dust!

        Thanks a bunch.
        Gary

        • Great to hear! And as for XP, modifying the .inf file will help out windows 7 – 10 people as well as it will now suggest a driver to use rather then letting the user pick. So it’ll help all around.

          Have fun with your modded Ouya!
          -S

  27. INSTALLED LOLLIPOP (still beta)

    Just want to share that using this fantastic “How-To”, I managed to get AOSP (Lollipop) installed on my Ouya.

    I had to make one tweak to correct controller mapping and it works fine! lollipop on Ouya.

    One problem I have noticed is that the video seems to not be detected once I change the source on my TV. For example, if my source is on HDMI for Ouya to display at boot-up and then I change to TV and then back to HDMI, my Ouya then displays a black screen. This could be related to my TV being 720HD and Ouya supporting 1080p and not detecting my video output.

    i found Ouya Lollipop image in XDA (http://forum.xda-developers.com/ouya/development/rom-aosp-5-0-ouya-t2970753)
    the files are named:

    aosp-lp-ouya-LRX22C-1.0.zip
    gapps-kk-20140105.zip

    Hope this helps everyone who is interested in exploring Lollipop. BTW, I could not get GoogleTV working. (I didn’t try too hard but would be interested to hear from others.

    Thank you all

      • Don’t have sound issues.

        Installed isenguard and recently, Jarvis. With no studdering. Not too sure of bugs in Jarvis so I’ll look for that.

        No problems other that what I previously described.

        Once you have clockwork and bootmenu installed, you can change the image to lollipop easily.

        I notice on the link I provided that there have been additional comments added. I can’t say much about that for now.

          • Would you guys say it’s worth installing Lollipop/CyanogenMod 13 rather than CyanogenMod 11?

            I’d like to futureproof my Ouya (still running Ouya firmware) as much as possible in order to keep running the latest versions of Kodi, but I wonder if 13 will be much less stable than 11…

            I’m a bit of an amateur, but this guide looks perfect. Thank you for all the hard work!

  28. To answer my previous question concerning the white screen issue. I used another power supply and problem was solved.

  29. Please help. I’ve never done anything like this so please bear with me.
    I’ve done the first part of the guide no problems, however nothing works with command prompts, it keeps saying it can’t find the path? Any ideas?

    • A little more information is required. Which command are you getting stuck on?

      Are you getting “system cannot find the path specified” error when you cd to cyanouya? Where did you extract the cyanouya.zip file to?

      • Sorry I only just saw your reply
        I’ve got past this problem now I did indeed have my path wrong
        Now I’ve progressed a little but I’m having an issue in that adb wont see my device
        I’m currently installing sdk? As I’ve been googling the issue and this seems to be recommended?
        Many thanks

      • after entering echo 0x2836 >> “%USERPROFILE%\.android\adb_usb.ini” in command once doing adb kill-servers I get the system cannot find the path specified? I did everything as followed in your video. I am on Windows 10, any help asap would be awesome. Thanks EDIT also just did adb devices command and nothing comes up in the list? am I suppose to have sdk installed? I only installed the driver from your video that was provided.

        • do the following:

          mkdir %USERPROFILE%\.android\

          then echo 0x2836 >> “%USERPROFILE%\.android\adb_usb.ini and it should create adb_usb.ini into the hidden .android folder underneath your user profile.

          without adb_usb.ini in its respective folder. adb has no idea what vendor hardware ID to look for in device manager to map to.

          apologies for that. I’ll amend a directory creation string into the tutorial.

          Also, You can install the Android SDK if you want. Just so long as you use your SDK’s adb.exe and fastboot.exe files that the SDK inserts.. The SDK sometimes fails if you mix different versions of the files together.

          • Thanks for the quick reply ^_^ (Just seen the rest of the post and missed your sdk comment XD SCRATCH OUT->) also do I need sdk to be installed, or will everything work with out it?

          • Everything in the Cyanogen.zip works without the need of the SDK.. I tried to package it up in a way where users which just want to mod/hack their ouya have everything they need without download 1.2gb worth of files they don’t.

            Let me know if it works out for you and thanks for checking out my blog!:)

          • I’m having a similar problem using a Windows 10 laptop: can’t get the Ouya to show up as a device. Almost certain it’s not the cable.

            Made the appropriate updates to ‘android_winusb’ in C:\Users\[name]\AppData\Local\Android\sdk\extras\google\usb_driver and the appropriate updates to ‘adb_usb’ in C:\Users\[name]\.android

            Can’t get echo to work… Ouya, which is factory resetted, simply won’t show up. Any ideas?

          • Hello again!

            Since this is becoming a habitual problem. I reloaded one of my test station with windows 10. And let it get the latest updates for it. And found something kind of disturbing on what Microsoft has done.

            After the last build update in 64-bit you will no longer find your Ouya ADB underneath “Unknown Devices” like it used to be under stock windows 10 or windows 7. But now it exists underneath the “Universal Serial Bus Devices” catagory. Microsoft essentially got enough Ouya vendor ID reports back to the point where microsoft ADB driver. Yes, even though Microsoft has not made a binary of adb to go with said ADB driver they decided to make an ‘official driver’ to simply stop the Ouya vendor ID from filling up their logs as a unknown device windows 10 is compatible with. Kind of a dick move on Microsofts behalf.

            To make things worse. the Cyanogen driver is unsigned because I had to modify the .inf file which windows 10 considers that as a threat to the operating system (only windows 10 64, 32 bit it doesn’t give a damn about). Which means in order for you to install your driver you have to place your windows box into driver test mode. the commands are easy, just open up CMD and type the following:

            bcdedit -set loadoptions DISABLE_INTEGRITY_CHECKS
            bcdedit -set TESTSIGNING ON
            shutdown /r

            Your windows will then restart into test mode. FINALLY you can proceed with replacing the Microsoft ADB driver with the Android ADB Driver.

            After you push your files and fastboot to CWM you can unplug the Ouya from your laptop and pass the following commands:

            bcdedit -set loadoptions ENABLE_INTEGRITY_CHECKS
            bcdedit -set TESTSIGNING OFF
            shutdown /r

            To back out of test mode in windows 10 and restore your OS to its “protected” state. As a note when you back out of test mode hooking the ADB cable will no longer work once again but that’s okay because from here on out you can simply use ADB network connectivity if you wish to push or install APK’s to Cyanogen.

            Anyhow, this is what I found on my test PC running windows 10 . Let me know if it’s the same for you and I’ll begin looking for answers or amending a blog to deal with this problem.

          • Great stuff, S-Config! I didn’t have to go to these lengths (W10 seemed to be a lot more cooperative when I resumed a day later) but I’m sure it’ll help many W10 users in future.

            Thanks again!

  30. Looking all over for the fix concerning playback controls. Can’t Stop or exit out of video during playback in Jarvis. Anyone have a fix?

  31. I’m at my wits end lol
    I’ve done everything that’s in this guide and tried a million other things and adb simply will not see the ouya. Can anyone help?

    • ADB connectivity is the hardest part about this tutorial because it relies on a lot of different environments such as OS, type of cable your using, installation of the driver, and finally installation of the connector file between ADB and your device manager. if any of those steps fail then a USB ADB connection will fail.

      You mentioned in your last post that you were going to install the Android SDK.. Understand that executable from different versions of the SDK (i.e. the one I used versus the one you may be downloading) will not talk nice to each other. As an example, if you installed the SDK drivers versus the ones I have provided then you will need to use adb from C:\android\platform-tools\adb.exe instead of my C:\cyanouya\adb.exe . Also, the SDK is expecting a smart phone ADB device to be hooked up. and requires modification to the android_winusb.inf file in order for it to see your Ouya via the SDK’s drivers.

      I’m going to assume that you have already checked your device manager and that your device is not showing up as “unknown device” or the android bridge connector has a yellow exclamation mark by it. Because if it is showing up as “unknown device” instead of something like “OUYA” if uninstalled or “android device bridge” installed then you may actually have an issue with your data cable.

      You already added the echo command to generate the “0x2836” text file android_usb.ini file . To verify this open up file explorer and for the path type in %userprofile%/.android/ if you get a folder not found or the folder has no files in it.. then just go to %userprofile% and create an “.android” folder. then inside that folder open up a text editor with the words 0x2836 and save as android_usb.ini .

      That android_usb.ini file is responsible for telling the ADB and fastboot executable where to look for the Ouya when it’s plugged into your computer. If missing ADB will show blank when you type in “adb devices”

  32. Thasks for the reply
    I have tried about 7 cables no difference
    The ouya shows a portable device
    I have no idea what a ini file is nothing shows as that
    I have something that displays as that but without the ini bit?
    I’m afraid I think that this is beyond me and I may just buy a raspberry pi
    The only reason that I wanna do this Is to run a slightly newerror version of kodi purely to add the context menu options
    Thank you for your time and patients but I truly think this is beyond me
    (Even tho I have degrees falling out of me lol)

    • Hi AGIS, I can sympathize with your frustrations. I did the upgrade using an old Windows XP laptop (32 bit) and it worked pretty much except for a small hitch. I installed the necessary files in the exact named folder as outlined in the guide. When I used the command prompt, I changed directory of the prompt until I was in the same directory as in the guide. Then when it came to execute commands in the command prompt, I copied (Ctrl C) the commands from the guide and pasted them (Ctrl V) into the command prompt window to run. That saved a lot of typing and avoided possible mistakes. I admit that my knowledge of the command prompt is limited and I have only used it for survival. The way I understand the use of the command prompt, first the system looks in the current directory for executables, etc. If those aren’t found there, only God knows where the system looks next. So that’s why I always make sure to run the command prompt from the same directory that the files are stored in.

      I only had trouble with my out-dated Windows XP in getting fastboot to run. S-Config helped me with that and I got through the rest of it. I also did the optional update at the end to get the OUya game controller buttons working properly..

      Overall, it was a bit of an adventure, but my silver Ouya box is now working very well without problems, running CM11.

      If you are having trouble, maybe you can try another computer and follow the instructions as exactly as possible, I am not sure if that could be some of your problems, but it is worth a retry. The Ouya (silver edition) is a sweet tv box after the upgrade.

      Good luck with your upgrade, and I as I mentioned, by knowledge of the Command Prompt is “limited to survival” only.

      G

    • Sorry to hear that it didn’t work out for you. But if you’re doing it showing at a portable device then you’re getting there because in your device manager the Ouya has the potential of showing up under unknown devices AND portable devices at the same time. This can be problematic as if different drivers such as ones from microsoft start interacting with the Ouya prematurely ADB will not work.

      I understand if you don’t wish to continue. And the Raspberry Pi especially the gen 3 version is a worthy media box as I own one myself (with a little playing around with the bluez driver you can even make the Ouya controller work with the Pi-3). Just make sure when you buy the Pi to get a good power supply and some heat-sinks for the CPU. Pi-3 gets hotter then any other Pi before it.

      If you wish to continue troubleshooting it at any time I’ll put some notes here in case you ever return to it.

      The object now to me seems that you may have multiple drivers messing with your PC and giving you a very hard time with ADB. The drivers for ADB are version specific. If you install a newer driver but use an older executable it simply does not work. So a device manager cleaning is in order. To verify right-click on your portable device in device manager. and click on the details tab. under the property drop down click hardware ID. If it says something like USB\VID_2836&PID_0010&REV_0232&MI_01 then that is defiantly the ADB port underneath another drive. You can then right-click and uninstall the driver. Check the box to delete the driver and then finally click on action and scan for hardware changes.. If “OUYA” comes back underneath unknown device again when you are back on track for installing the ADB part of this tutorial.

  33. thanks for the tutorial.
    I have two questions:
    I own 2 Ouya consoles, can “clone” the Ouya that es’ta with the CM11 to another console?
    CM11 installed following the guide this site , what do I install AndroidTV now?

  34. Dude, thank you so much for this walkthru. Everything worked perfectly for me. The only “hiccup” I had was that Bootloader Device was automatically recognized after installing the first driver…no second driver install was necessary. It threw me off for a few minutes trying to figure out why I didn’t have any “unrecognized” devices, but once I noticed the Bootloader device under Android it all made sense.

    Again, I can’t thank you enough for the step-by-step screenshots. I’ve made tutorials in the past and I can honestly say they take a ton of patience to do this thoroughly. Thank you very, very much!

    • No problem, thanks for letting me know about the hiccup in the bootloader device. I think that may have been a side effect caused by me fixing the android_winusb.inf to work with windows XP boxes as you don’t get the option to force a driver in XP. I’ll have to revise that part a little bit.

  35. Hello, thanks for that really good job.

    I have some questions:

    Can i still sleep and wake up the Ouya from the controller?

    How to shut down (not sleep) the console?

    If i use a combined USB keyboard/mouse only to do the initial configuration and then disconnect it i will get permanent touchpad functionality back after reset?

    Do i need to install Xposed, Mod Collection and/or MOGA pivot to use MOGA compatible games?

    Is possible to upgrade Cyanogen to new versions or nightly builds without repeating the whole proccess of ADB´ing and the rest?

    Thank you very much.

    • Hello, let me try to answer these questions here.

      1. The lack of sleep function is a known bug in cyanogen and you will not be able to wake your Ouya with the controller.

      2. You can go to google play and download quickboot. Very nice app. Allows you to soft boot, shut down or boot into recovery if necessary.

      3. You only need the keyboard for the CM11 install really if you want to retain functionality of your touchpad. When logging into Cyanogen for the first time you can use the TAB key to cycle through the menu options and arrow keys/enter once you get to the desktop to activate your Ouya Bluetooth.

      4. This I have not tested yet so I’m not entirely sure.

      5. Yes, reguardless if you are upgrading to the latest nightly from Milaq or if you with to participate in the android 5.0 beta builds on the XDK forums. You go into recovery and simply upload the next cm-11-version.zip file that you have and keylayouts.zip file for your joysticks. No need to install bootloader or google play as those are already installed. Also, only clear the cache as clearing dalvik and factory reset will mean entering login data again, on reboot it will state that it is optimizing all apps installed and you will be back to your desktop.

      • Thank you for the answers.

        Googling around i´ve found a really big concern so need to ask another question:

        Under Cyanogenmod can i directly install or move games from flash to an external mass storage USB?

        Many websites states that KitKat restricts access to external memory eliminating the “move to SD” option, and due to the fact that i mostly use my OUYA to play sideloaded games this could be a trouble because OUYA´s internal memory is too small.

        Any hints?

    • If I had to guess it’s not because of root access as much as it is that “ADB shell screencap” has not been implemented in the milaq build of CM11 which teamviewer uses to transmit the screen itself to the clilent.

  36. What a fantastic tutorial. With no experience it worked first time. Well done.
    I’m very impressed after changing out the ouya stock OS for this cyanogen but of course there’s a question.
    I can get the cursor / pointer to appear in videos so I can rewind pause etc whether in a video app or kodi or YouTube. There is no pointer using either my air mouse or the ouya controller which paired fine.
    Any ideas how to get the mouse pointer tracker thing going so I can seek in movies?

  37. Ok, I’ve done the hardware overlay trick. Now though the airmouse is visible but does not interact with the playing movie so I can select lause rewind etc (the ouya controller allows me to click U and then dpad move to pause rewind etc. Any reason the air mouse isn’t interacting with the functions?
    Thanks.
    Ed

  38. The: fastboot boot recovery-clockwork-6.0.4.8-ouya.img command doesn’t for me

    When I run it says

    downloading ‘boot.img’…
    FAILED (command write failed (Unknown error))
    finished. total time: 5.012s

    What do I do?

    • Hrmm, this is the first time I’ve seen this error on an Ouya. I had this happen once with an android device LG phone a long time ago only to find out that I was accidentally mixing different driver versions between the ADB driver and fastboot driver. Are you using the fastboot drivers supplied from cyanouya or are you using drivers from the android SDK? also have you tried a different USB data cable just to be sure it’s nothing simple like that?

  39. i am currently having issues resolving my over scan issue, i am not sure what you mean by going to back into the adb shell or launching the app, i tried launching the app under the cyanogen folder that was extracted from the zip file i downloaded. Can you please provided a walk through as i am having major trouble with this. Other then that the walk through was great and everything works perfectly!

    • Thanks, I sort of put the overscan issue in there because people were having some problems with it. I can break it off into a seperate blog with video if it would help people.

      In the meantime. What I mean by going back into ADB is you can either do it via USB cable similar to how you modded Cyanogen in the first place and typing “ADB Shell” to get into your Ouya.

      Or, there’s a app on your Cyanogen that’s simply called “Terminal” which if you have a keyboard attached to cyanogen it is identical to typing ADB shell from a computer.

      after passing the commands a reboot is necessary and the new overscan values will take effect.

  40. Its great, instructions are very well mentioned and it worked for me fine. One thing I noticed is that “Settings” just doesnt work anymore. If I reboot the box and immediately click on settings, then it opens, when I come out of settings, then try…its just a blank black screen. Then I have to come out of it pressing home button on Ouya controller. Any suggestions?

    • That’s a weird one. Out of all of the times I flashed and reflashed I never had the system menu glitch out that way before. The system app is integrated with the package library with cyanogen. So legitimately if you clear cache, factory reset, and clear dalvik there should be nothing left of the old operating system for the system settings APK to get confused on.

  41. Wow! you move through the steps so fast I have a difficult time keeping up.

    When I attempt to fastboot the clockwork recovery boot img I get

    C:\cyanouya>fastboot boot recovery-clockwork-6.0.4.8-ouya.img
    downloading ‘boot.img’…
    FAILED (command write failed (Unknown error))
    finished. total time: 5.027s

    The image in the folder says its corrupt. Any ideas what I might be doing wrong?

    • There was another commentator about a month back which had a similar problem. The only thing he responded with was “He had to redo some steps” didn’t really explain anything beyond that. I never experienced this problem myself which I tested on windows XP, 7, and finally 10. But I did some research on it a month ago and came up with the possibility of version differences between the ADB.exe and the android device bridge driver which could be why reloading the android driver did the trick for him. Some people experienced this if they loaded the entire android-SDK package while using the .exe’s in my zip file. I wish I could pin it down on what it is.

      And apologies for the speed of the video. On the first take I moved slow and felt like I was putting people to sleep. I went faster thinking people can simply hit pause or index back on the video.

  42. I loved how easy this tutorial was to follow. Had a bit of an overscan issue but my TV had an option to adjust for that.

    Since install CM11 on the OUYA, I’ve noticed that my 1080p MKV files are not making the CPU run at 100%. I’m currently running SPMC 16.3. Now I don’t know if anyone else had this issue but it is extremely frustrating since when running the original OUYA OS I didn’t seem to have this problem. I’m currently installing Kodi from the google play store and see if perhaps it runs better but I am curious to see if anyone else had this issue and if so what they did to fix it.

  43. Hi S-config, I would just like to say that I stumbled across your guide yesterday and was quite excited that I may have a way to give my Ouya a new lease on life. Well I completed your steps last night and I have to say it was one of the easiest guides I have followed, mind you I have already flashed tablets and phones many times before so the drivers were already installed making things quite a bit easier.

    Thanks again for taking the time to do this, when I get home from work tonight I will be installing Kodi and testing that out but already the Ouya is working very well, I will now have to flash my parents and a mates Ouya as well once they hear about this.

    Cheers

    Quazza :D

    • Glad to hear it! I had to flash my parents and friends Ouyas as well so they can keep using theirs as well.

      Thanks for the input and checking out my blog. It’s always appreciated!

      – S

  44. Hi Again S-Config, I have been playing around with Kodi and have noticed that the OUYA controller ‘U’ Button doesn’t seem to bring up info within a movie. Is there a way to remap the Keylayouts to more effectively mimic the Kodi remote ? Also one other question I was wondering if there was a plan to maybe move to Cyanogen 12 or 13 and if that was at all possible.

    Cheers

    Quazza :D

    • Hello Quazza,

      About Kodi, have you already applied the patch to disable HW overlay? A sure-fire way of finding out it’s a HW overlay problem is play an AVI file through Kodi which will only use the CPU and not the GPU. If the OSD pulls up fine via the U button but if you play an MP4 file it doesn’t then it’s a glitch between CM11 and Kodi.

      As for CM12/13 . development on XDA sort of stalled out on the beta of CM12.1. There’s an ASOP 5.0 rom that looks like beta-testing is in progress which appears promising so I might give that a shot and upgrade one of my CM11 Ouyas to see the good/bad in it.. So not entirely sure if we’ll get a stable CM12 for Ouya. Thinking about it technically CM11 isn’t what you call %100 either but at least it’s stable!:)

      – S

    • Thanks for the awesome guide. Everything went like clockwork. CM11 is great and can now run Kodi JARVIS. I’ve heard that Krypton uses Android version 5. I hope you will have a guide for upgrading to android 5 in the future before Jarvis support stops.
      Thanks again.

      • I did try the alpha 1 build of Krypton on Ouya CM11 and besides some random scripting errors which is to be expected in alpha it did play videos and music alright. But it’s understandable that when they go to compile the final APK they untick the 4.2 box from compilation since the staff for each platform is running a bit low on Kodi under “Call out to developers” paragraph. It’s far easier to chase bugs on just one baseline android platform then multiple.

        I will probably be playing with ASOP 5.0 on the XDK forums as that image seems to be the most mature out of the android 5.0 images for Ouya. People were complaining their ouya controllers not working with ASOP 5.0 but my guess is like getting Ouya Everywhere working on the Kindle Fire android 5.0 really hates it if you define multiple key-presses in the .kl file which then it will totally ignore the custom .kl and default to a generic.kl file.

        Either way, I want to get more Accustomed to ASOP 5.0 before pushing the tutorial. Don’t want to be handing people any wrong info.:)

  45. Hi S-Config,

    Yeah I have already been playing movies etc and it is working fine as far as overlay goes, just that the buttons don’t really seem to work as they do in Kodi on standard Ouya, although I have had the U button work a couple of times so I’m not sure why that is. I might try the PS3 controller and see what happens there.

    Understand on the CM12 / 13, it would just be pretty awesome if we were able to use CM13 Android 6 on the OUYA, mind you I am over the moon that we even have CM11 so don’t think I am complaining as that is not the case.

    Cheers and thanks again

    Quazza

  46. I have gotten as far as: Pass the Fastboot commands to your Ouya. At this point it doesnt recognize fastboot devices. I have tried to back up a few steps I have tried to move forward with no luck. It just isnt seeing it. Please help! I am stuck mid install.

    • If the last command you typed was

      adb reboot bootloader

      Then all you have to do is power off your ouya and power it back on and it will boot back to its original OS as nothing has been written to the Ouya if you can’t get fastboot going.

      Under your device manager. Is the device not showing up under “Fastboot” but instead it’s showing as an “Unknown Device”? If this is the case then there may be an issue with the USB data cable that you are using. Ironically enough I had one of my Ouyas throw an unknown device when I tried to use a GameStik data cable on it. Since there was too much resistance on the cable it couldn’t detect the device and simply showed as an “Unknown” in device manager.

      Also what OS are you using just so I can get an idea as to what is going on here?

  47. Hi, I have gotten to the point of installing CyanogenMod, but i always get this error after it says Installing Update

    set_metadata_recursive: some changes failed
    E: Error in /tmp/update.zip
    (Status 7)
    Update Aborted

    Now i know status 7 means it isnt compatible with the device, but i have a retail ouya, this shouldnt be happening. Any help would be appreciated.

      • Only issues I’ve found so far:
        -Cannot pull down status bar in full screen apps. I thought this was enable in KitKat? I tried installing a status bar pull down app from play store but to no avail. Could this be fixed in a later version of CM? Are later versions of CM even compatible with the Ouya?
        -Cannot get a location set. I tried using FakeGPS(really don’t want to have to do that…) but google play store still doesn’t know where I am and won’t allow me to download certain apps (specifically amazon prime video which I have on my phone and PS3)…

  48. This guide is awesome! thanks a lot for that. I was looking to installing CM11 in my Ouya and thanks to this guide I did it!

    My only concern is the next: I am not very keen with the Ouya Controller (OC from now) and also I have an iPega 9037 that works perfectly so this is my main controller for games. The problem is that the OC is paired with the console just pressing the home button and I would like to do the same with my iPega. So to pair this one I have to go with the OC to settings-bluetooth-and pair it and it’s kinda annoying.

    There is any way to set up another remote controller to be found automatically for the Ouya as it does with it own remote control?

    Cheers!

  49. OK. Specifically, I wanted to set up certain full screen games to play on my ouya so I could see them better. Games like Star Wars Galaxy of Heroes or Arcane legends. Star wars works with the touch pad reasonable well and almost perfect with a mouse. But, Arcane Legends doesn’t work at all with the touchpad directional controller. I tried installing Tincore but cannot switch to it while in the game so I can’t assign the keys. Hence the previous question about pulling down the top panel while in a full-screen app. I’ve dug around on the interwebs and asked on XDA forums but to no avail yet… Any ideas?

  50. i got the 5 zip files over to my ouya’s /sdcard directory.
    Then the first zip file: recovery-clockwork-6.0.4.8-ouya.zip installed/updated just fine.
    On the next 2 zip files i get this error: “This package is for “ouya” devices: this is “ouya_1_1”. (status 7).
    I get this error with ouyabootmenu-mlq-v2.0.4.zip & the cm-11-20160312-NIGHTLY-ouya.zip.
    i stopped & did not try unzipping/installing the remaining 2 zip files.
    Any help to get past this error would be appreciated.

    • Wow. This is the first time I’ve heard of this. Usually if your device is OUYA_1_1 that means that you are still using a factory recovery mode (it looks like the ClockWorkMod screens on my site except it has a orange Ouya logo instead of the android robot). And I did try this on a clear dev, Retail, and Anthracite ouya and each time CWM did rename the device to “OUYA” and kept installing.

      If you are indeed in CWM and are still encountering this error. There is something you can try.

      In each of the zip files there’s a file in them called /META-INF/google/com/updater-script . This is what CWM looks at in terms of a batch file. The first thing it checks is it determines that it is on an Ouya device. This is because if someone tries this mod on a phone it might brick the thing.

      assert(getprop("ro.product.device") == "ouya" || getprop("ro.build.product") == "ouya"

      change to :

      assert(getprop("ro.product.device") == "ouya" || getprop("ro.build.product") == "ouya_1_1"

      and re-insert it into the zip file.

      recovery-clockworks script looks for both OUYA and Ouya_1_1 because it is assuming people are using factory recovery more-so then the fastboot technique as described on this blog. Which is why that installed but the others did not.

    • You don’t need a bluetooth keyboard at all for this tutorial if you don’t want to. Just a USB keyboard to go through the menus in CWM and do the initial setup in Cyanogen. After that you can pair your Ouya Joystick and then unplug the USB keyboard from the back of your Ouya.

      Thanks for checking out my blog!

  51. Hi, can someone confirm if its posible to move apps from internal storage to an external USB drive? I dont want to read movies, but to install games and aps. Thanks in advance.

  52. Can you please go into more detail for the overscan instruction. Specifically you mentioned to go back into adb shell how do I do that? I’ve gone through all your instructions and coming up with a blank. I know it is obvious but after working on this for 10 hours my mind is mush. Thank you so much for this tutorial. The overscan is the last issue I am working with (till the next tweak). The screen looks great!

    • You can go into adb shell if you want, or you can simply launch the ‘terminal’ app that CyanogenMod gives you and with a keyboard hooked up you can adb locally on your Ouya with that application.

      su
      setprop persist.sys.hdmi.overscan 1
      setprop persist.sys.hdmi.overscan.val 0.2
      reboot

      Going line by line:

      su – You need to give yourself superuser access or else it will ignore your setprop command upon reboot.
      setprop persist.sys.hdmi.overscan 1 – this will enable overscan in CM11
      setprop persist.sys.hdmi.overscan.val 0.2 – This is a variable command. ranging from 0.0 being minimum to 0.2 which is almost shrinks the image 80 percent on the screen.
      reboot – When you pass a setprop command it does not take effect until you reboot CM11.

      This is something I can’t really automate because all HDMI flat panel units can vary on how much over-scan that exists. These commands effect the CM11 OS directly for gaming and surfing the net. If you are using it for Kodi you can adjust the overscan at the application level in Kodi as well.

      Hope that helps!

      – S

  53. i have this error , i have try with two differentt cable
    C:\ouya>fastboot boot recovery-clockwork-6.0.4.8-ouya.img
    downloading ‘boot.img’…
    FAILED (command write failed (Unknown error))
    finished. total time: 5.012s

  54. ok i have found the problem adb_usb.ini was not empty
    i have another problem the keyboard on the screen do not type with ouya gamepad.
    i can navigate with ouya gamepad but i cannot type?
    and is it possible to configure in azerty mode?

    • I did upload an APK-Pack that you could use to make life after Ouya a bit simpler. inside of the APK pack is a apk called “Leanback_Keyboard_vL-1236599.apk” which after you install it and setup input preferences in the system settings it restores a virtual keyboard through your Ouya Controller.

  55. Hello! Thank you so much for the detailed process. I would have never been ale to do it without something like this. But once I’ve finished the process and i turn on my ouya i get the screen where it says normal mode. But then the screen goes black and there’s nothing!

    HELP!!!!

  56. I forgot to say something. When i put the command “adb devices” mine comes up as unauthorized. Then I’m unable to push the zip folders.

    Thanks

  57. Hello again! Thank you again got this tutorial! !!! Please ignore my previous comments. After trying again and again I’ve got it installed! Yayyy! But i got a 55′ Samsung and have terrible overscan. I do not understand how to fix this. Do i put the command prompts on the pc or on the ouya? Please clarify and give more details how to fix this.

    Thank you! !!

    • Hello and sorry about getting back so late here. I’m glad you were able to figure it out.

      Now about the overscan commands. These can be passed one of two ways. Either via the “ADB Shell” command if you are still hooked up to your ouya via PC. or if you have a keyboard hooked to your ouya, you can launch the ‘terminal’ application and it does the same thing as being in ADB shell.

      I say it like this because Cyanogen sort of opens doors of how to do things. But I can make a blog similar to the HW-overlay fix I did with Kodi+Cyanogen.

      hope it helps! and thanks for checking out my blog!

  58. Great guide, all went well – thanks for that!

    I would like to re-emphasize tha the USB keyboard needs to be plugged into the OUYA BEFORE rebooting into fastboot mode, or it won’t be detected.

    Also, with regards to volume, I only seem to have on or off – I can’t adjust volume other than to mute it. I’ve tried other volume control apps and widgets and it’s either full volume (15) or no volume (0)

    Cheers,
    OD

    • The volume is a common issue not just with Ouya but I’ve seen this problem on even some of the pre-built images for the various Pi’s we have had (Pine64 and Orange Pi specifically) HDMI audio controls underneath android 4.x is primitive at best.

      But glad it went well for you. have fun with your Ouya!

      • Is there a way to fix this? I have it connected to a HDMI LCD monitor, the volume controls built-in to the monitor don’t seem to work, it must be letting the HDMI device control it. At the moment my Ouya with CM is unusable due to this :)

        As a side note, not a big deal but would be nice to have working – the menu overlay when playing a video in Kodi doesn’t seem to work either. Is there a way to fix this?

        Is there a stable CM12 that works on Ouya?

        Cheers,
        OD

  59. Hi,

    I’ve tried the instruction given here above. However, when trying to fastboot (I seen the device in the device manager under “other devices” as expected), my W10 PC says it encountered an error trying to install the Android Bootloader Interface driver due to the fact the hash file is not present and so the driver may be corrupt of having being tampered with.

    Tried to rdo the adb push part, but still not better.

    Any hint ?

    • Glad you got it going. Apologies for removing your link. The driver site mentioned was throwing out some questionable .exe files.

  60. Please help! I’ve never done anything like this so please bear with me. I am stuck at this step:

    “Working with ADB to transfer data to your Ouya for Cyanogen mod upgrade.”

    When I type the “cd C: \cyanouya” within the command prompt I get the following:

    “the system cannot find the path specified”

    I am sure it is because I have unzipped the Cyanouya zip into it’s own folder. I did this because I was getting numerous errors when trying to unzip it into C. Where I have it located is: This PC\Downloads\OUYA.Cyanogen

    Running Windows 10

    Thanks so much for writing this!

    • I have figured out how to get beyond this step!!

      Now I am stuck again! I am thinking it may be a cord issue, but I am uncertain. With one cord, the OUYA will be recognized as “Android Device”. With the others that I have (5 in total) it is recognized as “Unknown USB Device (Device Discriptor Request Failed)” with error code 43 listed once I right click and click on properties.

  61. Hi,

    thank you very much for this great and funny to read instructions.

    Before I start installing the cyanogenmod on my ouya, I would like to backup all my data, like archivements, kodi profile, saved games etc.

    What is the best way to do this?

    Regards
    Marc

Leave a Comment