yashsingh1/xdaforums huggingface dataset:
[G2 General] Quiox:
"Ok I heard the rumor and seen the post about the dreaded black lines and I decided to do some test on extra lg g2's that some friends let me borrow since they upgraded. Here are my results:

1) 1st LG G2 i kept on JB, and rooted and installed custom recovery (TWRP) with flashify. I then used Xdabbs method to update 24a, and installed CarbonRom 6/1/14 build just like on my phone and everything works great. No issues whats so ever. I even flashed it quite a few times ( 10 -11) times just to see what happens when it was over heating, and still nothing. Works like a charm and no issues whats so ever. I then installed other versions of 24a rom (beanstalk, and liquidsmooth), and again still no issues. I tested each rom by flashing the, quite a few times just enough where the phone starts over heating. I took the phone and reversed Xdabbs method and put the 12b back on and returned it back to stock, and its back to normal. Works like it did when it came out of the box the day it was opened.

Note: This phone came with 12b preinstalled

2) 2nd LG G2 I did a factory restore, and then updated to Kitkat, and rooted and installed custom recovery (TWRP) using autorec. This is where is becaming interesting, and I am not sure why. I made sure to do a nano backup because in the past when using autorec i had bootloops nearly all the time. I had three bootloosp till finally the last chance it didnt do it and it when to the stock rom. I transfered all the compatible 24a roms to my device and starting testing them same as above (10-11 flashes each) Using CarbonRom as the starter. It installed fine and had no issues. Nothing reported with that. Now I then installed Liquid smooth and for some reason it go to hot to touch at points. Installed beanstalk same thing and kept getting the hot to touch. Finally after installing them both a few times too see if i get the same effect still the same thing. Too hot to touch.

Note: This phone came with 11a preinstalled.

My opinion on what I am thinking may be occurring:

1) Any phones that had 11a or early installed may have been a defect and caused the over heating from non stop flashing roms, and then caused the dreaded black lines. It didnt over heat with the 12b preinstalled.

2) Continuing flashing roms like non stop daily to different multiple ones daily could cause this issue.

My honest opinion is this has nothing to do with the roms and more of the system itself. I did research on the internet and found nothing about any kind of software doing this besides viruses made to do this. Again this is just my opinion and I am not trying to upset anyone. Just figure I put my two cents in. Can't blame the roms because from what it seems its a small limited few and not a wide group of people..

Opinions and comments welcome."

This is kinda interesting saw this on the Carbon forum! Might help.
[G2 General] :
could be another common denominator, going from kitkat base to custom, or from jb to kitkat modem to custom.
[G2 General] lacus:
I have posted in a few pages back something like this happened to my d802 too, i didnt hard reset before it went black and it is doing fine up till now

Doesnt matter if you hard reset or let it reboot it self

D802 intl, lgd panel, desember 2013 too
[G2 General] Compass Linux:
My D805 came with 10a. I saw a 11a (or was it 11b?; I can't remember; doesn't matter anyway) but didn't upgrade. From 10a was the version I rooted and so on.

Thanks for contributing.

Compass.
[G2 General] GeneralRam:
I haven't had the black lines but I do flash alot (including versions of Houstonn's PA)

I have an "older model" bought in the UK (D802) around October last year, I also use Clockworkmod when possible - in case this fault may be recovery related. I don't use TWRP unless I have to.
[G2 General] Compass Linux:
In this post Philz Touch Recovery was used and got the black lines. Other conditions also apply in this case, so I wouldn't blame it solely on Philz Recovery.

Compass.
[G2 General] GeneralRam:
I haven't had any issues mate, just putting in my conditions that may help find a common cause :)
[G2 General] arcardinal:
I just wanted to clarify that on slimkat, the only time anybody had black lines were on test builds I put out a few months ago. I was messing with the GPU and it seemed to cause the lines for some people. The post you have linked in the op is from Feb 19th.
[G2 General] Compass Linux:
Mistake corrected. Added SlimKat to the Safe Rom list.

Thanks.

Compass.
[G2 General] 3pcssuits:
Is it me or does it seems as if those damn black lines are multiplying like rabbits on my screen?:confused:
[G2 General] arcardinal:
I guess I can't say its completely safe though. The official builds are using CM's kernel which some users have had black lines on now I guess. And the test builds I've been releasing lately are using dr87's kernel.
[G2 General] edruig:
Is it for all D8xx? or just specific models?
[G2 General] Compass Linux:
I should've confirmed first. My bad. Removed from the Safe List until confirmed to be safe to flash.

