I saw a post about this on the CyanogenMod Forums with no response so I thought I'd try here.
I have an Incredible 2 running Cyanogen Mod 7 Nightly 85. The morning after I installed 85, I installed 87 but was unable to send/receive any texts. I restored a backup and waited a few days but when I tried Nightly 90 last night, I had the same problem. I'm really clueless as to why and the only other thing I've heard is someone from asking on the CyanogenMod forums with just one unhelpful response.
Any ideas would be greatly appreciated! Thanks in advance!
Ryan
The newest nightlies are broken in regards to the radio working after wifi is enabled and disabled. Flash 85 again and you should be good
Sent from my Incredible 2 using Tapatalk
Flash 85 again and I should be good meaning I should be able to flash the newer ones without problem or will they still be "broken"? Whats the cause of this?
I mean wipe your cache and flash nightly 85 over anything you are running that's higher that that.
I just read a post that said 91 is working fine with no bugs but the ones between 85 abd 91 are broken for some reason. Not sure of the cause, just something went wrong in the building of the roms
Sent from my Incredible 2 using Tapatalk
I've waited a few days and still have had no success. I've wiped the cache and installed 85 before 93 (the latest). Nothings working. Any ideas?
Reflash nightly 85 and do not flash any other nightly builds. Wipe data/factory reset, wipe cache, wipe davlik cache first. YOU DO NOT WANT TO FLASH ANY NIGHTLY BUILDS AFTER 85, ALL ARE NOT WORKING. Keep an eye on the CM7 thread when a new build comes out that is functioning properly then you can flash over nightly 85.
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'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
Hi All,
My T-Mobile G2 running Cyanogenmod 7.0 randomly reboots itself throughout the day (average 3 times a day). I want to find out what's causing it. Is there any way to find out what the phone was "thinking" at the time of the reboot? I tried a logcat but it only seems to go as far back as the time it was last turned on.
Here's some additional info in case people know a solution. The reboots did not seem to start until I installed CM 7.0.2. They became more and more frequent over time peaking at about once every 2 hours. I did a full wipe (factory reset, wiped the dalvik and system) and reflashed 7.0.2 and the problem persisted. I did another full wipe, reverted to CM 7.0 and the problem is tolerable at least, but still there. Any suggestions? Thanks in advance for your replies!
My Android Version is 2.3.3, Baseband version is 12.22.60.09bU_26.02.01.15_M2 and my kernel is listed as 2.6.32.28-cyanogenmod-g4f4ee2e [email protected] #1.
Firstly try updating your Radio to a newer one because that looks like the stock one rolled out with your Desire Z. Then if it still reboots reflash a stable version of cyanogen. Then if it seems stable you can try flashing your preferred kernel onto it.
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...
Okay so I have CyanogenMod and I am still running nightly 56. About a month or two ago, my screen became unresponsive in certain areas. I was told that it was a hardware issue and required replacement, but I am really unsure about how to unroot, so I haven't returned it to stock. Today, as I took my phone off Airplane Mode, the dbm signal meter read -1 and I had no service. No matter what I do (battery pull, wipe cache, on/off airplane mode) I don't get signal. Has anybody else experienced this before? Or do I finally need to face my fear of unrooting my phone and sending it in?
Are you still rooted and running cm7? did you play around with the network options in settings? This sometimes causes no signal issues if not done correctly. I would try flashing 56 again after you wipe cache and dalvik, or flash the newest 100 nightly or cm7 stable build, both which have been reported to work now.
I have always had issues with cm7 on my inc2. From the earlier days to current versions. It is like my phone doesn't like aosp tons. I always have inconsistent signal and my highest battery drainer is cell.
Sent from my Incredible Sensation using xda premium
MJL99 said:
Are you still rooted and running cm7? did you play around with the network options in settings? This sometimes causes no signal issues if not done correctly. I would try flashing 56 again after you wipe cache and dalvik, or flash the newest 100 nightly or cm7 stable build, both which have been reported to work now.
Click to expand...
Click to collapse
So you think this is a software issue, not a hardware issue with the radio? And is it okay to jump from nightly 56 to nightly 100 without a full wipe? Thank you so much for your help.
yes it is ok to jump without a full wipe. just wipe cache and dalvik. and the only way to tell if its a software issue is to try different roms. try a newer nightly and if that gives you problems try a sense based rom and if it still doesnt work then it might be a hardware issue.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Okay. I overcame my fear of unrooting and I'm stock now. The signal does work, so you were right, it was a software problem. My screen is still unresponsive though. I switched to stock, but my phone is now 2.2.1. Will that be a problem for returning it for a replacement?