I got a new Nokia 920 today. Turned it on and got to the welcome screen and that is it. Not matter what I touch the screen does not respond. Is their a way to reboot the 920?
Try soft reset by pressing and holding both the vol - and power buttons for few seconds until phone reboots.
Related
Hi guys,
I tried to update my BONE STOCK Prime to the .28 update. I walked away for about a hour, came back and the screen is black, and nothing I do can turn the thing on.
I've done the following.
Held the power button from 2-120 seconds
Held Power Button + Vol Down from 10-120 Seconds
Pushed the Reset button for 30 seconds.
The only kind of response from the tablet I get is a vibration. The screen never turns on.
Does anybody have any other ideas that my get this thing started back up?
Hold vol up and down and power for a short while before the vibraation occurs. Then release vol up and you should be good. May take several trys.
Sent from my PG86100 using xda premium
Thanks for the suggestion, but it did not work.
Any other ideas out there?
let it drain completely so when holding power button it doesn't vibrate etc.
charge for 5 minutes. does red battery icon come on?
hold paperclip pinhole in for 30 seconds. release. does it boot or is it still black screen.
if still black screen, contact Asus. you may have it stuck in APX mode.
I dropped the flyer yesterday which isn't uncommon and it seemed fine after and I used it normally for the rest of the day. This morning I picked it up noticed a crack and the touchscreen won't respond so I can't unlock it.
Power on and rotation is working fine but I can't manage a reset as it is locked.
I was about to scarper off and look at Nexus 7/Kindle Fire HD prices but checking here it might be a matter of a glass screen/digitiser replacement? Is this correct?
Sounds like digitizer to me.
You can try a factory reset from hboot, as hboot only uses the volume and power buttons to navigate.
Hold down power button until the Flyer powers off. When the screen is black, hold down the volume down rocker (don't let go of it, until I say so later). The Flyer will either reboot itself, otherwise you can press power for a few seconds and release to power on. Keep holding the vol down rocker, until the white hboot screen appears.
I ordered a replacement Digitizer and will attempt this when I have time. I was able to do a HTC sync so it seems to be alive but I'm reluctant to hard reset as the I'm probably losing the dat for nothing.
Hi All,
I have an LG Optimus G E970 on the AT&T network, all stock. I recently dropped it and, of course, the digitizer glass cracked. The screen still worked just fine, and I could turn it on and off without a problem but no touch at all. As I was trying to shut it down without using any buttons by just holding the power button, it started acting strangely. I would turn it off (screen timeout) by just pressing on the power button, but when I would wake it up (by again pressing the power button) the cap. buttons on the bottom would light up, but the screen would stay dark. I chalked it up to the digitizer being messed up.
I have since installed a new screen/digitizer assembly, and it works great when I turn on the phone. However, as soon as the screen goes to sleep, I get the same problem - cap. buttons light up, but the screen stays black. All the buttons are working, as I can here them clicking, and I can turn up the volume, etc, I just can't get the screen itself to light up.
Has anyone run across this problem, or have any suggestions? I've already, reluctantly, tried a hard reset, which did not solve the problem, as well as any other little fixes that I found in this and other forums. I'm thinking it's a software issue of some sort, since the screen and everything work great when the phone is on, but I don't really know. I wanted to see is there were any answers out here before I tried rooting and installing a new ROM, which might be problematic anyways if the screen doesn't come back on.
TIA,
George G.
[AT&T] V10 Screens won't power on but phone vibrates once when power button pushed
BONE STOCK ROM. One day my V10 screens were unresponsive. The mini screen was updating time correctly but wasn't responsive to touch, and the power button would not wake the main screen.
I removed the battery for 30 seconds then replaced, pressed power button. I had one short vibration then nothing. Neither screen comes alive. Removal of battery and replacement followed by pressing power button always gets a single vibration like it's powering up, but screen never comes alive.
Has this happened to anyone else? I am also wondering if in repair, someone could somehow access my data... I have sensitive information but the system is security locked with screen pattern.
Suleeto said:
BONE STOCK ROM. One day my V10 screens were unresponsive. The mini screen was updating time correctly but wasn't responsive to touch, and the power button would not wake the main screen.
I removed the battery for 30 seconds then replaced, pressed power button. I had one short vibration then nothing. Neither screen comes alive. Removal of battery and replacement followed by pressing power button always gets a single vibration like it's powering up, but screen never comes alive.
Has this happened to anyone else? I am also wondering if in repair, someone could somehow access my data... I have sensitive information but the system is security locked with screen pattern.
Click to expand...
Click to collapse
Sounds like your LCD and digitizer has went out need to get it replaced . No they can not access your phone all they will do is replace the LCD digitizer and power it on to see if it comes on once it does there job is done . Replacing or repairing repairing screen will not erase anything because all your info is saved on the motherboard
I have a Verizon LG G6 phone, and the screen keeps going black, then the power button won't bring it back on. I am able to boot it by holding vol down & power though. The back glass is cracked near the power button, but the power button itself (the circle) is fine. Has anyone heard of this happening? I have tried booting into safe mode, but the same thing happened there.