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.
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
pacificblue03 said:
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
Click to expand...
Click to collapse
Run the trouble shooting guide in KIES to re-install the drivers . Also, use KIES AIR, that only needs WiFi and you can access files and folders via your pc browser. Hope that helps
unistaller old driver. go to samsung website download lastest driver and install it
depzaj said:
unistaller old driver. go to samsung website download lastest driver and install it
Click to expand...
Click to collapse
Yup that to. BUT, often on the Samsmug site the software version available is one version behind behind that available via online updates Kies.
Tried that
Hi, I have already done all of the above more than 3 times ive removed the drivers, kies and re installed and my computer will always just keep saying usb device not recognized with code 42.
This is what microsoft have to say:
"Windows cannot load the device driver for this hardware because there is a duplicate device already running in the system. (Code 42)
Recommended resolution
A duplicate device was detected. This error occurs when a bus driver incorrectly creates two identically named sub-processes (known as a bus driver error), or when a device with a serial number is discovered in a new location before it is removed from the old location. You may be able to resolve this problem by restarting your computer.
Restart your computer
Click Start, click Shut Down, and then select Restart in the Shut Down Windows dialog box to restart the computer."
I have to go out just now. I'll take a looky see when I get back.
error 43
oh im sorry its not error code 42 but 43
windows detectded problems with this device....
Do you have a Linux OS under the hand? It would give you a lot more information than Windows does... If you dont have but want to try, you can download the disc image from ubuntu.com or any other distro like linux mint or fedora etc.
Just to get information on your phone you dont have to install it, just starting on the liveCD, plugin the phone in and running comands like dmesg, lsusb and maybe hwinfo would be able to tell you what is happening with your phone.
Sent from my Nexus S using XDA
error 43
i have got xubuntu but it is weird tat the phone does this on any computer not just my laptop. i was at work today and it was still an unknown device.
pacificblue03 said:
i have got xubuntu but it is weird tat the phone does this on any computer not just my laptop. i was at work today and it was still an unknown device.
Click to expand...
Click to collapse
This is why I suggest you to try to plug it in a linux machine and run those commands, there is obviously a problem with your device and Linux could help you to define what it is since it gives more information on the hardware.
If you are unfamiliar with dmesg output you can create a pastebin and link it here I will try to help with it. The output of lsusb may provide interesting info too. (as hwinfo but I don't think it is available by default in Xubuntu)
Sent from my Nexus S using XDA
error 43
well i will try if i can but it will be in a day or two as im packed to the top with assignments
Also I did not mention that but you can access your phone via the wifi network starting an ssh or ftp server on it, the one I use is connect bot from the market. This way you can manage you music and files over the network.
Sent from my Nexus S using XDA
error 43
yes i have done it using kies air that works. i will try the ubuntu method as soon as i can. thanks for all your help so far everyone.
Can you confirm that your usb ports on the PC is working with other devices. Its starting to look like a faulty phone. Have you tried a different usb cable, or can you check the current one with another device. We need to exclude all other factors before we conclude it is a faulty phone.
error 43
other devices work yes.
OK, looks like a croaked phone. Last ditch effort. If you go over to the forums at http://www.sevenforums.com/ have a good search for that error 43 code, there might be an answer that I've missed. We could also have a good look at the windows error logs, but I don't hold much hope as you have proven the PC hardware works, and you have checked and cross checked the drivers. All the error logs will show is an expanded view of the error.
I would consider returning the device with a view to a new replacement. Sorry. :-(
.
Thread moved to Q&A due to it being a question. Would advise you to read forum rules and post in correct section.
Failure to comply with forum rules will result in an infraction and/or ban depending on severity of rule break.
Got the same issue on 3 different W7 pc's. Got my sgs3 like 3 days. first day USB connection worked just fine but now there's no way of connection it to pc with USB. offcourse you can connect with WIFI but with USB link is much faster
Galaxy S3 drivers issue...resolved!
pacificblue03 said:
I have a Samsung galaxy s3 which is just about 2 weeks old, stock rom and not modded in any way, i have been able to connect it to pc and it would be fine and work, the past 2 - 3 days whichever pc i plug it into mine or another pc windows will say that the usb device is not recognized and does not install the driver i also cant access it in any way (from usb).
i need help with this i have no answers on Google and i need to access my phone to get music and stuff on it but we need to figure out why mtp or camera mode or usb debugging all do not work.
Thanks.
Click to expand...
Click to collapse
I had the same problem and could not figure out why...here is the deal:
Prior to SGS3, I had the old Samsung Galaxy S/Vibrant and was using the USB cable which came with it...then I thought; maybe the USB cable in the box of GS3 is different or superior...i tried it and VOILA! it worked...so that is all I had to do...all these reboots and re-installing drivers was just a waste of time...PS> I am running Win 7 64bit
USB ERROR
I still cant connect with 3 different cables, i am going to do a factory data reset and tell you all how i go in about 15 minutes...
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 just bought a Nexus 5 and I'm having unbearable trouble getting it connected with my PC. I have spent the last 3 or 4 hours on Google and xda forums searching for a solution but nothing has worked so far.
My situation is as follows:
I'm using a laptop running Windows 8.1, I have tried both the original USB cable that came in the package as well as an older one and all the ports on my laptop.
I checked device manager and saw that it was connecting with ACER adb interface drivers. Some people had had the same problem, so I uninstalled the drivers. After that I installed Universal Naked Driver 0.73 (disabled checking for signatures first), my PC could not identify the Google package as a driver. Nexus still didn't show up in explorer although device manager now showed that it was connecting with the proper driver.
I downloaded the Nexus Root Toolkit and did the step-by-step driver setup. Toolkit itself connected perfectly well with my phone and stated that the drivers were successfully installed but my phone still doesn't show up anywhere in explorer.
I've really run out of ideas and cannot find anything online that's related to my problem that I haven't already tried. If anyone could help me, I'd really greatly appreciate it
Thanks,
Alselius
Alselius said:
Hi,
I just bought a Nexus 5 and I'm having unbearable trouble getting it connected with my PC. I have spent the last 3 or 4 hours on Google and xda forums searching for a solution but nothing has worked so far.
My situation is as follows:
I'm using a laptop running Windows 8.1, I have tried both the original USB cable that came in the package as well as an older one and all the ports on my laptop.
I checked device manager and saw that it was connecting with ACER adb interface drivers. Some people had had the same problem, so I uninstalled the drivers. After that I installed Universal Naked Driver 0.73 (disabled checking for signatures first), my PC could not identify the Google package as a driver. Nexus still didn't show up in explorer although device manager now showed that it was connecting with the proper driver.
I downloaded the Nexus Root Toolkit and did the step-by-step driver setup. Toolkit itself connected perfectly well with my phone and stated that the drivers were successfully installed but my phone still doesn't show up anywhere in explorer.
I've really run out of ideas and cannot find anything online that's related to my problem that I haven't already tried. If anyone could help me, I'd really greatly appreciate it
Thanks,
Alselius
Click to expand...
Click to collapse
Have you tried screwing with MTP and (the other) mode? Also is USB debugging on?
tevil said:
Have you tried screwing with MTP and (the other) mode? Also is USB debugging on?
Click to expand...
Click to collapse
Yeah, tried all the possible combinations, MTP, PTP, debug on and off. Responded the same, showed up in device manager and made the connected device sound effect but no folder.
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