Database Users

Blank screen crisis

During synchronisation, I found that the screen in my HD had gone blank. It could still receive calls. A soft reset didn't solve it. I rang HTC support, and all they could say was to send it in for repairs.
I then used mDesktop to look at the screen from my PC. It seemed there were some programs still to be installed. After installing these, I did a Sprite backup. This must have fixed the registry as the machine came to life during the reset.
I'm just leaving this in case someone else has this problem.
There's a way out.

I wrote too soon. Blank again. I suspect an intermittent hardware problem.

Try turning off device and removing battery overnight. Then re-insert battery and turn on device.

Thanks, I'll give that a try.

Tried this, but didn't seem to make a difference. I'll try a hard reset.

Strangely, after one last kiss of life with nDesktop (a soft reset controlled from the desktop), the HTC seems to be working fine. It's lasted more than 12 hours now. I hope for more.
What does disconnecting the battery overnight do?

Kevin Murray said:
Strangely, after one last kiss of life with nDesktop (a soft reset controlled from the desktop), the HTC seems to be working fine. It's lasted more than 12 hours now. I hope for more.
What does disconnecting the battery overnight do?
Click to expand...
Click to collapse
Other users have experienced similar situations as yourself with screen going blank but functions still working. One fix for this was to remove battery and leave device off overnight. I'm not sure why this worked, possibly letting device cool off, but it has worked for others. This is why I suggested it

Going blind slowly
Well, there seems a pattern. With time, the screen eventually fails to turn on. I then sync with the desktop and use mdesktop to re-boot the device. It works for up to an hour, sometimes more. Then it lapses back into blindness.
It can't be a software fault, as it happens even after a hard reset.
I don't think it's a faulty component, as it wouldn't fix after a sync.
It must be some strange electrical thing going on that responds to the reset process, but then eventually fades.
Perhaps I need some sorcery.

Kevin Murray said:
Well, there seems a pattern. With time, the screen eventually fails to turn on. I then sync with the desktop and use mdesktop to re-boot the device. It works for up to an hour, sometimes more. Then it lapses back into blindness.
It can't be a software fault, as it happens even after a hard reset.
I don't think it's a faulty component, as it wouldn't fix after a sync.
It must be some strange electrical thing going on that responds to the reset process, but then eventually fades.
Perhaps I need some sorcery.
Click to expand...
Click to collapse
If it is indeed hardware why not return it under warranty? Just make sure you have a stock SPL and rom on device before you return it

It's just out of warranty. That's why I was so keen to find a solution first.

Is the warranty 2 years?

Warranty is generally 12 months. Found this similar thread which may help

I assumed it was 12 months, but when I looked at the warranty pdf file from HTC's website it says 2 years.
http://www.htc.com/www/support/warranty.html
Western Europe, Windows Mobile
2. This Limited Warranty shall last for twenty-four (24) months from the
date of original purchase for mobile devices, and twelve (12) months
for accessories (whether included in the mobile device sales package
or sold separately) other than the media on which any software is
provided, CD-ROM, memory card (“Warranty Period”).
Click to expand...
Click to collapse

Something bricked my phone.

My phone, which I've had since waiting in line on March 24th quit on me today. I'm not sure if it was the culprit but, I installed a program called Lookout mobile security last night 5/6. When I started the phone this morning put it on the table, got some java and when I got back nothing..no buttons working...ok..no problem tried a soft reset...nothing..ok now starting to get worried. pluged into power source..boot up screen. whew..low battery. then blank, a few seconds..boot up screen AGAIN!..by now I'm in full freakout...Attempted to calm down.. didn't work..thought ok..most everything is backed up..lets do a hard reset..didn't WANT to but anyway! Did the hard reset .. Still had the same problem...Had to pinch myself HARD to make sure this wasn't a nightmare. Went to the TMobile store and the associate put me in touch with technical support (they were Super) Going to give me a new phone but, have to wait until next Friday to get it...and then tweaking and rebuilding it to what I want...I should have been ready for this coming from an iphone...All it takes is one $%@# program again, not saying it was the one mentioned above but, one with a malicious code or something that destroyed over five weeks of building a phone from scratch. Sorry about the rant... I still LOVE this phone. .

so you couldn't even boot it in to the bootloader? wow! Maybe you should flash HardSPL before trying to install that program again as there is far less chance of bricking it if you have HardSPL installed. Even if the rom gets completely stuffed, you can still boot it and reflash from SD.

