Database Develop

[Q] Captivate Won't Charge But Will Recognize PC Connection

Edit: It looks like this is a hardware issue and I'll likely try to get it replaced via insurance since I cannot revert to stock using Odin. It is impossible to revert without using Odin right? Thanks to all who read!
To start, I just want to state that I've searched and searched for answers/information on this (not just on XDA forums either) and I haven't found a similar issue - my sincere apologies if I missed it.
Quick "this post is way too long to read" Summary:
1. Phone will not charge
2. Phone will recognize PC connection via USB but with no functionality
3. PC will not recognize phone
4. All details on what I've done so far below
Friday 3/4/11 - I used a USB car charger (link below) to charge my Captivate with a USB cable known to be working (had worked on my Captivate before, works on my brother's Captivate). If you're asking why I used that charger... well I got it for free with my E-71. I'll never use it again. Anyway later that night I tried to charge my phone on my official AT&T A/C charger but nothing happened - the phone acted like no USB was inserted.
newegg[dot]com/Product/Product.aspx?Item=N82E16882923001
Sorry for the bootleg link, this certainly isn't spam but I'm not allowed to post links yet.
Since that date, my Captivate won't charge via AC power cord. My PC won't recognize it either, but here's the weird part - my phone recognizes when it's connected to the PC via USB. For example, I can connect the phone to the PC and it will state "USB connected" on the Android pull-down (top) menu. Since I have mass storage chosen as the default, it will give me the option to send or receive files from the PC from the same menu. However, if I attempt to actually take that option, the pop-up menu which allows you to mount your memory cards does not come up. In addition, if I have the phone in USB debugging mode and I connect to my PC, the phone recognizes that as well. The PC does not recognize the phone in any capacity, at any time. No matter what I've done so far it will not charge via A/C.
Background: I've had my phone for a little over 6 months now, I've been running Cognition 2.1.6 since about 3 weeks after I got it - before this problem I haven't done any modifications whatsoever since the first load of Cognition. My PC is Windows 7 Ultimate 64. To rule out a bunch of other things, I've tried to use multiple USB cords that are known to work with a different Captivate and my Captivate prior to this problem (3 to be exact), I've uninstalled and reinstalled all Samsung's drivers on Windows, and I actually reinstalled Cognition using the three button recovery mode. To further rule out external problems, I just put Serendipity on my brother's Captivate using the same USB cord and PC that I'm attempting to use with my phone. He had been using the exact same version of Cognition I was.
I of course tried to revert the phone to stock using ODIN in order to fix the problem. I attempted to use the two button method (hold volume keys and insert data cable from PC with Odin running) but of course since the USB is not working properly that didn't work. It's worth noting that the described method worked perfectly for my brother's Captivate to revert to stock in preparation for installing Serendipity. I attempted to manually unmount and remount my memory cards several times, change USB modes between mass storage, Kies, modem, etc - nothing seems to work. The phone seems to be completely normal except for this USB issue. One last thing that's strange is if the phone is powered off and I have the USB A/C charger plugged into it, I cannot turn it on. When I hold the power button a relatively small spinning circle comes up after a second or two near the top of the screen. It disappears when I release power. If I remove the USB cable and hit power again it powers up completely normally.
Because of all of the above, I'm 99% certain that the issue is with my phone (not from any other external source). My only uncertainty is whether this is a USB hardware issue or a software issue where the phone is trapped in some sort of limbo due to being in a quasi-data mode which is causing it not to charge via A/C power and causing the PC not to recognize it. Has anyone had an issue remotely like this? I've come to terms with the sinking feeling that this is a hardware issue and that the only option I'm going to have is for my phone to be accidentally run over by a car (in order to pay my $125 and get a "new" phone under AT&T insurance). If anyone has any suggestions I'll be more than happy to try, maybe we can get this thing fixed!
If you made it this far I'll just say thanks for reading my wall of text and thanks in advance for any advice you have.

Were you able to get this issue resolved? It just started happening to my Captivate earlier today, and I was hoping that a solution had been found.

I haven't been able to get it resolved, I actually just sort of gave up on it and went back to my old phone for now. I have insurance so I'm not totally screwed, but it's not that cool obviously.
Were you able to get anything resolved on your end? If so I'd love to hear how. The one good solution would be a package to restore to stock that you could run through update.zip on a memory card, that isn't available yet is it?

i have this issue as well. I flashed Cognition 4.4 and it ran just fine for a couple weeks and then it began not even recognizing the micro plugged into any power source or the samsung dock! debugging on or off, battery saver apps removed, all that. multiple reboots. nothing. it takes a spell of, if i'm lucky, recognizing it after i eff with it for a few minutes and flukes a decent charge but at night, it usually has a loop cycle charging effect. I can hear the "boop beep" charger plugged in sound over and over throughout the night.
i use the phone in my cars and everywhere with the same problem.
no resolution! HELP!!!

I came across the same problem with USB on ARMANI I9010 after installing Cognition5. The most unpleasant is that i have bought it abroad and there is no possibility to return it
Does any body found the solution?

[Q] No USB after TWRP install

My phone isn't seen by any computer (drivers installed and up to date, it worked right before I installed) after installing TWRP. I used the app from the Play store and said yeah to the memory patch thing, then updated TWRP to 2.8.4. I plugged it into the computer, nothing. Other computers, other drivers, other cables, nothing. I undid the patch from the app. Nothing. I tried mounting storage in TWRP. Nothing. Any ideas? Thank you in advance.

Jonathan_A said:
My phone isn't seen by any computer (drivers installed and up to date, it worked right before I installed) after installing TWRP. I used the app from the Play store and said yeah to the memory patch thing, then updated TWRP to 2.8.4. I plugged it into the computer, nothing. Other computers, other drivers, other cables, nothing. I undid the patch from the app. Nothing. I tried mounting storage in TWRP. Nothing. Any ideas? Thank you in advance.
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showpost.php?p=58297902&postcount=2

Hey, thanks, I forgot to mention it's not showing up in device manager either. Nothing showing here, no sound that it's connected, no indication I've plugged it in at all.

Jonathan_A said:
Hey, thanks, I forgot to mention it's not showing up in device manager either. Nothing showing here, no sound that it's connected, no indication I've plugged it in at all.
Click to expand...
Click to collapse
is this happening when the phone is booted up, or in the bootloader, or in recovery ?

All of the above. Charges fine, but is not seen through USB at any point.

Jonathan_A said:
All of the above. Charges fine, but is not seen through USB at any point.
Click to expand...
Click to collapse
first of all make sure your using the original HTC cable as all cable don't come with the 2 required Data+ or Data- wires inside.
Boot your phone up, plug it into your computer, then check the USB settings on the phone itself by pulling down the notification bar.
These are things I would just try myself, never experienced this issue before, but really the first thing I would do is uninstall anything I installed after it went wrong, I was going to say manually flash a recovery, but that's not much help if your phone isn't being seen in the bootloader either, in all honesty, it sounds more like a hardware problem to me than software.

Yeah, I'm hoping it's something with TWRP that can be fixed relatively easily, like permissions or something, but it does seem to be hardware related. I just don't get how it could be... in any case, I'll try what you suggested. If anyone else has any suggestions, I'll definitely take them.

Jonathan_A said:
Yeah, I'm hoping it's something with TWRP that can be fixed relatively easily, like permissions or something, but it does seem to be hardware related. I just don't get how it could be... in any case, I'll try what you suggested. If anyone else has any suggestions, I'll definitely take them.
Click to expand...
Click to collapse
im sorry but ive tried to replicate this problem but messing with settings in recovery and the bootloader and cant, its sounding more like a hardware problem to me, im at a loss, hopefully someone else can shed some light on the situation.

Jonathan_A said:
Yeah, I'm hoping it's something with TWRP that can be fixed relatively easily, like permissions or something, but it does seem to be hardware related. I just don't get how it could be... in any case, I'll try what you suggested. If anyone else has any suggestions, I'll definitely take them.
Click to expand...
Click to collapse
Have you tried connecting it to a different usb port on your pc? You could also try booting your pc to safe mode and uninstalling "USB Host controller" then reboot and reconnect. I had a similar issue the other day after switching from twrp to cwm to use a cwm nandroid.
After flashing recovery my computer would not detect my phone at all. Simply moveing to a different port fixed it for me. Although when I connected to the original port, that port still would not detect my phone. Reinstalling the USB Host controllers fixed that though.

Well, I plugged it into the charging port on my laptop with a random cable the other day, and it just worked. I have no idea how or why, but it seems to work no matter what now, on all the ports and cables I thought I was having problems with. I guess I'll file this under "user error - anomaly." Thank you guys for your time.

Jonathan_A said:
Well, I plugged it into the charging port on my laptop with a random cable the other day, and it just worked. I have no idea how or why, but it seems to work no matter what now, on all the ports and cables I thought I was having problems with. I guess I'll file this under "user error - anomaly." Thank you guys for your time.
Click to expand...
Click to collapse
Happy Days

Fastboot does not work

I've been having issues with my phone for a while. If I let my phone battery die to the point that the phone shuts off, it is nearly impossible to get back on. I can boot into bootloader but that's it. The status will say "Battery OK (charging)" which is a lie. The battery is not OK and it is not charging, which is why I can't leave the bootloader and boot android. It also says "Connect USB Data Cable" even though it is connected but I'm not sure if that's typical. I usually have to play around with various combinations of restarting my phone/unplugging the USB cable until it finally starts accepting a charge.
Anyway, I'm trying to flash M but when I get to the point of using the bootloader, fastboot does not work. fastboot devices returns no devices and it fails. ADB works perfectly fine and can detect my device. I know my drivers are good because a) they were untouched and worked previously and b) I fully uninstalled everything and installed Android SDK and can access my filesystem.
I believe these two issues are related. I'm running 5.0.1 LMY47I and my phone is decrypted using whatever method Wug uses in his toolkit.

Addressing your points.
1) just because adb works doesn't mean fastboot will / should
2) SDK doesn't install drivers.
Do check device manager and uninstall the driver and reinstall the naked driver following instructions in my thread. Nexus general > sticky roll up > adb and fastboot.
You're probably right, they may well be related but I just wanted to point out that 1 and 2 don't necessarily point to that being the case.

well I did get further but it is not fixed. It is a driver issue possibly. I think I may have messed my phone up, its stuck on the "google" splash screen now
Each time I loaded something to my device, ie radio, it went back to "Connect Data cable" but if I disconnected it and reconnected it, it would then transfer.

RandoTheKing said:
well I did get further but it is not fixed. It is a driver issue possibly. I think I may have messed my phone up, its stuck on the "google" splash screen now
Each time I loaded something to my device, ie radio, it went back to "Connect Data cable" but if I disconnected it and reconnected it, it would then transfer.
Click to expand...
Click to collapse
This sounds dodgy and could be multiple issues.. Really.it's a case of ruling out the hardware.. Cable, USB port,.computer. .it's tricky because it could be driver related too.

So I tried again right after getting stuck on the Google screen and got Marshmellow working, but I still had to unplug the cable after every fastboot command completed. Windows would popup with an "Unrecognized device detected" window, and the device would show as Unknown Device in device manager under USB ports. After the fastboot command completed the message would go back to "Connect USB Data Cable" and would not work unless I re-plugged it..
I tried reinstalling the naked drivers but Windows says they're all the same and that there is nothing to update. I also have gone through the full uninstall using USBDeview . I have tried other cables, even with the charging fiasco. The one thing I have not tried is another PC but that doesn't explain charging issues.

