The Mrs dropped the tablet and the touch function of the screen stopped working. No amount of cold boots helped so I decided to pop it open to see if I could see anything loose.
I could see that the cable towards the top left (by the power and volume buttons) was loose from the motherboard so I put everything back together.
Now the screen shows nothing... I can see the light come on but nothing is displayed
Related
i accidentally dropped my galaxy mini in water but immediately took it out..removed the battery and all .. there wasnt any sign of water inside the battery compartment and the water damage spot is still white.
but noticed some drops around the three buttons on the front and i 'manhandled' the phone to get the water out..like hitting it against my palm ..
the keys were working alright after this episode but later in the evening the back key started having issues then power key also started malfunctioning like whenever pressed instead of locking the fone it would take a screen shot..and similar problems with all three keys.
currently my back button is not working (sometimes randomly it works for few mins then again stops).. menu key is also not funtioning and power key although is locking the phone but sometimes it goes back to screen capturing.
i wanted to know if this can be due to keys getting stuck or have i done some serious damage?
and also can there be some software issue about this?
Long story short, I've got a fairly new (~few months) totally stock Captivate that I can't get warrantied. So I dismantled it to clean the lock button out (I had done this to another Captivate maybe half an hour before and it now works just fine) because it wasn't working, but now the screen on this one won't turn on. I can hear the boot-up sounds (wooshing and whatnot from the Galaxy S screen), and the touch buttons at the bottom light up when touched, but the screen never comes on. When plugged into a computer, it isn't recognized. When plugged into the wall, there's no indication that it was charging at all, though I suppose it did since it now turns on and didn't before. I've tried holding the volume buttons and the power button to hard reset it, but that seemed to be totally ineffectual (screen didn't come on, no additional/different sounds).
Is there anything I can do to fix this phone for my mom before I leave the country for 5 months?
It sounds like one of the connectors isn't full engaged. Carefully take it back apart and ensure any cables coming from the screen are properly attached.
I hear this a lot. People dismantle their phones and when putting it all back together their ribbon wire to the screen isn't properly secured to its original state.
Sent from my SGH-I897 using xda premium
Thanks, that did the trick for the screen. Turns out the lock button still doesn't work, after cleaning it several times (I used CRC QD Electronic Cleaner). At least it's back to being mostly functional.
Hey all,
I just installed a new digitzer on my Vivid. Everything went fine, and nothing broke as I was taking apart the phone, or putting it back together.
Now that the phone is back together, however, it is having some problems.
First off, When I try to power the phone on, it vibrates like usual, but then doesn't display anything. The phone then proceeds to enter in to a bootloop and keeps vibrating every couple moments. When plugged in to the computer, the orange light comes on for a few seconds, then turns off. Windows will not recognize the phone. All the while, the screen is completely black, and none of the lights come on for the buttons either.
The phone was working fine before replacing broken digitizer.
The phone is NOT rooted, nor has it ever been. I am running stock ICS.
have tried entering Hboot with no avail.
Any advice?
Thank you!
Can you get into any other modes? Try to get to hboot(hold down power button and volume down) while plugged into computer. Should take it to fastboot.
how long for? I tried holding down for a good 30 seconds...nothing happened other than my orange light turning off
I noticed with mine I had to go with:
Remove battery.
Replace battery
hold vol down + power
few seconds later release power
few seconds later in hboot
YMMV due to repair.
You can also try a knoppix boot disc and some tutorial to see if you can find any sign of life off the phone in dmesg.
hope this helps some.
Sounds like a loose connection. Make sure that you've correctly reconnected all internal connections. Especially the connection under the little door with the void sticker on the screw in the battery compartment. If after verifying all connections are made and proper, the problem persists, I'm sorry to say you may have physically damaged the connectors during disassembly. Please visually inspect all connections for damage. A powerful magnifying glass is recommended.
(I have successfully replaced my digitizer twice, and my LCD panel once on this phone...)
Sent from my HTC Dark Raider using XDA.
I have taken it apart twice, checked all connections, and everything is good. Phone cannot enter any boot mode, and computer still doesn't recognize it. The orange light still only stays on for a few seconds when plugged in, then turns off. The phone then proceeds to keep trying to restart itself, but the screen remains pitch black blank
idk.. get a replacement.?
Well a couple of days ago I was being dumb and swinging on some a construction thing and my phone fell out of my pocket about 3 feet off the ground. Well it landed on it's face and I picked it up thanking god my screen didn't shatter but I clicked the power button and it was all white with some vertical green lines. After about 5 seconds the screen goes black and my phone is just dead. I have no idea what's wrong with it but when I hold the power button when it is plugged in the home and back arrow flashes and the phone vibrates. It also does this if I hold the Power and Volume button but nothing happens on the screen. I need help diagnosing this to see if it is an LCD problem so maybe i can just get that replaced instead of the whole phone. Also, the first time I plugged my phone in to the computer HTC manager popped up but now it just wouldn't detect it. Help please!
Hello,
I have a rooted and TWRP installed but otherwise stock 5.something T710 that I had worked on months ago. It's been great and my daughter had been using it to watch videos a couple days ago. I took the tablet from her at the end of our road trip and noticed it had about 63% battery left. I left it in the truck while we went to the movies(about 40 degrees f outsides) and then drove home without ever touching it until we got home. I went to use it when we got home and it would not turn on. I plugged it in to let it charge thinking it died for some reason, using the stock charger, though battery icon never appeared. The next morning I went to check it and it still would not turn on.
When I press the power button or plug in or unplug the charger the Recent and Back soft key lights will turn on for a second, then turn back off again.
I've tried:
Holding the power button down alone for over 3 minutes.
Held the power and volume up button for over a minute
Power and volume down for over a minute.
Home, volume down and power for over a minute
Home, volume up and power for over a minute.
I can connect it to my computer and it recognizes that my Tab S2 is connected but no files show as the default for the device was just charging mode and not the file modes.
Odin3 v3.10.7 recognizes it as connected. But fails to send the TWRP file again.
Any help?
Since the soft keys light up and the computer recognizes the device, it sounds like maybe the tab is still working but with no display? By any chance did you have adb working? I f so you could try rebooting, or booting into recovery to see if you see anything on the screen. It's possible that when you held the button combos, that it did boot into download and recovery but you couldn't see anything? In which case it could be a hardware problem. Hopefully it will fix itself! Sorry I can't be of more help..
Well adb shows the device as unauthorized. Reboot command says the same thing.
The home key is unresponsive to my finger print unlocks and no sound plays when I try to adjust the volume, like the ding sound it makes to hear if this is the volume level I want. There are never any of the capacitive touch vibrations or whatever its called to feel when you press a button on the screen.
I was wondering if it had something to do with hardware it's just strange that it would stop working from just being in my truck. From my knowledge it was never dropped or bumped heavily or anything, at least recently.
I guess it is possible something just burned up inside, that would be inconvenient, I've got to look up if its still in warranty. I love the size and performance of this thing.
Thanks for replying, hopefully more to come.
Still can't get it to work, same issues as above. I let the battery fully die which took about 2+weeks from the initial post. Which is to say that eventually the back and recent buttons stopped lighting up. I recharged it and after holding the power button for a few seconds the same condition repeated itself. If I touch the power button or home button the back and recent button back lights turn on for a moment and turn off again. There is no other indication of life. I would assume if it was just a dead screen then I should feel it try to turn on.
If I had to replace parts which ones should I look at first? Probably just the main board?
Buy a new one. Send yours in as defect. Done.
erase111
I see that is an old thread, but I having the same issue to a certain degree. The screen goes dark, but I can see the back light. If I play around enough times, (pressing the back and process button, before pressing the sensor button... Sometime, pressing the volume buttons and back button before pressing the sensor button), everything goes back to normal. Of course, it some random time, even when I am reading a web page or some other activity, it will go back to black.
So has anyone figured out what this issue actually might be? I thought maybe it was an issue with the ROM I was using, so I just moved over to LineageOS 16, but the problem still continues!