All I can recommend is install a ROM via Micro SD card and maybe doing a Task 29 before you reinstall a ROM
for US Tmobile: http://forum.xda-developers.com/showthread.php?t=653614
For Leo: http://forum.xda-developers.com/showthread.php?t=609477
Or maybe try this thread: http://forum.xda-developers.com/showthread.php?t=668347
If those don't work then I don't know what else to recommend

They want my old phone back once I get the new one so, I'm going
to let them have it just as I turned it on yesterday. Let them
find out what the problem was created by.

I was about to install that "lookout" software...but after reading this I might as well hold on.

did you leave it on the charger overnight or did you just turn on your phone in the morning.
if you didnt have it charge all night, maybe all you needed to do was leave it on the charger a little longer before starting it back on.
i noticed that some phones with a dead battery and on the charger will sometimes not stay on until it has gotten a minimum charge on the battery.

Damitu said:
..most everything is backed up..<SNIP>...and then tweaking and rebuilding it to what I want...
Click to expand...
Click to collapse
Setting up the new phone shouldn't be a big deal if you did actually backup; just stick the old microSD in the new phone and run whatever backup app you had on the card.

I put it on the power supply and it is in the constant loop of
the first screen that appears. I am going to seriously look into
HardSPL. Thanks to all the good input from everybody.

Well now even customer service is at a loss. They cannot phantom why why two separate phones have the same problem. While I had CS on the phone we went thru various senario's to try to get the phone to operate properly. I even had them give me a new SIM card and that did not work...I suggested the problem might be the battery as it could have gone bad. You guys think the phone is playing hard to get--try to find a replacement battery! No stores within a 20 mile radius had one in stock....! Needless to say they are going to ship me yet another phone. plus a new battery and hopefully it will take care of the problem. The sales associate did a hard reset on both my old and the new phone without results so that unfortnately is not a viable solution. Now I am in the game I hate the most........The waiting one! ..

c_legaspi said:
did you leave it on the charger overnight or did you just turn on your phone in the morning.
if you didnt have it charge all night, maybe all you needed to do was leave it on the charger a little longer before starting it back on.
i noticed that some phones with a dead battery and on the charger will sometimes not stay on until it has gotten a minimum charge on the battery.
Click to expand...
Click to collapse
^^ what the op says above. This happened to me (and my gf as well) on our HD2s. The first time (mines) this happened, i hooked it up onto my car charger and immediately tried to turn it on.. it would go onto the TMO screen, but quickly shut down and loop. After realizing I may be trying to jump the step, I unhooked it from the charger, took the battery off, put it back on, hooked it back onto the charger and let it sit for about 10-20 minutes charging. Turned it back on and viola! It wasn't a brick.. I can almost guarantee this is your problem.
But I may be wrong lol...

So, now after 2 replacement phone sent to me, I find out that
it was the battery all along. Problem is that after the second phone
arrived and I had the same problem I called customer service and
explained it to them....They said a battery would be sent next day
air...Ok...called the next day and was told that the rep never sent
in the order...Long story short....I've almost been without my phone
for two weeks now and, all I need is a frelling battery.
Problem is there are NONE around me..I've tried every tm store in
the area, All radio shacks batteries plus...you name it....
I am being sent a battery UPS ground...could take 7 more days.
Just took the battery from my fiance's phone and it works
so, right now I would pay a ransom for a battery just to have my
phone back!

I had to do a hard reset after downloading that lookout trial.

at this point I don't know what caused it..Has anyone ever heard
of an application causing the battery to go bad?...I worked really
hard to keep the battery I had in good condition.. I hope UPS
delivers soon!

This is odd I have used Lookout Mobile on my phone since I had it. Mind you not had it for long, since April but still its never bricked or did anything that hindered the phone. I maybe another program.

Screen Issues

Having some random and annoying screen fluctuations. Its like the screen depolarizes and the images become distorted and somewhat inverted. Happens off and on and reboots do not help. Im gonna go back to stock just incase it needs to be sent in and to see if the ROM I am using is completely to blame, I have tried reflashing too.
Just thought I put this out there to see if anyone else is having similar issues.

