[HOWTO] adb / sideloading / superuser access

tcollum · May 10, 2013

Hey everyone! I put together some information on how to do a few things on your new Ouya! This info is by no means my own original contributions, but rather just a compilation of several different sources that I discovered through my quest to explore my Ouya. All credit goes to the original authors/brave experimenters.

SDK SETUP:

1. Install the Android SDK

2. Open SDK Manager and install the following packages:
- Tools: Including both Android SDK and Android SDK
- Android 4.1 (API 16): SDK Platform
- Android 4.0 (API 14): SDK Platform
- Extras: Android Support Library, Google USB Driver

3. Navigate to /android-sdk/extras/google/usb_driver

4. Open android_winusb.inf in an editor (I use Notepad++)

5. Add the following lines beneath [Google.NTx86]:

Code:

;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01

6. Connect your Ouya via micro USB to your computer and turn it on (it needs to be on for adb to work)

7. Open a command window in /android-sdk/platform-tools and run the following commands:

Code:

adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
adb devices

8. After 'adb devices' you should see a number, which signifies your connected console

9. You are now ready to use adb to sideload apps

=============================================================================================================

SIDELOADING APPS:

1. Place the desired .apk file to be installed within /android-sdk/platform-tools

2. Connect the Ouya and open a command window in /android-sdk/platform-tools and run the following command:

Code:

adb install [name.of.apk.file.here]

3. Wait for it to complete the installation

4. On the Ouya, navigate to 'Make' and 'Builds' and your app will be there

=============================================================================================================

ADDITIONAL STUFF BELOW

=============================================================================================================

HOW TO SET UP WIRELESS ADB (will allow you to wireless use adb command, without connecting directly to your computer)

1. Connect OUYA console via mini-usb (or using wireless adb) and run the following commands:

Code:

adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
chmod 666 /system/build.prop

2. Open another terminal (so we can do things locally) and run the following command:

Code:

adb pull /system/build.prop

3. Open build.prop in a text editor, add this line:

Code:

service.adb.tcp.port=5555

4. Return to the second command window and run the following command:

Code:

adb push build.prop /system

5. Now go back to your shell for the OUYA and run the following commands:

Code:

chmod 644 /system/build.prop

