Home > tech foo > Root Access on Ouya

Root Access on Ouya

Today I received my Ouya. For the ones who don’t know what an Ouya is, check out this link. The Ouya device has already the ‘su’ binary installed, so there is no actual ‘rooting’ necessary. But in order to get root access you still have to take some things into account.

ADB (Android Debug Bridge)
First we need a copy of ADB (Android Debug Bridge). ADB ist part of the Android SDK, which can be downloaded from here. Download the package according to your OS. On Linux just do the following steps

$ wget http://dl.google.com/android/adt/adt-bundle-linux-x86-20130522.zip
$ unzip adt-bundle-linux-x86-20130522.zip
$ cd adt-bundle-linux-x86-20130522/sdk/platform-tools
$ sudo cp adb /usr/local/bin

The ADB binary is self contained, so it can just be copied to somewhere else (e.g. /usr/local/bin).

adb_usb.ini
The second thing we need is an entry for the Ouya in our usb devices list. First we need to connect the Ouya to our PC with a micro-usb/usb-cable. Then call

$ dmesg

The output should look something like the following

[289053.442387] usb 1-1.5.6: new high-speed USB device number 25 using ehci_hcd
[289053.564585] usb 1-1.5.6: New USB device found, idVendor=2836, idProduct=0010
[289053.564595] usb 1-1.5.6: New USB device strings: Mfr=2, Product=3, SerialNumber=4
[289053.564601] usb 1-1.5.6: Product: OUYA
[289053.564606] usb 1-1.5.6: Manufacturer: OUYA
[289053.564610] usb 1-1.5.6: SerialNumber: 00000000000000

If you haven’t upgraded the Ouya’s firmware yet the vendor ID (idVendor) might be different. If you have installed the latest firmware the ID should be ‘2836’, like the one from above. Now we have to add the vendor ID to our ‘adb_usb.ini’. Just do the following steps to add the device

cd ~
mkdir .android
echo “0x2836” >> ~/.android/adb_usb.ini

It is important to add a ‘0x’ in front of the actual number (its hexadecimal).

Connecting to the Ouya
Now we should be able to connect to our Ouya using ADB

$ sudo killall adb
$ sudo adb devices

The ‘devices’ command should list the Ouya

List of devices attached
00000000000000        device

If it does not list your device make sure to kill all ADB instances on your machine, and the start ADB (with ‘sudo’) again.

sudo killall adb
ps -e | grep adb

The second command shouldn’t output anything. If it lists

 6680 pts/1 00:00:00 adb
15926 ?      00:01:31 adb

then there are still instances of ADB running.

When everything is cleaned up, and the ‘adb devices’ lists our Ouya we can connect to it using

$ sudo adb shell

This gives us a shell on the Ouya (we can even be super user).

Advertisements
Categories: tech foo Tags: , ,
  1. Carsten
    July 13, 2013 at 6:19 pm

    Thanks. This was the missing link for me to access my Ouya.

  2. July 27, 2013 at 2:36 pm

    This guide is great but you seriously need to change the ‘×’ to an ‘x’ and the quote marks into actual quote marks. Simply doesn’t work the way they are right now.

    Thanks 🙂

  3. chet
    July 28, 2013 at 5:29 pm

    HHmmm I can’t see the Ouya in adb. I tried both those extra commands at the end and nada. Does it make a difference if I’m running Ubuntu x64?

  4. chet
    July 28, 2013 at 7:04 pm

    Yep get the adt-bundle-linux-x86_64-20130717 zip followed the steps, and same thing. I can see the device in dmesg, but it can’t find it. I can get it to work in Windows, but not in Ubuntu (my OS of choice)

  5. July 29, 2013 at 8:21 am

    If you haven’t updated the firmware of the Ouya yet, you might have a different vendorID. When you run ‘dmesg’, have you checked that the id is really ‘0x2836’, or is it something different. If it is different then you have to add the given ID to your ‘adb_usb.ini’ file.

    • chet
      July 30, 2013 at 12:32 am

      Yep mines still 2836, I checked that. Still no go. Guess I’ll just have to switch to Windows to use adb. Anyone know if there’s a ftp app that you can use with ethernet? Right now I’m using Airdroid, but transferring via wifi is SLOW!

  6. July 29, 2013 at 8:21 am

    @Farran: Yeah, thank you, I think that’s a problem with the “quote”-tags of WordPress, I try to fix this.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s

%d bloggers like this: