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"
}

[HELP] My Nexus 4 is no longer recognized

Hello, since the update to android 4.3 my Nexus 4 is no longer recognized by my Windows 7/8 computers.
I have tried many drivers and software NRT, I also formatted several times.
I've used both connections (MTP and PTP) and USB debugging mode.
Several micro usb cables
Now I know what to do and the problem is that the phone to bootloader unlocked so I do not know if Google agree to exchange it for free.
Desolated if I make mistakes but English is not my native language
Thank you in advance

I don't think you need to exchange it and Google should exchange it even if the bootloader is unlocked, provided you factory reset it I guess. And to re-lock the bootloader you just have to boot it into fastboot mode and type in the command line: fastboot oem lock
(Just follow this guide to return the phone to stock if you need: http://forum.xda-developers.com/showthread.php?t=2010312)
As for recognizing the device, maybe the MTP driver become unrecognized or conflicted, check in the Device Manager of your computer it should be called "Nexus 4" under Portable Devices. If it's not, right click on it and uninstall it. Then reconnect the phone and let it reinstall the driver, also try switching on and off USB Debugging option in the Developer mode.
If that still don't work, try this method: http://forum.xda-developers.com/showpost.php?p=35667806&postcount=23
Because this is likely a driver issue even if you get a new Nexus 4 your computer still might not recognize it. The issue is likely on your computer side, unless your phone's microUSB port is damaged somehow.

Thank you for answering.
I tried the command to lock the bootloader but it does not work because my device is not recognized
That catches image
{
"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"
}

You need to install the adb/fastboot driver, again, follow the link I posted for instruction. But you can download the Universal Naked Driver here: http://forum.xda-developers.com/showthread.php?t=1996051
sent from xda premium app

I tried to update the drivers but Windows told me that the driver is already up to date

Uninstall it and also check the option to delete the driver, then rescan the devices and reinstall it.
sent from xda premium app

Without success

In that case I suggest do a clean Windows 7 installation and reinstall the drivers on a clean system . Or wipe out Windows completely and install the latest Ubuntu which will detect your device automatically.

OK I installed ubuntu, I 'll let you know

I just tried the live USB but it does not work ... I think I am forced to call Google for an exchange

androboy06 said:
I just tried the live USB but it does not work ... I think I am forced to call Google for an exchange
Click to expand...
Click to collapse
Did you try to update sdk manager, provided it is installed on your C: drive?
This 1st step has proven to be helpful for re-installing drivers which let you access adb and fastboot.
Bonne chance, mon ami

Yes, the SDK is installed and the drivers google
Merci

androboy06 said:
Hello, since the update to android 4.3 my Nexus 4 is no longer recognized by my Windows 7/8 computers.
I have tried many drivers and software NRT, I also formatted several times.
I've used both connections (MTP and PTP) and USB debugging mode.
Several micro usb cables
Now I know what to do and the problem is that the phone to bootloader unlocked so I do not know if Google agree to exchange it for free.
Desolated if I make mistakes but English is not my native language
Thank you in advance
Click to expand...
Click to collapse
I had simular issue.However if i am connected to USB and activate USB debugging, then windows sees the Nexus4 again as an MTP device, and stops as soon as i disable it. I know you said you tried that but still, thought i'd let you know.

I've ssay but thank you anyway

androboy06 said:
I just tried the live USB but it does not work ... I think I am forced to call Google for an exchange
Click to expand...
Click to collapse
Don't exchange it. After uninstalling the drivers, go to pdanet and get the drivers there. I was having the same issue and that fixed it

I've tried, maybe my problem is hardware and not software

androboy06 said:
I've tried, maybe my problem is hardware and not software
Click to expand...
Click to collapse
can you be precise bro
is it windows 8 or windows 7??

I have two PCs, one with Windows 7 and one with Windows 8

USBDView(download it), remove anything android and nexus involved, reboot and replug
Sent from my Nexus 4 using xda app-developers app

Hello, I have the same problem.
My phone is in the official service center,and the last information I have is that it needs logic board replacement which costs aproximately 230 euros.
They would repair it under warranty if it wasn't rooted and flashed with TWRP. Of course, I dont want to pay that amount of money, so I'll try to find to buy a N4 with cracked screen and/or back and take the board from it.
So, if anyone has the same problem, the only solution is replacing the logic board or using ADB over wifi if the kernel supports that feature. Nothing else will work

[Q] my pc cant read my N4 and accidentally wiped my storage

my problem started after i updated to oct 7 cm10.3 nightly. my pc and my mbp cant read my nexus storage.
searched for this problem and found some few n4 users that experienced this but my main problem is there is no android device listed on my device manager.
i checked for all possible solutions:
- uninstall driver on device manager and reconnect the phone to install the driver automatically (but theres no android device listed)
- changed the storage settings as to connect to mtp
- restore factory settings and wipe data
- tried different data cables
- changed my rom from cm to pa
- restart phone
- push adb but device not found (but my pc doesnt recognize my phone)
- turned on/off usb debugging (still cant read)
then out of frustration, i wiped my storage data completely
i cant flash any roms, no files found
i cant push adb because my pc cant find my phone even in recovery
any ideas? thanks in advance.

Boot into recovery and you should be able to see your device in ADB.
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 03:48 PM ---------- Previous post was at 03:48 PM ----------
Nvm, just read the end of your post haha. Are you on TWRP or CWM?
Sent from my Nexus 4 using Tapatalk 4

I had a quite similar problem after trying to install adb drivers (mtp wouldn't work). This is how I solved this:
Follow this guide (only the first part on installing adb driver). Once you have ADB drivers installed, go to device manager, right click on android adb device, choose update driver, pick from a list of device drivers on your computer and choose "MTP USB Device". Not only did I get storaging capabilities back, it preserved adb driver as well... found this method by frustratingly trying random things.

manpildo said:
I had a quite similar problem after trying to install adb drivers (mtp wouldn't work). This is how I solved this:
Follow this guide (only the first part on installing adb driver). Once you have ADB drivers installed, go to device manager, right click on android adb device, choose update driver, pick from a list of device drivers on your computer and choose "MTP USB Device". Not only did I get storaging capabilities back, it preserved adb driver as well... found this method by frustratingly trying random things.
Click to expand...
Click to collapse
ill try this one. thanks for replying.

MikeyCriggz said:
Boot into recovery and you should be able to see your device in ADB.
Sent from my Nexus 4 using Tapatalk 4
---------- Post added at 03:48 PM ---------- Previous post was at 03:48 PM ----------
Nvm, just read the end of your post haha. Are you on TWRP or CWM?
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
my desktop cant recognize my phone, even in recovery. im on cwm

manpildo said:
I had a quite similar problem after trying to install adb drivers (mtp wouldn't work). This is how I solved this:
Follow this guide (only the first part on installing adb driver). Once you have ADB drivers installed, go to device manager, right click on android adb device, choose update driver, pick from a list of device drivers on your computer and choose "MTP USB Device". Not only did I get storaging capabilities back, it preserved adb driver as well... found this method by frustratingly trying random things.
Click to expand...
Click to collapse
hey, i tried it and still doesnt work.
my laptop sees it as an unknown device and even if i browse for drivers, can' install.

up

Water Dispenser said:
up
Click to expand...
Click to collapse
Have you tried the universal naked driver?
Link
Or in the past I've used WUG's tool kit just for the driver installation part WUG's
What OS are you using on your PC

mrhiab said:
Have you tried the universal naked driver?
Link
Or in the past I've used WUG's tool kit just for the driver installation part WUG's
What OS are you using on your PC
Click to expand...
Click to collapse
im using win7 and win8
when i plug my phone on win7, nothing happens.
but when i plug it in on win8, this shows up
{
"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"
}
then this shows up on the device manager
then if i install any adb driver, either wugs toolkit or nexus 4 toolkit, etc. this shows up
and then this again

I'm currently having the same issue now, on cm10 4.3 and now my crap doesn't want to read. I switched to another lap top and I'm keep getting this. I even tried switching USB cables and no luck at all.
Sent from my Nexus 4 using xda app-developers app

Android SDK?
Nexus 4 - PA rom and franco kernel

reiko09 said:
I'm currently having the same issue now, on cm10 4.3 and now my crap doesn't want to read. I switched to another lap top and I'm keep getting this. I even tried switching USB cables and no luck at all.
Click to expand...
Click to collapse
and now my problem is how will i flash a rom
be careful not wiping your phone.
also try what others told me, flash to stock rom. it might fix the issue
and also, if that fixed it, let us know. :good:

[GUIDE] adb and fastboot drivers for Windows

If someone has problems installing the official Motorola adb and fastboot drivers for Windows, try the following, this works for me:
1. download the UniversalADB driver from @Koush here: https://github.com/koush/UniversalAdbDriver
2. install it
3. locate the file android_winusb.inf in the folder (may vary) x:\Program Files\ClockworkMod\Universal Adb Driver\usb_driver
4. open it with any texteditor
5. add the following two lines (somewhere in the devices section) and save the file:
Code:
MotorolaADBInterface = USB_Install, USB\VID_22B8&PID_2E76&REV_0228&MI_01
MotorolaBootLoaderInterface = USB_Install, USB\VID_22B8&PID_2E80&REV_0100
6. let Windows install this driver from koush's directory once in adb mode and once in fastboot mode (two drivers!)
7. enjoy!

Work fine thanks

Is the phone recognized by RSD Lite in fastboot mode with these drivers?
I have the Motorola drivers, using Windows 7 SP1 32-bit.
With USB debugging enabled I get a "Mot Composite ADB Interface" device in device manager (Driver Version 2.0.1.0).
The phone can be seen by 'adb devices' and in fastboot by 'fastboot devices' however using RSD lite 6.1.5 no device appears.
{
"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"
}

t-bon3 said:
The phone can be seen by 'adb devices' and in fastboot by 'fastboot devices' however using RSD lite 6.1.5 no device appears.
Click to expand...
Click to collapse
Got the same with the universal ADB/fastboot drivers damn.
[edit]
The MotoG PID is missing in PST.ini and/or sdk_common.ini, maybe we have to add it manually or wait for a new RSDlite

hi,
have you some newz about new RSDlite ?(maybe i'm too impatient ... )

Worked great. Thank you

maty3ux said:
hi,
have you some newz about new RSDlite ?(maybe i'm too impatient ... )
Click to expand...
Click to collapse
Not yet, last version is 6.1.6

I do not understand this instruction:
shaftenberg said:
let Windows install this driver from koush's directory
Click to expand...
Click to collapse
Windows doesn't attempt to do anything when I connect the phone in ADB mode. Device Manager lists XT1034 under Other devices and says "The drivers for this device are not installed. (Code 28)". If I do "Update Driver Software" manually and direct it to the "ClockworkMod" directory, Windows says it cannot find driver software for the device. If I right click on the "android_winusb.inf" file and choose Install, Windows says the "file doesn't support this method of installation".

adb devices does't see my moto g
fastboot devices yes, but adb devices only says List of devices attached.
Any help will be appreciated

The latest update of UniversalAdbDriver does not require those lines to be added. Moto G device configuration is added by default
Tested in win7 64bit.

Thank you!!
it works for me
i installed Motorola device manager and this application
reversegear said:
The latest update of UniversalAdbDriver does not require those lines to be added. Moto G device configuration is added by default
Tested in win7 64bit.
Click to expand...
Click to collapse
that's right .. i didn't do that too and it works

I've tried this and when I try to install it, it says "The INF file you selected does not support this method of installation." What do I do?

Didnt work for my moto g
sir, i am really new at this backup thing.
i just want to backup my injustice save game, so that i can restore it to previous point if something goes wrong.
i downloaded latest version on universaladbdriver but still my laptop didnt recognised my MOTO G.
i want to use HELIUM/CARBON for backup and i cant proceed till this problem is removed
please help me, i am new to xda as well.
THANKS
my os is win7 32 bit

hey
same problem i cant install adb or motorola drivers in my pc windows 7 64bit. the links with drives dont work for me..any solution? i want to unlock my bootloaderrrrrrrrrrrr :silly::silly::silly: (when i start to install the adb drivers stuck )
https://www.youtube.com/watch?v=RDA8PpPSFuk here i found solution for me i hope u help guyz(turn the music off )

Gronnd said:
adb devices does't see my moto g
fastboot devices yes, but adb devices only says List of devices attached.
Any help will be appreciated
Click to expand...
Click to collapse
Same problem here how do you solved this issue? wand to flash stock via rsd lite but he doesnt recognize my phone..

nuri-d said:
Same problem here how do you solved this issue? wand to flash stock via rsd lite but he doesnt recognize my phone..
Click to expand...
Click to collapse
To solve this when u are in ADB go in device manager, find ur phone with yellow exclamation mark ( !), right click, insta driver-> manual-> android single sooner ADB interface! It will work like a charm!
Sent from my XT1032 using XDA Free mobile app

I had a similar problem on W7 x64, no driver available for my phone (Moto G LTE, XT1039) even with the Universal ADB driver from CWM and the two lines of the first post added in the INF file.
But, you can notice that all Motorola phones in the android_winusb.inf file refer to the same driver : MotCompositeInterface.
So I went to the Device Manager, found my phone, chose to Update the driver, Find a driver from my computer, Choose from List (sorry if the names are not accurate, my Windows version isn't in English).
Then, you can select ClockworkMod, scroll down to Mot Composite ADB Interface and choose it as your driver.
It worked for me (both in adb and fastboot mode), I was able to unlock my bootloader and flash a recovery using it.
Hope this helps !

Hi, I tried all the solutions in this post unsuccessfully, but I found one here: stackoverflow.com/questions/22217792/android-moto-g-mobile-doesnt-show-in-the-devices-list-of-eclipse
that is the simplest and the only one that worked for me.
Download 'Adb Driver Installer' from here adbdriver.com/downloads/
after this connect your Moto G and start the AdbDriverInstaller.exe it will list your device and then press install.
Click to expand...
Click to collapse

[Q] [HELP!] softbricked, can't load files, what to do?

So I was attempting to load Lollipop onto my Nexus 4, and stupidly was multi-tasking at the time. I wiped the cache, data, the system, dalvik, etc in preparation for loading the new ROM, GAapps, etc. Then when I tried to install them from a zip, I realized the really stupid error I made - I had also wiped the sd card. So now I have no installed ROM, and a completely blank sd card and phone, and of course it is in a bootloop. I've looked all over, and all of the answers seem to be the same - either push the files on, use sideload, or if all else fails, use the Wugfresh toolkit to restore it to factory. Sounds great. Except now windows can't see my phone and I can't copy files to it, push files to it, reach it through adb, etc.
- The phone turns on, and I can reach the bootloader and recovery.
- Windows recognizes that a device is attached, but then tells me there is a problem with the drivers. I have run the full driver install from Wugfresh with the Google drivers, and it says it is fine, but any time I connect the phone, it has an error.
- Through device manager, I've updated drivers to various types (standard MTP, android ADB, etc) and it usually works successfully, but the phone still doesn't show in explorer and adb lists no attached devices.
Any ideas? Thanks for your help.

ahs646 said:
So I was attempting to load Lollipop onto my Nexus 4, and stupidly was multi-tasking at the time. I wiped the cache, data, the system, dalvik, etc in preparation for loading the new ROM, GAapps, etc. Then when I tried to install them from a zip, I realized the really stupid error I made - I had also wiped the sd card. So now I have no installed ROM, and a completely blank sd card and phone, and of course it is in a bootloop. I've looked all over, and all of the answers seem to be the same - either push the files on, use sideload, or if all else fails, use the Wugfresh toolkit to restore it to factory. Sounds great. Except now windows can't see my phone and I can't copy files to it, push files to it, reach it through adb, etc.
- The phone turns on, and I can't reach the bootloader and recovery.
- Windows recognizes that a device is attached, but then tells me there is a problem with the drivers. I have run the full driver install from Wugfresh with the Google drivers, and it says it is fine, but any time I connect the phone, it has an error.
- Through device manager, I've updated drivers to various types (standard MTP, android ADB, etc) and it usually works successfully, but the phone still doesn't show in explorer and adb lists no attached devices.
Any ideas? Thanks for your help.
Click to expand...
Click to collapse
Press and hold Volume + and Volume - with Power toghether.
Stay press until it don't self-reboot itself.
When the logo about bootloader will load up, you can choose what to do :
1 ) Reinstall the stock roms 4.4.4 (https://dl.google.com/dl/android/aosp/occam-ktu84p-factory-b6ac3ad6.tgz)
2) If you still have a modify recovery (CWM or TRWP) you can run it and install zip from sideload. Put the rom zipped you wanna install where did you have adb tools and run "adb sideload <file.zip>" and wait it should be install.
If that dosen't work, you need to use download mode from LG ( for the moment i can't found a guide to do it, check on XDA / Google).

Thanks LainX, but as I said in my original post, my pc can't see the phone, so ADB can't connect and I can't get the new files over to it.

ahs646 said:
Thanks LainX, but as I said in my original post, my pc can't see the phone, so ADB can't connect and I can't get the new files over to it.
Click to expand...
Click to collapse
Did you try download 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"
}

I don't think I've seen this "download mode." Where is this - on the phone (in recovery?) or through adb or sideload. The problem seems to be (and I see there are a few others right now with the same problem) that windows sees that the phone is connected, but then there seems to be a driver error such that the device doesn't show up in explorer, and abd and fastboot can't see the phone either.
I've tried different drivers, but haven't systematically gone through every single option so far, which is my next stop. Is any one driver option more failsafe than the others? Also, perhaps related - in the past, any time I've installed the drivers and connected to my phone from my pc, it never seems to "stick." Invariably, I can't access the phone through MTP after a short while (maybe after a reboot?). Recently I found updating the driver to just a Portable Device/Standard MTP USB device driver (i.e. not Google, Samsung, Android, etc) made it work. So now I feel the driver troubleshooting part is even longer and more complicated - go through all of the uninstall/reboot/install with the four Android options, then all of the generic Windows options. So I was just hoping that someone out there might have already cracked this and could point me in the right direction.
Also, in digging through some posts on reddit on related problems, someone said that Windows Media Player is somehow critical for MTP functionality. Is this the case? I had never heard this before. I don't have WMP installed, and in trying to install it, have come up with a Windows error. I'm not clear on the relationship between MTP and ADB/fastboot. Is MTP necessary for the file transfer, or is that not relevant here?
And one final question - to use adb/fastboot, do I need to be in bootloader or in recovery? To install the drivers, do I need to be in either bootloader or recovery?
Thanks so much.