This started yesterday out of nowhere, I had my phone connected to my desktop copying some music files to the SDcard. I finished copying the files and disconnected my phone. I immediately realized I missed one album I wanted so I plugged the cable back in. Boom, instant reboot. So i tried it a few more times thinking it was a fluke, same thing. I tried 2 different USB cable thinking mine may have shorted out, and I also tried connecting it to 3 different computers. All give instant reboots. So i then tried turning my hero off, taking out the SDcard, putting a different one in, and booting up. Again, reboots instantly. So, i did a full wipe and restored a nandroid from 2 days ago.... and it still reboots.
Finally I tried turning off USB debugging, and it worked fine! So no mater what I do, i can't connect to a PC with USB debugging on without it rebooting.
Any thoughts on what might be causing this strange condition? I'm going to run a RUU tonight to see if that will fix it. However even if that fixes it, i would still like to be able to understand whats actually happening here.
RUU fixed it
Just a thought: maybe the notification sound you used had become corrupt somehow? and every time you connected the USB and it attempted to play the notification sound for the USB debugging (which maybe became a corrupt file?), it caused the phone to reboot itself?
Related
for the past few weeks i have not been able to connect my phone with any computer using any cord. all are either vista computers or they have active sync 4.5. at this point i have reached the conclusion that the problem lies with the phone itself. i may have deleted the whatever it is that runs the usb on the phone.
any suggestions or past experience would help. i don't really feel like spending money on a new one. it gets frustrating when many mods are done from (or at least started) on the computer, and then require my to connect my phone.
btw... i have synced the phone many times before the problem started using all the same components i am trying now.
EDIT: the battery icon shows it is charging when i plug it into a usb, but from there, i have nothing, and i have also reset memory a few times since then too.
Thanks again from a modding newb!
-mike
How are you trying to sync it? Plug it in and wait for Active to launch? Launching Active yourself and clicking connect, or from within the phone itself?
I wonder if disabaling USB charging would allow you to sync it up again.. Have you reinstalled the computer software from the CD again?
I am sure there is something you can do aside from a full phone reset...
At first, i just plugged it in, like i do every day, and wait for active to launch, but it didn't, so i opened it manually.
I tried reinstalling from the OEM disk, and also downloading directly from Microsoft (both AS 4.5).
ill poke around and see if i can disable USB charging like u suggested. thank you.
Earlier today I was at my brother in laws house, was gonna copy some music from my phone to his computer (always have a usb cable in my car ). For some reason windows (vista) kept giving me unknown device and the option of mounting the sdcard never appeared.
I thought that was odd, never had the problem before, was short on time and didnt mess with it besides tryin to unplug and plug it back in. Well I get home and I see there is a new cyanogen build (a couple actually, mine is about 2 weeks old).
I plug in my phone with the normal usb cable I use and nothing. The phone charges (as it did on my brother in laws computer) but I the option to mount it doesnt come up on my phone. I dont see it in device manager and adb also cant find the device. USB debugging is turned on as well.
My only worry is that it is not a software problem because I got pretty drunk the other night and fell on my phone. The touchscreen is cracked a little but its just cosmetic damage, the phone has functioned 100% after that until now. Is there anything I can try here short of wiping and flashing my ROM again?
Tried searching but "sdcard mount issue" and other similar searches come up with pages and pages of unrelated stuff
Vista never sat well with my phone, ADB was a pain to get working and then, of course, I lose my data cable
But as far as that goes, I'm not even sure Vista works with the Android SDK, because I never got it to work. I was able to succesfully mount and unmount like it was a stock phone.
Your best bet is to, indeed, wipe and reflash. Use Cyan's recovery to make a backup and you can restore that after you sort things out with the sync'ing problems.
Well I have had the SDK working just fine, well adb and fastboot is all I have used on both my desktop and laptop.
Guess I will have to dig around for my adapter and give try giving it a wipe.
Well I just wiped and flashed the lastest cyanogen, before doing that I booted into recovery, hit the back button and it went into fastboot mode. I tried giving it the command to reboot, fastboot reboot, cmd prompt showed as it should be successful but it would never reboot.
I didnt think that was a good sign but I went ahead and wiped and flashed, same problem still persists. The sdcard worked fine in the adapter and both my ext3 and fat32 partition are working fine through the phone.
Anyone have any ideas? Would be nice if I didnt crack my screen, although its just cosmetic damage (phone functioned 100% for weeks now), I am pretty sure that will void my warranty if the phone were still under warranty.
This problem isn't huge, would like to be able to use adb again and not have to turn my phone off and use the adapter if I want to flash a new ROM.
Have you tried uninstalling/reinstalling the drivers in Windows?
It isn't showing up in device manager (only way I know to uninstall the drivers).
I think it has to be a hardware issue though, tried multiple computers, couple of different usb cables, wiped and flashed a different rom. Guess it's time to call up asurion
rondey- said:
It isn't showing up in device manager (only way I know to uninstall the drivers).
I think it has to be a hardware issue though, tried multiple computers, couple of different usb cables, wiped and flashed a different rom. Guess it's time to call up asurion
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=531310
try that. if that doesn't work, its a hardware problem.
Yeah that didnt work either. Thanks for the help though guys, just sucks this is gonna have to cost me money through insurance for a stupid crack in the screen.
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?
i had my phone connected via usb like a mass storage device with OpenRecovery when my pc crashed for god only knows what reason... it seems to coincide with the phone simply DYING, meaning that now it doesnt even turn on, no OR no nothing, the only thing that does work is the charging light when i do plug it in... however that is all i can do.
so did i just break it? if yes - someone shoot me... if no - how do i fix it? i dont care for whatever was on the phone since i just had it all backed up and was about to wipe everything and reinstall a new CM6 version since by mistake i've gotten myself a little older one... anyway. help?
EDIT: on second thought disregard my stupid face, something tells me that while doing nandroid backups and other crap i killed the battery and simply have to charge it, i was able to get back into OR however the phone turned off before i could connect it to the pc, i'll probably turn off panic mode and go sleep on it while the phone is plugged NOT into the pc for charging -.- I would still like to know if my theory is right... etc etc...
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