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
Related
Hi,
I have a stock unrooted Desire Z, and I'd like to root it using the instructions provided here.
I've downloaded gfree and visionary r14, and I already have the Android SDK installed, along with adb. However, for some reason, adb doesn't detect my phone when connected. It's set to "Charge only" and "USB debugging" is also enabled. I've already installed HTC Sync, however Device Manager still shows an "Android Phone" under "Other devices" as shown below
{
"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"
}
I've tried to install the driver again but I'm not sure where to point it. I've tried pointing it to the <sdk>\google-usb_driver\ but it couldn't find any appropriate driver. I looked at android_winusb.inf and sure enough I don't find my Desire Z in the list of USB VID/PIDs.
I've also tried installing the drivers in <HTC>\HTC Driver\Driver Files\XP_x86, <HTC>\HTC BMP USB Driver\qcusbmdm, or <HTC>\HTC BMP USB Driver\qcusbser, but none of them worked.
Lastly, I've tried uninstalling the "Android Phone" driver(it's not installed in the first place, but just to get it out of device manager), but once I reconnected the phone, "Found New Hardware Wizard" comes up again prompting me to install a driver for it.
Is this the reason why my phone isn't being detected? How can I install the correct driver and get adb to detect the phone properly?
Thanks!
In before you get flamed and this thread gets locked.
ZOMG yoo didn't search DIAF!!!!!111one
BTW there is a Q&A forum which is really the right place for issues like this (http://forum.xda-developers.com/forumdisplay.php?f=829)
To answer your question, yes it's a driver issue. The drivers do seem to be tricky what worked on my work laptop (Windows 7 x86) did not work on my home laptop (Vista x64)
Are you using this guide? http://forum.xda-developers.com/showthread.php?t=865685
You can also try this guide: http://forum.xda-developers.com/showthread.php?t=834748
There is a driver in that one that worked on my Windows 7 machine: http://www.mediafire.com/?wzdjcmowziw
There is another one to try but I can't remember where it is, the search function isn't working right now and as I mentioned this thread will likely be locked soon.
Are you using "Update Driver" from device manager, then using "Have Disk" and pointing it to the folder where you have the driver extracted?
If you still need help PM me I will look for that other driver.
Edit: this may also be helpful
raitchison said:
BTW there is a Q&A forum which is really the right place for issues like this (http://forum.xda-developers.com/forumdisplay.php?f=829)
Click to expand...
Click to collapse
right, not dev related, moved to q&a
Anyone know how I can get ADB on WINXP? doesn't work for me.
Sent from my HTC Vision using XDA App
What part isn't working? Does the SDK refuse to install or are you getting some kind of error.
Without more information I could offer the first google search result for "adb xp" http://forums.t-mobile.com/t5/Operating-System-Software/How-to-Install-ADB-XP-and-Vista/m-p/163836
It seems a bit dated but may be helpful all the same.
Ok thanks. When I first rooted my G2 I tried with ADB but didn't work for me. I don't think. So I went with visionary. The easier way? I keep hearing ADB is like a must so we could see exactly what we're doing. How about that ADB wireless app? Does anyone use that and is it good?
Sent from my HTC Vision using XDA App
Hi raitchison, thanks for the reply.
I've not followed those 2 guides specifically, but rather googled and found other guides, and followed them(the general gist).
In the first guide's "complete" way, I've completed Steps 1, 2, 3, 5.
Didn't do 4 but rather just went to the platform-tools folder and ran adb directly from there. Shouldn't matter.
I'm using a 3rd party cable, didn't think it'd make a difference but I guess I'll try with the original cable as well. This cable seems to work on another PC(at least driver installation, haven't tried with adb yet) with the same OS(Windows XP Pro SP3)
Step 7 doesn't show any devices. That's the problem.
Did a similar installation with the "quick" way. Same problem. The 2nd link seems to be similar.
I'm using Device Manager->Android Phone->Update Driver->Install from a list or specific location(Advanced)->Include this location in the search-><Path> where <Path> is the location of the drivers that I tried(from SDK or HTC Sync). Windows tells me that there's no appropriate drivers in that path to install.
Also tried Device Manager->Android Phone->Update Driver->Install from a list or specific location(Advanced)->Don't search. I will choose the driver to install->Other devices->Have Disk-><Path>. Same problem.
Are you sure you installed the latest HTC Sync (linked to in the guide referenced earlier)? Otherwise, you can try installing PdaNet (it'll install the correct drivers as well---a lot of users have reported success with it). You can also try using the drivers attached to this post. It is simply the SDK drivers modified with the ID for the G2:
Code:
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01
I think it should work with the Desire Z as well, but I'm not sure...
What version of Windows are you using ? The HTC Sync drivers should give you everything you need. It does sound like it's installing using the wrong driver, and that's why it's not seeing it.
steviewevie said:
What version of Windows are you using ? The HTC Sync drivers should give you everything you need. It does sound like it's installing using the wrong driver, and that's why it's not seeing it.
Click to expand...
Click to collapse
The HTC Sync drivers did not work on my home PC, which is Vista x64, I had to use a different driver to get it to work.
raitchison said:
The HTC Sync drivers did not work on my home PC, which is Vista x64, I had to use a different driver to get it to work.
Click to expand...
Click to collapse
Vista 64 ? ok, that's probably not that common though. The HTC Sync drivers do work with Win 7 64-bit, because I walked a guy through it myself. So I'm suprised they don't work on Vista 64 as well (but I don't doubt you).
(read the guides so please don't just link it....i've seen that on other threads)
for some reason kfu wont install the kindle driver.... (unsigned driver)
it didn't give me a prompt but i went into my driver signing and clicked allow.... still wont go through
can someone help me out please?
(i've only rooted a MT4G and i had no issues back then...)
running windows xp x32
i've been at it for hours and came across one on youtube but it says android composite ADB instead of android ADB
im still on stock 6.3.1 ( no changes have been made yet to the device )
this is the guide i've been reading which kindav just says " ur own your own" to my unsigned driver problem
http://forum.xda-developers.com/showthread.php?t=1552547
NovaxxBite said:
...
this is the guide i've been reading which kindav just says " ur own your own" to my unsigned driver problem
http://forum.xda-developers.com/showthread.php?t=1552547
Click to expand...
Click to collapse
Is that really all it says on the topic? Is "you're on your own" truly what you got out of reading the following?
kinfauns said:
If Windows refuses to install unsigned drivers, that feature must be disabled before continuing. The process differs for various Windows releases, so search Google and find a suitable method for your system.
Click to expand...
Click to collapse
I gave you a "search Google" link. The first item the search returns gives you step-by-step directions on how to get around the problem. Have you read it? Have you tried it?
kinfauns said:
Is that really all it says on the topic? Is "you're on your own" truly what you got out of reading the following?
I gave you a "search Google" link. The first item the search returns gives you step-by-step directions on how to get around the problem. Have you read it? Have you tried it?
Click to expand...
Click to collapse
wow i just reread my post. that wasnt what i meant to say. sorry, i hope/wasnt trying to be rude or offend anyone:angel:
the google link kindav felt like i was on my own...i've searched all over google and all the windows xp steps either say press F8
( no driver option there on my PC) or to click ignore /warn for the dialog prompt
( basically.. no link addressed my issue)
( following the first link)
i'm not getting the dialog to begin with, i've clicked both ignore and warn but nothing works
also... when i click instal.bat i get
'and' is not recognized as an internal or external command ( did i miss a step?)
after that the kindle driving window pops up, i hit next and after not even a split second it says it wouldnt install..unsigned driver
-edit-
tried using 2 other computers...same problem
NovaxxBite said:
wow i just reread my post. that wasnt what i meant to say. sorry, i hope/wasnt trying to be rude or offend anyone:angel:
the google link kindav felt like i was on my own...i've searched all over google and all the windows xp steps either say press F8
( no driver option there on my PC) or to click ignore /warn for the dialog prompt
( basically.. no link addressed my issue)
( following the first link)
i'm not getting the dialog to begin with, i've clicked both ignore and warn but nothing works
also... when i click instal.bat i get
'and' is not recognized as an internal or external command ( did i miss a step?)
after that the kindle driving window pops up, i hit next and after not even a split second it says it wouldnt install..unsigned driver
-edit-
tried using 2 other computers...same problem
Click to expand...
Click to collapse
1) Download KFU from this link http://forum.xda-developers.com/show....php?t=1399889
2) Before you start rooting ur device.. do the below
3) Extract the util.. run the install_drivers.bat.. this will help you install the drivers..
4) Once it is successfully done..follow the steps outlined in the document attached below (install drivers for ur kindle.docx)
5) Next step is to root ur device and install the google framework and market
6) To root your device.. run run.bat.. select option 2 to install the root.. it might take sometime and will restart the kindle and notify you
7) to install the google apps..run option 6 and then select 1.. sit back and watch the magic happen
This should help you.. let me know if you are not able to do it.. it will good if you can tell me in which step you are facing trouble
kishorev said:
1) Download KFU from this link http://forum.xda-developers.com/show....php?t=1399889
2) Before you start rooting ur device.. do the below
3) Extract the util.. run the install_drivers.bat.. this will help you install the drivers..
4) Once it is successfully done..follow the steps outlined in the document attached below (install drivers for ur kindle.docx)
5) Next step is to root ur device and install the google framework and market
6) To root your device.. run run.bat.. select option 2 to install the root.. it might take sometime and will restart the kindle and notify you
7) to install the google apps..run option 6 and then select 1.. sit back and watch the magic happen
This should help you.. let me know if you are not able to do it.. it will good if you can tell me in which step you are facing trouble
Click to expand...
Click to collapse
link broken?
NovaxxBite said:
link broken?
Click to expand...
Click to collapse
Thats wierd.. try it again http://forum.xda-developers.com/showthread.php?t=1399889
:good:
kishorev said:
Thats wierd.. try it again http://forum.xda-developers.com/showthread.php?t=1399889
:good:
Click to expand...
Click to collapse
this is the same link from the guide lol
i can't get past your 3rd step...
(unsigned driver )
ALSO... why cant i get ADB in device manger?
i've installed SDK tool, SDK Platorm-tools, Android 2.3.3 SDK Platform and Google USB Driver via Android SDK Manager
but when i plug in my kindle fire, it's listed under "other" instead ADB or Android ( and no driver can be found for it....)
kfu wont install kindle drivers because its unsigned
i've done the methods to allow it / ignore the warning prompt but again... its not working
(i didn't get a warning btw... it just said it wouldnt install after not even a second)
i've installed a different (non-related) unsigned driver perfectly ( to test ) but when i use kfu, i the unsigned error immediately after clicking next :crying:
and i've tested on 3 computers now...its all the same for me :<
NovaxxBite said:
this is the same link from the guide lol
i can't get past your 3rd step...
(unsigned driver )
ALSO... why cant i get ADB in device manger?
i've installed SDK tool, SDK Platorm-tools, Android 2.3.3 SDK Platform and Google USB Driver via Android SDK Manager
but when i plug in my kindle fire, it's listed under "other" instead ADB or Android ( and no driver can be found for it....)
kfu wont install kindle drivers because its unsigned
i've done the methods to allow it / ignore the warning prompt but again... its not working
(i didn't get a warning btw... it just said it wouldnt install after not even a second)
i've installed a different (non-related) unsigned driver perfectly ( to test ) but when i use kfu, i the unsigned error immediately after clicking next :crying:
and i've tested on 3 computers now...its all the same for me :<
Click to expand...
Click to collapse
What you can do is try adding the drivers manually to ur device instead of running the .bat file.. using the update driver option in ur device manager..
The driver will be available in the folder Kindle Fire Utility\drivers\kindle
kishorev said:
What you can do is try adding the drivers manually to ur device instead of running the .bat file.. using the update driver option in ur device manager..
The driver will be available in the folder Kindle Fire Utility\drivers\kindle
Click to expand...
Click to collapse
thanks, that seemed to work
now under android phone, i have Android Composite ADB Interface
-sigh-
when i checked cmd.exe for adb devices, it says
List of devices attached
( shows nothing )
well at this point, i've tried 4 different computers...
3 windows xp x32
1 windows 7 x64
On windows 7, the kfu installed the drivers but when i click run.bat , i get
adb offline
Boot status : unknown
Ive tried uninstalling, reinstalling, manually installing, rebooting computer and device
( everything i can find on xda and google )
nothing works
please help :/
Sent from my HTC Glacier using xda app-developers app
NovaxxBite said:
well at this point, i've tried 4 different computers...
3 windows xp x32
1 windows 7 x64
On windows 7, the kfu installed the drivers but when i click run.bat , i get
adb offline
Boot status : unknown
Ive tried uninstalling, reinstalling, manually installing, rebooting computer and device
( everything i can find on xda and google )
nothing works
please help :/
Sent from my HTC Glacier using xda app-developers app
Click to expand...
Click to collapse
Did u try changing the boot mode by selecting the option 1 (Boot Mode menu)
What error message did u c then?
Was the KFU able to restart ur kindle?
Recovery and Normal hangs on waiting while fastboot gives the " oops " error
no kfu never restarted my device
here's a screenshot from my XP computer ( its the same results on each computer )
( the boot menu is from trying to use fastboot mode )
{
"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"
}
there a problem with XP vendor code? apparently
"Thepooch" fixed that for me and showed me how to work kfu so thanks
thanks "kishorev" for helping out also btw
The kindle fire's vendor id was missing from adb_usb.inf . It was just a matter of opening adb_usb.inf with notepad and adding and saving this change.
Code:
0x1949
Then KFU could recognize the kindle as online bootmode 4000.
NovaxxBite said:
well at this point, i've tried 4 different computers...
3 windows xp x32
1 windows 7 x64
On windows 7, the kfu installed the drivers but when i click run.bat , i get
adb offline
Boot status : unknown
Click to expand...
Click to collapse
I hope this isn't redundant or anything, but if you still have your Windows 7 machine still handy, try rolling back the driver. That's how I got mine to work. It should be listed under Android Phone -> Android ADB Interface in the first place. If not, try reinstalling the drivers first.
I hope this helps!
jma9454 said:
I hope this isn't redundant or anything, but if you still have your Windows 7 machine still handy, try rolling back the driver. That's how I got mine to work. It should be listed under Android Phone -> Android ADB Interface in the first place. If not, try reinstalling the drivers first.
I hope this helps!
Click to expand...
Click to collapse
thanks, unfortunately the win 7 laptop i used was borrowed
( i need to get one... XP drivers are crappy lol )
but i'm sure this will help someone whos having this problem, searches xda or google and comes across this :highfive:
Alright, you've been messing around with Windows for far too long. Now it's time to do it the right way.
Indeed I second that the right way
Thepooch said:
Indeed I second that the right way
Click to expand...
Click to collapse
soupmagnet said:
Alright, you've been messing around with Windows for far too long. Now it's time to do it the right way.
Click to expand...
Click to collapse
nice. thanks & thanks again :victory:
:highfive:
Universal Naked Driver 0.72
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 30D25BC073F010CA01178CD6E2C5E4FA
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!
been looking for something liek this. I have no idea how to even install the drivers for adb and stuff
any specific instructions to install/
or just plug and play?
thx!
Thanks for your drivers.
BTW, what's the APX mode for Nexus 10? How to access APX mode?
padest.com said:
Thanks for your drivers.
BTW, what's the APX mode for Nexus 10? How to access APX mode?
Click to expand...
Click to collapse
APX is for tegra devices, so you would not need this mode on nexus 10.
Megiddo2000 said:
been looking for something liek this. I have no idea how to even install the drivers for adb and stuff
any specific instructions to install/
or just plug and play?
thx!
Click to expand...
Click to collapse
plug in per adb and per fastboot mode each! then in device manager point to the folder you extracted, done!
1wayjonny said:
plug in per adb and per fastboot mode each! then in device manager point to the folder you extracted, done!
Click to expand...
Click to collapse
Hey mate,
Can you tell me the driver names (USB\VID_**) for the Nexus 10 so I can add them to the automatic install in the Toolkit. I looked in your inf file but couldnt seem to find a Nexus 10 section like the others you have added. I need the adb and fastboot driver names and download mode driver names if they are included in your pack.
If anyone else also knows this please let me know as soon as possible as I want to release the Toolkit tonight.
Mark.
mskip said:
Hey mate,
Can you tell me the driver names (USB\VID_**) for the Nexus 10 so I can add them to the automatic install in the Toolkit. I looked in your inf file but couldnt seem to find a Nexus 10 section like the others you have added. I need the adb and fastboot driver names and download mode driver names if they are included in your pack.
If anyone else also knows this please let me know as soon as possible as I want to release the Toolkit tonight.
Mark.
Click to expand...
Click to collapse
Hello mskip,
I know what you mean and its not listed separated in the INF from Google but I can tell you its one of these below for ADB but the only Bootloaders one is the fastboot. Google stuck it under the generic section, not sure why. I do not own one so I can not verify sorry.
Code:
;Google Nexus (generic)
%GoogleNexusBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE1
[B]%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE2
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01[/B]
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE3
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_01
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE5
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
1wayjonny said:
Hello mskip,
I know what you mean and its not listed separated in the INF from Google but I can tell you its one of these below for ADB but the only Bootloaders one is the fastboot. Google stuck it under the generic section, not sure why. I do not own one so I can not verify sorry.
Code:
;Google Nexus (generic)
%GoogleNexusBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE1
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE2
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE2&MI_01
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE3
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_01
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE5
%GoogleNexusADBInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
Click to expand...
Click to collapse
Thanks for the info I figured maybe it was those but needed to be sure as I dont have the device either yet (stupid google) and needed to be sure.
Mark.
These drivers are working for my N4, and were working for my N10 when inside Clockwork recovery, but they are not recognizing the device when it's booted. The drivers say they are updated, and when I try to uninstall them, there is no option for removing the driver software. The device is showing up in Portable Devices inside Device Manager.
Can I manually delete the driver software to try again?
Edit: I'm stupid. Didn't have USB debug enabled.
My nexus 10 said it was Nexus a Nexus 4 under devices
Maybe this is normal... anyhow great driver... works great updated from Samsung drivers I was using b4 :^}
What about the drivers installed by Kies.... Should I be deleting those as well?
Sent from my Nexus 10 using Tapatalk 2
detects my nexus 10 as a nexus 4
---------- Post added at 03:15 PM ---------- Previous post was at 03:08 PM ----------
nvm.... was able to root with Superboot regardless
Drivers work great thank you for your work. Was able to root with my Nexus 10 with Superboot without unlocking. Made the whole process way easier.
1wayjonny said:
plug in per adb and per fastboot mode each! then in device manager point to the folder you extracted, done!
Click to expand...
Click to collapse
Can you explain more details? I just have no idea how to use it.
I'm just very new to all these stuff.
Any help will be much appreciated.
How would I get the driver to work with my AT&T One X? Keeps saying the driver is up to date with the "MTP USB Device" driver.
Universal Naked Driver
Thank you very much for this!
Deleting old Drivers
I'm working on getting the naked drivers working on an Asus transformer prime but when I go to uninstall the old/automatic drivers there is no option to delete them so when I disconnect it from my laptop and reconnect it (offline) it still picks up the old drivers.
when I try to manually change the drivers (with the official one still installed) it tells me
" The software you selected does not contain a compatible software driver for this device. if the folder contains a driver make sure it is designed to work with windows for 32-bit systems."
help
no matter what i do i cant root my nexus 10, i had it rooted before the 4.2.2 update, doing it via my girlfriends laptop running but the laptop broke and cant get root access again because im running windows 8 and my days what a pain in the arse this is to do,
i see in device manager when nexus 10 is connected as followed:
Other devices:
! ADB interface with warning sign
! Unknown device
but no android phone or anything
portable devices
nexus 10
please help guys im just trying to do one of the simplest things here in rooting,, took 30secs on windows 7
Thanks! makes things a lot easier!:good::good:
whats the adb command to get the device bootloader version?
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!
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