Thanks.

Compass.
[G2 General] Compass Linux:
If you can take screenshots it would help. Specially if new lines appear and you can capture the in between.

Compass.
[G2 General] Compass Linux:
Various models. If you search you'll find them in this thread.

Compass.
[G2 General] easyguy:
So basically what this list say is that it is an hardware issue,

Maybe this is the beginning of the end? Maybe eventually all of our LCD screen have have the same fate?
[G2 General] Ascertion:
But Mahdi is a very popular ROM and none have reported damage from using that ROM. I think it's likely a display commit that's causing these issues and the ROMs involved are all pulling that commit every build.

Interesting thing is Sprint OTA mention. I'd like to ask the user who reported that to list the steps they've taken prior to OTA. (Like maybe being on a custom ROM, then tot back to stock and took OTA?)

Sent from my LG-LS980
[G2 General] easyguy:
It was not even a large number of people affected in the first place. Maybe 5 claims out of thousands? PA is the most popular according to the views and the replies. I've had many phones and flashed my phones many times and read hundreds of threads and never once did I see a commit causing damage to a screen. The other day I counted about 1K people downloaded the suspected build from PA with the "screen commit" if you think it was a commit why didn't it affect more people? 10%, 20% 25%? not even, it was close to 0.4%
[G2 General] Ascertion:
True, but don't you think the timing is a bit suspicious that these problems started occurring shortly after the 4.4 sources were being transitioned? Still, even if it affect minority, I feel it to be essential to avoid the risk until the issue is resolved.

