Related
USB Drivers are let your PC communicate with your device.
If you are executing some ADB Commands, you will need USB Drivers installed which will let the ADB server on your PC communicate with the ADB client on your device. If there are no USB Drivers installed on your PC, you will not be able to perform activities on your device via the PC.
First of All I would recommend you to install Universal ADB Driver Installer.The Universal ADB Driver installer detects your phone and installs the ADB drivers for it.This tool developed by drsmart is your solution to the “device not found” error you might get on executing ADB commands.
Universal ADB Driver Installer Download Link - http://adbdriver.com/downloads/
USB DRIVERS
1.SAMSUNG:
--- http://www.samsung.com/us/support/downloads
2.LG
---http://www.lg.com/us/support/mobile-support
3.HTC
---https://support.htc.com/en
4.SONY
---http://developer.sonymobile.com/downloads/drivers/
5.ASUS
---http://support.asus.com/download/options.aspx?SLanguage=en&type=1
6.MOTOROLA
---http://www.motorola.com/sites/motodev/us-en/motodev_lp.html
MORE DEVICES WILL BE UPDATED
Thanks for the info. I tried the univ adb driver installer but it showed I already had the right driver installed. Windows explorer can see my phone but other apps like HTC Sync or myphoneexplorer can't. This only happened after I rooted & installed a new rom. Maybe the rom is faulty...
I want Google nexus driver
any one can help me ?
mt6572 driver
Please add driver for mt6572 device
thx. very usefull!
thanks for the updated links.
Gole Maryam said:
I want Google nexus driver
any one can help me ?
Click to expand...
Click to collapse
an universal driver for all Nexus Devices (Phones and Tablets) can be found here:
http://forum.xda-developers.com/showthread.php?t=2513339
No access to USB debug
I give up and need some professional help...Ya both kinds.
Here we go, I have the Galaxy 3 d2att I747
Rooted
I was running CM 10.2 with latest nightly, I think 20131208 and decided to update to CM11 via my Cyanogenmod updater but before I did I had read somewhere I should change from CWM recovery to TWRP so I downloaded Goomanager and updated to the TWRP version for my phone then went for the KitKat update and thats when the trouble began.
I am now stuck in a boot loop even if I try to boot into TWRP all I get is the TWRP boot logo then straight into boot loop again. I am almost positive I did a factory wipe as well as cache/dalvik.
Not being able to use TWRP to get into recovery I thought I would just use Odin but I can't get any of my laptops to recognize the phones USB, I just get the windows usb driver error and have tried to install the drivers manually via device manager using my samsung 7 chronos with windows 8.1 and my acer with windows 7. I updated drivers using Samsung Kies and from the website, no luck.
I also ventured into an area that I have no expertise in but I guess thats how we learn so I downloaded the Android SDK thinking I could use it to download and install the google USB drivers that way, but I can't get out of boot loop to make sure USB debugging is checked. The only thing I can access is the stock download mode which would be great if I could use the USB connection.
What am I missing? Any suggestions?
USB Not Recognized Error
I noticed that my phone suddenly stopped being recognized on both my Windows 7 and Win8 laptops. I have been trying to fix it with the drivers but to no avail. However, I plugged my phone in with a different USB cord and voila it was recognized and working. Maybe this could possibly be a simple fix.
My computer stopped recognizing my Skyrocket
Hi Everyone,
I also am having trouble with my win 7 computer recognizing my Skyrocket suddenly. I have been using several KitKat roms and they have been working just fine, except for some reported bugs that the CM devs are working on. I even was able to connect to the computer and explore both my internal and external drives. Then suddenly that stopped and the computer gave me a need to get drivers warning. I've tried to download drivers from Samsung and the computer says they are already installed. I also tried the universal driver download and got the same message. Any help would be appreciated. Like the others on this forum, I wouldn't be able to odin if I got in trouble.
Thanks for your concideration,
drewfs7270
I switched to a different rom and now it's working again !
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Thanks.. :good: usefull
Also, any mobile manufacturer website has guides or direct downloads for drivers. Otherwise uni drivers suffice.....
Sent from my Nexus 5 using xda app-developers app
mtk preloader driver unable to install/unplugged appears
mt65xx unplugged when I try installing my device, I tried uninstalling all preloader vcom drivers in my laptop then restart and when I try to connect my device mtk mt65xx preloader just pops up in device manager then suddenly disappears and unknown device shows instead. I also tried manually update driver for unknown device then select the folder where my mtk driver is saved still unsuccessful? I've also searched and tried many other ways out there still no luck. Can anybody give me a solution? By the way i'm using windows 7 x64.
Delted
Edit: Deleted
soft brick
I face bad experienced, the tablet can not boot ( after install TWRP ) but enable to enter the fastboot mode and can be detected by the computer as android adb interface but adb can't communicated with the tablet. (list of devices atached)
I do have a backup file ( I make it before soft brick, I make backup using dd command, because I don't have cwm/twrp recovery ).... but how to flash it ? Tablet chipset is wonder media 8980 OS android 4.2.2
I can not flash it by adb/fastboot.
Maybe someone here can give me a little guide for how to....
I really appreciate for your kindness
Hey, I made an expirience, which might help other users as well.
I have a Sony device (Z1C) and use Windows 10, maybe this will help for other brands and for other Windows 10 users.
I installed drivers for my device and was able to use adb. When I put the phone into fastboot mode, it was not recognized anymore. I found out, Sony has a seperate (updated, maybe?) driver for fastboot mode. When I tried to install this, the driver was not signed and Windows refused to install it. However, you can enter the UEFI (successor of BIOS) and enable installation of unsigned drivers (at own risk). Then I was able to install the fastboot driver and controll my phone in fastboot mode as well as in adb mode.
In conclusion: You might think you installed drivers, because you did, but maybe you did not.
Even on LineageOS page, many people fail to mention that, you DON'T and SHOULDN'T install any generic or universal ADB driver if you have Samsung device. As you can just install Samsung USB Drivers officially from Samsung site. Samsung USB Drivers already contain ABD interface driver just fine so Universal ADB driver is redundant for Samsung phones.
Hi guys, I need your help.
I installed ClockWorkMod v6.0.1.9. I've done that with wkparts omaptools and fastboot. Any doubt, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2045942
and this:
http://forum.xda-developers.com/showthread.php?t=1978543
Ok, thats fine, it worked. Now, when I boot into recovery mode (Holding VOLDOWN + 3D + Power) I get into ClockWorkMod.
So, I connect the USB cable in order to access the phone via ADB. But, when I look into device manager, there is a unknown device called "LGE COSMO USB Device" and I couldn´t figure out what driver I have to install. I installed LG United Driver and it didn´t work.
Any suggestion? Thks
adrianohck said:
Hi guys, I need your help.
I installed ClockWorkMod v6.0.1.9. I've done that with wkparts omaptools and fastboot. Any doubt, take a look at this:
http://forum.xda-developers.com/showthread.php?t=2045942
and this:
http://forum.xda-developers.com/showthread.php?t=1978543
Ok, thats fine, it worked. Now, when I boot into recovery mode (Holding VOLDOWN + 3D + Power) I get into ClockWorkMod.
So, I connect the USB cable in order to access the phone via ADB. But, when I look into device manager, there is a unknown device called "LGE COSMO USB Device" and I couldn´t figure out what driver I have to install. I installed LG United Driver and it didn´t work.
Any suggestion? Thks
Click to expand...
Click to collapse
Go to device manager and right klick on the unknown device and hit preferences.
there you go to tab details. there look for device instance path.
USB\VID_1004&PID_61FA&MI_04\6&301C001A&6&0004 == ADB
USB\VID_1004&PID_61FA&MI_02\6&301C001A&6&0002 == USB Serial Port
USB\VID_1004&PID_61FA&MI_00\6&301C001A&6&0000 == Platform USB Modem
Download and install LG drivers ala link section and part 1
http://forum.xda-developers.com/showthread.php?p=39269819
troopii said:
Go to device manager and right klick on the unknown device and hit preferences.
there you go to tab details. there look for device instance path.
USB\VID_1004&PID_61FA&MI_04\6&301C001A&6&0004 == ADB
USB\VID_1004&PID_61FA&MI_02\6&301C001A&6&0002 == USB Serial Port
USB\VID_1004&PID_61FA&MI_00\6&301C001A&6&0000 == Platform USB Modem
Click to expand...
Click to collapse
hi troopii,
i did that. here, i can see this:
USB\VID_1004&PID_D001\2CD00004000000010910D4D11800F00C
What does that mean? Is it ADB?
What am I suposed to do with this number?
Could you help me?
adrianohck said:
hi troopii,
i did that. here, i can see this:
USB\VID_1004&PID_D001\2CD00004000000010910D4D11800F00C
What does that mean? Is it ADB?
What am I suposed to do with this number?
Could you help me?
Click to expand...
Click to collapse
hmm looks interessting, i think you dont have a p920.
ok try a different way.
deactivate on your phone usb debugging.
plug your phone to the pc.
now you should have 2 unkown devices. one cdc serial and one lg cosmo usb device.
that lg cosmo usb device that you now see is Platform USB Modem.
now look at that device instance path and take a note.
now activate usb debugging again. plug phone to pc.
now you should have 3 unkown devices. one cdc serial and two lg cosmo usb device.
look again at the device instance path and if the current matches your note, you have found the "Platform usb modem" again. install driver for it
the other one should be the "android sooner singel adb interface".should be the same also in recovery.
gl
troopii said:
hmm looks interessting, i think you dont have a p920.
ok try a different way.
deactivate on your phone usb debugging.
plug your phone to the pc.
now you should have 2 unkown devices. one cdc serial and one lg cosmo usb device.
that lg cosmo usb device that you now see is Platform USB Modem.
now look at that device instance path and take a note.
now activate usb debugging again. plug phone to pc.
now you should have 3 unkown devices. one cdc serial and two lg cosmo usb device.
look again at the device instance path and if the current matches your note, you have found the "Platform usb modem" again. install driver for it
the other one should be the "android sooner singel adb interface".should be the same also in recovery.
gl
Click to expand...
Click to collapse
But I can´t desactivate USB debugging because I can´t access android in normal mode. I only can access android on Recovery Mode (ClockWorkMod).
I need to install some kind of driver to access the phone using ADB while in ClockWorkMod. I guess this is possible (I read this at http://forum.xda-developers.com/wiki/ClockworkMod_Recovery).
The problem is: when i connect the phone on PC while in ClockWorkMod there is a device called "LGE COSMO USB Device" and i didn´t find any driver that match.
drastic00 said:
Download and install LG drivers ala link section and part 1
http://forum.xda-developers.com/showthread.php?p=39269819
Click to expand...
Click to collapse
Hi,
I installed this two drivers:
LGUnitedMobileDriver_S497CA20_WHQL_ML_Ver_1.0
LGUnitedMobileDriver_S497MA20_WHQL_ML_Ver_1.0
Is that correct?
None of them worked. When I go to device manager, there is still a device called "LGE COSMO USB Device".
Read and follow all details carefully and it will work. You will need to change port to 41 as well as force omap4430 driver to install so it stops blinking.
drastic00 said:
Read and follow all details carefully and it will work. You will need to change port to 41 as well as force omap4430 driver to install so it stops blinking.
Click to expand...
Click to collapse
Hi drastic00, I really appreciate your help and attention.
Let me try to explain my problem: I can´t turn on the phone in normal mode and, of course, I can´t follow your steps. The phone is locked, there is a password to unlock the screen. So, I can´t desactivate the USB debugging because I do not have access to Android.
The only way I have to boot the phone is in recovery mode (ClockWorkMod). But, I need to access the device to copy the data. And it is possible to do that using ClockWorkMod and ADB. The problem is: when I boot my cell phone into recovery mode (now on screen I see the options of clockworkmod) and plug the usb cable, then there is device "lge cosmo usb device" and i can´t access the phone via ADB. I typed "adb devices" and the answer was nothing...
None of the driver install steps require phone to be booted; all driver install steps require battery to be out of the phone. So why can you not install drivers?
drastic00 said:
None of the driver install steps require phone to be booted; all driver install steps require battery to be out of the phone. So why can you not install drivers?
Click to expand...
Click to collapse
I installed all the drivers. When I connect the phone of my friend (a p920 too), it works fine! I can also access his phone using ADB.
Solution found
Thank you guys, I find the solution.
Thanks verry much for manekineko. See:
http://forum.xda-developers.com/showthread.php?t=2028598
It worked when I installed PdaNet+ drivers:
http://pdanet.co/a/
Thanks at all.
Hm. New one on me but good to know.
I recently bought a YU YUPHORIA . When i tried to root it I was stuck at waiting for device. I checked on different forums and somehow everybody was telling about how the ADB drivers are not installed. I tried different methods . I tried to update the Android Composite ADB Interface as they had worked for a lot of other people but they didn't work with my phone. Then i tried to install ADB drivers with the help of Pdanet but the Pdanet was stuck at Trying to install Pdanet on your phone. When i write fastboot commands like fastboot -i 0x2A96 devices my device is recognised. But when i write adb devices my device doesn't show up. Please help because I really need to use this phone for app development purposes but Android Studio is also not recognising my device. I have managed to root my device but can't solve this problem of ADB not detecting my device.
Usb debugging is enabled and i Have tried uninstalling all android drivers . But then the android ADB interface is shown in other drivers with yellow mark and when i try to update it same thing happens "Window unable to install drivers"
Is their any hardware problem with my Device.?
suparv2204 said:
I recently bought a YU YUPHORIA . When i tried to root it I was stuck at waiting for device. I checked on different forums and somehow everybody was telling about how the ADB drivers are not installed. I tried different methods . I tried to update the Android Composite ADB Interface as they had worked for a lot of other people but they didn't work with my phone. Then i tried to install ADB drivers with the help of Pdanet but the Pdanet was stuck at Trying to install Pdanet on your phone. When i write fastboot commands like fastboot -i 0x2A96 devices my device is recognised. But when i write adb devices my device doesn't show up. Please help because I really need to use this phone for app development purposes but Android Studio is also not recognising my device. I have managed to root my device but can't solve this problem of ADB not detecting my device. Is their any hardware problem with my Device.
Click to expand...
Click to collapse
First, be sure you have enabled USB debugging in developer options. Also, you may have to uninstall all android drivers from your PC and then reinstall the specific drivers for your device.
Evolution_Tech said:
First, be sure you have enabled USB debugging in developer options. Also, you may have to uninstall all android drivers from your PC and then reinstall the specific drivers for your device.
Click to expand...
Click to collapse
Usb debugging is enabled and i Have tried uninstalling all android drivers . But then the android ADB interface is shown in other drivers with yellow mark and when i try to update it same thing happens "Window unable to install drivers"
suparv2204 said:
Usb debugging is enabled and i Have tried uninstalling all android drivers . But then the android ADB interface is shown in other drivers with yellow mark and when i try to update it same thing happens "Window unable to install drivers"
Click to expand...
Click to collapse
OK, try to update manually. Select update driver, then choose let me pick, then navigate to where you have the new driver.
Evolution_Tech said:
OK, try to update manually. Select update driver, then choose let me pick, then navigate to where you have the new driver.
Click to expand...
Click to collapse
I mentioned in the post I tried that . But windows shows the same message. I have tried with Google Usb drivers . I have also tried with other mobile drivers of Asus , Htc but same thing happens
Dear all,
Please Help me. My One plus one is on CM12 official rom (rooted). Problem is when I connect my phone to computer and use ADB it is detected (adb devices: number & devices detected) but when in fastboot (fastboot devices : nothing is detected) I check in my device manager (yellow triangle on android ) My problem is why CAN it be detected when my phone is on but NOT during fastboot.
Necessary checks done : USB debugging, Universal driver, SDK installed, USB driver reinstalled again, tried changing usb ports on computer, tried on 2 laptops)
I am helpless, tried checking on forums can not find the answer.
CalvinVeez said:
Dear all,
Please Help me. My One plus one is on CM12 official rom (rooted). Problem is when I connect my phone to computer and use ADB it is detected (adb devices: number & devices detected) but when in fastboot (fastboot devices : nothing is detected) I check in my device manager (yellow triangle on android ) My problem is why CAN it be detected when my phone is on but NOT during fastboot.
Necessary checks done : USB debugging, Universal driver, SDK installed, USB driver reinstalled again, tried changing usb ports on computer, tried on 2 laptops)
I am helpless, tried checking on forums can not find the answer.
Click to expand...
Click to collapse
Have test to fastboot commands?
In fastboot be unplugged
Write
fastboot reboot
for test
Will answer wait for device
Plug device to test
My pc also does not recognise but work fine
with commands
geowolf1000 said:
Have test to fastboot commands?
In fastboot be unplugged
Write
fastboot reboot
for test
Will answer wait for device
Plug device to test
My pc also does not recognise but work fine
with commands
Click to expand...
Click to collapse
Tried adb reboot bootloader then phone boots into fastboot mode but from here..
is total no connection. Tried checking fastboot devices (nothing), fastboot reboot (waiting)
then i tried as u said unplug & plug in (not recognize) from here adb cannot be written anymore. (no more commands can be typed). Tried others like down loading Pdanet ,force install driver..Nothing works. Thinking ,did I corupt the bootloader while I was rooting it last time.?
I think if something was wrong with bootloader you could not either boot .
Do you use antivirus to pc?
Try without antivirus
What happening the false is from computer
Mine is reverse issue. When in fastboot mode, pc recognizes OPO, but when OPO is normally connected to pc, adb is not working. Its charging and can transfer data through USB, but OPO is not recognized through adb commands. Device Manager too recognizes my OPO only when it is in fastboot mode and not when normally connected via USB for data transfer.
I have a software, through which I can REVERSE TETHER my PC's internet to my mobile via USB. Because my OPO is not recognized via USB in normal mode, I can't do that. Any idea, what's wrong with my OPO.
(I have installed Android SDK and google usb drivers, for my OPO to work in fastboot. I have rooted. My pc runs on win7)
mrsureshisha said:
Mine is reverse issue. When in fastboot mode, pc recognizes OPO, but when OPO is normally connected to pc, adb is not working. Its charging and can transfer data through USB, but OPO is not recognized through adb commands. Device Manager too recognizes my OPO only when it is in fastboot mode and not when normally connected via USB for data transfer.
I have a software, through which I can REVERSE TETHER my PC's internet to my mobile via USB. Because my OPO is not recognized via USB in normal mode, I can't do that. Any idea, what's wrong with my OPO.
(I have installed Android SDK and google usb drivers, for my OPO to work in fastboot. I have rooted. My pc runs on win7)
Click to expand...
Click to collapse
Install pdanet+ for win
I rooted my Samsung A9 2018 SM-A920F, but now i have problems with smalipatcher to mock gps. I installed Java, but an error occurs. NO ABD devices found. I tried it with platform tools, in device manager i tried to update drivers, but keeps saying best drivers are installed, but the phone is still not recognised. OEM debug and OEM unlock is on, tried to revoke oem debug as well, but smalipatcher still cant find phone. Tried different cables as well. Someone that can help me?
Add Samsung A9 2018 SM-A920F to this thread's title thus mainly owners of such device get addressed.
Lucvdkant said:
I rooted my Samsung A9 2018 SM-A920F, but now i have problems with smalipatcher to mock gps. I installed Java, but an error occurs. NO ABD devices found. I tried it with platform tools, in device manager i tried to update drivers, but keeps saying best drivers are installed, but the phone is still not recognised. OEM debug and OEM unlock is on, tried to revoke oem debug as well, but smalipatcher still cant find phone. Tried different cables as well. Someone that can help me?
Click to expand...
Click to collapse
What does
Code:
adb devices
return?
jwoegerbauer said:
What does
Code:
adb devices
return?
Click to expand...
Click to collapse
Nothing. Gives no number. I rebooted my usb drivers as well. When I connect the usb and check device manager it adds Samsung Android Phone en when i open it gives Samsung Android ADB interface. My phone does not pop up as Samsung A9 but as MTP-USB-device
Lucvdkant said:
Nothing. Gives no number. I rebooted my usb drivers as well. When I connect the usb and check device manager it adds Samsung Android Phone en when i open it gives Samsung Android ADB interface. My phone does not pop up as Samsung A9 but as MTP-USB-device
Click to expand...
Click to collapse
You have to switch phone's USB mode to ADB.
jwoegerbauer said:
You have to switch phone's USB mode to ADB.
Click to expand...
Click to collapse
OEM unlocking and USB debugging are on, I put default usb configuration on Transferring files. Is that what you Megan? How do I put it on ADB?
Lucvdkant said:
OEM unlocking and USB debugging are on, I put default usb configuration on Transferring files. Is that what you Megan? How do I put it on ADB?
Click to expand...
Click to collapse
Your phone is configured to connect to phone via USB in Media Transfer Protocol (MTP) mode what is for transfering files.
As already said you have to configure phone that it connects via USB in Android Debug Bridge (ADB) mode.
IDK how you can achieve this because I don't have a phone as yours.
Follow my advice given in post #2
jwoegerbauer said:
Your phone is configured to connect to phone via USB in Media Transfer Protocol (MTP) mode what is for transfering files.
As already said you have to configure phone that it connects via USB in Android Debug Bridge (ADB) mode.
IDK how you can achieve this because I don't have a phone as yours.
Follow my advice given in post #2
Click to expand...
Click to collapse
Thanks, My device is not found in platform tools using the adb devices command, but it's on OEM unlock and USB Debugging is on. I added the phone in the tiltle, hope someone had an solution for my problem. Don't understand why it's not working. When I connect phone without the USB debugging it get's recognised, but with debugging mode on, nothing to find
Lucvdkant said:
Thanks, My device is not found in platform tools using the adb devices command, but it's on OEM unlock and USB Debugging is on. I added the phone in the tiltle, hope someone had an solution for my problem. Don't understand why it's not working. When I connect phone without the USB debugging it get's recognised, but with debugging mode on, nothing to find
Click to expand...
Click to collapse
Enabling OEM Unlock and/or USB Debugging simply sets an allowance flag, nothing else. It doesn't configure phone's USB mode.
I tried it on the laptop from work and there the phone is recognized in adb. But sadly I don't have administrator rights on that laptop to open Smalipatcher. Is there an alternative or work around available?