I may have had something similar the other day - basically the color blue would go away, and the remaining R&G pixels would smear. Best way to describe it would be to pretend that there is a specific frame buffer for blue, and it has a pointer, and that pointer was getting whacked. Meanwhile the pointers for the red and green buffers were having less-significant bits screwed with. Yeah, like I said, "pretend". My initial gut said it was a simple case of some bad silicon on a line driver. Done.
While getting ready to exchange the Tab (aka removing stuff), I discovered the behavior was strongly impacted by memory pressure. If you've played with ESXi, you know what I'm referring to. If not, go read about Ballooning.
With lots of crap floating around, screen gets more wonky more often to the point of being unusable. Including during the boot splash screen. Remove the junk (not programs - just... stuff, music, browser cache, whatever)... less wonky, less often. Still wonky, mind you, but less wonky, and less often.
Decided the culprit was likely Task Manager by Rhythm Software. Removed exactly it, cold started, and never had an issue since. Note that I'm not really keen on saying Rhythm's work was at fault, especially since saying "it's fixed!" is trying to prove a negative and this is not a reported problem. OTOH, the behavior did start within a few days of installing it, and the behavior's ending exactly coincides with RTM's removal.
In that sense, take a close look at what you're installing - something otherwise fine might be suffering an... unexpected feature.
HTH,
- sbb

Thanks for the tip, mines still looking like hardware failure. Sometimes when i put it into the samsung keyboard dock it randomly clears up, as if the jiggle in the pin connector port affects it but it will reappear eventually.
Been trying to use the return to stock stuff from the main sticky in the development section but it keeps erroring and failing in CWM when I attempt to flash. Oh well.
Thanks for the reply yo!
I think its because the stock rom they have is p700 and I am p7510 or whatever. Am I in the wrong place? lol Time to scavenge the forums.

Unroot for Return
So, I made my backup copy of my ROM after it was rooted. How do I get this thing rooted again so I can take her in? I tried using the info on the stickie in the Dev section but I get an error when flashing the supplied stock ROM, repeated, no mistakes I am pretty sure.
Any tips?
also, hasnt been 30days, should I just go back to best buy or call samsung?

I have the exact same issue with my tablet and going to return it for warranty. I had to unroot and get it back to default blind, since the screen is almost never readable here (too much distortions).
I got it back to factory default (unrooted) through ODIN + Download Mode. Use the files and step-by-step guide on this webpage: http://droidangel.blogspot.com/2011/06/samsung-galaxy-tab-101v-p7100-stock-rom.html

I got the same problem. the screen just distorted, which happens on several custom ROM. It happens after heavy use. I have to put it aside for a couple of hours to get it back to normal.
Is that hardware issue? If it is, how could you convince the shop to get it replaced?
you may not be able to reproduce it at the shop.

I lost my interest to samsung product. It took quite some time to create an account and file a case. Now the webpage just keeps telling that it is processing the data.
I remember that I have never succeed to create an account through the TAB.
very bad service.

Well, mine's finally going in for repair.
As mentioned in the post above... after removing a few apps and most of the data from the tab... not a single issue with the screen, since.
Then... the behavior came back last week, gradually becoming worse until the colors are just plain hosed. Blew out the browser caches, wiped any remaining data... pulse, etc... and it cleared back up again... for about an hour, but rapidly reverted back to horrid. Did a hard reset... no avail.
It is quite the interesting behavior, to say the very least.
It's not mechanical. It's not thermal.

Is samsung service center the only solution for this?

Does yours look like this?
www youtube com/watch?v=WauTDdzxGq0
(Sorry, you;ll need to fill in the obvious missing doys. It was either that or posting 8 random posts)

My Tab also has similar issue and it still appears after hard reset, trying to convince the shop to exchange or help me to send back to Samsung.
Did Samsung cost you any charge for repairing? The shop say it need charges and they don't want give any help.

not really. Mine has distorted display but more likes adding white noise.
Seems that sumsung really sucks. products have so many different issues.
pholklore said:
Does yours look like this?
www youtube com/watch?v=WauTDdzxGq0
(Sorry, you;ll need to fill in the obvious missing doys. It was either that or posting 8 random posts)
Click to expand...
Click to collapse

