Related
Hi,
Has any one been able to connect to samsung galaxy I5801 using adb? Running adb devices is not listing the device for me. I have installed samsung kies.
thanks, srb.
srbose said:
Hi,
Has any one been able to connect to samsung galaxy I5801 using adb? Running adb devices is not listing the device for me. I have installed samsung kies.
thanks, srb.
Click to expand...
Click to collapse
Have you put USB in debug mode?
Ciao
Hi Slumpolo,
Yeah, i have enabled the usb debugging option and rebooted the phone.
Before doing that I also went to Settings>About Phone>USB settings, and selected "mass storage" . This options gets disabled when USB debugging is on, but I did it just to be on the safe side.
Windows device manager shows that all the drivers are installed correctly.
i also did adb kill-server and adb devices multiple times.
Oh boy....its much deeper than that. Search YouTube "how to Android adb devices"...its kinda tricky.
sent from the current baddest cell phone on the planet.....the HTC Evo 4G
Hi StaraSkola,
I went over all the videos I could find and I believe I am doing everything right. To verify my setup, I connected by friends Galaxy S I9000 and I was able to see it in adb devices.
I did the same with my GT-I5801, and it does not get listed in adb devices. I made sure I was in USB debugging mode.
One difference I noticed in device manager was this:
When I connected I9000, a device called "Samsung Android Composite USB device" showed up in the USB devices.
But when I connect the GT-I5801, I get a device called "Samsung Composite USB device" ... there is no android mentioned any where.
I have tried reinstalling the driver but Windows insists it cant find a better match.
Does this help in root causing the issue?
thanks,
srb.
I finally managed to connect to my GT-I5801, both via Samsung Kies as well adb. yay!
I will note down all the steps that I did, in case any one finds it useful.
1. I re-installed Samsung Kies and then I reinstalled the Samsung drivers. This can be done using the "Driver Recovery" option available in the top left drop down menu in the Kies window. Its a button called Kies. I did this as I had messed around with my devices and drivers trying to discover my phone. But this did not solve my problem.
2. I unmounted the SD card and re-formatted it. The SD card had a few mp3 files in it and Samsung Kies is known to have issues with some types of MP3 files. This did not solve my issue. Phone was still undiscovered.
3. My most drastic step: I went to settings > reset to default. This erased all my settings and all my installed apps and I lost all my notes etc ( .. But, after I connected my phone back to the laptop, everything came up just fine. I was able to browse the phone using Kies and then connect to ADB shell after enabling USB debugging mode. So the problem was with one of my installed apps. I dont know which but I suspect it could be a modded Navigation app (BRUT mod) , that I had installed. But I am not sure.
4. When connected using Kies, there is an option in Kies to eject the phone. If I use this, then Kies does NOT connect back to the phone when I plug it back in. I have to reboot the phone. The workaround is, never use the eject option. Always remove the phone by simply unplugging the USB cable. Then Kies discovers it on connecting back and even adb is able to connect to it. I dont know if other other Galaxy models suffer from the same problem but folks can try out this work around.
Thanks,
srb.
Hi all,
I just connected my TF101 to transfer some files (its rooted with ARHD 3.2.1) and windows 7 fail to recognize it.
They find it as Transformer TF101 but with error. I tried to install the Asus ADB drivers but still doesnt open so i can copy some files i want....
Any suggestions ?
Do you need ASUS sync (usb transfer) or full ADB. You can try downloading the android-sdk from google here: http://developer.android.com/sdk/index.html
Also make sure 'USB-Debugging' is checked in the developer menu on the TF.
I dont need asus sync, i have disabled it also, and debuging is on. (yes i only need the usb transfer)
I already have tried the SDK, but still nothing.
I only need it to transfer some files (i ve already rooted it).
For the moment i can only do it via wifi but i cant see my SD on wifi and there is also no mass transfer.
My device manager recognizes it as Transformer TF101, but even when i manualy try to update the drivers with the Asus, i get that they arent compatible
What version of the drivers are you trying to install? Im using 1.0.76, and they work fine on win7 ult. x64
I tried the official http://support.asus.com/download.aspx?SLanguage=en&p=20&m=Eee+Pad+Transformer+TF101 and google SDK also...
Still even when i try to manually update them from the folder i unziped the drivers nothing happens.
I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
I don't have any issues with mine
Sent from my SCH-I535 using Xparent Blue Tapatalk 2
thats nice but it doesnt exactly do anything for my problem
Joey22688 said:
thats nice but it doesnt exactly do anything for my problem
Click to expand...
Click to collapse
Did you try a factory reset?
Sent from my SCH-I535 using xda app-developers app
This happened to me too but I was running a CM10 ROM. What are you running and have you tried a different ROM?
Unfortunately, I cannot remember exactly what I did but I recall allowing Windows (I'm on W7) to find the drivers and install for me.
I'm not having any issues either, I'm using both 32/64 versions of Win 7...
These are the drivers I'm using:
http://downloadcenter.samsung.com/content/SW/201206/20120620051748445/Verizon_Wireless_I535_GSIII_Samsung_USB_Driver_v1_4_6_0.exe
Hope this helps..
I think I found the problem (its not the phone)
its the drivers that samsung issued
I plugged the phone on my win 7 64 bit desktop (not installing any drivers beforehand) and I got a few failed messages for drivers but I was able to access the file system fine
I then installed the driver pack posted and above then got the mtp driver installation failed message and was unable to access the file system
uninstalled the driver pack and connected the phone back up and I can access the file system (with some other drivers failing to install, I think relating to usb modem stuff ect...)
so until samsung fixes the driver problem I will have to deal with a few driver installation failed message every time I hook up the phone, but at least I can access the file system
im running the phone on the stock ics btw, didnt install cm10 or anything like that, the phone is rooted though but I rooted it after I found out about the mtp driver problem so it shouldnt mean anything
I have the same problem on Windows 7 32 bit. I rooted my phone and installed samba as a temporary fix.
Plus I just bought an external 32 GB SD card and I plan on using that as my workaround and just transfering files between the two.
Sent from my SCH-I535 using Tapatalk 2
Problem for me was the root.
Could you humor me and try this:
- go into the superuser app
- Select the 'temp unroot' checkbox from the first screen.
- unplug then replug the USB cable on your phone. The drivers should install on the first try this time (they did for me) and Kies should work too.
The problem seems to be that SuperUser exploits the USB Debug internally so, even though USB Debug is unchecked, it is still detected as checked by the connection and fails the install of the driver.
Solution #2 is the amazing script that transforms your MTP connection into a UMS one (look in this thread http://forum.xda-developers.com/showthread.php?t=1785243 and thank open1your1eyes0 ). Once in UMS, you don't need the MTP driver to see your device so that's another approach.
Good luck
I bought Samsung Galaxy S3 2 weeks ago. Windows installed the drivers for it when first connected to my Windows 7 64 bit PC. It came up in the list of Devices on the Explorer. I installed "Kies_2.5.0.12094_28_8" which installed USB driver on top of the Windows driver. At the end of the installation, it gave "failure to install Samsung MTP driver".
Saw a thread on other forum where it was suggested to remove the driver from System Driver window under Control Tab/System and reboot. To be cautious, uninstalled Kies. Rebooted PC. Windows installed the driver. As soon as Kies was installed the whole issue unfolded again.
Looks like ALL Kies versions (including previous version of Kies_v2.3.3.12085_7_5) have incompatible and wrong driver which is resulting in this unresolvable situation.
I removed the MTP driver (control panel/system/device manager - MTP driver has ? mark - this is the one). Then removed the phone and rebooted PC. After reboot, connected the phone back. Windows detected the device and automatically installed the driver. The device is listed in Explorer and is fully accessible. Started Kies. It showed the device as GT-I9300. It took a while and connected to the phone. All functions became useable. Sync'ed the contacts etc.
Day2. Booted the PC. Device is still shown in Explorer. Kies shows GT-I9300 and then displays "Connecting Device" - IT FAILS TO CONNECT and on pressing "Trouble shooting" button, it re-installs its own drivers and fails to install MTP driver AGAIN" - the Kies software SUCKS
Solved! For real!
For some reason, any of those options helped me to make it work:
- Reinstall Windows Media Player
- Remove registry key
- Clean up old usb drivers
- re-install 100 times drivers from Verizon, Samsung. Even old versions.
- Install from Windows Update. I tried to do that 1000 times. Gosh!
- enable UMT access (mass storage) on the phone.
The only thing that worked was, for some reason , getting the drivers from a random computer that was the only computer that worked.
Windows 7 x64
Attached the files. Go to the devices manager and update the drivers.
Israel Leite
How I solved it
Joey22688 said:
I just got a S3 yesterday but was greeted with the dreaded MTP driver installation failed message on win 7 (32 bit)
I installed the regular verizon s3 drivers from samsung's site, did the same thing, uninstalled and tried Kies and let it install the drivers, same problem
tried a different usb port, same thing
restarted the comp and computer, still no go
im getting frustrated now
it seems samsung has known about this issue for over a month now but still hasnt been able to fix it
my a500 and galaxy nexus work fine with MTP so not sure why this would mess up
ive looked at other threads but there was no clear solution on how to fix it
Click to expand...
Click to collapse
1. Un-install Samsung Kies and USB drivers
2. Then install the Install Samsung Usb driver for mobile phones version 1.4.6.0
3. with phone un-pluged from the usbcable Go into settings/Developer Options un-check Stay Awake un-check USB debugging un-check Allow mock locations Now hit the HOME button then plug in the USB cable and your are set..
This worked perfectly painless for me :laugh:
Solution x Win XP
This solution worked for me.
Install microsoft patch for usb and reinstall MTP driver
see:
http://forum.xda-developers.com/showthread.php?t=1150211
Hope this helps
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
aaa12585 said:
I have a rooted Nexus 5. MTP and PTP refuse to work. Doesn't matter how I install/remove drivers or anything. I've tried every trick on the internet and no avail.
The PTP storage used to work when I didn't have root, so what's the deal?
Could this be due to my rooting process? To be honest, I don't remember how I rooted. I'm new to the Nexus scene, having come from a samsung device.
However, I was just having this issue with my older E4GT (GS2 variant) when running rooted/custom roms.
Now, I have a friend with a S4 who decided to get rooted/custom roms and is now having the same issues, except before, both his MTP and PTP worked!
I'm lost and losing hope for this stuff.
Click to expand...
Click to collapse
Is the device showing up under Device Manager (which would indicate that the driver is installed--see #2 here)? This is not a "root" issue. I've run rooted devices for over three years and have only had the problem in the early days with the Pandigital Novel. Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
ritchea said:
Have you used USBDeview to look at what you have for USB drivers and to make sure all drivers are being removed? Try another cable and another usb port. Some cables don't handle data, they just charge; cables are a variable in the process.
Click to expand...
Click to collapse
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
aaa12585 said:
Yes, I've tried all three of those things. This seems almost to be mission impossible.
I am running rooted stock and my friend is running a new rom altogether. using different computers, but getting the same issue.
See, while I can get Fastboot and ADB to work without a hitch, I can't get PTP or MTP working AT ALL.
ADB and Fastboot seems to be the only thing people are focusing on, and that's not my issue... so It's even harder to find solutions online
Click to expand...
Click to collapse
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Sent from my Nexus 7 using Tapatalk 4
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
ritchea said:
So it does show under device manager? Have you right-clicked and updated driver? Step #2 in the link pointed to USB drivers rather than adb. Yes, adb Is the usual culprit, but I've seen quite a few reports of your problem lately. Usually, removing the drivers and allowing the PC to reinstall works. Have you tried wireless to transfer files--at least a temporary solution?
If you're interested (desperate enough) to do a factory reset, I'd recommend WUGS toolkit. It will wipe do backup everything. Revert to stock and unroot. Then root and install custom recovery.
Click to expand...
Click to collapse
I have tried that too, but I end up with the same outcome. Same drivers I would normally have installed and give me no recognition of the device for file transferring.
Fortunately, knowing how this goes down, as it has happened before with me and my S2, I'm not desperate enough to factory reset. As I would ultimately reach the same issue.
I've been interested in wireless file transferring, but I much more prefer not having to upload the file to something like dropbox or manually setup a server. I'm more into the press-and-go (similar to the plug-and-go method... haha, get it?... made a funny there cause it relates to a cord ordeal) routine.
I haven't actively searched that route yet because I'm in hopes that there is a fix for this problem. I'll get to it if there really is no other choice. So, if there is a program that will allow me that ease of access, I'm open to suggestions!
AkaGrey said:
Happened to me when i rooted the device with wugs. I think because I used the RAW drivers. Just uninstall adb android driver from device manager and all the other drivers that resembles the nexus on usbdeview, reboot . Then put again the usb in the pc , and you are ready to go
Click to expand...
Click to collapse
Seeing this makes me question whether I'm confusing the purpose for each of these drivers or you haven't read what I wrote. However, our circumstances differ. I didn't root through conventional means of the toolkits, I just came across it through my search for driver issues. I have tried the method you are suggesting, as the toolkit driver installation steps take me through that step before I do anything else; but this doesn't work. I end up with the same outcome: Device is recognized and drivers are installed (if I allow windows to automatically search for them), but no PTP or MTP for any file transferring.
ok, silly question : Is it enabled on your android phone? under memory ->tap the 3 dots and you will see mtp/ptp try to uncheck and check.
Otherwise I don't really know anything u could do about it.
By using the NRT or toolkits to root, all of the pc's usb drivers were deleted and new/generic/universal ones installed to re-install custom recovery & achieve root. Go to Control Panel on the PC, do you see Portable Devices listing including the Nexus 5 ? Most likely, no - only Android Interface.
A simplistic approach that worked for me is to roll it back - if you are using PC running Windows OS, use System Restore to go back to a previous state to an earlier (earliest possible) time before - with the N5 disconnected. When the PC is restored, turn OFF USB debugging on the N5, connect via the OEM N5 cable - it should be recognized, then turn ON USB debugging if there are missing drivers - let Windows search & install.
At some point, N5 will be recognized as a Portable Device along wit Android Interface, and "Auto Play" would pop up, with full access to all the SD folders & files. Toggle MTP and PTP if necessary as it might install more drivers - you should be good to go.
Reboot the PC just to reconfirm that everything is back to normal, connect N5 and profit - enjoy.
If this work, please share & if it doesn't - please comment what didn't work.
The simplest and shortest way to connect google nexus5 with PC as MTP(Media device)
When I plugged it, there wasn't any yellow exclamation mark within Device Manager. So for me, the drivers were OK. But the device was not listed within my Eclipse DDMS. After a little bit of searching, it was just an option to change in the device settings. By default, the Nexus 5 USB computer connection is in MTP mode (Media Device).
What you have to do is:
Unplug the device from the computer
Go to Settings -> Storage.
In the ActionBar, click the option menu and choose "USB computer connection".
Then select Media device(MTP) or Camera(PTP) based on your requirement...
Plug the device and you should have a popup on the device allowing you to accept the computer's incoming connection..
I hope this will help!
Hi,
I have a very serious problem with my OnePlusOne (64GB) after updating to version YOG4PAS3JL. Since the update, ADB no longer recognizes my phone.
It doesn't depend on the computer I'm using, I have tried to use my phone on 3 different computers (Windows) that I use on a regular basis and none shows my phone with the command adb devices.
Connecting via MTP is no problem, but when I enable Android debugging with USB, my phone will not show up in Windows Explorer.
I have also attached a Samsung Galaxy Note 4 and a HTC phone, both are recognized by ADB.
If I change the mode to MTP, it will show up as portable device called A0001 in the windows device manager. If I switch to Android Debugging, it will simply disappear and not show up
as "other device" or usb device without driver. So I can't even reinstall Android ADB Interface, it also doesn't show up in the Device Manager any longer. If I try to install a driver for my OnePlus One when it is in MTP mode, it will also only allow me to install MTP drivers (no possibility to install the previously so fine working Samsung USB drivers).
I have literally tried every solution out there I have found, from unplugging and restarting my phone, using different USB ports, using different USB cables, reinstalling Samsung USB drivers (didn't help as phone did not show up as unrecognizes device any longer), uninstalling Google USB driver, adding OnePlusOne to the .inf usb driver file myself (which mostly resulted in an "no compatible driver was found in this folder"-error), installing fastboot (didn't change anything), universal adb driver setup, pdanet, using USDBDeview, removing drivers with the bacon root toolkit to removing mtp files from the inf folder of windows to prevent MTP driver installation, but nothing worked
I would prefer to go back to the version before YOG4PAS3JL, where ADB worked fine or install a different ROM, but I have seen that every guide states that you need to have ADB to install a new ROM. As my phone is not rooted and I can no longer use ADB with my phone, I'm basically pretty stuck and don't know what to do I'm pretty desperate after two days of trying to solve this problem without success and would be so thankful for any suggestion what I could do.
Same situation...let me know if you find any solution.
Same situation here. Anf I guess this might have a link with my lack of internet connection while tethering.
Did any of you tried the USB or wifi tether? Does it work?
Sent from my A0001 using XDA Free mobile app