I'm running CM6.1.1 currently, but I've been having this issue since before I flashed that. The problem is that the phone, generally when it's been in my pocket (but not always) will lock up in such a way that I can't 'wake' it. The only way to revive it is to pull the battery and reboot.
Other than the phone being idle (in my pocket, on a table, etc..), I can't seem to find any pattern to it. Here's the changes I've made from stock:
Permarooted, subsidy unlock, and s-off via gfree (-f)
Clockword Recovery 3.0.0.5
Eng Hboot
Flashed new radio
Bacontbits OC Kernel (running 245-1305 ondemand)
CM6.1.1
Launcher Pro
1800MaH EVO battery upgrade
Problem is, I did all of this stuff at once, so I can't pinpoint when the behavior started. Any ideas on what could be causing this? Or even how I might track down what happens just before it goes kaput? I guess I could flash it back to stock and start adding things methodically...but what a pain. Also, I'm so hooked on CM, I don't know if I can ever go back to vanilla froyo! :-D
Thanks!
flash the pershoot kernel and see how that goes
it works p. good for me
*shrug*...can't hurt. No lockups yet. We'll see though.
On a related note, I found a somewhat accepted name for my problem...Sleep of Death. Thanks CM forums!
Pershoot seems to have cleared it up. Dunno why, but thanks!
Does Pershoot have a new kernel out?
Related
I am having several major problems with my phone ever since I tried flashing some new stuff over the Skyraider 3.3 final ROM!! Everything was fine, except for the extremely excessive battery drain after I installed the ROM the first time. Then I flashed a splash zip and also the blue battery circle zip and last but not least the #5 kingxklick bfs kernal. Ever since then my phone has gone berserk. When I hold down my power button, not only does the screen for all of the options(hibernation, power down, reboot, etc..) not come up, it just goes straight to my bootanimation screen and it boots back up. Also, the excessive battery drain has gotten worse!! So, I booted back into recovery and did a restore. This seemed to stop the craziness of my phone, unfortunately it still just reboots when I hold the power button down and the excessive battery drain is still going on!!! Anyone have any suggestions? I'm afraid to do anything else because it seems that I have done enough for right now top screw it up!
Make sure you're not overclocking more than your phone can handle (if at all).
I'm running this same combo (SR 3.3/Kingxkernel BFS #5) and it's working quite well for me with good battery life.
If you choose to reinstall, do a complete wipe/cache wipe *twice* from the recovery menu before flashing.
First of all, Thank you very much!! I know this is a dumb question, but how do I check to see if I'm overclocking? I don't know how to do that, obviously. Ha.
that rom is dependant on radio, and HBoot being up to date. If you don't meet both, you will have problems. I had all sorts of issues with 3.3 when I installed it only to find you have to have s-off, 2.15 radio, and .79 Hboot. The reboot problem is more than likely the Hboot, anything below .79 frow what I understand will not support the new hibernation modes, which causes the reboot.
SoCGHOST said:
that rom is dependant on radio, and HBoot being up to date. If you don't meet both, you will have problems. I had all sorts of issues with 3.3 when I installed it only to find you have to have s-off, 2.15 radio, and .79 Hboot. The reboot problem is more than likely the Hboot, anything below .79 frow what I understand will not support the new hibernation modes, which causes the reboot.
Click to expand...
Click to collapse
I was using the hibernation mode every night since it came out on .77 HBOOT with no issues. I only just now updated HBOOT cause I got bored and wanted the newest one lol.. But yeah, was I just lucky? :/
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.
Can't find an answer to this on google or xda. Didn't know if I should post this in General or Q&A.
I have been using my Incredible since it came out. I quickly learned about rooting, roms, s-off... with no problems. I have been running Skyraider almost from the beginning.
Here is the problem: A few days ago, I noticed on the SR thread that there were updates for the radio and hboot. So, I went ahead and flashed them. Almost immediately I started noticing the screen becoming unresponsive. After a minute or two I did a battery pull, rebooted, and again after a little while, freeze and reboot. I also noticed that even when the phone is awake but screen off, it would wake itself up. The rebooting and freezing makes it impossible to use my phone.
I tried everything I could think of:
Nandroid restore (obviously didn't work since this doesn't effect hboot or radio).
Reinstalled fresh SR Rom wiping everything, including dalvik, and did factory reset.
Finally, I downgraded back to the hboot and radio versions I had before, still no effect. (Baseband version 2.15.00.07.28, hboot .79 ).
I tried installing another ROM (Uncommon sense) to make sure it wasn't a ROM issue, ..same problem.
Please, any help would be much appreciated. I don't know what my next step should be.
do you overclock at all?
g00s3y said:
do you overclock at all?
Click to expand...
Click to collapse
No overclocking, I don't use setcpu, and I have been running the stock kernel. But it does feel like overclocking.
I wonder if the timing of events is just coincidence and its a hardware issue. I've had my Inc since June... rooted s -off in july and had no problems until about a month ago. I don't oc I use the new stock kernel but my phone hates change. Even flashing a small mod will cause rebooting.... and navigation always causes it. Phone heats up fast with these particular activities too but sometimes it will reboot at only 35c after a flash. I'm thinking hardware
Sent from my ADR6300 using XDA App
Thanks,
You may be right.
For now things are working, let's hope they stay that way.
I want to preface this by apologizing if this has been covered, but I was unable to find anything with a search.
Every single 3.70 based ROM results in wakelock issues within 24-48 hours. I have tried everything, including flashing the stock rooted rom and no matter what, my phone stops sleeping after a day or so. I fully wipe, flash the rom, and I don't download a single app until the wakelock kicks in, at which point I grab spare parts and get no useful information.
I am currently alternating between CM7 and CM6 because AOSP roms work fine...they just aren't quite as solid as I would like them to be at this point. GPS bugs (I've tried the fixes), no HDMI (I've heard about the beta apps and I'll try those soon), no 4G (I realize this has been added to the nightlies for CM7, but the GPS issues are a deal breaker for now) and slow file transfers between my PC and my phone when using CM7 also kill the rom for me.
I figured I would simply flash the stock rooted 3.30.651.3 so that I could have a fully functional phone without wakelock issues if the need arose. But whenever I try to flash after a full wipe (including dalvik cache), I get stuck on the white HTC EVO screen. All 3.70 roms and AOSP roms flash fine so there must be something I'm missing...do I have to downgrade my radio or something? Any help would be greatly appreciated. And once again, I'm sorry for the post if this has been covered.
Yes the radio has to be downgraded first. I'm not sure which radio you need but you should check out one of Viruses rom threads since his roms are mostly 3.30 based.
Ladies and gents.
First, I realize Saturday is probably not the best day to have an issue, so I appreciate any input I can get.
First, I'm running a rooted (toast method) evo, currently on CM7.
For the longest time, I didn't change roms, and then updated to CM7 a couple of months ago (iirc).
Shortly thereafter, I began experiencing random reboots, my phone getting extremely hot, and sitting through bootloops upon startup.
After upgrading my radio, nothing was solved. I downloaded another CM7 clean and flashed it. Same issues.
I download a Fresh Rom, and was unable to even flash it after wiping continuously.
I nanroided back to my CM7, of course with the same instability issues.
Then I nandroided back to the ROM (damage control, iirc) I had (that was perfectly stable at the time for nearly 1 year) before CM7, and I barely got it booted all the way through before it reset and started looping.
I don't know if it's a hardware issue or a software issue, but I can't flash another ROM to find out.
I was going to unroot today and take it down to Sprint. Of course, I can't get the dadgum thing to restart in a stable manner, so I was going to move the PC36IMG file to my SD card via ClockwordMod recovery.
I get in to the bootloader and choose recovery. My phone resets like normal before entering recovery, except now it enters a bootloop.
Pulled the battery, tried again. Same result.
So if you have any thoughts on any of the issues above (in particular the CM7 stability issues or the recovery issue) I'd love to hear them.
healthpellets said:
Ladies and gents.
First, I realize Saturday is probably not the best day to have an issue, so I appreciate any input I can get.
First, I'm running a rooted (toast method) evo, currently on CM7.
For the longest time, I didn't change roms, and then updated to CM7 a couple of months ago (iirc).
Shortly thereafter, I began experiencing random reboots, my phone getting extremely hot, and sitting through bootloops upon startup.
After upgrading my radio, nothing was solved. I downloaded another CM7 clean and flashed it. Same issues.
I download a Fresh Rom, and was unable to even flash it after wiping continuously.
I nanroided back to my CM7, of course with the same instability issues.
Then I nandroided back to the ROM (damage control, iirc) I had (that was perfectly stable at the time for nearly 1 year) before CM7, and I barely got it booted all the way through before it reset and started looping.
I don't know if it's a hardware issue or a software issue, but I can't flash another ROM to find out.
I was going to unroot today and take it down to Sprint. Of course, I can't get the dadgum thing to restart in a stable manner, so I was going to move the PC36IMG file to my SD card via ClockwordMod recovery.
I get in to the bootloader and choose recovery. My phone resets like normal before entering recovery, except now it enters a bootloop.
Pulled the battery, tried again. Same result.
So if you have any thoughts on any of the issues above (in particular the CM7 stability issues or the recovery issue) I'd love to hear them.
Click to expand...
Click to collapse
Try running a RUU from here.
http://forum.xda-developers.com/showthread.php?t=884060
[Hint, don't run 4.24.651.1 or you'll lose root ]
Since you rooted using Toast's method, I doubt you ever ran unrevoked forever. So run the 3.70 RUU or lower. If you can get into recovery, I'd flash unrevoked forever just to be safe.
Unfortunately your issue sounds like a mixture of problems I've seen others have. If this is the case, worst case scenario is that you'll never be able to boot your phone again if the issues continue... you'll constantly loop regardless of running RUUs, etc. Best case scenario is that you'll always have the bootlooping/overheating issue and eventually have to get a replacement.
Again, these best/worse case scenarios are based on what I've seen others experience. Hopefully the RUU will fix your problems.
Good luck!
Sent from my PC36100 using Tapatalk
Good Afternoon,
I flashed my phone with a bunch of stuff a few weeks ago, and it's been running spectacularly, but the past few days, I've been having some issues getting my phone to boot completely. ADW would keep force closing, and my phone would randomly reboot, and I'd sometimes need to battery-pull to restart it from being frozen completely. Also, my volume buttons no longer work, and the screen occasionally goes 4-split screen from the keyboard opening ( I'm assuming flex ribbon ). Now today, after the the splash screen, the phone screen just goes black and stays like that. From reading around, I think I know what the problem is, but I was wondering if anyone more knowledgable could give some insight as well, specifically, if there's any chance it could be a software issue and **crosses fingers** not a hardware issue. I attached what I could get of the adb logcat.
Also, if it helps, here's some info about my phone:
Rooted & S-Off, with newest radio
Rom: nickmcminn60's XM-8 Vr 1.1
Kernel: Miguel's
Mods: darktremor A2SD & ?Firerat's? Custom MTD Partition
Any help or advice would be much appreciated.
1) don't use Miguel's kernel with these latest builds.
2) did you fix permission with rom manager to help with fc's.
3) I don't think this will fix the screen issues, that's is mostly hardware related.
Sent from my fingertips using Android.
Thanks for the help! I hadn't done fix permissions yet, as last time it somehow broke my rom. Unfortunately, I tried doing a nandroid backup first, yesterday morning before trying fixing permissions, and after my phone finished and rebooted, the phone just froze, and I couldn't reboot into recovery ( my volume buttons don't work ), and after a few reboot attempts, my screen died. I'm going to try ADBing into it tonight if I can.
In case I can get it fixed though, what kernels should I be using instead? I tried drowningchild's, but I seemed to have fewer issues with Miguel's.
Use stock cm kernel when using cm roms if using sense I believe nbetcher has a good kernel
Sent from my fingertips using Android.