Database Info

[Q] Screen not responding to touch

Hi everyone, just got the tablet today and set it up at work, played with it for bit and everthing was working fine.
Got home about 2 hours ago and now when I wake it from Sleep, the touch screen is not responding at all. Have tried everything, power is 98%, plugged into a PC, did the hard reboot, even wiping the data to start setup again. But all to no avail.
The screen isn't responding at all. Its very frustrating as I want to play with it some more!!!
Hope someone has experienced this and can help.

had the same issue once...i turned it off and left it for about 5min...turned it on and the screen works again...
this hasn't occured since then..probably just a system glitch..

Happened to me once, reset the device and it worked. Now it happened again and its been unusable for a day. If it doesn't work tonight, the $hit is going to hit the fan...

Are you stuck at the lock screen immediately after booting because the unlock function doesn't respond to touch? If so, I'm having the same situation. I really hope that waiting a few minutes does the trick...
Edit: even did a full wipe and the thing is still unresponsive. I assume this is a very bad sign. FML.

Have you guys contacted ASUS support? They will probably have you RMA it. How long did you guys have it before this happened? Now I'm worried that mine will do the same thing.

ASUS support did want to RMA my TF that was having this problem. However, after leaving it off for a couple hours, I went to turn it on to wipe out all my account settings and the touchscreen started working again.
I have no explanation for why it started working though. The last thing I did before it was magically fixed was go through the normal shutdown procedure by answering the 'do you want to shut down' using the dock's mouse instead of just holding down the power button. Maybe that made a difference?

Blue_Man said:
Are you stuck at the lock screen immediately after booting because the unlock function doesn't respond to touch? If so, I'm having the same situation. I really hope that waiting a few minutes does the trick...
Edit: even did a full wipe and the thing is still unresponsive. I assume this is a very bad sign. FML.
Click to expand...
Click to collapse
This is what happened to me. Stuck at the lock screen, no touch at all. After 4 days of waiting for Asus to reply to my email and several disconnected phone calls, I have returned it to newegg. Since this item is still out of stock I expect to receive a full refund. Which is fine by me. June 8th, here I come.

Same thing happened to me, just returned it to fry's and was able to avoid the restocking fee. Going to get the galaxy tab come june 8th now instead.
Sent from my Xoom using XDA Premium App

I have weird little quirky things like this happen from time to time with my TF, such as having to hit the power button or lock button twice before it works. I think it might be more of a software issue than anything to be honest. Hoping that future updates will correct all of these issues.

I hope its a software issue....

Found a solution that worked for me. I booted into recovery mode by holding vol down and power. then I selected vol up to enter recovery. Then the exclamation point came up with the android robot. I left it like that for a few minutes then held down the power until it resarted.
It booted up like normal, no data lost. I then restarted for good measure. Came right back up like normal, touch screen and all.

Thanks jdmnash. I followed your instructions and it worked like a breeze. Should make this part of a sticky help thread.

Found a solution
Update: Tried every fix I could identify on the forums as I was also draining the battery as suggested on several forums. After 4 days waiting for the battery to drain, I was able to restart the TF and get active responses to the touchscreen. Unfortunately I had performed a reset and wipe earlier so I am having to reload everything. I am happy to have a functioning TF again, but have serious concerns about this failure and this awkward repair method. Additionally, I have still not had a response from ASUS support from 5 days ago.

Mine is constantly doing this. Randomly.
Its as if the daemon for screen touch detection crashes. The rest of the unit is fine but that stops and the only fix is a power button off, then on.
Something is not right here. Its vanilla out of the box, no extra software just the 13 FW update.
Will 3.1 fix this? Hopefully, as it stands, this will have to be returned. It is not fit for purpose, constantly failing.

