Related
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.
Greetings all,
This one is primarily for DCD but anyone with input please chime in: I have both a 6700 and a 6800 that I mess with and have run into somthing on the 6800 that is strange and wonder if anyone has hit this. I stopped at 3.0.0 and the 3.35 radio because everything is working very well for me, even the GPS locks faster than my Girlfriend's Garmin NUVI. I have in the past brought up the ##3424 code and had the PC detect the CDMA Modem and brought up the QPST in the past with previous ROMs, but with the 3.0.0 ROM the DM_Router will come up, the device manager in the PC will drop the device, but will never detect the CDMA Modem and the TX/RX packets do not increment on the phone screen. I plug in my 6700 and it works fine so I know it is not the PC. I just wanted to mess with the aGPS test fixes for the VZW unit to see if I can get lock in the sheilded switchroom at work. Does DCD or anyone know of this problem in the 3.0.0 ROM ???? I am sure that going up to the 3.16 ROM would probably fix this, but I do not want to break mine or deminish the performance. Thanks all.
madman34 said:
Greetings all,
This one is primarily for DCD but anyone with input please chime in: I have both a 6700 and a 6800 that I mess with and have run into somthing on the 6800 that is strange and wonder if anyone has hit this. I stopped at 3.0.0 and the 3.35 radio because everything is working very well for me, even the GPS locks faster than my Girlfriend's Garmin NUVI. I have in the past brought up the ##3424 code and had the PC detect the CDMA Modem and brought up the QPST in the past with previous ROMs, but with the 3.0.0 ROM the DM_Router will come up, the device manager in the PC will drop the device, but will never detect the CDMA Modem and the TX/RX packets do not increment on the phone screen. I plug in my 6700 and it works fine so I know it is not the PC. I just wanted to mess with the aGPS test fixes for the VZW unit to see if I can get lock in the sheilded switchroom at work. Does DCD or anyone know of this problem in the 3.0.0 ROM ???? I am sure that going up to the 3.16 ROM would probably fix this, but I do not want to break mine or deminish the performance. Thanks all.
Click to expand...
Click to collapse
are you sure its not a driver issue? im pretty sure the xv6700 drivers wont work for the xv6800. i use the moto Q drivers for the 6800 with QPST. do you have another PC you can test on (that hasnt had your 6700 drivers loaded), or can you watch device manager when you plug in and see if it grabs any hardware?
if dmrouter is broke in 3.0.0 there is another way to put your device into that mode via bootloader commands. i can walk you through that on AIM or MSN if we need to.
madman, did you install the wmodem drivers from the tutorial? Or are you just trying to use the 6700 drivers already installed on the PC?
Thanks DCD and GC14
gc14 said:
madman, did you install the wmodem drivers from the tutorial? Or are you just trying to use the 6700 drivers already installed on the PC?
Click to expand...
Click to collapse
GC; I used these drivers on the 6800 a while back to crack the ESN change process and later used them with the 6700, and did plug into 3 other laptops with DM_router on and as with my main machine it does not make the plug and play noise, but plug in the 6700 and all 4 laptops make the noise, and the 6800 did detect back on a previous ROM, and will active sync now so i know the data port on the 68 is ok.
DCD: I would be real interested in that knowing bootloader commands would be great, I will leave my AOL on, I am mdanley34, thanks;-)
Hey guys, I did try searching, but if I missed a post please link.
Problem is this: Randomly at the beginning of the week 3G stopped working, and along with that (probably unrelated, but never-the-less...) the phone, when plugged into any computer, would not be recognized ("Unrecognized Device" and under device status is it would say "This device cannot start. (Code 10)"). I did fix the 3G issue, but the phone still won't connect to any computer.
I've tried on computers with and without samsung drivers, with the phone both in and out of debug mode, usb storage both on and off. Currently on my PC it sees that it is a samsung device, but it has the yellow triangle, signifying that it still cannot start the device. Cannot ADB into it obviously, and cannot even get ODIN to see it when in download mode. Yes, I've also tried 2 different cables.
Using Windows 7 on all the computers I've tried it on (don't own anything older unfortunately/fortunately) and currently using ComRom 2 RC 2 PBJ (though this started on ComRom 1.3, and have tried the OTB kernel as well) thoughts?
Thanks guys!
Have you tried booting to CWM while plugged into the usb? That usually fixes it for me.
what i do is go to device managers look for your device and make sure the right drivers are installed once you install the drivers everything should be good
bryan901 said:
what i do is go to device managers look for your device and make sure the right drivers are installed once you install the drivers everything should be good
Click to expand...
Click to collapse
correct drivers are definitely installed.
hecantbreathe said:
Have you tried booting to CWM while plugged into the usb? That usually fixes it for me.
Click to expand...
Click to collapse
just gave that a shot. new dialog box popped up "usb device not recognized".
I'm probably going to try and go back to stock, but I'm not sure if that is really the issue.
Same thing here.. no idea what to do.. last time this happened I installed/uninstalled drivers until I thought I was going to puke.. even now I'm on a fresh install of Windows 7 x64 with SP1.. so .. this is really starting to suck!! Plug in the device and INSTANTLY "device unknown"... Yeah.. right!
Have both of you tried changing usb setting from mass storage to ask on connection? Uncheck usb debugging, go into usb settings change it from mass storage to ask on connection, go back and turn on usb debugging, then connect phone to computer.
landshark68 said:
Have both of you tried changing usb setting from mass storage to ask on connection? Uncheck usb debugging, go into usb settings change it from mass storage to ask on connection, go back and turn on usb debugging, then connect phone to computer.
Click to expand...
Click to collapse
I will do this promptly and post if there is a success story.. har har!! Thanks for the tip.. we'll see..
/EDIT/ Does nothing... nothing at all.. I hear the sound when USB is connected to Win7 ... then immediately says "unknown device" doesn't even seem to try and pull drivers.. it's almost ready to fly out the window...
/EDIT2/ Well I just got one step closer... I basically uninstalled ALL USB hosts, etc. Restarted, they installed.. then plugged phone in.. recognized, got the "installing device drivers", then FAILED to install... I'm lost.
Now here is the actual message that I am getting, I can only assume OP is too...
Windows has stopped this device because it has reported problems. (Code 43)
Click to expand...
Click to collapse
jbarcus81 said:
Now here is the actual message that I am getting, I can only assume OP is too...
Click to expand...
Click to collapse
Oddly enough, I'm not getting that. I'm getting error 10, device failed to start. I'm sure these are related somehow.
Also, I did try the above suggestion, with no success. I did notice though after I unchecked "usb debugging", told it to ask on connection, then re-enabled usb debugging i get "no accessibility services" which I'm not sure is an issue, but it is never-the-less an error message. does everyone get that message?
thanks for the help everyone
dopepope said:
Oddly enough, I'm not getting that. I'm getting error 10, device failed to start. I'm sure these are related somehow.
Also, I did try the above suggestion, with no success. I did notice though after I unchecked "usb debugging", told it to ask on connection, then re-enabled usb debugging i get "no accessibility services" which I'm not sure is an issue, but it is never-the-less an error message. does everyone get that message?
thanks for the help everyone
Click to expand...
Click to collapse
I get that message everytime I check usb debugging. Just click OK and everything should be fine.
All I know is that it's out-right ridiculous.. I seriously doubt there is anything wrong with either of our phones since this has worked fine to this point.. I'm just trying to get back to stock using ODIN .. but can't .. I am so frustrated I can't figure it out..
Something interesting here.. I plugged the USB cable into a port and windows said it was an unknown device.. I just plugged the cable in.. bad cable issues??
I have been attempting to fix this very problem for weeks. Nothing has worked. It won't even recognize the phone in Recovery or Download mode (Odin or Heimdall). I'm getting tempted to request a phone replacement.
For me it started right after I installed blackberry drivers on Win7 x64. Does anyone else have this in common? Maybe recently installed other USB drivers? Perhaps the problem and the install are mere coincidence? Anyway I ordered a new USB cable so I'll give that a try.
Also, has anyone trided naven's format utility? I'm starting to think this may be the signs of the USB port dying.
I wonder.. will there be an issue for service if I have a rooted phone with custom rom installed? That's the only issue right now about sending the phone back.. and the more I think and mess around with it.. if I hold the plug snug in the phone and wiggle the cable some, I can connect and disconnect... I think my cable is messed up ...
I think I have my issue resolved... Usb cable is bad... My buddy has the same cable end to his phone charger and it will charge my phone... And now my cable won't even do that... Need to find a usb cable to verify but it seems these cables are very sensitive... Check your cable OP...
Sent from my SCH-I500 using XDA App
I will update on if my issue is fixed when I get my usb cable on wednesday. Fyi, the samsung cable is available on amazon with prime shipping for around $2-3.
Sent from my SCH-I500 using XDA Premium App
Just picked up a USB cable from Walmart .. not a bad deal and guess what? Fixed 100% ... Was a bad USB cable. Never again will I use the Samsung USB cables.. only lasted about 3 months.. LoL.. All fixed!!! YAY!!!! OP - I think you will be all set as well once you get your new cable..
Replaced the cable and I still have the error. =(
I'm not sure what else I can even try...
EDIT: Fixed it. Uninstalled all USB drivers from my system and let windows reinstall them. toggled USB debugging on the device and mock locations on and it works. What an odd problem..
I Also solved this issue with a new cable. I had tried a different cable and still had the same problem.
So I wasted much of two days troubleshooting. Finally arranged for a warranty replacement but still had the same problem. I was getting ready to do a clean installation of windows and it struck me. Try a new cable, even though the two cable test ruled that out.
I figured that was worth a try before rebuilding windows.
The new cable fixed the problem. The 2 cable test should have revealed this. It's possible I had two issues and the warranty replacement and the cable fixed it.
Sorry that a second cable didn't fix the problem for the person above me.
Sent from my SCH-I500 using XDA Premium App
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..
Hello,
I have the very frustrating problem of my DNA causing my computer to crash whenever I plug it in. I just got the phone yesterday and of course the first thing I wanted to do was root it. I plugged it in, and the drivers were not installed correctly (when I clicked more information, the window that popped up said that two or three out of the five things had not installed). I tried uninstalling and reinstalling the drivers, using HTC sync when I plugged it in, but regardless, my computer will always blue screen when I plug it in. The screen says that a conflict has been detected with Windows Device Manager. I have Windows 7 and 4.1.1 on my DNA. Any help is greatly greatly appreciated!
Cody
Try a different cable
RLGL said:
Try a different cable
Click to expand...
Click to collapse
I have tried three cables so far, and it does it every time. I think it may be a conflict with something on my computer, but I just don't know what. Are there any drivers that would conflict with the DNA driver?
unccody said:
I have tried three cables so far, and it does it every time. I think it may be a conflict with something on my computer, but I just don't know what. Are there any drivers that would conflict with the DNA driver?
Click to expand...
Click to collapse
what happens if you go into safe mode on windows and then plug in the phone? F8 when starting windows gives you the options. EDIT: and have you tried different ports not just different cables, and is it a USB3 port?
unccody said:
I have tried three cables so far, and it does it every time. I think it may be a conflict with something on my computer, but I just don't know what. Are there any drivers that would conflict with the DNA driver?
Click to expand...
Click to collapse
If USB debugging is enabled try disabling it, also having multiple device drivers can cause conflicts as well, consider removing drivers from past devices, may help.
Tapatalked from my HTC DNA - Carbon
reaverclan said:
what happens if you go into safe mode on windows and then plug in the phone? F8 when starting windows gives you the options. EDIT: and have you tried different ports not just different cables, and is it a USB3 port?
Click to expand...
Click to collapse
I have tried it in safe mode, and it still crashes to the same blue screen. Also, I believe my computer has all usb3 ports. I will try all of them in a second. An update: I tried it on my friend's computer, and everything installed fine, and I would have rooted if Verizon hadn't stopped htc dev from allowing us to unlock
pio_masaki said:
If USB debugging is enabled try disabling it, also having multiple device drivers can cause conflicts as well, consider removing drivers from past devices, may help.
Tapatalked from my HTC DNA - Carbon
Click to expand...
Click to collapse
Thank you, I have had USB debugging on, so I'll try it with it off. And I think I have all previous HTC drivers deleted but I will double check.
Also, if you haven't already, try another PC, just to make sure it's not an issue with your phone.
Kevin5377 said:
Also, if you haven't already, try another PC, just to make sure it's not an issue with your phone.
Click to expand...
Click to collapse
I did and it worked fine, so it has to be an conflict with another driver or program on my computer I guess... That's hard to troubleshoot.
Remove all drivers and software related to phones from your PC. Start fresh with new drivers once you finish that.