[Q] screen issue - faulty screen or GPU? - HTC One S

I rooted this phone and installed LeeDrOiD One Supreme which worked absolutely flawlessly for some time. Then the phone was left lying in a drawer for a couple of months. When I turned it on again a few days ago, the display showed a moiree pattern, see attached file. Starting into the bootloader via hotkeys, the display is blank (ie black, nothing showing). When I turn it off by long-pressing the power key, it remains off for approx. 5 seconds, then turns itself on again. No way of keeping it off (until of course it runs out of battery).
However it seemed to start into the bootloader OK, so I used Hasoon2000's brilliant All-In-One Tool to relock my bootloader and re-flashed stock ROM with the appropriate RUU exe. This was successful (I think, because I can now hear the HTC chime on boot) but did not change the problem, moiree still there and still turning itself on after being forced off.
I will add that I have never opened the phone, nor dropped it, or anything like that.
Does anyone have any ideas? A faulty LCD, I could/would replace. Otherwise probably sell it for spares?

i would guess fault on pcb (gpu/cable)not lcd

Related

[Q] HTC Sensation Unresponsive

Hi guys,
I have had my Sensation rooted with ARHD for about 4-5 weeks and everything has been smooth till now, when yesterday I was just reading an text message and my phone's screen went black but still lit up. I replaced the battery, SIM, SD and tried rebooting but it would still just appear as a black screen with the backlight on, but the keys are not lit up. Occasionally, the HTC splash screen would appear after taking the battery out and restarting, but then would again, go to the black screen. I can't go into Boot Loader either (i think i had my phone set to fast-boot cause I need to frequently switch my phone off).
Anyone have any ideas as to what I should do?
Cheers in advance
Try the taking out the SD card and then booting with the power/vol dn combo to see if you can get to the bootloader. If successful, may have to reload your firmware (P58IMG) and possibly ROM.
Just fyi fastboot has absolutely nothing to do with how fast your phone turns on lol.
Kevc44485 said:
Just fyi fastboot has absolutely nothing to do with how fast your phone turns on lol.
Click to expand...
Click to collapse
Enable fastboot in settings, power off your phone and then power it back up again (without taking out the battery).
Your phone will boot in a jiffy. This more of a Sleep-Wake than a Power Off & power On, but yes, enabling the fastboot option will boot up the phone faster.
nabbyboii said:
Hi guys,
I have had my Sensation rooted with ARHD for about 4-5 weeks and everything has been smooth till now, when yesterday I was just reading an text message and my phone's screen went black but still lit up. I replaced the battery, SIM, SD and tried rebooting but it would still just appear as a black screen with the backlight on, but the keys are not lit up. Occasionally, the HTC splash screen would appear after taking the battery out and restarting, but then would again, go to the black screen. I can't go into Boot Loader either (i think i had my phone set to fast-boot cause I need to frequently switch my phone off).
Anyone have any ideas as to what I should do?
Cheers in advance
Click to expand...
Click to collapse
There were threads a few weeks ago simiar to this with Sensations randomly dying.
What version of ARHD were you running, kernel, and firmware?
gustav30 said:
What version of ARHD were you running, kernel, and firmware?
Click to expand...
Click to collapse
I'm running ARHD 6.5.5 with 3.32.401.5 (can't remember anything after 5) and selected the Sebastian kernel when I installed the ROM ...
Kevc44485 said:
Just fyi fastboot has absolutely nothing to do with how fast your phone turns on lol.
Click to expand...
Click to collapse
He means the feature that just suspends your phone instead of powering off. Ironically, both methods don't fully turn the phone off. Coincidentally, it's also called Fast Boot. You're thinking of that set of bootloader tools.
As per OPs issue, I have no idea. It sounds hardware related, but intermittent. Perhaps crack it open and see if there are any loose ribbon connectors or anything? I'm thinking the ribbon responsible for the screen may be loose. If it's loose but still kind of in place, the pins responsible for power might still be in contact but the ones responsible for sending data to the LCD might not. That could be why it turns on but it's only solid black. Pulling the battery and putting it back in might just coincidentally be "helping" because the angle of the phone is affecting a loose ribbon. Mind you, this is all speculation, and it might not be hardware at all, but that's my best guess.
Also, if you can get it resolved, never use HTC's Fast Boot. It's convenient, but tends to be a major pain when you have legitimate issues.
I have been having similar issues. My phone will be fine and all of a sudden it will turn off. Receiving calls, changing tracks from the lockscreen or playing games. Sometimes just unlocking my phone to use it will cause it to crash. Then getting it to boot again can be a royal pain in the behind. Anywhere from the first bootsplash to first unlock / loading the UI can make it crash and it's usually a pull of the battery SIM and SD to get it to boot.
Age of the ROM is something I have noticed to be a factor, the older the ROM, the more likely it is to do this but wiping cache and Dalvik from 4EXT has no real effect on stopping it from happening for any noticeable length of time.
Also to note, battery life seems to be very jumpy when this happens. I have had 4% battery life for hours, listened to music (at volume) and it's remained at 4%. Hardware LED isn't lit and it's just the OS with it's UI warning me so every so often, with the battery indicator staying at the 4%. It'll change again if the phone crashes again. Either to an accurate reading or to another fixed percentage, but it seems to like the 4%.
Not sure if it's the ROM, or firmware, but my previous ROM's have been using Bricked Kernel. I don't know it that's a deciding factor or not.
Sorry for hijacking the thread, but I too have stability issues and been wanting to say something on here for a while.
I'll post version details later on as I'm just about to get ready for a road trip.
Mark
kgs1992 said:
Enable fastboot in settings, power off your phone and then power it back up again (without taking out the battery).
Your phone will boot in a jiffy. This more of a Sleep-Wake than a Power Off & power On, but yes, enabling the fastboot option will boot up the phone faster.
Click to expand...
Click to collapse
fastboot has nothing to do with how fast your phone boots up. take your battery out and put it back in then start it and see if it starts up fast. you're thinking of quick start from basically hibernate
http://android-dls.com/wiki/index.php?title=Fastboot

