I have had an HTC Desire via T-Mobile UK for a couple of months. It runs Android 2.1 with HTC's Sense interface. I have made no modifications to the phone. This evening the phone would not turn off so I removed the battery. Then it would not boot.
When I press the power button, the screen comes on, the phone vibrates (once) and I get the red ring -- and that's it. It sits with a blank screen apart from the red ring/disc.
I have tried removing the battery (that's the only way to switch it off), removing memory card and SIM. Still nothing. Then I tried a factory reset by clearing the memory, which appeared to work -- but no improvement. It remains stuck at the red disc.
Is my phone goosed? Is this a hardware fault?
The only thing I did before this problem was to try to install Swype using a APK file via my memory card and installing a third party app installer. The app installer did not find the APK file on my memory card so I couldn't install Swype - but I noticed a lot of forced closes before I tried to switch off. I presumed switching off the phone would resolve this. Then my problems began...
I don't think it's f***ed... try a hard reset, if that doesn't work flash an original HTC rom again.
bobbyelliott said:
I have had an HTC Desire via T-Mobile UK for a couple of months. It runs Android 2.1 with HTC's Sense interface. I have made no modifications to the phone. This evening the phone would not turn off so I removed the battery. Then it would not boot.
When I press the power button, the screen comes on, the phone vibrates (once) and I get the red ring -- and that's it. It sits with a blank screen apart from the red ring/disc.
I have tried removing the battery (that's the only way to switch it off), removing memory card and SIM. Still nothing. Then I tried a factory reset by clearing the memory, which appeared to work -- but no improvement. It remains stuck at the red disc.
Is my phone goosed? Is this a hardware fault?
The only thing I did before this problem was to try to install Swype using a APK file via my memory card and installing a third party app installer. The app installer did not find the APK file on my memory card so I couldn't install Swype - but I noticed a lot of forced closes before I tried to switch off. I presumed switching off the phone would resolve this. Then my problems began...
Click to expand...
Click to collapse
does the triangle look like this... /!\ if so press volume up and tap the power button.
hope this helps! good luck!
The device has been factory reset. Several times. No difference. Maybe a new ROM will cure it. I'm surprised that a ROM could be so easily corrupted. This "red ring of death" on an HTC Desire might become more common in the months ahead.
OK. I promised to report back when the problem was resolved.
I got the phone back yesterday, one month and three days after I sent it for repair. The company I sent it to (the one I had the warranty with) could not fix it so sent it to HTC.
The device has a new IMEI, which tells me that the motherboard was replaced. It was, therefore, a major hardware fault and not an OS/software fault.
I'm not sure if it was a coincidence that I was messing around with non-standard software (using a non-Market source) or whether this goosed my mobo but my mobo was most certainly goosed.
So, for posterity, the red ring of death on an HTC Desire (and possibly some other handsets) is, indeed, a ring of death. The phone is f*cked.
The red ring you talk about seems to be some kind of error screen on T-mobile handsets. As far as I know, a non T-mobile handset has a black screen with 4 triangles, 1 in each corner.
Glad you got it sorted though
rolfd said:
The red ring you talk about seems to be some kind of error screen on T-mobile handsets. As far as I know, a non T-mobile handset has a black screen with 4 triangles, 1 in each corner.
Glad you got it sorted though
Click to expand...
Click to collapse
its no error screen it is part of the t-mob boot up process
Related
Today my friend got his HTC Desire, attempted update to 2.2 (I think that's what he tried)...
before the update started, the screen went black. He cancelled the update and hard rebooted the device. Still no luck. there's nothing appearing on the screen at all.
The other features of the device all work, the phone works, and the touch screen is registering input, the reboot key combination appears to work, but the screen isn't displaying anything, and the backlight isn't coming on at all.
Any ideas as to why this is happening, and what can be done to make the Desire desirable once more?
Have you tried rooting it?
is it a branded or debranded Desire?
Can you confirm what it was he was doing??
It's a UK o2 branded Desire, he was attempting to debrand at the time.
We have tried both warm and cold reboots
This sounds like a hardware problem. I am facing the same issue, but it's sporadic. For me it started before I rooted (so I don't think it's related), and the screen went blank with a single pixel width white line at the top. After a while the screen would gradually go green. I found that it fixed itself after either taking the battery out or waiting a while. I'm gonna return my handset after I unroot it (t-mobile uk, locked), but will have to wait till I get back from abroad. I'm hoping the t-mobile update won't be out when I get back cos I want to be able to root it.
Sent from my HTC Desire using XDA App
he's had it replaced by o2... thankfully he hadn't rooted it before the problem occurred, and they straight up swapped it for him
I have a six months old desire (still under guaranty), not rooted, with froyo.
Lattely it it doing some weird things:
- randomly (once a day) the phone freezes, so i have to push home button after that happens and the phone goes to stand by, i cant wake it- the buttons lights up but the screen stays dark (i have to take out the battery to restsrt the phone)
-sometimes my phone isnt ringing when someone is calling
Can someone please help me, what should i do (should i root and try another ROM or sent it into repair?).
tank you
First try a normal factory reset. If the problem is gone you can root or keep using it unrooted. If the problem is still there just send it to repair.
I have already tried a factory reset and it is the same. Does that mean it is a hardware problem?
Would say so, if it's unrooted there is no other real reason for these problems. You can try to see if a custom rom fixes it but I wouldn't try to fix a phone still under warranty by breaking the warranty. Just send it back to HTC unless you can't miss your phone for a month.
Could it be possible that my sd card is causing the problems?
yesterday i have inserted another sd card and the phone seems working fine now.
I tried running the card i previous had in the phone on my computer ani it did not work ( didnt even find it).
So im wondering if the card was fault for the desire behaving weird? I gues i will have to wait for a couple of days and see what happens.
What do you guys think?
Sounds exactly the same as mine. I had to remove battery once a day due to freezing, missed so many calls.
Tried rom upgrades, factory resets, new SD card, still the same.
Finally sent it to HTC UK service who replaced the mainboard, all good now.
Phone was returned in less than a week, really happy with their service.
Same here sent it to repair got a new main board and all is good. HTC repair is better than most
Sent from my HTC Desire using XDA App
My friend is running CM 7 on his Tmobile G2.
He was describing that yesterday was acting weird with market downloads.
Here is what he he emailed me on what happened.
the phone was acting normal throughout my day until the evening towards the night, i noticed it failed to finish downloading the update for google earth along with google maps. the phone was fine, and then i pulled it out of my pocket a few times and saw multiple times that it was randomly turned off. i would turn it back on and it would still give me the same issue. when i got home and plugged it in to charge, it would boot and then get to the main home screen telling me that google maps is downloading to update. however the update would be frozen, and a few seconds later the phone would freeze altogether, forcing me to turn it off by pulling out the battery. this happened about 4 times, and now has reached the point that it has become a brick and refuses to turn on or show the charging light
any suggestions on what might be wrong with the phone? Thanks in advance. Im running Cm7 on my phone and never experienced this issue.
same happend to me 3days ago, phone running then freezed... bootloop after batterypull... recovery worked for 2 times but had problems with flashing new rom/backing up -> errors with cache partition...
after 4hours of letting it stay off -> it wont turn on again und wont charge (no LED)
tried it with another dz battery+charger... no change... i wrote htc and they answered within 1hr that i have to send it in without battery...
i guess its a known problem (or why wouldnt they want to have me sending in charger+battery .. if its a power-on problem..)
there are semibrick threads here and in other forums.. but they all don't suffer from the power on problem... so i guess i did the right thing sending it in
edit: never had heat issues, never had random reboots, no overclock, no indication of an update from any app did any harm to my phone, running cm7 for 3 weeks without any problems, no hboot flash, no radio flash ... nothing that would indicate a risk of brick (according to guides & forum threads)... first htc that ever failed for me ;(
Thanks for the reply. I will forward it to my friend. I think he is going to try to exchange it at the store and if it all fails we are going to try HTC.
have any of you tried to boot into recovery? did you have eng-hboot on your devices? go to #g2root
its complete dead as in dead... no LED light, no turn on, no hboot mode (or what its called when you press vol+power key).... i dont have a g2 but a unbranded european dz.. hboot and radio was never touched by me
Similar thing happened to me. My phone kept frozing on me running cm7..was fine for a week though.
So I booted into recovery..wiped cache,factory reset flashed another rom got bunch of erros recovery thing rebooted stuck i n htc logo for like 20min yanked out battery rebooted and it never rebooted back. No hboot,no nothing.
My light indicator still worked though but no hboot or anything.. got a new one now have to send the old one back to tmobile but I'm scared that they're gonna charge me for removing void stickers.
Even though I checked twice that removing void sticker won't avoid warranty according to tmobile customer chat sevice..
So I'm thinking about swiping out the sticker that contains serial number and such on back of our phone with the old one and tell them the new one came without a void sticker lolol
Sorry I got way off topic rofl..
Sent from my HTC Vision using Tapatalk
We went to the store today and exchanged it for another g2. The guy didnt ask any questions and exchanged it happily for a new one.
This very same thing happened to me today. Updated to CM 7.0.3 from 7.0.1 and the phone was freezing when installing items from the market. Pulled the battery and the phone was stuck on the boot animation. Pulled the battery again, and now it will not start at all. No charging light, no nothing. Had more than 50% charge, and now it seems entirely unresponsive. I can't use the power w/ volume button technique either, because the phone does not respond.
Seems like somehow I have bricked the phone, or the phone just coincidentally died just after updating to CM 7.0.3? (seems unlikely)
just a short update on my case:
i got the mobile back from HTC repairs.
they exchanged my "mainboard" (changed IMEI) under warranty.
i don't know what emmc chip i had before cause it died so fast, but my usb deviceIDs changed completely and are now simmilar to the ones in the cm wiki.
my current emmc is now:
$ cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc0/mmc0:0001/name
SEM04G
Click to expand...
Click to collapse
might help ppl.
Has anyone experienced any spontaneous reboots on their ZL yet?
Mine has done it twice, both times while doing things related to Google apps or accounts. The first time my phone rebooted, I was actually adding my Google account after a reset to fix the notification LED issue. When I unchecked the option to backup and restore my Google account, my phone blinked the xperia logo, then rebooted (Sony logo, xperia logo, boot animation then done). It was a very quick reboot.
The next time, I was installing apps from the Play Store. A bunch of apps were queued up, downloading and installing over Wi-Fi. I hit the home button, then was about to open up a folder to check my Gmail app settings when again, the phone blinked the xperia logo and proceeded to reboot. When it was done, it continued to install my apps as queued from the Play Store, as if nothing happened. It hasn't done it since (of course, this was only a few hours ago).
My phone is not rooted & I have not messed with the bootloader unlocking or anything. It's 100% stock while I'm evaluating it against my SGS3 for a potential permanent switch. I've got the US C6506 model (black, on AT&T -- LTE is working fine).
I really, really like this phone so far, and I'm just hoping that these two reboots were a random oddity, not to be repeated.
Interestingly, I actually fully set up the phone yesterday evening, but when I discovered I had the notification issue, I reset it this morning and re-did all of it. The phone did NOT reboot at all yesterday in the 4 or 5 hours I spent playing with it, either. It sat in standby overnight without incident as well -- all prior to the reset today & the 2 subsequent reboots.
I guess from here it'll be a waiting game to see if it does it again, but in the meantime, I was curious if anyone else had seen anything like this with their ZL.
Yup, seen it twice myself. First time, I noticed that it had rebooted when I couldn't find any previously running apps. The second time I was in the Settings screen when it randomly rebooted. I was just about to click the Display setting when this happened.
I'm just running the stock ROM on the C6506 model. I'm keeping an eye out on it and will see if there is a pattern.
rajeshr said:
Yup, seen it twice myself. First time, I noticed that it had rebooted when I couldn't find any previously running apps. The second time I was in the Settings screen when it randomly rebooted. I was just about to click the Display setting when this happened.
I'm just running the stock ROM on the C6506 model. I'm keeping an eye out on it and will see if there is a pattern.
Click to expand...
Click to collapse
Thanks ... in some ways it's good to know, and in others, it worries me. I hope it isn't a pattern, though. Thus far, I've used the phone since the two reboots without incident (music playing, bluetooth connections, and phone calls).
EDIT: A third reboot. This time I had just updated a few apps in the Play Store, returned to my home screen and was about to turn my Wi-Fi off when it rebooted. One common thread thus far is that my Wi-Fi has been on each time. I have no idea if that's related or not, though.
I have been using mine for 1 week and have not had any reboots. I am using the hspa version (c6502) and I am a heavy user
Seems to me that the random reboots are isolated to 6506 models. I haven't had one single reboot in the past week I have been extensively using mine (6502). However, while I was on CM10, my phone hung and rebooted like hell.
Yeah I'm c6502 aswell no random reboots.
Sent from my Nexus 4 using xda premium
No reboots on C6502
Same here, have been using my ZL (C6502) for the past 22 days without a single reboot or freeze. Heavy usage for last week or so (wifi on all the time). I too think this and the low call volume issue might be specific to C6506 (LTE) version.
6502 here as well, no reboots so far and I'm rooted. Been about 2 weeks.
I'm starting to think this issue is unique to me and/or my phone -- at least my specific case. Actually, I'm glad for that, because I love this phone.
I realized I may in fact have memory card corruption. I'm going to explore that further, because I had some serious issues with my SGS3 corrupting microSD cards. I thought it hadn't done it on my current card, but I have discovered some corrupted sound files on it, so I think I'm going to do a format of my microSD and see what happens.
Thanks for all the input, folks!
I had some reboots in past one week
using since March 10th
today itself had 2-3 reboots
one more thing is had blank screen during a phone call also
we need Roms for this device I never understood
why there is so much delay in release of custom Roms
Once,
but not sure it was rebooting. Cuz the screen went blank. Then i had to press a tiny yellow button that says off near the sim slot. Then it came back to life. Plus my wake up button is kinda hard to press. Do you guys hv that problem?
Sent from my C6502 using xda app-developers app
safuan7822 said:
Once,
but not sure it was rebooting. Cuz the screen went blank. Then i had to press a tiny yellow button that says off near the sim slot. Then it came back to life. Plus my wake up button is kinda hard to press. Do you guys hv that problem?
Sent from my C6502 using xda app-developers app
Click to expand...
Click to collapse
I wouldn't call that a reboot, at least not in the sense that I was seeing them. That's more like a freeze that would require a battery pull on a phone with a removable battery (I used to have this all the time on the Samsung Captivate).
My ZL was rebooting fully right in front of me (screen goes black, then the xperia logo, followed by the full normal boot sequence, just very rapid -- the boot animation is shorter than a cold boot).
Note -- I have not actually fixed my memory card yet, and I have not seen any more reboots. I'm nearly a full day on my current battery charge, too.
I have the C6506 also, and I get numerous random reboots also. I did get few logcats, but I have not seen any revelant info that causes the random reboots. I replaced my micro-sim, thinking it may caused modem panic reboots, but that wasn't root of the problem. However, I did notice that the reboots occurred less without micro SD card, but I haven't completely made that conclusion yet (I want to listent to my music!).
I also have a 6506 and have been experiencing some kind of reboot. Not a full reboot that the OP has been talking about, but one where my screen just turns off. At first I thought better battery stats was just having issues as my stats would end up all out of whack for no reason. Then today the screen shut off while in use. I only had to push the power button to get back to my lock screen. But again my stays were all out of whack. I'll have to pull the log later but I hope this is is just a software issue.
Qmann05 said:
I also have a 6506 and have been experiencing some kind of reboot. Not a full reboot that the OP has been talking about, but one where my screen just turns off. At first I thought better battery stats was just having issues as my stats would end up all out of whack for no reason. Then today the screen shut off while in use. I only had to push the power button to get back to my lock screen. But again my stays were all out of whack. I'll have to pull the log later but I hope this is is just a software issue.
Click to expand...
Click to collapse
Interesting. I've replaced all my corrupted files on my microSD card as of now, and so far, aside from that first day, I have not had a single reboot of the kind I saw before. Actually, no reboots at all, and my current uptime shows it (111 hours).
What happened to me was I had had a bad microSD card in my SGS3 -- files would become corrupted with time on it. I finally replaced it with a new one, but apparently when I copied my data back to it, I inadvertently copied a few of the corrupted audio files (notification sounds, actually) but never noticed it. I realized this when I was resetting my notification sound for text messages and heard the signs of corruption in the file, and so I began to think my phone had been responsible for the corruption. I know now that that can't be true -- otherwise I'd have some corrupt photos as well, and I don't. Only a few select sound files were bad, and because I keep regular backups of the contents of my microSD cards, I just copied the wrong ones (d'oh!).
Of course, I've had random reboots on android devices before (Asus TF101), so I'm quite wary of them -- if I see anything further, I'll post about it.
I looked at the log and saw nothing conclusive that would be making my screen turn off. I also checked my up time and it hasn't reset, so I know it's not a true reboot. When I put my SD card in I just wiped it from the phone. The only thing I put back was music files. Thinking about that now it wasn't the clean start I usually give my phones. So I just wiped the card again and we will see today if anything happens
C6503 here and I've been getting a couple reboots a day since I bought it. 2 days ago I used PC Companion to solve another issue (random loss of network signal) by reinstalling the phone software and that seems to have fixed it. Unfortunately the random reboots are still present.
I don't use any SD card at the moment.
I've now been using my ZL for a month or so, and since that first day when I made this post, no spontaneous reboots at all. I have no idea how or why, they just stopped on their own.
Hi i have this supper anoying problem after 5.0.2 update! So basicaly What it does is when ever i will pick up the phone it would turn off like the screen would dim (not rebbot or shut down) and after a little tapping on a screen it would turn on again and sometimes when it does that it would glitch a little. While typing this it happened twice its sooooo anoying idk what to do now if i wont find any solutions i will just buy samsung galaxy or something like that. Also my carrier is Virgin Mobile thanks
Same problem, same phone.
Definitely annoying! Seems random but especially while rotating for me. I have not been able to dig up any solutions thus far.
Check out your proximity sensor settings in the HTC testing app, or try Gravity screen. Mine did the same thing a couple times, also clean off your screen at the very top left, if you look real good you can see the sensor just under the front camera hole in the glass, also sometimes a screen saver will mess with this sensor. One more thing is the stock lock screen can cause an issue similar to what you are talking about, hope one of these help yo out, cane0716
Sent from my 710C using XDA Free mobile app
hi
thanks for information i already gave that phone to my friend and i think he fixed it by actually having different lock screen i currently have samsung galaxy s5 its wayyyy better lol
Phone turns off during use and will not complete boot unless plugged to charger even when the battery is almost full.
This error started last night after I did factory reset because of observed phone lag. I did mistakenly "wiped internal storage" but got the alert of "no OS during reboot", so I restored from my backup from SD.
the phone started properly but went off during initial setup and will go back off each time I tried turning it back on. I thought it was battery so I plugged it to power.
it did boot but will go back off once I have few touches on the screen.
I had to leave it plugged to setup my accounts else it will go off.
I'm using its Wi-Fi to send this message via my PC because any 2 - 3 touches will switch the phone off.
once it does that, it won’t even boot to bootloader before it goes off again unless plugged to power.
what I do to solve this please??