I've been trying to get the USB drivers to work. I'm running Win7 x64 and I get an error saying the driver install has failed. I've tried doing the driver install manually, through Kies, etc.. Nothing seems to work -- am I missing something?
rkjunior said:
I've been trying to get the USB drivers to work. I'm running Win7 x64 and I get an error saying the driver install has failed. I've tried doing the driver install manually, through Kies, etc.. Nothing seems to work -- am I missing something?
Click to expand...
Click to collapse
hmmm. try turning on USB debugging and see if u can connect it.
Nevermind, I figured it out. It was the crappy USB cable I had laying around from a Palm Pre. Used a Samsung cable and it was fine. Go figure.
Win 7 64-bit driver issues HELP
E4GT rooted stock EL 29 Kernel. Same problem as above, except changing cord has not helped. Have tried loading drivers from Samsung site, thru Kies, and from xda threads. None work same error. Really puzzled. Worked first time to flash rooted stock EL29 Kernel, but now can't connect. HELP
I'm trying to install clockworkmod and root, by following the guide here:
http://forum.xda-developers.com/showthread.php?t=2022270
Everything is going well until I reboot into clockworkmod, at which point my computer fails to recognize the Nexus 7 for ADB, and I can't continue.
The weird thing is, after installing the ADB drivers from Asus' website on my Windows 7 PC, it connects perfectly in Windows. However, in clockworkmod, it just shows up in my Windows Device Manager with a yellow exclamation mark next to it.
Anyone knows what the problem might be?
Okay, solved my own problem.
Dunno what the problem was. I also tried installing the official Google drivers from the SDK to no avail. Fixed it by using the PDANet drivers here:
http://www.junefabrics.com/android/download.php
Now all is well.
manekineko said:
Okay, solved my own problem.
Dunno what the problem was. I also tried installing the official Google drivers from the SDK to no avail. Fixed it by using the PDANet drivers here:
http://www.junefabrics.com/android/download.php
Now all is well.
Click to expand...
Click to collapse
Thanks verrrrrrrrrrryyyy much guy. It solved my problem:
http://forum.xda-developers.com/showthread.php?p=46754283
You are awsome for share your knowledge.
Hi all,
Got my new S III on Jan. 1. Love it. Gave me an opportunity to use my old Cappy to experiment with. Flashed a couple of ROMS already and really love it. OK..so here's the problem. The only thing I have done with the S III is root it using the QCOM Toolkit. When I downloaded the drivers and plugged in phone it said that if a device number was showing that all drivers had installed. Don't really know if the MTP driver loaded at that time or not...but the device number was there and I proceeded to root the phone. Now when I try to connect to PC I get the dreaded MTP driver failed error message. Did a TON of research on this and tried EVERYTHING...still no joy. I am running Windows 7 Home Premium and even tried using my XP Pro machine...still no joy. Would love to flash a ROM on the new S III but no way to copy to SD card without PC connection.
Phone is A T&T SGH-1747 4.04 Version.
OK to reduce the number of "have you tried's" I have: tried various cables, uninstall reinstall Kies..Kies driver repair, uninstalled/reinstalled all Samsung drivers. Tried the MTP/PTP toggle idea. Plugged in with USB debugging ON and OFF. Sooooo tired of getting the MTP USB Device Driver failed message!!!
Any new ideas out there?
do a factory reset on ur phone
uninstall/install drivers again http://www.samsung.com/us/support/owners/product/SGH-I747MBBATT
after u install drivers open odin and connect phone. it should be recognized
MoeisHere said:
do a factory reset on ur phone
uninstall/install drivers again
after u install drivers open odin and connect phone. it should be recognized
Click to expand...
Click to collapse
Thanks Moe. Yeah I was afraid of that. Just got all my apps restored. Oh well. Well worth it if it works. Thanks again!
Factory reset is the only option that worked for me, and I tried everything you listed above. Also, based on prior posts, I plugged it into my computer before I signed into my google accounts.
sjroberts98 said:
Factory reset is the only option that worked for me, and I tried everything you listed above. Also, based on prior posts, I plugged it into my computer before I signed into my google accounts.
Click to expand...
Click to collapse
Right SJ...I had heard that also. I really hope it works because if I do a factory reset and lose all my apps and data and it doesn't work...I am gonna lose it! LOL!
When I connect my Nexus 7 to my windows 7 computer it is not recognized in MTP, but is when I change it to PTP. When I connect my 1st gen Nexus 7 to the same computer it is recognized fine and I am able to transfer files. I have all the drivers installed and adb works when I am in PTP I just cant transfer any files. Has anyone else experienced this problem or is there maybe something wrong with my Nexus?
Check out this thread. I was experiencing similar issues although I didn't test out PTP .
Sent from my Galaxy Nexus using xda app-developers app
Disregard. I figured it out. It was a driver issue after all.
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
lucastmw said:
My N7 2013 won't connect with my Macbook Pro. I already have the Android File Transfer app, which works fine with my Nexus 4, but it won't recognize the Nexus 7 2013. It charges, but no connection. Anyone have any ideas?
Click to expand...
Click to collapse
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
jmileti said:
Might be a silly question but did you enable USB debugging in developer tools.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes, I tried it with debugging on and off.
thaliagoo said:
How did you fix it? I have the same problem. Is root needed to view transfer files via USB?
Click to expand...
Click to collapse
Root is not needed to transfer files via USB. I just uninstalled the previous driver and updated to the latest and that worked for me.
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
thaliagoo said:
No matter what, I always keep getting error code 10, device cannot be started when I install the new nexus 7 drivers Android ADB device (from the previous posts- Nexus 7 root). I'm not even trying to root, just trying to install drivers correctly.
Click to expand...
Click to collapse
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
fixed mine by just forcing it to reinstall the drivers.
fstbusa said:
fixed mine by just forcing it to reinstall the drivers.
Click to expand...
Click to collapse
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
dirtyfingers said:
These are the drivers I used... http://developer.android.com/sdk/win-usb.html
Click to expand...
Click to collapse
It is definitely a driver issue. I had to uninstall my drivers and then manually install others, because I had a Nexus 7 2012. Those drivers were showing up as *up to date* according to windows, but the device was not working. Total clean install worked to correct it.
Xirix12 said:
How did you force it do that? I've actually never ran into this problem. Windows 8 is what I'm running.
Click to expand...
Click to collapse
In device manager, go to the properties of each android device. I had one near the top of the list and one lower under portable devices. Click update driver and navigate to your updated drivers folder.
It should update them. The device listed under portable devices had mtp as part of the title so I figured that one was the problem.
Sent from my Nexus 7 using xda app-developers app
To anybody who comes to this thread looking for help.
Go to device manager, and under devices remove the Google ADB Driver. This drove me nuts. All of my nexus devices wouldn't connect because they lacked an external SD.
Sent from my Nexus 7 using XDA Premium HD app
I've tried every suggestion in all of these threads so far & nothing worked. Even after I deleted the ADB drivers, windows 7 would automatically reinstall them. When I tried to update the drivers, win7 said they already had the best drivers (ADB).
Here's what worked for me:
I had to turn off USB debugging, delete the ADB drivers in Device Manager, then reboot the device while it's still plugged in. Windows recognized the device as an MTP device & installed the drivers before it even fully booted.
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
golfinggino said:
i installed the drivers from the link in this thread and still no luck, i am running the latest paranoid android rom, and tried it on 8 different computers with 23 different cables and no luck - would it help if i flashed a stock rom ? otherwise i dont know what to do - any help would be appreciated, thanks, chris
edit flashed a stock rom and now it is working again - came right up on my pc, i am selling it today to buy the 32gb and just wanted to get me twrp backups off it
Click to expand...
Click to collapse
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
huizingajm said:
I have the same problem. When I was using stock ROM I could connect fine to my PC. When I installed CM10.2 I can not longer connect. i have no problem when I try it with my phone though.
Click to expand...
Click to collapse
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
sfhub said:
After helping someone with Paranoid ROM, I think the problem you are experiencing may be on the ROM/kernel side. Part of the problem is the custom ROM was sending out different USB IDs from stock. I was able to help them force the recognition of the MTP device from a driver standpoint on windows, but the MTP device wouldn't start up when windows tried to initialize it.
Click to expand...
Click to collapse
I switched kernels to stock to jassy to tiny. None of them work so it has to be the ROM. I am just going to use WiFi transfer of files. Nothing major right now while everything is still new to 4.3.
Kies 3 saids it not supported for my device? Should i use kies 2.6? I have all the usb drivers and everything. Runing Windows 8.1 and cm11 rom and galaxy tab s 10.5. Help!
DUHAsianSKILLZ said:
Kies 3 saids it not supported for my device? Should i use kies 2.6? I have all the usb drivers and everything. Runing Windows 8.1 and cm11 rom and galaxy tab s 10.5. Help!
Click to expand...
Click to collapse
I had this issue, it was because I grabbed the wrong white USB cable! Added a tag to the correct one so it won't happen again!
flhthemi said:
I had this issue, it was because I grabbed the wrong white USB cable! Added a tag to the correct one so it won't happen again!
Click to expand...
Click to collapse
Well im using my stock usb cable that came with my tab s. It worked a month agoñ
Maybe try a different cable or USB port. I know sometimes I plug mine in to a USB hub and it starts installing the drivers again because I didn't use the same port...strange I know but it could be missing the drivers it needs. You can open the device manager in Windows and see if everything is being found....other than that this n00b is stumped because it's working on mine. So Kies 3 does work on this tablet.
flhthemi said:
Maybe try a different cable or USB port. I know sometimes I plug mine in to a USB hub and it starts installing the drivers again because I didn't use the same port...strange I know but it could be missing the drivers it needs. You can open the device manager in Windows and see if everything is being found....other than that this n00b is stumped because it's working on mine. So Kies 3 does work on this tablet.
Click to expand...
Click to collapse
I look into that, check the drivers, may I ask what is the driver called in the device manager? Shouldnt be usb andriod something?
DUHAsianSKILLZ said:
I look into that, check the drivers, may I ask what is the driver called in the device manager? Shouldnt be usb andriod something?
Click to expand...
Click to collapse
Here is my device manager with the S connected...but there are a lot of drivers that get installed and I don't think it wise to take the automatic install of Windows drivers. If you have Kies installed anytime it needs driver you should stop it from getting them from Windows Update and get them from C:\Program Files\SAMSUNG\USB Drivers. Keis has an option to reinstall the drivers. Might try that if something is missing. OR Download the driver package from Samsung Support and install it.
Thanks ill check if anything is wrong with the drivers or usb cable and will post back
Edit! Kies will not work on custom roms! Only stock rooted or stock based Roms will work. Thanks you all for helping me as I reverted back to see if it was the os. Cm11 doesn't have support for kies