So, I've had CM 10.1.2 installed for about a month with no issues, it has been working great - this is my first experience with a stock Android-based ROM, and I like it more than Touchwiz. Yesterday, I received a notification for an update to CM 10.2 RC. I didn't think about it too much, I wanted to check out the update, so I just downloaded it (I know, I know....I definitely should have read up online about it beforehand).
Once downloaded, I started having an issue with my phone having periodic reboots - it reboots about every ten or fifteen minutes. I figured the issue was with the update, so I flashed back to 10.1.2 - wiped data/factory reset, wiped cache, wiped Dalvik cache, installed the stable 10.1.2 from CM website, installed the compatible Gapps, and rebooted.
Now, I am still getting the reboot issue. What would be the cause of this issue? Would there be something left over from the update yesterday that I could delete?
Thanks for any help!
Maybe this will help you
Might be, because you just updated it and you just overwrite the system so there will be leftovers from the update. I suggest you do a clean flash method which is Wipe Dalvik-Cache , Data , System , and Cache. Flash again the CM10.1.2 or CM10.1.3, there the same but actually I use CM10.1.3 and this time I have no issue of rebooting itself. Causes of reboot might be a bad applications or bad flashing.
Related
i downloaded and flashed cm10 on my phone from xda and it was the att version of cm10. everything works perfectly except it freezes sometimes when in use. i have to reboot phone to make it work. i wiped before flashing and cleared cahe and factory reset and everything and it still freezes. i also downloaded jb gapps from link on xda. any suggestions?
Cm10 is not fully functional its still under construction
CM10 is stated in that thread as being in an "early state". Its basically still beta. If you did a full wipe (particularly data), probably not much else you can do.
If you want the cutting edge, you will have to expect some random bugs and freezes. If its not for you, try a more mature ROM.
ewokiscool said:
i downloaded and flashed cm10 on my phone from xda and it was the att version of cm10. everything works perfectly except it freezes sometimes when in use. i have to reboot phone to make it work. i wiped before flashing and cleared cahe and factory reset and everything and it still freezes. i also downloaded jb gapps from link on xda. any suggestions?
Click to expand...
Click to collapse
I haven't had one single reboot and I've been running it for at least a week(streaming music,playing games,watching vids etc.) and each time I flash a new nightly? All I do is clear both caches then install cm10 nightly plus gapps then clear caches again for good measure then reboot. It's been great for me! In the earlier stages it was worse but too me its quite stable now. :good:
ewokiscool said:
i downloaded and flashed cm10 on my phone from xda and it was the att version of cm10. everything works perfectly except it freezes sometimes when in use. i have to reboot phone to make it work. i wiped before flashing and cleared cahe and factory reset and everything and it still freezes. i also downloaded jb gapps from link on xda. any suggestions?
Click to expand...
Click to collapse
I had CM10 for a while and never had that issue. Make sure to wipe everything (cache, dalvik, factory reset, & system). Hell, do it twice to be sure. Then reflash.
Beginning 4 or 5 days ago, the CM nightlies have become absolutely unusable on my phone. Even after a full clean flash (wipe system/data/cache/dalvik), the first boot will yield multiple force closes, usually including SystemUI and com.android.phone. After a couple reboots these will stop for the most part, but flashing gapps prompts a whole slew of new FCs (pretty much every gapp crashes, along with the accounts manager).
TouchWiz roms, older CM nightlies, and AOKP build 2 all run fine. But I simply cannot get CM to work.
Any ideas?
demonguard said:
Beginning 4 or 5 days ago, the CM nightlies have become absolutely unusable on my phone. Even after a full clean flash (wipe system/data/cache/dalvik), the first boot will yield multiple force closes, usually including SystemUI and com.android.phone. After a couple reboots these will stop for the most part, but flashing gapps prompts a whole slew of new FCs (pretty much every gapp crashes, along with the accounts manager).
TouchWiz roms, older CM nightlies, and AOKP build 2 all run fine. But I simply cannot get CM to work.
Any ideas?
Click to expand...
Click to collapse
I've tried all of the CM10 bases roms and the one that seems to run rock solid for me with zero issues so far is paranoid android, plus I like the things that he cherry picked, I'd give that rom a try as it works super smooth and fast with imo's lean kernel.
natethegreat86 said:
I've tried all of the CM10 bases roms and the one that seems to run rock solid for me with zero issues so far is paranoid android, plus I like the things that he cherry picked, I'd give that rom a try as it works super smooth and fast with imo's lean kernel.
Click to expand...
Click to collapse
That rom actually runs fine for me too, along with anything else based on a CM before ~9/17, but I'd love to know why my phone wont run the newer nightlies.
I have had no issues at all running the CM10 nightlies, works like a champ for me. If you find out what is going on please let us know!
Still having this problem on a clean flash of the 10-04 nightly. Email, gapps, setup wizard, talk, and Play store all chain force close on the first boot.
Your forgetting to format your system in cwm mounts/storage. That's a true clean install. Double check your md5 and try again doing all you did+format system.
Sent from my YP-G70 using xda premium
Hey so I have been having the exact same issue! I flashed back to the M1 snapshot and I'm staying there until this get sorted out. Weird how it's only happening to a couple of us...
Sent from my SCH-I535 using xda premium
Have you guys tried fixing permissions after flashing?
yosterwp said:
Have you guys tried fixing permissions after flashing?
Click to expand...
Click to collapse
So do you think that we should do a full wipe then install, boot, go back into recovery then fix permissions or can we do it without a full wipe?
yosterwp said:
Have you guys tried fixing permissions after flashing?
Click to expand...
Click to collapse
I wiped system, data, cache, and dakvik. Then I installed CM. Then I wiped cache and dalvik, and fixed permissions. Same issues ocurred.
Still having this problem with M2 and the new gapps after formatting and wiping and fixing literally everything.
demonguard said:
Still having this problem with M2 and the new gapps after formatting and wiping and fixing literally everything.
Click to expand...
Click to collapse
What I would do if I were you....
Odin all the way back to stock
Re-root
Re-unlock bootloader
flash cwm
Wipe data/factory reset
wipe cache
wipe dalvik
FORMAT /system <- under mounts
rewipe
install newest cm10
install newest gapps
boot
Odin'ing back and formatting will help wipe out any remnants you may have derp'd along the line somewhere
You should have no issue with these steps. It put me rock solid every single time (along with many many others). Report back and let us know.
Ok bizarre problem guys. I have an international 6810 running Paranoid Android 2.13. I was browsing Facebook on Sunday morning via the app when the tablet rebooted mid scroll.
When it boots it gets right to the 'almost loaded' part of the boot animation where the brightness drops a little bit. However instead of booting to android (and if you've cleared dalvik cache the next thing you would see is the 'Upgrading - 1 of 200' messages there), it reboots and does this cycle endlessly.
I can get into bootloader and recovery (which is currently the first one I installed - CWM 5.5.0.4) and I can Wipe Cache fine, however as soon as try to Wipe Dalvik Cache the tablet reboots, which leads me to think there might be something wrong with the Dalvik Cache? This also (obviously) means I'm unable to do a Wipe Data/Factory Reset as that also attempts to wipe Dalvik Cache and causes a reboot.
I am able to flash roms (though I've only tried reflashing PA 2.13 so far and it will not boot with the same issue described above) and other zips successfully (i can run Aroma scripts without issue and have tried the emmc_scan_all_partitions_once.zip without problem (from a Galaxy Note thread and linked to in the 'How to avoid Superbrick' 7.7 thread)).
I'm looking at the 'Superbrick' thread wondering if I need to move my cache to another area but I'm loathe to do so if its something simple!
Anyone have any ideas?
FYI: After another day of searching I've found this post that appears to be having the same issue: http://forum.xda-developers.com/showpost.php?p=28533566&postcount=155
Gonna try that out and see what happens, will update after.
Uvaavu said:
FYI: After another day of searching I've found this post that appears to be having the same issue: http://forum.xda-developers.com/showpost.php?p=28533566&postcount=155
Gonna try that out and see what happens, will update after.
Click to expand...
Click to collapse
Ok what was described the thread linked above worked fine - seems I needed to overwrite /data to get rid of some sort of corruption. Everything back to normal now, on newest PA.
Uvaavu said:
Ok what was described the thread linked above worked fine - seems I needed to overwrite /data to get rid of some sort of corruption. Everything back to normal now, on newest PA.
Click to expand...
Click to collapse
I'm facing the same problem with mine. Stuck in bootloop until i wipe Dalvik Cache.
What exactly did you do to make it stop bootloop-ing?
Hello XDA,
Sorry for the long post but I am desperate!
The first ROM I ever flashed was CM 10 M2 which ran well and went without any problems. For this I used CWM. I found a stable nightly early in December and decided to update. I also wanted to store my backups on my external however, so I switched to TWRP and created a new backup of my stock TouchWiz rom using TWRP then backed my CM10 M2 up just in case. I flashed the update without wiping the data (factory reset) but did wipe the dalvik cache. This worked fine; all my apps were still there as well as my background. So when GooManager told me there was a 10.1 update for my Rom I thought why not try it out. I figured this was a big update so I wiped dalvik and did a factory reset. After flashing I ended up in a loop of "com.android.something or other has stopped" which turned into "setup wizard has stopped". The homescreen would not load. Fine. Booted into recovery last night after this and reinstalled my latest backup of the nightly I had been using for about 20 days. Seemed OK but the "android activation" screen was taking forever so I pushed home, plugged my phone in and passed out. I Woke up this morning and tried to send a text but it wouldn't send. Tried to call and I couldn't. Now I have restored every recovery I had (Stock, M2, Nightly) multiple times and same problem except that in stock I get a roaming charge warning. I was sure returning to stock would solve this. Does anyone know what I can do? Im not sure exactly how to factory reset but am willing if thats what it takes.
Thanks a ton!
Pups
Try here: http://forum.xda-developers.com/showthread.php?t=2065285. It has worked for several people.
Hi Everyone,
I've been having some trouble getting custom ROMs to fully boot on my girlfriend's Galaxy Tab 2 (p3113). I was able to gain root access (I used this method: http://forum.xda-developers.com/showthread.php?t=2510669) and managed to install the latest CM rom, SlimRom, or OmniRom (with their respective Gapps).
However, I always run into the same problem: whenever I reboot from recovery (regardless of which rom was installed), android begins "optimizing" apps (presumably because I've cleared caches, including dalvik) and at the end, reports 2-3 process that have unexpectedly stopped, and reboots. I've done clean wipes with each install, and even tried re-downloading the roms, but nothing seems to work. Also, it doesn't seem like the stopped processes are consistent between roms. For example, the CM rom would report calendar and keyboard processes that have stopped, whereas Omnirom would report mediastorage and google search processes that have stopped.
Anyone have any ideas of what I can do to fix this?
It sounds like you are not doing a full wipe, I dont think it should be optimizing on a fresh clean install. Try factory reset, wipe cache/dalvik. And possibly system.(usually recomended)
Sent from my SGH-T889 using XDA Premium 4 mobile app
Thanks - that what I suspected as well, although I thought I was doing a full wipe (including /system) in TWRP, but maybe not?
Anyway, I somehow got it working last night after formatting /data and then flashing the last CM stable release (CM-10.1.3, p3110). Got the tablet to boot and setup and everything. Maybe there was something conflicting in the data folder, or that there was no more space on the internal SD. Guess I won't know now..
But I decided to flash the latest Omnirom instead, to get a 4.4 rom. Seems to be working fine now. Thanks for the reply!