Database Users

Why can't I get ADB to work?

I never had a problem with the g1 but am having trouble setting it up for the g2.
When developer mode is on it doesn't install the adb drivers. I used the drivers that were downloaded with the sdk setup. Tried installing them manually through the device manager and it wouldn't accept the drivers.
I'm using windows 7 ultimate x64. I'm not computer illiterate by any means and never had trouble in the past so it's really bugging me.
Thanks in advance!
Sent from my T-Mobile G2 using Tapatalk
EDIT: Crap, meant to put this in G2 Development...

Jorsher said:
When developer mode is on it doesn't install the adb drivers. I used the drivers that were downloaded with the sdk setup. Tried installing them manually through the device manager and it wouldn't accept the drivers.
Click to expand...
Click to collapse
Probably because sdk setup driver's inf file doesn't have entries for G2.
If you have linux desktop, connect your phone and use lsusb to find the VID & PID. You can add those to the inf file and perhaps it will work properly.

jashsu said:
Probably because sdk setup driver's inf file doesn't have entries for G2.
Click to expand...
Click to collapse
That's what I figured and the reason I gave up trying.
Is the driver available somewhere, can the information be added manually (I suppose I can open the inf file when I get home), or do I just have to wait for Google to release an updated driver?

VID and PID
vendor id: 0bb4
product id: 0c91

themadbogart said:
vendor id: 0bb4
product id: 0c91
Click to expand...
Click to collapse
So open %SDK%\usb_driver\android_winusb.inf with a text editor and insert this under the sections [Google.NTx86] and [Google.NTamd64]
Code:
;T-Mobile G2
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01
;
and see if that lets the driver install properly.

ADB drivers installed no problem for me with my G2. I already had PdaNet installed. Windows 7 32-bit. They do have a 64-bit version listed, too:
http://junefabrics.com/android/download.php

now the big thing is does it recognize the device as online or offline? for some reason and i haven't played with mine yet cuz it is at the house and i'm at work. but in the dev forum they are having that issue... working on root already

Not sure how it worked for you seancneal.
Anyway, thanks, added the entries, installed without issue.
I know you can get to recovery/bootloader through ADB, but is there a way I can without using ADB?

Jorsher said:
Not sure how it worked for you seancneal.
Anyway, thanks, added the entries, installed without issue.
I know you can get to recovery/bootloader through ADB, but is there a way I can without using ADB?
Click to expand...
Click to collapse
Hold volume down while powering on the phone and you will get to bootloader, from there you can select recovery
Sent from my T-Mobile myTouch 3G Slide using XDA App

tubaking182 said:
Hold volume down while powering on the phone and you will get to bootloader, from there you can select recovery
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Nice, thanks.
Yesterday when I was trying to get to it, I tried holding power/voldown, power/volup, power/camera, etc.
Guess I just needed to press the power button instead of holding it.

Any tips for getting this to work in Ubuntu?
lsusb shows the device, and adb devices shows "??????? no permissions"
Edit -- found it in another thread, sorry.
To re-post: Add this line to /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666"
Then run
adb kill-server
sudo service udev restart
adb start-server
adb devices

uplinked said:
Any tips for getting this to work in Ubuntu?
lsusb shows the device, and adb devices shows "??????? no permissions"
Click to expand...
Click to collapse
Ding ding ding! Congratulations on being the 1,000,000 person to ask this question. Please run adb as root to claim your prize.

jashsu said:
So open %SDK%\usb_driver\android_winusb.inf with a text editor and insert this under the sections [Google.NTx86] and [Google.NTamd64]
Code:
;T-Mobile G2
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01
;
and see if that lets the driver install properly.
Click to expand...
Click to collapse
Thanks! I was having problems getting it going on my comp too

