[Q] OUYA_1_1 Driver????

G

GarbageGamer

Member
Jul 16, 2013
12
0
0
Jul 16, 2013 at 2:08 PM
I am trying to run CWM recovery to backup my OUYA OS. When i go to fastboot the .img, the command prompt says everything was fine but I have a black screen with my PC detecting a new device called OUYA_1_1 and its asking for drivers.

I have looked all over the Forums and Google and saw people talking about it but no one addressed the issue.

is there a driver i am missing or something i need to add to the android_winusb.inf file?


Many thanks in advanced :D
 
ElMeteK

ElMeteK

Member
May 9, 2013
12
1
0
Jul 16, 2013 at 3:00 PM
GarbageGamer said:
I am trying to run CWM recovery to backup my OUYA OS. When i go to fastboot the .img, the command prompt says everything was fine but I have a black screen with my PC detecting a new device called OUYA_1_1 and its asking for drivers.

I have looked all over the Forums and Google and saw people talking about it but no one addressed the issue.

is there a driver i am missing or something i need to add to the android_winusb.inf file?


Many thanks in advanced :D
Click to expand...
When you are asked for a driver go to find it on your computer.

Then go to your android sdk install folder.

Then extras.

Then google

and then usb_driver.

and stay in this folder for your driver, don't search further on AMD64 or i386.

Have you modified the android_winusb.inf ?
 
G

GarbageGamer

Member
Jul 16, 2013
12
0
0
Jul 16, 2013 at 3:15 PM
ElMeteK said:
When you are asked for a driver go to find it on your computer.

Then go to your android sdk install folder.

Then extras.

Then google

and then usb_driver.

and stay in this folder for your driver, don't search further on AMD64 or i386.

Have you modified the android_winusb.inf ?
Click to expand...

