Quick background: I purchased a One X from AT&T a few weeks ago. It came with the 2.20 firmware, so I used the X-Factor Exploit and unlocked the bootloader via HTCDev. From there I flashed TWRP Recovery and then AOKP.
Pretty much everything was fine at that point, except for the fact that once or twice a day I would pull my phone out of my pocket and it would be completely unresponsive. None of the buttons would wake the phone up, plugging it in didn't do anything, and it wouldn't receive calls. I would then have to do a hard reboot (Power + Volume Down) to get anywhere.
I thought maybe it was an AOSP problem, so I flashed a Sense-based ROM (CleanROM 5). I experienced the same issue.
From there, I re-locked the bootloader and ran the latest RUU. That was 4 days ago and I have yet to experience the problem again.
Has anybody else experienced this, and is there any way to prevent it?
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
redpoint73 said:
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
Click to expand...
Click to collapse
I would just select reboot and it would boot normally. Power alone would also work, I believe. I usually just did power and vol down out of habit I guess.
GPS and WiFi were always on.
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
c5satellite2 said:
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
HBoot 1.14. Didn't mess with the radio, so the stock AT&T 2.20 one (0.19as.32.09.11_2_10.105.32.25L).
Yes, I flashed the correct kernel. It did it with both the plain AOKP kernel and rohan's kernel.
Cleared caches several times.
GPS on when this happens, by any chance?
redpoint73 said:
GPS on when this happens, by any chance?
Click to expand...
Click to collapse
I hardly ever disable it, so it was likely on. No idea if it was actually in use any of the times.
I can say one time it happened immediately after a call, one time it was immediately after a SMS notification, and the rest just seemed to be randomly in the middle of the day.
Try going straight to CR5 directly from the stock ruu rom and see if it persists. Maybe the aokp Rom borked something along the way and the ruu has restored it now. I have seen issues similar to this that only the ruu will fix.
Sent from my HTC One X using xda app-developers app
Have the same issue.Try going to ViperXl and see what happens.My phone constantly reboots and enters sleep of death.I always have the gps disabled.have 1.09 hboot.And currently I am on 1.85 stock at&t.This issue is kikling me
I only mention GPS, since my old phone (Desire Z) had an issue where leaving the GPS on, would make the phone shutdown, and only a battery pull would start it (never tried going into hboot). Which sounds similar to what you were seeing. In my case, no ROM, kernel, or radio flashing ever remedied it. And I could isolate the issue to the GPS being on. If the GPS was used, the phone was going to black screen within a couple hours, without fail. But rebooting the phone after using the GPS (and shutting off GPS) prevented it every time. A few other owners of the DZ had the same problem. One guy sent his into HTC, and they told him it was a defect of the GPRS module, and replaced the motherboard, which fixed the problem.
Hopefully, its not a similar hardware issue in your case. But the fact that you have the GPS on all the time, and the black screen hasn't cropped up like clockwork (like it did in my case) seems to point to the fact that it might not be the exact same issue.
These types of issues tend to be really hard to troubleshoot (and pinpoint the cause). In my case, it took me a couple months to realize it was the GPS, since I usually have it off, and don't use it all that often (usually just when travelling). And I also suffered a lot of "placebo effect" type incidents while flashing various ROMs and kernels trying to fix the issue. If the issue doesn't crop up again after running the RUU, I'd consider myself lucky, and leave it well enough alone.
No it is not the same problem redpoint73.This only happens on Custom ROMS.I have tried every combo on the 3 ROMS i flashed.Could it be an int.d problem???My only is this.
nighthawk696969 said:
No it is not the same problem redpoint73.This only happens on Custom ROMS.
Click to expand...
Click to collapse
Yeah, I already said its probably not the same problem. But it doesn't hurt to check everything. As I mentioned, its easy to get sucked into thinking you have the cause isolated, when you really do not.
I understand what you're saying but i have checked it,i'm sure..
nighthawk696969 said:
I understand what you're saying but i have checked it,i'm sure..
Click to expand...
Click to collapse
It also doesn't sound like your problem is exactly the same as the OPs. You mention reboots, while OP does not (just BSOD, or shutdown requiring rebooting in hboot).
No my main problem are the Sleeps of Death.There are no BSODs in android
nighthawk696969 said:
No my main problem are the Sleeps of Death.There are no BSODs in android
Click to expand...
Click to collapse
Some people have been calling this condition BSOD = Black screen of death. Yes, its a little too derivative of things like Windows blue screen, XBox RROD etc. But you get the idea.
Update: I re-unlocked the bootloader and flashed CM 10.0.0 upon its release. I've yet to encounter this issue, so I'm thinking my stint on CleanROM might have buggered something. I probably forgot to wipe something somewhere along the line. D'oh.
I am, however, having a pretty severe albeit unrelated problem with an app called Voxer. Every time I listen to a message it kills the microphone until I Force Stop the app. I guess I'll pop over to one of the other AOSP ROMs and see if it persists.
I was having a similar problem on king kang and pacman. I could turn the phone on and off with the power button, but the touch screen was completely unresponsive. Happened randomly, I would have to hold the power button down and watch the lights flash until the phone shut down, and would be fine after a reboot. When I tried installing viperxl, I had the same issue during the aroma installer, I had to try flashing it 7-8 times, because it kept freezing during the install. No issues running it after a successful install. I was using king kang and rohans b5 kernel when it was happening most often
Related
I only noticed this after flashing CM7.1 stable. Never saw it on RC1.
For some reason, any time I power off the phone, it immediately turns on again. If I pull the battery and put it back in, it turns on again. I can't seem to do anything to keep the phone powered off short of keeping the battery out.
I can't imagine how the ROM could cause this, but is anyone else experiencing the same issue? Maybe it's a bug in Clockwork Recovery?
Sent from my HTC Glacier using Tapatalk
It might not be the ROM or clockwork at all. One of my OLD phones that was just a basic Samsung slider did that same thing and I had to take the battery out to get it to stay off.
Try switching roms or even unrooting and re-rooting. If that doesn't do anything then its most likely a hardware problem and you should unroot it and bring it to t mobile.
Sent from my HTC Glacier using xda premium
Power button stuck.
Sent from my HTC Glacier using xda premium
It's the HTC Panache from Mobilicity, not from T-Mobile, but same hardware. And I'm using it on WIND, so I hope warranty won't be an issue.
It's not the power button because the button works fine in all contexts. When I sleep the phone it stays slept. It's just that when I power it off, it pops back up again.
I tried rolling back to an older Clockwork recovery. No change. Logically this function should probably be controlled by the bootloader. I know I have the bad eMMC but no obvious symptoms of failure. Is this perhaps a sign that it's starting to fail?
Sent from my HTC Glacier using Tapatalk
Update: if the phone is plugged into power when I turn it off, it stays off. Once I unplug it, within 5 seconds it boots up again.
Sent from my Nook Color!
Update: I took a full Titanium Backup and a full nandroid backup, and then tried flashing back via PD15IMG.zip to the original Mobilicity HTC Sense ROM.
Once Fast Boot is disabled (as that results in a "fake shutdown"), if I power off the phone... one, two, three, four, five, and it comes back on. So this doesn't seem to be related to the ROM after all. Something has gone weird with the phone that prevents a full hardware shutdown.
Fortunately this is the only hardware problem I'm experiencing. So now I'll have to think about whether to bring this in for warranty. Restoring the Nandroid to CM for now...
EDIT: Well this is interesting. After restoring the nandroid backup, I selected power off in CWM and it powered off... and stayed off! Puzzling.
Booting back into CM7.1, and powering off one more time. Drumroll... and it stays off!
Well... I guess I... fixed it? *shakes head*
I had the same issue with an earlier nightly of CM7. In fact, it was probably multiple builds.
I think clearing cache/dalvik cache probably would fix it. I had a confusing moment where suddenly it stayed off as well, hasn't bothered me since.
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium
Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!
I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?
I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.
Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.
He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O
@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves
Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!
Ok so I have a rogers skyrocket and it's been random rebooting and vibrating in 1 or 2 sec intervals wile the camera flash flashes on and off I've search but have found no answers I've wiped the phone 3 times and flashed rogers stock but it still persists any ideas guys only thing I haven't tryed is odin.
Probably a sticky power button. Although the camera flash is weird. It's a common problem. Search stuck power button
Sent from the short bus
Ya I figured that thought I'd ask thx I'll have to grab a #0 phillups tomarrow
I had this exact same issue on the UCLL3 leak for AT&T. I got out whenever I would flash gs2user's mods on top of the odexed stock version. It required me to reflash my ROM.
Sent from my SGH-I727 using xda app-developers app
Well I've reflashed stock rogers and wiped 3 times before and after flash so I hope that fixes it skyrockets not my daily driver but my friendwants to borrow it so I hope I fixed it up
xstokerx said:
Ok so I have a rogers skyrocket and it's been random rebooting and vibrating in 1 or 2 sec intervals wile the camera flash flashes on and off I've search but have found no answers I've wiped the phone 3 times and flashed rogers stock but it still persists any ideas guys only thing I haven't tryed is odin.
Click to expand...
Click to collapse
I flashed the same ROM on both my son's phone and mine. Exact same phones. Exact same ROM exact same steps. His did this as well but mine never did. I wiped everything, and reformatted the system/data 3 times and reflashed. It did it every time. I ended up putting him back on CM10. Mine never did it and his hasn't since...go figure
phone reboots and vibrates
tobesedated said:
I flashed the same ROM on both my son's phone and mine. Exact same phones. Exact same ROM exact same steps. His did this as well but mine never did. I wiped everything, and reformatted the system/data 3 times and reflashed. It did it every time. I ended up putting him back on CM10. Mine never did it and his hasn't since...go figure
Click to expand...
Click to collapse
So, do you think it was a sticky power button? I have been having this problem for a while now, and it is VERY FRUSTRATING! I love my phone but I hate this problem. I have done a lot of internet searching on this topic, all which suggests a sticky/dirty buttun. However, I disassembled my phone and found NO dirt. I cleaned it anyway, to get rid of any invisible dirt, but its back. Basically, every week this happens to me for a day or so.
I am running ICS (seanzscreams) and hadn't had this problem for the first few months. I am thinking of reflashing my phone to see if that helps.
If any can add additional insight, I would appreciate it. Not particularly in the mood to reflash, but it would be better than a broke phone!
(PS: vibrate/reboot only...no funky camera flash issue)
as-ny said:
So, do you think it was a sticky power button? I have been having this problem for a while now, and it is VERY FRUSTRATING! I love my phone but I hate this problem. I have done a lot of internet searching on this topic, all which suggests a sticky/dirty buttun. However, I disassembled my phone and found NO dirt. I cleaned it anyway, to get rid of any invisible dirt, but its back. Basically, every week this happens to me for a day or so.
I am running ICS (seanzscreams) and hadn't had this problem for the first few months. I am thinking of reflashing my phone to see if that helps.
If any can add additional insight, I would appreciate it. Not particularly in the mood to reflash, but it would be better than a broke phone!
(PS: vibrate/reboot only...no funky camera flash issue)
Click to expand...
Click to collapse
Seems odd to me that it would be a sticky power button for one ROM and not another, but then I can't figure for the life of me why mine worked fine and his didn't. Twilight phone zone lol
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Ya so I cleaned mine and still it does it I odined back to stock still dose it I'm at my wits end its pissing me off
OK so I odined back to stock factory reset stock then flashed twrp in odin then updated twrp and flashed the super light cm10 with gapps haven't had a reboot yet fingers crossed that it worked must be a software thing I got no clue.
OK update my phone started doing this again to day did it like 6 or 7 times FML its defently a hardware problem.
I'd have to agree that it's a hardware problem
I wiped my phone shortly after my post and did a clean install of seanscreamz newer ROM as well as TWRP. Problem continued to happen...actually worse than before. But at that point I had yet to put a single app on it, so an issue of incompatibility of my apps and ROM did not seem to be the case. I then wiped my phone AGAIN, and di a clean install of CWMR and CM10 (I went from ICS to JB), figuring maybe a TOTAL change would do the trick. Not the case.
The phone still randomly reboots, but now that I am certain it is a problem with the power button, I know how to deal with it, and can minimize te recurrence and my frustration levels. I read a post that said someone else had the same problem, and smacked his phone on his desk repeatedly on the power button, and the problem stopped. I didn't do that, but when the problem occurs, I will repeatedly hit the bower button, or if my otterbox case if off, I will stick my nail into the button to pull it out.
It's too bad, 'cause it's a great phone otherwise!
I got an app called tap tap tap and it uses the proxy sensor to unlock the phone and adds a widget in the notification bar to lock the phone works great then my power button does not get stuck Cuz I don't need to push it.
I began posting this problem in a previous thread but am starting a new one to avoid clogging said thread.
Here are my phone details at the moment:
S-Off
SuperCID
HBoot 2.14
Radio 0-24p.32.09.06
Open-DSP-v34.1.0.45.1219
I bought the phone used off kijiji. It was stock when I got it. Rogers, Android 4.1, 3.17 firmware. I unlocked the bootloader, got SuperCID and S-Off, flashed TWRP and flashed a custom ROM - CleanROM. Things were okay for a bit.
Then I started getting random restarts and losing signal. I realized I was on 2.14 hboot so I updated to 2.15. I thought it fixed the problem but no- before long, more random reboots--though I did fix the signal issue.
So I flashed Beastmode kernal. Now, I did this without doing a full wipe - just threw it on top of CleanRom. Possibly a bad idea because everything kinda got all screwy at this point. The phone started acting really oddly--freezing a lot, restarting even more often, and sometimes the touchscreen would act up.
Next step: I tried to do a full wipe and flash a different ROM: KickDroid. Only thing was, it wouldn't flash. The installer would crash, most of the time at 30%. The phone would then restart, though it wouldn't boot (obviously), so I'd have to hold down the volume to put it into the bootloader.
Tried flashing CleanROM then - no go. It wouldn't flash either - phone would just power down.
This became a theme. The phone would just start turning itself off all the time. Even sometimes when I was doing a wipe in TWRP, the thing would just crash partway through and turn off. Somehow, this morning, I DID manage to get CleanROM to flash, but then it wouldn't boot- froze at the Google splash screen and turned off...
On timmaaa's suggestion at this point I went to an RUU and tried to get the phone back to stock. Went with the 3.18 Cingular RUU. For whatever reason, it didn't work the first time (might have been my fault - I forgot to uninstall HTC Sync Manager) but when I tried it again, it did. I was excited - phone was, hopefully, back to its old self, after all!
Booting to splash screen: freezes on the HTC logo. Turns off, randomly. AAGGHH!!!
So I try again, knowing, at this point, it's futile. The phone BEGINS to boot up. Gets to the Cingular screen and then just enters into Android - says it's going to start refreshing apps or whatever... and then it turns off.
Note that I have it sitting in the bootloader right now and it is not turning off. The bootloader itself seems to work well enough.
Even now, I tried to boot the thing up just one more time, and it again just nearly got into Android but turned off before fully loading.
I'm at a loss. It's not like I've been just randomly flashing things on here - I only used ROMs that worked for the phone. Maybe my dirty flash (is that the right terminology) of Beastmode was the problem, but I feel like it shouldn't continue to persist this long, after using an RUU. I'm wondering if perhaps it's a hardware issue at this point.
Any thoughts, ideas, suggestions, etc. are amazing... thank you.
At this point I believe you've tried pretty much everything you could try. It's possible you have a faulty motherboard.
Sent from my Evita
timmaaa said:
At this point I believe you've tried pretty much everything you could try. It's possible you have a faulty motherboard.
Sent from my Evita
Click to expand...
Click to collapse
Darn. Anything that can be done about that? Is it feasible or even worth it to try to replace it?
Get this - it just booted to Android, and seems to be staying there. For the time being, anyway.
Edit: never mind. lol. Turned right off again after connecting to wifi.
It all depends on whether you think it's worth the money to repair it, or just to buy a new device.
Alright. Thanks a lot for your help. I'll try to consider my options.
Try running a different RUU. Not sure of it will help just a suggestion
Sent from my HTC One XL using xda app-developers app
johnnyp12321 said:
Try running a different RUU. Not sure of it will help just a suggestion
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yeah, I'll give that a shot, too. Thanks. Though I'm not that optimistic at this point, lol.
On a related note: I have the opportunity to buy an HTC One XL with a broken screen for cheap. What do you guys think the options are for me (a) taking the mobo out of the broken one and using it in mine or (b) replacing the screen on the broken one with the working one from mine? Do you know how difficult/manageable either process is?
The phone seems to be more or less completely dead now. It will occasionally power up but can't do much beyond the bootloader. Anyone have any experience replacing motherboards on the HTC One XL? Is it possible to swap one out from a working phone? Or is it possible to use my screen to replace one on a phone with a broken screen?
This has been a pain in the butt because I've missed morning alarms just to find our my phone is sitting in the bright white screen of derp. This time I need to know, is this an issue for people in general or could this be a ROM issue?
HTC M8 used the $25 unlocking tool and slapped CM 12.1 on this beast. My advanced reboot menu is OFF in developer options. There is no fastboot or whatever from the stock ROM as far as I can tell. Nothing is pressing on the screen as its just face up on the ground. What can I do, what should I try?
EDIT (8/28/15): After trying a sense based rom the issue went away. Just followed the advice given below
Gevork Gevorkyan said:
This has been a pain in the butt because I've missed morning alarms just to find our my phone is sitting in the bright white screen of derp. This time I need to know, is this an issue for people in general or could this be a ROM issue?
HTC M8 used the $25 unlocking tool and slapped CM 12.1 on this beast. My advanced reboot menu is OFF in developer options. There is no fastboot or whatever from the stock ROM as far as I can tell. Nothing is pressing on the screen as its just face up on the ground. What can I do, what should I try?
Click to expand...
Click to collapse
Does this happen every night?
If it occurs often.. I would honestly just try flashing a Sense ROM for a few days and see what happens. At least you will know in a few days instead of pulling your hair out.
If it still reboots in Sense, probably a hardware problem
If it doesn't reboot anymore, probably a software glitch in CM
So after wondering "maybe the USB cable plugged into my wall charger causes it to somehow go to fastboot mode"... I just had a reboot at work. Had a youtube video open, I hit pause and turned off the screen, and slid the phone into my pocket. No sound, no vib no indications, 5 minutes later I check and find out that its in fastboot mode. So its not from the USB.
I'll try to install a Sense 7 ROM and see how that goes. Very frustrating.
The only other issue I have is GPS not updating quickly enough, it only catches my location approximately and only if WiFi is enabled even if its not connected...
I've only had issues with a bad boot.img, but i couldn't boot the ROM at all. I would try a different ROM & see if that is the issue
---------- Post added at 09:50 PM ---------- Previous post was at 09:49 PM ----------
What ROM are you on? Just plan CM
Same issue here, running Candy ROM. Never see this before, it's almost made me miss my alarms.
Gevork Gevorkyan said:
So after wondering "maybe the USB cable plugged into my wall charger causes it to somehow go to fastboot mode"... I just had a reboot at work. Had a youtube video open, I hit pause and turned off the screen, and slid the phone into my pocket. No sound, no vib no indications, 5 minutes later I check and find out that its in fastboot mode. So its not from the USB.
I'll try to install a Sense 7 ROM and see how that goes. Very frustrating.
The only other issue I have is GPS not updating quickly enough, it only catches my location approximately and only if WiFi is enabled even if its not connected...
Click to expand...
Click to collapse
Any luck with Sense ROMs?
It happened to Me while on BlissPop,and Sonic Open Kang when I had root,it would take two reboots to get my phone back running
Sent from my HTC6525LVW using XDA Premium 4 mobile app
I have the same problem. I seems to be completely random. It only happens when plugged in overnight. Also, I have to select reboot twice to get the phone to reboot. The first try doesn't work.
HTC M8 running The latest Candy ROM.
gmoe65 said:
It happened to Me while on BlissPop,and Sonic Open Kang when I had root,it would take two reboots to get my phone back running
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You say when you had root. Did it stop when you turned root off?
I had to get a replacement phone,and it came back with lollipop 5.0.1
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Gevork Gevorkyan said:
This has been a pain in the butt because I've missed morning alarms just to find our my phone is sitting in the bright white screen of derp. This time I need to know, is this an issue for people in general or could this be a ROM issue?
HTC M8 used the $25 unlocking tool and slapped CM 12.1 on this beast. My advanced reboot menu is OFF in developer options. There is no fastboot or whatever from the stock ROM as far as I can tell. Nothing is pressing on the screen as its just face up on the ground. What can I do, what should I try?
Click to expand...
Click to collapse
Did you install the right GAPPS package for that CM?
Did you fac reset before new OS install?
Fastboot was an option with KK, it is not an option with lollipop.
I use CleanRom 4.0 which is 5.0.1 based, no issues. Sense 6 based. Does not need GAPPS. If your gonna tryout other ROMs, I would try CR 4 for the M8. If it does not reboot auto like then maybe its the CM ver you used or maybe it did not load right. I like CR because it has been cleaned of all carrier software. Has only what you need to function as a phone and mini surf machine, lets you do the customization.
Hope you solve it.
luck
spyknee said:
Did you install the right GAPPS package for that CM?
Did you fac reset before new OS install?
Fastboot was an option with KK, it is not an option with lollipop.
I use CleanRom 4.0 which is 5.0.1 based, no issues. Sense 6 based. Does not need GAPPS. If your gonna tryout other ROMs, I would try CR 4 for the M8. If it does not reboot auto like then maybe its the CM ver you used or maybe it did not load right. I like CR because it has been cleaned of all carrier software. Has only what you need to function as a phone and mini surf machine, lets you do the customization.
Hope you solve it.
luck
Click to expand...
Click to collapse
I'm on Candy ROM which I believe is based off 5.1.1 CM12.1. I flashed GAPPS only after the installation and did a full wipe beforehand. After sticking with a N6 so long I don't really like the Sense layout anymore.
The method I used as per CleanRom guide.
Get 2.8.5 TWRP installed, a must for lollipop.
Make a nandroid backup.
Get firmware for Android 5 installed, carrier dependent!
Factory reset from bootloader
Install Sense or AOSP rom android 5.x.x.
if Sense based your done, if AOSP based install GAPPS ver for your OS/rom
Installing lollipop without right FW could cause issues.
Installing FW can brick your device! so be sure its right one, and make sure you get a nandroid backup stored on your added sd card. More importantly do not just take my word, double and triple check all steps before you leap.
I'll be honest I haven't really tried anything because I don't want to go through the hassle of installing and using other ROMs. Mainly because I think it's hard, even though I know it isn't :silly:
I've been just kinda dealing with the occasional random fastboot reboots. Same thing I have to press reboot twice to reboot the phone, and it happens both when plugged in and charging and when just sitting idle in my pocket. But it's never happened while I was using the phone.
Gevork Gevorkyan said:
I'll be honest I haven't really tried anything because I don't want to go through the hassle of installing and using other ROMs. Mainly because I think it's hard, even though I know it isn't :silly:
I've been just kinda dealing with the occasional random fastboot reboots. Same thing I have to press reboot twice to reboot the phone, and it happens both when plugged in and charging and when just sitting idle in my pocket. But it's never happened while I was using the phone.
Click to expand...
Click to collapse
I've been rebooting the phone every night. So far I haven't run into the issue, and I've never had my phone reboot in my pocket.
Gevork Gevorkyan said:
I'll be honest I haven't really tried anything because I don't want to go through the hassle of installing and using other ROMs. Mainly because I think it's hard, even though I know it isn't :silly:
I've been just kinda dealing with the occasional random fastboot reboots. Same thing I have to press reboot twice to reboot the phone, and it happens both when plugged in and charging and when just sitting idle in my pocket. But it's never happened while I was using the phone.
Click to expand...
Click to collapse
Flash another ROM, or reflash CM. Make sure you wipe first. It was probably a bad flash and something is bonked. It'll take you less than 30 mins. I bet that'll take care of your issue. Good luck.
After many months now of using a sense based rom I've yet to run into the fastboot reset problem. I'm going to switch back to CM this weekend and see where it takes me.