So I have been having some trouble lately. I'm running the latest versions of everything and have been having a few USB problems. First, my phone was mounting as a usb device even when set to charge only. Then, USB Debugging stopped working. I redid the entire thing, using the PC36IMG.zip that contains the image for the latest OTA and Radios and patching with Superuser. It worked for a while, then a couple days ago the charge only stopped working again. Now my Evo rebooted on its own while plugged in, something I've heard of but never experienced with any Android phone. After the reboot, USB Debugging stopped working again. Please, if anyone knows what I can do to fix this, please help. I'd be willing to give more information if needed. I'm fairly good at ADB, but can't seem to fix this problem. Thanks.
Related
Hi everyone!
So, I've been using my DHD since.. last November, of course I almost immediately flashed it and now it's running Cyanogenmod 7.
I tried many other ROMs before Cyanogenmod, but I found this one the best suiting for me.
So, on to my problem. My DHD has started screwing with me and it won't connect to as a USB storage device anymore, when I plug the usb cord into a PC and the other end of course to the DHD, the orange led just lights up but nothing else happens, nothing on PC end or the phone end.
I've tried this on multiple PC's and all do the same.
Not yet have I tried changing the rom, but could that be the issue, or is something broken, or could something be broken?
Also, if something is broken, am I able to convert back to original state for warranty?
Thank you for any answers.
-Joonas
Yeah, I installed Android Revolution HD rom on my phone, still the same problem exists.
So I'm starting to think it's a hardware fault, and should I send the phone for warranty?
I'm not sure how to revert all the changes I made, so any guidelines for that?
Device: Desire GSM
I installed insertcoin 1.1.3 on monday and it seemed to have sorted the problems I had with crashing sense.
However I did have a problem with usb detection on win7 64 at one point. I had a demand for a scan pop up- this is something that occured frequently when my camera was still crashing. I cancelled the scan and Win7 sprung me a device error. That had not happened before.
I just unplugged/replugged and the issue was solved.
The next day I saw the 1.1.3 and 1.1.4 updates solved usb tethering issues. I figured why not try and updated, then flashed the kernel (without booting).
Result: windows won't recognize the device anymore, doesn't accept android usb drivers for it (the device returned an error). It is shown as unknown device in device manager. Furthermore, after trying to connect the card can no longer be mounted by the phone.
A restart sorts it, but it's still not very satisfactory. Does anyone have the same problem?
Did I flash the wrong kernel? It said bravo...
Meanwhile I'm going to go back to 1.1.2 and stay there...
Sounds like usb brick. A guide how to fix can be found here on xda.
TouchPaled from Oxygen with Transparent XDA App
Not a phone issue
Well I went back to 1.1.2, flashed a different kernel, flashed leedroid, then back to 1.1.2.. all of which gave no joy. Same issue exactly.
However finished my sick leave and it connects fine on my work pc.
So it's probably the cable and I'll check that tonight (was a bit too ill to crawl around the back of my home desk) and report.
(for those who found this by searching I guess RMD recovery is the USB Brick fix.)
No that's not the usb brick fix, it's a recovery. By using the search one can find a guide extra for usb brick.
TouchPaled from Oxygen with Transparent XDA App
So it turns out to be a faulty cable, and that is that.
Hey guys
i recently flashed codename android 1.3.3 and i could no longer mtp host so i switched roms and still not dice i flashed every kernel and nothing is working does anyone know how to fix this or and i screwed. to be clear my phone still charges it just wont mount to transfer files. adb does not recognize that a phone is plugged in either
thanks in advance for all the help
Matt
Mine is doing this now as well following AOKP Build 23. I haven't bothered flashing anything else yet as I was doing preliminary research before work to try to find out exactly what happened and how I could fix it. (No answer yet).
Edit: I found a solution. It won't automatically turn on anymore, but I can turn it on manually under Settings > Storage. Problem fixed (for me anyway).
no idia??how can improve this
i tried that still not working is there any way to uninstall the drivers from the phone?
Had this problem after installing AOKP 23 too. Have to turn on manually.
Working now.
Could be that you have a faulty USB port. Many have reported about this here http://forum.xda-developers.com/search.php?searchid=15930021
My GSM unlocked GN, running original ROM IMM76D with Franco kernel Milestone 3, stopped responding to being plugged into a USB port using the original cable (I don't have another cable atm). I just wanted to change some music I had on it and I realized it just doesn't detect the phone.
Since I tried an OTA update to IMM76I that didn't work, I thought it might have fiddled with something, so I decided to upgrade to IMM76I using the trusted toolkit which I've already used several times.
[on win7 sp1 64bit]
I managed to browse the phone when it was in recovery mode (ADB), and take off it my various backups - not via the toolkit. Flashed, unlocked, rooted, the works. Restored apps. Plugged back into the computer... Nothing. The computer reads it when in fastboot or recovery though. If the device is plugged in before fully booting into Android, it works fine. If I unplug it and try again - when android is fully up and running - no cigar. It doesn't even read on the toolkit. Receives power though.
I've tried connecting the phone to other computers (other win7 no sp1, xp), still nothing. That's why I assume it's a phone software problem, but I can't figure out what. Did anyone encounter this phenomenon?
Do you have fast-charge enabled?
Also make sure MTP is checked in Settings>storage>options.
MTP is on and always was.
I have supercharging on via the franco app. I'll try turning it off and plugging it in when I get home.
Sent from my Galaxy Nexus using XDA
That is why. If you disable USB fast charge it'll work great again.
Only use fast/supercharge, if you're in a hurry to charge your phone, like in a train, or something...
When you're at home, just leave everything as it is, and you'll never have problems, like that...
If that then doesn't work, reinstall the drivers
thanks people! I'll send franco an email about mentioning that supercharging disables data right next to the enabling tickbox.
Not home yet...
Sent from my Galaxy Nexus using XDA
Hey guys... after using the Clutch V1.0 for a while, my computer stopped recognizing my USB cable last night. I tried installing the drivers again, tried restarting the computer and the phone, no luck. I finally just installed a fresh copy of the Rom and everything worked fine. Question is, anyone know what actually causes this and if there's something to fix it if it happens again? It's a pain to start fresh, so hopefully there's a solution out there. Thanks!