Permanent Screen Damage Thread - G2 General

Hi there.
Following @Tijmen's advice, this thread is for those who have damaged screens (specifically the black lines). There are reports that a reboot triggers this issue. @autoprime had his G2 (never flashed recovery, kernel or ROM) get the black lines after rebooting into Stock Recovery when he was only using ADB with the phone hot.
My device:
Model: LG G2 D805
Current ROM: CloudyStock 2.3 (flashed after the screen panel replacement through RMA)
Panel: $ su -c 'cat /proc/cmdline' -> mdss_dsi_g2_lgd_cmd -> LGD Panel
Damage: Permanent Vertical Black Lines on the right side (borrowed screenshot; even in recovery)
External Links: Reddit 01, Reddit 02
From #[email protected] (irrelevant lines have been removed):
<gitanO0|vs980> hey all, long time since i've been on here
<gitanO0|vs980> anyone experience top to bottm vertical black lines on the right side of their screen after flashing rom?
<gitanO0|vs980> persists through boot and seen in recovery
<gitanO0|vs980> i've seen some other folks have this issue after flashing rom but not seen any solutions
<gitanO0|vs980> right after the flash of the rom, the lg boot screen came on and went all inverted and fading... I booted back to recovery and flashed nandroid and now have these perma lines on the right 1/8" or so of screen
<@autoprime> wat rom? PA?
<gitanO0|vs980> no carbon
<gitanO0|vs980> one of the devs made some 24a bootstack changes for some of the repos
<@autoprime> if it persists thru recovery it might be perm damage
<gitanO0|vs980> yeah, that's what I figurered
<gitanO0|vs980> might have to go the send it back route. any good "back to stock, unrooted" guides out there?
<gitanO0|vs980> autoprime, is there anything I can test or look at to verify if it's permanent?
<@autoprime> if its in recovery its most liekly perm
<@autoprime> if it was rom only then its fixable
<gitanO0|vs980> right
Click to expand...
Click to collapse
IMPORTANT - MUST READ IRC TEXT BELOW IN RED!:
<@autoprime> wah... i has lines on mah g2
<@autoprime> RMA
< Compass_Linux> no worries. the'll be present in the
< Compass_Linux> G3 if LG does it right.
< chachin> lol
< Compass_Linux> i wouldn't cheer to soon when this is fixed though. some regressions come with a vengeance.
< Compass_Linux> s/to/too
<@NookieBot> Compass_Linux meant: "i wouldn't cheer too soon when this is fixed though. some regressions come with a vengeance."
<@autoprime> i wasnt even flashing custom rom
<@autoprime> so its not the roms lol
<@autoprime> wasnt using twrp either
<@autoprime> was messing with adb and stock partitions
<@autoprime> reboot into stock recovery... stock recovery has lines.
< Compass_Linux> autoprime: you serious? :|
<@autoprime> Compass_Linux yup :/
<@autoprime> suxxxxxx
* Compass_Linux needs a hammer for his G2. And quick!
<@autoprime> i think its heat. mine was getting really hot in adb
< Compass_Linux> autoprime: can i add your txt to the OP?
< Compass_Linux> damn LG...
<@autoprime> ok
<@autoprime> 100% stock
<@autoprime> :/
<@autoprime> so based on how mine went down.. its not related to rom/kernel flashing :/
< Compass_Linux> cr*p
< Compass_Linux> i'll update the OP.
<+savoca> autoprime: your g2 just got lines one morning?
<+savoca> autoprime: apperently its a possible defect as well.
<+savoca> however pa's kgsl sh*t bumps the probability by like 200%
<@autoprime> today.. lines on right side
<+Khaytsus> autoprime: So your device has lines now? geez
<@autoprime> Khaytsus indeed
<+Khaytsus> Has anyone positively identified this happening on a device that's always been stock?
< Compass_Linux> Khaytsus: yes, just happened to autoprime right now.
<@autoprime> my g2 was 2nd batch
<+Khaytsus> Has anyone positively identified this happening on a device that's _always_ been stock?
<@autoprime> :/
<+Khaytsus> autoprime: Yours hasn't always been stock, right?
<@autoprime> of course it has :|
<+Khaytsus> really??
<@autoprime> this is public record
<@autoprime> :X
<+Khaytsus> My point being nobody really knows what the failure cause is yet.
<+Khaytsus> But nobody has had it happen on a device that's _always_ been stock that I'm aware of.
<@autoprime> Khaytsus i wanna say heat. but idk
<@autoprime> mine has been getting hot the past few days
<@autoprime> never had issue before
<@autoprime> then was using adb and got hot again.. rebooted into stock recovery.. lines
Click to expand...
Click to collapse
How I saw it happen:
After twrp flashed the files mentioned above, the phone rebooted to a black screen with a vertical non uniform white band in the middle, which rapidly expanded sideways until the screen suddenly went entirely black (that's the moment the screen was damaged), vibrated and turned off. When turned on, permanent vertical black lines on the right side of the screen in recovery, in ParanoidAndroid etc. Flashed a stock D805 ROM, problem persists.
What has been confirmed about the origin(s) of this issue:
@dr87 was kind to clarify this issue here, here, here and here.
@houstonn has some information here and here.
This issue in numbers of LG G2's affected is very low. What is increasing until now are the number of different ROMs affected.
*** Unconfirmed Information (updated 28/07/2014) ***:
It was previously thought that Custom ROMs/Kernel were the cause of this problem, and that Stock ROMs/Kernels were safe to use. This is no longer the case due to @autoprime's experience. I removed the safe and unsafe ROMs list because of this and the Black Lines Survey. The possible reason (and I'm speculating here) Custom ROMs are more prone to this is that modifications done to them or their Kernels accentuated the problem that the phone already has but haven't yet appeared (not all devices due to the still small number of complaints). With the information we have now, it indicates that a hardware failure related to heat is to blame, and using a Custom ROM/Kernel can make the failure appear more quickly than if you keep completely at Stock. In @autoprime's case the simple use of ADB then reboot into Stock Recovery with the phone hot triggered the black lines. And since people are asking what is safe to flash and whatnot, there is unfortunately no answer as of yet.
My device is back from RMA (Return Merchandise Authorization). The panel has been replaced, and after flashing (recovery and ROM) no black lines.
@dr87 has a very interesting post here. He has also built a custom twrp with thermal control. If you use this and it corrupts your /cache partition, do this.
@chillstep1998 has a post about an app that can somehow remove (in his case all of them) the black lines. I'm not sure how it works but if you do chose to use it (if you have no warranty for example), remember that your results will likely vary from others experience.
Which Panel do I have? LGD or JDI?:
Here. Thanks go to @autoprime.
When was my G2 manufactured?:
Here. Thanks go to @jdk2. Once you input the URL, check the generated page source code (you might not have to do it; I did) and read this.
Here is another (and better) way to check the same information. Thanks go to @razrzxcvbnm.
I'll leave both methods just in case one or the other "disappears".
Hints:
@RusherDude has an interesting theory. If the conditions he mentions match yours, please confirm and elaborate the best you can in the thread. Thanks!
In the meantime (considering no permanent way to avoid the black lines):
You're crazy about Custom ROMs as I am and still have some months warranty for your device. I had my screen panel replaced under warranty and it's working fine for now. If I get the black lines again I can take it for repair, as long as I'm under warranty. Once my warranty expires, I'm on my own;
You're crazy about Custom ROMs as I am and no warranty for your device. You fall into two situations basically. Repair the screen now for around USD$80 (parts only), or live with this situation and flash to your hearts content. Repairing the screen hopefully fixes the problem permanently.
Black Lines Survey:
User @NicoC72 created a Black Lines Survey, Graph and Spreadsheet. Thanks!
Contact:
You can find me and lots of nice people in the #lg-g2 IRC Channel at irc.freenode.net (go to Freenode for instructions on how to connect)
To see if I'm away, use /whois Compass_Linux.
Compass.

