[HOWTO] adb / sideloading / superuser access

[sqkid89]

After rooting the ouya I resently connected it to my pc and it doesnt show up at all under device manager.

Update: I did a factory reset and ouya showed up under mobile device and other device and I was able to have it show up as android adb device but when I run this command
adb kill-server
echo 0x2836 >> "%USERPROFILE%\.android\adb_usb.ini"
adb start-server
adb devices
theres no number after adb devices

Update: got it working

What did you do to fix this? Having same result. Thanks!

 

[dh4645]

What did you do to fix this? Having same result. Thanks!

i think thats what mine originally did..when i went into the device manager, there were 2 listings for ouya and one had an exclamation sign of a missing driver (not the same one as mentioned in the instructions) so i updated the driver and then i got a device #

 

[sqkid89]

figured it out. since i have windows 8 64-bit (and amd processor?), had to add the same lines to NTamd64 in the inf file. also had to reboot and turn off driver signature. thanks for the help

 

[rossdret]

figured it out. since i have windows 8 64-bit (and amd processor?), had to add the same lines to NTamd64 in the inf file. also had to reboot and turn off driver signature. thanks for the help

Sent from my SPH-L720 using Tapatalk 2

How do you turn off the driver signature? And where did you find the ouya driver?

 

[nex86]

so I have a problem. I had just rooted and installed CWM on my OUYA yesterday. I was going to make a backup, but as I just finished installing CWM a friend walked in I haven't seen in years and wanted to play, so I didn't get around to the backup. I started messing with this, I plugged up to windows, connected to adb and everything was working fine, went through the first steps to setting up wireless adb, I got through

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

and I accidentally skipped the step to pull the build.prop and tried to run the service xxx.xxx.xxx:5555 whatever the IP is, and i of course got a failure so I went back and looked, and tried to pull the build.prop and it pretty much told me that my device was no longer connected. I exited, killed the adb server and tried to restart it, and no devices showed up. I turned my ouya on and off and it worked, I tried adb again, didn't work. then I rebooted the OUYA again, only to a black screen. adb is not connecting to my device, and my device is not loading on my TV. So I ran OUYA ToolBox by foil to see if there was anything I could do there, and when I pull it up, it shows my device connected at the bottom with the id that adb usually pulls up 015d8eb1855c060a. And to get the ToolBox working, I had to use your directions for modifying the adb_winusb.inf file before I could get it working because it needs to connect through adb. so SOMEHOW ToolBox is connecting through adb, but I cannot connect to adb through command prompt. Do you think running these few commands, doing the mount, remount, and chmod build.prop and do you think that running the code that I needed to edit (service ip:5555 as a command) could've bricked the device? That makes no sense to me, it would just seem that it would've failed. I don't know what's going on here. If you could help me with this it would really help. I don't know how to get in and do a factory reset because I can't pull up the screen and I can't factory reset through ToolBox. If you can help me it would save my day.

When you didn't change the permission of the build.prop, your Ouya is softbricked.
If you have no way to access ADB shell to fix the permissions you have to reflash the firmware.
Download the latest firmware here: https://ouyafw.skumler.net/

shutdown your Ouya, plug a USB keyboard on, boot it and hold down ALT+PRINT SC+I several times until you get into the recovery.
If you see the Ouya logo with an ! press home.
Flash the new Firmware via ADB in recovery, sideload the zip with "ADB sideload filename.zip"
If you have luck your Ouya might haven't lost all data.

 

[rossdret]

How did you update the driver? Im using win7 and I have searched high and low. I even installed the Samsung keis software as suggested in this thread but no luck.

Same issue with me...doesnt list any devices.

Sent from my SPH-L720 using Tapatalk 2

 

[TadeoNYC]

How did you update the driver? Im using win7 and I have searched high and low. I even installed the Samsung keis software as suggested in this thread but no luck.

Same issue with me...doesnt list any devices.

Sent from my SPH-L720 using Tapatalk 2

I accidentally discovered a great tool to cleanup and install as well as test adb drivers. http://forum.xda-developers.com/showthread.php?p=43869563

Sent from my Nexus 7 using Tapatalk 4 Beta

 

[rossdret]

I accidentally discovered a great tool to cleanup and install as well as test adb drivers. http://forum.xda-developers.com/showthread.php?p=43869563

Sent from my Nexus 7 using Tapatalk 4 Beta

You are the man!!!

Sent from my SPH-L720 using Tapatalk 2

 

[Petesky]

Should this work on Windows XP, I followed instructions in first post and I've got the usb driver installed but it just wont work , should I have usb debugging turned on , I've tried it on and off ,when its off I can see contents of ouya on my pc ,with it off it's looking for an mtp driver

 

[Midnitte]

Followed original OP directions, then tried universal + original + adding to AMD64 section (Using Windows 8 64 bit on AMD) plus disabling driver verification... still no work

 

[Ch4m3l30n]

Thanks for posting this concise information with which I was able to root my OUYA on the first try in less than 5 minutes using my Ubuntu Linux system.

 

[cnnxda]

i tried everything and when i finish the first part of the command. adb devices.. i dont get any sserial number. all i get is "device is listed" or something similar.

any help? i opened ouya toolbox and doesnt recognize the ouya.

i have already rooted it via the sideload method.

 

[elmerohueso]

Bumping this up as the newest OTA update breaks the oneclickroot app. OUYA rep says the update should still ship with terminal/ADB root access, like always, so manual method should still work (I don't have access to my OUYA to test, though).

 

[lscheres]

This does in fact still work for the new OTA... first time i had to do it this way, the new hotfix made all the buttons on my mele f10 pro stop working

 

[lscheres]

For some reason after the recent update i cant get root back even doing it manually. I have adb access and have busy box and super user installed on the ouya. Even uninstalled and reinstalled and restarted and still super user wont update the binarys..... I dont know what im doing wrong. Ive done this before a million times. Did anything change in the recent update???

 

[rah2501]

Link for busybox, superuser and su binaries no longer working.

HOW TO INSTALL BUSYBOX, SUPERUSER, AND SU BINARIES

...

2. Download and unzip the needed files here.

Unforunately this link no longer works. Does anybody have a copy of the file that this link used to go to?

Thanks.

Edit: For those who may come after me, I found an archive here that contains superuser.apk, busybox.apk and su binaries. Not tested yet though.