Database Info

USB Problems??

My phone has been working fine, up till last night. All of a sudden when I plug it into USB I get an error that there was a device malfunction. In dev man there's a Microsoft WPD FileSystem Volume that windows says cannot start properly, and a unknown device under USB.
I've system restored, I've power drained, I've tried on 3 pc's. Same thing. All pc's are running windows 7 64 bit.
Any ideas?

Maybe reinstalling the samsung drivers from the website. Maybe a driver got corrupted. Other than that I don't know. Bring the phone back get a new one faulty device.

Tried reinstalling drivers. Problem is I can't even reflash because I can't get the phone recognized to use the stock rom.....

if you are getting the same result on multiple PC's then the odds favor that your phone is the problem, and not the computer or drivers.
Have you tried different USB modes?
Have you tried a factory reset?

Trying the reset, we'll see. I'm desperate now. Yes, I've tried Kies and mass storage. I don't even need to select one though. (I have it set to ask) I get the error as soon as I hook it up..
Update: Reset didn't do it.

The Same thing happened to me, i tried Factory Reset but it did not work.

Good luck, I'm about at the point of giving up. I'm trying my work PC tomorrow and if it doesn't work, I'm off to the ATT store.

I called ATT cust Care, the lady did not understand what the problem was and said that i should contact Samsung rather than calling ATT to resolve the issue.

bhanuteja said:
I called ATT cust Care, the lady did not understand what the problem was and said that i should contact Samsung rather than calling ATT to resolve the issue.
Click to expand...
Click to collapse
thats some good troubleshooting right there

Driver issues, I had the same problem with windows 7. Use that usb view program and disable the htc drivers and samsung something usb bla bla drivers. Then replug and use the notifications to mount the sd card. It's hit or miss for me too.

Downloaded USBdeview?? Seems to be what you're talking about. Disabled, all samsung devices, there were 2. Plugged phone in. (I know longer get the mount options) soon as I hit mass storage on the phone though it throws the same error.
Then uninstalled the two devices, same thing. So I uninstalled ALL non HID devices, same thing. Gives me the error, throws an unknown device in dev manager, if I try to update/reinstall the driver it tells me the best one is already installed. Tried uninstalling it and reinstalling from add/remove. Same thing.
I'm thinking this is something with the device, not windows. It seems like the OS is somehow corrupted and not allowing windows to see it/load it.??? Sounds weird but 3 computers and 2 days solid of trying to fix this have gotten me no where.

Are you guys using Win7 x64 or 32?
I've had nothing but trouble with x64 and the samsung drivers. I can get the device to mount as a mass storage device if I uninstall all of samsung's drivers, and I have never been able to get the phone running in debugging mode (drivers always fail, adb shows nothing is connected). I can't even get the drivers working properly under WinXP 32bit running in vmware on my Win7 x64 computer.
The drivers work perfectly fine on my laptop running 32bit Vista, though. Installed the drivers, plugged in the phone, everything runs great.
Have not tested with a linux livecd, but I suspect it will also work fine.

I've only tried on 64 bit so far. I do have an Ubuntu box I could try it on I guess. Let's see....

Well... Nothing. I can't figure out how to get it to work in Ubuntu. Not sure it will. Honestly I just installed it and have yet to spend any time with it.

I use Win7 64 bit, tried it on Win XP but still have the same issue.

I'm wondering if it's the cable now. If I turn the phone off, then plug it in, as soon as the battery icon pops up I get the message. Nothing in DM though.

32 bit, used samsung drivers from their site, all the ones from here. As long as I get a connect once in a while I'm fine. I use my method which works for me. Oh well nothings perfect.

I grew up with rabbit ears and 4 head VCR's with bad tracking.

Yeah, unfortunatey I can't even get it to work once in a while......

[Solved-BADUSB]I think I managed to brick this Captivate