---

RIP screens :/

---

did you try a return to stock method to check if issue survives that?

---

bachera said:
did you try a return to stock method to check if issue survives that?
Click to expand...
Click to collapse
Few people have reported using tot and kdz, and the issue stayed.
Sent from my Vs980 running Mahdi 2.5

---

http://forum.xda-developers.com/showthread.php?p=52969597
so after going to stock and using the dialer code ( update firmware) it stayed after a reboot? Dr's suggestions might be handy. I dont have the issue but listing all avenues walked to solve might help.

---

Is there not a disclosure in every op.. To flash at ur own risk.. I have ran many of houstonns roms and i highly doubt that a rom can cause this.. Closing houstonns thread is little to much dont u think... 4 or 5 out of 1000s of people who flashed this rom. Come on! Bullsheit
Sent from my LG-D800 using XDA Free mobile app

---

I agree, I've seen this issue pop up in multiple rom threads. It's not just PA. It happened to me after a flash of slimKAT a while back. I don't think it's software related. I think it's faulty hardware that's causing the issue. Quite honestly, I think that while backing up and flashing a new rom in recovery, the device gets hot and stresses the hardware.
I think that houstonn is getting crucified unfairly on this.

---

bachera said:
did you try a return to stock method to check if issue survives that?
Click to expand...
Click to collapse
Yes, no success.
Thanks for mentioning. I've updated the OP.
Compass.

