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.
Related
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.
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?
EDIT: SOLVED!!!! it was a usb brick. see last post for details.
hi all,
I have a problem with my desire.
Bluetooth won't turn on. If I try to enable BT, it says grey'ed out for like 10 secs and the goes back to unchecked.
I got this device used so I don't have many background information. All I can tell is I tried different ROMs and wiped all I could, but still no luck. I actually highly suspect this might be an hardware issues, but I'd really like to try everything before shipping back to assistance.
Here are my current specs:
htc desire amoled
bravo pvt1 ship s-on
hboot 0.80.0000
radio 5.11.05.27
rom cyanogenmod 7.1.0
kernel 2.6.37.6-cyanogenmod-geb50077
Recovery: Clockworkmod
ANY hint highly appreciated.
Got exactly the same problem.
BT worked while running the former stable CM release. I first noticed this issue when flashing latest CM. You tried other ROMs which didnt work?
Did you try other Radios as well?
I am not an expert, but I think it could be a problem of the radio. I never totally understood what the radio does, so could anybody help with this guess? I never changed Radio as there was no need for (never touch a running system).
lexo, did you try rolling back to 7.0.3 to see if BT would work again?
I was also thinking about radio, exp b\c it seems to not be a ROM-specific issue, as I have tried several: LeeDroid, InsertCoin, MIUI, as well as a stock rom.
I believe the point with radio is not necessarily about having the latest, but finding the one that works well with one's rom. Also, there is RIL, but that I don't know what it does.
No, didnt try that yet.
I use BT in my car to listen to music only so I didnt notice the issue at first. Now i am thinking about buying Galaxy Nexus, so I am not too exited about that point. But as I am willing to pass my Desire to my lil sister I would love to have it fixed.
Whats "RIL"? Think I never heard about it.
Don't know if this is relevant but had a similar problem with Bluetooth, wifi and Mobile data yesterday. None of them had connectivity!
The remedy that worked for me was to wipe the cache and dalvik, reflash CM7.1 via recovery (but remember to also flash the Google apps package) and soft reset.
No data is lost this way.
Hope that helps!
Sent from my HTC Desire using XDA App
This may not be relevant but when I couldn't enable Bluetooth on my done when I have a USB brick.....
Try the USB brick fix it may work
Sent from my HTC Desire using XDA App
update:
so far I did:
- wiped everything including dalvik and reflashed cm7 - no luck
- removed files in etc/bluetooth [read somewhere] - nuthing
- applyied a .zip update that is supposed to fix a possible USB brick - no change.
@LEXO: I think you might try the first two things I did, in your case they might work.
So now I flashed a RUU Rom and reverted to stock s-on bootloader, hboot, radio (ril, too, I believe, though I dunno how to tell ril version) and recovery.
The only thing I'm not completely sure about is the USB brick fix, but otherwise it's ready to ship to assistance.
@Reaper, can you point me to the USB fix you referred to?
guys!!! Thanks everyone, expecially reaper.
My BT is working again!!! turn out it was a USB brick, which I was able to solve fairly easy.
I had tried a usb brick fix that involved flashing a .zip, which I did. However still no BT changed so I assumed phone was not bricked after all.
Also, I always assumed usb brick would involve major cd and usb connect malfunctions, and that was not my case at all.
However it must have been that fix that didn't work, because I then followed the guide on this forum http://forum.xda-developers.com/showthread.php?t=691639: got my CID via fastboot, modified the files accordingly, put them on sd card, got temp root with visionary, issued the necessary commands with "free root system tool" terminal, rebooted, and voilà! BT is finally green.
I can't believe I made it!
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
Whenever i connect phone to pc, the option on the phone on whether i charge only or mount etc, doesnt show up. Even after a fullwipe problem persists. I have to mention that this came up after installing v6supercharger, but even after fullwiped and reinstall rom, still cant make it work. Any help will be welcome!
Using GingerSense4 with RCmix3d v12 kernel
Also, the PCSCII.apk is installed, and reinstalled, but the service is not running (under Application-management-services).
Problem semi-fixed. Flashed the PCSCII.apk from this guys thread: http://forum.xda-developers.com/showthread.php?t=1559683&page=9
But you have to untick the "ask me everytime i connect" button on settings, and manually change whatever you want.
I'm having this same exact problem, and tried all the same things; I've been scavenging the internet for a fix, but have yet to find a solution.
In my case I'm on a rooted Inspire(same as Desire) HD, running Android Revolution HD ver. 6.3.1. This problem didn't occur right after any of that though, It's been working fine this whole time up until 2 days ago(to my knowledge at least). "Funny" thing is I've had this happen before with this same model of phone, and that one wasn't rooted.