Database Info

[Q] Symptoms of a bricked phone? (related to all skyrocket users)

background info:
I am (or was) running MHX superlite 3.0 rom with romracers stockish 0.3 kernel.
UCLA3 modem and radio.
So today my phone decides to restart itself and never will load past the "first two"
samsung screens.
Once these "two" samsung logos pass by, the screen turns blank (not on)
and starts to vibrate with 1 second intervals.
The only way for it to stop is if I pull the battery.
Heres the weird part.
I tried to ODIN back to stock...once I put my phone into DOWNLOAD MODE.
The little android guy that says DOWNLOADING "dont turn off" will show for a millisecond and then the screen will shut off and start the vibrations. ODIN will not recognize the device either
So what I have is a phone that wont load past the samsung logos if the power button is pressed
AND
Download mode works, but the screen will turn blank and vibrations start buzzing.
My phone is having seizures. The only way to stop the vibrations is by pulling the battery.
I have accepted the fact that the phone may be done for.
It was a great 4 months together. tear*

Well, if you can't get it sorted out there's always this! Unless the hardware is busted, but maybe he can fix that too??
http://www.youtube.com/watch?v=AkJQAbwZjRk

Did you try booting into recovery mode instead of odin?

Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.

silver03wrx said:
Is that an overclock kernel? If so sounds like may be set to high. And did u choose set on boot.
Click to expand...
Click to collapse
No, its not. Can't OC or UV. It can only UC.
Sent from SKYROCKET
NexusMod 4.0
Romracer 0.3

if u can boot into cwm flash darkside

OP... what rom/kernel/modem were you running before MHX-SuperLite? and what wipe process did you use prior to MHX flash?

Can you get into recovery and restore a backup?
If you don't have a backup and can get into recovery, try wiping data/cache, then go into mounts/storage and format system, data, and cache, then go to advanced and wipe Dalvic cache. Then power down and try to Odin back to stock again.
If this doesn't work, try another data cable or usb port on your machine (or another pc if this doesn't work). Maybe communication is getting lost due to bad usb connection...
EDIT: Are you saying you tried to Odin even though Odin wasn't recognizing your phone? That could be part of the problem. Try re-installing the Samsung drivers and see if Odin sees it then.
If you can get into download mode you aren't hard bricked yet...

I think he is saying that Odin recognizes his phone but his phone goes black before he can't start the reflash right?
Sent from my SAMSUNG-SGH-I727

Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.

Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts

DoctorQMM said:
Did we lose the OP'r? I was just getting ready to flash this ROM (MHX) but Jooosty has thrown up a curveball. Hope you get it resolved.
Click to expand...
Click to collapse
MHX is great. The rom has nothing to do with it i believe

Jooosty said:
Okay sorry for late response.
But i was running skyice speed before hand.
Ive only used CWM to wipe data.
No OC or UV on this kernel.
Cant get into cwm or recovery. The screen turns blank before i can do anything at all.
Ive concluded its most likely a internal hardware failure maybe...
Going to try to sell for parts
Click to expand...
Click to collapse
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!

skrambled said:
I wouldn't give up just yet. I have never seen an instance of a hard brick where you could get into download mode. Try using Odin from another machine (preferably not a laptop).
If it's internal hardware failure then you have a defective product that is covered under warranty. Call support and get them to replace it (as a last resort of course--I honestly think you'll be able to get Odin to work if the drivers are properly installed and you have a solid usb connection).
EDIT: If you insist on selling it, please pm me so I can make an offer!
Click to expand...
Click to collapse
He already said Odin/connection isn't the problem. His phone won't stay on long enough for the communication to be made. According to what he said, it has nothing to do with machine/drivers/cable. He needs a way of keep the phone on long enough to make the connection, or somehow communicate with it another way. Unfortunately, I have no ideas. Although, I really hope someone does. That RussianBear guy seems to be onto something with communicating with the emmc without the phone being on... or something like that.

heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/

Jooosty said:
heres a link to a video update!
http://imageshack.us/photo/my-images/254/oww.mp4/
Click to expand...
Click to collapse
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.

plwalsh88 said:
Man that is so weird. Random, but have you tried leaving it plugged in and charging for a few hours? Haha I just can't think of anything else.
Click to expand...
Click to collapse
Or even a external battery charger maybe there is just enough juice to turn on and then dies
Sent from my SAMSUNG-SGH-I727