I just got my Captivate last Friday. Hadn't done anything complicated with it, basically I just used "Unleash the Beast" to root and sideload the thing. Ended up with some sort of weird permissions issue going on with the SuperUser app that had been installed with it, I was getting permission request loops. So I used Odin to reset it. At this point there wasn't anything really wrong, USB worked and the device appeared to the computer. So I just rebooted the Captivate into download mode using adb reboot download and went on.
So later on I grabbed SuperUser 2.3.4(?) or whatever the latest one I found online was, loaded that to do adb pull /system/apps since I realized that Unleash the Beast just deleted everything and I honestly hadn't even seen what it removed yet on the phone itself besides the list on the web site. So after the backup I odin'd again and then grabbed the files from SuperUser 2.3.4 replaced the existing files in Unleash the Beast with it. Actually ended up working perfectly for a while.
I'd used the phone for a few days, no issues, finally got my 16GB SD card from my Raphael and inserted it, had been downloading apps left and right. Well all of a sudden the phone seemed to have it's USB stop working for anything but charging. I recall plugging it into a charger or computer when I first got it and it would ask if I wanted to mount the SD cards for use, then I would just see the battery indicator charging. and I'd toggled developer usb a half billion times trying to get access and fix it.
The computer didn't see it, device manager didn't even flinch(Win7 x64) like it normally does when you plug in and unplug a USB device. Tried it with another computer and same issue. So I rebooted into recovery mode and tried that, the first several times around nothing was detected. Well my finger slipped and ended up hitting the Clear user data and cache option in the recovery mode.
At this point when it boots up, i still dont have usb access, I'm stuck in a force close loop, I can't install apps, can't seem to get it to reboot into download mode via the key commands, and installing apps is impossible since browser and market crash on start.
I've spent the night rebooting and trying to get into download mode for odin, I used to be able to get into recovery mode everytime I tried, eventually I started to see an "uknown device" show up in device manager, which I googled some info from it and all I could tell was it was Microsoft's dummy driver for devices that couldn't be found. Another weird response, it seems to be beginning to hang on the charging battery thing from time to time now.
At this point, its been under a week and I'd trade it in. Except the thing is with enough struggling you can see the apps installed. Most of them were removed but Market Access and Superuser are still in the apps list, and I'm worried about AT&T spotting that, figuring out what I've done and rejecting the claim.
just under half the time now, it boots, the other over-half of the time I get the spinning "battery loading" icon that shows up before the battery thing gets loaded, but not spinning. It pops up, and disappears, from time to time goes to show me my battery status instead of booting, even when not plugged in.
I'd like to think I haven't tried everything? quite obviously i can't run update.zip files from my 16gb sd card since it gets mounted at /sdcard/sd, and I've lost the file browser to move anything around. I've tried rewiping but that doesn't do a thing.
I hadn't gotten to the rom manager stuff yet since I wasn't planning on playing with roms if at all. and at this point that doesn't appear to be an option anymore.
Any suggestions? I was getting to continuing to reboot it till the battery thing comes up 100% of the time then goto ATT and see what they say.

So long that you can get to download mode you SHOULD be good. When you plug in the usb..you need to pull the home dropdown..select usb and tell it to mount. I may be telling you what you already know but download mode is hold both volume buttons from the battery screen...one black screen...att screen...black screen and release pwer but hold buttons. I had problems with this so what I did was unplug the usb...volume buttons...hold power and see att boot screen...(plug in usb)...black screen...att boot...black screen and release power til u see download mode. You can use Odin and set back to stock from there normally.
If the PC is showing unknown device..you are kind of stuck til you fix the driver issue. Maybe remove and reinstall or something not sure on that but that's the first order of business. Go to the dev forum and try reinstalling from there. (One click Odin downloader has teh drivers)
If your phone boots or can get into recovery or download mode you are ok. I ran into the problem where I couldnt even power it on.

