Database Users

[Q] Windows 7 Driver Problems

Hi guys,
I have literally tried everything I could find here. I have tried the Universal drivers, the PDAnet drivers, and the Google drivers, and I have used an installer as well as manually installed the drivers. For the universal and Google drivers, I can get the phone to be recognized by Windows 7 as a Nexus 4, and Windows says the drivers are configured properly. However, the phone doesn't mount and ADB/fastboot still don't connect (and yes, the phone is in USB debugging mode).
After every failed driver I uninstalled the device, removed the Google drivers from USBdeview, and reinstalled the next set of drivers, to no avail. The computer has been restarted many times, no luck. I have tried all three USB ports on my laptop, and I have tried multiple cords, one of which I know for sure works.
Any suggestions would be appreciated. Thank you.
EDIT: If you want, I can add a screenshot of my USBDeview entries to see if there are any conflicting drivers/interfaces. My old phone was a Samsung Galaxy S, but I removed as many of those drivers as I could find.

Silly question, but when attempting fastboot, you did reboot into the bootloader? If you use twrp, they have an adb push setting in the advanced tab(?), see if that's recognized at all?
Sent from my Nexus 4 using Tapatalk 4 Beta

I couldn't use adb or fastboot at all. No adb when the phone is on, no fastboot in the boot loader. I don't have a custom recovery because I can't flash one without fastboot.
Sent from my Nexus 4 using xda app-developers app

I'm also on 64-bit Windows 7, I forgot to mention that. Just tried the Universal Naked Drivers, to no avail.

Did you update adb to the latest version (v1.0.31)? If not, adb won't see the phone

EddyOS said:
Did you update adb to the latest version (v1.0.31)? If not, adb won't see the phone
Click to expand...
Click to collapse
Thanks for the reply. I've been trying to use Minimal ADB and Fastboot so far, since I really don't want to download the SDK. However, I've also tried to use the newest versions of Wug's Nexus Root Toolkit and mskip's toolkit, both of which do not work.

My Windows 7 Pro x64 work PC can see it as can my personal Windows 8 Pro x64 laptop at home - both using the stock Google drivers from the SDK
Remember, also, that when you run 'adb devices' the phone will ask you to allow the PC to connect. If you don't click OK on the phone it will say it's offline

EddyOS said:
My Windows 7 Pro x64 work PC can see it as can my personal Windows 8 Pro x64 laptop at home - both using the stock Google drivers from the SDK
Remember, also, that when you run 'adb devices' the phone will ask you to allow the PC to connect. If you don't click OK on the phone it will say it's offline
Click to expand...
Click to collapse
The window never pops up on the phone. ADB list of devices comes up blank. I'll try the SDK later.

Using the SDK and the newest ADB did not help, still the same problem. I'm out of ideas.
EDIT: Attached are two screenshots of the USBDeview program after I've uninstalled all the Google and Android drivers. Is there anything there that looks like it needs to be uninstalled?
{
"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"
}

[Q] Nexus 4 MTP Storage Problems

Recently, I have not been able to get my Nexus 4 to show up in my computer. I am able to use ADB and the drivers work fine, but when I connect my Nexus 4 it will not install the drivers for MTP. Rather, it will say it has the correct drivers installed, but it cannot start (Code: 10) and the icon for the device has a yellow exlamation mark next to it. I tried switching it between MTP and PTP as well as enabling and disabling USB Debugging, but it wont show up. Next, I decided to try to switch ROMS, as well as uninstall and re install all the drivers for the phone. No matter what I do I am able to connect to the phone through ADB, but MTP will give me the same error over again. Even on PTP my PC wont install the drivers for the phone.
I have looked through numerous threads and tried all kinds of solutions people have suggested, but none of them have worked for me. I've even tried switching between USB ports, cords, and computers (32 bit, 64 bit) and have tried plugging it into a new computer which i have never plugged the phone into, and nothing at all will work.
I am really at a loss here as I have spent many hours going through the solutions posted on these forums and others. I use USB for backing up my device as well as adding files etc. , and I dont want to do anything with my phone without being able to connect to it by USB at the very least. Airdroid will work as a temp. solution but it is way too slow when i transfer bigger files. My Nexus has worked fine with MTP since I bought 3 months ago, and even after rooting and updating the MTP has still worked regardless. I am running Windows 7 ultimate 64 bit, and my phone is on 4.3.
To anyone who will tell me to look on other threads I realize there are a ton of them out there, but I have tried using so many of the methods described, and none of them have worked.

Is there anyone that can help me with this problem? My phone is having issues and I need to backup up my stuff so I can flash to stock, factory wipe, etc.
Sent from my Nexus 4 using xda app-developers app