The battery is fine. Wouldnt keep rebooting if otherwise. O well.
Just bought a captivate to feed my android in me
Sent from my SAMSUNG-SGH-I897 using XDA

DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litmus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....

xtechx said:
DUDE!!!! mine just started doing the EXACT same issue....SOB....
no cwm, no download, just reboots...i acn see cwm lettering for like 0.1ms then it reboots, and reboots every second...download mode, as soon as I choose continue, it goes into reboot loop.....
this is exactly what happened when it happened to my phone......
I went to hit the power button to lock the screen, was listening ot music on power amp. instead of screen locking, the power menu came up...hit back, and tried ot lock screen again? screen went black, 2 vibrates back to back....then saw sgh-i727r boot logo, then black and 1 second vibrate intervals.....
got it sitting in rice right now in case it got wet...battery litinus paper is good...only thing it may have gotten warm today, was working outside and it was 26° celcius....
I did drop it about 1.5 months ago and changed my screen about 3 weeks ago...unfortunately I broke the old lcd when removing the screen, I guess I didn't heat the glue enough...so I can't pop it back in and test to see if related...
I may take apart my phone in a bit and see if any liquid has leaked in...but I didn't get wet....
i think i'm going to order a gt-i9100 again, as I miss that phone.....
Click to expand...
Click to collapse
What ROM were you on man?
Sent from SKYROCKET
NexusMod 4.0
Faux 010m

HTC One S shuts down and won't turn on, no charging led.

Hi,
yesterday I pulled my One S out of my pocket, opened up the browser, made a search on google and all of a sudden, while the page was loading the screen turned off, completely black. The capacitive buttons stayed awake for 4-5 seconds, then they turned off too.
Completely dead, the phone won't turn on anymore, not even in recovery mode. If I connect the wall charger the charging led doesn't light up, although I can feel the phone is heating (as usually happens when charging).
I've tried connecting it to the pc via usb and windows after a while, detects a peripheral named "qhsusb_dload". I've read on google that this isn't any good... Anyway, even connected to the pc (for hours) the charging led doesn't light up.
No signs of life from my One S... :crying:
The phone is completely stock, unrooted.
Do someone have any hints?
Thanks.

I believe you're in download mode.
Hold the power button until your button leds start flashing and then keep holding it until they stop again. Now let go. If they don't start flashing within (say) 20 seconds, you can also let go. Hold the vol-down button and press&release the power button. Hopefully this boots you into bootloader mode. If not I don't nkow what else to suggest other than look at the unbricking thread in the development forum.

There's no way I can enter bootloader. The phone shows no signs of life (no capacitive buttons, no charging led, nothing at all)...
One thing that maybe is important: for about a month, I've been experiencing a strange battery drain. The drain used to occur even if the phone was in deep sleep (I'm sure about this because I've checked with cpuspy and anyway I hadn't installed any new apps for quite a while), at a rate of 7-8% each hour. I could leave the phone on the desk with screen off and in standby (no 3g data, no wifi, not even cellular network) and the drain was still there.
By the way, when my phone died I had plenty of battery left, about 70%.

nor-ric said:
The phone is completely stock, unrooted.
Do someone have any hints?
Thanks.
Click to expand...
Click to collapse
If it's unrooted then your warranty is still 100% intact and HTC will replace your phone no problem. What you describe just happens sometimes, more so with this phone then others I've seen.
The qhsusb_dload means it's not worth tinkering with yourself if you can just submit it for warranty.

dc211 said:
If it's unrooted then your warranty is still 100% intact and HTC will replace your phone no problem. What you describe just happens sometimes, more so with this phone then others I've seen.
The qhsusb_dload means it's not worth tinkering with yourself if you can just submit it for warranty.
Click to expand...
Click to collapse
I see, thanks. Is this qhsusb-dload issue hardware-related? If so, is it possible that they swap my S4 chip with an S3?

nor-ric said:
I see, thanks. Is this qhsusb-dload issue hardware-related? If so, is it possible that they swap my S4 chip with an S3?
Click to expand...
Click to collapse
Think of qhsusb-dload kinda like your normal PC without windows. Your phone could not find an operating system to boot into and defaulted to qhsusb-dload mode waiting for a command. Our problem is that we don't really know the commands for qhsusb-dload nor do we have the files needed to use it only the manufactures do.
They can't swap a s4 chip for a S3 version that isn't the same product.

