Hey All,
I'm really here to give a report about my HTC One (M8). I have had this phone about 24 days and it has ran perfectly until a couple of days ago. Before I go into the issue my phone is rooted and flashed with Venom Rom 1.5.0 and whatever updates associated with 1.5.0. (quick shout out to the Venom Team: Great job Venom Team). But a couple of days ago while I was using my phone my screen went completely dark, one could tell the backlight was illuminated but the screen did not render anything. The phone is fully functional; volume controls, power off/on, notifications and incoming calls, anything that you could control without needing a screen worked. I tried to hard boot but no luck, adb reboot bootloader command did not bring the screen back and adb devices rendered in my terminal window. Long story short, I called T-Mobile and I have a replacement phone on the way and it should be here by tomorrow. (I can't wait to get that Venom Rom on it) Has anyone heard of the M8 screen just going out of commission? I searched some on the web and I found a couple of other occurrences. Thanks.
I had a similar experience with mine. One night the screen just randomly started flashing and strobing, it stayed that way for a couple days then it went completely black except for the status bar. I had gone to the T-Mobile store and showed them and they ordered a replacement, when I got home suddenly the screen started working perfectly again. Now I'm paranoid to send it in because it says tampered and relocked but has no visible issue anymore, I would hate to keep it and have that problem happen again, but would also hate to be charged or denied the replacement because I rooted and put a custom recovery on.
Related
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.
I was running MightyRom for almost a year, no problems. Suddenly about a month ago my screen alignment was occasionally wacked, by a 1/4 inch or so.
But the alignment screen function no longer worked, I had to restart the phone to exit the application.
Yesterday I flashed back to the stock Sprint ROM and removed the SIM card, I'm giving the phone to my kid so I wanted to reset it to factory specs.
So the 'startup for the first time' sequence begins and the align screen application simply will not 'align'. The crosshairs just prompt me to keep pressing for alignment but I cannot get past this to get to the Home screen.
I hard reset the phone several times from the bootloader screen, even tried to re-flash the Sprint ROM again, but no avail.
Any suggestions? I've been all over google looking for solutions.
I should also mention that it's a brick since I can't make calls/text, etc.. I'm stuck on the 'align' screen.
I took it to the Sprint store, they confirm that it must be a hardware issue.
Rep ordered me a new one, says it will be in by Monday or Tuesday, just have to activate an old phone for the weekend.
0 deductible!!
I'm glad that I got that Sprint ROM back on it just in time.
Greetings to all members.
A couple of days ago i received a new G2.
As soon as i rooted it i installed http://forum.xda-developers.com/showthread.php?t=1605016
Everything completed and the phone would operate normally. I let it fully charge during the night. Next morning i installed some apps from the market (skype fb and a weather widget), then i let it charge again for 20 minutes or so. When i got back to see if it charge, the screen was dimmed like in power saving mode, it wouldn't go back no matter what and the phone hanged there.
I got the battery out and upon rebooting the screen was still dimmed.
I got back to 2.3.3 stock which i had backed up to SD from clockwork, but the problem continued.
I contacted the seller and said they would ship a new one as soon as i sent them the shipping back notice. The thing is i don't want to wait half a month or even more to get the new phone.
I've attached a video of the problem.
I played with the brightness levels on 4.2, you will notice that if i put it on 100% the screen goes completely black.
Also when i put it in standby with the power button and push it again the screen starts flickering for some seconds before it gets stabilized again.
Thanks in advance for your time.
Johnny91i said:
Greetings to all members.
A couple of days ago i received a new G2.
As soon as i rooted it i installed http://forum.xda-developers.com/showthread.php?t=1605016
Everything completed and the phone would operate normally. I let it fully charge during the night. Next morning i installed some apps from the market (skype fb and a weather widget), then i let it charge again for 20 minutes or so. When i got back to see if it charge, the screen was dimmed like in power saving mode, it wouldn't go back no matter what and the phone hanged there.
I got the battery out and upon rebooting the screen was still dimmed.
I got back to 2.3.3 stock which i had backed up to SD from clockwork, but the problem continued.
I contacted the seller and said they would ship a new one as soon as i sent them the shipping back notice. The thing is i don't want to wait half a month or even more to get the new phone.
I've attached a video of the problem.
I played with the brightness levels on 4.2, you will notice that if i put it on 100% the screen goes completely black.
Also when i put it in standby with the power button and push it again the screen starts flickering for some seconds before it gets stabilized again.
Thanks in advance for your time.
Click to expand...
Click to collapse
Are you using automatic backlight?
Johnny91i said:
Greetings to all members.
A couple of days ago i received a new G2.
As soon as i rooted it i installed http://forum.xda-developers.com/showthread.php?t=1605016
Everything completed and the phone would operate normally. I let it fully charge during the night. Next morning i installed some apps from the market (skype fb and a weather widget), then i let it charge again for 20 minutes or so. When i got back to see if it charge, the screen was dimmed like in power saving mode, it wouldn't go back no matter what and the phone hanged there.
I got the battery out and upon rebooting the screen was still dimmed.
I got back to 2.3.3 stock which i had backed up to SD from clockwork, but the problem continued.
I contacted the seller and said they would ship a new one as soon as i sent them the shipping back notice. The thing is i don't want to wait half a month or even more to get the new phone.
I've attached a video of the problem.
I played with the brightness levels on 4.2, you will notice that if i put it on 100% the screen goes completely black.
Also when i put it in standby with the power button and push it again the screen starts flickering for some seconds before it gets stabilized again.
Thanks in advance for your time.
Click to expand...
Click to collapse
Sounds to me like it is really a hardware issue... while it's understandable that you don't want to wait for a new phone to arrive, it is better than ending up with a dead backlight...
It really was a hardware issue, took another one back after a month and it works great.
Thanks for your help guys
Hi,
My HTC One X is about 12 months old and in very good condition. I have never had a problem with it until around 1 month ago when it started randomly giving me a black screen.
When the phone goes into a sleep mode and I pressed the power button to display the screen nothing happened. Sometimes the lights at the bottom would show but nothing on screen and if I pressed the volume buttons on the side I could hear it fine.
I tried reformatting the phone but that never worked so I sent it to HTC for repair. They sent it back saying they had replaced the screen etc but after a few days the problem has returned. I have sent it back to them again and have been told they are sending it back with "no failure, no repair" as they never seen a problem.
I know I am going to get the phone back with the same issue so I was wondering if anyone else knew how to fix this problem?
I don't think it will be connected but it seemed to have started from when I done the latest htc update (not the 7th March 2013 one).
Thanks and all help is appreciated.
Hi,
I installed the cyanogenmod 11 nightly like a week ago on my galaxy note 2 and all was running perfectly until this morning.
When I woke up this morning the phone screen was black. The phone is actually working, I can hear emails notifications, phone ringing etc.
The buttons light up when i press them. When I connect it to the PC I can browse the phone contents etc. All seems to function except the screen.
The battery is charged. I tried to remove the battery for a long time and try again but still nothing.
I can't get into recovery or download mode as the screen is blank (sometimes there is a like a weird area at the top where there are like different colored pixels present). I know people will say the screen might be damaged but last night before I went to bed it was all fine, the phone was placed on the table, and this morning when I picked it up screen is blank.
I want to flash back the stock firmware. However I can't get into download mode in order to use Odin. Is there any other way to get into download mode or hardware reset the phone?
Any suggestions are welcomed.
EDIT: The touch screen also seems to work when I touch it as I can for example call numbers for which I had speeddial scortcuts but it is still completely blank.
I think this is hardware issue. You must replace the screen
verny94 said:
I think this is hardware issue. You must replace the screen
Click to expand...
Click to collapse
Yeah I think so too. I've sent it to Samsung.
It was rooted and had cyanogenmode so probably I have no warranty
However I managed to install stock ROM so hopefully they won't (can't) notice.