Sounds like my Nexus 7's dodgy USB port. It's gotten a bump somewhere along the road and doesn't connect properly with the USB cable anymore. Only way I can flash anything is by firmly pressing the cable into the port the whole time.
What I'm trying to say is that it sounds like your USB port is broken. Possibly...

Well I'm just going to stick to stock Marshmallow so I don't have to worry about fastboot and I'm never going to let my phone battery die. I'll see how long I can go

USB port problem?

My T810 has stopped fast charging and is no longer connecting when plugged into a computer. But is does charge. Have tried several USB cables and chargers that work with other Samsung tablets.

Same here. Started a week ago.
Slow charging and PC does not recognise the device any more.
USB OTG does not work any more.
Additionally I see a never ending wakelock from 'Android OS'. No more deep sleep.
The issues are maybe connected.
Because the device is not rooted, I can't use WakeLockDetector to find the specific reason. The ADB workaround also does not work, because USB connection fails.

Have you tried to hard reset?

meawww said:
Have you tried to hard reset?
Click to expand...
Click to collapse
Not yet. I first try to find a solution without setting up everything again. Without root unfortunately I can't use TitaniumBackup. Without USB I unfortunately can't root.

android.outliner said:
Not yet. I first try to find a solution without setting up everything again. Without root unfortunately I can't use TitaniumBackup. Without USB I unfortunately can't root.
Click to expand...
Click to collapse
If you have twrp i think you can root your device with chainfire su