simgamer50 said:
My Tab also has similar issue and it still appears after hard reset, trying to convince the shop to exchange or help me to send back to Samsung.
Did Samsung cost you any charge for repairing? The shop say it need charges and they don't want give any help.
Click to expand...
Click to collapse
I was covered by seller warranty. I sent it back, and the seller sent me a new device. I don't know where you're at, but usually sellers are required to handle this for you, if under warranty, _by law_. This is obviously a manufacturing fault, not bad usage.

Need Help with APX Mode Brick.

Running (was) a stock rooted N7 v1 on 4.3. Bought a data recovery tool off of the play store to try and recover some photos I had deleted. At some point it rebooted into safe mode, my battery was running low and I shut it off to let it charge. Now it's dead in the water. Stuck in APX mode. I am asking if there is anyway to breathe life back into this tablet.
The tablet does nothing on the screen, period, no matter what you do. When plugged in to a computer it sometimes registers as an unknown device, sometimes APX. None of these get you anywhere. Toolkits on these forums won't recognize the device, installing the android development kit and drivers does nothing, executing commands from the command line is worthless because the device won't register. I do not have any "blobs" and have no clue at this point even what they are or what they could have done for me had I made them.
I've searched this forum and found bits and pieces here and there and wanted to start a thread dealing solely with devices stuck like this and what has or hasn't worked and get others input if warranty service was done and the state your tablet was in when you sent it in (locked/unlocked, rooted etc).
Anyone stuck here will have probably tried the same things as I have but here is is a minor rundown...
1) Every button combo press known to man for short, medium, and extended periods of time.
2) Charging with the Original charger/cable for 1 hour, then button presses then charging for 12 hours.
3) Same as above but with different aftermarket chargers at different amperages.
4) Uninstalling and deleting drivers. Trying different drivers. Getting the Android drivers etc.
5) Trying every toolkit on the forums to no avail because the device won't register.
6) Checking to make sure the battery cables are seated correctly.
7) Screaming and yelling at your new paperweight.
My hope here is that I've missed some important thread about recovery and someone can point me in the right direction. Failing that, if I should get a new mobo or try and send it in for warranty service in the state it's in.
Any help would be much appreciated.
Sent from my Rooted Frameworked SCH-I545 using xda app-developers app

I don't know what you tried before to revive your tablet and what the tool did to get you into this state, but generally APX mode can be left by pushing the power button *only* for about 10-20 sec, as long as there us enough power within your battery and the hardware / software is working / consistent.
Sent from my Nexus 7 using xda app-developers app

I don't think I've ever seen anyone in here describe a situation where they observed the tablet in bootloader mode without seeing *something* on the screen.
And as you found out through your reading, using "nvflash" on the N7 is only useful at this time for folks that made prior disaster recovery preparations. So, APX mode is of no use to you (at this date 12/2013).
So, until you see something happen on that screen, drivers on a PC are of no value to you anyway.
It is really unfortunate that the N7 doesn't have a physical charging indicator - that makes it difficult to distinguish between a tablet which is truly borked vs. one that refuses to boot simply because the battery isn't charged.
Holding down a specific button combo (iirc Pwr+VolUp) during an attempt to get "something, anything" to happen will put the tab into APX mode, so it isn't particularly diagnostic that you have observed APX mode once or twice.
Really about the only way to know if the battery in a non-responsive N7 is charged or not is to put it in another tablet or measure the open-circuit voltage. (About 4.15v fully charged & about 3.5v discharged)
The reason that I mention this is that there have been a few reports from users in similar straits as you that report something like "I don't know what happened, but I tried it a few days later and all of a sudden the tablet booted up". Almost every one of those reports involved mentions of low battery conditions, just as your narrative does.
I don't know what file recovery program you used, but I suspect that is a red herring . It might have to have root privileges in order to read raw partitions, and might even want the tablet in safe mode to minimize write activity by *other apps* while it does it's forensics, but it certainly isn't going to recover files by writing in raw mode on a mounted, live filesystem - it would do all it's writing through normal kernel syscalls. That's the long way of saying that a low battery is more likely to be the original source of your troubles.
So what to do now? I think the first order of business is to figure out if your battery is charged or failing to take a charge. If it really is well charged, then a warranty return is probably in your future.
If you can't find a second N7 or a voltmeter, then you could try just leaving it on the charger for a couple of days... but that really is just a "grope about in the dark, wing & prayer" kind of strategy.
good luck
Button sequences & USB Identifiers (VID/PID pairs):
http://forum.xda-developers.com/showthread.php?t=2133986

