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
sooo i decided to try the portable hotspot function today and found out that everytime i went to the hotspot settings it force closes on me. I get the error " process com.android.settings has stopped unexpectedly)
anyone have this problem? or have any insight to fixing it?
i thought i disabled something but i went through and re enabled processes but nothing so far is working. im going to keep trying in the mean time.
I would backup your apps and do a factory reset. That should fix your issue.
Cosign Dubie - that's not normal behavior. Try turning off fast boot and restarting your phone and see if that helps first.
thanks, a backup and factory reset fixed it... everything is back to the way it was with mobile hotpot working again. really didnt want to have to do it but eventually i had to.
The Illest 619 said:
thanks, a backup and factory reset fixed it... everything is back to the way it was with mobile hotpot working again. really didnt want to have to do it but eventually i had to.
Click to expand...
Click to collapse
If your phone is rooted, does a factory reset unroots it?
No @ franca
sent from my Sensation on CM7 Alpha#10
Hi,
I rebooted my sensation and after around an hour the CM boot screen just froze. I tried rebooting it again and it did the same.
Ive now factory reset it and when running through the initial setup it gets to to the section where you select the time and date etc. then the setup says it has crashed. After pressing force close I just get a black screen with the notifcation bar at the top and im unable to do anything?
Can anyone help with this?
Thanks
Tom
are you still s-off right? so wipe all and flash the rom again
tombullock92 said:
Hi,
I rebooted my sensation and after around an hour the CM boot screen just froze. I tried rebooting it again and it did the same.
Ive now factory reset it and when running through the initial setup it gets to to the section where you select the time and date etc. then the setup says it has crashed. After pressing force close I just get a black screen with the notifcation bar at the top and im unable to do anything?
Can anyone help with this?
Thanks
Tom
Click to expand...
Click to collapse
Are you using a factory or custom ROM?
matt95 said:
are you still s-off right? so wipe all and flash the rom again
Click to expand...
Click to collapse
Sorted
The CM7 ROM I had saved on my SD card did the same thing but I redownloaded it and it worked!
Thanks!
So I installed clockwork and then installed an unlocked bootloader, after that I booted into recovery and installed cm 10 and gapps after I wiped data. Once that all finished I started the phone up I was already activated and stuff like that, but every time I would restart it would bring up a screen talking about activating my phone, and it never did anything just sat on that screen.
So I looked around and saw a post with someone having the same issue, and someone told them to wipe data and clear dalvik cache, so that's what I did. Once I started it back up, I had to go through the setup process again, this time it stopped and activated my phone, but it fails every time.
How could I fix this? I also tried installing cm10.1 and Liquid and neither of those would activate either.
If all else fails I will do http://forum.xda-developers.com/showthread.php?t=1867253 but I'm afraid that won't work correctly either..
Had the same problem after flashing the Carbon rom. Try going in settings>More>Mobile Networks>Preferred Network Mode. Select CDMA / EvDo auto. Reboot.
Ah that fixed it! I didn't have to activate either, it just started working.
Oddly though I tried dialing *22890 and it failed to activate.
I do have another question though, when I reboot it still seems to come up with the activation screen. Any idea how I can stop that from happening?
Im a straight noob on here. So, sorry if this is a re-post. I tried looking for a similar problem but didn't find anything.
I have rooted and flashed Hyperdrive RLS2 on my GS4, everything went fine. I went into Hyperdrive control and installed a few cool tweaks (adblock, adobe, transparent and volume hack) rebooted into recovery to install those items thru TWRP recovery (as suggested) again everything went smoothly. I rebooted system, and a window appeared with a error message " Unfortunately HyperdriveOTA has stopped."
I tried opening Hyperdrive control and it forced closes.
Could someone tell me whats going on. Did I do something wrong?
cambonese said:
Im a straight noob on here. So, sorry if this is a re-post. I tried looking for a similar problem but didn't find anything.
I have rooted and flashed Hyperdrive RLS2 on my GS4, everything went fine. I went into Hyperdrive control and installed a few cool tweaks (adblock, adobe, transparent and volume hack) rebooted into recovery to install those items thru TWRP recovery (as suggested) again everything went smoothly. I rebooted system, and a window appeared with a error message " Unfortunately HyperdriveOTA has stopped."
I tried opening Hyperdrive control and it forced closes.
Could someone tell me whats going on. Did I do something wrong?
Click to expand...
Click to collapse
I have the same issue. Help.
Edit: Just figured it out. Go to Application Manager.. All.. HyperdriveOTA. Force Close and Clear data/cache.
solution
nkranes said:
I have the same issue. Help.
Edit: Just figured it out. Go to Application Manager.. All.. HyperdriveOTA. Force Close and Clear data/cache.
Click to expand...
Click to collapse
This was pretty much what I did and it worked. I only forced closed and cleared data and cache in hyperdrive hub and hyperdrive ota. Now everything is fine.