So im a long time lurker back all the way to the OG Incredible and never experienced a problem like this before. My problem first started with Cyanogen Nightly 71 I had been using it as my daily for a few days when the lockscreen started to no longer function.
The softkeys light up but the display is off and doesn't come back on. I figured restoring would fix the issue but ended with the same result. I've tried restoring older nighties, factory reset, clearing caches, fixing permissions, and installing other ASOP roms like liquid and the CM7.1 "Stable" but as soon as the phone locks it no longer wakes up. Currently i was able to restore to Newts Incredible HD but i cant live without ASOP if you have any ideas on what has happened or how to fix this please help out and thanks in advance.
I had the same issue and for me I switched to 4ext recovery, converted system to ext4 and aosp has worked since
Sent from my Incredible 2 using XDA App
CM 7.1.0.1
A new upload over in the dev section.
CM 7.1.0.1
Compass still an issue, but now there is a direction to post Issues...
Enjoy...
Related
Hello everyone. I'm pretty new to rooting and flashing ROMs and everything. I was playing with my buddy's rooted Incredible (CM 6.0.1) and I was amazed. I just recently rooted my Incredible and flashed a couple different versions of CM with the same outcome. My phone freezes and then reboots randomly after a couple minutes of it being on. I've tried wiping and restoring factory settings, wiping the cache and wiping calvik. I also tried clearing the storage and then flashing the ROM with no luck. Is it possible that CM just doesn't work with my Incredible or is there any possible way to fix the constant reboots? I apologize in advance if this has been covered already. Thanks!
Yes, I had the exact same problems. Impressed with the features, but disappointed with stability. I switched for now to VirtuousROM and have been happy. Also, check forum.cyanogenmod.com. Several people facing the same problem.
Is it just by chance that it's so unstable? My buddy has been running CM 6.0.1 for awhile now with no reboots at all. In any case, thanks for the info. I'll give the cyanogenmod forms a try.
If I recall, CM 6.0.1 had a default overclock of 1.15 which some phones can't handle. But CM 6.0.2 restored default setting to 998 (stock), which should solve the problem!
I tried both CM 6.0.1 and CM 6.0.2 and both had the same results. They both of them did the freeze and reboots over and over again.
I've had great luck with CM nightly builds starting from 9/6 which was released after 6.0.2. I'm currently running the 9/8 nightly. If you decide to try a nightly, do a full wipe first.
Don't feel alone I have struggled with cm as well. Im using. 92 hboot 2.15 radio and still get splash freeze and reboot upon install. I have wiped: data,cache& dalvik...still no success. Any help.would be great. I've tried almost all nightlys rc3 6.0 6 6.1 6.2.
Sent from my ADR6300 using XDA App
Do I need the sd-ext partition to run CM? When I go to wipe everything it always returns with the message "sd-ext partition does not exist" but it still wipes everything else. If so, how do I go about creating that partition? Thanks for all the help.
kirkland signature said:
Do I need the sd-ext partition to run CM? When I go to wipe everything it always returns with the message "sd-ext partition does not exist" but it still wipes everything else. If so, how do I go about creating that partition? Thanks for all the help.
Click to expand...
Click to collapse
You don't need the sd-ext partition. I would download set-cpu, you can find it free on xda, and make sure that it is not overclocking for you.
I purchased set cpu....how would I tell if my cpu is over clocked?
mine is set to 998 max 245 min....still cant install cm6
Has any one found the same install issues as myself.....Ive been trying for at least a month to two months to get cm6. Just tried again tonight got the nightly to work once ...i rebooted and gota stupid bootloop. I tried to install again and just a bootloop this time. Please help!
I justest loaded CM 6.1.2 on my HTC evo and now every time i try to use my camera it freezes and has to force close. Any idea's? I'm new at this whole phone moding thing, so if I left out any important info just tell me. I had someone who is more experienced help me root my phone and load the rom so I don't think I messed up anything there.
Hmmm...that's strange.....I had the CM on my phone, and didn't experience any camera issues. Are you using a custom kernel?
Have you tried clearing the data and cache from the camera and then opening the camera back up? (Settings/Applications/Manage Apps/Camera) This has helped others on certain roms. Not sure on CM though.
Also, agreed with the kernel thing from filmaker. Sometimes that will do it. Try a different one.
Good luck!
I'll try that, thanks. I loaded a different rom on my phone and I'm having some problems with it, I'll reload cm and try what you told me. As to the custom kernel question, I dont believe I do. I also read on the cm forum about CM6.1.2 having issues with the camera pm newer evos and they talked about a fix but I couldn't seem to find it.
Having sorta the same problem... I switched to CM6 and the camera is just buggie... It either wont take a picture, lags really bad or FC's... I've tried clearing the data out of it but that seems to have made it worse.... Any other idea people? Thanks
Oh, I'm runnin CM6 with a stock kernel... maybe try a different kernel? And if so, can I just flash a kernel without changin anything elese like radios and what not?
Well I reinstalled cm and the camera worked prefect for a while but its not working now. I tried what you said and it didn't work. I have the stock kernal as well.
Sent from my PC36100 using XDA App
hhhmm... that's prolly gonna be a deal breaker for me if I can't get it fixed... I use my phone camera quite a bit
Did you wipe data, cache, and dalvik between ROMs? How about system?
Well I know I wiped data, cache and dalvik... and I think I wiped system (If that's an option in to do from recovery then yeah I did)..
What recovery are you using and what rev? When I first tried CM6.1.2 I was using RomManger, which was using ClockWork 3.x.x.x recovery. I couldn't get CM6 to run for more than a day without having issues. I was able to switch to Amon_RA 2.2.1 and flash a few other ROMs which ran fine for days without any issues. I have since loaded up the EvoNonsense 4.3.1 ROM, which feels a lot like Cyanogen but still has Sense, so everything works (4G, HDMI, Camera/Camcorder, etc...). Anywho, not sure if using Amon_RA recovery will fix your Cyanogen issues or not but it may be worth a try. If that doesn't work out then you may want to try the EvoNonsense ROM.
http://forum.xda-developers.com/showthread.php?t=758197
I'm currently using Cm7. I just rooted it tonight and I'm currently not being able to receive txts. I rooted using Revoked and clockwork recovery.
Did I root wrong? I tried wiping and reflashing different wrongs. I also tried downloading different Messaging apps such as: ChompSms and Handcent, still no luck. Please help
Did you update all radio/WiMAX/PRI/NV?
I'm having the same issue. I was running the latest Calukin rom (which has sense) and all of the sudden it stopped, I uninstalled all my apps, nothing, I flashed to mikfroyo, nothing. Updated my prl and profile, nothing.
I experienced a similar issue switching from one CM7 nightly to another, I forget which I was upgrading from/to. To resolve the issue, I restored the nandroid backup of the last working ROM I had, verified things were working again, and reflashed the latest nightly from there. Good luck, hope this helps...
Brian
brianw7761 said:
I experienced a similar issue switching from one CM7 nightly to another, I forget which I was upgrading from/to. To resolve the issue, I restored the nandroid backup of the last working ROM I had, verified things were working again, and reflashed the latest nightly from there. Good luck, hope this helps...
Brian
Click to expand...
Click to collapse
not to thread hijack, but I was running a sense rom and it happened suddenly
I'm haven the same issue wit my CM7 nightly build 29...any way on fixing that problem
Sent from my PC36100 using XDA App
Within 30-40 seconds after opening any application (including the android system ones that auto-load @ boot), they crash ; promting: "__ has stopped unexpectedly. please try again."
Recent changes:
installed avast! (recently uninstalled)
set up swift key X
any ideas/fixes?
on cm7 btw.
As a last resort, if nobody is able to come up with a specific fix for you, I would suggest reflashing the ROM or restoring to factory settings within the ROM. It can be a pain in the butt, but if nothing else works, it's like starting from scratch in the ROM. That tends to be what i do when i have problems that are widespread like that and it always fixes it for me.
Out of curiousity which build of CM7 are you using? I have the latest nightly (420) of 7.2 and it is the most stable and customizable DInc ROM I've tried.
EDIT: I am flashing CM 7.2 RC2 right now, I didn't realize it came out a few days ago. Until further notice though, I still would recommend the nightly just because I haven't really tried this yet, knowing CM though they wouldn't release an RC if it wasn't ready. Hopefully they will start work on CM9 for dinc soon if we cross our fingers.
of course >.<
i believe its a standard build of 7.0.2, i cant check though because settings crashes immediately
ugh.. now its bootlooping.
flashed to 7.2 RC2;
please lock.
vassskk said:
flashed to 7.2 RC2;
please lock.
Click to expand...
Click to collapse
I hope it works out for you!! if you have anymore problems, come on back and someone will try to help you out.
I can't boot cm10 (unofficial) or Evervolv's JB preview ROMs. They both sit at boot screen. Also, Sometime mid July cm9 (unofficial) changed something that breaks my data somehow. Stock browser begins to load but stops and closes. Same with FB app. Any nightly (cm9) I use prior works fine and last Evervolv ICS release works great as well.
Is my Evo outdated? I've heard of some Evo's not handling some ROMs for whatever reason but I haven't heard of anybody having my problems with these new ROMs. I use Smelkus ver RA recovery and I have my SD partitioned, though I rarely use sd-ext. I'm always through on wiping and my hardware is 003 if that helps.
I have a pretty old EVO as well, and haven't had any issues getting any jb up and running. Have you tried redownloading? The most recent one I tried was here http://forum.xda-developers.com/showthread.php?t=1805348 and I liked it, just no camera so I had to go back to an ICS.
If you do a full wipe there shouldn't be any reason why ur not able to run those roms.
Thanks for the input. I flashed the ROM above (With evervolv jb gapps) and decided to wipe everything individually. I'm running JB now! Only thing I did differently was not use combo wipes and try this ROM. I wonder if that's it. Will try other ROMs now.
Just for an update I downloaded new Evervolv JB preview 5 and it booted so not sure what's going on. Unofficial CM10 still won't boot so maybe it is a download issue but I've tried multiple ways (3g and landline). Team Dirt CM10 booted though. I'm scratching my head.....
So basically I am just here to answer your question concerning if your HTC EVO is too old? Why, yes, yes it is, actually, any phone that comes out is usually obsolete within one to two months after debute.
I have booted cm10 to my evo with no problem. I have encountered a few issues with cm10 but that was expected. Can't wait for the camera to work. Only major setback.
Sent from my PC36100 using xda app-developers app