Today, my family was going to celebrate Canada Day. I was running Root-Box *with Halo!* and everything was well. I charged up my phone to 80%. Cleared the necessary caches, resets, and then proceeded to restore to my now 20 day old ViperXL Backup. I restored and booted , everything was working well, but the phone was hot as it always is when i restore a ROM. So i went to go get ready, when i came back i turned the phone on from standby and it didn't respond. I unplugged it and did all button combinations ( volume up and down and power, volume down and power,just power). I did lots of research and I all I could find was that leave it to cool down then charge. So I left it and came back after 3 hours and it was still the same. Another finding from my research was to charge it. Now, when i do it flashes the red led. and thats all. Its supposed to go to solid red after a while but its been 3 hours and still blinking red. I tried to adb things (adb reboot, addb flash recovery <file link here>). But nothing. So now Im here hopefully you guys can help me out. Thanks for reading.
Also, when i plug it into the computer, it detects installs a driver thens stops. It keeps on making connect and disconnect sounds on the computer. Not detected by adb or htc sync manager. I tried all the power cables, stock HTC, apple power block, samsung and even blackberry!
mr.5106411 said:
Also, when i plug it into the computer, it detects installs a driver thens stops. It keeps on making connect and disconnect sounds on the computer. Not detected by adb or htc sync manager. I tried all the power cables, stock HTC, apple power block, samsung and even blackberry!
Click to expand...
Click to collapse
hope it doesn't detect QHSUSB_LOAD when you connect it to your PC...
cr1960 said:
hope it doesn't detect QHSUSB_LOAD when you connect it to your PC...
Click to expand...
Click to collapse
thanks for the reply it connect but disconnects. If you go to device manager it keeps refreshing as it connects and disconnects and then reconnects. When you do however go to human interface devices you see HID interface, and USB input devices. Thanks for replying. I cant get into the bootloader either. Charged it all night and its still the same thing.
mr.5106411 said:
thanks for the reply it connect but disconnects. If you go to device manager it keeps refreshing as it connects and disconnects and then reconnects. When you do however go to human interface devices you see HID interface, and USB input devices. Thanks for replying. I cant get into the bootloader either. Charged it all night and its still the same thing.
Click to expand...
Click to collapse
Have you tried the simulated battery pull?? Just hold down power until captive lights start flashing.. let it keep flashing for I think 10-12 times and release power button.
Sent from my HTC One XL using xda premium
31ken31 said:
Have you tried the simulated battery pull?? Just hold down power until captive lights start flashing.. let it keep flashing for I think 10-12 times and release power button.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I tried all combinations, it wont go to boot loader, it wont do a simulated battery pull it wont re calibrate the chagring mechanism. (vol up + vol down + power).
mr.5106411 said:
I tried all combinations, it wont go to boot loader, it wont do a simulated battery pull it wont re calibrate the chagring mechanism. (vol up + vol down + power).
Click to expand...
Click to collapse
lights wont flash. The only thing that flashes is the red LED. it flashes quickly, not slowly like it does when you put it for charging after its dead (no battery).
mr.5106411 said:
lights wont flash. The only thing that flashes is the red LED. it flashes quickly, not slowly like it does when you put it for charging after its dead (no battery).
Click to expand...
Click to collapse
you got warranty?
mr.5106411 said:
I tried all combinations, it wont go to boot loader, it wont do a simulated battery pull it wont re calibrate the chagring mechanism. (vol up + vol down + power).
Click to expand...
Click to collapse
Stay away from vol up + power. It will put the phone in QHSUSB_LOAD, which nothing good will come from.
You should not be trying "all combinations" just the right one for bootloader. Make sure you are holding vol down, the press power for 5 seconds or so (do the capacitive buttons flash at all if you do that?) release the power button, but do not release the vol down button until the hboot screen comes up. Or of course, you are convinced the phone is still not responsive.
Try this with the charger plugged in and unplugged.
Make sure you charge for several hours on the wall charger, not connected to your computer.
---------- Post added at 09:44 AM ---------- Previous post was at 09:40 AM ----------
cr1960 said:
you got warranty?
Click to expand...
Click to collapse
There have been some cases of the phone becoming suddenly unresponsive like this, apparently due to hardware failure. These reports seem to be getting a bit more common as the phone is getting a bit "older" (over a year).
However, since the OP was just futzing with it (restored a nandroid), I tend to believe its not a hardware failure. And that he can still possibly recover.
But that is just a gut feeling (and maybe being too optimistic).
redpoint73 said:
Stay away from vol up + power. It will put the phone in QHSUSB_LOAD, which nothing good will come from.
You should not be trying "all combinations" just the right one for bootloader. Make sure you are holding vol down, the press power for 5 seconds or so (do the capacitive buttons flash at all if you do that?) release the power button, but do not release the vol down button until the hboot screen comes up. Or of course, you are convinced the phone is still not responsive.
Try this with the charger plugged in and unplugged.
Make sure you charge for several hours on the wall charger, not connected to your computer.
---------- Post added at 09:44 AM ---------- Previous post was at 09:40 AM ----------
There have been some cases of the phone becoming suddenly unresponsive like this, apparently due to hardware failure. These reports seem to be getting a bit more common as the phone is getting a bit "older" (over a year).
However, since the OP was just futzing with it (restored a nandroid), I tend to believe its not a hardware failure. And that he can still possibly recover.
But that is just a gut feeling (and maybe being too optimistic).
Click to expand...
Click to collapse
I tired both of your suggestion but no hboot menu. and my warranty just ended last month. ( any other ideas?
Here is a video showing what happens. I appreciate the help BTW. http://www.youtube.com/watch?v=0lzm5PKlp-E&feature=youtu.be
Related
hey guys,
my phone litteraly wont do anything. i f*ed up some fonts using type fresh, then tried to restore using the odin3 downloader. i accidentally closed it, and now my phone wont boot up/react to any buttons pressed. any help? thanks guys!
had the same problem. i cant figure out how to even get odin working, it says one click but when i hook up it to odin it gives me a message that still doesnt tell me ****. i had to send my phone back for a new one and told them i used easyroot on the market bc i didnt know what it was and it sounded cool but now i know not to ever do that again that it messd up my phone. Praying to god that they dont charge my for anything
You should still be able to enter bootloader mode by turning phone off and holding down up/down vol and pwr simultaneously until boot screen flashes then release power button only
it wont even do that
open odin (use the stock one click version)
with the phone off (remove/reinsert the battery if need be) and not plugged in; hold vol. down and insert the usb cable (keep holding vol. down untill you see the download screen). this should put you into download mode and if you have the right drivers odin should recognize the phone.
I've stuffed my captivate on a few occasions and so far I have been able to use this method to get into download mode and fix it.
it wont do anything at all. it wont power on, show up in adb, anything... and stupid att wont do ANYTHING -_- oh well. any help would be appreciated!
Have any of you offering support to the OP actually had your phone in the described state? I've read a few posts where the phone is seemingly completely dead as the OP describes and no one says they've successfully recovered from that state. All I ever see is the same old button combinations/battery/usb shenanigans and statements of that should work and that the phone is unbrickable. I have personally seen a device that was behaving in such a manner and no combination of battery pulling, usb plugging, button holding, or tongue twisting would generate anything from the phone. The only thing the phone would do was get hot.
same here. Phone showed bright green screen...wasnt done with teh flash and said it was finished...now the nly thing I can get is power and hold the vlume up for some IRQ and hex stuff. I posted a questionthis morning but...serious. Vol up and down and any things else gives nothign but a black screen..battery out...back in anything..its torched.
Have you tried getting into download mode via the sdk?
Sent from my SAMSUNG-SGH-I897 using XDA App
daveshih said:
Have you tried getting into download mode via the sdk?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
when i plug it in, windows doesnt make any noises and doesnt recognize it, and when i use the "adb devices" command, nothing shows up.
daveshih said:
Have you tried getting into download mode via the sdk?
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Did you read the rest of the posts? The OP already stated several times that the phone does nothing. I realize that most people will say it does nothing or is "bricked" if it simply shows the "connect to computer" screen, but the OP has stated more than once that the phone shows nothing. Yes, everyone is trying to help, but simply repeating what has been said numerous times before doesn't help.
Has anyone actually recovered a phone that displays NOTHING? No logos, no recovery, no nothing.
Last night, i turned off the light in my room when i noticed a glowing from my desk. i walked over, and it turns out my captivate's screen was in fact on, it was just a faint black glow, and none of the power buttons would do anything. when i took the battery out, it shut off completely!
As I pointed out here
http://forum.xda-developers.com/showthread.php?t=757293
Im pretty sure it was my fault for not completely following instructions on the ext4 one click install root, settings.db etc so everyone needs to make sure if the dev says flash before..do it.
State of the phone was, it would not completely power on..therefor no usb drivers would load and Odin cannot see the phone and it can no longer flash..the only thing I could get it to do was show a screen with that text. I put in my post. I ordered it via letstalk.com so I sent it back and assuming they get the same result Ill have a new one hopefully by the end of the week. Im just glad I stil had my old iphone3 to slap my sim card in.
The odin one click flash thing..it just flaked right at the start it looked like..but I cant be sure because as soon as I saw a blue progress bar I stepped into the kitchen for abtou 30 sec..I came back and the screen was florescent green and Odin said it was done. I knew something was wrong as it was way too fast so I unplugged, removed the battery and set it back in...from there on out it would do nothing with the power button unless on a semi rare occasion if I hit the volume up button and power I got the IRQ stuff.
Annoying as I had a nandroid backup just before I started messing with it.
i just sent mine into samsung... back to mah ol trusty blackjack. gonna have to get used to supermario bros 3 instead of spyro....
ANYWAYS theyre sending me a new one!
uiskibum said:
open odin (use the stock one click version)
with the phone off (remove/reinsert the battery if need be) and not plugged in; hold vol. down and insert the usb cable (keep holding vol. down untill you see the download screen). this should put you into download mode and if you have the right drivers odin should recognize the phone.
I've stuffed my captivate on a few occasions and so far I have been able to use this method to get into download mode and fix it.
Click to expand...
Click to collapse
So, yes in same state as op... no nothing... couldn't get jack out of it. at all, none
what this post said worked.... not holding power button... nothign...
removed battery
plugged in battery
hold vol down
(still no response)
plug in usb cable and continue holding vol down.
it went to recovery mode
... no holding of power button, just vol down and plugged in USB... give it a shot man, let me know
EDIT: feel free to PM me if you want me to help walk you through it...
ace518 said:
So, yes in same state as op... no nothing... couldn't get jack out of it. at all, none
what this post said worked.... not holding power button... nothign...
removed battery
plugged in battery
hold vol down
(still no response)
plug in usb cable and continue holding vol down.
it went to recovery mode
... no holding of power button, just vol down and plugged in USB... give it a shot man, let me know
EDIT: feel free to PM me if you want me to help walk you through it...
Click to expand...
Click to collapse
Hey thanks, but i already sent it to em... thank you everyone for your help!
Just a note... i said before hold vol down and plug in usb. I had it in a pretty bad state tonight. Played around. Same idea as before, but had to hold vol up and vol down. If i brick a few more times, i'll give a better guide. But this phone can DEFINITELY come back from a state where you can't even get it to power on. Figured any additional info on this would be good.
I just got this device Ran the NvFlash and oneclick root All was working fine I went to grab a drink came back phone was off now wont turn on period full battery i try to run NvFlash over top again I can hear the computer find the phone when i hold vol up and Down but it gets stuck at waiting for bootloader to INT please help and is this bricked being i can hear the sound when the i hold vol up and down and plug it in the laptop??
nucentury08 said:
I just got this device Ran the NvFlash and oneclick root All was working fine I went to grab a drink came back phone was off now wont turn on period full battery i try to run NvFlash over top again I can hear the computer find the phone when i hold vol up and Down but it gets stuck at waiting for bootloader to INT please help and is this bricked being i can hear the sound when the i hold vol up and down and plug it in the laptop??
Click to expand...
Click to collapse
Sounds BRICKED!!! No Bootloader? Ouch. Do you have a jtag rig? If not or if you dont know what one is id say take it back to t-mobile.
Jtag??? whats that
nucentury08 said:
Jtag??? whats that
Click to expand...
Click to collapse
If you don't know what it is you don't have one, and more than likely won't know how to use one... have you tried keeping the battery out for a bit (2-3 minutes), I had a minor issue that when I tried booting NVFlash and install recovery, after pulling the battery and replacing it within a second my phone wouldn't boot
nucentury08 said:
I just got this device Ran the NvFlash and oneclick root All was working fine I went to grab a drink came back phone was off now wont turn on period full battery i try to run NvFlash over top again I can hear the computer find the phone when i hold vol up and Down but it gets stuck at waiting for bootloader to INT please help and is this bricked being i can hear the sound when the i hold vol up and down and plug it in the laptop??
Click to expand...
Click to collapse
Not to worry -- this happens occasionally. Just try turning it on normally (don't hold vol up + down, just hit power) with the phone plugged-in without the battery, plugged-in with the battery, unplugged with the battery...lather, wash, repeat.
It will work eventually. Not sure what causes the issue, but I've had two of these phones so far and both had this issue.
ok
Erislover said:
Not to worry -- this happens occasionally. Just try turning it on normally (don't hold vol up + down, just hit power) with the phone plugged-in without the battery, plugged-in with the battery, unplugged with the battery...lather, wash, repeat.
It will work eventually. Not sure what causes the issue, but I've had two of these phones so far and both had this issue.
Click to expand...
Click to collapse
i dont know why it is doing this anyway ??
Yeah just keep trying remove and replace the battery a couple of times or even more than just a couple of times. I had to do this but it eventually turned back on.
Hey guys,
I got an infuse from a friend. When she gave it to me it was all stock and functional minus the fact that it would bootloop. When you would turn it on it would show samsung, turn off, samsung, turn off... About 3 seconds per on time. It would do this whenever it had the battery in or was plugged in. At first I was able to get it into download and then flash stock OEM. This fixed the problem, then I got into recovery and flashed a custom rom. All of this worked fine. Here's the problem
I tried restoring to the stock that I got the phone to before the custom rom was installed. This took 25 seconds and I knew something must have been wrong but I rebooted anyway. When rebooting I was faced with my original issues up above. Unfortunately its rebooting too quickly to put it into download mod. By the time I press the volume buttons and insert the usb it already boots and then starts over. If I do it quickly enough it goes to charge and bootloops to charge. The problem is that the phone bootloops whenever the battery is in. I don't have to press power for it to start.
Pretty frustrated and really would like some help. Thanks
EDIT: I ****ING FIXED IT!!! I swear this isn't a joke... I was reading a forum that had this problem and they all were saying they got angry and threw it/hit their phone and it booted up. Sitting there I eventually started entertaining the idea. I did a quick survey of the library I am in and... smacked it on my fist. THEN THE ****ING THING BOOTED UP!! What the hell!! SO excited. If it happens again, most efficient way is to drop the device on the top off the phone on a carpeted floor from about 2 feet
Faulty power button. Do a search.
Sent from my SGH-I997 using xda premium
Los maizak
psal217050 said:
Faulty power button. Do a search.
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
Am I looking for a replacement or what? Thanks for the speedy reply
psal may be on to something however it sounds like you are not trying download mode correctly - if you had the battery pulled and the usb disconnected it could not be rebooting.
Edit: If the power button is sticking, most likely no need to replace- here is a video of how to replace the screen, not what you are doing but the point is it shows how to take the phone apart so that you can clean the power button. Hope this helps : http://www.youtube.com/watch?v=1WS5I0SpL6c
Pony Express said:
psal may be on to something however it sounds like you are not trying download mode correctly - if you had the battery pulled and the usb disconnected it could no t be rebooting.
Click to expand...
Click to collapse
It reboots only when I put the battery in. So the moment I put the battery in to try and get it into recovery it starts booting immediately. It doesn't give me enough time to actually press volume up and down and then insert usb. If i do it fast enough it just boots to charging mode and boot loops to that instead of the samsung splash
Edit: I have already taken apart the phone. Not really sure what I should clean. It looks completely fine and acts similarly to the volume buttons. How would you recommend I clean it?
Pony Express said:
psal may be on to something however it sounds like you are not trying download mode correctly - if you had the battery pulled and the usb disconnected it could not be rebooting.
Edit: If the power button is sticking, most likely no need to replace- here is a video of how to replace the screen, not what you are doing but the point is it shows how to take the phone apart so that you can clean the power button. Hope this helps : http://www.youtube.com/watch?v=1WS5I0SpL6c
Click to expand...
Click to collapse
I am not so sure that this is a hardware issue. Why would the problem disappear when I flash the OEM but then return everytime I restore to the faulty stock. I already took apart and the power button seems pristine.
With this extra info, it is pointing more toward a sticking power button with a hardware issue still something to consider... have you tried pulling battery, install usb, hold both volume buttons (no power button) and while continuing to hold vol buttons insert the battery ?
Edit: If the issue is indeed in the faulty rom, delete it and use something different.
Pony Express said:
With this extra info, it is pointing more toward a sticking power button with a hardware issue still something to consider... have you tried pulling battery, install usb, hold both volume buttons (no power button) and while continuing to hold vol buttons insert the battery ?
Edit: If the issue is indeed in the faulty rom, delete it and use something different.
Click to expand...
Click to collapse
Not sure how I would delete the rom because I cannot boot the phone, boot to recovery, or boot to download. I did try having the usb in, holding volume and then putting in battery. It didn't work. Do you think a jig would work? Thanks
Yes, I think for such a small price it is worth a shot- best of luck !!
It would also be worth mentioning to be certain you have a good usb cable as well as a good usb port on the puter.
aeppacher said:
Hey guys,
I got an infuse from a friend. When she gave it to me it was all stock and functional minus the fact that it would bootloop. When you would turn it on it would show samsung, turn off, samsung, turn off... About 3 seconds per on time. It would do this whenever it had the battery in or was plugged in. At first I was able to get it into download and then flash stock OEM. This fixed the problem, then I got into recovery and flashed a custom rom. All of this worked fine. Here's the problem
I tried restoring to the stock that I got the phone to before the custom rom was installed. This took 25 seconds and I knew something must have been wrong but I rebooted anyway. When rebooting I was faced with my original issues up above. Unfortunately its rebooting too quickly to put it into download mod. By the time I press the volume buttons and insert the usb it already boots and then starts over. If I do it quickly enough it goes to charge and bootloops to charge. The problem is that the phone bootloops whenever the battery is in. I don't have to press power for it to start.
Pretty frustrated and really would like some help. Thanks
Click to expand...
Click to collapse
Use this to go to stock old version:
http://forum.xda-developers.com/showthread.php?t=1116251
Then open kies mini connect your phone on kies update and upgrade to the newest GB version.
At this point u are on a stock if u want root try this:
http://forum.xda-developers.com/showthread.php?t=1613523
Option C is the better
daemonlmrj said:
Use this to go to stock old version:
http://forum.xda-developers.com/showthread.php?t=1116251
Then open kies mini connect your phone on kies update and upgrade to the newest GB version.
At this point u are on a stock if u want root try this:
http://forum.xda-developers.com/showthread.php?t=1613523
Option C is the better
Click to expand...
Click to collapse
I can't do this because in order to go to download mode the phone needs to be off. The moment I insert the battery it automatically starts bootlooping
Pony and psal are prolly right. Try fixing your power button.
Hey guys this is my first time posting.
I've rooted my One X loaded up a ROM (AT&T made sure it was right), was logging into Google, then my phone went black (it's connected to the computer) and it was making a sound like when you plug in a usb drive, then after a few minutes it stopped. The phone is not doing anything, can't turn it off or on. Tried to do a hard reset (volume down + power button for 30 seconds) that did nothing. Tried connecting my phone to Ubuntu and it did nothing. Any ideas?
Thanks,
Matt
Which Rom and were you low on battery?
omario8484 said:
Which Rom and were you low on battery?
Click to expand...
Click to collapse
ROM was this "Calkulin's_One_XL_ROM_v1.2" the battery was at 85
Try leaving in wall charger for. A while...did you recently get it wet or any other hardware failure?
Any charge light if you plug it into the wall charger?
---------- Post added at 02:42 PM ---------- Previous post was at 02:39 PM ----------
matt.j.roell said:
Tried to do a hard reset (volume down + power button for 30 seconds) that did nothing.
Click to expand...
Click to collapse
That is (mostly) how you get into hboot, not hard reset (is no button combo to reset the phone, per se).
You only need to hold the power button for about 5 seconds. Then release power only, keep holding volume down, and see if the white hboot screen comes up.
omario8484 said:
Try leaving in wall charger for. A while...did you recently get it wet or any other hardware failure?
Click to expand...
Click to collapse
I left it plugged in for a few hours and the charge light would not come on, and no hardware failure or was it wet.
Were you using a different companies charger? I've seen people brick from use of diff charger and try holding just power for 30 seconds and see if your key lights blink
omario8484 said:
Were you using a different companies charger? I've seen people brick from use of diff charger and try holding just power for 30 seconds and see if your key lights blink
Click to expand...
Click to collapse
The charger is from HTC I've tried holding down the power button for 30 seconds, when I do connect it to the computer it's trying to connect as a HID device but the computer stops trying to install the driver after a few minutes.
redpoint73 said:
Any charge light if you plug it into the wall charger?
---------- Post added at 02:42 PM ---------- Previous post was at 02:39 PM ----------
That is (mostly) how you get into hboot, not hard reset (is no button combo to reset the phone, per se).
You only need to hold the power button for about 5 seconds. Then release power only, keep holding volume down, and see if the white hboot screen comes up.
Click to expand...
Click to collapse
No charge light, or any combination of power and or volume button holding is working.
Its not looking so good. If the phone was left on wall charger for a few hours, and no charge light, you are probably screwed. You might look into the unbricking thread in General, since you have a Linux computer.
The fact it went dark after flashing a ROM is suspicious. I wouldn't think it would boot at all if you flashed something that corrupted hboot (like ROM for the international One X). But the timing is awful suspicious. What ROM did you flash?
redpoint73 said:
Its not looking so good. If the phone was left on wall charger for a few hours, and no charge light, you are probably screwed. You might look into the unbricking thread in General, since you have a Linux computer.
The fact it went dark after flashing a ROM is suspicious. I wouldn't think it would boot at all if you flashed something that corrupted hboot (like ROM for the international One X). But the timing is awful suspicious. What ROM did you flash?
Click to expand...
Click to collapse
Good news, I plugged it into the charger and held down the power button, the charge light went to blinking red, then pressed the power button and it went solid. I then was able to get it into bootloader. It was very odd, the batter is at 94%, not sure what was going on, I think it was a bad ROM. I'm going to flash it and see what happens.
matt.j.roell said:
Good news, I plugged it into the charger and held down the power button, the charge light went to blinking red, then pressed the power button and it went solid. I then was able to get it into bootloader. It was very odd, the batter is at 94%, not sure what was going on, I think it was a bad ROM. I'm going to flash it and see what happens.
Click to expand...
Click to collapse
This happened to me awhile back. However, I wasn't rooted. I was complete stock. Just left it on the wall charger for an hour, held power button for about 30 econds or so and it deicided it wanted to work again. I was also on 2.20.
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
devmage said:
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
Click to expand...
Click to collapse
Well the good news is that you aren't bricked, if the phone gives any signs of life then you are not bricked. Have you always installed SuperSu updates through recovery? I always select I believe it says "normal" and let it do it's thing and until now (knock on wood) haven't had any issues updating binaries that way. I would go back to stock and see if your problems continue or flash the previous SuperSu and see if it still happens.
devmage said:
HTC One M8, S-Off, Skyfall latest on 4.4.4, stock kernel, TWRP 2.8.1.0. Have been running Skyfall latest since a few days after its release, and TWRP 2.8.1.0 similarly. No problems to report so far.
I was using my phone today as one would, browsing Facebook through the app, and my phone freezes. Screen goes black, power off. Phone was probably at 80-85% battery when this happened.
I am no stranger to freezes and hard reboots, so I expected the phone to come back up shortly after this. It did not.
Tried to reboot via ADB. Couldn't detect the device.
Tried to reboot into recovery by holding Vol Down and Power. No response.
Tried to reboot into a soft reset by holding Vol Up and Power. No response.
Tried to force a battery recalibration by plugging in the phone to a charger* and holding Vol Up, Vol Down, and Power for two minutes. No response. (*the charger was not the stock HTC charger, as I don't presently have access to that, but was rather a generic charger rated for [email protected])
Somehow, miraculously, after leaving the phone plugged in for a few minutes more and fumbling a bit with (I think) the Power and Vol Up, the phone powered on, rebooted twice, and then entered the OS normally. Was stable for what seemed like about 5 minutes. After receiving a few text messages and in the middle of responding to one, it froze and powered off as before.
Last system-level tweaking that I did was to accept the latest SuperSU upgrade a few days ago. That needed to reboot into recovery, install a zip, and reboot again. All appeared to work correctly, and phone booted back up afterwards without issue. Appeared to be stable until today. I'm not blaming the SuperSU update just yet, and it seems an unlikely culprit given that the phone booted back up without issue and was stable for several days following.
Thoughts? Would greatly appreciate any troubleshooting ideas beyond these.
Update 1: After leaving it plugged in for a few minutes, I tried the battery calibration approach again. The device powered on and showed the initial boot splash (the one with the development notice in ugly red). I then released all buttons, and after a few seconds the screen went black. Would not respond afterwards. Beginning to suspect this may be a power issue.
Click to expand...
Click to collapse
Make sure you aren't trying to power it on while still plugged in. The charging animation bug really rears its ugly head sometimes when trying to do that.
The Stig 04 said:
Well the good news is that you aren't bricked, if the phone gives any signs of life then you are not bricked. Have you always installed SuperSu updates through recovery? I always select I believe it says "normal" and let it do it's thing and until now (knock on wood) haven't had any issues updating binaries that way. I would go back to stock and see if your problems continue or flash the previous SuperSu and see if it still happens.
Click to expand...
Click to collapse
I would love to go back to stock if I could get the device to turn on.
This was the first SuperSU update that I can remember having installed, so yes, I've always installed through recovery. The update even prompted me that, for HTC devices, better luck is had via updates through recovery.
dottat said:
Make sure you aren't trying to power it on while still plugged in. The charging animation bug really rears its ugly head sometimes when trying to do that.
Click to expand...
Click to collapse
I'm unaware of this bug. When disconnected, the device still refuses to reboot via any of the usual reboot patterns (Power, Power + Vol Up, Power + Vol Down, Power + both Vols).
devmage said:
I'm unaware of this bug. When disconnected, the device still refuses to reboot via any of the usual reboot patterns (Power, Power + Vol Up, Power + Vol Down, Power + both Vols).
Click to expand...
Click to collapse
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
dottat said:
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
Click to expand...
Click to collapse
Power light does not blink at all on connection. This is true both when connecting to a USB power adapter and to the computer.
My computer does not recognize a device. ADB does not report that a device is connected. Also, I use a Mac, so System Information does not report any USB device being connected. For comparison, I tried with my wife's Samsung S5, and it reported correctly in both places, so I know the cable and computer are working correctly here too.
devmage said:
Power light does not blink at all on connection. This is true both when connecting to a USB power adapter and to the computer.
My computer does not recognize a device. ADB does not report that a device is connected. Also, I use a Mac, so System Information does not report any USB device being connected. For comparison, I tried with my wife's Samsung S5, and it reported correctly in both places, so I know the cable and computer are working correctly here too.
Click to expand...
Click to collapse
Can you check dmesg on your Mac and see if you have any qualcomm devices show up near the end of the file? . Plug the phone in right before running the command.
dottat said:
Can you check dmesg on your Mac and see if you have any qualcomm devices show up near the end of the file? . Plug the phone in right before running the command.
Click to expand...
Click to collapse
Nothing from Qualcomm, nor anything related, upon plugging in the phone.
Using
Code:
sudo watch 'dmesg | tail -n 15'
(OS X requires dmesg be accessed with sudo), I saw the following come up upon plugging in the S5 mentioned before:
Code:
USBMSC Identifier (non-unique): 0x00000000 0x4e8 0x685b 0x232, 2
With the same watch in place, I saw no output at all for the M8.
devmage said:
Nothing from Qualcomm, nor anything related, upon plugging in the phone.
Using
Code:
sudo watch 'dmesg | tail -n 15'
(OS X requires dmesg be accessed with sudo), I saw the following come up upon plugging in the S5 mentioned before:
Code:
USBMSC Identifier (non-unique): 0x00000000 0x4e8 0x685b 0x232, 2
With the same watch in place, I saw no output at all for the M8.
Click to expand...
Click to collapse
I would suggest warranty route through HTC. You have got a brick.
dottat said:
I would suggest warranty route through HTC. You have got a brick.
Click to expand...
Click to collapse
That is my fear. Thank you for your help.
dottat said:
OK. So couple more questions....
Does the power light blink for a second and then go out when you connect power or does it stay on?
What type of device does your computer see the phone as when you connect it? Please try if you have not. Watch device manager while doing so.
Click to expand...
Click to collapse
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
TIA for any help!
Matt
sigmaxaa said:
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
Thanks TIA for any help!
Matt
Click to expand...
Click to collapse
I'm afraid that I won't be of much help going forward. I sent in the device on a warranty claim.
I will add that, in the day or so following my posts here, I plugged the phone in again and to my surprise it began taking a charge again. I let it charge for about an hour, and tried turning it on - remarkably, it came up normally. It was stable for about an hour more, and then froze and powered off as before, refusing to once again turn on.
I left it alone for another couple of days, during which time my replacement arrived, and tried again. It began taking charge, and I left it as such for a couple hours more. This time knowing that my stable time was limited, and with a replacement phone in hand, I immediately restored the phone to RUU stock and locked it.
Your problem seems different from mine, in that my device was outright refusing to even take power or turn on. Best of luck to you, though!
Thanks for the info...I appreciate the response. I'm hoping that there's something that can be done but after 2 hours, trying every trick I could find via
Google with nothing to show for it, I'm keeping fingers crossed that it's something simple I'm missing. If I could just get into the dang bootloader!
Thanks again!
Sent from my SM-P600 using XDA Free mobile app
---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------
sigmaxaa said:
Hi,
Background: Rooted, S-Off (via Sunshine), was running CleanROM (on the 444 firmware) and tried installing Vanir 444. ROM installed no problem, Gapps installed no problem, installed SuperSU 2.40 at the end and rebooted.
I've run into the exact same situation as the OP. Tried all the button combinations/adb stuff and the phone only boots to the initial white HTC screen but then goes blank. I've tried everything to get into bootloader but nothing seems to get me there. The phone vibrates when it "turns on" after the hard reset but nothing after the white HTC screen except a black screen.
I'm responding to this post in particular because my phone was/is showing the blinking power light when it's plugged in. Hopefully this is a good sign?
TIA for any help!
Matt
Click to expand...
Click to collapse
To add to this, I've let the phone sit for about an hour, untouched, and now the green light is blinking like it does when there's a SMS/email. Pushing the power button doesn't do anything.
devmage said:
I'm afraid that I won't be of much help going forward. I sent in the device on a warranty claim.
I will add that, in the day or so following my posts here, I plugged the phone in again and to my surprise it began taking a charge again. I let it charge for about an hour, and tried turning it on - remarkably, it came up normally. It was stable for about an hour more, and then froze and powered off as before, refusing to once again turn on.
I left it alone for another couple of days, during which time my replacement arrived, and tried again. It began taking charge, and I left it as such for a couple hours more. This time knowing that my stable time was limited, and with a replacement phone in hand, I immediately restored the phone to RUU stock and locked it.
Your problem seems different from mine, in that my device was outright refusing to even take power or turn on. Best of luck to you, though!
Click to expand...
Click to collapse
For what it's worth for anyone that finds this info useful...can't take credit for this as I found it over in the One M8 forum. Thanks to @mpogr
I quote his post: "The problem was that my phone's screen was going blank after the normal boot screen, so I couldn't see when it gets turned off. I was simply pressing the Vol Up + Power for too long, so it would go into full reboot. I just measured the amount of time it was taking to do this (was ~12 seconds). So I pressed Vol Up + Power for ~10 secs, then released those and pressed Vol Down. That finally brought me into Fastboot.
I could have probably gotten the same result by pressing Vol Down + Power, however, the phone screen was blank all the time, so it was difficult to understand when I should have released the Power button to let it go into Fastboot."
I held Power/Vol Up for 10 seconds (as he described) and then let go and immediately held Vol Down only...after about 3 seconds, bootloader screen came up and I was able to get into recovery and restore a backup.