ok so here is the rundown
Device: HTC one on vzw
Rom: Slimbean 2.x
Gapps: Slim AIO gapps
had a weird problem with the display today if anyone has had this or know someone who has i would greatly appreciate the help. I just flashed Slimbean 2.x last night and all was good. no problems what so ever, got everything setup and was working fine. this morning around 10am i opened snapchat to view a video. i clicked on the video and as soon as it started the screen went blank and would not turn on. i tried holding the power button down for at least a minute and nothing. also tried power and volume down, power and both volume buttons, power and volume up and still nothing seems to work. when i plug it into the wall charger the red LED light does not turn on and screen does not wake. when i plug it into the computer the computer does not ever read the device and noting pops up letting me browse the files on the phone. i have no clue why this happened it has been working fine for the 3 months that i've had it. took it to verizon about an hour ago and they didn't know either but they are sending me a replacement htc one. all i really want now are my photos that i have on the phone.
does anyone have any ideas about what i could do?
thanks
I had something similar and think it was conflict related. After installing the "advanced power menu" with xposed, I had an issue when trying to use it to boot into recovery. Basically it had timed out and then went away without rebooting. The next time I tried it locked up and my screen went black. My keys would light up if I clicked on the power button (it was dark in the room so the sensor was still working), but nothing else. Nothing I did would make the screen turn on at all and holding down the power key to reboot did not work. I just planned on letting the battery die out. After about 45 minutes, the phone just rebooted and everything was back to normal. I really think it locked up due to a conflict similar to what a PC might do.
Hello everybody,
2 days ago, my Google Pixel XL received the January patch and downloaded it. It installed the first step flawlessly, but the second phase took a lot of time (the progress bar was staying around 50% for at least 60 minutes). Since I was not watching my phone during the rest of the process, I cannot say precisely what happened, but as I wanted to look how far the progress bar is, the phone did not respond anymore.
here is a summary of the situation:
- it is the pixel XL with 128GB of memory directly bought on the Google store
- the battery was fully charged before the update began, an it was approximately around 85% as I looked at the progress bar for the last time
- the phone was not hot during or after the update
- the screen is now black and does not display anything (I have tried everything I thought about: it is definitely black and nothing happens anymore, even when plugged for charging, or when connected to a PC (the USB communication with the PC is not building up anymore))
- the phone react only when the power button is maintained pressed for several seconds: it vibrates briefly, but nothing more happens
- the phone was never rooted, there was no "unknown sources" app installed (I had Cerberus installed but have uninstalled it 2 days before the Android patch was installed), and the USB debugging is not activated
- I called the Google support and they immediately proposed to ship a replacement device (they did not ask me to do some tries)
I have tried to discharge the battery by maintaining the power-on button pressed during hours: the red led then turns on when the charger is plugged in, but the screen stays black.
If somebody has an idea of a test I could make, I would appreciate the held.
Thanks a lot in advance for your suggestions.
Best regards
Vincent
Have you held power and volume down for 14 seconds?
vincent.lorentz said:
Hello everybody,
2 days ago, my Google Pixel XL received the January patch and downloaded it. It installed the first step flawlessly, but the second phase took a lot of time (the progress bar was staying around 50% for at least 60 minutes). Since I was not watching my phone during the rest of the process, I cannot say precisely what happened, but as I wanted to look how far the progress bar is, the phone did not respond anymore.
here is a summary of the situation:
- it is the pixel XL with 128GB of memory directly bought on the Google store
- the battery was fully charged before the update began, an it was approximately around 85% as I looked at the progress bar for the last time
- the phone was not hot during or after the update
- the screen is now black and does not display anything (I have tried everything I thought about: it is definitely black and nothing happens anymore, even when plugged for charging, or when connected to a PC (the USB communication with the PC is not building up anymore))
- the phone react only when the power button is maintained pressed for several seconds: it vibrates briefly, but nothing more happens
- the phone was never rooted, there was no "unknown sources" app installed (I had Cerberus installed but have uninstalled it 2 days before the Android patch was installed), and the USB debugging is not activated
- I called the Google support and they immediately proposed to ship a replacement device (they did not ask me to do some tries)
I have tried to discharge the battery by maintaining the power-on button pressed during hours: the red led then turns on when the charger is plugged in, but the screen stays black.
If somebody has an idea of a test I could make, I would appreciate the held.
Thanks a lot in advance for your suggestions.
Best regards
Vincent
Click to expand...
Click to collapse
How long have you had it plugged in? It sounds like the battery is empty.
Try to leave it on the charger for a couple of hours.
If it does not boot by pressing the power button, you can try to boot bootloader by pressing volume down and power at the same time.
The battery has been fully charged, so I am pretty sure that it is not the battery (the phone has been plugged in for more than 12 hours to recharge it).
I have also tried every button combination that I know and that I found on the web: there is nothing else than a short vibration when the power button is pressed, but no reboot and nothing is displayed.
vincent.lorentz said:
The battery has been fully charged, so I am pretty sure that it is not the battery (the phone has been plugged in for more than 12 hours to recharge it).
I have also tried every button combination that I know and that I found on the web: there is nothing else than a short vibration when the power button is pressed, but no reboot and nothing is displayed.
Click to expand...
Click to collapse
I would try pressing and holding the power and volume down buttons until you get the short vibration. Hopefully after vibration you will be in bootloader. Then connect to a PC and try and flash-all the factory image.
Golf c said:
I would try pressing and holding the power and volume down buttons until you get the short vibration. Hopefully after vibration you will be in bootloader. Then connect to a PC and try and flash-all the factory image.
Click to expand...
Click to collapse
Thanks for your response. Unfortunately, after the vibrations, I do not get anything on the screen. In my previous phones, I was used to flash ROMs and so on. I never bricked a phone. But with the Google Pixel XL, I must admit that I do not have anymore ideas how to rescue it. I have tried the following:
- holding only the power button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume up button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down + up buttons for several seconds --> short vibrations after several seconds, but nothing else
I have made these tries with the charger plugged in, plugged out, and removed at different instants. Nothing more than just the short vibrations.
vincent.lorentz said:
Thanks for your response. Unfortunately, after the vibrations, I do not get anything on the screen. In my previous phones, I was used to flash ROMs and so on. I never bricked a phone. But with the Google Pixel XL, I must admit that I do not have anymore ideas how to rescue it. I have tried the following:
- holding only the power button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume up button for several seconds --> short vibrations after several seconds, but nothing else
- holding the power button and the volume down + up buttons for several seconds --> short vibrations after several seconds, but nothing else
I have made these tries with the charger plugged in, plugged out, and removed at different instants. Nothing more than just the short vibrations.
Click to expand...
Click to collapse
Your screen may be black, but there is a small chance your still in the bootloader. I have read that other people have recovered from a black screen. I still think its worth a try to connect to a PC and see if the factory image flashes after holding power and volume down and after vibration. Those vibrations have meaning.
Thank you, I gave it a try: the PC does not even ask to install a driver, when the phone is connected. I made several tests, exactly as it is required to flash it, but there is no communication with the PC. :crying:
vincent.lorentz said:
Thank you, I gave it a try: the PC does not even ask to install a driver, when the phone is connected. I made several tests, exactly as it is required to flash it, but there is no communication with the PC. :crying:
Click to expand...
Click to collapse
I thought there might be a small chance. At least you will get a new phone. Best of luck.
I hate to tell you this but I had the same issue with a 32 GB 5 inch pixel...It was dead...Everything you have said is what happened with mine.
What happened was the slot the phone was trying to boot into had no bootloader or it was a bad flash...Either way, the slot didn't have a bootloader on it when it tried to boot and that black screen is the result...Google sent me a new one and all was well and they will do the same for you.
This is why I don't trust OTA updates...I manually flash everything and I'm sure to flash the bootloader to both slots anytime I update my phone...Good way to keep this from happening again....Best of luck man
You keep saying several seconds. You gotta hold the power and volume down for a pretty long while. Just saying.
Probably a bad boot partition though..
Thank you very much for your kind support, guys.
Your explanations is very interesting. This means that the strategy implemented for the bootloader itself is not very safe. I would be interested in knowing how such a faulty flash can happen and what are the possible reasons behind. Is there a procedure that can increase the chances for a successful flash by doing some things before the OTA update is allowed to be installed?
xocomaox said:
You keep saying several seconds. You gotta hold the power and volume down for a pretty long while. Just saying.
Probably a bad boot partition though..
Click to expand...
Click to collapse
Believe me, I pressed the button for a very long while also (hours) by blocking the button in such a was that the phone boots up until the battery is discharged. So also such an extreme tray was made. The only consequence was the red light flashing.
Iam having similar(exactly) situation as stated by OP. Phone dead, only short vibration, no boot loader, no dshub qualcomm either detected while plugging USB to pc. Charging still ok.
update: now phone can be detected as Qualcomm HS-USB QDLoader 9008 in Device Manager.
droidan said:
Iam having similar(exactly) situation as stated by OP. Phone dead, only short vibration, no boot loader, no dshub qualcomm either detected while plugging USB to pc. Charging still ok.
update: now phone can be detected as Qualcomm HS-USB QDLoader 9008 in Device Manager.
Click to expand...
Click to collapse
Phone is in Qualcomm Emergency Download mode. What happened? Also a bad OTA flash?
You only have two options:
Press power button for ~ 30 seconds to get out of EDL. If it's completly bricked then RMA. You're under warranty yeah?!
5.1 said:
Phone is in Qualcomm Emergency Download mode. What happened? Also a bad OTA flash?
You only have two options:
Press power button for ~ 30 seconds to get out of EDL. If it's completly bricked then RMA. You're under warranty yeah?!
Click to expand...
Click to collapse
Yes. Bad OTA Flash.
Hold 30secs still nothing.
droidan said:
Yes. Bad OTA Flash.
Hold 30secs still nothing.
Click to expand...
Click to collapse
RMA is your only option so
I have a Samsung I9250 which I've unlocked, rooted and loaded with Lineage. The Lineage version is 13.0-20171126-NIGHTLY-maguro. The recovery is TWRP and the root is through SuperSU FREE (CM) v2.79-SR3. The On/Off button doesn't usually work. If the phone is off then pressing On/Off has no effect. Occasionally it works for no reason I can see, it seems to be random, but for the most part it simply doesn't have any effect. If the phone is on then the same is true. Turning it off from the On/Off button is usually impossible. I get round this through Settings>Display & lights>Wake on plug. This means I can activate the phone by connecting it to a PC using its USB cable. This will activate the phone immediately if it is off. It doesn't help with turning it off and I am usually reduced to taking the battery out. The phone is effectively useless although it is clearly NOT bricked. When I can turn it on it works fine.
I don't know if this is a hardware or software problem. If it's a software problem I don't know if the fault is in Lineage or TWRP or SuperSU. I noticed that the problem existed before I installed SuperSU. Has anyone else come across this problem? I'm reluctant to bin the phone because I spent such a long time getting Lineage on to it, but, if I can't turn it on or off it's not really a phone. Any help would be greatly appreciated.
@erich_vogt it's more a hardware problem, you can buy a new button (find link of online stores in accessories section or google.it).
for easyness you don't need to plug charge/usb everytime, you can set volume button waker, find in settings > button (don't remember where correctly, it will be somewhere there) then use volume switches to wake it.
erich_vogt said:
If the phone is off then pressing On/Off has no effect.
Click to expand...
Click to collapse
There have been power button bugs, but only in the OS. If it's not turning on from off, then I think the switch is broken! A common failure in old phones, which is why "volume button to wake" is important, to reduce load on the power button.
Thanks very much for offering to help.
I already had the option for the Volume control buttons to wake the phone turned on. It's here - Settings > Buttons > Volume Buttons > Wake up device. This worked for a while then stopped. I disassembled the phone to look at the On/Off button. I tried turning the phone on directly from the metal contact pad beneath the plastic button. This worked. When the phone had booted I checked to see if there was another nightly update for Lineage. There was the 3rd of Dec update. I downloaded and installed the nightly update using TWRP. It reported a successful install. The phone rebooted and never got past the Google boot-up screen. I waited for a few minutes and the took the battery out and tried turning on again from the metal contact pad. The phone booted but again got stuck (or seemed to) on the Google boot-up screen. I'm afraid that's it for me. This doesn't appear to be related to anything I have done or not done. The phone is just taking up too much time and it will have to go the the local recycler. Life is, as they say, too short. Thanks again for your suggestions.
erich_vogt said:
Thanks very much for offering to help.
I already had the option for the Volume control buttons to wake the phone turned on. It's here - Settings > Buttons > Volume Buttons > Wake up device. This worked for a while then stopped. I disassembled the phone to look at the On/Off button. I tried turning the phone on directly from the metal contact pad beneath the plastic button. This worked. When the phone had booted I checked to see if there was another nightly update for Lineage. There was the 3rd of Dec update. I downloaded and installed the nightly update using TWRP. It reported a successful install. The phone rebooted and never got past the Google boot-up screen. I waited for a few minutes and the took the battery out and tried turning on again from the metal contact pad. The phone booted but again got stuck (or seemed to) on the Google boot-up screen. I'm afraid that's it for me. This doesn't appear to be related to anything I have done or not done. The phone is just taking up too much time and it will have to go the the local recycler. Life is, as they say, too short. Thanks again for your suggestions.
Click to expand...
Click to collapse
3rd dec nightly has problem with booting, get back to older than it.
Reset volume button waker, if it stopped working. I never had problems with volume buttons.
I'd second the idea of it being software. I've had problems with all builds after 20171112. I get the impression there was something overlooked when the developers unified the builds for different GNex variants.
If you still have the phone, try that 20171112 build.
I don't know how to roll back to an earlier build. The phone will not boot. If I try VolumeDown+On/Off to try to get into TWRP Recovery mode nothing happens. The adb bridge option is turned on but if I connect the phone to my PC with a usb cable it does not appear in Device Manager as it used to. If I run ".\adb devices" it is not listed so clearly adb cannot find it. I don't know what else I can do.
erich_vogt said:
The phone will not boot. If I try VolumeDown+On/Off to try to get into TWRP Recovery mode nothing happens. The adb bridge option is turned on but if I connect the phone to my PC with a usb cable it does not appear in Device Manager as it used to. If I run ".\adb devices" it is not listed so clearly adb cannot find it. I don't know what else I can do.
Click to expand...
Click to collapse
Ah, ok. Sorry, I thought you could still do more than that, but it was rebooting and unusable in that sense.
That's well beyond any help I can offer you. I hope you got any data off it.
My wife was typing and the screen froze, she pushed the power button was the reboot or power off box appeared. She selected reboot and the screen went dark and now nothing comes on no matter how long the power button or power + power up or power down is held. I plugged in the charger and the battery icon does not appear. Could the connection from the motherboard to the screen have come loose? It seems strange that it would die coincidentally after requesting a reboot. Another other suggestions before I try to sell it as a paperweight on Ebay?
lmacmil said:
My wife was typing and the screen froze, she pushed the power button was the reboot or power off box appeared. She selected reboot and the screen went dark and now nothing comes on no matter how long the power button or power + power up or power down is held. I plugged in the charger and the battery icon does not appear. Could the connection from the motherboard to the screen have come loose? It seems strange that it would die coincidentally after requesting a reboot. Another other suggestions before I try to sell it as a paperweight on Ebay?
Click to expand...
Click to collapse
It depend on if you had TWRP Recovery installed on your tablet. Was this an original setup device or a custom ROM? If it was custom, you should have the necessary files to reinstall from scratch. If you know you do have TWRP Recovery installed (IIRC, it would not show up as an installed app) then to access it you need to push POWER, HOME button (middle front panel)and VOLUME +(up)at the same time! This will get you into recovery mode. Then, you would have to reinstall your custom ROM and gapps from backups. If you don't have these you may still be able to repair it via a Windows PC connection with the right files.
When you post probs you are having, the more info that you include, the better chance you will get a solution for it. I have three smp600 tabs, all configured the same way with multiple backups for each on SD cards as well as Google Drive cloud. So, I can have any tab restored fully in under an hour. Whatever you do, good luck, but it takes a lot to truly "brick" one! ;-DeanoD=
Sent from my SM-P600 using Tapatalk
Thanks. It was running stock Lollipop with no custom recovery. When I was taking the back off to see if a connection was loose I could hear audio but I did not find a loose connection so it's still dead.?
Yesterday I was listening to a podcast when it suddenly stopped and my earbuds disconnected. The phone appeared to be dead - nothing happened when pressing or long-pressing the power button, and the screen would not turn on. After getting home, I found out it's not completely dead because my PC recognizes it if I plug it in. However, some of the settings seem to have been reset since I no longer have ADB access or bluetooth pairings. It seems to be connected to wifi tho.
So... what are my options? I would like to recover what I can from the storage. The only thing I can think to do right now is let the battery run out (it's not like I can turn it off anyway) and see if anything changes.
Stock ROM, T-Mobile version reflashed to International + Magisk 24.3
Well, today I plugged it into my PC, pressed the power button for a few seconds, and it booted up normally. No idea what happened.
I just had a similar thing happen to me as well. One minute everything was working, then bluetooth started being really weird (connecting and then disconnecting). I told the phone to restart and then nothing. Didn't respond to the power button. Finally, I was able to get into Fastboot and then recovery. From there it was then able to restart normally and I haven't had any issues since.