Phone Freeze > White Screen > Vibrate + Black Screen

My HTC was working fine yesterday until it froze at one point and it wouldn't respond to any buttons including the lock button (which has never happened before except occasionally during incoming calls). I did a battery pull and at first it would only vibrate and remain a black screen, though I could see that it did light dimly when I pressed the power button. After about 20 battery pull attempts it went back to showing the splash and screen and the phone turned on succesfully. After about 10 minutes it froze again, I did a battery pull and now it only showed the splash screen and froze, occasionally showing a red light in the top left corner. My phone was already on low battery so this process went on for another 25 minutes or so (vibrate + screen, freezing on splash screen, or booting then freezing) until I gave up. I came home and charged it overnight while it was off, and it was fully charged this morning, but now it won't turn on at all, it only vibrates once with the screen lighting very dim for a moment then just has a black screen.
I've been searching for a solution for the last 3 hours, seems it could be a range of things but nothing I've tried has worked. I'd appreciate the help, I already spent £90 on getting the screen repaired a couple weeks ago, I don't really want to spend more especially if for some reason HTC decide it can't be repaired under warranty.
Are you s-off and running a custom Rom? It so can you provide details on Rom, kernel and firmware?
There were threads a few weeks back about sensations randomly dying.
Thanks
s-off?
No I'm not running custom ROM.
Came acrosss a few other threads with similar threads but my problem seems to be a combination of everyone else's problems, so I'm a bit lost
are you under warentee? Your stock so there should be no reason at all for HTC to deny your warentee. I'm curious, have you tried to put a different battery in? To see if possibly your battery has gone bad? Worth a try? Even though it says full charge maybe its gone bad? Wouldn't hurt to try. If not and new battery won't work I'd definitely look into warentee repair. You have not altered your device so they definitely should honnor repair.
Sent from my HTC Sensation Z710e using xda premium

