My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Are you doing Apps to SD? It could be your card.
Did you move any caches?
Do you have any nandroid backups? (just fastboot flash if so)
Did you recently try to update to anything and fail?
Try to use the update.zip again. If that doesn't work then start over from scrap.
bsander said:
My phone worked perfectly for a few days with ADP1.5H r3 on it, but now it refuses to boot, it seems to be looping forever. The blue android logo comes up, but the "shining" animation stops moving after usually 1-2 seconds, then the screen flashes back and the same thing repeats over and over again. I have already tried a wipe earlier, but now I'm having the same problem again. Any clues on what causes this or (better) how to fix this?
Click to expand...
Click to collapse
Wipe worked for me. It was sticking on the Android flash screen, but worked after the wipe.
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
In answer to binary: yeah I do apps on SD but I've been doing that since ADP1.1, so I doubt the card is the problem. Didn't move any caches. Yeah I have a nandroid backup, and all the updates I did went smoothly. I had the whole system working for about 2 days until this happened (probably, because this was the first time I rebooted since installing Contact Owner, though I can't really remember that 100%)
bsander said:
Yeah, a wipe fixes it. Later today I stumbled upon a thread which suggested the problem is the "Contact Owner" app that doesn't play nice. Can anyone confirm that?
Click to expand...
Click to collapse
Contact Owner caused my phone to go into a reboot loop, but that was on the 5.02H build. I haven't had the guts to try it on JF1.5 or 1.5Hr3. If you look through the market comments for Contact Owner you'll see quite a few complaints of the same issue.
Hi there,
And sorry for reviving this old thread. I am the developer of Contact Owner an I kinda need your help in debugging this issue. I got a small number of messages from users of custom builds a while ago (about a month or two) but thought it was an issue with those builds.
Now it came back to bite me in the ass, as it seems the HTC builds in various countries (Canada, Sweden, South Africa) have the same issue: the phone goes into a reboot loop. I've tried (and failed) to install a custom build on my dev phone (almost bricked it) so I'm going to ask nicely if someone is willing to debug the issue for me. Please, please, please!
All that's needed is to install and run Contact Owner and if the device goes into a reboot loop, simply attach it to USB, run 'adb logcat' and then post the output. To recover from the reboot loop, simply start in 'safe mode' (hold Menu down while booting) and then uninstall Contact Owner.
I suspect the problem lies in SQLite, because I've seen similar complaints from Klaxon users and that app also sets the alarm message (which then ends up in a SQLite db, I guess). The Alarm Clock app that comes with Android also does that but I imagine it's because the message set by Alarm Clock is always short and has no newlines. I also don't think the issue is in Dalvik code, because the device should not crash if managed code causes an error.
TIA,
Paranoid Android.
Please help me with this recurring error. The message occurs consistently upon boot-up and then randomly.
"The application cyanogenmod setting (processcom.cyanogenmod.cmparts) has stopped unexpectedly. Please try again."
I am currently running nightly 34 with the default kernel, but have had the same error with previous builds and various other kernels. Sometimes it starts up immediately after flash, sometimes starts later. This last time after 20 hours without the error, it appeared to start immediately after changing themes with Theme Chooser. I have not seen any functional problems resulting from this error; it is just really irritating.
Swype appeared to stop working at the same time (changing theme), but was fixed by reinstalling.
I solved my own problem. Previously I was using OC/UV kernel and had "Set on boot" under CPU settings checked. Must have been restored along with my apps and data. I unchecked it and the problem went away. Apparently the error was caused by asking the program to do something that it couldn't. Previous similar problems probably had a different cause but Nightly 34 seems to be real close to a RC, all functions are running flawlessly and stable. Congrats to the CM team!
Thankyou so much, I was having the same problem on my x10 but wasn't receiving any mature suggestions on what may be the cause... Thankyou
Sent from my X10 using XDA App
I'm testing the new Endless7 build and I'm having problem sliding out notifications. When I slide one notification it gets stuck some pixels at the right and then the notification system doesn't work anymore (but the phone works).
Is there a way of restarting the notification system? I've tried restarting the launcher, but that, obviously, didn't fix the thing.
The only way I found is to restart the phone
no more...
It fixed alone... don't know how but today the problem wasn't there anymore...
no, my mistake
It didn't fix it. It's just that it doesn't happens verytime but from time to time.
Does anyone has a solution that doesn't involve restarting the phone?
Install ROM Toolbox from market (needs root)
Go to "Rebooter" and "Restart status bar"
Thx!
Thanks Marius! You're THE man. You saved me countless hours of rebooting
Until Endless7 fix that bug I have to reboot my M2 every now and there
i dont know why but all of a sudden every few minutes when i use the tablet it will all of a sudden freeze and the error "Unfortunately, the process com.google.process.gapps has stopped" i am just on stock rooted and i didnt change any system files around. it doesnt seem to have any effect outside of the freeze, but its still really annoying. any ideas short of doing a factory reset?
Hi, i started getting with with the team alliance ROM, factory reset and clear Dalvik, came back after a while. Switched to latest rooted stock, same as you, started getting it again. Seems to be a bit random, haven't been able to tie it to anything specific and luckily it doesnt happen that often at all.
I installed this on my HTC Vivid and have had no issues with that process. The one issue I do have though is when I return to my home screen from an app. It seems that the launcher or some other running part of the phone reboots when I do this and it displays the HTC logo. It doesn't take long for the logo to go away, and after it does it displays a loading window for a few seconds. After this everything goes back to working normal.
This happens every time without fail and while it doesn't seem to be causing many problems, it is quite annoying.
Does anyone know how to stop this?
Edit
Ok so I apparently missed the step where I was supposed to flash the boot.img before installing the ROM. I only did it afterwards. No problems now.