Green Screen? - Google Pixel 2 Questions & Answers

Hey,
I was replacing my screen, when I went to test it instead of the google logo I got a fully green screen, the phone booted, but continued to be green. The always on display looks exactly as it should. Once it was fully on, I managed to put my pin in blind and the phone all works fine (it seems), and some black gets through, I assume the screen turns off those pixels which is why maybe that shows up correctly(ish).
The interesting thing is, I did at one point have to working fully, full colour, this was between reconnecting the ribbon cable and restarting, but I pressed the power button to sleep it and then hit it again and if I remember correctly was green again. So that made me think "poor connection" of come kind. What's even more strange is that when it is green and I press the power button to sleep and wake, the screen appears at least to display the full colours at the end and begging of their animations respectively. Maybe its not full colour, but at least it's more visible.
The final thing is when I go into the bootloader, sometimes it's full colour, and others it's got the solid green effect where black isn't displayed. What's odd is, even when the bootloader is showing correctly as soon as start is click it goes to a full green screen again and we don't see the logo at all. Also I managed to get into safe mode and it made no difference. It's just odd that it seems to decide to green, rather than due to any cable tussle
Basically has to a cable issue, but I'm not sure how to troubleshoot it, and advice on how to proceed would be much appreciated. Like if the screen arrived faulty, if the connector is damaged in the phone so it can't be used, and the motherboard would need replacing.
Thanks,
Dillon

In recovery mode, there's full colour as well, I factory reset the phone, but it made no impact. However entering into recovery mode did flash the google logo and some of the screen whit, and the same thing happened on reboot from recovery mode.
It seems so odd to have these kind of consistent moments of colour and not colour if it's the ribbon

I should have also mentioned, that the clamp is broken, could that be the issue, does the connection need to be screwed in?

Also Here are some images of both the phones connection and the screens

I'd say jb weld your broken clamp before buying parts. Could be as simple as that it's not a tight enough connection

Related

TouchPro screen wouldn't turnoff with powerbutton.. kept getting strange black screen

I had a weird instance happen on one of my pros a little bit ago. I hope I'll be able to explain this well enough for someone to recognize it (i'm pretty tired).
I was charging my pro... i disconnected it from the usb, then went to turn the display off via power button and my screen turned black. Not off, but black. Even in this black mode, you could see fuzzy lines so it was obviously acting strangely (picture an old tv on an input channel not being used. Youd be able to tell the tv was still on...). The phone still functioned, i just couldn't turn the display off at all no matter how many times i pressed power on/off (I'd only get the strange fuzzy black screen). A soft reset fixed this right away... I just think it's weird that it would still acknowledge my power button presses by turning to that black screen... why couldn't it just turn off if it was acknowledging what i wanted?
Has anybody ever had this happen on any of their phones, present or past? I'm thinking this is just an isolated incident, but i'd like to know how rare of an occurance it actually is...
i'd hate to think i'm the only one that this has happened to.
I've had this same problem -- and so is a coworker of mine who has the same phone... we're running Juggalo's 0.06B ROM.

[Q]Samsung Galaxy S3 screen problems

