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.
Related
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'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.
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
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.