Most likely it the micro USB charging port that's gone toast.. happened to mine exact same symptoms. I was actually unlocked, HTC dev unlocked too, running a custom ROM as well as custom recovery and splash screen. I still sent it in repair with hope of they will never be able to turn the damn thing on to discover my deeds and will replace my phone but they didn't mind, they reflashed stock rom after repair and sent it back but I was still s-off
Send it into repair mate. Best option instead of tinkering with it lol
Sent from my HTC Sensation using xda premium

Nope, there is a solution.
http://unlimited.io/qhsusbdload.htm
Sent from my HTC One S+

Ok, thanks everybody.
I'm going to try usaff22's method and if that doesn't work I'll send the phone in.
I'll let you know! :fingers-crossed:

It didn't work. The terminal waits for the device, however it doesn't respond...
I'll have to send the phone in.

Crazy idea but that sounds like the mode you go into for the downgrade so maybe the last part of it might help to get you up and running again.

Darknites said:
Crazy idea but that sounds like the mode you go into for the downgrade so maybe the last part of it might help to get you up and running again.
Click to expand...
Click to collapse
Where can I find the guide you're referring to?
Thanks.

nor-ric said:
Where can I find the guide you're referring to?
Thanks.
Click to expand...
Click to collapse
Here you go, Downgrade/Unbrick.

Darknites said:
Here you go, Downgrade/Unbrick.
Click to expand...
Click to collapse
I've read that thread: do you mean I should try the 9th point?
you can open a new terminal window and run the following command IF AND ONLY IF the phone doesn't reset out of QDL mode
Code:
$ sudo ./emmc_recover -r
Click to expand...
Click to collapse

nor-ric said:
I've read that thread: do you mean I should try the 9th point?
Click to expand...
Click to collapse
No that for flashing Hboot think you want step 12 but will need to edit the file the download has but you will need to do step 3 so you can do step 12. I have no idea if it will work but its an idea and also might be best to ask about it there too before doing anything.

thanks a lot touch of jobo i was going to get crazy :laugh:

touch of jobo said:
I believe you're in download mode.
Hold the power button until your button leds start flashing and then keep holding it until they stop again. Now let go. If they don't start flashing within (say) 20 seconds, you can also let go. Hold the vol-down button and press&release the power button. Hopefully this boots you into bootloader mode. If not I don't nkow what else to suggest other than look at the unbricking thread in the development forum.
Click to expand...
Click to collapse
that worked for me. thanks a lot
btw. maybe someone can answer this: how come that the phone goes in download mode?! I had the phone unused the last hours before I recognized it wasn't on anymore? Does this just happen? I am on CM11 Nightlies atm.

[Q] Help? Bricked One X?

I think I bricked my one X im not sure how or why but out of the blue it just said the 10 second power off message and no longer turns on at first i was able to turn it on a few more times but now i cant.
It is not taking charge both from my computer or ac :/
when i plug it into my computer it says HID compliant device found. and the three led buttons light up every about 5-10 seconds but the top led notification doesnt turn on
If it matters
Hboot 1.14
on jokerfg jb rom
also this is a week and a half old device. if i have to replace it i will but I am more concerned with formatting it or getting it to stock before hand incase i send it in and they get it running

Uff. I have not encountered this issue. Sorry brother. Update if you find a fix.
Sent from my HTC One X+ using xda app-developers app

How did it get to that state?
What are the 5 contact looking things at the back of the phone for?
Sounds like you need to give the thing some charge, i'm sure one of those street corner shops can pop it open, macgyver some volts in, and reflash something that will boot for $30ish?

I'm not really sure, my power buttton is stuck but it retracts like a button should, but it has died and refuses to power up now. I just wanna turn it on to reformat it. or is it possible htc wont be able to turn it on themselves and when they receive it just trash the device?
gururug said:
How did it get to that state?
What are the 5 contact looking things at the back of the phone for?
Sounds like you need to give the thing some charge, i'm sure one of those street corner shops can pop it open, macgyver some volts in, and reflash something that will boot for $30ish?
Click to expand...
Click to collapse

so the battery is dead and it wont charge? if it will charge youll have to relock the boatloader and ruu to stock if u cant get in to recovery