jashsu said:
So open %SDK%\usb_driver\android_winusb.inf with a text editor and insert this under the sections [Google.NTx86] and [Google.NTamd64]
Code:
;T-Mobile G2
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01
;
and see if that lets the driver install properly.
Click to expand...
Click to collapse
I added these 2 lines of code under both of the sections in the .inf file. It installed fine but when I try adb get-state it says unknown, when I try adb devices it comes up blank. Not sure what I'm doing wrong.

SlicedKuniva said:
I added these 2 lines of code under both of the sections in the .inf file. It installed fine but when I try adb get-state it says unknown, when I try adb devices it comes up blank. Not sure what I'm doing wrong.
Click to expand...
Click to collapse
Do you have USB debugging enabled?

jashsu said:
So open %SDK%\usb_driver\android_winusb.inf with a text editor and insert this under the sections [Google.NTx86] and [Google.NTamd64]
Code:
;T-Mobile G2
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C91&MI_01
;
and see if that lets the driver install properly.
Click to expand...
Click to collapse
thanks this works. should be stickied.

I've tried this and a few other ways of getting adb but no luck. Any more suggestions are welcomed. Thanks guys.

Download PDA Net on your PC and install it, it will automatically install the drivers for you. You can uninstall PDA Net afterwards if you want and the drivers will stay.
There seems to be a problem with Win7 x64 when installing the drivers using the SDK (which looks solved by the posts above, but if those don't work, try PDA Net).

Thanks. I already tried that, still no luck.
Sent from my T-Mobile G2 using XDA App

USB Debugging got it to work for me, after much toiling.

[SOLVED] Google Android USB drivers - Nexus S SCLCD GT-i9023 not recognized

Hi everyone,
i've bought a SCLCD Nexus S (GT-i9023).
I've tried to get the device recognized by the Google Android USB driver packaged with the Android SDK r10.
But the android_winusb.inf file provided with the USB drivers version r4 doesnt mention the Nexus S :
Code:
; HTC Dream
%SingleAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C01
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C02&MI_01
%SingleBootLoaderInterface% = USB_Install, USB\VID_0BB4&PID_0FFF
; HTC Magic
%CompositeAdbInterface% = USB_Install, USB\VID_0BB4&PID_0C03&MI_01
;
;Moto Sholes
%SingleAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB
%CompositeAdbInterface% = USB_Install, USB\VID_22B8&PID_41DB&MI_01
;
;Google NexusOne
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_0D02&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E11
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E12&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E22&MI_01
Having a look at Windows devices manager, i've added my Nexus S device identifier ton the .inf file :
Code:
;
;Google NexusS
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
With this i've been able to use fastboot and unlocked my phone.
But when im trying to use ADB, my device is not listed as connected. So i've modified the previous lines by these one:
Code:
;
;Google NexusS
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&MI_01
But it doesn't change anything :x
Do you succeed in using the Google Android USB drivers
With wich Nexus S version ?
Does it have ever worked ?
Go Google go !!! This device is month old

Hi folks,
final answer, to make the GT-i9023 works with Google Android USB drivers you got to edit the "android_winusb.inf" file located in the "extras\google\usb_driver" dir of your Android SDK installation to add the following line to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
Code:
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
If this is not working, you got to :
* go to the Windows devices manager and uninstall the driver for every Nexus S sub-devices as describe in the attachment
* wait for windows to ask for installing the new devices using your new .inf file
* restart adb : adb kill-server & adb start-server
Should be working fine then

Still cannot recognize my i0923
I was trying to write a recovery image to my nexus s (i9023 with SCLCD), and have successfully installed the usb driver for my nexus s, but both fastboot and adb just cannot recognize the device. When I typed
Code:
fastboot devices
and
Code:
adb devices
, nothing shows up. Is there anything that I can do to fix this? Thanks!

I solved the previous problem
I browsed your guide to unlock nexus s and found someone suggested in the reply to copy AdbWinApi.dll and AdbWinUsbApi.dll from platform-tools directory to tools directory, then it worked.
Hope someone sees this and it will work for them.

Thanks for this, now my Nexus S bootloader is unlocked.
( no need for Pdanet program or other crazy solutions)

one more Trick
i did all the above and it didn't work but i added an another trick that worked
C:\Program Files (x86)\Android\android-sdk\tools>adb devices
List of devices attached
....
no devices were found , though SNS was found in Device manager ,
to fastboot unlock , i did the below command
C:\Program Files (x86)\Android\android-sdk\tools>fastboot.exe -s YOUR_SERIAL_NUMBER oem unlock
...
OKAY [ 38.590s]
finished. total time: 38.590s
and it worked , give it a try if you faced drivers issues

NEWBIE HERE. I have the i9020T. Will any of these fixes work for this one? And I'm a little confused on where to start. Where do I type all these commands?

jrocka01 said:
NEWBIE HERE. I have the i9020T. Will any of these fixes work for this one? And I'm a little confused on where to start. Where do I type all these commands?
Click to expand...
Click to collapse
Have you found your answer?
If not, try this link.
http://forum.xda-developers.com/showthread.php?t=895545 - AllGamer has put the process step by step very clearly, and this thread is specifically for i9020T for Gingerbread 2.3.3, I am pretty sure it is same for 2.3.4 as well.
If you want to know where to type all these and all, pm me and I will get you some answers.
If you don't want to get into typing a lots of commands, you can't get away with it completely, but try doing what vincentleung says, put those two files into the directory, it worked for me as well.

creativedevil said:
Have you found your answer?
If not, try this link.
http://forum.xda-developers.com/showthread.php?t=895545 - AllGamer has put the process step by step very clearly, and this thread is specifically for i9020T for Gingerbread 2.3.3, I am pretty sure it is same for 2.3.4 as well.
If you want to know where to type all these and all, pm me and I will get you some answers.
If you don't want to get into typing a lots of commands, you can't get away with it completely, but try doing what vincentleung says, put those two files into the directory, it worked for me as well.
Click to expand...
Click to collapse
I've lost USB connectivity so this won't work. Do you know of a way to do it OTA?

Might be obvious but is there a chance you can root your device using improper drivers?

Needed to do the exact same thing on my brand new Vidéotron Nexus S this week-end.
I added these lines:
Code:
; Google Nexus S
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&MI_01

My Nexus S required the following lines:-
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
Note the change of ID from 4E20 to 6860
1st one works for recovery, second is for ADB
Device is running Koush ICS (CM9 Alpha 12)...
Not sure if that's why they are different.

Update: after installing the driver make sure to change the folder in cmd to \android-sdk\platform-tools and then run fastboot, as that's where fastboot.exe is (newly).

kursk said:
Hi folks,
final answer, to make the GT-i9023 works with Google Android USB drivers you got to edit the "android_winusb.inf" file located in the "extras\google\usb_driver" dir of your Android SDK installation to add the following line to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
Code:
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
If this is not working, you got to :
* go to the Windows devices manager and uninstall the driver for every Nexus S sub-devices as describe in the attachment
* wait for windows to ask for installing the new devices using your new .inf file
* restart adb : adb kill-server & adb start-server
Should be working fine then
Click to expand...
Click to collapse
thank u for this guide...it really saved my rest this night

worked for me!
TrickyEarlobe said:
My Nexus S required the following lines:-
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
%CompositeAdbInterface% = USB_Install, USB\VID_04E8&PID_6860&MI_01
Note the change of ID from 4E20 to 6860
1st one works for recovery, second is for ADB
Device is running Koush ICS (CM9 Alpha 12)...
Not sure if that's why they are different.
Click to expand...
Click to collapse
Worked for me! Thanks! Just had to go next to device manager and select the file for the driver.
Thanks

sampainho said:
Worked for me! Thanks! Just had to go next to device manager and select the file for the driver.
Thanks
Click to expand...
Click to collapse
Does this work for the NS4G as well? I can't find a forum post similar to this and I've been trying for hours to get my drivers correct.

Jyro275 said:
Does this work for the NS4G as well? I can't find a forum post similar to this and I've been trying for hours to get my drivers correct.
Click to expand...
Click to collapse
It should work, you must add the correct lines inti the .inf file. To find the correct strings, check the properties of the unknown device in the Windows hardware manager.

I'm also having problems with finding a driver. Going to try this when I get home.
Verstuurd vanaaf miene Oneplus One mit CM11-M11

kursk said:
Hi folks,
final answer, to make the GT-i9023 works with Google Android USB drivers you got to edit the "android_winusb.inf" file located in the "extras\google\usb_driver" dir of your Android SDK installation to add the following line to both "[Google.NTx86]" and "[Google.NTamd64]" sections :
Code:
;
;Google Nexus S GT-i9023
%SingleAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20
If this is not working, you got to :
* go to the Windows devices manager and uninstall the driver for every Nexus S sub-devices as describe in the attachment
* wait for windows to ask for installing the new devices using your new .inf file
* restart adb : adb kill-server & adb start-server
Should be working fine then
Click to expand...
Click to collapse
This worked! I want to kiss you!:good::good::good::good::good::good::good:

[q] kindlefire root troubleshoot please help

Im having trouble rooting my kindle fire. I have windows 7 and when i get to the step on opening the device manager and updating the driver for the kindle my computer wont let me because it says that it doesnt support x64. Can somebody help me?!!?

I'm on windows 7 64 bit and I don't have this problem can u right click and open as administrator or something like that.

I was having the same issue make sure it is applied under both the X86 and X64 parts of android_winusb.inf, then it should install but to use it I had to hit f8 at startup to disable driver signature enforcement. Hope this helps

When you added entries to the android_winusb.inf file, did you add the code to both sections?
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
...
Code:
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
...

YES I DID.

I found the rooting thread in the dev area- and I'm trying the step to create the usb file in the .android folder. He says to run "adb update usb" to get it to create- but when I run that- it spits out all the available commands/switches that can be run with adb (like a help file).. Is that the wrong command? I can't seem to get the usb file to create.
edit: nevermind got it- had to install all the android 4.0 stuff- I had unchecked it before and only installed dev tools and usb driver

[Q] How to install of Thinkpad Tablet ADB drivers on a Windows7?

Hello everyone.
Could please let you know how to install ADB driver on Windows7 OS?
This is because in the Windows7 devices manager there was no other device section related with Thinkpad tablet.
Is there any special method to installation of Thinkpad ADB deivers on Windows 7 OS?

I noticed you are a new member, I am too so I'm not going to flame you for not searching. However, the creed here on xda is search, and I personally answered a similar question yesterday on this forum.
The short answer is that lenovo has provided specific drivers for the thinkpad. The standard adb honeycomb drivers wont work. The full guide to setting up adb on windows and the link to the thinkpad driver can be found here:
http://www.thinkpadtabletforums.com...ent/complete-setup-guide-android-sdk-and-adb/
Follow the guide to the letter, windows and adb seem to have a mind of their own at times. Try not to leave anything out. Good luck

Thank you for the reply.
If my behaviors makes you an uncomfortable and I'm really sorry.
I read few times above links of your articles but I'm not sure if I've got a find the answer of my questions.
so I was posted a same question Lenovo and XDA-forum.
And you know that Installation of ThinkPad table ADB drivers on Windows7 64bit has a little bit different procedures.
In My case, I was not found a any kind of other devices section on my computer management tool.
So, I was do a following method but was not started normally.
1. In the device manager on my computer I manually added a ThinkPad tablet using downloaded driver from Lenovo.
2. I saw there are two kind of device that following when I manually added.
First one is “Lenovo ThinkPad tablet ADB interface” and second one is “Android Bootloader Interface”.
I added all of those device drivers.
3. However, Those two drivers were not a started normally, and marked a yellow in the device manager.
But, there were my mistakes that I don't know added of following information.
And I read your post from top to bottom and found below information someone's reply your post.
-----------------------------------------------------------------------------------------
In the downloaded Lenovo ThinkPad tablet ADB driver folder please open an android_winusb.inf then in a INF file
find a [Google.NTamd64] and added a following.
[Google.NTamd64]
;
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
;
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_741C
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741C&MI_01
;

sometimes, adb, drivers and windows seem to have different minds. I never understand . when in doubt, its a good idea to reboot both the windows and TPT just to have a clean connection.
I also suggest following the steps below to the letter:
1. Uninstall those unrecognised devices in device manager
2.enable usb debugging on tablet
3. connect to pc via usb cable
3. on the 2nd tab at the top of device manager click "scan for hardware changes"
4. when the thinkpad shows up, right click it, select update driver software, and browse your folder to where you unzipped the downloaded TPT driver and OK.
5. Let it scan and install
Hopefully, the steps above will get the thinkpad to play nice with windows and adb
Good luck

jeong760 said:
Thank you for the reply.
If my behaviors makes you an uncomfortable and I'm really sorry.
I read few times above links of your articles but I'm not sure if I've got a find the answer of my questions.
so I was posted a same question Lenovo and XDA-forum.
And you know that Installation of ThinkPad table ADB drivers on Windows7 64bit has a little bit different procedures.
In My case, I was not found a any kind of other devices section on my computer management tool.
So, I was do a following method but was not started normally.
1. In the device manager on my computer I manually added a ThinkPad tablet using downloaded driver from Lenovo.
2. I saw there are two kind of device that following when I manually added.
First one is “Lenovo ThinkPad tablet ADB interface” and second one is “Android Bootloader Interface”.
I added all of those device drivers.
3. However, Those two drivers were not a started normally, and marked a yellow in the device manager.
But, there were my mistakes that I don't know added of following information.
And I read your post from top to bottom and found below information someone's reply your post.
-----------------------------------------------------------------------------------------
In the downloaded Lenovo ThinkPad tablet ADB driver folder please open an android_winusb.inf then in a INF file
find a [Google.NTamd64] and added a following.
[Google.NTamd64]
;
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
;
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_741C
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741C&MI_01
;
Click to expand...
Click to collapse
Ok, it took me a while to find out why this wasn't working in my case: I had to change the device ID to the one that applies to my tablet! So that's how I did it: In devcie manager right click on ThinkPad Tablet - go to properties and choose the "Details" tab. Here choose "Hardware Ids" and have a look what it says there. In my case this is:
USB\VID_17EF&PID_741B&REV_9999
USB\VID_17EF&PID_741B
So I changed jeongs entries to:
;
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
;
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_741B
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741B&MI_01
;
Then it worked like a charm!

Thank you! This fixed my problems as well. Cheers,
ChiefOHara said:
Ok, it took me a while to find out why this wasn't working in my case: I had to change the device ID to the one that applies to my tablet! So that's how I did it: In devcie manager right click on ThinkPad Tablet - go to properties and choose the "Details" tab. Here choose "Hardware Ids" and have a look what it says there. In my case this is:
USB\VID_17EF&PID_741B&REV_9999
USB\VID_17EF&PID_741B
So I changed jeongs entries to:
;
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_0955&PID_7000
%CompositeAdbInterface% = USB_Install, USB\VID_0955&PID_7100&MI_01
;
;NVIDIA Tegra
%SingleAdbInterface% = USB_Install, USB\VID_17EF&PID_741B
%CompositeAdbInterface% = USB_Install, USB\VID_17EF&PID_741B&MI_01
;
Then it worked like a charm!
Click to expand...
Click to collapse

in my case it was very weird.... because i had to enable storage first, otherwise i saw the ThinkPad in the device manager, but was not able to enable the driver for it... instantly after i enabled the storage, the ADB Driver was enabled and i could saw the device with adb devices...

raph3ix said:
in my case it was very weird.... because i had to enable storage first, otherwise i saw the ThinkPad in the device manager, but was not able to enable the driver for it... instantly after i enabled the storage, the ADB Driver was enabled and i could saw the device with adb devices...
Click to expand...
Click to collapse
very strange. for me it only works when set to "charging only" and MTP deactivated. Im on win7 64.
worked with adb devices in windows cmd console.
otherwise I only get the lenovo window where you can select, browse, sync office etc. and nothing listed in console.

[Q] MTP and ADB not working

As the title states, MTP and ADB are not working on my Nexus 4. MTP - phone doesn't show up in my computer. adb devices gives a blank list
Here are some things I tried:
I tried reinstalling device drivers
I tried using different USB cables
I plugged a different phone (HTC m7) into my computer (running windows 8.1 Pro), ADB and MTP work with that phone
Plugged my phone into a different computer, nothing works. But ADB and MTP work for the m7.
Neither MTP nor ADB work in recovery mode (TWRP 2.8.5.2). No fastboot, either.
Situation happened since CM11 and remained after clean wipe to C12.1
Phone charges fine, so USB connector (as a whole, at least) isn't borked yet
So.. any ideas?

Try to look at the google USB drivers .INI file. My last encounter with this file, is that there is no definition for the nexus 4 in the .ini file. So you may try to create a new entry for the nexus 4 and then copy the correct values for the PID and VID values from the device manager /nexus 4 or equivalent tab. Right click and go to hardware details or so.
Then update the drivers as normal from the device manager and navigate to the location of the .INI file and choose the adb boot loader interface.

prince93 said:
Try to look at the google USB drivers .INI file. My last encounter with this file, is that there is no definition for the nexus 4 in the .ini file. So you may try to create a new entry for the nexus 4 and then copy the correct values for the PID and VID values from the device manager /nexus 4 or equivalent tab. Right click and go to hardware details or so.
Then update the drivers as normal from the device manager and navigate to the location of the .INI file and choose the adb boot loader interface.
Click to expand...
Click to collapse
OK, i looked at the INF file. Amongst the Google Nexus devices listed, there is no Nexus 4 specifically but there is this
Code:
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%CompositeAdbInterface% = USB_Install, USB\[B]VID_18D1&PID_4EE2&MI_01[/B]
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE7
The one in bold seems to match with what I see when I plug in my phone and look at device manager.
Another thing is very strange - only when I switch from MTP to PTP mode, then my Nexus 4 shows up in my computer, and ADB works! But this is still weird and want a proper solution.

c00ller said:
OK, i looked at the INF file. Amongst the Google Nexus devices listed, there is no Nexus 4 specifically but there is this
Code:
;Google Nexus (generic)
%SingleBootLoaderInterface% = USB_Install, USB\VID_18D1&PID_4EE0
%CompositeAdbInterface% = USB_Install, USB\[B]VID_18D1&PID_4EE2&MI_01[/B]
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE4&MI_02
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE6&MI_01
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4EE7
The one in bold seems to match with what I see when I plug in my phone and look at device manager.
Another thing is very strange - only when I switch from MTP to PTP mode, then my Nexus 4 shows up in my computer, and ADB works! But this is still weird and want a proper solution.
Click to expand...
Click to collapse
Well you can try to add a new entry for nexus 4 (copy and paste from nexus 7 entry for example and replace the hardware I'd values with the ones you see in the device manager). Second make sure you have adb enabled in developer options. Third choose to update the driver in the device manager for your nexus 4 entry (or android phone). Click through choosing manual drivers and so on until you are required to navigate to the .INI file. Once you get there you will have to choose adb boot loader interface and complete the process. From there you should be able to communicate with your device over adb.

So, after a bunch of Googling and trying other things, this is the solution that worked for me: http://forum.xda-developers.com/showpost.php?p=41712600&postcount=11
I also had ClockworkMod Universal ADB driver installed and had to manually uninstall that. When Google asked for new drivers, I pointed it to the ones I downloaded from Google. Hope this might help others in the future...