You are in the same situation I was in - nothing shows up on screen. I got APX drivers to finally install (had to search all over the internet to find them) and that STILL didn't help. I was never able to get it to come back. Nothing ever showed up on the screen.
No combination of button presses helped. I finally gave up and, since my N7 was still under warranty, I RMA'd it back to ASUS. It took about 3 weeks, but I got it back with a new motherboard installed on it.
It was borked and your's sounds the same way as mine. Just either register your N7 on the ASUS website and RMA it that way, or call it in over the phone and RMA it that way. Hopefully, you still have the box your N7 came in because you'll need the serial number.
Others have stated you can get it by opening the back, but that will void your warranty. I do believe you MUST have the serial number, so find the box and get it from there.
Also, you'll definitely lose everything that was there, especially if they replace the motherboard. So hopefully, you backed it up. I backed mine up just before it got borked, so I was lucky.
Good luck!

I am wary of trying to do the battery swap. I went and bought a new version after it crashed but I would be voiding both warranties to try the battery swap.
I do have the serial number if I want to try and get service.
I have done some reading about "deep discharge" battery issues and I suspect this may be a part if it but I have tried leaving it plugged in for days and nada.
I don't know if there is a way to "shock" or jump start the charging process and I am going to put the multimeter on it tomorrow and see what I get.
Thanks for everyone's input. I will keep you up to date.
Sent from my Rooted Frameworked Verizon Galaxy S4 on MJ7 using the XDA App.

LG randomly overheating and won't stay on - No previous heat issues

Hi, I have a LG K20 Plus. I currently can't turn the phone on, so I don't have much software information to give you. The phone was bought at T-Mobile (Metro by T-Mobile) and I had a SafeLink sim card and a 16 gb micro sd card inserted when the issue started. I have since removed both. It says Qualcomm snapdragon on the screen when it starts. It was also rooted and the bootloader is unlocked.
I broke the screen on my phone and I decided to do the repair myself. I have done about 7 or 8 screen replacements and I actually did this phone a year ago with no issues, so I felt I could manage this one as well. I bought an entire display (from ebay) and switched it out with no problems. Initially it worked great! I used it for a few days before realizing that I had no sound. I opened it back up and noticed the loud speaker had fallen out. I found it, put it back in, reassembled it as I normally do and turned it on.
NOTE: when I was reassembling it the second time, I actually tried to put a screw in a hole that wasn't a screw hole. I used a light to normal amount of pressure but I didn't force it. I think it's the hole where the moisture detector is. Picture #1
I turned it on and right after the logo screen I got a message that said "High temperature detected Powering off for your safety" and it immediately shut off. The phone does appear to charge normally but it won't stay on. I did a factory reset (I'm not sure if it's still rooted but the bootloader is still unlocked). I also switched back to the old (broken) display just to check if that would work. I couldn't see any difference in the shielding but I switched them just to be sure. I bought a new battery and installed it. I took a q-tip and 95% Isopropyl Alcohol and cleaned pretty much the entire motherboard, paying special attention to the battery connections. After each one of these things, I tried to start it with the same error message immediately upon start up.
NOTE: At no point has the phone every physically felt hot or even warm. I don't think it's on long enough for it to get hot. But something is wrong and I have no idea what it is. I, literally, took the phone apart, put in the speaker and put it back together in less than 5 minutes. Could it be I just bumped something and knocked it loose?
I searched for any information I could find both here and with google but there is next to no information on the LG K20 Plus. I did find some information on the LG V20 that had overheating issues, and that has been all the luck I've had. I watched several videos and it seems the solution is to apply thermal paste. But my phone doesn't have any evidence that thermal paste was ever on it. I went and bought some but I have no idea where exactly to put it or even if it's needed. Most videos showed people using some kind of aluminum foil but I'm not sure if that is safe. I have several old phone laying around and I managed to get some of the silver tape and a copper square thing but, again, my phone did not have these things to begin with. I don't want to start adding things only to make it worse.
There is a slight difference of the tape that is on my phone now (the display I just bought) as compared to the old one (broken display). Picture #2 Again, I have no idea if that means anything but I thought it worth mentioning. Picture #3 is how it looks now as if I were going to put it back together. Picture #4 is the part (don't know name) where the videos show to apply the thermal paste and the shielding.
I'm really at a loss as to what to do next and I can't really afford to take it in to have it repaired before next month. If anybody has any insight or answers as to what happened, I'd be very grateful for your help. I'm sorry for the long post. I just wanted to tell you everything I have done in detail. Thank you