---

bachera said:
http://forum.xda-developers.com/showthread.php?p=52969597
so after going to stock and using the dialer code ( update firmware) it stayed after a reboot? Dr's suggestions might be handy. I dont have the issue but listing all avenues walked to solve might help.
Click to expand...
Click to collapse
Doing the Touch Firmware Upgrade also fails, unless you mean something else. Thanks.
Compass.

---

bps119 said:
I agree, I've seen this issue pop up in multiple rom threads. It's not just PA. It happened to me after a flash of slimKAT a while back. I don't think it's software related. I think it's faulty hardware that's causing the issue. Quite honestly, I think that while backing up and flashing a new rom in recovery, the device gets hot and stresses the hardware.
I think that houstonn is getting crucified unfairly on this.
Click to expand...
Click to collapse
You need to share that this happened to u on another rom with the monitor that closed his thread
Sent from my LG-D800 using XDA Free mobile app

---

iamtha1 said:
Is there not a disclosure in every op.. To flash at ur own risk.. I have ran many of houstonns roms and i highly doubt that a rom can cause this.. Closing houstonns thread is little to much dont u think... 4 or 5 out of 1000s of people who flashed this rom. Come on! Bullsheit
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
I don't think closing houstonn's thread is too much. Moderation has tried to contact him to no avail.
As for the 4 or 5 people out of 1000's, those are the ones that have been reported in XDA. If you leave this issue unresolved, you can expect an increase in those numbers.
And so far the damage is permanent.
I mentioned the warranty/liability in my Post 01. If I knew I could damage my hardware permanently like this, I wouldn't have upgraded P.A. and might have changed ROMs (back to stock maybe).
bps119 said:
I agree, I've seen this issue pop up in multiple rom threads. It's not just PA. It happened to me after a flash of slimKAT a while back. I don't think it's software related. I think it's faulty hardware that's causing the issue. Quite honestly, I think that while backing up and flashing a new rom in recovery, the device gets hot and stresses the hardware.
I think that houstonn is getting crucified unfairly on this.
Click to expand...
Click to collapse
It could indeed be a hardware issue, but that doesn't exempt the fact that P.A. (and other ROMs apparently) is triggering this.
Compass.

---

On the Mahdi thread I saw the ROM author say he avoids commits that change the panel driver code, or something to that effect, and that's why his ROM hasn't had that issue. Have there been reports on his ROM too? Now I'm scared to flash anything.

---

Compass Linux said:
I don't think closing houstonn's thread is too much. Moderation has tried to contact him to no avail.
As for the 4 or 5 people out of 1000's, those are the ones that have been reported in XDA. If you leave this issue unresolved, you can expect an increase in those numbers.
And so far the damage is permanent.
I mentioned the warranty/liability in my Post 01. If I knew I could damage my hardware permanently like this, I wouldn't have upgraded P.A. and might have changed ROMs (back to stock maybe).
It could indeed be a hardware issue, but that doesn't exempt the fact that P.A. (and other ROMs apparently) is triggering this.
Compass.
Click to expand...
Click to collapse
Dude every dev warns u that flashing roms can damage ur phone.. Come on... Stick to stock if u cant handLe damaging u phone
Sent from my LG-D800 using XDA Free mobile app

