Develop Bugs

A: Fastboot doesnt see device

ok, I lost root and then fastboot wouldnt recognize my device because in the sdk there wasnt the galaxy nexus figured into the setup.inf file in the drivers folder. I typed this in between the ns4g and the nexus 7
;Google Galaxy Nexus
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4E30
%SingleBootLoaderInterface% = USB_Install, USB
\VID_18D1&PID_4E30&MI_01
%SingleBootLoaderInterface% = USB_Install, USB
\VID_18D1&PID_D001&REV_0216
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
%CompositeAdbInterface% = USB_Install, USB
\VID_04E8&PID_6860&REV_0216&MI_01
computer asked to restart...yes. upon reboot I went to device manager, uninstalled android 1.0 and did a hardware scan. BAM!! installed! went to fastboot, reflashed su and recovery...good to go!
make sure you look up your hardware id in device manager BEFORE you edit the file to make sure you type the correct numbers replacing the ones above if you have to!

Doesn't belong in Development. There is no development here this is just an FYI or a general "guide"
Sent From My Toro+ via RED Tapatalk

oh, I thought I was in general...

JediNinjafication said:
oh, I thought I was in general...
Click to expand...
Click to collapse
LOL its alright i reported it to be moved you should be fine.

I can't find anything when not using phone. I stare at xda screen on computer and am all..duh..where'd it go.. so excited to have root again!

[Q] cant sideload the ota in recovery

its pretty early in the morning and all i want to do is sleep, so i got to apologize for possible typos and lazy writing, and whats even worse is that im a complete noob on the android platform, so please bear with me. (hi, im the new guy btw)
anyways, i fu'd my "su" up by resetting after rooting and now i cant sideload the ota in recovery mode to fix it.
what i do:
get ouya into recovery (adb reboot recovery) and select "something something from adb"
(sorry, its really, REALLY early and i ran out of coffee)
the screen then gives me the message:
Now send the package you want to apply to the device with "adb sideload <filename>"...
and thats the point where im stuck, after typing "adb sideload RC-OUYA-1.0.346-r1_ota.zip" it just tells me: error: device not found.
i also tried "adb install RC-OUYA-1.0.346-r1_ota.zip" but that just gave me the same error with the message "- waiting for device -" below.
also adb doesnt recognize the ouya in recovery mode (adb devices gives me an empty list) but DOES recognize the console out of recovery.
i can also still boot it up and play with the settings, the only issue is that sometimes wifi just randomly refuses to work (and i dont have any games installed so i cant test that)
its not really important but,
what i did:
i sucessfully finished the [how to] adb sideloading superuser-access tutorial by ty collum (not the wireless part)
and then i tried booting CWM (the one click batch thing) which gave me the "OUYA!" screen (just like in recovery mode) so i made a factory reset, after which i couldnt access su anymore. (which again is why i want to sideload the ota, to start over.)
thats all i can think of for now, if someone needs more infos just ask, apologies again for being a little inconvenient, but im really tired.
sincerely smokey.
EDIT:
nobody has even the slightest clue what could cause this? drivers, missing librarys, a bug in the sdk, nothing?
just reinstalled windows 7 ultimate x64 (had to do it anyway) and going to retry the procedure now, reporting back once im done.

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]
EDIT
at this point you can simply continue the driver installation tutorial
Click to expand...
Click to collapse
after that proceed to sideload the ota via "adb sideload *filename*.zip"
also it now shows up in the "adb devices" list while in recovery mode (my ouya never showed up in recovery before)
greetings smokey.

THANKS!!!
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]
after that proceed to sideload the ota via "adb sideload *filename*.zip"
also it now shows up in the "adb devices" list while in recovery mode (my ouya never showed up in recovery before)
greetings smokey.
Click to expand...
Click to collapse
you are a legend, i was having the same issue with x64, i just did a system restore to back up right before I started all this jazz. through hours of researching, regarding how to reset my drivers from the MTP USB device, to click ALT+Sysrq+i for a solid half hour. this post with the the slight alter in code was the final touch to being able to sideload. my OUYA is now back up and running! THANKS!

You can also append the line, you don't have to replace it.
Like this:
Code:
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01
%CompositeAdbInterface% = USB_Install, [B]USB\VID_18D1&PID_D001
[/B]
Btw thanks mate!

[Q] Ouya Toolbox can't detect my ouya...

I finally got my Ouya. I installed the drivers following ouya's docs but when I run Ouya ToolBox, It can't detect my ouya Tried running as admin reinstalling drivers and restarting my pc but still nothing.
My goal is to install StockPlus rom for cifs support but I'm going out of my mind trying to detect it.
Am I forgetting something, anything I can do to fix this?
Regards,
Rick

Rick7C2 said:
I finally got my Ouya. I installed the drivers following ouya's docs but when I run Ouya ToolBox, It can't detect my ouya Tried running as admin reinstalling drivers and restarting my pc but still nothing.
My goal is to install StockPlus rom for cifs support but I'm going out of my mind trying to detect it.
Am I forgetting something, anything I can do to fix this?
Regards,
Rick
Click to expand...
Click to collapse
There's a "test" version, try it.

