I'm on the PAC ROM. Always worked great, with some minor issues. Today, I received a message on Whatsapp and, suddenly, trying to open it, both from the notification drawer and from the app drawer, caused phone to reboot. I tried killing the process from settings, it rebooted before loading all the running apps. After that, I've not been able to run anything without causing a reboot. Why is that and how can it be solved?
EDIT: I understood it is Smart App Protector's fault: every app works fine except that and all the locked apps. Trying to uninstall or stop it causes the phone to reboot, as well. Any idea on how to solve this?
Try wipe data/factory reset.
if the problem remains unsolved:
re-flash your rom (clean flash).
you can backup your data through recovery.
regards
ASMI1 said:
Try wipe data/factory reset.
if the problem remains unsolved:
re-flash your rom (clean flash).
you can backup your data through recovery.
regards
Click to expand...
Click to collapse
Thank you very much, it works now. But Google Play is stuck on the loading screen... Any solution to avoid reflashing?
EDIT: Nevermind, it is magically running again.
Pkmns said:
Thank you very much, it works now. But Google Play is stuck on the loading screen... Any solution to avoid reflashing?
EDIT: Nevermind, it is magically running again.
Click to expand...
Click to collapse
Yup, this is because Google play have to update itself and change interface directly after each data wipe
best regards
Related
hey all,
on friday I rooted my NS again to check out cm7 rc1. before i was totally stock @ 2.3.2. friday evening i wanted to show my iphone friends the nexus s with cm7. the first one took it and did take some photos. then he smiled and gave it back to me. force close: SORRY: Android.process(???) has stopped unexpectedly.
this error was looping all the thime. i pressed okay and one sec later it was there again. i tried to flash the rom again in recovery, but the error was still there. i did date and cash wipes and some factory resets and then the error was gone.
on sunday i was travelling home on train and suddenly the error was back. i tried again some wipes and then i deceided to restore my nandroid backup. so i was back on 2.3.2. during sunday afternoon and evening i got these errors:
- NS is freezing while it is in standby... if i grab the phone and want to unlock it but the display keeps black -> i have to put out the battery..
- NS is beside my keyboard and suddenly all four buttons are on. display is still black. unlock not possible--> battery again
- NS is freezing while using facebook or twitter app
today... i unrooted it again and went back to a nandroid (2.3.1) guided _here_.
after unrooted again NS wanted to update to 2.3.2 which i confirmed.
about to hours later the errors i explained came back.
am i the first one who bricked NS?
please give me some help how to get it back working correctly, because i love this phone so hard.
I did another factory reset and now the phone is hanging at the google Logo. The four buttons are powered.
This is looping, too.
Yesterday I tried some things to kill these errors. I did:
- factoy reset (in settings menu)
- fastboot erase userdata 2x
- wipe cache, wipe data, wipe devliak
Today the phone was with out a problem, but just a moment ago I wanted to unlock it by pressing the power button but the display didn't react as usal. It is still black and the only thing I can do is to take out the battery....
Last step I can do is to send it back to my girlfriends sister in US so that she can bringt it to Samsung US to get it serviced.
"bricking" the phones involves the phone not being able to turn on or do anything, period. your phone isnt a brick. after doing a "factory reset" you want to reflash whatever rom you are using. it seems like youre having problems with a bad app or some bad data.
thx simms22. i just flashed the newest cm7 nightly with rom manager (incl. wipe). i set up all my apps and 20 min later the error come.
to figure out if it is a bad app problem i do a factory reset now and won't log into google account and see if the error appears.
simms22 said:
it seems like youre having problems with a bad app or some bad data.
Click to expand...
Click to collapse
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
stiefa00 said:
i did a factory reset and skipped google setup after first boot.
i just entered sim code and let nexus s in idel mode.. about 15 mins later the four buttons were lightened but i couldn't unlock the phone. battery out... and i could power it on.
so it's some kind of bad data problem? but how to find and/or clean this bad data? thx again for your help.
edit: I found a lot on google for "full wipe bad data". I'm reading now! But I may have to ask you something
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. then i mounted usb and copied this nandroid 2.3.1 to it and flashed it. I booted and installed system update 2.3.2. now testing again without apps.
edit3: the hole day no problems. I only installed twitter and in the evening 2.3.3 manually. This morning again the phone was not unlockable. I had to take out the battery... on my way to work I did a wipe from stock recovery but shortly later the phone freezed while I used the slider to unlock it. oh man that sucks I thought it was fixed.
I make some coffee now and start google'ing. If you have some tipps, please throw them to me.
maybe reflashing radio?
Click to expand...
Click to collapse
are you using any of the custom kernels?
no, I'm using stock kernel and never flashed a custom kernel.
stiefa00 said:
no, I'm using stock kernel and never flashed a custom kernel.
Click to expand...
Click to collapse
im going to have you try wiping once again. wipe data/factory reset. only this time reupdate to android 2.3.3 right after the factory reset in recovery. dont boot after wiping, update after wipe, then reboot.
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
stiefa00 said:
--> stock recovery -> wipe / factory reset -> reflashed update (ota2.3.3) -> testing now without installing apps
thanks simms!
Edit: the phone got a freeze while I wanted to unlock it -.-
Edit2: I'm testing now in airplane mode. Maybe the error doesn't come...
Click to expand...
Click to collapse
im now thinking it might not software related. if it was software, a wipe and reupdate should have fixed it. maybe you should check into a warranty replacement. .
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
stiefa00 said:
In airplane mode the error is there, too.
Okay thx 4 ur help. I'm starting a service request. Bad day -.-
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
the only other thing i can think of that might cause something like that after wiping is something bad on your "sd" storage. copy everything you need off your "sd" storage and try wiping that.
stiefa00 said:
edit2: in recovery (cwm3.0.0.5) I did: format system, format data, format cache and format sdcard. Then nandroid restore...
Click to expand...
Click to collapse
I think I allready did this? Or do you talk about this 1gb sd. If so, how to format this one?
Could I find something usefull with logcat?
Sent from my Nexus S using XDA App
According to this thread I think you will have to get it replaced:
http://www.google.com/support/forum/p/Google+Mobile/thread?tid=44db6d8e31129d4c&hl=en
Holy sh** what an anoying link. -.-
BUT: thanks dude.. now I know waaazzz up
I recently bought a rooted Nexus s (GSM), and everything was fine until I powered off the phone. When I re-powered the phone, the mobile data didn't work, and the phone kept harassing me with the notification "sorry! the process com.android.phone has stopped unexpectedly" and made me force close it. and when I do press force close, the notification would pop up again instantaneously until I got tired of it and ripped the battery out.
The phone is currently running on NSCollab-1.0.35 ROM.
I tried hard-resetting the phone, but when I try to do it (via hard key reset and through settings->privacy-> etc) it would get stuck on the black google boot page and wouldn't budge. I can't even get to the recovery page.
I also tried to flash clockworkmod, then fix the permissions, and then reboot the phone, but that also failed.
The only way to stop the phone from harrassing me with the sorry notifications is to put it in airplane mode.. which certainly does not help my case. Please help! I will be eternally grateful.
Ok the reason this is happening is because you used the "switch from 3G to 2G" widget. You should've read the bugs when you downloaded the nscollab. Btw I use nscollab and I love it.
I fixed it by just wiping cache and just reinstalling the ROM.
acesofbelkan said:
Ok the reason this is happening is because you used the "switch from 3G to 2G" widget. You should've read the bugs when you downloaded the nscollab. Btw I use nscollab and I love it.
I fixed it by just wiping cache and just reinstalling the ROM.
Click to expand...
Click to collapse
yes, wow. I did do that. I see, I screwed up. Thank you so much!
acesofbelkan said:
Ok the reason this is happening is because you used the "switch from 3G to 2G" widget. You should've read the bugs when you downloaded the nscollab. Btw I use nscollab and I love it.
I fixed it by just wiping cache and just reinstalling the ROM.
Click to expand...
Click to collapse
well, I'm trying to wiping cache, but I can't even get to the recovery mode...
I get that message when I go into Settings>Application Manager and tap on the All tab. If I try this several times, the phone starts rebooting when I just try to go into Settings. I tried wiping cache in the stock recovery, but that didn't help? Any ideas?
wipe data
droidstyle said:
wipe data
Click to expand...
Click to collapse
Thanks. Wiping data is the same as a factory reset in that it will revert phone to original state when purchased, correct?
Wingnuts said:
Thanks. Wiping data is the same as a factory reset in that it will revert phone to original state when purchased, correct?
Click to expand...
Click to collapse
yes and it will reformat your internal sd, so back it up first.
OK, thanks for you help.
I've backed up my IMEI with adb nvbackup and QPST. The Synergy backup .zip doesn't work unless I'm rooted and unlocked, correct? Should I root / unlock and flash the Synergy zip before wiping data? Any chance rooting and unlocking will fix the 'settings has stopped' issue? I assume wiping data will cause me to lose root and unlocked state. Thanks for your help.
sordswi seems
Same thing with me on Samsung GT-I9300 with Android 4.1.1
I came across this problem 2 times.
The first time it happened when I installed a game "Waking Mars". The game was working fine, I played for around 20 minutes and then wanted to check free storage left after installing. But when I opened Application manager swiping was very laggy and after a few (5-10) secs it crashed with "Unfortunately, Settings has stopped" error or just closed. At that time I didn't know that it was because of "Waking Mars" and started to delete unnecessery applications I installed that day and yesterday, but problem vanished only after uninstalling "Waking Mars". Also, while this app was installed, phone's screen was glitchy and became bleached (the glitch disappeared after rebooting), like when "Natural" screen mode is activated, but it wasn't. When I had tried to install the game again, the problem came back.
The second time it was because of "Galaxy On Fire 2" installed. Same problems appeared: crashing Application manager and glitchy screen.
Both games contained their data in ".apk" file, but another Waking Mars version with separate data (cache) caused the same problem too.
By the way, funny thing is that both games are about space
P.S.: Sorry for my English, it isn't my native language.
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
louiscar said:
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
Click to expand...
Click to collapse
boot into recovery and wipe dalvik cache n then do a normal reboot n check wad happens
you can also make a nandroid backup n install a custom and check wheather the problem exisit by doing backup ull not loose ur data n u can return to stock again just by restoring the backup ... try and let me know
louiscar said:
Can anyone suggest a troubleshooting method without a factory reset. This is what I am experiencing:
Everytime I reboot the Sensation will boot up and go through the normal process. About 3 or 4 minutes it will just reboot. Often when this happens I note that I don't have to re-enter my pin (a clue?). This rebooting will go on repeatedly but eventually (if I leave the phone alone) I will at some point end up with the phone up and running.
There are no random reboots, it is only this situation that causes the problem and it's obviously some point 3 or 4 mins into the process that is causing the problem.
I've noticed that if I reboot to recovery and then select reboot from there it is usually successful.
I am s/off via wire trick method, and rooted. recovery is 4 ext and I am still on stock rom.
I'd like to find out what is happening at the point of the reboot, is there a good way to do this?
Click to expand...
Click to collapse
Hi,
Have you installed a new ROM recently?
Did you fully wipe the phone before you did this?
If not,try re-installing the ROM you are on.
No wipes.
You will not lose settings or data.
shrex said:
boot into recovery and wipe dalvik cache n then do a normal reboot n check wad happens
you can also make a nandroid backup n install a custom and check wheather the problem exisit by doing backup ull not loose ur data n u can return to stock again just by restoring the backup ... try and let me know
Click to expand...
Click to collapse
What I noticed is that the problem didn't exist when rebooting from ADB or fastboot either.
Anyway your suggestion so far looks promising. I've tried a normal restart from the phone and a battery change both of which would usually end up with the rebooting problem. Both of these tests haven't caused it so I'll keep testing but thanks for the suggestion.
What is does the Dalvik cache do and how would this have caused this kind of problem? I'm interested in the whys. The problem appeared soon after installing a couple of things as I remember and I did try to backtrack without much success.
malybru said:
Hi,
Have you installed a new ROM recently?
Did you fully wipe the phone before you did this?
If not,try re-installing the ROM you are on.
No wipes.
You will not lose settings or data.
Click to expand...
Click to collapse
No I've not installed any Roms, I'm on stock.
Revived thread - as it's happening again
I'd like to revive this thread - perhaps I should post a new one but since it's here ...
This problem has returned with a vengeance. It took me about 3 hours of fighting to get this phone to stop rebooting. It seems clearing the dalvik cache isn't a solution anymore (if it was in the first place).
What I've observed is that if I take the sd card out it doesn't reboot. When the card is in I have several shortcuts on one of my home screens which often will not refresh for ages (ie. android icons for anything moved to sd card). When the icons start to appear the reboot will happen shortly after. All the time I'm waiting for this to happen the phone is very sluggish.
I don't think this is an incompatible sd card but maybe it is, however, if I can get this to stop rebooting then all is ok till I attempt another reboot.
Ideally I'd like to track this down to find out if there is an app which is misbehaving. Are there any tools that can help me do that.
Any suggestions would be most welcome.
Backup all your data and do a factory reset
This problem might be due to 3rd party app as you phone without sd card dosent reboots
Might be some of ur app is seriously miss-behaving
After a factory rest install each app n check ( I know it's time consuming)
Hit thanks button if you find me helpful
sent from amazing HTC sensation using xda premium
shrex said:
Backup all your data and do a factory reset
This problem might be due to 3rd party app as you phone without sd card dosent reboots
Might be some of ur app is seriously miss-behaving
After a factory rest install each app n check ( I know it's time consuming)
Hit thanks button if you find me helpful
sent from amazing HTC sensation using xda premium
Click to expand...
Click to collapse
Yeah hoped to avoid that for 2 reasons. 1) It's a bummer 2) I won't know what the problem was / is.
I did do a factory reset after backing up data via my recovery. It seemed to be ok but I had nothing on SD at that point. I loaded a couple of apps and moved them to sd and it still didn't happen. The I restored the data and it was back to the same problem.
I may have to go with your suggestion but I'm going to lose some data as I can't back up selectively (so it seems).
Is there a logger I can use that starts at reboot. If I could find out exactly what it's doing when it decides to reboot I might nail the app?
louiscar said:
Yeah hoped to avoid that for 2 reasons. 1) It's a bummer 2) I won't know what the problem was / is.
I did do a factory reset after backing up data via my recovery. It seemed to be ok but I had nothing on SD at that point. I loaded a couple of apps and moved them to sd and it still didn't happen. The I restored the data and it was back to the same problem.
I may have to go with your suggestion but I'm going to lose some data as I can't back up selectively (so it seems).
Is there a logger I can use that starts at reboot. If I could find out exactly what it's doing when it decides to reboot I might nail the app?
Click to expand...
Click to collapse
hi
greetings
to find the problematic app might go tough you will have to install each and every app and check after that
try installing all the trustworthy apps before eg. file manager,fb,twitter,gmail etc then check once again ,after that install single app at a time
Hi there,
I went back to stock some days ago. Worked fine so far. OTA to 1.56.401.81.
When I reboot the phone, it ist starting to optimize the Apps again, like it does after an update. When it ist done, it reboots again and begins optimizing the apps again.
Only thing I can do here is reboot to recovery and delte dalvik cache. (also tried data and cache). Still after a reboot it is looping again.
Any idea what I can do about this?
I found the Problem. IT Happens After I disable the Google app in the settings. Could Not find a Solution exept of leave IT enabled.