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!
Related
I've rooted my phone for the first time the other day and started venturing into the custom ROM's realm, but so far all I got were dramas and failures.
I started by downloading Cyanogen 6.1.1 and 7 RC1. I thought I'll try each to see how they perform. So I copied them to the sd-card, along with the radio update that was recommended on the Cyanogen 7 RC1 thread, and rebooted to Clockswork recovery. I wiped my data and cache and went on with the ROM installation followed by the radio update (notice that I skipped the backup stage. stupid, I know).
Upon booting, I immediately noticed that I have no signal, and a force close message that says: "the process com.android.phone has stopped unexpectedly. Please try again" pops up every 2 seconds. Nothing happens when the message is dismissed, mind you, but it still comes up constantly every couple of seconds. This, along with the 'no signal' thing, rendered the phone unusable.
At this point I'm thinking that maybe my phone is just not reacting well to the non-final build of the Cyanogen 7, so I gave the stable Cyanogen 6.1.1 a go. Lo and behold, same thing happens with it also. Now panic kicks in when I realize that I have no backup, and no stock ROM to go back to.
Eventually, I downloaded the latest rooted Desire 2.2 ROM, got it into my sd-card and installed it. Thankfully, everything was working properly again. After some asking around in the Cyanogen forum, it got to my attention that the update to the radio might have caused all of this trouble, and that the installation of the stock ROM brought the previous radio version with it, which solved the problem. But when I tried to install Cyanogen again, without tinkering with the radio, same thing happened. I then tried Oxygen 2, thinking that maybe my device just doesn't like Cyanogen, but the exact same problem persisted.
Anyone have any idea what's the deal here?
Did you wipe dalvik cache after flashing the roms?
Sent from my HTC Desire using Tapatalk
I wiped the cache partition before I flashed. It didn't say 'dalvik' specificaly, just 'cache partition'. I never wiped any type of cache *after* the flashing process.
You should wipe the dalvik cache after (or just before) flashing roms.
You can find it under the advanced menu in clockworkmod recovery.
Sent from my HTC Desire using Tapatalk
Alright, tried wiping the Dalvik Cache after flashing, problem still persists.
You could try downloading another radio and trying it. Even if it's not the recommended one, an older radio works better for some people. There is no such thing as 'the best radio to use', since result may have large variations for different people (in different locations, using different phones and ROMs). Just browse the radios post and pick one
Btw, since the dalvik cache is stored at /data/dalvik-cache, wiping the /data partition implies deleting the dalvik cache
Well, since the radio that I have installed now works, and since it stays the same one after installing a different ROM, it seems to me that the radio is not the problem here. I really would like to stay away from tinkering with the radio stuff...
Bump.
This really bugs me that it wont work. I feel like I'm missing out on the biggest feature of having a rooted phone...
Hmm... I've found that if I force the phone into Airplane mode, the FC messages stop. Of course, I still have no signal.
So, the reason for the FC messages is due to the failure to connect to my mobile network. Now, why would I be able to connect to my network fine on the official Desire ROM, but not on any other ROM?
If all else fails you could always trying flashing the RUU for your phone then start from the beginning and root again if you've tried everything else.
Sent from my HTC Desire using XDA App
Ok, I'll try that.
Just a quick question. After I run the RUU and the device is unrooted, will I be able to recover my nandroid backup fully after I re-root?
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.
hope someone can help, been changing roms, sense and non sense for last 3 weeks and had no problems at all until yesterday. last 24 hours I have had reboots almost every 10 mins. actually it is ok for about 1 hour after flashing the rom and boot image which is about enough time to get it set up to my liking, then the rebooting starts. I have flashed the boot image from each rom correctly in fastboot and erased cache before and after flashing boot. flashed roms in recovery after doing a wipe and all have worked perfectly first time. the problems started 1 hour after flashing the latest slimbean, I wiped and flashed latest cm10.1 nightly this morning with same results after 1 hour. hopefulley ther are attacments for the last_kmsg and logcat below, if I've done it right :fingers-crossed:
had to split txt file in 2, it was too big
Bump
Sent from my HTC One X using xda premium
Have you tried to not "set it up to your liking"?
Maybe there is a bug with an app installed?
Did you tried other Roms?
Does the problem only happen when then screen is off?
Maybe also try an other scaling governor?!
By setting up to my liking I just meant the settings of the Roms before any apps are installed, and yes I have tried about nine different Roms. Late last night I discovered something interesting, when I started flashing Roms, about 3 weeks ago I intended to try a few and settle with the one I liked most, I tried them in this order :- cm10.1, pa3, Slimbean, icecoldjelly, miui and viperx 3.5 and 3.6. All of these went without any problems and I decided I liked Slimbean the best so reflashed that. That is when the reboots started, I then put cm10 back on and miui but still reboots. Then last night I flashed viperx 3.6 and not one single reboot! I noticed when viper was flashing, via aroma, a line popped up saying " formatting EXT4 ". Now if you look at the known CM10.1 issues below the installation instructions for cm10.1 nightlies, it states you must be formatted VFAT(HTC standard) as it does not support EXT4. This whole problem started after going from viperx back to slim and cm10.1. So is this possibly something to do with the EXT4 formatting of viperx ? and if so can I re-format to vfat ?. After searching I can only find reference to formatting fat32. are fat32 and vfat one and the same thing ?.
Sent from my HTC One X using xda premium
Sorted, I think
decided to flash CWM 5840 touch, formatted and wiped everything, using every option available, copied over slim rom 4.2, flashed boot, flashed rom and gapps and I've had it working for 2 hours now without any reboots. so keeping fingers and everything crossed , including my grannys knickers, for the rest of the day, cya peeps
Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )
nabeelmoeen said:
Hi,
I had CM 10.2 running fine on my HOX. A couple of weeks ago I decided to test out CM11, since this is not my primary device, stability wasn't that big of a concern for me. The first few tries CM11 installation was a failure with some error (I can't recall) occurring when installing the zip in Recovery (if i remember correctly it had something to do with version of recovery I was using).
Anyways, I searched online, found a solution and was able to install the CM11. I have flashed the boot, erased the cache, tried wiping/factory resetting the device, in all kinds of orders (wiping/installing/flashing boot.img, flasing boot.img/installing CM11, etc). but no matter what I try my phone always stays stuck at the boot animation.
I found multiple threads on the forums with similar problems, but in most cases the OP was either missing flashing boot.img or erasing the cache helped. not so in my case.
Also, weirdly enough, now even if i try to reinstall CM 10.2 (which was working earlier), I get the same issue.
any further guidance on troubleshooting / overcoming this issue is highly appreciate
HOX International H__J15
HBOOT 1.31
CWM Touch Recovery 6.0.4.8
(btw, just tried Beanstalk ROM, same issue... I dont know what I F'd up on this phone!! )
Click to expand...
Click to collapse
Your HBOOT is to low you must to upgrade ti 1.39 or 1.72 but 1.31 is tooo low and for this the CM11 don't boot
Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version
nabeelmoeen said:
Actually I think 1.31 is the latest version which came out with jelly bean rom for the htc__15 id.
what's frustrating is that I can't even get the 10.2 version of CM working again either...which should be fine with this hboot version
Click to expand...
Click to collapse
try restore stock and chek for update restore nandroid and see I am not sure J15 is only 1.31
Will give it a shot tonight and report back. ...what's grinding my gears is none of the other roms including jb ones I tried are working either
i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!
nabeelmoeen said:
i finally managed to resolve my issue. I tried changing recoveries, tried multiple ROMs and also tried to run RUU (which failed since i have a later version of the ROM vs. what's available in RUU).
finally decided to try formatting the boot, System and Cache partitions and installing CM11 again.
I had never used the 'format <partition>' feature before. Apparently this did the trick and now i am running CM11 .!!
Click to expand...
Click to collapse
is HBOOT still the same version or did you upgrade it?
I am curious about the order in which you did things. After formatting boot, system and cache partitions, did you flash the boot image again or did you do that prior to the formatting.
Thanks