Hi,
I have a HTC One M8 ATT, which I have rooted, S-OFF and unlocked the bootloader. As of now I have the Skydragon GPE ROM on it. I have been using it for a month so far without any issues. Suddenly this morning the display started acting up. It looks like it has opened up in safemode or something. I have attached a pic to describe how it looks like. When it boots up the boot up logo is fine, suddenly half way through it moved into this 'safe mode' view.
PS: I know how to take a screenshot, just that a screenshot looks just fine.
Fixed
I figured it out. I had color inversion mode on. Went to Settings->Accessibility and turned off Color inversion.
Whoops! glad you got it figured out.
Related
My wife recently started having a problem with her Thunderbolt. After leaving it on the charger overnight the phone turns on to the lock screen like normal. Once she unlocks it the screen is just white. There's no text so I didn't think it was recovery mode. If she relocks it the lockscreen still comes up fine, but unlocks back to the white screen. Hitting the home key is the only way to bring it back to the regular screens, no other keys have any affect. Any ideas on what might be causing this? She stock unrooted running the most recent update. Thanks for any help!
[email protected] said:
My wife recently started having a problem with her Thunderbolt. After leaving it on the charger overnight the phone turns on to the lock screen like normal. Once she unlocks it the screen is just white. There's no text so I didn't think it was recovery mode. If she relocks it the lockscreen still comes up fine, but unlocks back to the white screen. Hitting the home key is the only way to bring it back to the regular screens, no other keys have any affect. Any ideas on what might be causing this? She stock unrooted running the most recent update. Thanks for any help!
Click to expand...
Click to collapse
No clue of a cause here, but I'd work on backing stuff up before it really takes a dump if there's anything important on there she wants.
Good idea, didn't think it could be bad enough where that was possible. It's weird, we both got them at the same time, she's had a bunch of little problems and mine has been completely fine. Wondering if she got one from a bad batch.
Alot of the sense style roms (including stock) hesitate on a white screen with the HTC logo after unlock. This happens to me after a reboot usually. If you unlock relock and then wait a little while it should work. Or just use launcher pro...
Sent from my tbolt running ShiftTh3ory AOSP
That's the strange part. I've had that happen with the HTC logo before, but it only happens after long charges. And the screen is completely blank, not even the logo.
Sent from my ADR6400L using XDA App
About a week ago I had just checked an email using the gmail app and put the phone to sleep. I then remembered I needed to do something else on my phone, so I woke it back up. Upon waking, the entire screen was red, I could see the background still, but there was noticeable artifacing at the top of the screen. I unlocked the phone, and it was still the same. I could use the phone as normal, but the entire screen was a translucent red. I put the phone to sleep and woke it back up and everything was back to normal.
I am still in my 30 days of ownership, so I was wondering if anyone thinks this was a one time bug or if there is a deeper problem. At the time I was not rooted and was running 100% stock.
I'd most definately take that phone back and exchange for another.
It _might_ have been a one time issue, or it might have been a symptom of a hardware issue. Why risk it?
Thats not really a common issue... in fact the first that Ive heard of. Could be a one time issue... or a hardware LCD/screen issue. Id take it back.
I hadn't heard of it either. When it happened the phone was only a few days old.
I regularly replace iphone 4 screens and I have come across red tinted screens. At least on them it was a sign of screen problems, not software. Samsung does/did make screens for Apple. I've never heard of an iphone having a red screen then dying. I have heard of them being red and not ever going back to normal colors.
Not worth the risk for me. If it was my phone I'd exchange it.
Sent from my páhhōniē
I had a similar experience, except the screen went green, and wouldn't go away until I rebooted. It was probably due to CF.Lumen though, or at least that's what I thought.
On my Captivate, every once in a long while the screen would boot or unlock with a weird color tint. Seem to recall it having been green, but couldn't swear to it.
Either way, a quick lock/unlock again made it go away. Always figured it was a software bug somewhere in the display driver...
I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
void4ever said:
I'm brand new to HTC devices so I'm unsure if the dialer is sense or if this is a ICS dialer were dealing with. (My old phone was a Droidx, so my exp is with blur and asop 2.3 from liberty).
Either way though i seem to have come across an interesting "bug" or at least unusual behavior.
I've noticed on almost every other call, weather it's incoming or outgoing, the MOMENT you dial/answer the screen goes dark. Now i can press the power button to wake it up again and it will stay on for exactly 5 seconds before going dark again. If i flip on speaker phone the screen will stay on, however the moment i turn off speaker phone it goes dark again.
Whats really annoying is if i go back to the home screen it still goes dark after 5 seconds but now when i wake it up it's at the lock screen. If i try to unlock it the moment i touch the screen it goes dark. No matter where i touch the screen the phone is now perma locked until the call is finished.
Now like i said this happens every other call so far in the 6 times I've tested this, which i thought was really odd. The other times the screen stays on and acts completely normal no matter what i do while a call is active. Fresh reboot makes no difference. I haven't done a factory reset yet as I'm trying avoid that.
What i have done so far is unlocked the bootloader, Flashed recovery, and the root from con247's thread in the dev section. I don't think that has anything to do with it though since i noticed the screen going black during a call before i started messing with bootloaders/recovery/root. I just didn't test it as well before doing those things cuz i didn't think anything of it.
Is anyone else seeing this behavior and does anyone have any suggestions?
Void4ever
Click to expand...
Click to collapse
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
blazingwolf said:
Sounds like the proximity sensor is going wonky. You might try a factory reset and without installing anything else see if you get the same issue. Also, make sure that any programs you have installed are not affecting it for some reason.
Click to expand...
Click to collapse
Just factory reset it, skipped setup completely and started making calls, same issue. You maybe right about the sensor though. The first call acted up like i explained. The second call the screen was staying on like i expected, but once i switched speaker phone off and then back on the screen shut off and started acting like call one again.
I just got this phone 6 hours ago i wonder how hard it will be to convince verizon there's a hardware fault. I guess i'd better unroot it and remove recovery so i can call in the morning.
Void4ever
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
void4ever said:
I just wanted to make sure i understand this before i do it.
To remove the root i need to install the RUU for the phone, which i found at http://themikmik.com/showthread.php?13550-Asian-Shooter-goes-ICS-and-a-VZW-Fireball-RUU (second link i assume).
I haven't downloaded it yet, but it's an exe. Will it flash the phone via USB, or does it just extract something i can use recovery to flash with?
Once i get the root removed i just need to flash back the original recovery and i should be good to go right?
Void4ever
Click to expand...
Click to collapse
There are directions in the RUU that will explain all of the steps. You will connect your phone with the USB cable.
It shouldn't be to hard to convince them. Just show them the steps you did to reproduce the issue. Good luck.
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
void4ever said:
On the phone right now and the guy is setting up overnight sat delivery to my house. We are a fairly large business account so i'm glad they are going that extra mile.
Just to note I've noticed the sensor doesn't shut off after a call is complete. In fact it stayed on last night for around 6 hours before finally turning off. I did another test this morning and once again the sensor is stuck on, so good call. Thanks so much for your help, i never would have thought sensor, it seemed like a software issue to me!
Void4ever
Click to expand...
Click to collapse
No problem. Glad you got a new one coming.
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Good to hear man. Enjoy that puppy.
void4ever said:
replacement came today and it works like a dream now, got custom recovery and root going! It was def a bad prox sensor on the other one. Thanks again for your help wolf!
Void4ever
Click to expand...
Click to collapse
Awesome.
Sent from my ADR6410LVW using Tapatalk 2
Hello.
When I leave my phone in sleep mode (screen locked and light off) and try to wake with On/Off button, sometimes I get a black screen with a faintly image. The touchscreen works and all the buttons, and if you click 2 times On/Off button - the image appears all ok. I tried to flash another stock ROM - all the same. Then I`ve unlocked the bootloader, rooted the phone and even did the S-off with wire trick (1.53 Hboot). Then I`ve tried 3-4 custom ROMs with 6-7 different kernels, from stock to custom, but all the same. Yes, I`ve updated the firmware file, also, but with no difference.
Well, I see that this problem is not so usual, but I couldn`t find any real solution. Did anyone have this kind of problem and solved it? Since I got this phone from another country - official warranty is out of the question, I need a DIY solution.
Any help is greatly appreciated.
THX in advance!!!
I would have to say it looks like the light for your screen is dying, I had my screen replaced once, my screen would flicker from very dark to very bright
Sent from my HTC EVO 3D X515m using xda premium
flashallthetime said:
I would have to say it looks like the light for your screen is dying, I had my screen replaced once, my screen would flicker from very dark to very bright
Sent from my HTC EVO 3D X515m using xda premium
Click to expand...
Click to collapse
hmmmm, but when I get the OK image - it doesn`t flicker or go from dark to bright, it only has trouble to "wake up from sleep mode". even when i relock the screen quickly and don`t leave it unused for 2-3 minutes, the screen works OK every time....it looks like a software problem, but still I didn`t manage to fix it with all the ROMs/kernels/firmwares I`ve flashed....
E-ducation said:
Hello.
When I leave my phone in sleep mode (screen locked and light off) and try to wake with On/Off button, sometimes I get a black screen with a faintly image. The touchscreen works and all the buttons, and if you click 2 times On/Off button - the image appears all ok. I tried to flash another stock ROM - all the same. Then I`ve unlocked the bootloader, rooted the phone and even did the S-off with wire trick (1.53 Hboot). Then I`ve tried 3-4 custom ROMs with 6-7 different kernels, from stock to custom, but all the same. Yes, I`ve updated the firmware file, also, but with no difference.
Well, I see that this problem is not so usual, but I couldn`t find any real solution. Did anyone have this kind of problem and solved it? Since I got this phone from another country - official warranty is out of the question, I need a DIY solution.
Any help is greatly appreciated.
THX in advance!!!
Click to expand...
Click to collapse
Thinking about how to troubleshoot if hardware or software. When in sleep mode, instead of using the power button, I would have the phone plugged into a computer and use the " adb reboot " command to reboot the phone without touching the phone a few times and see if it lights up correctly. The first thing you should see is the boot screen, and if it works every time, then you do have an issue with your firmware. If you don't see that boot screen first every time, then as much as it sucks, I would guess there is a hardware issue.
Good luck, but this is the easiest way I know of to help determine what the issue likely is.
Minor update here, the first thing (at least on mine) that I see is the lock screen for just a quick second or two, then it quickly goes into the boot sequence. This is important as in "sleep" the ROM is running, so if the first thing you see is the boot sequence every time, and not the lock screen, then it points more to a software problem than a hardware issue. CM9 had an issue for the epic4g where you had to turn it off and on sometimes to get the keyboard to light. They found the issue in the firmware causing it.
Just wanted to make this as accurate as possible.
Wow so I am not the only person with this problem. The EVO 3D that I have was replacement phone that was given to me from Sprint from the first EVO 3D that I had which had issues with the digitizer. I received the replacement phone this past Tuesday and it worked fine for two days. It was not rooted and I did install the ICS update. On Friday morning I took it off the charger and went to work, while in the break room the screen suddenly went black and I could not get the phone to display anything after that. The Android function buttons at the bottom will light up but the screen wont, the phone also gets hot even with it powered off.
Long story short, I took it back to the Sprint store where they ordered me yet another replacement EVO 3D. Has anyone had to go through 3 EVO 3Ds or more?
sonza said:
Thinking about how to troubleshoot if hardware or software. When in sleep mode, instead of using the power button, I would have the phone plugged into a computer and use the " adb reboot " command to reboot the phone without touching the phone a few times and see if it lights up correctly. The first thing you should see is the boot screen, and if it works every time, then you do have an issue with your firmware. If you don't see that boot screen first every time, then as much as it sucks, I would guess there is a hardware issue.
Good luck, but this is the easiest way I know of to help determine what the issue likely is.
Minor update here, the first thing (at least on mine) that I see is the lock screen for just a quick second or two, then it quickly goes into the boot sequence. This is important as in "sleep" the ROM is running, so if the first thing you see is the boot sequence every time, and not the lock screen, then it points more to a software problem than a hardware issue. CM9 had an issue for the epic4g where you had to turn it off and on sometimes to get the keyboard to light. They found the issue in the firmware causing it.
Just wanted to make this as accurate as possible.
Click to expand...
Click to collapse
Excellent thinking, I didn't think in that direction. I'll try this tomorow, since I'm not at home. My personal oppinion that it's a software problem but if I did all the above - what did I miss? If I flashed the firmware, ROM and kernel, what else is left untouched that could affect the LCD? Could anyone suggest a good kernel? Or can I downgrade the firmware, since no one had such a problem with GB?
just to inform all - I tried all soft solutions, but all the samo. finaly - I replaced the LCD and everything is OK.
THX all for help
I clicked on a link in Dolphin which opened the YouTube app. The video started loading and went full screen. Suddenly the whe screen turned different shades of Grey stripes. Then slowly the stripes started changing color to a darker Grey starting from the middle of the screen and almost morphing to edges of the screen. It looked really cool but also scary. Then the phone crashed and rebooted. I thought that this would be the end and I saw myself having to but another phone. I have never seen anything like it.
Alas, everything was fine.
I'm running Ineffabilis Deus with the Cubed kernel.
The Other Side was trying to communicate with you through your phone
The cubed kennel never works for me on any Rom except viper. I'll lose damn near 50% battery in 8hrs just sitting in my pocket. Not to mention all the other funky sh*t that happens
Sent from my Rezound using Tapatalk 2
I had a similar crash with my original rezound, except I didn't get gray a gray screen... it turned blue like a BSOD on windows except with no text. This happened like 4 or 5 times with in a month last February, and finally after one such crash the screen never turned back on again. Verizon sent me a new Rezound and haven't had a problem like that since.