[Q] Bricked phone (in a weird way)

So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
stealth.kid said:
So it seems my phone has become a shiny paperweight. The thing is, I don't really understand why it happened. I've been reading how other people arrived at the same situation and although some symptoms are similar, I didn't do any of those things. I wasn't flashing anything, I didn't drop the phone etc
This is what happened: about 24 hours ago, I was using my phone as a GPS (google maps and waze) when it froze. No biggie, it had happened a few times before so I pulled out the battery, waited a few minutes, put the battery back and pressed the power button. The phone started as usual, it got past the HTC splash screen, the boot animation started. A few seconds (maybe 5) into the boot animation, out of reflex, I pressed the power button to turn off the screen. Don't ask why, dunno. As I've said, reflex. So the screen went black. And it stayed that way.
Since then I've been trying to bring it back to life. No luck yet. Here's the status of the phone:
Battery is not empty - when my phone froze yesterday it was about 80% full. I tried a different battery, no change
When I plug in the USB cable to charge it, the orange/green LED that usually lights up, well... doesn't
When I press the power button, the screen backlight turns on for 2 - 3 seconds, then turns off. Pressing VolDown+PWR does the same thing. I know it seems like a battery issue, but I'm pretty sure it isn't
The computer does not see the phone anymore when connected through an USB cable. 'adb devices' doesn't return anything and I don't see anything in the Device Manager (I was hoping for a QHSUSB_DLOAD but no such luck...)
The phone is a HTC Sensation 4G, HBOOT 1.17 (I think), S-OFF, rooted, was running InsertCoin 3.4.6/Android 2.3.5. As I've mentioned, I wasn't doing any of the things that usually lead to a bricked phone like trying to S-OFF/S-ON, flash a ROM etc. I'm currently reading the internets in an attempt to figure out what went wrong and how to fix it. These are the questions I'm trying to get an answer for:
When the phone boots, is it not in read only mode? At least when it gets to the boot animation part.... And if so, even if the power button is pressed... shouldn't the phone just turn off and that's it?
Since the phone seems to be as responsive as a... well, brick... If I send the phone to HTC to repair it, will they be able to tell it was S-OFF and all that?
Does this sound like something that JTAG could fix?
Thanks in advance for any help or info.
Click to expand...
Click to collapse
It reminds me Desire S problem - fried emmc chip... If your phone has no valid warranty, I'm suggesting to see phone's internals and inspect emmc chip.
The phone still has warranty, I will try to have it repaired/replaced. The only thing I'm concerned about is the fact that it was S-OFF and running a custom ROM... And I don't have the knowledge or equipment to try to take it apart and fix it myself
If you have warranty just use it they won't be able to ckeck if phone was unlocked or not since it can't boot up.

Nexus S [CM11] - hardbricked, no vigration, no computer detection!