What rom and kernel are you running? Have you tried on stock firmware and stock kernel, with USB Debugging turned off? It sounds like an issue with the software in your phone.
Also when you connected your device, look in Device Manager and tell me the exact name listed for your Nexus 4, it should be saying "Nexus 4" or "Google Nexus 4 ADB Interface".
You can back up your files through adb: adb pull /sdcard/ C:\backup\
Instead of AirDroid you can try WorkGroup/Samba sharing. Enable a Workgroup shared folder on your PC then use ES File Explorer to access it and transfer file that way.

Here is my system info:
{
"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 have tried enabling and disabling debugging but it doesn't make much of a difference. It'll show up as MTP USB Device under portable devices with a yellow exclamation mark next to it, as well as Google ADB Interface Device under Android Device. Sometimes it will show up in Other Devices as Nexus 4, but then it install the drivers for ADB and it goes away.
I have also tried getting it to connect with AOKP milestone 2 (4.2.2) and the latest version of Carbon ROM which was also 4.2.2. I had Franco.kernel installed on both of these. The only thing I haven't done is a factory reset of all my data or flash back to stock rom.
Thanks for the backup tips I'll try those to see if I can get everything off it.
Sent from my Nexus 4 using xda app-developers app

Try uninstalling the driver, select the checkbox option to delete the files as well. Then reconnect it while in ADB mode and use the Universal Naked Driver: http://forum.xda-developers.com/showthread.php?t=2263822
Also this will sound strange, but on your Pc, go into "Disk Manager" and make sure there are no blank partition or disk that might vaguely resemble your device. If there is one and without a driver letter, assign to it any drive letter.
Make sure there aren't conflicting ADB or USB drivers from other Android device, if there are, remove them.
Try live booting into Ubuntu 13.10, if it still can't copy your files, the phone is the problem.

Wow. I just plugged it in to uninstall the drivers and it started working. I didn't do anything to the phone or the computer, its the first time it has worked after hours of trying to get it to show up. Thanks for the help, sorry for the trouble.

Well let me know when it stopped working.
sent from xda premium app

Oh, one more thing. Is there a way for me to know what I can put onto the folder that shows up in the windows file explorer. Sometimes, I will put a folder in /sdcard, and it won't show up on the computer. It is really confusing sometimes when I need to move certain files to my computer.

Microsoft's MTP is a ****ty protocol, that's just my opinion.
The new files won't show up if it's not been read by the Media Server (I think), you have to do a media scan and replug the phone. If you still don't see it, just reboot the phone and let it scan the files for a few seconds before plugin it in. You should be able to move any files to the phone, just ignore the warning if it say the file might be incompatible.
sent from xda premium app

I often have to disable/uninstall the ADB device in Windows device manager to get MTP working...but that was on a Windows XP machine.

afff53 said:
Wow. I just plugged it in to uninstall the drivers and it started working. I didn't do anything to the phone or the computer, its the first time it has worked after hours of trying to get it to show up. Thanks for the help, sorry for the trouble.
Click to expand...
Click to collapse
Something similar happened to me once. I reinstalled the drivers several times unsuccessfully and then it just started working. It seemed like a Windows 8 issue to me but I never determined for sure what caused it. Good luck.

I solved my problem at this way. Maybe it will help.

How to fix my GT-S5360

About 5 months ago, I installed the Hyperion ROM (http://forum.xda-developers.com/showthread.php?t=2457022) on my phone, and I had no problems wit it. Yesterday, I decided to install the Lenox Evolution V2 ROM (http://forum.xda-developers.com/showthread.php?t=2462914), and I must have installed it incorrectly, because now my phone appears to have no ROM. It won't let me access recovery mode, only download mode, and Odin won't recognize the device. Is there any way for me to fix my phone?

njmakunura said:
About 5 months ago, I installed the Hyperion ROM (http://forum.xda-developers.com/showthread.php?t=2457022) on my phone, and I had no problems wit it. Yesterday, I decided to install the Lenox Evolution V2 ROM (http://forum.xda-developers.com/showthread.php?t=2462914), and I must have installed it incorrectly, because now my phone appears to have no ROM. It won't let me access recovery mode, only download mode, and Odin won't recognize the device. Is there any way for me to fix my phone?
Click to expand...
Click to collapse
Download USB driviers from internet and try to change the cable or port.
if not working send it to a repair center

There is no reason that odin won't recognise your device unless you have not installed the proper drivers. Search Web for Samsung adb drivers and install them.
Sent from my ST15i using Tapatalk

njmakunura said:
[...]Odin won't recognize the device.
Click to expand...
Click to collapse
Did it recognize the device in the past? Odin shouldn't be depended on Kernel/Rom, as long as you have the correct drivers.
Here is a good albeit slightly outdated guide (just use the up to date versions).

KaffeeKiffer said:
Did it recognize the device in the past?
Click to expand...
Click to collapse
Normally, when I want to access the files on my phone, I take out the memory card and use a card reader to access my files.So, I don't know if this has always been the case or not.
Souroking said:
Search Web for Samsung adb drivers and install them.
Click to expand...
Click to collapse
I have re-installed the samsung drivers, and every time I plug the phone into the computer, I get this notification:
{
"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"
}
mohamedrashad said:
Download USB driviers from internet and try to change the cable or port.
Click to expand...
Click to collapse
I have tried several USB ports on the computer, and Odin still won't recognise the phone.

njmakunura said:
Normally, when I want to access the files on my phone, I take out the memory card and use a card reader to access my files.So, I don't know if this has always been the case or not.
Click to expand...
Click to collapse
Okay, good to know ^^.
Did you shut down all KEIS processes before starting Odin?
Which version of Odin are you using?
I've problems when using a version > 3.09, so maybe "downgrade" and use an older version.
Another possible problem: defective cable. I've heard that Odin may be a bit picky even if the cables connects fine under windows.

I too have the same problem ..... I ve tried everythng ...bt it is not at all recognized ... Bt earlier.. I ve twice flashed using odin...
Sent from my Q3000 using xda premium

Might be a problem with your pc try on a different one once.
And make sure you are not using a hub or an usb extender.
Sent from my ST15i using Tapatalk

Uninstall/reinstall drivers/KIES.
Use Windows XP/7
If you have the possibility: Try the process in a VM.

U can connect usb in deffrent port
And u can Get latest version of keis on the pc /u might need to remove any usb drviers like said before
If win 8/8.1
Run installation on prems of Admins
And compatiblty of win 7
If win 7 just run as admin

Try to use odin v1.85 connect phone to pc w/o the battery, then insert the battery while holding the volume down and home key

Thank you for all your help @mohamedrashad @Souroking @KaffeeKiffer @myaservip @epipok
I managed to get my phone working again! :victory:
I uninstalled Kies and drivers, re-installed Kies and drivers, and connect in different USB ports until it worked. I think the problem was to do with the drivers not being correctly installed (maybe the installation process was terminated before completion?)
Thank you again for everything! :smile:

[Q] Cable data transfer issue - Can only pass data in fastboot

When I plug my Nexus 4 into a PC (only tried Win7 so far but multiple systems) Windows reports 'The USB device has failed, please remove device'. It repeatedly tries to communicate with the Nexus 4 while plugged in and connects and disconnects every few seconds but at no point is recognized as a Nexus 4 or do I get a chance to install drivers. This occurs with USB debugging on/off, MTP on/off, CWM/TWRP USB mounted or not. I have tried various ROMs all with the same result. It still charges though.
I recently changed the USB daughterboard as the socket was becoming temperamental while charging. I can't remember the last time I transferred data with a cable as I normally use bluetooth, wireless FTP etc so I can't be sure the problem has only been occurring since installing the new USB board.
Interestingly enough, I discovered after not being able to boot a ROM, that I could still push data to the device via fastboot. To me it seems if the hardware was faulty then it would not allow data to pass in any mode. Correct me if I'm wrong but as far as I know USB always uses pins 3+4 for data and 1 + 4 for +5V and ground respectively so it's not like the hardware is being used differently.
I have ordered another LG USB daughterboard along with a new battery as mine is on deaths door, so I'm hoping this new USB board will solve my problem...
Do you know why can I only pass data over the USB and get the device recognized in bootloader using fastboot?

Have you checked your usb in device manager when you're normally booted or in recovery? It uses different usb drivers than when you're in the bootloader. Check to see if its a driver issue.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Have you checked your usb in device manager when you're normally booted or in recovery? It uses different usb drivers than when you're in the bootloader. Check to see if its a driver issue.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
This is half the problem. Because Windows enters a sort of loop where it keeps trying to recognize the device, it does not show up for more than a split second in device manager and when it does, it is recognized as unknown device. If I am fast enough to right click on the unknown device and try to manually point drivers at it, Windows tells me the best drivers are already installed. Obviously Windows has no idea what my Nexus is at this point.
I have connected in bootloader and the phone shows up normally in device manager as Android Device etc. I have updated the drivers manually pointing Windows to C:\android-sdk\sdk\extras\google\usb_driver but this does not help trying to connect in fully booted MTP mode when the recognition loop starts again.
I have been working my way through this thread with no luck so far. Other people appear to have had the same problem and just given up.
I am going to try my Nexus on an XP machine tomorrow and see what happens.

I recommend using the nexus root toolkit and following the driver installation guide. I've had similar problems in the past but reverting to this program and following the basics has always led to working results.
Sent from my Nexus 4 using XDA Free mobile app

Solved!
Ok, so I know this may not help many people apart from simply reiterating the fact USB sockets do fail so if you get stuck with Windows recognizing the device bear this in mind. Although one thing I have learned is that it is possible for such a failure to occur which allows data to still be passed in boot loader but not in MTP mode. I would still be interested to hear if anybody knows why/how this is possible?
After hours of trying different combinations of peoples methods of installing drivers It turns out the USB socket/daughterboard was to blame.
I replaced both the USB board/socket and battery and my Nexus is like a brand new phone. As soon as I plugged it in to my PC (using an old non LG cable) Windows recognized it, installed drivers and mounted it ready for me to browse. No manual driver installation required. Data can be transferred normally. It just works as I expect an Android phone to.
Thank f**k for that
{
"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"
}

[Guide] Fix for device not working in fastboot / unable to install official driver in Windows 10 / 11

If you are getting the error as in the screenshot below, this solution is for you.
1. Download the attachment "Generic Driver.zip" and extract it
2. Click on "Update Driver" in the dialog in the screenshot.
3. Browse my computer for drivers
4. Let me pick from the list of available drivers
5. Show all devices
6. Have Disk
7. Point it to the extracted folder and click OK.
8. You will see 3 new items in the box now Choose "Android bootloader interface" in the list and click next
9. It will show you a warning. Ignore it and press Yes
That's all! Enjoy
{
"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"
}

Oneplus USB drivers were not enough on my win11 pc but your method worked, thanks very much

Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.

anuahmed89 said:
Hi,
I am facing the same issue, after updating to windows 11 my one plus 7T driver stopped working...i tried all the possible solutions I the forums, from updating driver of Generic driver, Qualcomm drivers, and USB driver...nothing has worked...in fact I saw many members posting to update the android driver in device manager in the other devices tab which solves the issue...many have an android option but on my device there isn't any android option..i don't know what to do..I'm very frustrated and tensed as to what needs to be done...please if any on can help me personally it wud be really great.
Click to expand...
Click to collapse
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com

in my case, the other devices it doesnt show when i connect it with usb and it also doesnt show USB CONNECTED notification on my status bar? it would be really helpful if someone can help with the fix, Thankks and Appreciated.

I just went through the same exercise. However, I did not want to download drivers from unknown source (or even worse - run some *magical* driver fixing executable), right?
I am using Samsung Galaxy Tab A7 Lite and the ADB drivers came from Samsung and adb was working.
However, once I put the tablet in fastboot mode the USB re-enumerated and Samsung drivers didn't cut it!
Inspecting DeviceManager gave me the USB\VID_18D1&PID_4EE0 and Google search shows this is actually a Google VID. The rest is history: Downloaded (signed!) driver from Google (specifically this) and voila - life is good!
I hope this may help others avoiding wizardry with unsigned drivers.

I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance

Dieppy said:
I didn't think I'd get to ask something like this but here I am:
I can't get the phone to be detected while it is bootloader mode to my PC. I always updated and rooted my phone without any issue but with f.15 I can't.
All drivers are fine because I've rooted f.13 like one month ago so i really don't know what to do.
I remember once I had to install "Android Bootloader Interface" but now when I'm in bootloader mode my PC doesn't see the phone. No "unknown android" under window devices manager, nothing.
When the phone is ON I see "ADB Interface" in devices manager, when it's OFF nothing shows up in the list like the PC doesn't see I've plugged my phone.
What am I missing?
Thx in advance
Click to expand...
Click to collapse
Not sure if this will help but I would run "usbview" to see what is enumerated. Since the tree is very bid these days with many hubs and USB devices already connected you might first plug-in anything known to the same USB port to see where on the tree it sits. Then plug-in the phone and look at the same spot ("bark at the same tree" ;-) )
If you nave a NIX system "lsusb" will do you similar service. Both are driver independent. Then (if the phone is recognized) get the VID and PID and google what got enumerated and you may end-up with the right driver.
In the case nothing is detected at this low level the only explanation I would have is that the boot doesn't initialize the USB interface on the phone. That would be weird and nasty.

Hey
While trying to install drivers using have disk I encounter a problem. After navigating to the android-usb.inf file I press ok and it rolls back to asking me where is the disk. I tried disabling driver enforcement but to didn't work. It's like windows doesn't want to work. I am using a win 11 copy via parallels on an M1 Mac.