Leave the phone on the wall charger (not USB) for several hours (overnight) and see if you can boot. You might also try to power on, or hold the power button, or try to enter hboot while the phone is plugged to the charger (after letting it charge for several hours). As at least one guy that I thought was hard bricked got his phone to boot this way.
What appears like spontaneous power off has happened to some people. So it may be nothing that you did. Hopefully, letting it charge for a few hours will fix it up.

I have the same exact problem as the OP. I have already made a thread and have tried to express my problems but I don't think people are willing to help (although some did and I appreciate it a lot) so I am going to try to get some help here. Help a brother out?

mr.5106411 said:
I have the same exact problem as the OP. I have already made a thread and have tried to express my problems but I don't think people are willing to help (although some did and I appreciate it a lot) so I am going to try to get some help here. Help a brother out?
Click to expand...
Click to collapse
I had this happen. I left it on charge (from powerpoint not USB to PC) over night and then connected back to PC. It didnt start but the pc was telling me USB device connected and disconnected when long pressing power button.
after running RUU and changing bootloader I finally got it to work. I would try the latest RUU from US / ATT as it has newest everything and see how that goes.

vangoogle said:
I had this happen. I left it on charge (from powerpoint not USB to PC) over night and then connected back to PC. It didnt start but the pc was telling me USB device connected and disconnected when long pressing power button.
after running RUU and changing bootloader I finally got it to work. I would try the latest RUU from US / ATT as it has newest everything and see how that goes.
Click to expand...
Click to collapse
Thanks for the reply but how did you RUU if the phone connects then disconnects quickly?

mr.5106411 said:
Thanks for the reply but how did you RUU if the phone connects then disconnects quickly?
Click to expand...
Click to collapse
It stays connected. I meant u can hear the Win 7 sound of connect USB when u press power and then disconnect USB if u long press power.
Sorry I cant be of more help.

i would try ruu or another usb cable

vangoogle said:
It stays connected. I meant u can hear the Win 7 sound of connect USB when u press power and then disconnect USB if u long press power.
Sorry I cant be of more help.
Click to expand...
Click to collapse
Thank you for your help so far. Ill try this tonight.

mr.5106411 said:
I have the same exact problem as the OP. I have already made a thread and have tried to express my problems but I don't think people are willing to help (although some did and I appreciate it a lot) so I am going to try to get some help here. Help a brother out?
Click to expand...
Click to collapse
I'm one of the folks who tried to help you in the other thread. Saying that you think people are unwilling to help sounds ungrateful and a bit whiny. Remember that the community here provides help for free, and that we also have lives and can't be on here to help you all the time.
Since you've tried charging (wall charger) for several hours, and tried (unsuccessfully) to get into bootloader, there isn't much else you can do. The idea of trying to run the RUU is a good one. But if you can't connect and can't run the RUU, the phone might be done. In particular, the blinking red light is not a good sign. I think there have been some other folks that have gotten this recently, and were not able to recover from it.
But keep trying to charge, and keep trying the bootloader button combo. The fact that your condition happened right after trying to restore a nandroid, leads me to believe its something that can be recovered from, and not a random hardware failure. But that is just a gut feeling, and maybe a bit too optimistic.

when my battery dies and i plug it up to charger led blinks red until it has enough juice to be powered on. you shouldn't try to power on your phone when it is blinking red, i assume that might end up killing the battery for good if you do.

Completely dead, unresponsive phone

Hey guys,
I can't believe what happened to my phone. It was working perfectly up until a few hours ago.
I tried flashing ElementalX v8 which I have been running for months with no issues, as I wanted to change some of the settings. After the flash, it showed it was successful, but there was also another line similar to "E: cannot mount partition". Can't remember exactly. I went to wipe cache and dalvic manually as I always do, then saw a few more lines that looked similar to that, then after tapping Reboot the System, my phone powered off and hasn't worked since. The battery was at 21% and plugged in at the time, which I suppose is risky, but i've never had a prob before. I flash ROMs. radios and kernels a lot.
My phone will literally not do anything at all right now. The LED isn't even on while it's plugged in to it's wall charger, it won't vibrate, flash anything on the screen. Absolutely nothing
I have tried holding power button for up to a minute while plugged in and unplugged, and also, held volume down and power for up to a minute while plugged in and unplugged.
When I connect it to my PC, it shows a device with a driver error "qhsusb_dload". From my research, it seems that I will need to send it for JTAG service or try the steps in the "unbrick evita" thread, which I will, after leaving it plugged in overnight.
I would like to know:
Can I resolve this by purchasing a used Logic board, either from the AT&T or International version?
Can a replacement battery resolve this? A friend has the same phone with a broken LCD that he's scrapping
Is there any possibility it will start working again if it was just left plugged in for hours?
I am in Jamaica and this is a really sticky situation for me. I can't even get a phone out here to use a MicroSIM :-/
I'd appreciate any help at all. Thanks

