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 I'm trying to upgrade my Cherry Mobile Flare/Karbonn A9+ from ICS to Jellybean and was following the tutorial I found here at http://forum.xda-developers.com/showthread.php?t=2330823&highlight=karbonn+a9 . I have followed the tutorial exactly and when I get to step 5 Download the AP firmware I load the Stock JB Rom folder into Qualfast then click OK boot my phone into green mode and connect it with microusb it just sits there and does nothing and says waiting for devices. I noticed when I plug it in at this stage the phone shows up in my device manager under other devices as "Android" and does not have any drivers installed. I installed the drivers included in the Karbonn driver pack before I started the whole process already, I don't know why it just sits there when I plug it in the green screen mode in Qualfast. I'm a new user and can't post in the tutorial thread yet, any help would be appreciated. Thanks.
Using Win 7 64bit btw.
After looking at a few more tutorials and youtube videos it seems the problem is my abd drivers. When I plug the phone in fastboot(green screen mode) in device manager it is now showing up under adb interace "Android" but it have the yellow exclamation and in properties it says the device is not configured correctly driver is not intended for this platform. Everytime I try to install the abd drivers for win64 is says the drivers are already up to date. I tried uninstalling the device and reinstalling it always does the same thing. Any help?
Well I figured it out, I couldn't get the ABD drivers to manually install no matter what I tried so I installed the drivers via pdanet.exe program. Anybody having trouble installing ABD drivers on x64 just use pdanet to install them.
is it woriking?
Hi everybody, Yesterday my friend and i were trying to upgrade his Samsung Galaxy Core (GT-I8260L) from official stock jellybean 4.1.2 to kitkat 4.4.4 unnoficial. We rooted it succesfully, installed Super SU, and BusyBox. Then we downloaded a TWRP file to flash it through ODIN. the flash was succesfull but when the phone rebooted it got stuck at the download mode. It doesnt boot, and we can't acces the recovery by any means. it just turns the screen on and show the download mode screen (picture attached).
We have tried everything, but the thing is that the device isn't recogogniced by the pc (We've tried in a win 8.1 and win 7 pc, but had no luck.). It fails to install the right drivers. we've tried to download almost every samsung phone drivers, but none of them worked. ODIN also fails to recognize it.
we also tried Heimdall, but when we try to install the drivers it does recognize the phone as 'MSM7x27' for some reason.
We also have problems setting up the 'SAMSUNG Mobile USB CDC Composite Device Driver', failing to make it work every time we tried to configure it (Automatic Windows Driver Install or Downloading it manually).
I hope someone can at least guide us through the solution or suggest a way to fix it.
Thanks in advance
I have a Moto G 2015 installed the ROM CyanogenMod 12.1 it. I went back to the original, made all commands after restarted the device did not call more. I can not even access the Fastboot Flash Mod screen. The computer recognizes the phone driver as Qualcomm HS-USB qdloader 9008. Help me please!
This happened to me with moto g 1st Gen. Did u restore thru a nandroid backup? The solution for me was to reinstall the oem firmware thru the bootloader. But if I understand u correctly, u can't even get the bootloader screen, right?
I would recommend you to go back to cm12.1, make sure debugging is on and try and see if your computer is able to recognize the phone. If that happens then reinstall the oem firmware.
Sent from my MotoG3 using Tapatalk
LucasAway said:
I have a Moto G 2015 installed the ROM CyanogenMod 12.1 it. I went back to the original, made all commands after restarted the device did not call more. I can not even access the Fastboot Flash Mod screen. The computer recognizes the phone driver as Qualcomm HS-USB qdloader 9008. Help me please!
Click to expand...
Click to collapse
Also try removing the Qualcomm device in the computers device manager, replug the phone and see if it will reinstall the phone driver correctly.
Sent from my GT-P5210 using Tapatalk
Hey i have a problem with my OP6,
I rooted my phone and relocked the bootloader.
I failed.
Got the message that my phone is corrupted and won't boot. Now i'm stuck in the bootloader. I can't power off and I can't boot into recovery (TWRP in my case) or into OxygenOS. I tried to unbrick it. But windows refuses to use the Qualcomm drivers. I tried to uninstall my present drivers. Because my phone gets detected under Kedacom USB devices as Android Bootloader Interface. When I try to uninstall them they automatically get reinstalled by Windows. I tried to disable this but it seems that this doesen't work.
What can i do?
Can someone help me?
Thanks.
LuckyCrasher