ElMeteK said:
There's a "test" version, try it.
Click to expand...
Click to collapse
I tried the test version and still a no go. I'm at a loss I have no idea what to do. I have never had a problem with my phones.

Rick7C2 said:
I tried the test version and still a no go. I'm at a loss I have no idea what to do. I have never had a problem with my phones.
Click to expand...
Click to collapse
Ok ToolBox 1.1.2 randomly started detecting my ouya I got it rooted...Now I'm trying to do the recovery however I don't have fastboot drivers and can't find them. OuyaToolBox said to use the same drivers as before but when I browse to that directory windows says it could not find the drivers for fastboot.

Rick7C2 said:
Ok ToolBox 1.1.2 randomly started detecting my ouya I got it rooted...Now I'm trying to do the recovery however I don't have fastboot drivers and can't find them. OuyaToolBox said to use the same drivers as before but when I browse to that directory windows says it could not find the drivers for fastboot.
Click to expand...
Click to collapse
Well I figured out how to bypass needing fastboot drivers and I am now in recovery only to find out I NEED a USB Keyboard well fml... I guess I gotta go buy a keyboard to flash my new rom.
Anyways I guess this can be closed/deleted.

could you please share how you got around needing fastboot drivers?

the ouya has a different hardware id when it is in fastboot mode. In fact, normal operation, recovery, and fastboot are all different hardware ids.
connect the ouya, adb fastboot, then go to the device manager, find the device and notice the hardware id change.
gotta go to the android_winusb.inf and edit it to match the new hardware id.
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_***&PID_****
^^^^ fill in the blanks.
OR!!! just separate the 3 different ids by commas.
;OUYA Console
%SingleAdbInterface% = USB_Install, USB\VID_2836&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2836&PID_0010&MI_01, USB\VID_****&PID****, USB\VID_****&PID_****
see what i did there?

WooHoo!!
Finally got it
About time! Thanks guys

[Q] OUYA_1_1 Driver????

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

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
Click to expand...
Click to collapse
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 ?

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...
Click to collapse
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...
Click to collapse

Still cant find ANY info on OUYA_1_1, no drivers no nothing, for such a *easy to hack* system it sure is not easy to hack lol

hmm
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..

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...
Click to collapse
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:

Are you in "none signed drivers" mode in windows ?
Envoyé depuis mon GT-I9505 en utilisant Tapatalk 4 Beta

ElMeteK said:
Are you in "none signed drivers" mode in windows ?
Envoyé depuis mon GT-I9505 en utilisant Tapatalk 4 Beta
Click to expand...
Click to collapse
it's telling me there are no drivers at all, but yes

I am having this exact same problem and I cant for the life of me figure out how to get past this to install recovery

try this
DrROBschiz said:
I am having this exact same problem and I cant for the life of me figure out how to get past this to install recovery
Click to expand...
Click to collapse
try this http://forum.xda-developers.com/showthread.php?t=2295645

GarbageGamer said:
it's telling me there are no drivers at all, but yes
Click to expand...
Click to collapse
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.

Here is exactly what i see after i fastboot the recovery image using the ouya tool box
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

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

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

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.

Ugh Guess ill try the entire process on my laptop and see if it helps

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...
Click to collapse
\/ 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...
Click to collapse
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.

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.

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.

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

ADB not working

I for the life of me can't figure out why my computer won't recognise my Pixel C for ADB.
Bit of background, using Win 7 64 bit. Never had a problem with this computer recognising phones for ADB (including various Nexus phones/tablets and Sony Xperia Z3 Dual).
My computer recognises the Pixel C as a device, and I've read through the various other posts of people having these problems, including:
http://forum.xda-developers.com/pixel-c/help/help-getting-pixel-c-recognized-adb-t3268991 and installing the adb installer suggested in that thread. I normally use Wug's Nexus toolkit and I don't think I've got a problem with the ADB drivers on my computer. I've tried to uninstall and then reinstall adb drivers a few times, but that doesn't work either.
I don't think its the cable I bought as well, because I have used the cable on another computer (borrowed) and ADB worked fine on that computer.
Any suggestions, or am I missing something?

Does it show up but can't find the driver? I have this issue with Windows 10 (currently fighting with it, that's how I found this thread). You need to add these device strings to android_winusb.inf for it to install the drivers, but it keeps telling me the correct hash isn't there, this is how I fixed it before.
Code:
;Google Pixel C
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_5201
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_5201
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_5201&MI_01
Edit: Just remembered an easier way: if the driver isn't installed, try to install it manually and select it from the list and select "Android Devices" then "ADB interface", and it should work.

Hi sorry, no-one every responded to the thread, so I didn't update it. I actually got it to work. Basically I deleted all my ADB drivers (and I had a lot, from all the various devices I have had over the years). I then plugged the pixel c in and boom it installed the driver correctly.