Firstly, it is the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)? Where did you download the kernel?
I think you are one of the very rare and unlucky people whose phone has bricked for no apparent reason. A battery will not fix it because your partitions are screwed. The only options you have see these:
1. Leave the phone connected to a charger overnight (or at least eight hours) and try to power it on again. This option only has a very slim chance of working.
2. Replace the motherboard.
3. Jtag repair.
Sent from my Evita

timmaaa said:
Firstly, it is the HTC One X (Endeavoru) or the HTC One XL / at&t One X (Evita)? Where did you download the kernel?
I think you are one of the very rare and unlucky people whose phone has bricked for no apparent reason. A battery will not fix it because your partitions are screwed. The only options you have see these:
1. Leave the phone connected to a charger overnight (or at least eight hours) and try to power it on again. This option only has a very slim chance of working.
2. Replace the motherboard.
3. Jtag repair.
Sent from my Evita
Click to expand...
Click to collapse
Thank you for the reply.
I have the AT&T One X 16GB Model. The Kernel I has was from these forums as well, which I used numerous times before. I just wanted to flas it again to change the settings so the kernel file itself has been on my phone for quite a while now.
Is this the only part i'll need to get?: http://www.ebay.com/itm/ATT-HTC-One...e_Replacement_Parts_Tools&hash=item4d1859d891
I will still attempt the guides here: http://forum.xda-developers.com/showthread.php?t=1966850 and here http://forum.xda-developers.com/showthread.php?t=2226445

That looks like the right part to be, except that it's a 32gb model, which I don't think would be a problem. It's definitely worth trying this unbricking methods, but successful attempts are pretty rare. I think you're about the third person I've seen brick after flashing the Elemental kernel.
Sent from my Evita

badbwoydes said:
Can a replacement battery resolve this? A friend has the same phone with a broken LCD that he's scrapping
Click to expand...
Click to collapse
Its not a battery issue. As timmaaa mentioned, something went wrong with the flash (as it has happened to a couple others). JTAG is probably your best bet, or replacing the board.

This probably wont help but I had a bad flash of twrp not long ago. Flashed the recovery and the phone died on reboot. I hooked it up to the computer and i got "qhsusb_dload" in device manager. I thought it was bricked for sure. Anyway while i was trying different things, I held the power button on for a long time and it started up again. It didn't have a recovery but i flashed 2.6.3 again and it has been fine ever since. Thinking that i was one of the lucky ones though. I guess you have already tried that though.

falcon66 said:
This probably wont help but I had a bad flash of twrp not long ago. Flashed the recovery and the phone died on reboot. I hooked it up to the computer and i got "qhsusb_dload" in device manager. I thought it was bricked for sure. Anyway while i was trying different things, I held the power button on for a long time and it started up again. It didn't have a recovery but i flashed 2.6.3 again and it has been fine ever since. Thinking that i was one of the lucky ones though. I guess you have already tried that though.
Click to expand...
Click to collapse
Hi. When you said died on reboot, do you mean you chose the option for it to reboot then it never turned back on? Mine is literally and totally dead. It does absolutely nothing and when it's plugged in to my PC it shows "qhsusb_dload"
How long did you hold the power button? I've held mine for about 3 minutes now.

badbwoydes said:
Hi. When you said died on reboot, do you mean you chose the option for it to reboot then it never turned back on? Mine is literally and totally dead. It does absolutely nothing and when it's plugged in to my PC it shows "qhsusb_dload"
How long did you hold the power button? I've held mine for about 3 minutes now.
Click to expand...
Click to collapse
It was less that 3 minutes. I flashed the recovery in fastboot, rebooted and it didn't start. No led when plugged into the charger. Showed "qhsusb_dload" in the my computer's device manager. It was just dead. It was the right recovery for the phone, just the modified 2.6.3 version for 4.4.2 roms. After I got it going again, I flashed the normal version. I have since flashed the modified one again and it was fine. I don't really know why it happened.

