I have a Sprint Nexus S4g, and have been using Bugless Beast ROM for a few weeks. About a week ago I started having Random reboots to recovery, as well as locking up at the Google splash screen when rebooting. I have also had many problems with google apps crashing as well as the phone just being locked up when I go to use it (in this case the notification lights usually are lit).
I have tried clearing cache/dalvick cache and factory reset. The last time I even wiped my SD card and am now stopping Google from installing my apps other than Goomanager.
about an hour after my last attempt, I got my first random reboot to recovery. I am not sure what to try next.
Thanks for any help!
Go back to stock and see if the problems persist
snandlal said:
Go back to stock and see if the problems persist
Click to expand...
Click to collapse
I am going to try when I get home. If that doesn't work, I guess I will send it to Samsung under warranty.
Just returned to stock, and it is still locking up.
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
My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Did you have any undervolt settings applied?
The phone is not underclocked, it is not overclocked. It was rooted, I unrooted it. its currently unrooted absolutely factory stock and still doing that. What can I do to fix this?
warranty is over as of 3 months ago
Forgot to mention the most important thing!!!
When I am on the phone with someone, it works perfectly forever, as soon as i hang up, it ends the call. this key thing might help someone find the solution!!
himalaya333 said:
My infuse is rooted with zues. A few weeks ago, it was stuck on the samsung boot logo and it keeps looping. I wiped data and cache and installed zues again and it was fixed. Last night, this happened... so my phone turns on for 2 minutes max, then turns off and starts the loop. I can only keep on for 2 minutes before it starts looping again. by saying keeping it on for 2 minutes, i mean everything works! talk, text, games, ect...
so i turned it off, went to clockwork or root menu, whatever you guys call it, and i wiped data and cache. Whats weird is that even on boot menu or clockwork, it still wont stay on, it keeps turning off and turns on and loops!
i installed zues again, still turns off and loops
next step? is my phone dead?
Click to expand...
Click to collapse
Don't panic just yet... I doubt your phone is dead.
You say you've "wiped data and cache". Are you also making sure to wipe /system and Dalvik Cache?
Try flashing Zeus again.
Boot to CWM, Wipe EVERYTHING (/data, /cache, /system, Dalvik Cache). (Alternatively, get "Clean Wipe" from Qkster's Scripts and flash with CWM to easily wipe everything.)
Flash Zeus and go.
If you're still having problems, perhaps try a different rom?
okay, I read everything you guys wrote.. This is where I am, I am open to suggestions
I am on the stock rom and unrooted. Phone still boot loops. What should I do now? Step by step instructions would be great. Im unrooted, so should i root again? even though im having this problem?
bump! really need help with this guys!
Have you tried going back to stock?
If it keeps looping while on download mode then I would say you are dealing with a hardware issue.
Sent from my sweet & buttery Infuse
It just came to me that it doesn't loop in download mode. It does loop in clockwork, I flashed the stock kernel using ODIN and went completely stock through ODIN.
How do i fix this? i'm pissed that i had it for a year and three months and right after the warranty ended, the phone stopped working! Samsung never again unless this issue is fixed
I'm a newbie to flashing, so take it with a grain of salt. At least two more things seem worth trying to me:
1 - Try factory data reset (assuming you already tried the wipe Davlick and wipe cache). I'm not positive what this does, but I think you may lose some of your data if it's not backed up.
2 - If that doesn't work, try qkster's Heimdall UCLB3 stock (since you can get into download mode...shouldn't be a problem). This is complete back to stock so should be able to clear any software problem I'd think. I know you may think it's redundant since you are already back to stock, but worth trying imo since some things just take more than one try, and you may have had a bad flash the first time around.
Why zeus? try latest ones with jelly bean
Hey,
Try other roms based out of jelly bean. They are pretty stable. CM10 with 09/14 build is the latest
Here are the standard steps if you have CWM enabled.
1. Factory re-set (only when switching between different roms).
2. Cache partition wipe
3. Dalvik Cache wipe
4. Install the zip file
5. Re-start and wait until it re-starts. Initially it will take some time.
I have tried various roms and versions as well. Best would be the CM10 Jelly bean.
Thanks Kran.
I've been having spontanious reboot problems where my charge would reboot and get stuck in a boot loop freezing on the droid eye animation and rebooting. In the past I've been able to clear the delvic cache and regular cache and get the phone to boot and go back to working order. Today however, clearing cache didn't work. Thinking this was a software problem, I connected the phone to oden and flashed the stock software ED1. I was planning to install back to EP5 and redo Tweaked 3.2 since the phone had developed a lot of lag.
Now the phone gets to the droid eyebll and stays there. Every so often the animation freezes for a second or two then continues. Is the phone dead? Can it be brought back to life so that I can use it while I figure out a new phone. I'm asking because this is my only smartphone and I'm now stuck activating my old chocolate flip
Mike
Why all the way back to ED1? Do you have everything backed up in case you need to flash with the pit file?
Sent from my SM-N900V using XDA Premium 4 mobile app
beavermjr said:
I've been having spontanious reboot problems where my charge would reboot and get stuck in a boot loop freezing on the droid eye animation and rebooting. In the past I've been able to clear the delvic cache and regular cache and get the phone to boot and go back to working order. Today however, clearing cache didn't work. Thinking this was a software problem, I connected the phone to oden and flashed the stock software ED1. I was planning to install back to EP5 and redo Tweaked 3.2 since the phone had developed a lot of lag.
Now the phone gets to the droid eyebll and stays there. Every so often the animation freezes for a second or two then continues. Is the phone dead? Can it be brought back to life so that I can use it while I figure out a new phone. I'm asking because this is my only smartphone and I'm now stuck activating my old chocolate flip
Mike
Click to expand...
Click to collapse
No, the phone is not dead, it is a bit lag.
16 GB black Nexus 5 on ART with stock recovery, stock kernel and rooted using CF's autoroot and bootloader unlocked. The phone was running perfectly for the past 3 months.
Now it has started to randomly reboot all the time and goes into bootloops which take a while to recover from. It seems that the power button is super sensitive. Even touching it mildly brings up the power off option. After reboot the phone went back to Dalvik runtime from ART.
I've been running Dalvik every since. I've uninstalled most apps. But the phone keeps on rebooting again and again just randomly in the middle of tasks. After this the phone goes into a boot loop until it boots successfully. It's almost impossible to use the phone right now, because the reboots just happen more and more frequently.
I've tried wiping the cache, uninstalling apps etc. Nothing has helped.
Any suggestion? Thanks in advance.
iamjimmy said:
16 GB black Nexus 5 on ART with stock recovery, stock kernel and rooted using CF's autoroot and bootloader unlocked. The phone was running perfectly for the past 3 months.
Now it has started to randomly reboot all the time and goes into bootloops which take a while to recover from. It seems that the power button is super sensitive. Even touching it mildly brings up the power off option. After reboot the phone went back to Dalvik runtime from ART.
I've been running Dalvik every since. I've uninstalled most apps. But the phone keeps on rebooting again and again just randomly in the middle of tasks. After this the phone goes into a boot loop until it boots successfully. It's almost impossible to use the phone right now, because the reboots just happen more and more frequently.
I've tried wiping the cache, uninstalling apps etc. Nothing has helped.
Any suggestion? Thanks in advance.
Click to expand...
Click to collapse
Sounds to me like a hardware issue-as if the button is partially depressed at all times. You could try popping the back off and blasting around the button with compressed air. Another option would be to RMA.
mrfeuss said:
Sounds to me like a hardware issue-as if the button is partially depressed at all times. You could try popping the back off and blasting around the button with compressed air. Another option would be to RMA.
Click to expand...
Click to collapse
Thanks for the quick response. I don't want to mess around with the hardware of the phone. I think I will go the RMA route.
Do you have any suggestions in terms of the best way to backup the phone? Do you think a factory/data reset of the phone might help before RMAing?
I'd factory reset just as a precaution as your phone probably has some personal info on it
keepermike said:
I'd factory reset just as a precaution as your phone probably has some personal info on it
Click to expand...
Click to collapse
Yes. I will definitely factory reset before RMA.
Any idea on the best way to backup the phone content? Should I flash all system files for factory reset or just use the phone's menu?
Thanks.
iamjimmy said:
Yes. I will definitely factory reset before RMA.
Any idea on the best way to backup the phone content? Should I flash all system files for factory reset or just use the phone's menu?
Thanks.
Click to expand...
Click to collapse
Upload photos, music and videos to drive, dropbox or to your computer with usb. Then depending if you're rooted or not helium or titanium backup for app data. Me personally I'd just flash all files cause it doesn't take long to do so. Good luck and hopefully your new Nexus gives you better luck
My gf has a N5 and decided to let the update install (not sure which one was on the 23rd) and all of the sudden her phone just went crazy. It reboots randomly, sometimes it will boot completely and other times it just gets stuck at the boot screen. Before this update the phone was working normally and it doesn't appear to be an issue with the power button.
Her phone is bone stock. No root, no unlock. It is unfortunate, but she is on travel and has no phone.
Has anyone else seen this sort of issue after a software update?
Yes it can happen. Did you try to clear cache from your stock recovery?
I will do this once she is back from her trip. She tried to wipe the cache already, but it just got stuck there and afterwards she was not able to get past the google logo. I hope that it lets me wipe the cache and it sorts things out... I will post back once I have a chance to look at the phone to see what's going on with it.
EcPercy said:
I will do this once she is back from her trip. She tried to wipe the cache already, but it just got stuck there and afterwards she was not able to get past the google logo. I hope that it lets me wipe the cache and it sorts things out... I will post back once I have a chance to look at the phone to see what's going on with it.
Click to expand...
Click to collapse
If it doesn't fix your issue you should flash the factory images to start from scratch.
Also wiping the cache partition can take a long time on a nexus 5 - sometimes 10 to 15 minutes. Not sure why this is - on my Nexus 7 wiping the cache take seconds.
Trev
Got the phone yesterday. I wound up having to reinstall the OS and then factory reset. Not sure what happened to it, but it's working fine now.