Just like people in this thread: http://forum.cyanogenmod.org/topic/70506-freezes-and-re-boots/
I've looked everywhere. but cannot find any answers.
I've been having trouble with constant reboots ever since any ROM released after cm-10.1-20130316-NIGHTLY-d2spr
Today I saw that there is RC2 available so I decided to try it.
I did my best and got rid of all the 0\0\0\0\ folders (only 1 left it seems), updated Clockworkmod (to the newest I think), then installed the newest RC. (clean install).
Everything was going well until about an hour ago the phone began rebooting again.
Does anyone know what the issue is?
OR if anyone else has a suggestion for a non cm-based rom that is good, let me know.
Did you verify md5sum? Try flashing another kernel right after the ROM flash.
Related
I'm currently running Cyanogenmod 6.1.1 stable and every time I try to flash it the rom will at some point within the first 30 minutes of using it reboot. After that point it will start sporadicly rebooting. I've tried everything from flashing the stock rom and flashing back to even unrooting it and rerooting it but nothing has worked. It doesn't seem to be a problem with the rom itself though as I had these same problems running myn's twopointtwo rls4. The odd thing is though that when I run the most recent rooted stock rom I haven't seemed to have these problems. I could be mistaken about the stock one though because I haven't run it for very long. I'm going to try a few things with cyanogen and if I keep having problems I'll probably flash the stock one and see if they go away. But has anybody else had this problem and if so do they know how to fix it?
edit: turns out my battery has some sort of short in it because I replaced it with my spare and haven't had any problems.
Hi,
So yesterday i was walking the dog listening to some music when my phone just died. I booted it back up again, listened some more and it died again. When this happened i was running version 1.2.0 of said mod, so i decided to try the latest.
Seems like i have this issue there aswell Everytime my phone goes into lock it shuts down. Anyone have an idea what can cause this? my phone is almost a year and a half.
Update: Removed my memorycard and no problems so far, will try to format it and let you know.
Update 2: Formatted SD-card, seems to be working again now.
Update 3: Nope, its back again. Any ideas?
Thanks to everyone for any help on this
Juji
Try installing the test version of 1.4 and do a full wipe before that.
You should also try and flash any other ROM (maybe even stock) to make sure it's a ROM issue and not some HW fault on your phone.
Do we have any chance to have a 2wcr kernel for this great ROM?
I have the same 1-2 times per day after calling with
Virtuous Quattro RC3
so maybe a bug in ICS ?
Have been running without any force shutdowns for over 24hours now, so it might have been temporary for me atleast.
I got no problems so far with ICS on DHD, flashing from 1.2.0 to 1.4.0 without full wipe. I think different phones get different issus with same ROM. Maybe the installed apps are a reason for that.
I had that bug, but I was running Gingerbread at the time. The problem worked itself out, around the same time I upgraded the SD card. That might be a cause, maybe re-seat the sd card? Might be loose or something along those lines.
I'm running 1.5.0 and mine keeps saying no network and keeps rebooting itself????
Hi there!
I installed
http://forum.xda-developers.com/showthread.php?t=1912187
with basbeand 77 instead of the recommended ones, and it appeared to work just fine for two days.
Today, I installed the LBE Guard, and so my Desire was stuck in bootloop, which I could get out of after a fullwipe and a new install.
So, then, I installed the LBE privace Master (v4.3.2738),
http://forum.xda-developers.com/showthread.php?t=1422479
because I read it was okay for JB. While configuring it, my phone crashed, and I was again stuck in a bootloop. I tried to make a fullwipe again, and a new install, but I have still these random (but appearing soon after booting) crashings and then a bootloop. It even appears when I use the Aroma Installer, but not in the CWM.
So my question is - what went wrong and more importantly, how do I get my phone to work again?
Thanks for replying.
The part with the baseband is wrong - that was my other phone.
I am quite the noob-cookie, I also have the problem with random reboots and freezes. I have been messing around with the new Nikez 4.2 Jellybean Rom, i thought that could be the reason why. But now I am also experiencing it with the old Nikez 4.1 Rom that used to be very stable for me. Anyone know a good solution? I have done several full wipes..
Cheers!
So I've decided to start playing around with custom ROMs. I'm still pretty new to Android so maybe this is going to be stupidly simple.
Earlier today I flashed PACman Rom. Downloaded directly from the thread. I wasn't super happy with how slow it ran and a friend suggested it might be a nightly. I noticed in settings it said the release was from 09/09 so I thought he might be right. I decided to wipe it and install the most recent stable version of PAC man.
Seemed to flash just fine, but the startup was a bit odd. It didn't go through the standard stuff like syncing your google account, setting up wifi, etc. Jumped right to the home screen. At first that didn't seem like an issue. I can do that all manually. But then it flashed on screen saying AOSP keyboard couldn't launch. Obviously without being able to type at all or even open the keyboard, I can't do a whole lot to get it set up.
Tried a couple times to flash that ROM and same thing every time. Restored from my nandroid and everything worked perfectly. Decided to try CyanogenMod and got 10.2 stable release with gapps. Wiped and flashed. Same thing. Straight to the home screen, no keyboard. Every other gapp is there.
Any ideas on what I can do differently? Or what I might be doing wrong, or some way I can get this to work?
Did you flash gapps with pacman ROM?
Sent from my Galaxy Nexus
Yes I did. And I actually just figured out what it was. I was using 4.3 gapps with 4.2.2 ROMS
So I have CM12 installed, but when I go to flash the latest nightlys I keep getting System UI crashing. When I acknowledge it, the error will not go away. I have HBOOT 3.18 and radio 1.19 with TWRP 2.8.4.0. I've wiped everything I can think of save the internal and external SDCARDs. What am I doing wrong to not be able to flash the latest nightlys? Ive tried flashing on top of my current CM12, which was upgraded from CM11, and wiping clean. When I wiped clean everything was working great till the phone went to sleep. When I woke it up, same issues.
Yeah, I was having that issue as well. CM12 just isn't stable right now, at least for me. Everything lagged after having the phone on for about a half hour, took 4-5 seconds to do anything after selecting it... it was just a mess. Went back to stock.
Everything runs like a champ, I just cant flash the latest version. It seems that I'm the only one having this issue, or no one cares to help anyone anymore.
Tobb555 said:
Everything runs like a champ, I just cant flash the latest version. It seems that I'm the only one having this issue, or no one cares to help anyone anymore.
Click to expand...
Click to collapse
Okay, I have cleared off a bunch of crap off my phone and am willing to give CM12 a try just to see if you have the issue. Which CM12 version are you referring to?
Thanks for the help. Right now Im running version 12-20150128-NIGHTLY-m8. When I try to update to any of the latest versions Im getting the System UI crashes. It doesnt matter how many times I acknowledge it, it wont go away.