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.
Related
Just hooked this baby up. Amazon, of course, doesn't provide any information on USB drivers or on how to enable debugging on the device. Probably one of their attempts at "security".
Anyway, looking for two things:
1. Any leads on drivers for windows. I could also do this on a Mac
2. How to enable debug mode so that I can actually test my damn apps on the device.
Everyone keeps talking about how they suspect this is running on cheapened-up BB Playbook hardware... not sure that would help at all...
breon said:
Found it. It's pretty easy. http://blog.actlocalmedia.com/2011/11/developing-on-kindle-fire.html
Click to expand...
Click to collapse
keyesdav, this should help. Thought I'd cross-post (cross-quote?) it over here in case you didn't see / haven't found it yet.
I was able to use the google adb driver on win7 x64, but you have to add the device id to the ini file.
Edit %androidsdkdir%\google-usb_driver\android_winusb.inf
Try adding the following lines under [Google.NTx86] AND [Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Still unable to get Kindle Fire to attach to Win 7 x64
I have a Lenovo W520 laptop. I've made these changes, however the Kindle Fire still comes up unrecognized in the Device Manager.
adb devices shows nothing
repeated adb kill-server, adb start-server no change
Help!
BTW, my "google_usb_driver" directory is in C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver.
Did they move it recently?
Did you go to Device Manager on your PC and then select the Kindle 'Unknown Device' and update the driver by selecting the Inf file you had edited? After updating the driver the system will then show the ADB connection. This is the same process to go through when doing the Root.
That worked!! Thanks!
(I didn't have to do this when I rooted my Galaxy Tab. Samsung provided a driver.)
So I have my Kindle Fire rooted, with TWRP 2.2.2.1, FFF 1.4A and the latest version of CM 10 w/ SGT7 (9/05). Using KFU 0.9.6 when I attach my Kindle to my computer the ADB status is offline, while the drivers on my computer recognize it as an "Amazon Kindle Fire" and if I look in the properties I see "Amazon File-CD Gadget USB Device", "USB Mass Storage Device", and the drive it's recognized as "M:\" for me. No matter how often I attempt to reboot my computer, the Fire, or uninstall the drivers and install the drivers manually (either through the install drivers.bat or adding
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
and
0x1949
to android_winusb.inf and adb_usb.ini respectively.
However when I reboot my Fire into recovery, it's recognized as Online. Any help with getting it recognized when regularly booted up?
Sounds like a ROM issue. The new builds of CM10 have a PID of 0004 for some reason, rather than 0006.
Why it wouldn't affect recovery, though, I couldn't tell you.
Damn, alright. Thanks, at least I can always transfer a new ROM over and flash it when I need to. Hopefully they'll get it fixed soon.
Just use recovery to send adb commands.
soupmagnet said:
Just use recovery to send adb commands.
Click to expand...
Click to collapse
Right, I'm using it. I installed JandyCane and it's working just fine now. However I find I'm missing much of what I liked in the other ROM. Ah well, time to explore ROMs! Thanks for your help!
I added these 2 lines to the already long list of ids saved the win_usb file then reinstalled the driver now adb works
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0004&REV_0216&MI_01
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