My phone: Nexus S, 16Gb, Rom CM11, Android 4.4.4 (List of updates: https://download.cyanogenmod.org/?device=crespo)
My story
Yesterday, (about 9.00pm 13/12/2015) my phone got some laggy, so I powered him off. I left it there, 15 minutes later I came back, and I forgot that he had been powered off, so I thought it was just sleeping. I picked him up and press PowerButton. Nothing happended!
Then I got a look at CM rom, found that interesting is my Rom just got a new update at 2.00pm 13/12/2015. I think that my phone has auto-updated!!
In the past, sometime he behaved the same: PowerButton not respond. So, after that 1st press, about 5 sec later, I started to press the PowerButton repeatedly and rapidly, hopefully the phone would wake up.
But no, the reality was that he was being off. There were about 6-7 presses, I will describe slowly below (assume between each press is 0.2 sec):
1st and 2nd press: nothing happened
3rd press: the phone vibrated, and Google logo appeared
4th press: (I had no mean to continue pressing, but it was too fast, I couldn't stop) suddenly, the Google logo disappeared (so the logo stayed on screen just for about 0.2 sec; while normally, it should stay there for atleast 5 sec)
5th and 6th press: nothing happened!
And from then on, no more, anything happened.
What I tried
Hold PowerButton for even 1 minute: nothing happen!
Hold PowerButton + VolumeUP for even 1 minute: none!
Hold PowerButton + VolumeUPandDOWN for even 1 minute: none too!
Connect to charger (wall or pc): no Battery Animation show up! BUT the phone and Battery get warming up!
Take out the Battery for even 15 minutes, then put it back, and PowerButton: nothing!
And the phone not get recognized by PC too.
Sumary
No display
No vigration
No recognized by PC (because of this, I can not follow this method: http://forum.xda-developers.com/oneplus-one/general/guide-unbrick-oneplus-one-t3013732
More Information
In the past, the VolumeDOWN sometimes seems get stucked, cause the phone silent and auto boot to safemode, after many try to press and reboot, the phone may get out of safemode (because VolumeDOWN back to normal)
PowerButton sometimes not respond.
My Battery is not good, sometimes it drops too much! Eg: having 50%, after reboot, dropped to 3%, and start to increase slowly, max around 30% and become normally.
Hope you guys have some ideas! I still can't do anything, when the phone is not regconized by PC!!
Thanks for reading!
Thank you!
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
demkantor said:
Hey,
2 things come to mind and I bet are both the problems. First off you need a new battery and you seem to know this, very cheap now a days but still buy a good one as cheap knock offs are abundant and don't support the power they say, try mugen, anker or stock oem
Also you need to replace power button, this phone was always notorious with bad ones, a new one is cheap but many often found just a loose connection so if you open up the phone, check the ribbon connections and then throw in that new battery all should be well, hopefully
Best of luck!
Click to expand...
Click to collapse
Thank you. I'll try your suggest ASAP.
But I'm wondering, that do you think that CM Update maybe also a reason?
I kind of doubt it as that should only effect the software, if you were getting a bootloop or anything to that extant yeah, but being it won't power on at all I doubt it
thank you
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See: https://wiki.cyanogenmod.org/w/EMMC_Bugs
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
FalconFour said:
Nope, I've seen these symptoms before - exactly the same thing. Dude, I think your phone is Superbricked.
I've got a stack of 3 Nexus S 4G's that have exactly the same problem - the eMMC card is trashed by a buggy "secure erase" implementation. See:
My "working" one was working great, even set it up to sell on eBay, when I went to wipe its data with a factory-reset from the settings menus. When it shut down to reboot, I pulled the battery. That's what bricked it - because the eMMC was halfway through a background erase/rewrite procedure, it wiped out the boot loader somehow and completely bricked the phone. It now does precisely, exactly the same thing you describe - absolutely nothing, except when it's plugged in, it warms up after a while.
Best I can tell, the only way out from here is to use a JTAG device[/URL] to reflash the chip, but even then, the eMMC itself might be "unbootable" (i.e. can't start up, can't be read or written, can't be reformatted/restored).
I just called it "end of life" for those phones and now they're just a sour reminder on my shelf
Click to expand...
Click to collapse
thank you!!
my heart just stop breathing :'( :'(
God, I wish there were a solution to it. I'd really like to donate a phone to anyone that thinks they have the tools or skills to make a "how I did it" explanation - involving whatever tools/software are necessary - to bring these phones back and help us all. I bought 2 of those 3 phones as "for parts" on eBay, and it turned out that both of those phones appeared to have exactly this same issue (though one also had a cracked glass). I even verified the issue by swapping in my good phone's eMMC (at least on the NS4G, it's a swappable card module), and the boards booted up. I only needed the one for the good screen (as I had a good board but completely destroyed display panel) - and that's how I got my one working again.
Then, in the end, I accidentally stumbled upon the method by which the previous two phones were bricked - and now there are three. It seems like a fairly common problem. :/

Poco X3 NFC - Can't access bootloader, fastboot or system (bootloop)

Hi. My close friend has this issue. I'm posting this because she can't figure it out by herself. A month ago, her phone downloaded an update and she installed it. Since then, the phone has restarted by itself without any reason, just random restarts and the frequency of restarts was more frequent with each day. Fast forward to this day and the phone is constantly turning up and shows the POCO logo and restarts by itself. This loop is not ending until the battery is completely dead. When trying to access fastboot or recovery mode, she can get there but only for few seconds (until the device restarts again) which is not enough time to make any changes / factory reset. She did not accessed developer tools in system, so the bootloader is still locked. Holding down power button does nothing. ONE SINGLE UPDATE screwed up whole phone. Can't do ****. There's no SD card or SIM card in the slot. Is there any "hack" to stop the phone from restarting itself? Note when the battery is completely empty and she plugs the charger, the whole nightmare starts again. I'm lost. Did you guys have any ideas what to do? Or is the repair centre only solution? (She cracked glass of the display, i'm not sure if that voids warranty. [it's not glass COVER, it's the glass which is part of the display])
Is this device unlocked? If not, then RMA.
If it is, my best guess is to get the device into recovery (or fastboot?) and immediately connect to PC.
If it holds, leave it there as it will charge, although at much slower rate.
When charged, use TWRP to try to reboot to system.
If it doesn't work, then factory reset.
Sadly, i can not get to recovery because in about 2 seconds the device will reboot. There's literally no time to make any changes - factory reset. Also the device is not unlocked. I hope RMA accept the phone even though it has cracked screen . Thanks for response anyway
Then RMA it is. If you're in EU they'll have to take it, even with the cracked screen.
But does the reboot happen even when connected to PC? Two seconds is enough to plug it in if you're fast...
Yeah, we tried every possible idea we can think of. Pressing the toggle button from different angles with different intensity to make sure it isn't stuck inside, covering up the proximity sensor (yeah makes no sense but even that we tried, lol). Tried with connected to PC as with classical charging brick. No change. Back in those days where smartphones doesn't have unibody construction and you were able to take down the back cover and remove battery it was way simple. Nowadays it's not possible to stop the phone from booting itself until battery is completely empty. My friend says the problem started about month ago, when the phone annouced that there is an update available so she downloaded it and installed it. Before that, there was no problem with the phone whatsoever. Maybe it's caused by some kind of virus but IDK which apps she was using. She didn't have rooted phone not unlocked bootloader in developer tools. Also i googled that it may be caused by "Airtel Thanks" app which she didn't have installed aswell. I will keep this thread updated as what happend to the phone cause i'm also interested what went wrong and to help future users who will struggle with this problem a solution. Thank you.
CaptainFedora, did you solve the problem? I have the same issue...
Yeah, actually. Sorry for not posting the answer although it was definitely her fault. It was the power button being pressed down (which made continuous bootloop). But the button was somehow pressed deep into the phone's body. So complete dissasembly was needed.
Btw. my friend lives in other country so we discussed this problem over internet. If i could have the phone physically with me i would definitely know what was the problem.
Hi.
Yesterday I had the same problem, the device kept restarting every 10 seconds, it didn't even come to any screen besides the first one with the POCO logo in yellow.
Things I tried that did NOT work:
restart
hard restart
fastboot (it did enter the fastboot mode, but only showing the picture of the 2 robots and after 10 seconds restarting again to the POCO logo image)
plug it to power
plug it to computer
After 3 hours of continuous restarting and trying anything I could find in the internet and I could imagine of (except extracting the battery because it seemed complicated and difficult to revert), I tried randomly something that miraculously worked...don't ask me why.
pressing the power button shortly and quickly around 30 times (it might have worked after 10 or 20, but I just kept doing it a little longer
Afterwards it just started as if nothing had happened...doesn't make any sense, but I just wanted to tell you in case you are in a similar situation and desperate to not lose all the images and videos as I was yesterday.

Categories

Resources