Related
I am in dire need of assistance.
My hero is running 1.1 fresh and trying to use prekitchen 0.2 after prekitchen 0.1 and 0.1b failed yesterday. My phone won't give me the option to MOUNT SD when I connect to my pc, though it does have option for HTC Sync.
Now my device wizard is showing problem for the "android device" and when I open it, it tells me it's missing the adb driver!?!?!
WTF? I have had zero problems until yesterday. I also tried to DL the update driver from http://developer.android.com/sdk/index.html but after extraction windows says there is no driver in the folder.
AHHH. I think I might break my Hero in half, or worse, my computer.
please help, anyone, please.
try re-downloading the SDK and running/installing it. That's where the drivers come from
Please try to not post the same thing in multiple places.
You are running windows 7. Download the driver from here and install it.
flipzmode said:
Please try to not post the same thing in multiple places.
You are running windows 7. Download the driver from here and install it.
Click to expand...
Click to collapse
It worked!! Thanks so Much Flipz, wish I could figure out how this stuff got removed to begin with since your pre-kitchen worked successfully once.
Hi all,
Yesterday I stayed till 3 AM trying to flash the new firmware to my 9100, but KIES was so unstable that I decided to re-install.
We all know if we simply install Kies under XP, there is an issue with an Android MTP driver failing to install. No matter what you do, it won't install. This is the driver that Kies requires to work in order to sync contents and flash new firmwares.
After trying different options and settings, the solution is quite simple. Follow the steps (XP tested):
1.- Remove Kies entirely.
2.- Remove Samsung USB Drivers
3.- Reboot.
4.- Install latests .NET framework.
5.- Download and install latest Windows Media Player (ver 11 for XP). This is the key, since it installs a User mode driver framework used by Kies.
6.- Reboot
7.- Download and install latest Kies. Reboot.
6.- Plug in your phone. It will detect everything.
8.- Start Kies.
This should make it.
Hope it helps!
Cherni.
I had Rooted and Custom ROM-ed with AOSP GingerMOD.
Then when connected to PC via cable, W7 failed to install MTP driver.
Heres what worked.
Turn off USB Debugging on the phone. Reconnect via USB storage mode.
Voila!
Am not using Samsung Kies. so dont know whether it will work with the same trick.
cherni said:
5.- Download and install latest Windows Media Player (ver 11 for XP). This is the key, since it installs a User mode driver framework used by Kies.
Click to expand...
Click to collapse
What if you have XP?
ro-mann said:
What if you have XP?
Click to expand...
Click to collapse
He said version 11 for xp lol.
BTW, for those of you with windows 7 enterprise N - The "N" means no multimedia drivers, so media player would not be enough.
You need to download some 300+MB package which I don't remember the name. and then media player.
I meant W7!
Well I just tried this and it didn't work, am losing hope here...I already tried everything and nothing works
undertaker677 said:
Well I just tried this and it didn't work, am losing hope here...I already tried everything and nothing works
Click to expand...
Click to collapse
Is usb-debugging on?
Sent from my GT-I9100 using XDA App
I have tried it with or with out debugging
calexus1182 said:
Is usb-debugging on?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
All this started when I updated from version 2.3.3 to 2.3.4 through KIES
Hi, were you able to solve? I'm stuck at the same point, tried almost everything and i'm still getting the MFT driver error with my Galaxy S 2.
OS is WinXP 32bit, I tried before with Kies version 2.0.3.11082_152_2, then yesterday with 2.0.3.11082_152_4, no luck.
I tried the suggested Windows Media Player 11 procedure, i did the whole process as written in the 1st post (installed .net 4, then WMP11, then reboot, then Kies, then reboot again) and it didn't worked.
Before that i tried with USB debugging mode, i tried following what Kies says (connect device, got the error, disconnect the device then go to "tool -> the crap that should be supposed to repair drivers but that truly does nothing", then reconnect the device just to get the error again), I tried a tool i found somewhere on the internet while reading HUNDREDS of pages of users having the same error (Samsung engineers, that means that you really SUCK!) "FileSearcherforKiesFix" to find files with long extension on my SD, deleted some files (was only some thumbnails), NOPE, still getting the same F****n' error
So, were you able to solve in some way this error? How?
Thank you for your help, and sorry for my english (i'm Italian).
and if that doesn't work...try a different USB port on your computer. I have found that only one of the 4 on my t410 thinkpad plays nicely with the samsung usb drivers...
having said that, i have sworn off kies entirely and will only use Odin,
I'm on the Galaxy SII and was having similar problems. Went to the samsung website, DLed the USB driver, then to get the MTP to work: Turn off Debugging, go into "wireless and network", then into USB Utilities, unplug usb, click connect to PC, then plugged it back in, and bingo, we have a winner.
I didn't read the entire thread to see if this method was already posted, to f'ing tired!
Hopes this helps.
edit: looks like Kragusk did a similar (exactly the same?) install. So yeah, what he said....
the fix
This fix for windows XP was discovered by a chap named Dennis.
The problem is caused by some drivers from WMP11 failing to install correctly.
(WMP11 contains the MTP drivers, nothing to do with Samsung or USB drivers)
You just need to re/install them
rename C:\WINDOWS\system32\drivers\wudfrd.sys xxx_wudfrd.sys
rename C:\WINDOWS\system32\drivers\wudfpf.sys xxx_wudfpf.sys
rename C:\WINDOWS\system32\wudfhost.exe xxx_wudfhost.exe
rename C:\WINDOWS\system32\wudfsvc.dll xxx_wudfsvc.dll
rename C:\WINDOWS\system32\wudfx.dll xxx_wudfx.dll
rename C:\WINDOWS\system32\wudfplatform.dll xxx_wudfplatform.dll
rename C:\WINDOWS\system32\wudfcoinstaller.dll xxx_wudfcoinstaller.dll
Then run this file (umdf.exe) found inside the windows media player 11 install
(Hint: download then open in winrar to find the file)
Sorry as a new person I can't post a hotlink to a file.
wwwDOTmediafireDOTcomSLASH?2ak0f9n985ql00h
This not only cures Kies, but almost all other Media Player connection problems as well!
Kragusk said:
Go to Samsung Kies software, on top left of the window, click the menu > Driver recovery.
Let it reinstall drivers
After driver installation finished, go to your phone, Settings> Application > Development, tick USB debugging mode.
Under USB debugging mode connect your phone to the PC with USB.
It installs correctly!
Disconnect from PC
Untick USB debugging mode
Connect again
and it works!
Click to expand...
Click to collapse
This method really helped me. Thanks a lot man
wrong thread.....
Windows Media Player has the secret sauce! thx Cherni & pjclark1
5.- Download and install latest (ver 11 for XP). This is the key, since it installs a User mode driver framework used by Kies.
Cherni.
Worked for me, too. Didn't need to reboot.
XP sp3 captivate
I cant believe it that so many people are having this ****in problem! I will try post #1. Thanks
i tried post #1 but still doesnt work.
i tried installing a standalone Samsung USB drivers also doesnt work.
Anyone has a clue?
thank you v m~
It worked for me.
Thanks a lot.
I can't seem to get the Windows driver installed for the Evo Shift. I uninstalled the USB Mass Storage drivers for the Android phone and the phone shows up in Device Manager with the Yellow triangle, but whenever I try and update its driver and point it to the USB Driver folder from the Android SDK it says that Windows could not find driver software for the device.
Any ideas here? I did try using ADB to check for devices and nothing shows up in the list.
Thanks for the help.
ks-man said:
I can't seem to get the Windows driver installed for the Evo Shift. I uninstalled the USB Mass Storage drivers for the Android phone and the phone shows up in Device Manager with the Yellow triangle, but whenever I try and update its driver and point it to the USB Driver folder from the Android SDK it says that Windows could not find driver software for the device.
Any ideas here? I did try using ADB to check for devices and nothing shows up in the list.
Thanks for the help.
Click to expand...
Click to collapse
Did you download the right drivers from HTC?
Sent from my PG06100 using Xparent Blue Tapatalk
YoungCorruptionV2.0 said:
Did you download the right drivers from HTC?
Sent from my PG06100 using Xparent Blue Tapatalk
Click to expand...
Click to collapse
No, I've been trying to point it to the USB Drivers folder from the Android SDK. I can't seem to find the driver from HTC (or know which is the right one).
I didn't think it was HTC Sync but maybe it is...
If I remember correctly what I did (it was so long ago on windows lol), after you download the sdk from google you have to run the sdk/tools/android program to update and download the windows drivers. After that I went to device manager where the yellow triangle is and then right-click on it and select install manually instead of search online for drivers. Then click the browse button and find where in your sdk folder it downloaded the drivers to (can't remember where they are since so long ago). Select the correct drivers, there's probably more then one so you might have to mess around with trying different drivers out to get it working. Hope that helps and good luck. Or you can try the above method and try out the HTC drivers but I never used those so I can't say how to install them exactly.
Ok, I think I got it working, I guess I did need to install HTC Sync to get the driver.
I now have a device number in ADB. My phone said Couldn't find HTC Sync on the computer but I don't think that matters if the device number was in ADB, correct?
Thanks for the help.
sparksco said:
If I remember correctly what I did (it was so long ago on windows lol), after you download the sdk from google you have to run the sdk/tools/android program to update and download the windows drivers. After that I went to device manager where the yellow triangle is and then right-click on it and select install manually instead of search online for drivers. Then click the browse button and find where in your sdk folder it downloaded the drivers to (can't remember where they are since so long ago). Select the correct drivers, there's probably more then one so you might have to mess around with trying different drivers out to get it working. Hope that helps and good luck. Or you can try the above method and try out the HTC drivers but I never used those so I can't say how to install them exactly.
Click to expand...
Click to collapse
That makes sense, I never ran the program, just had it search the folder. I think I got it working though as mentioned in my post right above this one. Thanks.
You need HTC Sync and you need admin rights to install drivers on windows.
ks-man said:
Ok, I think I got it working, I guess I did need to install HTC Sync to get the driver.
I now have a device number in ADB. My phone said Couldn't find HTC Sync on the computer but I don't think that matters if the device number was in ADB, correct?
Thanks for the help.
Click to expand...
Click to collapse
Yeah your all good man, when you do adb devices and get your serial # back all is well, I had sync on my Vista pc and it wouldn't let me use HTC sync, it would just say not found, but I always just used the unrevoked EVO drivers and they hold true to this day, I've done G2s inspire and MT4GS all without new drivers
Sent from my Bulletproof_Doubleshot using Tapatalk
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
Ok so a little background. After hearing about the Carbon backup app a while ago I decided to install it and followed the instructions to do so. One of these steps is to change the normal USB drivers to the ATB ones from the Android SDK. I did this and it all went well without a hitch. However I came to add some movies on to my nexus 7 today and it would only recognize my device in PTP mode (as per the Carbon app requires). I proceeded as normal but found that I could not create a new folder for my films. When i tried i was faced with this error:
However I found that I could create a new folder in one of the existing sub-directories so I proceeded with that. I started copying the movie files over and got another pop up looking like this:
After clickking yes I was soon faced with another error screen:
This happens for nearly every video file i have tried to transfer. I have tried uninstalling the ADB drivers and letting windows install the default drivers it used the first time, however now it will not find any driver software for my nexus 7 unless I point it to the ADB drivers. Whenever I try to connect my device as an MTP device instead of PTP windows will not recognise it and nothing will show up in my computer. Is there any way that i can defer back to the default drivers and use my device on MTP instead of PTP?
Just for a bit of extra info, the same problem is occurring on my nexus 4.
Thanks
Hmm, i have adb drivhttp://forum.xda-developers.com/showthread.php?t=2214386alongside stock drivers for mtp as im sure many do n do not face this problem.
Have you uninstalled the backup app and cleaned the registry?
Try going in to device manager and enable 'show hidden devices' and search for any leftover usb drivers or interface that might interfere with the stock drivers. As a last resort you can download your usb chipset drivers, then uninstall all chipset drivers and usb devices including those hidden, then reinstall the chipset and other drivers u may need. Eg.printer drivers, then try again.
Previously i had a sony erricson phone and it's SE's software screwed up the usb interface n i wasnt able to connect anythin thru usb mtp. That helped me. Alternatively, if u have system restore on you can try restoring to a date before this all happened.
Also, check your device for any apps or settings that might interfere usb functions like usb debugging altho it's rare. Not sure what you did but you might have semi/permanently broken some settings in the device...if you had an earlier backup which was flawless, try restoring to that first. Remember to play safe when doing all troubleshooting, windows isnt exactly smart with device drivers =< worse case you have to reset both the usb drivers and device if nothing works...
Unrelated but might help http://forum.xda-developers.com/showthread.php?t=2214386
Or
http://forum.xda-developers.com/showpost.php?p=39752670&postcount=5
i faced the same problem last week. what i do is go through step by step like what nexus root toolkit suggest. start from scratch. remove all previous drivers and reinstall. Follow to the letter what it says. So the problem is just probably of a bad driver stuff. Remember to restart too.