meawww said:
If you have twrp i think you can root your device with chainfire su
Click to expand...
Click to collapse
I wanted to wait until end of warranty. So no TWRP as well.
There is an older thread with a slow charging issue. A hard reset solved it in this case and it was thought that a vpn client was the reason. I use 'Block This!' and already updated it to the latest version and also disabled it and rebooted. No success up to now.

android.outliner said:
I wanted to wait until end of warranty. So no TWRP as well.
There is an older thread with a slow charging issue. A hard reset solved it in this case and it was thought that a vpn client was the reason. I use 'Block This!' and already updated it to the latest version and also disabled it and rebooted. No success up to now.
Click to expand...
Click to collapse
Yes i was also on that thread because i have 2 tab s2 1 with broken screen and 1 with charging problems too so i did is swap the mobo to get a 100% working tab. I never tried to hard reset the defected mobo because i cant remove the working lcd again because of the adhesive of the hw buttons which is hard not to break when removing screen. Hope you find solution to your problem and incase you do pls share the info mabe i can recover the other mobo, its always better to have extra item for future repair

android.outliner said:
Same here. Started a week ago.
Slow charging and PC does not recognise the device any more.
USB OTG does not work any more.
Additionally I see a never ending wakelock from 'Android OS'. No more deep sleep.
The issues are maybe connected.
Because the device is not rooted, I can't use WakeLockDetector to find the specific reason. The ADB workaround also does not work, because USB connection fails.
Click to expand...
Click to collapse
I want to add, that Odin does not see the device in download mode.
I slowly begin to assume that I have a broken USB and the WakeLocks are not connected to the issue. Or maybe Android tries to access the Port and does not find it and for that reason stays awake. Does that make sense?

android.outliner said:
I want to add, that Odin does not see the device in download mode.
I slowly begin to assume that I have a broken USB and the WakeLocks are not connected to the issue. Or maybe Android tries to access the Port and does not find it and for that reason stays awake. Does that make sense?
Click to expand...
Click to collapse
My other tab was not even showing in computer only charging with red X when connected to pc, while in normal usb charger it takes forever to charge. ive tried to chage the port with my other tab too and nothing changed

meawww said:
My other tab was not even showing in computer only charging with red X when connected to pc, while in normal usb charger it takes forever to charge. ive tried to chage the port with my other tab too and nothing changed
Click to expand...
Click to collapse
So in your case it was a motherboard failure and not a broken USB? The 'red X' and 'charging takes forever' sound familiar.

android.outliner said:
Not yet. I first try to find a solution without setting up everything again. Without root unfortunately I can't use TitaniumBackup. Without USB I unfortunately can't root.
Click to expand...
Click to collapse
Smartswitch mobile, backup to sdcard.