If you're using Kernel Auditor or any other kernel adjustment simply reset to default and use only ondemand or interactive. There's also options for the thermal portion of the kernel, don't mess with those. If VCC or another thermal option was checked off turn it back on. Putting the GPS to the moderate setting (the one below high accuracy) will keep the temps down as well. Are you using a custom ROM? If you're on Discord you can feel free to message me SCOPE★ BRΞΛD #8460 . I am only offering that so we can get this resolved quickly for you, just copy and paste since I use special characters.

Omgosh, thank you so much for taking the time to respond! Although I'm sure everything you are saying is very smart, I have absolutely no idea what you're saying. I'll do my best to try and answer you. I don't know what SCOPE is or how to send a message there. I don't think I'm using any thing for the "kernal". Also, I don't know what VCC or Discord is. As far as turning off setting for GPS or any other app, the phone will not stay on. I get about 1 sec after the logo when it boots up, then the error message about overheating and it immediately shuts off. I did a factory reset so everything should be good to go as far as apps. I don't think I'm using a custom ROM. The only thing I did was install TWRP, unlocked the bootloader and rooted the phone a year ago but nothing since then. As I stated earlier, this happened right after I did a display repair. Is there something on the MOBO that can get bumped that will make your phone get hot or send a overheating error. My phone doesn't show any sign that there was ever thermal paste on it prior but should I add some now. Will that help?

Update... Now the phone does not power on at all. When I plug it in to charge it I get an error that says "Device temperature is too high or low. Please move to another place to charge. I wonder where you went. I googled SCOPE so I could sign up to message you like you asked me to but nothing but definitions came up. I know I'm out of my league here. You guys all talk so technical. I didn't understand one thing the person asked me for. I know it's rare to get a response as quickly as I did and I was so happy to see someone had responded. Now, I just feel stupid and defeated. I thought this site was inexperienced with cell phones friendly. I'm just trying to get help so I don't have to go out and buy another phone again. Can someone refer me to a site that is more directed toward people who don't know much about the technical side of cell phones... please! Again, thank you for your time.

HelpNeededPlz said:
Update... Now the phone does not power on at all. When I plug it in to charge it I get an error that says "Device temperature is too high or low. Please move to another place to charge. I wonder where you went. I googled SCOPE so I could sign up to message you like you asked me to but nothing but definitions came up. I know I'm out of my league here. You guys all talk so technical. I didn't understand one thing the person asked me for. I know it's rare to get a response as quickly as I did and I was so happy to see someone had responded. Now, I just feel stupid and defeated. I thought this site was inexperienced with cell phones friendly. I'm just trying to get help so I don't have to go out and buy another phone again. Can someone refer me to a site that is more directed toward people who don't know much about the technical side of cell phones... please! Again, thank you for your time.
Click to expand...
Click to collapse
Hey, I just wanted to say sorry this happened to you. The same thing happened to me. My LG K20 Plus, no matter what button combinations I push and for how long I hold them, will not turn on or go into download mode. Plugging it in to a charger or PC does nothing either. Before it got to this state, I got the infamous green screen of death/Demigod crash handler (google this--it's a known issue with some models of LG phones and it happens when they overheat). It's definitely a hardware/build issue, and especially since this issue keeps the phone from turning on or connecting to a computer, I don't see a workable fix short of buying a new phone, unfortunately. Again, I'm in the same boat so I'm not happy about it either. I would say XDA is by far the best site to find a fix to this sort of problem, so if no one here has any suggestions on how to fix it, I think you (we) may be out of luck.

Thank you for letting me know. I'm not sure of some of what you said but I did catch the bottom line. Basically, just hold onto the phone until someone here comes up with a fix or workaround? I have a question for you. Did your problem start after you did some kind of repair? I'm wondering if I bumped something on the mobo to make it give a false overheating error. Do you happen to know where that sensor might be located? Sorry you are having problems to. It really stinks when your phone breaks and no matter how much time and energy you put it to figuring out the problem to fix it, there just isn't any good answers out there. I wish you lots of luck and if you figure anything out, please update here so I can try it too.

You need a whole new phone.
That or you're gonna have to replace the hardware