[Q] Scary Experience With HTC One M8

As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?

ricarpe said:
As I'm writing this, my phone just came "back to life". I'm going to explain what happened...
... I'm on the train commuting to work. I was texting my wife to let her know that my boss ha approved me using 4 hours of leave to skip out of the office early so we can start our holiday weekend early. After I send my last text, my phone times out as normal. It vibrates, and this is where it gets weird...
... I take my phone off my belt to look at the text message I thought I received (vibration alert). I double tap the screen to wake the phone and I get nothing. I press the power button and get nothing. I thought that maybe the battery drained and was dead, so I plugged in my external battery... and get nothing.
I get to my cubicle and immediately plug it in and tap the power button to see if the recharge indicator comes on. Nothing.
I press and hold the power button. Nothing.
I press and hold the power and down volume buttons. Nothing.
While I'm typing this message, my phone vibrates and the HTC & Verizon boot animations start. The phone had about 23% battery life (after it booted) and is currently charging and at 28%.
Everything appears to be normal now, but that was not something I expected to happen this morning. I thought my phone was dead.
I'm running the stock ROM and kernel, but the phone is s-off'ed and perma-rooted using the guides in the forums (weaksauce, firewater, TWRP recovery). I'm not sure what happened.
Has anyone experienced anything like this before?
Click to expand...
Click to collapse
Same thing happened to me on Wednesday. Stock ROM, S-Off, perm root and a few minor modifications. Screen timed out as normal after a little bit of usage and about 40% battery life left, went to pick it up and turn it on and it was completely dead, for what ended up being about six hours or so. Called Verizon to have my old phone reactivated until I figure out what I'm going to do. Tried everything from pressing combo of buttons, charging, adb commands, no luck. HTC one came back on after I plugged it into the wall and held power. So I called Verizon to reactivate it. Verizon offered me a brand new device since I am still within my 2 week period for a return. I have until this Saturday to return the device, but everything has been fine these past couple days. Still not sure what I'm going to do. It's almost as if the device was completely stuck or frozen until the battery died, then when I plugged it in again it powered on and showed 1% charge. It might also have something to do with Verizons new XLTE. Either way, scared the crap out of me and I was pretty frustrated for awhile. Never experienced this before and I've been rooting and ROMing devices for about 4 or 5 years.
Thought I would add, that I was sitting next to my fiance and within the 5 minutes that this happened to my device, her old samsung stellar, which is rooted and rom'd, started vibrating and was stuck vibrating for about 15 seconds before she picked it up and turned the screen on. Very strange.

