Related
Hi all,
I've searched the forums (honestly), but I can't find an answer to my problem.
I have a Vodafone branded 32B phone.
I installed the AndroidSDK as supposed to, added the path, made the phone root, booted into the recovery console using fastboot and flashed my phone with different operating systems... but during all this time I hever got ADB to work.
Whatever I do, adb never finds the phone. Fastboot works and finds it, when it's in fastboot mode, but ADB never. So, I can't permanently install the recovery console nor do any of the other funky stuff.
ADB doesn't work when the phone is in fastboot mode nor normally operating. I have USB Debugging turned on. The phone works normally and I can access the SDCard just fine.
Any help?
Suggestion.
Look into purchasing a G1 to be kept as a spare and used for development. That's what I've done with my G1. GParted is within most recovery images nowadays, therefore you can do most anything there, well...important functions that is. Keep that in mind.
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Reignzone said:
You might need to uninstall the driver that recognizes your phone, then manually install the updated driver.
Click to expand...
Click to collapse
that's what i had to do to get it to recognise my phone.
i'm pretty sure the driver came with SDK. either way i've attached the one i used.
go into device manager and update the driver it's currently using with the attached one.
Incorrect driver.
It should be the 1st driver listed in the Android SDK file.
As far as I know, you could also choose to push ADB to your system32 file folder under the C: drive in your computer. That is if you're using a Windows machine.
just a thought
Are you on windows or linux? If you're in ubuntu try sudo adb ... the default unprivilaged user doesnt automatically have access to the device.
If you're in Windows I would uninstall the Android Phone device in device manager and reboot with the phone disconnected. Then connect it and install the usb driver from the sdk when prompted. Might also pay to download the sdk again.
Install HTC Sync
Another known way to fix the issue is to download and install HTC Sync http://www.htc.com/au/SupportViewNews.aspx?dl_id=573&news_id=169
This seems to install the correct drivers
For more info check the Wiki:
http://wiki.xda-developers.com/index.php?pagename=HTC_Sapphire_Hacking#sec02
Hey Guys,
Forgot to mention I'm on Windows Vista 64 bits.
That last suggestion did the trick. I went to the site and downloaded the HTCDriverUpdate_Vista_64bits.exe, and within seconds I had an ADB connection.
Thanks for your help!
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.
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.
so I got the latest Universal Naked Drivers 0.73 zip file, extraced it to its own folder on my desktop, and then I opened device manager, went to Other Devices>Nexus 4, right clicked, uninstalled, restarted my laptop and nexus 4, and then opened device manager again, and this time clicked on Update Drivers for nexus 4, and when I select browse files on my computer, then I click that folder, which has two sub folders in it, one for AMD64 and then i386, and there is also some other files in the main folder, outside the subfolders, called androidwinusba64 and androidwinusb86, as well as two more called android_apxusb and android_winusb.
But When i click on the main folder so it searched through that and the two subfolders, it keeps saying it's not finding any drivers for my device, and i've tried clicking on each of the sub folders, and neither of those make it work either. I've done what every guide has shown me, which I've installed drives hundreds of times in my 27years of life, and I have never had a problem before. Especially not with Android devices. I can't get my brand new 16gb nexus 4 that i just got yesterday (got it while I wait for Tmobile to get the Nex5 in stock, and then I am switching them out) to show up under my computer as a media device so I can actually drop files onto it. I dont get what the issue is here. I know that the 4.3 update (which I updated to last night when i first powered on my phone and activated it) cause some driver issues from what i've read, but supposedly they have been fixed or whatever, and this Naked Driver is supposed to help as well. But getting them installed first would work better lol. everytime I plug the phone in, it tries to install the drivers itself, but it keeps failing for some reason. Any thoughts on how to proceed ?
It's ADB driver, you need to enable USB Debugging. If you are using Windows 8, reboot it into advance mode and disable driver signature checking.
eksasol said:
It's ADB driver, you need to enable USB Debugging. If you are using Windows 8, reboot it into advance mode and disable driver signature checking.
Click to expand...
Click to collapse
i already know all that lol I've been modding for quite a few years, so I know all about USB debugging, thanks tho. That's definitely not the problem. I can get the phone to work with ADB no problem, but I can't get it to show up as a media device like its supposed to when i have that selected in the USB mode options.
Oh, and I am sorry, I shoulda clarified, I am on Win 7. I already read about the Windows 8 thing tho. Which I got a copy of Win8, so I do plan on upgrading soon, check it out see what its like. But I just gto a new copy of Ubuntu, so I've been playing around with that a lot lately.
Anyone ? I have tried so many different things and Just can't get it to work, bout to chuck my laptop out the window lol
I can't speak for the naked drivers as I have never used them, but the ones that come with the SDK work fine with Win 7 on Android 4.3 (Copy and pasting files with Windows Explorer, adb, fastboot, etc.).
Did you resolve your issue? If not you should try to run "Usb Tree View" and make sure your phone internal USB switch is set to PDA and not MODEM or BOTH etc. I don't know how that works for the Nex4 but its a thing to look at.
Hello!
Please advise, I really don't know what to do with it anymore ...
Every ROM with Android 10, including Crdroid, Pixel Experience etc ... as soon as I upload it to the Mi A1, then (after normal first start and boot) I connect the USB cable and choose "USB transfer files", so it just doesn't appear on a Windows PC and I cannot transfer anything. As if the phone was just unplugged, it's just charging USB tethering works. Direct selection of "USB file transfer" in the developer options won't help either. Where's the problem? Once I get back to Android 9 (Any... Stock and AOSP), everything is fine.
I flash the ROM normally. Starting from STOCK, unlock the original bootloader, load TWRP, delete DATA, SYSTEM, INTERNAL, DALVIK, flash ROM, then GAPPS (eventually) and then restart...
I really don't know where the problem is when nobody reports anything like that here
neobit78 said:
Hello!
Please advise, I really don't know what to do with it anymore ...
Every ROM with Android 10, including Crdroid, Pixel Experience etc ... as soon as I upload it to the Mi A1, then (after normal first start and boot) I connect the USB cable and choose "USB transfer files", so it just doesn't appear on a Windows PC and I cannot transfer anything. As if the phone was just unplugged, it's just charging USB tethering works. Direct selection of "USB file transfer" in the developer options won't help either. Where's the problem? Once I get back to Android 9 (Any... Stock and AOSP), everything is fine.
I flash the ROM normally. Starting from STOCK, unlock the original bootloader, load TWRP, delete DATA, SYSTEM, INTERNAL, DALVIK, flash ROM, then GAPPS (eventually) and then restart...
I really don't know where the problem is when nobody reports anything like that here
Click to expand...
Click to collapse
? Might be something to do with the usb driver(s) on your pc. Also if you can't get it to work then try FTP as that's an alternative. See if you can transfer files via usb when you boot into recovery (twrp etc). Have you tried Derpfest ROM? That ROM might work for it. Just a few possibilities lol
I don't assume that it would be a USB driver, because the same phone with Android 9 works normally. And to replace the direct connection via USB by FTP connection? I don't think about it for a second Maybe when I'm in a bit of a mood I'll try another ROM and maybe I'll be lucky...
I'm rather surprised that no one has a similar problem and I would just like to solve it
Anyway, thanks for trying to help me
Hi,
Try flashing latest firmware. For me personally, New USB Cable solved it
---------- Post added at 03:05 PM ---------- Previous post was at 03:04 PM ----------
On the other hand, you can always use something Like mixplorer with ftp or HTTP server
I'm calling off my problem!
It was really enough to completely remove the existing drivers and let Windows do its job and install them again.
I'm sorry, I'm sorry, I'm sorry!
This should happen to newbies only! Unfortunately, I made it very complicated IN MY HEAD and I didn't think clearly
I apologize to everyone!
It is a problem with the drivers, it does not matter what ROM you use or if you have Android 9 or 10. You have to enter the Windows task manager, put the mobile in file transfer mode and delete Google driver by uninstalling the device from the system, just delete that driver and re-target your Mi A1 to PC. Windows will install the correct driver.
In Windows 10,go to Device manager & uninstall Google nexus device.then plug your phone.Storage working well
dilupalakmal said:
In Windows 10,go to Device manager & uninstall Google nexus device.then plug your phone.Storage working well
Click to expand...
Click to collapse
I solved the problem with your directions. Thanks!
neobit78 said:
I'm calling off my problem!
It was really enough to completely remove the existing drivers and let Windows do its job and install them again.
I'm sorry, I'm sorry, I'm sorry!
This should happen to newbies only! Unfortunately, I made it very complicated IN MY HEAD and I didn't think clearly
I apologize to everyone!
Click to expand...
Click to collapse
Same trouble, can you send screenshoot device manager, i dont know what driver must be I update
Roober_4 said:
It is a problem with the drivers, it does not matter what ROM you use or if you have Android 9 or 10. You have to enter the Windows task manager, put the mobile in file transfer mode and delete Google driver by uninstalling the device from the system, just delete that driver and re-target your Mi A1 to PC. Windows will install the correct driver.
Click to expand...
Click to collapse
You are a life saver! I spent an entire night re-flashing ROM and troubleshooting but this solved the problem. Thanks!!!
dilupalakmal said:
In Windows 10,go to Device manager & uninstall Google nexus device.then plug your phone.Storage working well
Click to expand...
Click to collapse
You Are Awesome !! Your suggestion helped me too !!
Removed the Nexus in Device Manager and reconnected the USB cable .. This pushed my Google Pixel device into USB File Transfer mode.
Roober_4 said:
It is a problem with the drivers, it does not matter what ROM you use or if you have Android 9 or 10. You have to enter the Windows task manager, put the mobile in file transfer mode and delete Google driver by uninstalling the device from the system, just delete that driver and re-target your Mi A1 to PC. Windows will install the correct driver.
Click to expand...
Click to collapse
thanx for your suggestion thats really work , or there is no problem in pixel rom