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.
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!
Hi All,
Been having a problem with the touchscreen randomly becoming unresponsive or the phone rebooting on its own ever since when I'm (trying) to run MIUI ROMs.
By "random" I mean that it sometimes occurs while typing, switching home screens, opening an app, or even just when the phone's idle.
Not experiencing any unexpected FCs throughout the MIUI ROMs that I've tried however... so at least that's a good thing?
I don't experience any of these problems at all when running a stock Sense ROM, so I'm hoping it's not the same rebooting problem described in another thread that requires sending it in for repairs as that would be very troublesome.
The phone's a HKCSL Desire that was rooted using unRevoked. The problems occur even when I don't install any apps onto the phone and when the phone's just idle with the screen off (for randomly rebooting).
Any suggestions would be greatly appreciated =) and I hope I'm not just SOL for MIUI ROMs since no one else seems to really be having these problems.
---
List of things I've tried:
1. Full wipe with Dalvik & cache before flashing a ROM (many, many times)
2. Updating to 32.48.00.32U_5.11.05.14 radio and downgrading to the suggested 32.44.00.32U_5.09.05.30_2 (Thought it might've been caused by WiFi connection as I always have it on... but doesn't seem like it)
3. Using different versions of Clockworkmod (2.5.0.7, 2.5.0.1, 2.5.0.1 modified by MIUI.cn)
4. Repartitioning/formatting SDCard before/after flashing a new ROM
5. RUU-ing the phone and redoing everything from scratch
6. Using an untranslated base MIUI-Desire ROM
7. "Upgrading" the ROM by flashing on top of the 10.15 build
Versions of MIUI ROMs I've tried:
Pretty much all the releases of 10.15 and 10.22. Currently fiddling around with eevek's stock 10.29 and mobiousdigital et al.'s 10.29 builds.
Hopeful bump =)
Hey all, I have only been flashing custom ROMs onto my G2 for about a month now, so this might be a dumb oversight. Ever since RC4, I have had an issue where every single time I reboot or power off the phone and power it back on, I get the HTC screen for a few seconds and then the CyanogenMod 7 splash screen with the arrow going round and round. And that's it. Even overnight. Now the ROM runs BEAUTIFULLY all the time. No GPS, Google Sych, or Battery Life Issues. Love it, so any help that would allow me to stick with this ROM would be great.
I am running CM 7.0.0
.26 Radio
the base CM7 kernel (2.6.32.28)
Overclocked to 1017Mhz
What should I do to get this issue to stop?
SpeedBlue47 said:
Hey all, I have only been flashing custom ROMs onto my G2 for about a month now, so this might be a dumb oversight. Ever since RC4, I have had an issue where every single time I reboot or power off the phone and power it back on, I get the HTC screen for a few seconds and then the CyanogenMod 7 splash screen with the arrow going round and round. And that's it. Even overnight. Now the ROM runs BEAUTIFULLY all the time. No GPS, Google Sych, or Battery Life Issues. Love it, so any help that would allow me to stick with this ROM would be great.
I am running CM 7.0.0
.26 Radio
the base CM7 kernel (2.6.32.28)
Overclocked to 1017Mhz
What should I do to get this issue to stop?
Click to expand...
Click to collapse
Have you tried a full wipe and then reflash? What rom did you come from? A few details about those things might make it easier for people to help u
dont send me pm's crying about how i hurt your feelings in a thread
I came from the stock post-ota ROM. I did a full wipe when I installed RC4, but I haven't since, just wipe data then re-flash. Should I wipe everything - data, cache, dalvik, etc and then re-flash? Of course Nandroid before...
just cache and dalvik was enough... no data wipe needed (at least.. I haven't needed that before)
But I still need to re-flash the ROM after I clear cache and Dalvik though, right?
Well, apparently, that worked out. Everything is humming along just fine. Thanks a lot for the help everyone.
Hi there. Currently im using HTC one x and its been 3 months im using it. The day that i bought the phone was using ics and then i'd updated it to jelly bean. since then, my phone start rebooting for no reason. Then i try to root and using custom rom so i hope that my phone will be stable but the result was disappointing. It still rebooting. then last week i change back to stock rom and hope it will be the same as the first day i bought that is without rebooting. but still the result was same and it kept rebooting. Can someone please help me and guide me because this is my first android phone and currently i dont know what to do anymore. I still want to keep this phone. Thank you
After all that you tried its probably a hardware related, but theres still hope tho.
How long does it take for it to reboot, is it consistent or random?
Also what ROM, kernel Hboot version etc. could be useful.
My Hox has a similar problem.
It keeps rebooting for no apparent reason. It does so 10-15 times in a row, and the stops for an hour or two and then repeats.
It is 8 month old and it only reasonly started doing that.
I run ViperX 3.3.8
Hboot: 1.39.0000
Don't know if these are the ones needed:
Kernel:
3.1.10
[email protected] #5
Hi,
I have been using custom roms for a while on my note II N7100. From my last rom my phone was restarting on its own at least once a day and complete freezing quite a few times. Only solution was to reboot the phone by holding the power button for few seconds, nothing else would work. Even tried leaving the phone for 10-15 minutes however it did not help.
I was using Carbon Rom earlier. I changed Liquidsmooth 2.9 however the same thing happened. In fact the frequency increased with Liquidsmooth. I was worried about a hardware problem as even after complete wipe and with different rom same thing was happening.
I decided to perform a complete factory reset, wipe cache/dalvik cache. After flashing liquidsmooth 2.9 I did not flashed the gapps, used the phone for couple of hours and things were fine. After I flashed the requied gapps - gapps-jb-20130301 - same thing started happening.
Somebody please let me know if I can flash the earlier version of Gapps or later version if available.
Regards