Found and read a similar thread here: https://forum.xda-developers.com/oneplus-5t/help/help-data-oneplus-5t-unresponsive-screen-t3824092
But in my case USB debugging was set to on, so maybe I can do something, just don't know how? (or the Pie update reverted it to "off", I say that because Windows don't see the phone as a drive when I plug it in on the lock screen)
In any case: After the upgrade to Oxygen OS 9.0.0, the screen has become unresponsive. This has happened occasionally on the Oreo version, and a restart would fix the issue. Now, after restarting, the screen is still unresponsive, I'm not able to get into the phone because I'm not able to put in my pattern. I held the power button and volume up for 10 seconds and tried to enter Recovery mode, but I can't get pass the pattern, because the screen is unresponsive. How do I fix this? Can I at least back up my data?
Related
First off, I have the Canadian LG G4 H812 which I bought back in July of 2015 from Rogers.
So, today I got a software update on my device in my notifications, which I am guessing was the Marshmallow update, and proceeded to ignore it while I was doing some work in an app. My phone then randomly restarted/crashed and kept restarting again and again, which I assumed was the bootloop issue everyone seemed to be having. I then took out my battery and put it back in the phone hoping that might solve the issue. The phone now would load the lock screen but then restart again as soon as I tried entering my knock code. So, I opened up the power menu and held the power off button to access the safe mode boot option and selected boot into safe mode.
After selecting boot into safe mode, my phone has become completely unresponsive and will not turn on. I have tried holding the power button down, doing a hard reset and charging the phone but nothing seems to make the phone turn on or give any kind of responsive.
ANY help you can give me is greatly appreciated. I don't want to send in the phone for repairs as I am apparently no longer under warranty since I got the phone unlocked from the carrier.
My Pixel C is fully changed but the screen is black and won't display anything at all. I know it is on because I can take screenshots with the hardware button and hear the noise. I can also see it on Android Device Manager. I have long pressed with all the different button combinations. It reboots but the screen shows NOTHING (not even the Google boot logo).
Any ideas would be greatly appreciated!
It is stock and not rooted but subscribed to the Beta channel.
I has this problem today as well and I'm on beta as well. I had to press the volume down button as well as the power button to get into recovery mode and rebooted from there. I can only assume it's something to do with the beta as I have not had this before I updated to O beta.
mightywhites29111971 said:
I has this problem today as well and I'm on beta as well. I had to press the volume down button as well as the power button to get into recovery mode and rebooted from there. I can only assume it's something to do with the beta as I have not had this before I updated to O beta.
Click to expand...
Click to collapse
I didn't elect to install O. I didn't see the update notification in the last couple weeks before it had this problem.
I can't get to recovery because the screen is off. How did you do it? Or were you able to see the screen after holding the volume down button as well as the power button to get into recovery mode?
I had to hold both buttons down for about 30 secs and then I got into recovery mode. From there I just restarted the device.
mightywhites29111971 said:
I had to hold both buttons down for about 30 secs and then I got into recovery mode. From there I just restarted the device.
Click to expand...
Click to collapse
Thank you for your reply. Unfortunately, that is not working. I have tried holding for 60 seconds just to be sure. It is so strange!
Not sure what it is in that case. Have you tried the volume up button to get fast boot mode?
I am having this problem aswel, on the android O beta. I can not use it and I can not see the bootloader when holding down power + volume down
edit: resolved the issue by trying button combinations until it booted (took around 2 hours total with time of disappointment in between)
edit2: oh my ****ing god it booted correctly (showed bootloader warning + bootlogo + lockscreen) but it locked and now it's black again!
edit3: was able to get into fastboot after 3 tries so i'm flashing the factory image right now (7.1.2)
edit4: flashed 7.1.2 factory image and was able to fastboot boot into twrp but still no display.
edit5: i am now troubleshooting i checked all the files in /sys/devices/50000000.host1x/54400000.dsi/54400000.dsi.0/backlight/lpm102a188a-backlight/ they all indicate 255 which is 100% anyone have any ideas?
final edit: i fixed it by trying a **** ton of times
Hello,
Can you tell what have you do to repair the pixel? Have the same issues after Oreo update :/
Anyone found a way to fix permanently? Mine started doing it around Christmas 2018, and it takes more and more tries every time (to ctrl-down power) and at some point it works... Then all stays fine until I close the lid or put it to seep.
Did someone reinstalled completly the os and got a success? I am not rooted, this started when It tried (and failed) to install 8.1 (update of oreo).
So my PIxel XL locked up (of course) and I had to soft reset it to come back. This time, however, the touch screen is 100% non responsive. Fingerprint is fine, other buttons are fine, but no touch screen. It happened to be in the middle of Play updates when it locked up - that may be related to the problem.
Anyway, I was going to try and reboot into safe mode,but I cant seem to get it into safe mode without a way to actually turn it off other than another reset, which just boots it again. I got it into recovery mode once but all I could do was reboot.
I;m reasonably savvy with the various tools, but since I can't unlock it I'm not sure where to go next.
And of course I absolutely need a working phone for work (and everything else in the world....) :crying:
Help?
mikeprachar said:
So my PIxel XL locked up (of course) and I had to soft reset it to come back. This time, however, the touch screen is 100% non responsive. Fingerprint is fine, other buttons are fine, but no touch screen. It happened to be in the middle of Play updates when it locked up - that may be related to the problem.
Anyway, I was going to try and reboot into safe mode,but I cant seem to get it into safe mode without a way to actually turn it off other than another reset, which just boots it again. I got it into recovery mode once but all I could do was reboot.
I;m reasonably savvy with the various tools, but since I can't unlock it I'm not sure where to go next.
And of course I absolutely need a working phone for work (and everything else in the world....) :crying:
Help?
Click to expand...
Click to collapse
Factory reset.
toknitup420 said:
Factory reset.
Click to expand...
Click to collapse
It sounds like his phone won't power off though. How do you get to the bootloader menu when holding down the power button automatically does a soft reboot of the phone? He might need to let the battery drain so the phone actually shuts off before he can get to the bootloader menu to do a factory reset.
Literally ALL android devices can be forced to shutdown or to restart in a similar fashion to pc's. literally just hold the power button.
In the pixels case, holding the power button for 15 consecutive seconds will force the phone to reboot.
press and hold power, start counting to 15, as soon as your about to hit 15 seconds go ahead and mash down the volume down button with it. this should get you into fastboot where you can access recovery or fastboot flash a image.
jhs39 said:
It sounds like his phone won't power off though. How do you get to the bootloader menu when holding down the power button automatically does a soft reboot of the phone? He might need to let the battery drain so the phone actually shuts off before he can get to the bootloader menu to do a factory reset.
Click to expand...
Click to collapse
This causes a full reboot on my current and previous pixel, not a soft reboot, ive used this method to save my arse many times. i hold it down, and it restarts all the way to the unlocked bootloader screen
I had a situation where as soon as the phone booted i would get all sorts of errors that prevented me from using the phone or even accessing the power menu, and this is the savior.
possibly try holding it more than 15 seconds? maybe let it cycle twice before attempting to enter fastbppt
Im looking to flash my galaxy s7 active because, for some unkown reason the os is corrupt or has a virus.
I have not downloaded anything, all i did was charge it while i slept, picked it up an hour ago and the voulme keeps going down no matter if i press the key or not, the button isnt damaged the voulme menu never leaves the top of device like some ghost hand is permently holding back on the volume dunno wtf that is. I did a factory reset, that didnt fix the issue. The phone is permmently stuck in safe mode, I have tried to enter recovery mode and it gets stuck in a boot loop or opens the light blue screen with the explaination point, the only options is download custom os or cancel. I would like your help on what software i need to fix my somehow randomly damaged device.
Andriod version 7.0
Model number: sm-g891a
jinakanishi said:
Im looking to flash my galaxy s7 active because, for some unkown reason the os is corrupt or has a virus.
I have not downloaded anything, all i did was charge it while i slept, picked it up an hour ago and the voulme keeps going down no matter if i press the key or not, the button isnt damaged the voulme menu never leaves the top of device like some ghost hand is permently holding back on the volume dunno wtf that is. I did a factory reset, that didnt fix the issue. The phone is permmently stuck in safe mode, I have tried to enter recovery mode and it gets stuck in a boot loop or opens the light blue screen with the explaination point, the only options is download custom os or cancel. I would like your help on what software i need to fix my somehow randomly damaged device.
Andriod version 7.0
Model number: sm-g891a
Click to expand...
Click to collapse
Your phone doesn't have a virus. The fact that you already did a factory reset has already reverted your OS back to retail apps and settings, just like how you first got it.
Given the scenarios you provided, it seems that your volume down-button is indeed "stuck" internally (for some reason). Samsung's universal safe mode trigger is to "press-hold down button while booting"--since your vol-down button is stuck, every time you boot, it will always be in safe mode.
You might want to remove the phone case if you have one installed. Then try to inspect the volume down button a bit closer. If all else fails, get a replacement/warranty or something similar (if still in scope). It could be a hardware defect that just popped up.
Goodluck
jembot said:
Your phone doesn't have a virus. The fact that you already did a factory reset has already reverted your OS back to retail apps and settings, just like how you first got it.
Given the scenarios you provided, it seems that your volume down-button is indeed "stuck" internally (for some reason). Samsung's universal safe mode trigger is to "press-hold down button while booting"--since your vol-down button is stuck, every time you boot, it will always be in safe mode.
You might want to remove the phone case if you have one installed. Then try to inspect the volume down button a bit closer. If all else fails, get a replacement/warranty or something similar (if still in scope). It could be a hardware defect that just popped up.
Goodluck
Click to expand...
Click to collapse
It had to have been a virus or corrupt os, I restarted into recovery and flashed it to stock and it works perfectly now with no issues, the button was not stuck internally or externally, as pressing it caused no issues as well as if the device button was stuck it should have navigated the recovery menu if it was stuck. either way after flashing it works perfectly so no it wasnt stuck, and besides i have a galaxy s7 active, trying to disassemble that thing is a nightmare
Hello guys.
I just bought my Pixel 3 XL phone straight from the Google Store and it just arrived two days ago. After learning about Android Q, I opted-in on the android beta and downloaded the Beta 6 OTA update to my phone. The phone downloaded the OTA and installed it and it seems all is well until the moment it rebooted. It didn't turn on again. It won't turn on. I tried to force restart it by pressing the power button 10 seconds, 30 seconds, or even 1 minute+, won't turn on, no haptic feedback, nothing. I even tried the power button + volume down combo. I also tried plugging it to the original charger it came with for 30 minutes, nothing.
Before this, I have experience with flashing stock and custom roms with pixel devices and other brands (I have owned the OG Pixel until it wont boot due to its motherboard issue), and while normally, I could have just unlocked the bootloader and installed the beta firmware thru fastboot/recovery, or even installed a custom recovery, I didn't and instead tried the OTA update thingy (which claimed that you don't have to unlock your phone or anything). I didn't expect that it will brick this early and unexpectedly.
My suspicion would be that the OTA update broke the bootloader itself, or the firmware that loads the bootloader, thus not responding to the power button correctly. It's also not a power problem, because the phone warms up when plugged to the charger. Also, I download and applied the OTA while the phone is charging (around 70%). Could that also be the culprit?
I'm at my wit's end here. I'm thinking I should RMA this phone, which I haven't done before. Are there any similar issues like this before? Did anyone else had similar issues like this one?
wincaffeine said:
Hello guys.
I just bought my Pixel 3 XL phone straight from the Google Store and it just arrived two days ago. After learning about Android Q, I opted-in on the android beta and downloaded the Beta 6 OTA update to my phone. The phone downloaded the OTA and installed it and it seems all is well until the moment it rebooted. It didn't turn on again. It won't turn on. I tried to force restart it by pressing the power button 10 seconds, 30 seconds, or even 1 minute+, won't turn on, no haptic feedback, nothing. I even tried the power button + volume down combo. I also tried plugging it to the original charger it came with for 30 minutes, nothing.
Before this, I have experience with flashing stock and custom roms with pixel devices and other brands (I have owned the OG Pixel until it wont boot due to its motherboard issue), and while normally, I could have just unlocked the bootloader and installed the beta firmware thru fastboot/recovery, or even installed a custom recovery, I didn't and instead tried the OTA update thingy (which claimed that you don't have to unlock your phone or anything). I didn't expect that it will brick this early and unexpectedly.
My suspicion would be that the OTA update broke the bootloader itself, or the firmware that loads the bootloader, thus not responding to the power button correctly. It's also not a power problem, because the phone warms up when plugged to the charger. Also, I download and applied the OTA while the phone is charging (around 70%). Could that also be the culprit?
I'm at my wit's end here. I'm thinking I should RMA this phone, which I haven't done before. Are there any similar issues like this before? Did anyone else had similar issues like this one?
Click to expand...
Click to collapse
Plug the charger in and hold all 3 buttons together, not saying it will work but worth a try, it deletes battery stats and cache, if it does boot then keep hold of them for about 40 secs, hold them for over ten seconds even try for a whole minute, this sounds like hardware fault to me though. Also, if youve just bought it, swap it.
boe323 said:
Plug the charger in and hold all 3 buttons together, not saying it will work but worth a try, it deletes battery stats and cache, if it does boot then keep hold of them for about 40 secs, hold them for over ten seconds even try for a whole minute, this sounds like hardware fault to me though. Also, if youve just bought it, swap it.
Click to expand...
Click to collapse
I have tried what you suggested. Still nothing.
If I can I'd try to resolve this without returning the thing but yeah, it may really be a hardware fault. Guess I have to wait for a miracle to happen (like the phone turning on by itself after several hours, like with some posts that I have found around).
If all else fail, maybe I'd just ask Google to replace it.
Thanks anyway :good:
You may want to try to see if you get a USB notification from your computer on Windows and if it does try to flash it Back to stock. Hope it works
Sent from my SM-G975W using Tapatalk
kentek said:
You may want to try to see if you get a USB notification from your computer on Windows and if it does try to flash it Back to stock. Hope it works
Sent from my SM-G975W using Tapatalk
Click to expand...
Click to collapse
I also have tried that to no avail. The phone won't just turn on. Anyway I already returned the device. Thanks
wincaffeine said:
I also have tried that to no avail. The phone won't just turn on. Anyway I already returned the device. Thanks
Click to expand...
Click to collapse
Have you tried making an edl cable, to see if the phone boots to qualcomm flash/diagnostic mode. I dont understand why no one in this thread as mentioned EDL mode, its a life saver for when you brick your device. This allows a full factory image flash through qualcomm flash mode. Plenty of tuturials on internet for EDL. (Emergency Download)
boe323 said:
Have you tried making an edl cable, to see if the phone boots to qualcomm flash/diagnostic mode. I dont understand why no one in this thread as mentioned EDL mode, its a life saver for when you brick your device. This allows a full factory image flash through qualcomm flash mode. Plenty of tuturials on internet for EDL. (Emergency Download)
Click to expand...
Click to collapse
Because of warranty?