Happened to me as well. It was just one time a couple weeks ago. It did this in the middle of the night, while it was on the charger for sleep. I woke up and wanted to check the time and could not wake the phone with any gestures or button press combinations. I ended up having to hold down or up (don't remember which) plus the power button and the phone eventually turned on. Sucked because I doubt my alarm would have went off.

I haven't had this with my M8, but I've had it happen in the past with my Dell Streak 7 tablet. It was a software problem. Basically like an app not responding but on a system level. Only way to fix most times was to reset.

question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..

blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.

Kuuroki said:
Do you have a citation for this?
I'd be interested to know if this is true or not. I doubt it, but I wouldn't be surprised.
Click to expand...
Click to collapse
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.

blazinandroid1 said:
question I have. Did you give Verizon superuser permission on there app... As my understanding goes. Verizon sends a signal to phone to get updates on your status.. This info came from a verizon rep. I dont know how true it is.. But we all know it wont surprise us. As there always getting into are pockets..
Click to expand...
Click to collapse
I did grant permission at first without thinking about it, until I immediately thought why the hell is Verizon asking for root, so i went into the superuser app and permanently denied permission. It was days before this happened to me.

Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.

hgoldner said:
Not sure why, but the Verizon app definitely asked for root permissions after its last update which I most assuredly denied.
Beamed from the holodeck of my Nexus 7 FHD.
Click to expand...
Click to collapse
Interesting..I run paranoid android on my One, and as such, have gotten rid of the Verizon bloatware.
That's slightly worrying. Verizon scares me sometimes.

In my mind, this validates my decision to go over to the CM11 nightlies and never look back.

Happened to me a couple times I just hold both volume keys then power till it restarts to simulate a battery pull cuz I always assumed it just got stuck in sleep
Sent from my HTC6525LVW using XDA Premium 4 mobile app

I've had this happen a couple times with my M8. The first time it made me late for work because my alarm clock didn't go off. Just last week I woke up and unplugged it from the charger. When I looked at the phone I noticed that the green charging light was still on solid even though the phone wasn't plugged in anymore. I held the volume keys and the power button and eventually got it to start back up. It's concerning, but I don't want to return my phone because I have an expensive Spigen glass screen protector on it. I guess I'll just hope it's a software issue and HTC will eventually get it sorted out. I'm currently running CleanROM and the CodeCraft_Final kernel.

I was quickly able to avoid the Verizon root perms. First of all I always recommend disabling play store auto update. I very rarely update apps unless the update fixes a direct issue I am having. Once I heard about the root perms, I disabled the app in settings and carried on the s off process (eventually). I then searched carefully for a ROM w/o my Verizon included and flashed cleanrom and that's where I'm at now. All these threads are making me scared to reboot my device lol. Only hope I have in finding some info about this is a rogue Verizon employee
Sent from my HTC6525LVW using Tapatalk

It isn't necessary to hold both volume keys, just volume up and power.

Some kind of an issue with Verizon bloat acting up?
I disabled most of Verizon preinstalled bloat and I've never seen this issue.

andybones said:
Verizon app asking for su perms? that is crazy, I would never allow that, they can only get information they cannot get from a phone that doesn't have SuperUser access, I just wonder what.. is this perhaps a new method to try and track those that are sending back defective devices that are S-OFF? As we most know, we can send back an S-OFF phone and you *should* have no issues. I wonder if this new SU thing, flags your account and they start checking our phones? Not really sure how badly they care about rooting and the extent Verizon will go to, to stop us from doing it, especially with the new Edge plans and having to give the phone back? I would think the process of making it a certified refurb would flash back any rooting of the phone back to stock, but who knows.
I actually didn't have what the OP had, but did have a scare, but is expected as I am running beta AOSP ROM.
I updated AdAway and did a reboot, went to the bathroom, came back and the phone was still rebooting, so I got confused, so I watched the phone and it was in a boot loop, I thought, strange, so I held volumeup and power to get me into bootloader, then into recovery. I decided to wipe and restore a nandroid. This is where it got interesting. I tried to restore - reboot, try to adb sideload ROM - phone reboots. not good..
I did the RUU that was put together, and luckily I was able to re-flash my TWRP recovery and it did load my nandroid without reboot so I believe I am good to go, but I wonder if all this weirdness does have anything to do with XLTE, or just a coincidence.
Click to expand...
Click to collapse
I am a little disappointed.. you didn't take your phone with you into the bathroom? Lol. this happened to me after I tried an aosp Rom for the first time then went back to my stock rooted with soff and thinking about it now I accidentally allowed root permission to Verizon application which I quickly disabled in su. I didn't think much of it considering I thought it was something I had done or maybe battery died but it only lasted about 5 minutes rebooted and I was good. I remember on a previous HTC phone if you had a bad Rom and radio/kernel combo the phone would act vertually dead even if the battery was fully charged.

This just happened to my M8. I rebooted it and it didn't reboot. When plugged in, the LED didn't come on. Rooted, S-OFF, running pretty close to stock ROM with an unvervolted, overclocked kernel. I've let the phone sit for about 24 hours now. Have ordered a warranty replacement, but may try once or twice more to see if it springs back to life. Very strange. Can't get into hboot or any other key combination. For all intents and purposes it is a brick. (If it can't register a charge, it won't take adb).
Even if it does come back from the dead, I'm not taking a chance and swapping it out.
UPDATE: Truly bizarre. Returned to life and rebooted in response to power-volume up about 26 hours later. Battery had dropped from 80% to 40%. Rebooted like nothing had ever happened. Editing this on it now.

This happened to my first m8, what I believe is happening is they are going into the bootloader, but the backlight is off. I didn't notice until I held it under a bright light and saw there was something in the screen. Afterwards I was able to navigate to reboot the device. Or you can try simulating a battery pull. Just something to try before you write your baby off as dead.
Sent from my HTC6525LVW using XDA Free mobile app

Sounds like SOD.