(seriously! the console won't boot if you forget this)

Code:

mount -o ro,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP

6. Disconnect your OUYA, put it where you want it, reboot it.

7. To wirelessly connect to your OUYA, use the following command:

Code:

adb connect 192.168.xxx.xxx

(your OUYA's ip address)

=============================================================================================================

HOW TO INSTALL BUSYBOX, SUPERUSER, AND SU BINARIES

1. Make sure you have ADB set up and working (wired or wireless).

2. Download and unzip the needed files here.

3. Place unzipped files in /android-sdk/platform-tools

4. Run the following commands to put su in the proper place:

Code:

adb shell
su
mount -o rw,remount -t ext4 /dev/block/platform/sdhci-tegra.3/by-name/APP
exit
exit
adb push su /sdcard/su
adb shell
su
cat /sdcard/su > /system/xbin/su
ln -s /system/xbin/su /system/bin/su
chmod 6755 /system/xbin/su
exit
exit

5. Install SuperUser and BusyBox:

Code:

adb install com.koushikdutta.superuser.apk
adb install stericson.busybox.apk

6. Run SuperUser on the Ouya (from Make > Software) and confirm the update (not in recovery).

=============================================================================================================

Again, this isn't my original content, only slightly edited (since I am OCD about writing).
My only intention is to share this knowledge with other users like me, who don't know much about this sort of thing (yet).

If i stepped on any toes, or did something wrong, I apologize. Let me know if you have any questions or concerns.

Thank you to the following people for their work in contributing to this guide:
WinDroidGuy
elmerohueso

cosine83 · May 10, 2013

The driver section doesn't seem to work on Windows 8 Pro 64-bit. I don't think the Google driver has been updated for Win8 yet.

tcollum · May 10, 2013

You're probably right. I'm on Windows 7. I'll see if I can jump on a buddy's computer to play around with it.

Upon a quick Google search, I found this: http://xdaforums.com/showthread.php?t=1161769

Perhaps give this a try? Please let me know how it goes.

cosine83 · May 10, 2013

I also tried Koush/ClockwordMod's universal ADB driver (adding in the Ouya section to 32/64) but same results about a bad hash in the driver file.

tcollum · May 10, 2013

Well it was worth a try. I'll keep my ears open for a Windows 8 solution.

Did you try setting up adb over wireless by any chance? I don't know much about this stuff, but perhaps that's worth a try as well?

TadeoNYC · May 14, 2013

cosine83 said:
The driver section doesn't seem to work on Windows 8 Pro 64-bit. I don't think the Google driver has been updated for Win8 yet.

My Ouya was listed twice in Device manager and one of them was a driver problem. I manually selected my Samsung adb drivers from the list and it works fine. the easiest way yo get those is to install KIES. This was with 64 bit Windows 7.

TIP: The micro usb port is extra deep and my samsung cables don't work, fortunately I have a Kodak one that does.

It motivated to set up wireless adb.

egandt · May 16, 2013

Not getting very far, first I downloaded the SDK, which will not run on my system, might be the AV/FW or something else, but it attempts to find java (which is in the path), and then it does nothing. So I try to go the ClockWorkMod way using the Universal driver (as I saw that should work), that is better as I at least have drivers and it finds my device, but it also will not install throwing a message: "hash for the file is not present in the specified catalog. The file is likely the corrupt or the victim of tampering." Well duh, I modified the inf to get it to find the hardware for the OYUA. I'd just use Google's if I could get a copy without installing the SDK since that is obviously not going to working on this system. Any suggestions, so far while adb works fine with the G3 on this system it appears impossible to setup for the OUYA.

Please note: in C:\Java\jdk1.7u21 is the JDK in c:\java\jre is the JRE. So they are both present and up to date. If I open a command prompt and type java -version it is located and works fine, so no understanding of what "SDK Manager.exe" is doing.

Also, yes I followed the thread as best I could, first copying java into c:\android makes no sense, but I tried it (did nothing), second the adb driver does not require any extraction, where is the usb driver, it must be in a zip somewhere in the SDK for it to be installable, so can I just manually extract it?

Thanks,
ERIC

TadeoNYC · May 16, 2013

egandt said:
Not getting very far, first I downloaded the SDK, which will not run on my system, might be the AV/FW or something else, but it attempts to find java (which is in the path), and then it does nothing. So I try to go the ClockWorkMod way using the Universal driver (as I saw that should work), that is better as I at least have drivers and it finds my device, but it also will not install throwing a message: "hash for the file is not present in the specified catalog. The file is likely the corrupt or the victim of tampering." Well duh, I modified the inf to get it to find the hardware for the OYUA. I'd just use Google's if I could get a copy without installing the SDK since that is obviously not going to working on this system. Any suggestions, so far while adb works fine with the G3 on this system it appears impossible to setup for the OUYA.

Please note: in C:\Java\jdk1.7u21 is the JDK in c:\java\jre is the JRE. So they are both present and up to date. If I open a command prompt and type java -version it is located and works fine, so no understanding of what "SDK Manager.exe" is doing.

Also, yes I followed the thread as best I could, first copying java into c:\android makes no sense, but I tried it (did nothing), second the adb driver does not require any extraction, where is the usb driver, it must be in a zip somewhere in the SDK for it to be installable, so can I just manually extract it?

Thanks,
ERIC

By G3 do you mean Galaxy S3? If so then hopefully you already have Kies installed. When I connected my OUYA and started all of this, it did not install properly. It showed up twice in device manager, it was installed as a portable device, but was also listed as "other device" and not installed. After a lot of searching,I saw that people had been able to get out working by manually selecting the Samsung adb drivers that are included with Kies. It worked for me. You need to manually select the drivers (have disk) and install OUYA as a MTP device.

Regarding the SDK I know nothing. It installed just fine on Windows 7 for me.

Good luck

Sent from my SCH-I535 using Tapatalk 2

eatmybiglazer · May 16, 2013

I was able to get ADB to work on Windows 7 64bit and Windows 8 64 bit by installing Samsung KIES and forcing it to use that driver.

egandt · May 18, 2013

eatmybiglazer said:
I was able to get ADB to work on Windows 7 64bit and Windows 8 64 bit by installing Samsung KIES and forcing it to use that driver.

Try this driver, got it to work, by selecting i from the list and forcing it

ERIC

FrostyWolf · May 24, 2013

Sideloading it relatively trivial for this. It is on by default (and can be toggled the usual way, you can access setting at manage->system->advanced-> security).

I used Real APK Leecher to snag ES File Explorer's APK, threw it on a web server, then downloaded it using OUYA's browser (make->software->browser). Installed it from settings (manage->system->advanced->storage->downloads)

The app then shows up under make->software

I have not tried a pen drive yet, but you could probably throw apks on a drive and use the USB port and install in a similar fashion.

tennisbgc · Jun 2, 2013

I'm trying to do step 7. I input C:\Android\sdk\platform-tools into comand promt but get not regognizable message. What am I doing wrong?

tcollum · Jun 2, 2013

You need to open the command prompt from wherever within platform-tools, or navigate to that folder from your command prompt. You can't run the adb command (which is located in platform-tools) unless your in that directory.

dh4645 · Jun 5, 2013

thanks. hopefully i'll get my OUYA soon. only 1 state away.

tennisbgc · Jun 7, 2013

I dont get a number after adb devices. I editited the google usb file. Im using the 64 version of android sdk is that ok?

dibblebill · Jun 9, 2013

@tcollum: Perhaps you should add this to the OP, I tested and it worked. You can add that ;Ouya to the amd64 section of the USB driver, too

dibblebill · Jun 10, 2013

FrostyWolf said:
Sideloading it relatively trivial for this. It is on by default (and can be toggled the usual way, you can access setting at manage->system->advanced-> security).

I used Real APK Leecher to snag ES File Explorer's APK, threw it on a web server, then downloaded it using OUYA's browser (make->software->browser). Installed it from settings (manage->system->advanced->storage->downloads)

The app then shows up under make->software

I have not tried a pen drive yet, but you could probably throw apks on a drive and use the USB port and install in a similar fashion.

I just find it easier to ADB over Network and install from my laptop.

Sent from my Nexus 10 using XDA Premium HD app

uncynd · Jun 10, 2013

TadeoNYC said:
My Ouya was listed twice in Device manager and one of them was a driver problem. I manually selected my Samsung adb drivers from the list and it works fine. the easiest way yo get those is to install KIES. This was with 64 bit Windows 7.

TIP: The micro usb port is extra deep and my samsung cables don't work, fortunately I have a Kodak one that does.

It motivated to set up wireless adb.

This was a great post...I did what you suggested and selected the latest Samsung ADB Interface driver in the windows list (think it was 23/1//2013) and voila. Thanks!

dibblebill · Jun 10, 2013

uncynd said:
This was a great post...I did what you suggested and selected the latest Samsung ADB Interface driver in the windows list (think it was 23/1//2013) and voila. Thanks!

You can also do the original USB driver edit in the OP and add it under the amd64 section in the inf file. Its how I did it.

uncynd · Jun 10, 2013

dibblebill said:
You can also do the original USB driver edit in the OP and add it under the amd64 section in the inf file. Its how I did it.

Ahh, did not see your post that would have been a lot faster, good advice and maybe should be added to OP?

[HOWTO] adb / sideloading / superuser access

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Member

Senior Member

Member

Similar threads

Top Liked Posts