android.outliner said:
So in your case it was a motherboard failure and not a broken USB? The 'red X' and 'charging takes forever' sound familiar.
Click to expand...
Click to collapse
Sorry for late reply im deodexing the android 7 and de-knoxing for my tab, Yes was a faulty mobo (not sure) because i havent tried the hard reset like the dude said in the other thread.. The X in the battery is only connected to pc if i connect to normal charger it has no X but charge super slow

android.outliner said:
Same here. Started a week ago.
Slow charging and PC does not recognise the device any more.
USB OTG does not work any more.
Additionally I see a never ending wakelock from 'Android OS'. No more deep sleep.
The issues are maybe connected.
Because the device is not rooted, I can't use WakeLockDetector to find the specific reason. The ADB workaround also does not work, because USB connection fails.
Click to expand...
Click to collapse
I now tried a hard reset. Unfortunately nothing changed.
I made an OTA update to Android 7.0. Unfortunately nothing changed.
So I assume a broken motherboard or a broken USB port.
I also tried a backup/restore with Samsung Smart Switch to an external SD card. It doesn't backup the App databases/settings and just more or less random SD card folders. It does backup the APKs. You can't rely on it but it's better than nothing if you don't have an USB port. Some Apps like Nova and Solid Explorer provide backups of their settings. Use it in addition to Smart Switch and manually backup your internal card.
Thanks for your comments.

android.outliner said:
Same here. Started a week ago.
Slow charging and PC does not recognise the device any more.
USB OTG does not work any more.
Additionally I see a never ending wakelock from 'Android OS'. No more deep sleep.
The issues are maybe connected.
Click to expand...
Click to collapse
Eventually I sent the device to repair. They changed the motherboard and everything is fine now. Warranty covered the repair, fortunately.

for people have this usb port problem, I had this too before,
what i did to fix it is to use hair dryer, dry usb port for 30 secs, rest for 10 secs, dry 30 secs again, then let it cool down for 3 mins , that's it , it fixed.

kevinchg said:
for people have this usb port problem, I had this too before,
what i did to fix it is to use hair dryer, dry usb port for 30 secs, rest for 10 secs, dry 30 secs again, then let it cool down for 3 mins , that's it , it fixed.
Click to expand...
Click to collapse
Interesting technique Kevin. Any idea how this fix worked?

Mi A2 : Grayed USB options && Charging issues!!

Seen some more posts around about it but wanted to report what I'm contently dealing with.
Device is charging whenever it wants, sometimes one cable works then doesn't. My best bet for charging is my Xiami Laptop charger but even with that, I might have to plug the cable 2-3 times before accepting it! Well sometimes that doesn't work either, in that case, device has to be turned off then connect the cable and then almost 90% will start charging. Then I can turn it on and still charging...BUT... if I unplug and reconnect the cable it might not charge... yeah I know it sounds ****ed up but that's not all....!
ADB doesn't work cause computer don't recognize it. It might charge sometimes even without turning it off to do so, but still doesn't recognize it! (yeah drivers installed, believe me I have tried almost everything, I'm not new with androids)...
Finally...
File transfer and any other USB option is grayed... tried various things but haven't managed to make it work!
Well, I have read that many people encounter similar issues with this device after an update... don't know about that, when I got the phone it was like that! And it seems like no one knows what the actual problem is or how to fix it! Still, I would like to know your experience and what you think about it!
Thanks a lot for your time.