Sent from my LG-LS980
[G2 General] Jank4AU:
I've had the screen turn white several times when I flashed a custom kernel months ago. That's not the same issue I'm almost certain.
[G2 General] hassaan123:
I was on stock 4.4.2 rooted. Flashed PA the correct way. Restored apps with titanium. After 30 minutes reboot and black lines :( lgd display and d802 which came with 4.4.2 pre installed.

PS: Had no warranty. Giving it for repair today.
[G2 General] edruig:
wow, damn, now i will be afraid of flashing any custom rom...
[G2 General] Compass Linux:
Could you give us more details? Specifically the versions of: P.A., kernel and recovery. Also if you flashed anything I forgot to mention.

Compass.
[G2 General] jesssiii:
Which version?
[G2 General] hassaan123:
4.3 Beta 7. I was on latest TWRP. didnt change kernel. flashed the latest PA Gapps. gave my device for repair, will receive tomorrow

Ps: the repair guy said it's a hardware issue caused due to overheating while installing a custom rom or updating anything that is linked with the gpu. He said something about the glue so I can confirm its a hardware fault.
[G2 General] Z0ld3n:
Just to clarify: there were reports about black lines back in December (or maybe even later) when everyone was using 4.2 sources so it definitely is not related to transition to 4.4.2 sources. There are more reports now simply because user base is larger than it was back then.

Wysłane z mojego LG-D802 przy użyciu Tapatalka
[G2 General] ps000000:
Oh Interesting thread.

I am from Nexus 5 forum... thinking about swapping mine with someone G2 !!! :eek:
[G2 General] DREWHAMM974:
DON'T DO IT. I have both and the Nexus is better in every way besides maybe battery.
[G2 General] erto90:
every way? lol

I owned nexus 5 before going to g2 and the only thing the nexus 5 is superior is... Nothing??

And also on nexus5 can happens, just read in a nexus italian community
[G2 General] mrdunn:
Would flashing and doing the first boot in a refrigerator prevent overheating and the problem?
[G2 General] Compass Linux:
Don't. Too much humidity. Use an air conditioner if you have to. No guarantees this will avoid the black lines.

Compass.
[G2 General] karazz:
I can confirm that one of the causes is the overheating. Im just sitting here in 30 degrees celcius playing a game on my d802 (pa 4.4 beta1) and suddenly one black line reappears (i've seen it a few times now, started on the previous pa rom). Its only one, and i'm quite confident it will disappear again, so i'm not panicking.
[G2 General] hassaan123:
No, your phone can be damaged due to humidity. But I think there is something in these roms which causes the overheating or too much load on gpu.
[G2 General] RusherDude:
It's semi-permanent or something? It appeared even if boot and then it some day dissapeared?

That would be even more strange... what the **** LG.
[G2 General] karazz:
I have only one black line which isn't there all the time. Just now and then. Temperature could be the trigger but i'm not sure if that's the only trigger.
[G2 General] oadam11:
I just got the black lines by restoring my nandroid backup :(

Sent from my LG-VS980
[G2 General] RusherDude:
Wow...
[G2 General] :
I dont count non permanent ones the same.

I had random black lines back in Januari, always dissapeared. Device was not hot when they came.
[G2 General] jal3223:
There should be a counter or poll so that we could see the actual number of people effected opposed to those who are not. It could give us a better idea of the percentage rates which could prove that it may be a rare manufacturer defect. By looking through this thread it seems like every other phone has the black lines at least once if not permanent.
[G2 General] reas0n:
+1 to this. Personally I NEVER had any problems with screen, any.

But I sometimes flash PA just to test if it's better than Mahdi, and there's always one thing that bothers me - the way how the kernel manages CPU is just sh*tty. I can see that it always activates all cores, that consumes power and makes the phone warm. It doesn't heat so much when for example You use Internet or somethin', but while playing games it can be the real problem. That's why I love faux's EcoMode (dorimanx kernel, Furnace kernel). Also dr87's kernel has very good CPU management.

Btw, You guys, who are affected with this screen fault, had You updates rpm and tz partitions before sh*t happened?

I saw that houstonn said that rpm is power management firmware, it could also mean something.

The truth is, I had my phone few times REALLY warm (usually when converting to ART) but as I said, no issues. I updated these partitions via flash KK .kdz

So, what could I recommend? Flash the latest 4.4 stock (REALLY stock, not like Cloudy's roms) firmware and then use this http://xdaforums.com/showthread.php?t=2715496. You will have updated baseband, rpm, tz partitions.. Just everything what is needed to custom 4.4 roms.

I never had any issues with rotation, GPS, strange screen behavior and so on.
[G2 General] :
interesting qoutes
[G2 General] butler360:
What panel, LGD or JDI?
[G2 General] bweN diorD:
this thread has had over 17,000 views and about 300 post. out of that 300 only a small percentage is actual reports of damage. i have read most if not all of this thread and ill make a wild guess, there is probably 20-30 actual post of damage. the rest is discussion of those post or related discussion.

no damage is acceptable, but 20-30 out of many thousands isnt an epidemic either.

i have a vs980 with the Japanese panel, flashed about 30-40 times since i bought it in November. first used gr33nd3vil's cm with cwm on jb, followed by a couple months on stock kk, followed by (currently) slim weekly's with twrp.

no black lines or funky boot screens when flashing, ever. (knock on wood :))
[G2 General] helpme364:
I've been nervous about flashing Mahdi after hearing about this issue. Looks like I might give it a go now then.
[G2 General] OnePotato:
http://xdaforums.com/showthread.php?t=2769042

This is not safe to flash!

It just broke my screen, I don't have a jdi as op said...
[G2 General] pvillasuso:
Confirming it once more :good:

I said this in my previous posts

And I dont have a jdi on my d802

---------- Post added at 06:34 PM ---------- Previous post was at 06:33 PM ----------

wont fix it , but thanks , I did this !
[G2 General] Compass Linux:
Can you specify more about what you've done?

Basically the old and current: Kernel, ROM, recovery, phone model and anything else you have flashed.

Compass.
[G2 General] OnePotato:
Kernel: Stock

Rom: Old - SlimKat New - TeamEOS

Recovery: Philz

PhoneModel: D802

Anything I flashed: I flashed rom, then SlimKat Gapps

I am so pissd right now...

There is no fix right? Even if I go to stock... I bought my phone in december and living in europe, do I have warrenty?
[G2 General] Compass Linux:
The lines are permanent from what people have said here in this topic. You need to change the panel to get rid of the black lines. Search for USD$80 and you'll find a store mentioned in this thread that sells them.

It is worth going back to stock if you're still under warranty and are taking it for repair. Going back to stock (search for flashing KDZ/TOT in the forum) will wipe the phone clean.

If you're keeping the phone as is, it doesn't matter which ROM you flash, because apparently it can't get worse (there is one report of the lines increasing, but screenshots are required for confirmation).

Whether or not you're under waranty depends on how you bought it and so on.

Compass.
[G2 General] NicoC72:
Black Lines Survey

I decided to make a survey that covers some of the potential factors. So if you experienced the black lines issue, please take this.

ONLY TAKE THIS IF YOU HAVE BLACK LINES!

https://docs.google.com/forms/d/1jpaVYANNn-Cg6Be_EZRJO0FaInzrRodWdHyaRllZ0sc/viewform?usp=send_form

I'm new to this Google Forms thing, so it's not the best but it should help.

Here is a link to the result graphs if anyone wants to see them:

Graph

Spreadsheet
[G2 General] tatanico:
More information of panel.

Terminal emulator:

su

dmesg | grep panel

My panel is lgit, Is lg or jdi?
[G2 General] NicoC72:
LG
[G2 General] kevingokki:
it would ba helpful if the links here will be included in the OP
[G2 General] pvillasuso:
Filled up , thanks for this ! :good:
[G2 General] gypsy214:
So what's the difference between lgd/lgit or jdi?

Recently I seen kernels with these two and TeamOS says if you have JDI dont flash the rom cause it may cause the lines on the screen.

Did LG used two different lcd to build the device?

I'm confused.
[G2 General] vrda08:
I had bad color on LG logo when flashed that teamEOSrom yesterday..and Logo slowly faded...i got scary and hard restart to twrp than flashed mahdi back...i never saw that LG strange colors ever before...maybe i had good luck..no lines on display..all good for now.
[G2 General] NisseGurra:
Nice to see some facts on what roms that breaks the screens.

A friend had same bug today with the latest PA rom.
[G2 General] OnePotato:
Happend to me too... I reflashed and I got the lines.. :)
[G2 General] Compass Linux:
Done!

Thanks @NicoC72!

Compass.
[G2 General] Compass Linux:
Here and here.

Compass.
[G2 General] OnePotato:
http://www.lg.com/de/service-mobil-telefon/lg-G2 on the website is written, that I have 24 months warrenty, so I don't have to pay anything right?

I ordered the lg g3 and I was going to put my phone on ebay, so it sucks !

Also, http://www.lg.com/at/service/service-reparatur/reparatur-anbieter-finden on this website is written, "when you have no warrenty and want to fix your phone, you can use this service down there"

Can I use the service, when I have warrenty? I don't want to send my phone to lg, since I don't have a second phone and I need my current phone
[G2 General] Compass Linux:
24 months warranty? That's nice. Remember to go back to stock before you send it in. You don't have to pay under warranty, but it is best to contact them directly if you have any doubts. Just don't mention flashing, root etc. Hell, don't even mention android at all. Say you have a screen defect (black lines) and ask what you need to do.

Corporations will always take your money, so if you want to spend on a repair even during warranty I don't think they'll deny. :laugh:

Compass.
[G2 General] OnePotato:
Well, they are listed on the site and I am sure, if there is a lg warrenty center in austria
[G2 General] edruig:
i have JDI panel, am i safe to flash?
[G2 General] OnePotato:
Nobody is save to flash buddy...
[G2 General] :
I am curious about something with the whole black line issue. I think I may have another idea. Please input for this will help confirm. What if it has something to do with downgrading the bootloader with autorec? Can anyone confirm keeping JB and installing xdabbebs 24a bootstack did this also?

Could it possible have something to do with autorec? Like I state before I am not pointing blame, but I read alot of post where people stated this has happened to them where they used autorec for kitkat and then installed? Maybe there is something where kitkat isnt working well with autorec downgrading the bootloader. If you downgrade any software with a newer upgrade wouldnt that cause instability within the kitkat itself?

What I am thinking is maybe the downgrade of the bootloader is causing over heating since it wasnt made for kitkat? Maybe it sounds stupid but what if? I remember having the black lines happen once before on a gnex I had and if i recall at one time you had to downgrade part of the software to gain custom recovery. My phone in fact got the black lines. What if we find a way to reupgrade the back to kitkats original bootloader and see if that fixes the black lines.

I know there was one case where someone claimed they got it after the OTA for kitkat, but could there be a possiblity that autorec was used in this case also?
[G2 General] JRJ442:
The bootloader has nothing to do with a display malfunction, or a difference in the amount of heat generated. People have already tried to restore to stock to get rid of the lines and it didn't work. That would've taken them back to KK stock, including the aboot.

I'm no dev, but my personal opinion is the lines are coming from the commits dr87 mentioned combined with excess heat causing a display malfunction. JDI displays have the white line issue, apparently this is our LGD issue. Which is obviously worse. dr87 didn't go in much detail, but in one post he mentioned the commits could be easily picked from the kernel. That makes me think its in LGs KK source. Which would explain why a VZW OTA and a Sprint OTA got them. They were the last to receive OTAs, so maybe the commits were added around then. Going into recovery seems to build up heat anyway. Those of us who run custom ROMs are much more susceptible to the lines, because obviously we go into recovery much more. Flashing nightlies and all. Where as someone who's stock, only goes in recovery once every 6 months. Thats just my theory.
[G2 General] :
But you can't rule out the possibility? Do we know if this started with kitkat release or before.
[G2 General] JRJ442:
Yes you can. Bootloaders have absolutely no bearing on heat in a phone or how a display works. There's no possible way the bootloader would affect it one way or another. They're not even tied together. Now a kernel, and certain commits do. Kernels have drivers in them for displays among other things. Which is why what dr87 said is the only thing that makes sense.
[G2 General] :
No you can't. Your telling me a downgraded bootloader can't have an issue with a kernal made for kitkat. I think it can. I seen something like this happen before with a tablet. Overpowering a bootloader with a kernal could cause overheating
[G2 General] JRJ442:
Once a bootloader loads the boot image, that's it. The kernel takes over, nothing is being overpowered. As I stated, the phone builds heat while sitting in recovery anyway. So that's where some of the heat's coming from. Not for the split second the bootloader is lining up the boot image to take over. Not only that, these issues just started right before dr87 and Savoca both warned about those commits, which was 2 weeks ago. 4.4 source based ROMs and AutoRec have been around much longer than that. If AutoRec was the problem, we would've seen this pop up long before now. And the Gnex thing you mentioned was wrong, we never had to downgrade anything. I bought that phone on launch day and the only thing that had to be done was renaming a file so recovery would stick very early on. It just sounds like you're fishing for something to blame other than what's really going on
[G2 General] :
I am disagree with u on all and leave it at that. I'm done arguing

---------- Post added at 07:03 PM ---------- Previous post was at 06:59 PM ----------

My phone works great lg g2 no black or white lines. I am trying to help people with the issue.
[G2 General] vrda08:
Did u use autorec method?
[G2 General] :
You're wrong.

Literally the definition of the linux bootloader is

"The boot loader is the first piece of software started by the BIOS or UEFI. It is responsible for loading the kernel with the wanted kernel parameters, and initial RAM disk before initiating the boot process. You can use different kinds of bootloaders, such as GRUB and Syslinux. Some bootloaders only support BIOS or UEFI and some support both."

The bootloader does literally nothing except load the kernel and it's parameters. It doesn't generate heat, it doesn't mess with code, it doesn't do anything except a system check and execution of what it's programmed to do. Autorec downgrades our bootloaders to the jellybean one because it's still vulnerable to the loki patch and thus we can still flash custom recoveries etc. If the bootloader was to blame, we would have seen it in Jellybean. You're wrong and your entire assumption about the bootloader is wrong. This all started exploding after a few commits were placed into kernels and people loaded them not knowing. The white lines issue existed before this permanent damage as well because we were unaware at the time that two different panels existed and two different kernel stacks were needed in order to initialize them properly. That didn't cause this heat damage issue.

Stop placing blame where it isn't warranted.
[G2 General] Compass Linux:
Fellows, check the RED BOLD TEXT I left in the OP. It came from @autoprime himself.

I'm updating the OP in real time at the moment, lol.

It's important. ;)

Compass.
[G2 General] :
see its funny that you guys all think I'm blaming someone else when I haven't blamed anyone so just keep your opinions to yourself just like I am right now have a nice day
[G2 General] jesssiii:
I think everything you said is correct but the above. Only because someone got permanent damage after flashing xdabbeb's stock rom and kernel, which he (xdabbeb) stated never contained any of those commits. Someone on sprint who never flashed got it from an OTA, too. It makes it harder to track when people get that other non-permanent screen problem mixed up with this one, also.
[G2 General] :
Look at the original post look like you're wrong too
[G2 General] :
you're correct that it had happened before hand, but i said that it exploded. meaning that a massive amount of people started receiving this problem. i completely agree with you that it makes it more difficult to track this problem though :\