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?
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.
I usually keep flashing ROMS.
This time in sheer confidence I didnt charge the battery full.
I was switching from mokee 4.4 to CM11.
I wiped everything for a fresh install and unfortunately CM11 didnt install.
The tab restarted and now it wont go into recovery. what just happened?
It is just showing logo and I cannot get into Odin more either.
The tab had about 30% battery when it shut off and I cannot reach a charger for it for the next 4 hours.
Can I switch it off in any way to save battery?
the phone has switched off now. Is service center the only alternative? the tab was rooted with mokee installed.
devarshi84 said:
the phone has switched off now. Is service center the only alternative? the tab was rooted with mokee installed.
Click to expand...
Click to collapse
Try charging it when you have time and then try re flashing the stock Rom before taking it to service center
will the tab 2 charge without a recovery or ROM in place?
devarshi84 said:
will the tab 2 charge without a recovery or ROM in place?
Click to expand...
Click to collapse
I think it should
Ok, the tab2 is charging. thank you
I installed all the necessary drivers and odin and recovery on my laptop.
The tab2 is giving error on pc (this device wont start) mtp uSB. THe tab is stuck at 'samsung p3100' logo.
If it is any help, I have a working p3100 also running on stock firmware.
what should be my next step? I think I can manage if only I can get odin to recognize my phone or get into recovery (both of which seem to be missing.)
devarshi84 said:
Ok, the tab2 is charging. thank you
I installed all the necessary drivers and odin and recovery on my laptop.
The tab2 is giving error on pc (this device wont start) mtp uSB. THe tab is stuck at 'samsung p3100' logo.
If it is any help, I have a working p3100 also running on stock firmware.
what should be my next step? I think I can manage if only I can get odin to recognize my phone or get into recovery (both of which seem to be missing.)
Click to expand...
Click to collapse
Try reinstalling drivers
@shsagnik : Thank you very much for helping out.
I got installed all drivers by using the other P3100. But when I connect the bricked p3100, pc doesnt install MTP USB drivers. Under device manager it says " failed to start".
ODIN doesn't recognize it. either.
My mistake was I flashed everything on the phone including the internal memory.
PS: Can I force ODIN to recognize my phone?
Ok, my almost bricked device is back and runnning.
This might just help somebody. but my android handset was on a logo only mode. something in the combination of
Attaching it to pc (windows 7 64-bit)
re-installing and rejigging drivers
trying to let ODIN identiify
connecting via Samsung kies (I also tried restore on kies).
connecting a working android phone instead of the dead phone with pc to find and install drivers.
worked.
PS: I also let it sit dead powered off (worked only when charger was attached) for a whole day before trying to boot into recovery or bootlaoder (both worked).
devarshi84 said:
Ok, my almost bricked device is back and runnning.
This might just help somebody. but my android handset was on a logo only mode. something in the combination of
Attaching it to pc (windows 7 64-bit)
re-installing and rejigging drivers
trying to let ODIN identiify
connecting via Samsung kies (I also tried restore on kies).
connecting a working android phone instead of the dead phone with pc to find and install drivers.
worked.
PS: I also let it sit dead powered off (worked only when charger was attached) for a whole day before trying to boot into recovery or bootlaoder (both worked).
Click to expand...
Click to collapse
Awesome, now please change the title to solved
Today I was messing around with flashify and tried updating my TWRP recovery. Something went wrong...
The tablet is now stuck at the first Samsung boot screen and loops constantly.
I am running GNABO v8 ROM.
Kies is as useless as usual.
I can get into download mode, but my PC (windows 8.1) won`t recognize the device (Device Descriptor Failure). This is a problem I have had since installing GNABO, but unfortunately now I cannot use ODIN.
I have downloaded and installed the correct Samsung drivers but the PC won`t recognize them automatically.
I want to try to force install the correct driver, but they have weird names like swallowtail, Shrewsbury etc etc.
My question is which driver / .inf file should I try to install?