Hi guys
I own an Desire
Recently, after installing the newest version of cyanogen stable release I found out that my bluetooth cannot be loaded and also I have problems connecting the phone to comp by the cable data. It looks like charging and 90% of cases it is unrecognized by comp.
I tried restore factory defaults, wipe data, installed at least 3 new OS.. same problems every time.
Where could be my problem other than in OS and how it can be fixed?
Thanks in advance for your time.
USB brick? Search for a thread like that here somewhere.
And try to flash a different ROM and wipe everything (data/sd-ext/dalvik).
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.
Hi, So i bought this Desire HD second hand about two weeks ago and it was already with Android Revolution version 6.1.0 by mike1986. As soon as i got it the flashlight app sometimes shuts off the phone when i open it, now two days ago i was on the internet(mobile network not wifi) and the phone rebooted and from then on it kept rebooting until i removed the simcard then it powered on ok without sim. Now whenever i plug in the sim it keeps rebooting the only way to power it on with the sim inserted is to connect the charger and power it on while charging then its ok. Please help me if you can as i desperately need the phone.
Now its also shutting off when im playing a game, sometimes when using the camera, even when i was using qrcode scanner.
My phone was also rebooting randomly. I send my device back to HTC and they changed motherboard and a lot of another things
It was in warranty, so i had it for free
How about if you superwipe, then reinstall the ROM?
You can get 6.3.2 (& superwipe) for the ARHD ROM here http://forum.xda-developers.com/showthread.php?t=840040. This is the stock HTC ROM, tuned by mike1986.
There is also the version 7.0.4, which is in fact a Gingerbread port from the Sensation. Given your problems, probably best to start with 6.3.2
If that doesn't help, it's not a software thing, so it must be hardware. The phone should be under warranty, so you could return it to the ex-factory state by flashing the standard ROM for your territory, and then take it to the service centre. There are several threads on this here.
Also SD card is known to cause this issue, try booting without SD card.
Yep, super wipe or full wipe is the best idea. Try the full wipe first and then root the phone again. Check the ROM section for the latest ROM updates, sometimes these things go wrong and it simply requires a full wipe and flashing the ROM again.
Hi Thanks for trying to help guys
So far i did clean wipe with superwipe, flashed radio,flashed Revolution rom 6.3.3,flashed the kernel and the problem is still there.
The only thing that is going over in my mind is why does it hold on for a little bit while its connected to charger if the phone is idle, but then sometimes when i open flashlight or camera or play a game its reboots again.
Try flashing an appropriate RUU, if the problem persists then you know it's hardware and it is still under warranty so return it to HTC for a fix.
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!
PLEASE IGNORE THIS. I SOLVED IT.
I have 2 debs and both are running the AOSP Pie ROM, currently. Until 2 days ago both were able to detect my SIM card; now only one does. Here's what I've done to resolve what I first thought was a hardware problem.
* I swapped SIM cards and rebooted; no luck.
* I soft rebooted; no luck.
* I turned on Airplane mode and tuned it off; no luck.
* I swapped out the USB charging daughter board (I had a spare) to which the SIM adapter is soldered; no luck.
So, I thought it was a software issue. I ran Wugfresth, which I've had installed on my Windows PC forever, and went totally back to stock 6.0.1; no luck..
Then I booted into recovery, wiped Dalvik, System, Data and Cache, and formatted Data, and flashed AOSP, Gapps 9 Micro, and Magisk again; but still no luck.
What could it be?? I must confess that I'm somewhat of a
serial ROM flasher, and I'm not even sure how to frame this question, but could the firmware "radio" have become corrupted in one of my serial re-flashing episodes? I hope someone can help me.
Thanks