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.
i think i have a soft brick on my tablet (Point of View Mobii 703) (The same: Allwinner A13)
i have booted the tablet into the upgrade mode, to install a custom rom with LiveSuit 1.11
but it says : no device seems to upgrade, i installed correctly the driver.
but i connected it again, it asks again for drivers, ok i install the same driver .... but it fails
disconnecting again and im trying to boot up normally, nothing happens, the tablet isnt going on.
its recognizing only on the pc, asking for drivers, but cant install driver. :crying:
first of all many thanks to all the developers for doing excellent work.
i am on odyssey 4.3 rom.when i connect my phone to pc in normal mode it shows everything is fine and working but when i connect it in download mode, i'm getting android composite device driver failed error even after instlling drivers many times,i have read almost everywhere related to the issue here but of no help.and major issue is in recovery mode bymistake formatted boot and so now my device is stuck in samsung boot logo.no recognision in odin so cant flash it either way.what should i do ?
Download driver from here
http://adbdriver.com/downloads/
(Samsung offical android driver(contains MTP and ADB Driver))
Connect and uninstall current driver with yellow triangle. Disconnect and install the downloaded driver. Now connect and see.
Now follow the post
http://forum.xda-developers.com/showpost.php?p=54459555&postcount=343
if you do not want to start it from zero ie from BG ddlf2.
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
Hi,
My Phone is now hanging up at the ":
"Samsung Galaxy S6 powered by android" screen
I can still get into recovery and downloadmode.
The pc "sees"the internal storage, but it wont allow me to copy a rom or anything to it,so that i may reflash a rom
Also if i use the "kies"or "smartswitch" programme, it says it cant connect to the Phone.
if reinstelled the samsung driver via kies
Also i have tried deleting the kies and driver from the pc, rebooting and reinstalling kies and driver, bit still the same result
It seems to me that if i could get a rom back on the internal storage i would be able to flas a new rom and get things working again?
Can anyone assist?
thaanks in advance