Since Monday morning, I have not been able to sync my phone (was dcd v3.0.4 when it stopped working). I have done much research and have tried many different things in an unsuccessful attempt to solve the issue.
When I plug it in, it begins charging but nothing else happens. No windows new device sound or system tray notification, no driver prompt, no windows activesync activity, nor any activesync activity on the phone (that little arrow icon on the top bar).
I have gotten this problem extremely intermittently previously but have always been able to resolve it with either a soft reset and/or a computer reboot. When that solution attempt failed, I tried moving the usb cable to a different port. I tried four or so different ports with no different results. I tried a different cable. I tried disabling advanced networking, deleting my partnerships (lost my contacts and have not yet been able to re-sync them :/), uninstalling activesync, and cleaning all the activesync files and drivers. I even launched device manager with hidden/non-present devices shown to remove the windows mobile devices (which were oddly not present, although this was after my first activesync uninstall/clean).
After not being able to get anything to respond, I thought it may be something not working properly on my workstation, so I tried similar processes of troubleshooting on my laptop with the same results.
At this point, I figured I had isolated the problem to the device, hopefully being just a software issue and not a hardware issue. At the time, I was still running rom dcd v3.0.4 with radio 3.35. I decided to flash to the newest versions in a hopeful attempt to restore my device's functionality. After flashing radio 3.39 and cooking and flashing a dcd v3.1.2 rom, I tried again with no different results.
Finally, I decided to connect it in bootloader mode, just to see what would happen (what is normal behavior for this anyway? does it get detected and drivers installed correctly?). It was detected as a usb device by my workstation but could not install drivers for it.
Needless to say, I have become rather frustrated with my device this week. I am not sure what the problem is exactly, nor what I could possibly do to fix it. I am on the verge of flashing a stock rom and *gasp* going to the Sprint store for support. Perhaps I finally dropped or shocked it one too many times this past weekend, and it does indeed have a physical issue...
Does anyone have any suggestions/ideas/thoughts? I would be very greatful for any input.
Thank you!
See this thread and see if anything in there fixes your problem.
http://forum.xda-developers.com/showthread.php?t=393918
I have been following that thread in hopes that something may prove helpful and have tried everything suggested, including attempting to clean the port (what would be best for this? anything more than just blowing into it?), trying the two Y adapters I have (emu -> emu / mini-usb & emu -> mini-usb / 2.5" stereo), running that batch script and working with the device manager (those devices were not present), and disabling advanced network functionality, all with no results.
VerusMaya said:
running that batch script and working with the device manager (those devices were not present),
Click to expand...
Click to collapse
If you've sync'd in the past then when you display hidden devices those devices should be present (at least faded). It'll be very strange if you don't see them. If not then uninstall the Mobile Device 6.1 upgrade, restart the PC and reinstall it. Then open up the device manager and watch what changes when you plug in your WinMo device.
Keystone said:
If you've sync'd in the past then when you display hidden devices those devices should be present (at least faded). It'll be very strange if you don't see them. If not then uninstall the Mobile Device 6.1 upgrade, restart the PC and reinstall it. Then open up the device manager and watch what changes when you plug in your WinMo device.
Click to expand...
Click to collapse
I also thought it quite strange that I did not see those devices at all at when I displayed hidden/non-present devices in the device manager. I definitely have sync'd on this machine many times, I typically leave it plugged in throughout the day here at work. My machine is part of a corporate domain but I do not see how anything pertaining to that would affect my devices. On my laptop (used to sync here), the devices were present in the device manager, but even after uninstalling them the phone would not be detected when I plugged it in.
When you say uninstall the mobile device 6.1 upgrade, are you talking about the vista mobile device manager? I am on XP with activesync 4.5.
Also, nothing happens when I plug the device in, not even the standard device connected notification sound. Nothing changes in the device manager, nothing is found when I rescan hardware, I even uninstalled all the usb root hub devices and rescanned for them, hoping a complete usb subsystem driver reinstall may help detect something.
I even downloaded and ran two usb tools, one free usbdeview (http://www.nirsoft.net/utils/usb_devices_view.html) which displayed and monitored all usb devices (present and non-) and drivers and a trial of a usbtrace (http://www.sysnucleus.com/) which was a usb protocol traffic capture and analysis program. I experimented with (un)plugging the phone multiple times in multiple ports with two different cables while running these programs, attempting to find something useful. Absolutely nothing at all happened in either program, which makes me believe it is something either on the phone software or hardware.
I have a feeling I may require a device swap :/
VerusMaya said:
When you say uninstall the mobile device 6.1 upgrade, are you talking about the vista mobile device manager? I am on XP with activesync 4.5.
Click to expand...
Click to collapse
Yeah, activesync then... I dunno, I'm at a loss.
Yeah me too, looks like I am going to have to flash the latest stock Sprint rom and take it in hopefully they can do something for me.
Went to sprint, it was a bad port after all, they gave me a brand new device.
VerusMaya said:
Went to sprint, it was a bad port after all, they gave me a brand new device.
Click to expand...
Click to collapse
Are you sure they gave you the brand new device? coz same thing happened to me a week ago and i went to sprint. They gave me the refurbished phone back. Physical condition of the phone is very good tho.
SptMogul said:
Are you sure they gave you the brand new device? coz same thing happened to me a week ago and i went to sprint. They gave me the refurbished phone back. Physical condition of the phone is very good tho.
Click to expand...
Click to collapse
Well I suppose I am not sure it was brand new, but it had the screen protector and the plastic stickers still on it (next to keyboard when you slide it out). I also received an additional 512MB SD card that comes with it.
Did you flash back to a sprint rom via sd card?
arcanecho said:
Did you flash back to a sprint rom via sd card?
Click to expand...
Click to collapse
Yes, I extracted the two NBH files from the latest (3.35 I believe) stock Sprint rom installer and first flashed the smaller image (bootloader/radio I think it was), and then the larger image (os) before I took it in.
The rep I dealt with at first was somewhat of a technical idiot and only served to confuse/delay matters but after I returned, I spoke to someone else and gave them permission to hard-reset, as well as mentioned I had done this multiple times as well as tried multiple computers and multiple cables, just to help them narrow down the possible source of the problem (as well as to block possible common excuses). After waiting around for half an hour or so in-store, a technician brought me a new phone and told me the port was physically bad.
All-in-all, I was quite pleased with Sprint's service and my free swap for an issueless and scratchless new device. I was afraid it was not going to be quite so easy, requiring more time and/or an insurance replacement fee. Not to mention the free 512mb sd card.
I had a similar problem, I was un able to connect to active sync but was able to charge. Everytime I would try to connect to active sync I got the "device is not recognized" error. Then someone on here suggested perhaps my USB port was messed up, sure enough I looked in the port and noticed one of the gold pins was flipped up slightly higher then the rest. My friend took a needle and adjusted the pin and it was good as new. Somehow I had lifted one of the pins.
Anyways IMHO it's good to look in there and just check if your having problems connecting, it saved me a trip to a technician and having to wait or go through reprogramming everything.
Related
Hello! My USB on my HD2 seems to be acting up, it has been working perfectly before but now I can not connect it to the computer any more. Charging it works fine though.
When I connected on mainscreen i got a "USB device not recognized" resulting in no connection between the computer and the phone. When I enter bootloader I get the device recognized as "Qualcomm CDMA Technologies MSM". I figured, ok, so perhaps it is ROM-connected and I just need to reflash to a stock and all will be fine and dandy.
(There were a lot more of fiddling around with USB settings before I went to bootloader, including reinstalling USB drivers on computer, trying different computers and trying different cables)
Flash got to 8% and then got an error message, now I get to bootloader automaticly on load, still the same Qualcomm device connected but SSPL-program on computer can't find a connection (and obviously not Window Mobile Device Center either.)
Where does my best hope lie? I dont have a cardreader for my microSD here at home so need to go out and grab that for any chance of reflashing that way. But I would seriously prefer to get the USB connection working.
Suggestions? Would be very appreciated!
I have just had excatly the same problem
Sent it to HTC Repiar centre (see their website). Despite other peoples experience mine was excellent. Repaired within a week and returned with new motherboard (hence new USB) and new case. They also fitted a new case as well as new battery terminals.
The phone had been loaded with a new rom by me. HTC reloaded the latest T-mobile rom (phone originally T-mobile) and returned it locked. They offered to send a new unlock code but I just re-loaded another (later) WWE rom.
All fixed - and free of charge.
Top service I say.
Good luck
I just got a new T-Mobile Samsung Vibrant. Running 2.1 Froyo Update 1, on JI6 modem and 2.6.29 kernel. Stock unrooted so far.
When I plug in my Samsung Vibrant into my Windows 7 64bit Machine, it is not being detected by Windows Explorer. I installed Samsung's Kies Mini and to STILL not being detected by the program. I installed 64 bit drivers and nothing. I've tried a combination of setting under USB settings Samsung Kies, Media Player, Mass Storage and Ask on Connection. None of them work.
I enabled/disabled USB Debugging in combination with some of the usb settings. I've disconnected and tried every single USB port on the back of my motherboard. I've reset the phone, and my computer. NOTHING WORKS. If someone can point me in the right direction if would be GREATLY appreciated. This is my first android phone and so far its not going so well....Will give THANKS to anyone who helps. What my main goal is to wipe the phone clean, and install a 2.2 rom on it or even Vanilla 2.2 With Root. Still new to this stuff....
Have you gone to the samsung website and downloaded/installed the drivers for your phone?
Here's a link for within XDA that has both the 64 and the 32 bit drivers
http://forum.xda-developers.com/showthread.php?t=728929
I think my issue is my LG Data cable. I've read around and apparently I need a Samsung Certifed USB Data Cable?
Edit: And yes I got the EXACT same drivers off the Softpedia page. Gonna reinstall for a another try but I'm 100% sure its my gimpy USB Cable.
Ah. I suppose that's possible as well. It's the same with car charger sometimes too. If it isn't setup with the exact same pins that your phone has then it won't work. So, even if the connectors look identical, apparently they're not.
Ah. I suppose that's possible as well. It's the same with car charger sometimes too. If it isn't setup with the exact same pins that your phone has then it won't work. So, even if the connectors look identical, apparently they're not.
You need a samsung certified data cable.
The pins look the same, but they aren't. Once you get the cable (I'm sure it's not more then $5), it should work. If you have T-Mobile around you (you have canada, so go to the provider that offers the equivalent of the Vibrant), ask to buy a "SAMSUNG CERTIFIED DATA CABLE". Nothing else.
Ordered one off of ebay should be arriving shortly. Hopefully this fixes my problems.
Same Problem
I'm having almost the same issue. However, rather than not being recognized by Windows, it tells me that there's a problem with the driver. And that's after I reinstalled Samsung's driver.
I'm not sure if the problem is with the phone, or with the cable, or with my computer. I'll try again at work on Monday.
In the meantime, assuming the problem is with the phone, how do I hard reset the phone, wiping the Samsung update, etc.? If I do so, will the Android Store know that I purchased all my apps, or will I have to buy them again?
And what backup program do you recommend for copying all my user data to my micro-SC card so that I don't loose everything.
Used my old BB cable and voila. Thanks for the help guys it was the USB cable indeed.
I recently picked up a Samsung Admire. It has Gingerbread 2.3.4, and my computer's running Vista 64. When I first got, it showed up on My Computer, but then it randomly stopped. I've tried everything I can think of to no avail. I've swapped USB ports, tried uninstalling and reinstalling the drivers, tried getting drivers directly from Samsung's website, tried debugging mode, tried going into Device Manager to find it there (where it does show up under Disk Drives and says it's working properly, but I can't do anything with it from there), etc, and still nothing. I've looked a several posts on here about it, too (which is where I got the uninstall/reinstall idea), but no luck (I'll admit I didn't understand some of what was said, as well...I'm not a phone guy, really). It's a brand new cord, too, in case someone mentions that.
It would be nice to be able to put stuff on it, so if anyone has any ideas, I'd certainly appreciate it.
Are you pulling down the status bar (at the top of the phone), and selecting 'Enable USB Storage'? Most android phones can connect to the computer and be seen by the device manager, but until the phone is told "OK, communicate with the computer", it will not actually let the computer access the file system.
ambiate said:
Are you pulling down the status bar (at the top of the phone), and selecting 'Enable USB Storage'? Most android phones can connect to the computer and be seen by the device manager, but until the phone is told "OK, communicate with the computer", it will not actually let the computer access the file system.
Click to expand...
Click to collapse
Oh yah, I forgot to mention it doesn't show up either way, whether that's enabled or not.
I guess I'll take it into the MetroPCS store and see if they have any ideas on what's up. I need to take it there anyway to find out why my reception is so constantly horrid. Worst reception of any phone company I've ever been with, and I've been with a few.
salihe66 said:
I recently picked up a Samsung Admire. It has Gingerbread 2.3.4, and my computer's running Vista 64. When I first got, it showed up on My Computer, but then it randomly stopped. I've tried everything I can think of to no avail. I've swapped USB ports, tried uninstalling and reinstalling the drivers, tried getting drivers directly from Samsung's website, tried debugging mode, tried going into Device Manager to find it there (where it does show up under Disk Drives and says it's working properly, but I can't do anything with it from there), etc, and still nothing. I've looked a several posts on here about it, too (which is where I got the uninstall/reinstall idea), but no luck (I'll admit I didn't understand some of what was said, as well...I'm not a phone guy, really). It's a brand new cord, too, in case someone mentions that.
It would be nice to be able to put stuff on it, so if anyone has any ideas, I'd certainly appreciate it.
Click to expand...
Click to collapse
Hi, i had the same problem with my admire but i have just recently found newly released drivers for the samsung from their website and now i have no issues with it anymore, you have to download the drivers for the samsung indulge YES THE INDULGE and it will operate perfectly..
...it really is a quirky device. At least mine is.
The other day, I was trying to use Winamp to sync my (up-to-date, stock, rooted) phone's music playlist using a Windows 7 computer, which I had done numerous times before. Just to eliminate the obvious, yes, the computer has a recent, working version of the HTC usb drivers installed, and yes I had the phone in Settings->Connect to PC->Disk Drive mode. No matter what I did, the computer would not recognize that the phone was plugged connected to it, and likewise the phone would not show that it was connected to a computer.
I was almost out of of options, but, as a last resort, I hooked it up to my linux (ubuntu 11.04) computer, which a couple of months ago had given me symptoms that were identical. Et voila! It recognized the phone with no problems whatsoever. You savvy readers here might remember that I posted about some of my pain with the linux box back then, because I was trying to update one of the botched OTA's that had left me unable to re-root my phone. So I booted it to the version of Amon Ra that I'd had problems with back then. Again, no problem. Go figure.
I then disconnected the phone, and hooked it back up to the Windows machine: No problem. Very, very puzzling.
I did a search here some time ago, and I don't remember seeing anything like this happening to anyone else. Regardless, just to be thorough, I'm going to ask once more: Have any of you characters heard of this kind of phenomenon with a Rezound?
many thanks!
john
I dealt with almost this exact problem of the PC connection with another user. In fact I've supported the user on three devices. His issue we eventually mostly figured out was with the sdcard mounting. In that process which seems so simple of plugging in the phone when it unmounts and remounts then afterwards unmounts and remounts, it would get part of the process and not finish the other part. He ended up thinking it was a faulty device and buying a new phone then eventually saw it on the new phone (different brand different OS). He called the sdcard company because it was a high end sdcard, the tech immediately said "I'm really sorry but almost every call we have had has been for this one problem with this one card. After testing we found a faulty internal chip, so we will gladly send you a brand new card that's bigger and better."
That was his experience, the problem is there's a lot of places in the food chain that could be a hardware failure, software failure or driver issue and would mimic the symptoms fairly closely.
Sent from my HTC6435LVW using Tapatalk 4 Beta
Thanks so much for sharing your experiences on that issue!
I have to say I thought of that some time ago, but since this mounting thing affected the internal one too, I didn't put too much energy into following up on that. I will now.
Cheers!
John
Going to take this a completely different way since I have never had the issues you describe, but had another thought...
I used to WinAmp for a long time, remember that with WinAmp if you have a WiFi network you can sync music wirelessly, it is how I did it all the time and to be honest if you have a solid WiFi network, it is faster than USB. All you really need is WinAmp on your PC and phone and a WiFi network.
acejavelin said:
All you really need is WinAmp on your PC and phone and a WiFi network.
Click to expand...
Click to collapse
And you need the winamp app installed on your phone; I'm a minimizer.
I appreciate the suggestion, but the winamp thing was only the vehicle that led to my discovery that the problems I had a few months ago connecting my phone to a computer weren't an anomaly. That experience left me with the feeling that my Linux system was somehow screwy.
Now I know that that wasn't the problem, and since I'm going to need to be able to connect reliably to a computer for adb/fastboot access as well, it motivated me to get some help figuring out why that was happening.
Cheers,
John
help? I recently had a hard drive issue, so i got a new hard drive and did a fresh windows 10 install. All seems to be working fine now, except I can NOT get windows to see my phones - captivate glide, s5 neo, or galaxy s7 all samsung - at all!!! The notifications say samsung_android is connected, but i cant access the files or folders at all, "my computer" brings up zilch as far as even recognizing the device fully, let alone files and folders. i dont remember having this issue before, so some update must have buggered something up somewhere along the line
more and more as the years go by, I crave windows 7. too bad support is ending in 3 months...
can anyone offer any help? Ive got drivers, though those were hard to find and didnt auto install so maybe not the *right* drivers. ive tried each version of connection several times (ptp, mtp) no dice on either. this is so irritating. Ive been literally having to remove my SD card and plug it in directly, and bluetooth between my devices to transfer anything which takes *way* longer on top of having to sit right there and click "allow for another 300 seconds" every so often.... why in the world would windows 10 restrict things SO much??
it wants you to connect your phone directly to your OS with a phone number and having to add an app to your phone. uhhhh, no thanks!!! How can i get the good old fashioned way back? I hadnt updated yet with my old hard drive, and now that this is a new install i cant go back. this is so frustrating. I just want access to my GD pictures without having to dismantle my devices.... and yes its a legit samsung cable and plugged directly in and all of that basic BS. this exact setup with this exact cable worked before. so wtf has changed with this august update (i delayed several times) to make things so unbearably complicated?
please help a frustrated user out!
No one else is having this issue?
Sent from my [device_name] using XDA-Developers Legacy app