+cs.tribal said:
Seen some more posts around about it but wanted to report what I'm contently dealing with.
Device is charging whenever it wants, sometimes one cable works then doesn't. My best bet for charging is my Xiami Laptop charger but even with that, I might have to plug the cable 2-3 times before accepting it! Well sometimes that doesn't work either, in that case, device has to be turned off then connect the cable and then almost 90% will start charging. Then I can turn it on and still charging...BUT... if I unplug and reconnect the cable it might not charge... yeah I know it sounds ****ed up but that's not all....!
ADB doesn't work cause computer don't recognize it. It might charge sometimes even without turning it off to do so, but still doesn't recognize it! (yeah drivers installed, believe me I have tried almost everything, I'm not new with androids)...
Finally...
File transfer and any other USB option is grayed... tried various things but haven't managed to make it work!
Well, I have read that many people encounter similar issues with this device after an update... don't know about that, when I got the phone it was like that! And it seems like no one knows what the actual problem is or how to fix it! Still, I would like to know your experience and what you think about it!
Thanks a lot for your time.
Click to expand...
Click to collapse
If you have warranty, just go and have your phone dealt with.
My reply sounds not-fun, but, there is a post from someone pointing out that sending his phone to service centre was his solution. It is reported by him that the issue has something to do with the motherboard.

same issue
+cs.tribal said:
Seen some more posts around about it but wanted to report what I'm contently dealing with.
Device is charging whenever it wants, sometimes one cable works then doesn't. My best bet for charging is my Xiami Laptop charger but even with that, I might have to plug the cable 2-3 times before accepting it! Well sometimes that doesn't work either, in that case, device has to be turned off then connect the cable and then almost 90% will start charging. Then I can turn it on and still charging...BUT... if I unplug and reconnect the cable it might not charge... yeah I know it sounds ****ed up but that's not all....!
ADB doesn't work cause computer don't recognize it. It might charge sometimes even without turning it off to do so, but still doesn't recognize it! (yeah drivers installed, believe me I have tried almost everything, I'm not new with androids)...
Finally...
File transfer and any other USB option is grayed... tried various things but haven't managed to make it work!
Well, I have read that many people encounter similar issues with this device after an update... don't know about that, when I got the phone it was like that! And it seems like no one knows what the actual problem is or how to fix it! Still, I would like to know your experience and what you think about it!
Thanks a lot for your time.
Click to expand...
Click to collapse
i have same issue, before my mia2 working normaly, but after update v10.0.13 usb optopn grey and disable, before that i can use my usb for debuging my android app etc. now its stuck. i think in update have corrupt file system. its bug in rom update. u have solution or have been fix it?

TechnoSparks said:
If you have warranty, just go and have your phone dealt with.
My reply sounds not-fun, but, there is a post from someone pointing out that sending his phone to service centre was his solution. It is reported by him that the issue has something to do with the motherboard.
Click to expand...
Click to collapse
The warranty is off! So it looks like I'm stuck with this ROM cause, its literally dangerous to try installing something else, in case it gets bricked there will be no way restoring that phone i guess!
xplancer99 said:
i have same issue, before my mia2 working normaly, but after update v10.0.13 usb optopn grey and disable, before that i can use my usb for debuging my android app etc. now its stuck. i think in update have corrupt file system. its bug in rom update. u have solution or have been fix it?
Click to expand...
Click to collapse
Seems like there is no solution! But I bet that something can be possible, but who knows... we need to find out

I have the same problem, but the same thing that you say happened to me, I installed a rom and it gave an error and the cell phone died, it no longer connects in any way or does anything, just turn on in fastboot mode or in recovery mode, but I can't install anything, plus everything was formatted

balther said:
I have the same problem, but the same thing that you say happened to me, I installed a rom and it gave an error and the cell phone died, it no longer connects in any way or does anything, just turn on in fastboot mode or in recovery mode, but I can't install anything, plus everything was formatted
Click to expand...
Click to collapse
Well you ****ed up... The whole thing is ****ed up... Seems like the only way to unbrick it is change the motherboard!!
Btw...there is a new update that im about to install... Who knows, maybe it will fix something....

It is not a hardware issue it is a kernel issue...upon boot a "chargeonlymode" file is created in sbin folder... I am a rookie at this but after a month of digging, 2 mia2's and 4 charger modules later, something is focing our phone into chargeonlymode. If i can find the solution I will post it