I'm currently running Cyanogenmod 6.1.1 stable and every time I try to flash it the rom will at some point within the first 30 minutes of using it reboot. After that point it will start sporadicly rebooting. I've tried everything from flashing the stock rom and flashing back to even unrooting it and rerooting it but nothing has worked. It doesn't seem to be a problem with the rom itself though as I had these same problems running myn's twopointtwo rls4. The odd thing is though that when I run the most recent rooted stock rom I haven't seemed to have these problems. I could be mistaken about the stock one though because I haven't run it for very long. I'm going to try a few things with cyanogen and if I keep having problems I'll probably flash the stock one and see if they go away. But has anybody else had this problem and if so do they know how to fix it?
edit: turns out my battery has some sort of short in it because I replaced it with my spare and haven't had any problems.
Related
I've been rooted for about a month now, playing with various roms and loving it.
However, today, I decided to try FrEak's newest rom using netarchy/toasts latest kernel. Things were going pretty well for a while, then all of a sudden, everything either quit responding or is taking at least a minute to respond, i.e. notification bar, menus opening/closing, touchscreen, etc.
So I did a complete wipe, cache, etc. and flashed the latest BakedSnack rom, again, with netarchy kernel, and same issue.
Does anyone have any suggestions? I'm wondering if going back and re-rooting would help....but if I do, should I use SimpleRoot or the newest unrevoked?
This is killing me!!!!
Last good responding rom I had was Fresh 3.1.0.1, but haven't tried reflashing that to see if it's the roms I'm using or something wrong with my phone.
Thanks in advance.
try a different kernel.
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
Hello everyone, just got a quick question to ask.
I was running CM10 stable and had a problem with my SD card a while back (which I never figured out), so I decided to preform a clean wipe of CM10.0 and a stock rom as a troubleshooting method.
I finally stuck back with CM10.0 and I've been rocking that install for some time, but have a problem. Every fifteen minutes or so the phone's cell connection would drop completely then pick back up a min or so later. It's very temperamental and I have no idea what was causing it. It never inhibited the utility of the phone, so I just dealt with it.
Today I flashed a clean install of Paranoid Android, gs2usr's unofficial version, and it still has the same issue.
I've flash different modems and the issue still remains, but I have no idea where to troubleshoot beyond that.
Any ideas guys?
|EDIT| Solution was taking it back to stock by flashing with Odin then re-rooting and flashing CM10 stable. No issues so far!
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
It's happened several times, last night within a few hours of plugging it in. In one case it must have happened right as I plugged it in because in the morning it had no charge left. The LED is lit (either amber or green) but the phone is completely unresponsive.
I've tried several thing to fix this. At first I just tried different CPU settings and kernels, but it kept freezing. I tried using no kernel (just flashing the ROM an Gapps) but that didn't work. I just tried SuperDuperWipe because I had installed Venom, but that didn't work. I tried fixing permissions but that didn't work either.
Has anybody run into this before? My next step is to flash an earlier CM9 build, then flash over with 9-05. Maybe the 9-05 build is missing something?
I'm S-OFF and running the .320 radio.
Click to expand...
Click to collapse
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
gtdtm said:
Ah the infamous lag of death...I had avoided it for a long time, and I never flashed Viperrom. Anyway. I started getting it here and there about two weeks ago and a fresh rom flash usually fixed it. Until yesterday. My phone was absolutely useless and no combination of wipes and rom flashes did anything about it...until I flashed Andybones stock rom. It hurts being on gingerbread, but it is running smooth. I believe other people have done the same and then been able to go back to ICS or JB AOSP roms later successfully. I'm a little hesitant to try myself, but that's the only advice I can offer.
Click to expand...
Click to collapse
I think SuperDuperWipe got it fixed. I had one lockup and one random reboot since using SDW, and it's been about a week. I consider that stable enough. I had forgotten I used the Viper ROM and needed to "clean the nooks and crannies".
roswell_nightlife said:
I having trouble with Aeroevan's CM9 9-05 freezing overnight, completely locking up and requiring a battery pull. I'm coming back to this ROM after using CM10 for a while, then the official CM7.
Click to expand...
Click to collapse
Try to change the core aeroevan.. I used kernel aeroevan v15 to CM10(Chillybean) with a good result.
Just like people in this thread: http://forum.cyanogenmod.org/topic/70506-freezes-and-re-boots/
I've looked everywhere. but cannot find any answers.
I've been having trouble with constant reboots ever since any ROM released after cm-10.1-20130316-NIGHTLY-d2spr
Today I saw that there is RC2 available so I decided to try it.
I did my best and got rid of all the 0\0\0\0\ folders (only 1 left it seems), updated Clockworkmod (to the newest I think), then installed the newest RC. (clean install).
Everything was going well until about an hour ago the phone began rebooting again.
Does anyone know what the issue is?
OR if anyone else has a suggestion for a non cm-based rom that is good, let me know.
Did you verify md5sum? Try flashing another kernel right after the ROM flash.