Screen is black and no combination of button input will do anything. Unit will charge and CPU is running since it's sending battery and location data. Unknown if unit may have been damaged/dropped. Have ADB. Help!
The phone is making normal notification and ringing sounds. I managed to locate and run Scrcpy.exe, a "carbon copy" program that lets you remote-in to the unit using a computer keyboard and mouse and ADB over a USB connection.
Invoking Scrcpy.exe I was greeted with an image of the "normal" phone screen (what I should be seeing on the phone's display if it wasn't black.) After about 10 seconds the phone-screen on the computer turned black and I was back to square one. Tried again and quickly used the mouse to trace my unlock pattern, this worked. Using the computer keyboard, mouse and display with Scrcpy.exe I was able to read email, check voicemail, I presume I could do anything I would have been able to do on the phone's touch screen (unknown if the touch screen still works).
Unfortunately I haven't yet been able to coax the phone's screen into displaying anything other than black.
It's beginning to look like the screen is FUBAR -- or is it?
E: The home key, power key, and the touch keys to the left and right of the home key all work. Ran Samsung diagnostics by pressing *#0*# . All diagnostic tests passed except for display and touchscreen.
Will attempt to drain the non-removable battery and try again.
Cured it by draining battery!
The battery was allowed to completely drain and was reconnected to a charger, resulting in the screen coming back to life!
Hooray beer!
/thread
Related
Hello
My phone accidentally got dropped in water today (for less than 1 minute).
I took the back cover off and removed the battery and SIM card. I wiped everything with a dry cloth.
I put everything back together and the phone did turn up. Touchscreen display is working but unfortunately screen is not responding to touch.
I took a friend's phone and called my number. I could see caller ID on the screen and three buttons - for accept, reject and message - however touching them does not work.
I sent myself a message on WhatsApp and I did get a notification on my phone (lock screen) that a message has come - thus WiFi is also working
I connected the phone to charger and I could see the battery icon on top-right turned green, indicating that the phone is charging.
I can however see a headset/headphone icon on top-right as well, even though no headphone is connected - although I am not concerned about this as I don't use headphone at all.
My issue is that touchscreen display is not responding to my touch, which makes the phone unusable. Note that the display is there and the clock is updating the time.
Is there anything that can be done please?
When I first restarted the phone after wiping off the wet parts,
I received a screen with following buttons.:
Chinese
PCBA Test
MMI Test
MMI2 Test
Hardware Info
fastboot
recovery
download
Power Off
PCBA test: FAIL
MMI test: FAIL
MMI2 test: FAIL
Finish(==VolUP+Power In==)
However, after a few restarts, this above screen went away and I was getting a normal lock screen (which I could not unlock because the screen is not responding to my touch)
Also when I press the power button to shut down, I get 4 icons (as usual for shut-down, flight mode, restart etc). But I cant interact with them. I have to remove back-cover and take battery off to shutdown the mobile phone.
So, seems like it is the responsiveness of the touchscreen, which is dead.
ilikeandroid2015 said:
When I first restarted the phone after wiping off the wet parts,
I received a screen with following buttons.:
Chinese
PCBA Test
MMI Test
MMI2 Test
Hardware Info
fastboot
recovery
download
Power Off
PCBA test: FAIL
MMI test: FAIL
MMI2 test: FAIL
Finish(==VolUP+Power In==)
However, after a few restarts, this above screen went away and I was getting a normal lock screen (which I could not unlock because the screen is not responding to my touch)
Also when I press the power button to shut down, I get 4 icons (as usual for shut-down, flight mode, restart etc). But I cant interact with them. I have to remove back-cover and take battery off to shutdown the mobile phone.
So, seems like it is the responsiveness of the touchscreen, which is dead.
Click to expand...
Click to collapse
Taking out the battery was the right thing to do. But you should have left it out for longer. Put the phone into a bag of rice or silicon desiccant and leave it for a while to ensure all the moisture has been removed. Its highly likely that your phone is still wet internally which will definitely screw around with the touchscreen. Right now you should just hope that your touchscreen controller hasn't been shorted out permanently, which can happen when moisture gets in.
Hi,
my name is Josemari, from Spain.
I have a TF101 with dock (and original rom from Asus) that does not display anything on screen since a soft fall from 10cm (daughter in a very very small chair).
When i plug the charger, it works (and beeps -charge-). When i plug the dock, also beeps. When i connect through hdmi output to my tv, it also works. I can use the tablet perfectly with my fingers.
What can i do?
I disassembled the tablet and i checked all conectors, but i do not see anything wrong.
Thanks.
I had the exact same problem. Even though it has fallen before without a problem, in my last 2 cases it was a loose connection for the video screen. I had to open up the tablet and simply push the video connection back on all the way. It's rather easy if you're familiar with taking things like this apart. Make sure you are careful when you re install the side trim that holds the buttons. It's easy to break the red tabs that press against the buttons. It may be helpful to you to look up a disassembly guide. I believe if you google the specific issue you will find pictures. Again it's been a long time. Hope this helps
I have the same issue since a few days.
Difference here, when I boot up (holding power button until reboot) the screen is on (Asus logo and boot animation)
The display goes balck / disappears (backlight off) when the lock screen comes up.
Checked the inner display cable and connector with no success.
Did a factory reset and it was working again, until I changed the brightness to a higher level. Then the screen was dark again.
I managed to change brightness to a lower level using the working HDMI interface. After that I switched the tablet off and on and the screen was lit up again.
Another effect: when power adapter is plugged in, I can go to a higher brightness level until the backlight turns itself off.
It looks like a hardware defekt of the backlight electronic to me. Couldn't find any spare parts, such as backlight inverter, though.
Can anybody confirm this or knows how to repair?
I will use it at 30-50% brightness now and see if it gets worse over time.
Hi guys,
This problem has me stumped, so I figured I'd consult the hive mind.
The touchscreen works fine after the phone is turned on - be that for a continuous period of 30 seconds or 30 minutes. However, if/when it goes to sleep, the touchscreen becomes completely unresponsive on wake up. The screen turns on, rotates, and the physical buttons work fine. I figure no touch input is acknowledged, because if I tap the screen after it dims nothing happens; but if I press a physical button, then full brightness is restored.
I have been looking around for a solution for some time, but none of the three I found appear to be working, ie:
- Ensuring the Wi-Fi's set to be permanently on (no change on any of the settings)
- Changing the ROM (problem appeared in stock ROM, it now sports LineageOS)
- Changing the digitizer (problem is the same on old or salvaged screen)
At this point, I am not sure what else I can try. Any ideas would be most welcome.
Maybe charger? Some cables/chargers make touch panel go crazy (it used to happen to me with bad chargers) so try to change charger and USB cable.
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
I'm attempting to run a google pixel 3 without the physical screen. The phone will be used in remote management, so I have a remote management utility installed on the device as well.
Everything works flawlessly when the screen is installed - all apps and configurations work as they are intended. However, once the screen is removed, the phone doesn't work. On a pixel 3a I was able to attach just a ribbon cable for the screen without the actual screen, and when I pulled it up in airdroid, it would only display a condensed screen about 1/3 the height. On the Pixel 3 it doesn't load up at all.
I've connected the phone to my computer with USB debugging enabled. Without the screen it shows up in the devices list. But with the screen it doesn't even show up in the devices list. The only way to make the phone operational is to remove the battery cable then restart the phone. About 30% of the time it displays a message upon boot "This device failed to boot, do you want to factory reset", with an option of "yes" and "reboot" (selectable through the volume and power buttons).
Also of interesting note, if I power on the phone without the digitizer connected, I can use AirDroid just fine, but it won't register my clicks on the remote view screen. Which leads to believe the phone is registering the hardware of the screen and digitizer upon boot.
If I disconnect the digitizer and LCD after the phone is booted up, I can attach them both and it'll work. It's just when they're disconnected from the phone during the initial boot phase.
I tested this with a Galaxy S8 previously, and that phone worked just fine without the screen attached, and ran fine that way.
Does anyone have any ideas on how to "register" the hardware correctly? I'm not certain that's what's happening, but it appears to be something with the hardware not registering correctly, or something like that. What's odd, is that it doesn't work even with the ribbon cables attached. It requires the full screen to be connected to the ribbon cables.
I've searched up and down google, but there doesn't appear to be much information available on this, as it appears to be a very specific problem which not many people encounter.
Thanks!