ok i recently accidently flashed a stock ef09 rom which took away my root and custom recovery. well i went to go put custom recovery back on my transform m920 with sw upgrade. my drivers work amazingly usb debuggin on or off it doesnt matter. but in download mode my computer sees it as unrecognized device. i have not installed adb drivers due to an error: (SAMSUNG Android USB Modem Software was not installed successfully (16) there is a driver installed for the device, please uninstall it first). im running a dell 1737 laptop windows 7 64 bit and any help will be appreciated.
- Use Device Manager on your PC to uninstall whatever device is showing with the error (possibly 'Samsung ANDROID')
- Uninstall any Samsung USB drivers you have installed
- Unplug phone from computer
- Install these drivers, or Kies from Samsung
- Enter download mode and re-plug into PC
Let me know how you get on.
Good luck!
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 there,
I have read through a load of threads on how to unbrick the KF2.
Although it looks like the tools work for most, when I connect my KF2 with the fast boot cable, my Windows 8 PC doesn't detect the KF2 properly.
Before I had the red screen, it did find it and it worked OK. I have all the drivers and the SDK installed. I had rooted the KF2 and had that working fine, I tried to install Android KitKat onto it and got this red screen.
When I connect it to Windows 8 PC now it says:
Windows has stopped this device because it has reported problems. (Code 43)
The USB set address request failed.
I turned it off/on a few times, tried a few different USB ports and always the same.
I then tried it on a Windows 7 laptop and that comes up with installing device:
"otter2-Prod-04" rather than Kindle.
It ends up in device manager in other devices with a yellow exclamation mark.
On neither PC the KF2 will detect with adb -devices command.
Not sure what to do now, and how to get it to detect so that I can 'unbrick' it....any ideas anyone?
I am having a huge issue trying to get the MT65xx Phone Driver to install for the Insignia NS-P10A6100. Running Windows 7 Ultimate x64. Without this I'm unable to do ADB and Fastboot stuff since neither ADB or Fastboot seems to want to detect the tablet.
I used the method here to try and get the driver to install: http://forum.xda-developers.com/showthread.php?t=2206421
I got as far as the VCOM step but that doesn't want to seem to show up in my devices at all. The driver does install and Windows says it's installed. The USBDeview x64 app shows it's installed as well. Is there any other method that maybe I'm over looking to getting this up and running properly.
Thanks in advance for any and all help.
A few days back my One plus One device got stuck in bootloop when I installed an App update from playstore ( Google app). I downloaded the One Plus toolkit from their site and installed it but even in fast boot mode the device is not recognized by Win 7. I changed my OS to Win 10 still it says the same thing " one of the devices plugged to the computer has malfunctioned and Windows doesn't recognizes it." I uninstalled the drivers for the USB controllers and checked for hardware changes , still the device is not recognized. Unless it is connected I can't run the toolkit to root the device or flash a new ROM. Why is this happening?