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?
Related
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.
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?
The first day allready 2 times black screen out of no where and afther that no reaction on any buttons.
The first time i waited 10 min or more then the S7 reacted normal again.
The second time i pushed the buttons....
The only reaction is when i press the same time: powerbutton, homebutton & volume button down.
Has anyone the same problem?
I had that issue once with the home button. I had to schedule a reboot through the craptastical built in scheduler that is says it is supposed to optimize the device. Search for restart in the settings.
I have the same sort of problems. All in all the s7e seems very buggy to me. Random crashes (especially in oculus app), sd card is sometimes not recognised and after most reboots I get two error messages (one about touchwiz and one about system proc). I'm not sure what is going on.
My wife's is a black too. I had a similar issues with my s6 last year it was the brightness had been swiped to low in my pocket, I was able to barely see the screen in a dark room and turn it up. No such luck with her s7. Hope someone can offer an idea, I'm headed to Verizon later if I can't fix it myself.
S7 black screen
Verizon did a reset for my wife's S7 to fix it hold down volume down, right side button, and the button on the face of the phone together for 15 seconds. The phone came right back on with all apps and stuff intact. Hope this helps, they said this wasn't the first S7 to come back like this they think it's a software glitch.
Im having the same problem....
any one having dead galaxy s7 edge not broken
ERYCKA said:
Im having the same problem....
Click to expand...
Click to collapse
Try turning off the App Power saving mode!! This fixed the black screen problem on my phone.
I've got the same issue (sometimes 4 times in an hour, sometimes it doesn't happen for 2 days..!!).
I've tried fixing by doing a factory reset and turning app power saving mode off.
Unfortunately this did not fix the problem. Yesterday I got an unresponsive blackscreen again :crying:
Any ideas how to fix this problem?
This happened two days ago with my wife's S7 Edge. She was using it to text me about dinner plans after work, her screen shut off, and it wouldn't work for several hours. The thing was getting very hot. When she was home and charging the phone the screen started working again for a little while, but with several green stripes down the right edge snd aa flashing horizontal band of grey near the top overlaying the screen image. Then when I tried plugging it into my computer to use Samsung's Smart Switch to roll back from the update she had accepted while at work the screen died again. It has not come on since, not even the stripes, and blue or red LED lights once in a wwhile at random. I managed to use Smart Switch to wipe the phone's memory. Then the program took several hours to download something very slowly and install that - a whole new OS update? That completed, and now the charging LED works correctly and the green stripes and grey band are back, flashing rapidly when powering on. Otherwise no screen function. She is shopping for a new non-Samsung phone now. Ridiculous.
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
So, first I thought my brother's A51 was water damaged because it was wet a little bit and charging was being interrupted. I left the phone turned off for the night and wanted to look at it again the next morning. The problem is that the screen or something else stopped working.
The screen works fine in Download mode, Recovery mode, or at splash screen with phone's model name, the problem begins when it's booting to Android. It's still stuck at the splash screen. no boot animation, no lock screen visible, just a model name. It's not bricked, because I can still unlock the phone (didn't have a password) and I can hear the unlock sound or charging sound (it started working again).
I tried factory reset through recovery - didn't help, flashing fresh firmware from Frija - didn't help. The only thing that changed is now the splash screen brightness goes down a bit and I noticed that until I am touching the screen so the phone can't lock itself it doesn't turn off the splash screen, but when I press the lock button it turns off the screen and I can't turn it back on, but the phone still works because I can hear charging sounds and it shows up in Device manager.
I also opened it because I wanted to see if there's any water damage, but I didn't see any water marks or burnt components. I cleaned the charging board with alcohol and let it dry but that didn't help.
I'm worried that there's something wrong with the motherboard or the charging board because it has a screen connector.
I can also see that some people here have similar issues:
Unbrick A51 - Stuck on samsung logo
Hi, My phone is stuck on A51 logo for days now it charges - I can enter download mode easily - I can sometimes enter recovery mode some other times it doesn't let me I tried flashing different stock ROMs of android 10, 11 for the phone with...
forum.xda-developers.com
black screen after splash and unable to factory reset, possibly frp?
Apologies for formatting, typing up on my phone during my break at work. To be more specific, I have a samsung a51 that recently had a black screen of death with no known cause. The samsung splash screen as well as the recovery menus alll work...
forum.xda-developers.com
I should also add that I don't have access to settings so I can't unlock OEM and flash custom recovery / ROM. I also cannot downgrade to Android 10 (duh)
I have exactly the same behaviour here.
I ordered a "defect" A51 on Ebay which was not working. I opened it an saw a water damage at the USB-C charging board. Since there was a lot of oxydated parts I ordered a replacement for this board.
After cleaning an replacing the charging board I have the same issue as szerbi. I see the charging screen (while powered off), I can enter download mode and transfering stock firmware using Odin, I can enter recovery mode. While all these states the display works well and I cannot see any damages like a broken display.
I even got it working correctly after several Odin firmware update and recovery mode / factory reset attempts and I could install some apps and set up my google account. I was very happy. But after some hours again: no screen while Android is running.
Now, when Android is running I hear the charging and the screen shot (pressing volume-down + power buttons) sounds and the phone will be visible as a storage device while connecting to a PC.
Conclusion: The display is black while Android is running. Since it was shortly active I assume either a loose contact on one of the flex cable connetions or a water damage at the displays flex board. Unfortunately latter cannot be checked without dividing the display from the display frame. I assume this is an irreversible process.