TL: DR: Screen sometimes is totally black, but otherwise the screen seems to work fine. Sometimes the phone acts completely normal. Sometimes the phone acts completely normal, but the screen is tinted green, but only after it's booted up. I can access download screen with no issue, most of the time I can get into recovery with out a problem, but not always.
I'm brand new to the GS3, but I purchased it last week on ebay (described as fully functional) since my other phone has been giving me troubles. I received it last Thursday (5/15/14), and it seemed to work fine. I have not been able to activate it yet since I did not have 4G sim card, so I've just been playing with it around the house to make sure it works until I get my 4G card from Verizon in the mail.
So Saturday comes along, and I notice that the screen is all black, but makes the usual sounds when you touch the screen. I pull the battery, and boot it back up. The Samsung logo would come up, but none of the boot animation. Nothing after the Samsung logo. It seems that if I push the power button, the phone seems to be functional, but nothing comes up on the screen. Sometimes if I push the power button a bunch of times, I can get the screen to come on. The screen looked normal, and everything worked fine, until I hit the power button. Back to the black screen. I booted into recovery, cleared the cache and did a factory wipe, and it seemed to be completely normal for a while.
I've noticed that sometimes phone acts completely normal (proper colors, screen turns off and on as it should), sometimes it works normally but the screen is tinted green (power button turns off and on the screen as it should), and sometimes, the screen is totally black, but the touch functions work normally.
Since the screen always works at boot (I can see the Samsung logo clearly and with no color distortion, but sometimes the rest of the boot animation is gone, even though I hear the boot music), and there is also no color distortion in recovery or download mode, am I likely looking at a software issue?
It is not rooted, and completely stock on 4.1.2. EDIT:Baseband is VRBMF1.
I have tried to make my problem as clear as possible, but I will clarify anything if necessary.
Thanks.
I downgraded to VRBMB1 with ODIN, and I still seem to be having the same issue (screen goes black, won't come back on), although the green tint problem hasn't happened yet. As long as I leave the screen on, it works fine. I'm thinking that this might be a problem with the power button, although I don't understand why it would allow me into download mode with no issues, but trouble doing much of anything else. I'm probably going to be sending it back for a refund, but if anyone has any suggestions, I'm more than willing to listen. Thanks.

[Q] Boot screen visible, but after boot - black screen

My daughter dropped her Nexus 5, which had been upgraded to Lollipop. She had her protective cover on it, and from the outside, nothing seems broken. When we turn it on, we see the white Google letters appear, then the android animation with the flying colorful dots (flying agonizingly slow), and then the phone builds the colorful android letters - again very slowly. All of that takes about a full minute. Then the phone seems fully booted (we hear the notification sounds), but the screen just goes and stays black. I can also get in bootloader and the screen works perfectly there too.
Does anybody have any idea about what could be wrong with it?
Also - I never rooted the phone, nor activated the usb debugging. Does anybody have any idea about how I might still be able to do that? And also - is there any way to back up personal data (like pictures) first?
Thanks!
Well it can't be a hardware fault surely.
You could try and get an adaptor to see if it will display an output on the TV. If you can do that, you may be able to backup the data. Although then again it may just be a waste of money. Does it show up as a device in windows?

[Q] Graphical glitching and static

My friend smashed the screen on his nexus 5 and gave it to some shady repair shop. They replaced his screen (with a white one, on a black phone btw, now it has a white dot on top) and he paid a lot of money for it, but now his display won't work, so he gave it to me to fix, as I have some experience with fixing phones and he has no money left. The repair shop refused to take it back and he doesn't want to start a legal battle. As far as I've tested, the phone shows three behaviours. The first is that the phone boots normally, but without displaying anything. I can still hear it getting notifications and can connect it to a computer, it's just not displaying anything. The second behaviour is identical to the first, except instead of a black screen the phone shows colorful static which seems to correspond to screen-on time (when I lock the phone it goes black and vice versa). The third behaviour, which is the weirdest, is that the display works, but everything displayed is glitching. The google logo maybe has the top 20% moved down a bit, the boot animation may be choppy or distorted, the recovery menu may be divided into blocks which are moved around a bit. In this 'mode', I have never gotten it past the boot animation. The reason I wrote 'may' is because it's different every time, but eventually it always just goes black and stops responding until i disconnect and reconnect the battery.
I opened the phone and fiddled with the connectors a bit and found out that pressing the usb board connector to the mainboard seems to cause the phone to switch between these behaviours. I took a small piece of paper, folded it over a few times and put it on top of the connector and then screwed the cover back on to hold the connector firmly in place. That seemed to put the phone into constant behaviour 3 (graphical glitching).
What could be the problem? I know that the static indicates that the usb board or more probably its connector is faulty, but I'm more concerned about the glitching. It seems to me that the graphical processor is malfunctioning, but I have very little knowledge about graphical processing and displaying so I really don't know. Any help would be greatly appreciated.
UPDATE: the phone just did something weird, when I turned it on it displayed static, but then it started drawing the boot animation slowly from top to bottom. And then proceeded with behaviour 3 as usual, the animation ran at about 3fps and just went blank after 10s.
Okay, I have located the exact location of the fault, the USB board ribbon cable that goes over the battery was bent at a sharp angle and then apparently straightened again. If I press it in that point, the screen switches between static and nothing. I have not been able to recreate the glitching since I cleaned all the parts of the phone with isopropyl alcohol. Still, I'm interested in an explanation to avoid further problems with glitching
now it's behaving even more strangely. When I turn it on, it slowly fades from grey to bright white screen and then goes black and starts blinking a red light. What does this mean? Please help
anyone?

SM-N915T green screen and then bootloop

So my T-Mobile Galaxy Note Edge (SM-N915T) running rooted Android 5.1.1 just encountered the infamous green screen seen. The first time, the green screen disappeared after entering sleep mode and waking up, then about 5 minutes later, the green screen stayed, even after a full reboot (even the Samsung bootup animation, download mode, and TWRP were tinted, so I think we can rule out software issue). The phone was still navigable and usable, just with a serious heavy green tint, curiously, the phone would change between the heavy green tint and a grey tint, and the tint would stay on the upper 30% of the phone and turn grey as it entered sleep mode, almost as if the phone was trying to correct the display or something was barely making contact inside the phone.
Then the green tint got more intense, I could make out the basic background, the fingerprint scanner let me past the lockscreen, and the S-Pen sounds would still play when the S-Pen was removed, inserted, and when the screen was touched. Additionally, my PC does not pick up the Note Edge, yes I have the Windows drivers installed, USB debugging enabled, and MTP + ADB enabled via the secret menu in the dialer. Also OTG is down, my mouse and keyboard are receiving power, but no longer recognized.
Now, after another reboot, the phone is stuck in a bootloop, with the Samsung and T-Mobile sounds playing over and over again, there is a green tint when the Samsung logo should be playing, but a dark screen (as in, AMOLED off) when the T-Mobile animation should be playing.
The phone can't even properly boot into download or recovery mode anymore.
The phone wasn't exposed to heat or pressure, it was just charging off an ASUS power brick and a LG microUSB cable (and was relatively cool, not hot).
The phone was bought second hand, KNOX is tripped, and well past the warranty period.
So my questions for everyone here:
-Any idea what the problem is? GPU failure? Bad solder? Short circuit? Screen failure?
-Any hope? I heard someone else was able to get rid of the green screen after freezing the phone, but at the same time, I don't want to risk condensation inside the phone if I don't have to, and if it was melted solder from some sort of charging issue, heating the phone would probably be a better solution.
While I do have backup phones and and a backup of all my files in case something like this happened, I'm going to miss the curved edge and the S-Pen, and I don't want to take the phone to a 3rd party repair shop, considering you can buy an used functional Note Edge for less than the price of a replacement display, besides, the new Note 7 looks nice.
Anything that hasn't been mentioned above would be helpful... Thanks
UPDATE:
Now the screen doesn't turn on anymore, it flashes green when turned on, but remains dead. The T-Mobile sound still plays, and the motor rumbles for a second, but the fingerprint scanner and S-Pen rumbles and sounds are no longer responsive notification light pulses between white and blue.
Attempting to boot into download or recovery mode yields 2 seconds of green screen, then the T-Mobile boot up sound.
UPDATE 2:
Phone boots properly now judging by the fingerprint scanner responding and S-Pen sound, touch screen also seems to be functional based on S-pen cancel sound, but screen is now completely black, is it safe to assume a screen failure/damage?

Categories

Resources