same problem
Just picked up mine. Out of the box at a cafe it worked just fine. Brought it home and same problem as everyone else in this thread. Have tried all of the suggestions in this thread (except waiting for the battery to die). Even installed the 3.1 update via SD. Still no joy. Guess I'll try a few more things before returning it. My guess is a problem in the supply chain with the capacitors that detect screen touch. Doubt that it can be solved solely through a software update (or if it can it definitely didn't make it into 3.1)

my touch screen stopped working a week ago while i was at school. and i got really pissed and just kept on rebooting it and after like 5 or 6 reboots it started working. Havent had same problem since.

Hmm... thanks for suggestion. Tried booting it about 5 times but still borked. Draining the battery now as my last attempt before taking it back.

Update: I ran the battery down to zero. Charged it up for 30 mins and now it works again. Hope I don't have to repeat that very often.
BTW, the fastest way I could find to run down the battery was to power on while holding down the volume down button. Then just leave it sitting in that state until it reboots itself and then repeat.

Unstable touchscreen
obi-nine said:
Update: I ran the battery down to zero. Charged it up for 30 mins and now it works again. Hope I don't have to repeat that very often.
BTW, the fastest way I could find to run down the battery was to power on while holding down the volume down button. Then just leave it sitting in that state until it reboots itself and then repeat.
Click to expand...
Click to collapse
Hi , After the battery is zero and then 30 minutes charging, in order to make it work , did you discharge it right after 30 minutes or still you keep it charging ?
I got same problem with my TF which is really a disappointment.. I tried to factory reset, reboot ... but still can't make it work. I have to try this trick by draining the battery to zero. Hopefully, I get advise from all of you for this problem ?
Thanks a lot

Can you guys try using ADW launcher and see if things improve?
I think it did for me.

[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.

Phone randomly corrupted somehow, need help.

Hello people, first off lemme say I'm not necessarily new to this forum, I for sure have used it a hell of a lot in the past and I know roughly what goes on around here, I've recently created my account in order for me to actually be able to be able to plead for the amazing help the XDA is known for.
Anyway, long story short, I don't know what the hell happened, but allow me to start from the beginning. I went on a camping weekend with my OPO, phone worked flawlessly all weekend and lasted the whole time, everything was fab, went back to a mates house and asked if I could borrow his phone charger (He has a Lumia 625 incase anyone was wondering), we then went out shooting and I left the phone there for a few hours to charge. Came back to it and it was fully charged, but had turned itself off? Because it was on the power off charge screen when I came back to it, and was on lock when I left it, nobody touched it in that time. I took it off charge, powered the phone up and it must of boot looped about 3 times? Eventually it got into CM but there was no lockscreen, went straight to the homescreen. This is where it went nasty, the capacitive keys outright weren't responding, the device wasn't slow as such, nor was the CPU running hot or doing anything intensive (I have CPU load display enabled), but the date was set to Jan 1970, and the phone couldn't pull a signal at all. WiFi outright wouldn't switch on either. So I tried rebooting it a few times, to no prevail. For some reason, I accidentally tapped Bluetooth in the quick settings panel, the phone crashed and rebooted, and wouldn't stay on for more then 3 seconds? Before crashing and rebooting. I've since gone into recovery and tried a factory reset, cleared cache and media too, but to no luck. Phone still doesn't stay on for more than about 3 seconds once it actually gets into CM (The welcome to CM screen, it crashes 3 sec immediately after boot).
I have no idea what I'm supposed to do, can anyone try shed some light on this? Much help would be appreciated and I sincerely APOLOGISE for the wall of text. Many thanks.
^Dat wall of text doe (sorry about that)

Check out this thread:
http://forum.xda-developers.com/showthread.php?t=2922849
PS. You might want to consider using paragraphs in future posts, that's one hell of a long paragraph there [emoji13]
Transmitted via Bacon

Thank you man for the pointer, I'll give it a go. And yeah sorry for the wall.

No worries, I hope it works for you.
Transmitted via Bacon

I am having the same issue since last night. Put my phone to charge and when I picked it up it stayed on for about a minute unable to connect to Wifi or cellular signal. Then it went to a crazy boot loop. Wiped cache, media and at the end data. Now it boots and it stays on for a few seconds and reboots. I will try the solution when I get home tonight but I was just curious if it worked for you.

HTC One M8 reset itself?!

The other day, my phone died midway through a call. When I tried to turn it on, the 0% sign showed up meaning it was completely dead. I had to urgently make a call so 30 mins later, I held the power button again, turned it on, and the phone went to the white HTC screen and then turned off. I finally got home and connected to my phone to my charger after. I let it charge for a bit then turned it on. I knew something was wrong when my phone was hung on the red Verizon boot logo for a while. Minutes later, it went past the Verizon logo and a pop-up appeared that said optimizing app 1 of 44. I thought this was odd because I already got the MM update about 2 weeks ago and since it updated, I never saw that message ever until now.
Once my phone gets past that and finally boots to the homescreen, I realize that a lot of things have gone wrong. First, I got signed out out of all my accounts (Whatsapp, Spotify, Instagram, Facebook, etc). On top of that, my call history was cleared, all my text messages were cleared, and all my contacts that were saved on my phone storage were gone. In addition, I also had to re-update a lot of apps including the HTC ones that you have to upon the MM update. Finally prior to those whole thing happening I had 10.7gb of free space. After this episode, I lost exactly 1 gb of storage and only have 9.7gb free.
I don't understand what could have caused this or why I lost all this data on my phone. Moreover, it doesn't seem like anything was deleted but my phone is just not reading anything that was already there.

mine just did this exact same thing after shutting off from a drained battery. It's like the data partition or whatever got wiped. Right now trying to log back in to everything and set EVERYTHING back up again. This sucks.

baune7 said:
mine just did this exact same thing after shutting off from a drained battery. It's like the data partition or whatever got wiped. Right now trying to log back in to everything and set EVERYTHING back up again. This sucks.
Click to expand...
Click to collapse
i came here for the same thing. mine happened around the same time. only thing i can add here is that my storage is almost maxed out on the phone. makes me wonder if that had something to do with it. but then this happened to two other people around the same time. very weird.

The exact same thing happened AGAIN! I was at the gym listening to music and texting some friends while my battery was at 15%. Went from 15% to 10% in a matter of mere minutes and then from 10% just shut off. Couldn't charge it until I got home so I just kept it in my pocket. Got home about an hour later, put it to charge and then turned it on when battery hit about 10%. Same damn thing, got stuck on the Verizon boot logo and then the dreaded Optimizing Apps message showed up. Once it finished, I was logged out of all accounts, updates to system apps were gone, and widgets/BlinkFeed were gone/reset. And just like last time, suddenly 1GB of storage was gone.
Literally un-freaking-believable. I dreaded that it would happen when my phone shut off and yep, my fears were right. Going to do a factory reset once I backup everything. From there, I am debating whether to replace the battery or replace my phone. While it sucks that it happened to you guys as well, I am somewhat glad its an HTC issue and not just an issue with my personal phone.

Same thing happened to me at 40%

This was recently brought up in the viper rom thread, could be of help.
TidusWulf said:
Your battery needs to be reset. Hold down POWER + VOLUME (can't remember if it was up or down. takes about 10 seconds)and let it keep resetting and keep holding it for 3 minutes. then let go.
It'll fix your battery so that it drains to 0 instead of 13, but it doesn't fix the weird pseudo-reset problem. It's a known issue and many people are struggling with it. My advice is to set EXTREME POWER SAVER to auto-on at 10%, and if you ever see it that low, just turn it off yourself until you get a chance to charge it.
Click to expand...
Click to collapse

Same thing has been happening to me since the MM upgrade. Before that I had NO issues with my battery so I find it hard to believe that my battery is the problem.
After the third time of this happening I finally decided to to a factory reset. This did not help, phone continues to die anywhere between 15% - 30% and revert some of my settings back to stock.
This is driving me insane as I rely on this phone for personal and work use.
Decided to call HTC support today, I did not expect a solution but wanted to make sure it was reported. Of course they had no idea and claimed to have never heard of this issue.
I am guessing that since the M8 is over two years old we wont be seeing and fix pushed out for this issue. I really like my phone and dont want to upgrade at this time.

Finally somewhere where people are actually having the same issue. I've tried factory resetting the phone, doing a fresh install of the OS (with firmware recovery tool) all with no avail. I note lose all my settings and app configurations every time the phone dies, shuts down or restarts. I hope there's a fix, otherwise it looks like a custom rom is the only way.
Has anyone tried wiping the dalvic cache? I can't get into the recovery on my phone so I can't try it, but heard I it might help.

Had the same issue last week
I was at about 20%, phone shut down. I plugged it in to charge, went to boot it up, and it got stuck on the Verizon bootup screen.
I waited a while and did a hard reset, and it came back on, but was completely wiped. So I had the same problem, which is a real pain, because I use the GOOD app for work, and each time that re-installs I have to get a new PIN. And I have had to re-install the app a few times in the past month for a variety of reasons...

Teevan said:
I was at about 20%, phone shut down. I plugged it in to charge, went to boot it up, and it got stuck on the Verizon bootup screen.
I waited a while and did a hard reset, and it came back on, but was completely wiped. So I had the same problem, which is a real pain, because I use the GOOD app for work, and each time that re-installs I have to get a new PIN. And I have had to re-install the app a few times in the past month for a variety of reasons...
Click to expand...
Click to collapse
I feel your pain. I use Mobilepass for work and every time my phone resets it deletes my token and I have to request a new one.....
Here is what I did two days ago that seems so far to be working for me. I calibrated the battery. I have tried this in the past but could never get the calibration to work properly. Each time I tried I had the phone plugged into the charger. This time I didnt and the phone went through the battery calibration process like it is supposed to.
Since I have done this my phone will stay on until it gets to 8 or 9% and then shut down but when i charge and turn back on all of my setting are still in place.
To calibrate the battery I held the up volume, down volume and power button (all 3) for a full 2 minutes without the phone being plugged in. During this time the phone will start and get to the HTC splash screen then shut back off, start again to the HTC splash screen then shut off, repeat, repeat, repeat.... after 2 minutes release the buttons and let the phone boot up, plug it in and let it charge to 100%.
I hope this helps,

This happened to me today. I let the battery get a little lower than usual last night, around 13% before shutting it down and plugging it in for the night. Turned it on this morning and it booted up normally. Didn't lose any apps or data, but every time I did something on the phone it gave me those little hints like its a brand new phone. I went to settings and it says it was factory reset at 6:46 a.m. this morning (about the time I turned it on).

Parakaleo said:
This happened to me today. I let the battery get a little lower than usual last night, around 13% before shutting it down and plugging it in for the night. Turned it on this morning and it booted up normally. Didn't lose any apps or data, but every time I did something on the phone it gave me those little hints like its a brand new phone. I went to settings and it says it was factory reset at 6:46 a.m. this morning (about the time I turned it on).
Click to expand...
Click to collapse
Did it reset your ringtone and notification tone settings? Thats what it always has done to me.

I would just like to say that the same thing happens to me as well on my HTC one m8. Battery suddenly dies, now even at 25%, even after a calibration which is just a temporary solution, and when I turn the phone again, SwiftKey settings erased, everything went to stock, messages and contacts are preserved, but the apps start updating itself even though they are not allowed to and I have to manually set a lot of things. It is a total confusion and I literally can't believe HTC allows themselves to not issuing a fix for this disaster.

Was it cold?
Same issue. With mine it seems to be when it gets cold. I was skiing today in 20F but inside my pocket this really shouldn't be an issue. It has turned itself off and refused to restart several times when it has been used to take pictures in cool weather (I live in western OR, it doesn't get COLD, by cool I mean <35F but >20F, usually > 25F). This is the third time it has totally screwed up the phone when it has happened. On another occurrence it reset under normal conditions too. I'm getting pretty sick of it as it is quite a process to get all my VPN tokens reset, get all the apps back etc. Of course it waited until the warranty was out to start acting up.
This time is especially bad, the phone will not restart properly and important processes just constantly flag as stopping so that I can't even get past the initialization screen. It looks like I will have to do a full factory reset. If anyone from HTC is reading...Not acceptable and I won't be buying another phone from you.
Unfortunately I've reached the point where I wouldn't be surprised if it is a programmed planned obsolescence function, but whether or not, this is really annoying behavior.

Sorry to hash up an old thread but I put up with this crap for 5 months before I finally punched and broke the screen out of rage during an important business tech support call when I was at the clients location trying to service their security equipment, it was so embarrassing having to tell them I have to come back especially since it was a remote location.
Mine would wipe contacts, texts etc regularly. I ended up installing Super backup or something and saving my backups on google drive and just restoring everything everytime it happened.
I decided to fix up the phone and replace the battery, broken charging port and smashed screen and unlock bootloader and root but flashing superSU didnt work, got stuck in a bootloop. Anyways through all this I wiped all the caches (including Dalvik cache) flashed the correct stock rom and did the battery calibration and that seemed to have solved the random shutdown and memory leaking issue.....but I guess I wont know for a while.

I have a HTC One 610, and like every once in a while it well automatically reset it self whenever I am in the middle of a text message, on facebook, or even sending an email on phone. Its getting annoying when my cell reset its self.
what needs to be done to it? and should I do.

PRINCESS2017 said:
I have a HTC One 610, and like every once in a while it well automatically reset it self whenever I am in the middle of a text message, on facebook, or even sending an email on phone. Its getting annoying when my cell reset its self.
what needs to be done to it? and should I do.
Click to expand...
Click to collapse
try a factory reset

I know its old but people are having the same issue still so I'm gonna paste this everywhere i find this problem.
There is a Modified stock rom named "Android_Revolution_HD-One_M8_53.1" and its almost the stock M8 without bloatware and so much more stability improvements. So hear me out and flash it with a custom recovery (i did it with twrp) and it seems to be working fine so far. Give it a go before you trash your -still so good- phone to the open seas.

Well, this issue is still happening. my phone has been doing the same for about a week now. ive made several attempts to reset the battery and had to reinstall back ups every time its happened also. the only difference i think now is that its happening at 90% instead of the usual 15%. ive been following instructions to hold volume up, down, and power (with the phone off) for about 2 minutes and then letting go. i have my extreme power saver set to come on at 15% but Im not even getting that low before it shuts off and resets. i have however noticed that recently that if you plug the phone on charge after it first dies you can avoid the phone resetting.. this may be a fluke but its allowing me to deal with the battery problem now without the loss of my data, contacts, etc.

This is exactly the reason why HTC One M8 is the last HTC phone I will ever purchase. Imagine the hassle of phone factory resetting on its own. Horrible.

Damn phone stuck in bootloop!

Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.

thomasanderson said:
Came home from work yesterday and the Pure XL was dead, said it needed to be charged. Never happened before but I figured whatever and plugged it in and went to sleep. Woke up this morning and powered on the phone and the all white BLU splash screen came up and then the phone went off. Came on again and the all white BLU splash screen came up and went off. Ive tried holding down the power button for over a minute. Tried holding the power button and volume keys to boot into recovery from 10 seconds to 2 minutes, nothing stops it! It just keeps rebooting. This has been my apprehension towards purchasing phones with non removable batteries. The boot recycle happens about every 15 seconds and the phone vibrates everytime it boots up for the past 2 hours. Its getting very annoying and there is no way to make it stop. Any help would be greatly appreciated.
Click to expand...
Click to collapse
Plug it into your computer (you'll notice that there will be a longer black screen in-between the bootloops) and hold down the power button for at least 10 seconds or more, then release it after the next vibration and the white BLU screen shows up. It might take a couple of tries.
If you manage to boot into at least recovery but can't boot into the system, then try clearing your cache/dalvik cache and try rebooting into system again.
If all of the above doesn't work for you, then your boot.img/system has gone bad, and you'll have to flash the stock images with SP Flash Tool (both of which can be found on other posts on this forum).

follow the instructions on the SP flash tool thread... sounds like what happened to me after bad flash... theres a lot of information in that thread that will set you up...

Thanks for the quick replies guys. The PC trick didnt work at all. I just called BLU and asked for a replacement(havent heard back from them ironically). I put the phone in the basement so I wouldnt have to deal with that incessant buzzing every 15 seconds. Eventually the battery died. Since I had it powered off finally, I plugged it in for about 10 minutes to give it enough of a charge to power on but not stay on to buzz for another 2 hours. This time I powered it on using the master reset button combo and was finally able to wipe the cache and restart the phone. Took a good 4 or 5 minutes to boot after that, but everything has been fine since. Really dont know what initially caused the issue, never happened before. Good thing too, cause BLU told me that they would send me a RMA within the hour and I still havent heard from them. Think this will be my last BLU phone. Thanks for the assist.

My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app

bolanoboyboom said:
My phone Is stocked without root or Twrp. And I find my self having a bootloop once a month for an odd reason. This forces me to take bat out and put it back in or just let it loop til battery dies
Sent from my PURE XL using XDA-Developers mobile app
Click to expand...
Click to collapse
??????

My phone is basically out of the box and I'm getting boot loop problems when I first boot. This happens like once a month
Sent from my PURE XL using XDA-Developers mobile app

This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.

Update
num1greeter said:
This happened to me for first time yesterday. Bought the phone earlier this year and everything worked fine. I restarted the phone because my sound recorder app froze up twice on open and the infinite boot started until the battery died. Tried the {power}{vol up} thing, didn't work to stop it, so I put it in my car and went back to the conference I was attending. Battery was dead when I got out. Contacted BLU by phone and they started a ticket for me, but I figured I'd see if other people were having this issue and learn what they did because I'd rather not be out of a phone for however long it takes for BLU to replace mine. Stumbled on this page. I never rooted my phone. And BLU only sent one wireless update since I've had the phone. I'm trying to get into the menu by connecting to the computer. Worked the first time, I cleared cache, and tried to backup my files, but I'd taken out the SD card in expectation of sending it to BLU. So, Powered off the phone, put the card back in, and now I haven't been able to get the menu back. Still working on it, if there are any suggestions anyone drops on me before Tuesday when I'll likely ship it (or at least hope to because I'll be yelling at them Monday), I'd appreciate it.
Click to expand...
Click to collapse
I tried to flash the phone, but the bootloop apparently wouldn't allow that. I had 0.0% progress after 3 hours. I then tried to go back into the menu you get from {Power}{Vol UP}: still no go. So, I started to take the phone apart again to get ready for shipping. The battery was still low so it didn't take long for it to die after I unplugged it from the computer. Out of curiosity, I tried to repeat finding the menu like I did earlier that day (conditions were that the phone had no charge when I connected it to the computer, and my SD card was removed.) No go. But, then I hit {Power}{Vol Up}{Vol Down} just to see what happened, and boom. My phone loaded up. No loop... Figured somehow the files had copied and the status bar was wrong. Turned the phone off, put my SD card back in and turned the phone on. Loop reappears ...I waited for the phone to die again, took out the SD, attempted to turn it on and the loop was there. Connected it to the computer and hit all 3 buttons, and the phone loads up. So, now I'm confused. Is there any way that the problem is some crappy connection to the SD?