Well... HTC One X running 3.2.7 > OTA update to 3.2.8... S-On, factory unlocked.
Has been running fine for 2 months or so now I believe. Today battery went to 0. Which has happened once or twice before. Plugged it in and the orange notification light was flashing (charging, but not usable yet). After an hour or so I held the power button to turn it on and the orange flashing light turned off. And now the phone won't turn on at all. Have still had it plugged in and try to turn on, hold bottom/both volume buttons while holding power... Hold power for 30+ seconds so as to allow it to completely force shutdown... and nothing. No orange flashing light, no screen on, no vibrate, nothing. When plugged in to my PC and I hold the power button for 10 sec it makes the "driver not found" sound. I have HTC USB drivers.
What the f*** happened?
Edit : After unplugging, the orange light now goes, off, on, off, on off (on for 1 second, off for 1 second).... forever.
Going to leave it charging overnight. **** better not be ****ing dead because it's off contract and I don't have the ****ing money to replace a phone because hitting 0% battery caused ****ing death.
Sounds like you're talking about the international one X. Wrong forum partner.
Sent from my One X using xda app-developers app
exad said:
Sounds like you're talking about the international one X. Wrong forum partner.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
What? Viper 3.2.8 is for the evita.
If it won't come on you may have been hit with the bug that quite a few others have experienced here where the phone bricks when the battery goes completely dead. If it's still under warranty I would suggest sending it back to HTC and they will probably give you a new phone. Or send it to mobile tech videos and they'll jtag it for about $60.
Sent from Xparent Red using my Venomized Evita
Oh lol I didnt see him mention viper. My bad
Sent from my Sony Tablet S using xda app-developers app
imranh101 said:
better not be ****ing dead because it's off contract
Click to expand...
Click to collapse
Doesn't matter. It's still under warranty. The phone isn't old enough to be out of warranty yet, it's release date was barely 1 year ago. I'm pretty sure the warranty is 2 years. They also can't void your warranty for running a custom ROM either, unless they can prove the ROM cause the failure which it doesn't sound like it did in your case. I'm pretty sure that holds true in the U.K., and definitely the U.S. The Magnuson Moss act is a powerful tool.
There aren't too many things (software wise) you can do to break this phone to the point where you need HTC to fix it. I, unfortunately, just did one of them to my phone. I'm praying repair is as nice as the support people. They were all awesome, although they wouldn't quote me a repair price even though I told them exactly what was wrong with it and how I broke it.
This is a known bug and has happened to bone stock phones. If you can't revive it, you should get a warranty replacement.
RainWind said:
Doesn't matter. It's still under warranty. The phone isn't old enough to be out of warranty yet, it's release date was barely 1 year ago. I'm pretty sure the warranty is 2 years.
Click to expand...
Click to collapse
Warranty is 1 year. But you are correct, unless the OP bought his right after release, it would be barely over a year old. Any more recent than that, and he is still good.
Keep the phone on the wall charger (not charging over computer's USB port) overnight, and see if that helps. This usually does the trick with the random power drops some of us have seen on this device.
After leaving it charging all night it turns on. However it constantly either freezes and reboots at the splashscreen or just shows the HTC white screen for minutes on end. Got it to boot in to recovery and did factory reset. Got it to boot up and during set up after choosing my WiFi and inputting password then hitting next it rebooted again.
Now what?
imranh101 said:
After leaving it charging all night it turns on. However it constantly either freezes and reboots at the splashscreen or just shows the HTC white screen for minutes on end. Got it to boot in to recovery and did factory reset. Got it to boot up and during set up after choosing my WiFi and inputting password then hitting next it rebooted again.
Now what?
Click to expand...
Click to collapse
Try upping the voltage on the CPU using Kernel tuner, the CPU might have been a tad bit fried and needs a little more juice to run
-Sugardaddy
Arrow44 said:
Try upping the voltage on the CPU using Kernel tuner, the CPU might have been a tad bit fried and needs a little more juice to run
-Sugardaddy
Click to expand...
Click to collapse
Phone won't even turn on. This poses 2 problems.
1. I can't flash kernel or change voltages or anything.
2. Since the sticker fell off the back of my phone, I can't retrieve my IMEI number. Now what the hell do I do?
imranh101 said:
Phone won't even turn on. This poses 2 problems.
1. I can't flash kernel or change voltages or anything.
2. Since the sticker fell off the back of my phone, I can't retrieve my IMEI number. Now what the hell do I do?
Click to expand...
Click to collapse
Pray
Was able to get my IMEI by going to the site where I bought my unlock code and logging in and checking purchases. Will this be enough for the repair people or will they need the sticker on the back to verify something? I emailed HTC and am awaiting response.
Okay latest update. I called HTC and for some stupid reason said I bought the phone used and they said they cant repair it then. I'll call back tomorrow and NOT tell them that.
In the mean time. I actually plugged it in and it turned on. First time got to HTC whitescreen then shut off. Second time got to the Viper XL splashscreen and then shut off.
Any chance this is still fixable?
I'm having the same issue. Left my phone unplugged when I went to bed last night, it had around 60% left. Woke this morning to find it completely dead and no light when I plug it in to indicate charging. Luckily I just got this in Nov or Dec so I should be able to get it replaced.
Related
Hi y'all,
My 3 days old sensation doesn't power up. It's S-Off, rooted and I've been testing different roms on it until I got to the revolution HD. I followed all the steps, Super swiped, flashed it, but the first time I rebooted it didn't power back on; I tried "power+Volume down" and no results.... I've tried removing the battery for an hour or so and trying and it still didn't work.. Kind of pissed cuz I paid the full non subsidized price for it ($530).
Can anyone help?
Thanks in advance
Wow I'm sorry to hear that did you try plugging it into the charger and wait about 20 minutes and see if you can boot it into clockwork mod
Sent from my HTC Sensation 4G using XDA App
Hey so sorry to hear what happened... I can imagine the pain going through..
Can you give some more details?
1. Does it vibrate when you press potter button?
2. Does it show any charging light when you plug in power?
3. try charging for one hour or replace battery with another sensation set as sometimes battery can be culprit
I always try to prevent running that super wipe script since that pays with your partitions...
Elbiba said:
Hi y'all,
My 3 days old sensation doesn't power up. It's S-Off, rooted and I've been testing different roms on it until I got to the revolution HD. I followed all the steps, Super swiped, flashed it, but the first time I rebooted it didn't power back on; I tried "power+Volume down" and no results.... I've tried removing the battery for an hour or so and trying and it still didn't work.. Kind of pissed cuz I paid the full non subsidized price for it ($530).
Can anyone help?
Thanks in advance
Click to expand...
Click to collapse
had your battery ran down all the way?
that happened to me and i had to do a battery swap and forwhatever reason it worked after that. i can still use my other battery no problems.
just something from my experience. might want to think about getting a secondary battery,just in case. 10 dollars.
(does the charging light blink orange 4 times, then nothing?
jjdoctor said:
Hey so sorry to hear what happened... I can imagine the pain going through..
Can you give some more details?
1. Does it vibrate when you press potter button?
2. Does it show any charging light when you plug in power?
3. try charging for one hour or replace battery with another sensation set as sometimes battery can be culprit
I always try to prevent running that super wipe script since that pays with your partitions...
Click to expand...
Click to collapse
rddocke said:
had your battery ran down all the way?
that happened to me and i had to do a battery swap and forwhatever reason it worked after that. i can still use my other battery no problems.
just something from my experience. might want to think about getting a secondary battery,just in case. 10 dollars.
(does the charging light blink orange 4 times, then nothing?
Click to expand...
Click to collapse
jslim38 said:
Wow I'm sorry to hear that did you try plugging it into the charger and wait about 20 minutes and see if you can boot it into clockwork mod
Sent from my HTC Sensation 4G using XDA App
Click to expand...
Click to collapse
Hi All,
1- No, it doesn't do anything. no vibration, no light. It like the battery's been completely drained.
2- Also nothing happens when I try charging it (I only tried charging thru the PC though)
3- I ordered a new battery, so hopefully that would fix it. Whats weird is that when I started the installation process the battery was more than half full.
First of a you need to try and charge from mains, does your pc make any noise or do anything at all when you pop it in?
Sent from my CM7 Sensation XE using xda premium
Sorry to tell you but...Its bricked. Mine just did this last night.
It was charging...Once done, I took it off the charger and set it down. I came back to it later to use it and it was completely dead. No response.
I connected it via usb to my laptop to try the ADB reboot and was told by my computer the DREADED "cannot install drivers". That was the last action that happened.
Tmobile is sending me a new one. Have to go till monday with an old flip phone.
Call Tmobile. They called it hardware failure.
Matt
Holy Crap!!! I just realized what I've done. While browsing my downloads on my PC I found two superwipe zip files: One for the sensation and one for the EeePad... I might have used the Eeepad zip file!!! Damn it! Most probably that's what killed the phone... But whats weird is that even after the superwipe, the phone was on. It didn't die until i decided to reboot it.... DUMB! DUMB!DUMB!
Elbiba said:
Holy Crap!!! I just realized what I've done. While browsing my downloads on my PC I found two superwipe zip files: One for the sensation and one for the EeePad... I might have used the Eeepad zip file!!! Damn it! Most probably that's what killed the phone... But whats weird is that even after the superwipe, the phone was on. It didn't die until i decided to reboot it....
Click to expand...
Click to collapse
I feel your pain. Not knowing what killed it is the worst part. I dont know if it was some ticking time bomb from a ROM, Kernel, theme, or if it was just an honest quality control issue that finally reared its ugly head.
The one clue I have is that when I got my phone on day one, long before rooting and all the magic, it did this to me...ON DAY ONE! After freaking out and doing a battery pull, it finally booted after holding down the power button for a minute. This time, however, its done for. If your PC wont recognize it, then its dead. Simple as that.
Id either call tmobile, or call HTC to see if they will fix it. (They will likely reflash it the elite way if its software related). If its hardware failure, then they will replace it.
I hadnt done anything serious to mine. It just stopped all on its own. The tmobile tech guy said its hardware failure for who knows what reason? I know that my phone has been buggy for a long time. Should have done this back when it was working!
Lesson to be learned: Dont put up with stuff that a warranty exchange can fix. Dont wait for a total brick to occur on its own. If you suspect issues, SWAP IT!
Word to your mother yall...
Matt
So the wife and I were out eating and my phone died. Came home, plugged it up and there was no red led charge indicator..... waited..... and waited.... it's been an hour now, still nothing. If I hold power the capacitive buttons just flash white and go off.
Any ideas on how to bring this thing back to life?.... I purchased from Amazon 2 weeks again and really need a phone now as I have no other phone.
Make sure you are using the original wall charger that comes with the phone.
Sent from my HTC One X using XDA
Press the power button for 2-3 seconds and let go, wait about 5 seconds for it to turn on.....or press and hold volume down and power until the lights blink 6 times then release ONLY the power button. Hold volume button until screen turns on, then using the volume buttons highlight fastboot, press power button to select, then highlight reboot and press power again that'll get u going again
Sent from my HTC One X using xda premium
You will need to replace your phone. Search the forums and you will find a thread or two about this same problem. I had to return my phone because of the same exact problem. The only solution is to completely let the battery die and then recharge for 30 minutes to an hour and then the phone should turn on. But I highly recommend you get it exchanged because the next time you use it, it will suddenly turn off while there is still some battery left and you will have to let the battery die.
same problem. gotta get htc to replace dat shiet.
Leave it on the charger for several hours, wall charger not USB, and see if it helps.
Could be various things. But one thing that has happened to some people, on various Android phones, is that the battery voltage may have dropped too low. Not zero, but too low for the phone to take a charge. In that case, there is no way to bring the battery back to life, except with special battery meters with a "boost" function (which most of use don't have access to). Leaving it on the wall charger has brought phones back for a few people. Its a longshot, but can't hurt.
Safety circuit is supposed to prevent voltage from dropping too low like this. But its not fail safe.
I know that is not what the OP is doing, just a sidenote: Some people will suggest draining the phone until it shuts down to calibrate the battery meter Its a poor idea, for the reason that the safety circuit may not always work properly. When calibrating the meter, its more than sufficient to drain to 10-20%. The meter is not that accurate anyway, and draining to zero doesn't make it any more accurate than 10-20%.
i tried that all, letting it die. letting it charge, everything.
Press and hold the power button while plugging the charger in
Sent from my HTC One XL using xda premium
didnt work. but when i plug it in to windows, i still get apx
swordsx48 said:
didnt work. but when i plug it in to windows, i still get apx
Click to expand...
Click to collapse
This happened to my EVO 3d and had to be replaced.
Other than trying a ruu back to stock I'm out of ideas
Sent from my HTC One XL using xda premium
It comes up as apx? Have u tried
Adb devices
and
fastboot devices
While plugged in to see if either recognize it??
if one of them do than this should be a simple fix.
If adb recognizes it then
adb reboot
If fastboot recognizes it do
fastboot erase cache
fastboot reboot
i tried adb devices and fastboot devices while plugged in and neither recognize it you gave me a sliver of hope
swordsx48 said:
didnt work. but when i plug it in to windows, i still get apx
Click to expand...
Click to collapse
Apx mode is tegra thing. Wrong forum.
Sent from my HTC One XL using xda app-developers app
sorry,i was googling and came across this thread and didnt notice.
swordsx48 said:
sorry,i was googling and came across this thread and didnt notice.
Click to expand...
Click to collapse
No worries.
Mine did the same thing. Went 100% dead. After a few random reboots the days leading up, it finally went off when I noticed it had really low battery. Never to come back on.
Not even getting the red light at the top so put it in for a repair through my Telco (Telstra), (who are apparently the authorised repairer for HTC in Aus) and the mainboard was replaced. Got it back a week later fixed.
Phone had been unlocked through HTCDev but had no issues with warranty. Obviously a hardware fault as couldn't even boot.
on other phones i find using a charger that doesn't have a removable usb cable works well, and don't try to charge it from the computer.
monstermm said:
Mine did the same thing. Went 100% dead. After a few random reboots the days leading up, it finally went off when I noticed it had really low battery. Never to come back on.
Not even getting the red light at the top so put it in for a repair through my Telco (Telstra), (who are apparently the authorised repairer for HTC in Aus) and the mainboard was replaced. Got it back a week later fixed.
Phone had been unlocked through HTCDev but had no issues with warranty. Obviously a hardware fault as couldn't even boot.
Click to expand...
Click to collapse
after one hour of wall-plugging, the unit gains some heat around the camera, but no signs of charging...damn, guess I have to ask for replacement...
eh...did you root/unlock bootloader/flash roms?
I'm kinda worried that Rogers will give me a hassle for that...although it's a battery problem...
nvm...need to work on my reading skills...so unlocking bootloader is fine....
So my phone has now been useless for two weeks. I can't even understand the problem. It started running ViperXL 3.2.4 and Elemental X 4.something. All with stock voltages. Then randomly, my phone wouldn't turn on. No red light would come on when charging, button combos didn't do anything. But if I left it sitting for a day it would eventually turn back on with a dead battery. I got rid of the ROM completely and went to 4.2.2 AOKP. The same exact thing happened, except worse. It seems to not respond to anything for two days now. I finally was able to get it responding enough to RUU to stock. I immediately unlocked the bootloader and then after rebooting -- dead again. So now my phone is sitting dead, waiting for it to respond so I can put it back to stock and just leave it there.
I'm stumped, I have absolutely no idea what's going wrong and I need some help. Thanks for any advice
Sounds like something is going on such as a hardware fault... Maybe a bad battery...does anything show up when you plug into the computer
Only when it starts becoming active and button combos semi work and the LED turns on when charging
Sent from my Nexus 7 using xda app-developers app
you do know overclocking will eventually kill your phone right? same as overclocking a computer.
Yes, but I have only overclocked by 200mhz. That takes the life of the CPU from 7 to 5 years. That is not what is causing this
Using the wall charger (no USB to computer) to charge, right? If so, and since its acted like this across ROMs and after RUU, I agree its sounding like a hardware failure.
This phone has some defect with power management that has plagued people to various degrees from the beginning. Other people have seen their phones die in similar fashions.
Sounds like you're ready for a warranty claim.
I switched off my phone for a day and then today when I tried putting it for charge (when the phone was still off) the battery charging sign came for just a second and then stopped. And since then my phone won't turn on.
I don't even know what to do since I don't know what went wrong. It didn't get wet, I didn't bang it anywhere...
The phone won't turn on so I can't get to download mode or recovery
I already tried letting it charge for about 1 hour but still nothing happens
Mohit12 said:
I switched off my phone for a day and then today when I tried putting it for charge (when the phone was still off) the battery charging sign came for just a second and then stopped. And since then my phone won't turn on.
I don't even know what to do since I don't know what went wrong. It didn't get wet, I didn't bang it anywhere...
The phone won't turn on so I can't get to download mode or recovery
I already tried letting it charge for about 1 hour but still nothing happens
Click to expand...
Click to collapse
2 reason first you battery is broken secind hard brick or sudden death
Do you have custom rom?
Sent from my GT-I8160P using xda app-developers app
It could be screen problem definitely, same happened to me, so i had to take it to Samsung's center where they gave me new Galaxy 3/Apollo.
It happens because of overclocking or underclocking even by undervoltaging your device. So next time take care.
Sent from my Galaxy SIV using xda app-developers app
My battery is relatively new (bought a year ago) and I didn't flash my phone recently.
I am using a custom ROM though. I haven't overclocked my device or undervolted it.
Hmm it's possible that the screen isn't working. I'll switch on the phone and try calling on it to see if it shows as switched off or if it rings. Then I'll come to know if it's a screen fault
I'll report back soon. Thanks!
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.