I tried what you said and it did not work :( . Yes i have modified it based on the tutorials adding the following


[Google.NTx86]

;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01

;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
Click to expand...
 
G

GarbageGamer

Member
Jul 16, 2013
12
0
0
Jul 17, 2013 at 12:44 AM
Lastcaress09 said:
try the test version of the OUYATOOLBOX, some people were having an issue with the actual releases...
try adding the OUYA code to the X64(I think thats what its called) part of the winsub. Also are you X64 bit system? if so try this code, if your system is stuck in recovery...http://forum.xda-developers.com/showthread.php?t=2352658
i had that issue when stuck in recovery and system as seen as a MTP USB device..
Click to expand...
Went back and tried the test version of OUYATOOLBOX and tried the link both did not work :(, What am i missing ???? is it because im on windows 7 x64? everything els works except CWM recovery


:crying:
 
T

TadeoNYC

Senior Member
May 9, 2013
281
50
0
New York
Jul 18, 2013 at 4:48 AM
GarbageGamer said:
it's telling me there are no drivers at all, but yes
Click to expand...
I have had nothing but problems with setting up OUYA drivers on two different Windows 7 home premium 64 bit systems. Two months ago on my laptop after the SDK drivers didn't work I was able to use Samsung adb drivers. I have a new to me Acer PC that I am using as a htpc. It's a new install and I tried the Samsung drivers again, but it changed the device name to Samsung mobile phone. After hours of system restores and multiple driver configuration attempts, I finally got the SDK drivers to work by adding

;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01

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

To both [Google.NTx86] and the amd64 section,
BUT no matter what I do it still changes the device name. Now it says something like adb composite device, but the OUYA toolbox test version got everything installed. I only needed su and CWM, my existing supersu and BusyBox updated perfectly.
 
D

DrROBschiz

Senior Member
Sep 21, 2011
170
17
0
Jul 18, 2013 at 5:55 PM
Yeah

Me and Garbage Gamer are basically in the exact same position

Whatever we did wrong... its preventing us from pushing the boot img with fastboot
 
G

GarbageGamer

Member
Jul 16, 2013
12
0
0
Jul 19, 2013 at 1:51 AM
I DID IT !!!!!!! i am currently doing a backup as we speak, only problem is i am not sure what i did differently except switch to my laptop to start fresh. I loaded the android SDK and made the changes based on the tutorial except the only thing is i did the recovery install and fast boot using the OUYA Tool kit. it still came up with the device looking for drivers but it let me install recovery and make a backup which is all i needed. i am so happy lol but sad as i wish i knew what i did wrong initially :(, my best advice would be to start fresh on a new PC if you can
 
A

ArdDarvis

Member
Jul 4, 2013
47
9
0
NE ohio
Jul 19, 2013 at 6:15 AM
CMW and stock recovery both reassign the device different hardware ids. so, yes, in normal operation it is pid_7100&Mi_01, but put it in recovery (of any kind) then right click the device in the device manager, then go to details (xp, sorry) and the hardware id will be different.

you have to get the hardware id for ouya_1_1 and put it in where you would put pid_7100&Mi_01, then direct the device to the driver. then echo the driver again in terminal.

hope that helps. i can try to explain it a different way if you're unsure.
 
I

iAmSmokey

Member
Jul 6, 2013
6
2
0
Jul 19, 2013 at 7:42 PM
incase you didnt try the link Lastcaress09 posted earlier (its irrelevant if your on a x64 or x86 OS, the procedure is the same):

\/ propably the solution \/

ArdDarvis said:
CMW and stock recovery both reassign the device different hardware ids. so, yes, in normal operation it is pid_7100&Mi_01, but put it in recovery (of any kind) then right click the device in the device manager, then go to details (xp, sorry) and the hardware id will be different.

you have to get the hardware id for ouya_1_1 and put it in where you would put pid_7100&Mi_01, then direct the device to the driver. then echo the driver again in terminal.

hope that helps. i can try to explain it a different way if you're unsure.
Click to expand...
\/ tutorial \/

iAmSmokey said:
UPDATE
solved it by trial & error. what happened:
apparently my (any?) ouya changes its hardware id after going into recovery, so i had to reinstall the driver IN recovery mode:
its basically the driver installation procedure
(google "setup instructions for the ouya odk" for a text or "ouya on windows driver setup" for a video tutorial)
with a slight change, instead of pasting:

Code: 
;OUYA Console
%SingleAdbInterface%        = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface%     = USB_Install, USB\VID_2836&PID_0010&MI_01
into the android_winusb.inf, open your hardware monitor and check your ouya's hardware id
(right click on the device->properties->details->and select hardware id's from the dropdown menu,
you need the one WITHOUT "REV_xxxx" in it)
and replace your id with the one in the "%CompositeAdbInterface%" line above, in my excample it now looks like this:

Code: 
;OUYA Console
%SingleAdbInterface%        = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface%     = USB_Install, [B]USB\VID_18D1&PID_D001[/B]
now you should be able to continue the driver installation.
Click to expand...
if that didnt help or you have a problem with the procedure, report back or ask.
also: in case you come up with a different solution, post it, somebody WILL have the same problem sooner or later.
 
  • Like
Reactions: ArdDarvis
A

ArdDarvis

Member
Jul 4, 2013
47
9
0
NE ohio
Jul 19, 2013 at 7:57 PM
Smokey! i looked for your link, but apparently i didn't look very hard. thanks for stepping in and finishing what i started.

also, thanks for the write up.

because i HATE going and getting the ID, putting in the inf, directing the hardware to the driver, yada yada, i just seperated the 3 hardware IDs (normal oppuration, recovery mode/CWM recovey, and fastboot) with commas. it works well so far. maybe try it out.
 
  • Like
Reactions: iAmSmokey
I

iAmSmokey

Member
Jul 6, 2013
6
2
0
Jul 20, 2013 at 12:34 PM
glad i could help :)
your right! seperating the ID's with commas seems to work so far, but im not really experienced in all this developement stuff, i rarely even used the cmd before i got my ouya, so somebody else has to do further testing.
 
T

TadeoNYC

Senior Member
May 9, 2013
281
50
0
New York
Jul 23, 2013 at 4:13 PM
I just found a relatively simple way to get a clean install of the universal adb drivers. I bought a Nexus 7 on Friday and rooted it using the Nexus Root ToolKit from WugFresh.com (also on xda).

The tool kit has a driver install wizard that includes a program "abdevoid" to help find and remove all adb drivers before installing new ones. There are four different sets of drivers to choose from as well. I used this utility to root and install recovery on my Nexus, then rebooted the PC to be overly cautious. I connected the OUYA and it installed automatically. I ran the adb devices command to be sure it was there and then proceeded to install su binaries and recovery using the test version of Foil's toolkit.

This is on a Windows 7 64bit home premium that is a very new install, but has had a ridiculous amount of adb drivers installed, including those from Kies, CWM Helium, and the Android SDK. Device manager lists the drivers as unsigned Google drivers version 7.something for adv. I could see the Windows driver wizard opening at every step and it all went off without a hitch. I highly recommend this method.

Sent from my SCH-I535 using Tapatalk 4 Beta
 
  • Like
Reactions: blipsqueak
You must log in or register to reply here.

New posts

Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone