Related
after i attemped to upgrade my jf 1.41 rc 30 to jf 1.41 rc 33 my phone freeze and then i took out the battery, try to turn it on and it wont turn back on is there any way or any buttons i need to push to get this back on again? i'm desperate and dont want to wait for a g1 replacement which is coming next week please give me some advice on how to make my phone work again.
both CAMERA/POWER and HOME/POWER are not working?
yup both i tried nothing works
ariex said:
my phone freeze and then i took out the battery, try to turn it on and it wont turn back on.
Click to expand...
Click to collapse
Did you put the battery back in?
what do you think?
I upgraded from JF 1.41 RC30 with no problem, Radio and all, good luck!
ariex said:
what do you think?
Click to expand...
Click to collapse
So far you are the only person with this problem so we are running through the basics.
Did you get any errors or messages during the update? Did the phone run out of battery mid update? Did anything odd or unusual happen?
quick question in while in the topic, had he done a FULL nandroid backup and was able to atleast get to boot screen would he be able to restore his phone? just a quick questions because to this day i have no idea how the nandroid thing works i cant do it on my x64 vista either and dont see how it comes in handy lol. Sorry just trying to fig it out.
after i tried to install the radio update it showed some sort of chip with an arrow and then it froze for over 10 mins so i ended up taking out the battery
@zgjbeta Yes. If you can get to the blinkin android screen, your not really bricked. Nandroid would fix it right up.
If it wont even turn on, like your case. I dono what to tell you.
For starters, try to connect it to a wall outlet to make sure its not the battery.
Also tell us exactly what happened during the update process.
EDIT: I read your most recent post. That's strange because everyone gets the chip thing, you shouldve tried home + back or menu + green + red.
One of those wouldve most likely worked.
Good luck.
Also maybe try to take it out again and put it back in.
I had the chip and arrow after the radio update, I didn't take the battery out, started pressing random keys, lol... and then it went away and booted back to a JF recovery style screen. Pressed home + back and it rebooted to a stuck flashing android. Then did call+menu+end to reboot and it has worked fine ever since.
There is definitely something whacky going on...
yes i tried to do the home key plus end and camera plus end options while in that chip state but didnt do anything so i resolve to take out the battery and it wont turn on again. i also tried all the button reset combo nothing happens
If it wont even turn then there is really nothing that can be done. Another thing I would try is if you know someone else with a G1 try their battery.
ariex said:
after i tried to install the radio update it showed some sort of chip with an arrow and then it froze for over 10 mins so i ended up taking out the battery
Click to expand...
Click to collapse
Also try cleaning the battery contacts in the phone and on the battery. This happened to one of my dumbphones once - cleaned out the battery contacts and it worked again. Bizzare situation, simple solutions first.
You might've turned it off while it was writing a vital file. Thus your phone might be bricked.
Here's an idea - sent it back to T-Mobile/HTC - and I don't think they will notice you violated your warranty until it's too late (they have to fix your phone to find out) so you could just refuse to pay and have them send it back to you.
I too saw the chip with the arrow thing, so that makes 3 people in this thread. It happened when I did the radio update. Anyway, in my case, I held down the recovery mode keys for a while and it went to the menu. Then I just rebooted and everything was great. Glad I didn't take out the battery (I considered it).
I had the chip and just waited and it took care of itself. Just be patient people.
plug in the wall charger, wait 10 seconds, then hold the red power button for 3-5 seconds then release, it should turn on
i tried that didnt work anymore advice?
also is there any way to run diagnostics of this phone to pc to make it work?
If the phone won't turn on, go back to the T-Mobile store and ***** em out. Not much else to say if we can't even get power to it.
Hey all,
My wife and I both have Nexus S phones bought together sometime in Jan. Both phones are running stock Android 2.3.2, no rooting or anything done yet.
Right now her phone is behaving weirdly, while mine is perfectly normal. I suspect that her battery is messed up somehow, but I can't figure out what to do.
For the last day or so, when her phone hits <15% battery, the low battery warning pop-up appears.. and just keeps reappearing. No matter how many times the pop-up is acknowledged, the pop-up just does *not* go away until we connect the phone to a charger. Sort of an aggressive warning
This means that the phone won't let itself be put to sleep, keep the screen turned off or anything -- unless we connect the phone to a charger. I feel as though the battery is charging slowly, but I can't be sure.
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display. This behavior goes away if the phone is connected to the charger. My phone does not show this behaviour - display goes off the moment I press the power button, regardless of charging status.
Any thoughts?
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S? We removed the battery and put it back in (which is basically a soft reset apparently) and now it seems as though the battery has lost calibration or something. Have not done a hard reset yet -- should I go ahead and try that too?
Thoughts/help much appreciated. This is very worrisome!
satishev said:
Another weird thing we're just noticing is that when we lock the phone by pressing the power button, the screen goes off and comes back on immediately. We have to press the power button a second time for it to actually switch off the display.
Click to expand...
Click to collapse
Sounds like it has a glitch in the software. Try wiping everything. Go into settings, unmount the USB memory, erase the USB memory, then do a factory reset. That will reload the firmware back into active memory for the phone and wipe anything out of the USB memory that might be causing this issue. I usually do a factory reset with a new phone after I play with it for a while anyway, and it doesn't hurt the phone at all. You simply lose your texts, contacts, photos, etc. Just copy or backup anything you need to keep and wipe it clean.
If that doesn't fix it, then you need to get it replaced.
Alternatively, could anyone point me to how to recalibrate the battery on the Nexus S?
Click to expand...
Click to collapse
Once you do a factory reset, turn off the phone and fully charge it using the supplied AC charger (don't use the computer port to charge), unplug it and wait a minute then re-connect the charger again for another hour, unplug it, turn on the phone and start using it.
Let us know if the reset fixes the issue.
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
satishev said:
I was hoping to get away without a factory reset, but I guess we have no choice. Will give it a shot later today, and let you know how it goes. Thanks.
Click to expand...
Click to collapse
Well a factory reset is a lot easier and faster than a return/exchange and accomplishes the same thing.
A new symptom has just surfaced -- right now, when my wife tries to lock the phone, it locks the screen but won't switch off the display. No matter how many times the phone is restarted, or the lock button is pressed, the display never actually goes off (timeout has been varied from 15 secs to 1 minute, to no avail). Phone was completely charged as of today morning, so its not popping any low battery warnings.. just not switching off display.
It definitely seems like a battery/software glitch of some kind. We've not done the factory reset yet (she's at work, and this just started happening). Just thought I'd keep the thread updated.
I went ahead and factory reset the phone, as well as manually installed the 2.3.3 update. Figured between the system reset and the update, something should get fixed
Restoring settings was relatively painless (love how everything just gets set up the way it was due to backing up everything with Google). We have the phone charging now (overnight), will update again tomorrow morning once its full charged and my wife is using it as normal.
Fixed?
Hey @satishev
I have the exact same problem, did yours get fixed?
thanks
Hey crobbie, sorry I forgot to update the thread.
After factory reset and update to 2.3.3, the phone has been working normally (so far). All issues related to battery/display are gone! Looks like it was some kind of software glitch that was causing it to read battery state incorrectly (Another symptom I had noticed was that on alarm/dock mode it would keep flashing a charging icon, despite no charger being connected). Initially after reset, the battery usage was acting wonky, but that worked itself out and everything is showing what I expect.
If interested, a blog post summarizing process/ZIPs for all updates to date can be found here.
Thanks, bfksc for all your help
okay, So i searched and apparently I am the only one with this problem happening.
Last night my phone went nut's, it would not turn on, reset or anything! So i contacted ATT and they keep telling me its the battery, 3 tech support agent's and they still told me it was the battery and i should go to the Support Center which is a bit out of my way. So i called the support center to see if I could get a replacement from them, They dont carry Cellphones apparently (yea -.-)
My problem:
The phone without a SIM card works.
The phone with the SIM Card, shuts itself off and either refuses to start, or constantly restarts itself.
I've tried:
- Re-installing Android (through the hard button reset)
- OTA Updating through settings (without the simcard)
- Manually updating through the PC (kept telling me I had less than 30% battery.)
Anyone help me!?
ATT is going to take 5-7 day's to give me my phone, and frankly.. Being without a phone is the worse thing for me (im trying to get a new job, so no phone is a big problem - on top of it being my alarm clock for my current job)
If you really cant wait for the new phone then maybe you could try taking it to an ATT shop and getting a new sim card. Although I dont really see how a sim card could cause this but I guess its worth a shot.
Second for the SIM card. I had a friend whose phone would randomly restart. When he changed the SIM, all was well. Occam's razor, my friend.
Sent from my HTC One X
I went to the local ATT Store for a sim swap, and the phone worked perfect in the store, Got home and it crashed.. Now it wont even turn on with the SIM in.
Are you rooted? You could try changing roms or flashing a new radio+ril. I have no idea if any of that will fix it but you never know
Nope, it's not rooted, I thought about it, but the phone wont even connect/charge now :/
I guess It's not happening to any of you? :/
-P.S. The SIM Card actually worked, then cut out :/ lol. HTC Is telling me its the SIM Card Reader in the phone :/
Thats a bummer! I guess you just have to wait until your new one comes in if it is the sim reader
Have u run a ruu? I would most certainly do that before send it in or anything. Only takes 10-15 mins
............My EVO Ways...........
(You Can S-Off For All I Care)
GamerRadar said:
okay, So i searched and apparently I am the only one with this problem happening.
Last night my phone went nut's, it would not turn on, reset or anything! So i contacted ATT and they keep telling me its the battery, 3 tech support agent's and they still told me it was the battery and i should go to the Support Center which is a bit out of my way. So i called the support center to see if I could get a replacement from them, They dont carry Cellphones apparently (yea -.-)
My problem:
The phone without a SIM card works.
The phone with the SIM Card, shuts itself off and either refuses to start, or constantly restarts itself.
I've tried:
- Re-installing Android (through the hard button reset)
- OTA Updating through settings (without the simcard)
- Manually updating through the PC (kept telling me I had less than 30% battery.)
Anyone help me!?
ATT is going to take 5-7 day's to give me my phone, and frankly.. Being without a phone is the worse thing for me (im trying to get a new job, so no phone is a big problem - on top of it being my alarm clock for my current job)
Click to expand...
Click to collapse
I'm pretty sure AT&T can send you a spare/replacement or whatever and you use the same box to send your HOX so you're not phone less. I haven't tried it but others have.
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.
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.