Well by now I know that download mode is the holy grail to get things fixed. Recovery mode, I used to be able to get to, but didn't show up. I'm wandering if somehow my USB port got shorted or something.
The drop down option to make it mount is why this all began, it disappeared and never came back.
Trying your steps specifically, first couple times would just end up back at the battery screen. I eventually ended up at recovery mode. Did I end up at recovery mode for releaseing early or late?
I've reinstalled the Captivate drivers a couple times now and tried clearing all past installs of it. Still unknown device. At the moment I have it in recovery mode, so I've rebooted my tower into Ubuntu(Which has the sdk, but never tested with it). Since I've kept reading that Linux doesn't need drivers. Well ./adb start-server and ./adb devices still show nothing...
I can grab a fresh computer that never connected to this thing to try, but I'm kinda doubting it will do this trick at this point. I'll download the odin w/ drivers on it and try that.

hmm.... just ran over to one of the computers here that had absolutely nothing to do with android on it, no drivers, no sdk, no software, nothing.
Went to
[STOCK ROM] Odin3 One-Click Downloader and Drivers(new user=no links)
Downloaded the Windows X64 drivers, installed and rebooted
Plugged the phone in after it rebooted and I'm getting
Unkown Device, I'd pull some info from the Device Manager, but all it is reporting is scewed due to it being a usb device and Windows installed dummy drivers.
All I've got left for testing is my brother's Win7 x32 laptop, granted all I've been able to try with here has been x64 so far. Also on the first computer I was doing all this with. The drivers DID work, they WERE installed and functioning. Previously I could ADB to my hearts desire and I've used odin before. I used the same USB port, used different USB ports, tried different cables.

I had some strange issues on mine. When I would try to go to download mode. All of my USB stuff (KB and mouse) froze up and I had to plug in via PS2. I had the unknown device issue and Not sure how I fixed it. I downloaded and installed the Samsung Kies program and I also downloaded the driver. Ultimatly after banging on it for a bit it worked..not a Unknown device but it was some king of...Gadget Driver or some stuff was messing with me. Try installing Kies and see if that does anything...also make sure you remove the drivers before installing. It acted really squirrly to me too tho. From what you say..it sounds like a borked driver. Im on 32bit XP and took it home to my 64 Vista and got it working whne the 32 was jacking me around.

Just had a chance to try with Kies real quick, I'm not so much thinking i killed my drivers but that somehow the cell phone changed it's id calls. I'm going to give it a shot with kies on a fresh Vista x32 system at work. I still can't seem to get it into downloader mode, but I'm getting more consistent with Recovery and getting the thing to boot back up. If I consider the Battery screens to be your blank screens then I can get it to go recovery or "normal" boot. But still can't seem to get download mode at all.
Up until recently, I didn't get Unkown device showing up even when the system was in "normal" boot. Before, originally it would only show up in device manager in recovery mode, and then it would be the unkown device.
Just out of curiosity could you spare the driver specs for your setup so I can compare? Like Date, Version, and any Hardware IDs? I'm wandering what hardware IDs this thing is giving off since windows wont show me.

Well not sure what suddenly happened. But after enough reboot--attempts, recovery mode is finalyl appearing on my office computer as SAMSUNG Android USB Composite Device. Win Vista x32, only installed Kies and download SDK(speaking of, adb still doesn't see devices). Just finished redownloading odin(wish i'd had a thumbdrive on me when i was at home) and am about to see if I'm going to be lucky by vista somehow.

If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App

jonscapri said:
If you still keep having issues find a way to short the phone out and tell at&t that the phone just got really hot and then turned off. They should replace as a bad unit and get you hooked up with a new one.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Well that thought has occured, that and magnets lol
I think i might have found a clue to the cause. I think it was tied to the whole usb thing. When it appeared to show up at all first time around, i had tapped the menu button while in recovery. And the natural way I'd been holding it applied just a little pressure on the usb cable. Well I got the phone to finally show all the notifaction tab options for debug and storage when i held down the usb plug in the phone down a little bit. I'm guessing that the pins for power are fine but maybe the data pins, or maybe one of the data pins is loose and thus it's an unkown device since it's not responding correctly.
I didn't have time to finish trying to fix it at work, and i'm stuck in class now. I'm'a see if i can get admin access on my terminal here and download everything while the teacher does his orientation. Otherwise i think i can fix it once i'm home now.
=====EDIT=====
Well getting the phone into Download Mode was a bit easier with Ubuntu via ADB since I don't have to wait for Windows to load the driver. Then just rebooted the box into windows for Odin. Long painful story short, I didn't setup Rom manager to be able to undo my changes when the USB port went bad/inconsistent and didn't expect those changes to complicate the recovery without USB. So I'm making sure it's a rather provable issue and going down to ATT with it. 7 Days from receiving the phone, and I'm goin in for an exchange due to bad USB. Funny.

[Q] Problem with communication during GB update

Alrighty,
So I keep trying to update my g2x through LG but I continuously get an error message that says, "Problem with communication between cell phone and PC", and then it never goes past 4%. Yes, I've downloaded the proper drivers, and have followed the prompts of disconnecting the phone, removing the battery, powering back and pressing restart (countless times). None of it works though. And no, my phone isn't bricking up on the SW update, so that thread doesn't really help me.
I've been doing some research and it seems that it just doesn't work for some phones, but I'm wondering if anyone here has been able to successfully troubleshoot this.
Yeah, I'm one of the unfortunate ones that got a bad phone a while ago, so I'm hoping I can find a way to make it work...
Thanks in advance!!

I have had the same problem. I have a G2x that I got off ebay. It was un-moded, running stock Froyo 2.2.2. I went to the T-Mobile / LG update site and followed the steps. The program actually worked the first time, it went through the whole update procedure and said it was complete. The phone restarted, but when it restarted it no longer recognizes the SIM card and there is a question mark for the battery symbol. When I go into the settings, it does not show a baseband version. I have tried to re-install using the update program, but it stops after 36% saying "Problem with communication between cell phone and PC". Any ideas?

npo123 said:
Alrighty,
So I keep trying to update my g2x through LG but I continuously get an error message that says, "Problem with communication between cell phone and PC", and then it never goes past 4%. Yes, I've downloaded the proper drivers, and have followed the prompts of disconnecting the phone, removing the battery, powering back and pressing restart (countless times). None of it works though. And no, my phone isn't bricking up on the SW update, so that thread doesn't really help me.
I've been doing some research and it seems that it just doesn't work for some phones, but I'm wondering if anyone here has been able to successfully troubleshoot this.
Yeah, I'm one of the unfortunate ones that got a bad phone a while ago, so I'm hoping I can find a way to make it work...
Thanks in advance!!
Click to expand...
Click to collapse
Mine did this the first time. This is where the phone is never commanded to boot into S/W update mode so at least this is not a step where it can be bricked, as no update has actually occurred yet.
This is how I fixed it and got mine to update. Use a different USB port on your computer. Yes there are different as some are on internal hubs. The update must have a direct USB port with no hubs in between. I also reinstalled the drivers through the LG Update program and not from the LG website. When I did this and plugged in my phone about eight new devices were detected and installed as opposed to about two the first time around. Also, make sure your phone is in debug mode in Android application settings.
Then make sure you disable any anti-virus programs and turn off the Windows firewall. Then use ctrl-alt-delete and close down any programs running. Also go to the taskbar and click on the up arror (if Windows 7) and right click on each icon and see if you can close it down. Also, unplug all other USB devices (even a mouse if you don't need it) as they can interfere with communications between the updater program and your phone. The only USB device I left connected to my computer was the keyboard.
The LG Updater must be run in Admin mode. If when you run it you get a Windows warning asking you if it is ok for this program to make changes to your computer then it is launching in Admin mode. If not right click the LG Updater icon by clicking Start>All Program>LGMobile Support Tool>LGMobile update. Right click the last item and run it in admin mode. Again this is assuming you are running Windows 7. Admin mode is not necessary for Windows XP.
If all the drivers get loaded properly and you are not on a flakey USB port then at 4% the updater instructs the phone to reboot into S/W Update mode and that is where the real magic happens if you are lucky.

coreycollins3066 said:
I have had the same problem. I have a G2x that I got off ebay. It was un-moded, running stock Froyo 2.2.2. I went to the T-Mobile / LG update site and followed the steps. The program actually worked the first time, it went through the whole update procedure and said it was complete. The phone restarted, but when it restarted it no longer recognizes the SIM card and there is a question mark for the battery symbol. When I go into the settings, it does not show a baseband version. I have tried to re-install using the update program, but it stops after 36% saying "Problem with communication between cell phone and PC". Any ideas?
Click to expand...
Click to collapse
Use another USB port and try again. At various points in the update the updater resets the phones usb port and it has to reconnect. If it doesn't connect don't do a battery pull. Just try removing the USB cable and reinserting it. If you hear the computer beep wait a bit and then click restart on the updater. Hopefully it should see the device this time and continue the update.

[Q] PC won't recognize Transformer

Ok, I am MAD. This is unsolvable. I can't figure it out.
When I plug the Transformer into the PC, the PC won't detect it. It did a couple of days ago. I plugged it in to move some files over. It showed up as a drive before, but not anymore. The TF is brand new from Christmas, and it actually worked just fine Christmas day (I was able to transfer over some photos).
Two things happened between then and now that I can think of:
1. I used a System Restore to go back a few days because of a bluescreen issue that is unrelated and that I solved. It only went back literally one day, though.
2. I tried to delete some of the stock apps installed on the transformer. Not through root trickery or whatnot (I'm not even rooted or modified in any way). Just by going to the app market and trying to remove some crap (of course I couldn't).
I plug it in. Windows says "detecting driver," then it says it failed. USB debug mode is on. So I went into device manager. It shows up as "MTP Device" or maybe just "MTP," and Device manager gives it a question mark. So I went to Asus's site, downloaded the USB drivers, and installed those. No go. So I turned off Debug mode. No go. If I have debug mode on and plug it in and go to Windows Update, it shows an update for "Asus MTP Device" or something like that. I do the update and it gives me an error, saying the device is not connected. It is.
I've even installed the stupid Asus Sync Suite. It decided I wanted like five different startup programs. Revo Uninstaller made quick work of them, stupid bloatware.
So I've made no progress. Not sure why I could do it before, but I can't anymore. One thing that was weird when it WAS working was that my computer didn't get USB 2.0 transfer speeds from the device. Music copied agonizingly slow and my PC told me that "this device can perform faster if plugged into USB 2.0," even though all my ports are 2.0.
Currently, all that happens when I plug it in is Device Manager shows "MTP Device." HOWEVER, something interesting. When it's plugged in, the "safely remove hardware" icon shows up in the tray. If I click it, I see "Eee Pad Transformer." So the PC DOES detect the device, it just can't access its storage.
I'm on a Win7 PC that I built. I'm totally updated. The Eeepad is totally updated.
Oh, one last thing... I *might* have gone into the filesystem explorer app that came preinstalled to the device. I noticed that there were some folders from apps that I had installed but then uninstalled, and that bugged me, because if I uninstall a program I don't want that folder laying around. So I deleted some. But none were preinstalled apps. Things like Angry Birds, apps that I installed.
I read some thread in my google searches about something like UMDF or whatever. I tried that, but it seemed to only work for people with Vista or XP. The exe wouldn't even run on my system.
if anyone can figure this out, they'd have my eternal thanks.
You guys are awesome,
wontstoptalkng
ps,
I read through this thread a bajillion times:
http://www.transformerforums.com/fo...ormer-manual-usb-drivers-sync-software-2.html
I tried the method used in post 12, which is what worked for the OP. It didn't work for me, either because that method doesn't work on Win7 or it doesn't work on a 64bit os.

[Verizon] If you're still having MTP driver/USB connection problems...

I may have found one more thing you could try...
After trying EVERYTHING I could find here on XDA, as well as across the web, I still couldn't get my S3 to connect to my computer. While trying to get mine to work, I discovered that my husband's S3 connected just fine, nixing the thought that it was computer related. I exchanged mine for a new phone, got it home, and it still didn't connect.
Several hours of troubleshooting later, I had it narrowed down that it worked immediately after a factory reset (while still connected to the computer), but BEFORE the setup wizard got to the Backup Assistant (where it was no longer visible in My Computer). SO, I reset it again, skipped out of the setup wizard as soon as I could, and bada-bing! It works! I discovered after the fact that my husband (whose connected so beautifully from the get go) had backed out of his setup wizard during initial setup, so it definitely could be more than just a one phone fix.
I'll be the first to admit that I'm a total newb to pretty much everything in this forum, so there may be a more knowledgeable person who could be able to pinpoint exactly why the setup wizard would prevent the MTP driver from working properly. At this point, I'm just happy it works, and wanted to put this out there in case there may be anyone else at their wits end.

I had to install kies before it worked properly for me and now i still have to plug in phone then unplug and plug back in before pc see's my phone.
Sent from my SPH-L710 using xda premium

jbadboy2007 said:
I had to install kies before it worked properly for me and now i still have to plug in phone then unplug and plug back in before pc see's my phone.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
Yeah, installing, uninstalling and re-installing Kies did nothing for my phones (first or second). I tried it all -- different usb ports on the computer, battery pull, reboot the phone, reboot the computer, install the drivers, uninstall the drivers, try it with usb debugging checked, try it all again with usb debugging unchecked, with an sd card, without one, with a sim card, without one, factory reset not connected and then factory reset connected. Even tried it all again on a separate computer running Windows 7 vs Vista. Finally, in the middle of a factory reset, I saw the magic words "Installed Successfully", but then it stopped working after I finished the setup wizard. Again, I have NO idea why the setup wizard would cause it not to work, but that was what I had narrowed it down to. I'm just glad to have it working!

Verizon Galaxy S3 USB Solution for Win 7 32bit
Micheliu said:
I may have found one more thing you could try...
After trying EVERYTHING I could find here on XDA, as well as across the web, I still couldn't get my S3 to connect to my computer. While trying to get mine to work, I discovered that my husband's S3 connected just fine, nixing the thought that it was computer related. I exchanged mine for a new phone, got it home, and it still didn't connect.
Several hours of troubleshooting later, I had it narrowed down that it worked immediately after a factory reset (while still connected to the computer), but BEFORE the setup wizard got to the Backup Assistant (where it was no longer visible in My Computer). SO, I reset it again, skipped out of the setup wizard as soon as I could, and bada-bing! It works! I discovered after the fact that my husband (whose connected so beautifully from the get go) had backed out of his setup wizard during initial setup, so it definitely could be more than just a one phone fix.
I'll be the first to admit that I'm a total newb to pretty much everything in this forum, so there may be a more knowledgeable person who could be able to pinpoint exactly why the setup wizard would prevent the MTP driver from working properly. At this point, I'm just happy it works, and wanted to put this out there in case there may be anyone else at their wits end.
Click to expand...
Click to collapse
Well, after reading about a dozen posts and so-called fixes. It all boiled down to uninstalling the Samsung Driver & Kies (if you installed separately). This def works for Verizon SCH-I535 Galaxy S3 16MB with 4.0.4 load.
1. Uninstall Kies, Uninstall Samsung Driver, reboot. Reboot your phone just to be safe.
2. On your S3 select Settings-->Developer-->Enable USB Debugging (hit ok at the prompt). Don't tweak anything else here. You MUST have the Debugging turned on for phone to connect to PC.
3. Plug-in the Samsung USB cable to PC (there was some discussion on which USBs work and which don't ... so you can try different USB ports if #4 fails to work below)
4. Windows will then install whatever driver(s) it needs and whala, you can now access your S3 via Explorer...it will show up as a phone, not an actual drive.
Hope this helps and saves you the time and frustration I experienced. I never saw the little USB icon on the S3 until I wiped all the Samsung and Kies drivers from my Win 7 system & enabled debugging on phone. So the issue lies with Samsung and their crappy Kies tool...their driver does not work for S3 (i.e., the standalone download that Version posts on their site). Go with the Windows Update driver (which is auto) and you should now be able to connect via USB to your S3. Again, this works for Win 7 32bit with Android 4.0.4.
-Cheers!

I have an old pc running xp. Nothing worked until I installed kies on both the phone and the pc. YMMV.
Sent from my SCH-I535 using xda app-developers app