---

I'd like to remind people that flashing a tot or kdz only replaces 12 partitions out of the total 39 partitions on the device.
Partition list here - http://pastebin.com/S5XtQtW3
I can't confirm anything but it seems no one has backed up all partitions and restored them after running into this issue.
so it's still not 100% that it's permanent damage(although it very well could be).
tot/kdz is made to get you booting.. not fix all the things. I have a zip I made to automate the backup of a lot of these partitions... of course you can always do it manually too.
http://forum.xda-developers.com/showthread.php?t=2451390
tbh.. I'm not sure what each and every partition does.. or if it can be shared between users. Example: modemst1 and modemst2 is your EFS and is unique to your phone only.
Only common thing I see between everyone with issues is they all used a custom recovery... maybe we shouldn't use those either

---

autoprime said:
I'd like to remind people that flashing a tot or kdz only replaces 12 partitions out of the total 39 partitions on the device.
Partition list here - http://pastebin.com/S5XtQtW3
I can't confirm anything.. but it seems no one has backed up all partitions and restored them after running into this issue.. so it's still not 100% that it's permanent damage.
tot/kdz is made to get you booting.. not fix all the things. I have a zip I made to automate the backup of a lot of these partitions... of course you can always do it manually too.
http://forum.xda-developers.com/showthread.php?t=2451390
tbh.. I'm not sure what each and every partition does.. or if it can be shared between users. Example: modemst1 and modemst2 is your EFS and is unique to your phone only.
Only common thing I see between everyone with issues is they all used a custom recovery... maybe we shouldn't use those either
Click to expand...
Click to collapse
Thank u prime!
Sent from my LG-D800 using XDA Free mobile app

---

iamtha1 said:
You need to share that this happened to u on another rom with the monitor that closed his thread
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Done

---

iamtha1 said:
Dude every dev warns u that flashing roms can damage ur phone.. Come on... Stick to stock if u cant handLe damaging u phone
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
I assumed the risk of flashing a Custom ROM, as I've mentioned before.
Again, this doesn't exempt the people responsible for the Custom ROM. I'm not seeking damages against them or anything. The only thing I asked for was to remove the P.A. ROMs from when this issue began. And I don't think that's too much to ask for.
Compass.

---

Compass Linux said:
I assumed the risk of flashing a Custom ROM, as I've mentioned before.
Again, this doesn't exempt the people responsible for the Custom ROM. I'm not seeking damages against them or anything. The only thing I asked for was to remove the P.A. ROMs from when this issue began. And I don't think that's too much to ask for.
Compass.
Click to expand...
Click to collapse
Because u had a problem with pa... Everyone else including myself know cannot run it.. I have ran every beta he has released with no problems what so ever! Now a rom that i love may be in jeopardy of being gone.... Thanx for ur help buddy but it wasnt needed!!
Sent from my LG-D800 using XDA Free mobile app

---

Flashes on VS980 no problem. You guys had me worried for a minute. Hopefully they fix the issue across all devices. It's a great ROM.

---

iamtha1 said:
Because u had a problem with pa... Everyone else including myself know cannot run it.. I have ran every beta he has released with no problems what so ever! Now a rom that i love may be in jeopardy of being gone.... Thanx for ur help buddy but it wasnt needed!!
Sent from my LG-D800 using XDA Free mobile app
Click to expand...
Click to collapse
Not only me, if you read the OP. And not only on Paranoid Android either.
I can private message you the Paranoid Android official webpage, where you can download. I cannot post the link here.
You have to contact houstonn to see if it will continue to be developed. I have no influence on the matter, as you suggested the contrary.
I also like Paranoid Android, but this problem cannot persist. It has even spread to other ROMs.
Compass.