Any ideas what might be causing this, or how to fix it?
If I have to power off my phone, when I turn it back on, it is perpetually stuck on the boot screen animation. The only way to move past that is to go into recovery and wipe data, davlik, and cache. Then I have to reinstall everything. But inevitably, it will do it again when I restart my phone.
I'm running the current ota version and rooted.
It shouldn't just happen randomly unless there's a hardware problem. Since you have root access, you might have done something that caused it. I suggest re-flashing factory images and then see if it still happens.
I did flash the factory image on Tuesday night after it happened the first time. I'll try it again when I get home this evening. Mayb there is something corrupt in my titanium backup file I restored a few programs from.
udrunner said:
I did flash the factory image on Tuesday night after it happened the first time. I'll try it again when I get home this evening. Mayb there is something corrupt in my titanium backup file I restored a few programs from.
Click to expand...
Click to collapse
Make sure you don't restore system apps.
udrunner said:
I did flash the factory image on Tuesday night after it happened the first time. I'll try it again when I get home this evening. Mayb there is something corrupt in my titanium backup file I restored a few programs from.
Click to expand...
Click to collapse
That might be it. But a fresh clean install is the way to go.
Sent from my Nexus 5 using Tapatalk
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
So the past 2 days I've had an interesting problem, with even more interesting results.
Both mornings I've tried to use my GPS and it just hangs on trying to connect to it. The GPS says it's on, and I can toggle it off and back on again but it never finds any sats.
Yesterday I reboot the phone and it takes a while to boot the phone back up (most like the first time you boot after a fresh install), and when the phone came back online the GPS worked but all my bluetooth pairings were gone.
Today I have the same GPS problem so I reboot again, and again it takes a while to boot and so far I still have my bluetooth pairings, but I've been unable to connect to the devices, all my sound settings are back to the defaults, when I hold down the power button now the only option I have is Power Off, nothing else, when my screen times out and I hit power to bring it back on it goes right back to wherever I was, I don't see the lock screen anymore. And to top it all off my home button and my search button do not work.
What a mess, this phone is getting worse by the day, I'm actually starting to regret the purchase. I guess it's time to call it in and see what they say.
Edit: Forgot to add all my SMS messages were deleted as well.
Rooted? Have you done anything to it? That's definitely not normal but I guess you know that
Ya it's rooted and has nvflashed clockworkmod recovery installed. Rooted the day I got the phone and clockworkmod recovery has been installed for about a week.
I just tried clearing the cache partition, wiping Dalvik Cache, fixing permissions, and no change. Running a full backup via Titanium Backup now before I try a factory reset to see if that fixes it.
If that doesn't do it I'll try restoring a backup image from last week.
gohawks1 said:
Ya it's rooted and has nvflashed clockworkmod recovery installed. Rooted the day I got the phone and clockworkmod recovery has been installed for about a week.
I just tried clearing the cache partition, wiping Dalvik Cache, fixing permissions, and no change. Running a full backup via Titanium Backup now before I try a factory reset to see if that fixes it.
If that doesn't do it I'll try restoring a backup image from last week.
Click to expand...
Click to collapse
I would guess it's not the phone but the CWM made the mess. You probably want to try factory reset.
My Bluetooth settings and profiles randomly appear and disappear and I'm bone stock.
Well, factory reset got all my buttons working again, and my screen locks again. Since I'm back to stock now and have to re-setup everything now I think I'll go try out the Eaglesblood ROM and see how that goes.
I rooted my phone and replaced all kinds of things and a installed a new launcher, but the startup time was unbearable. I let my friend tinker with it, and from the SuperMaid app, he apparently froze the Android OS (I guess he thought my launcher was an OS) before I had a chance to back anything up with Titanium. When the phone died, it won't of course won't load. It's a Samsung Mesmerize, so I have the the one file from ClockModRecover, and that's it. I tried to restore that file, and it won't. Is my phone bricked? I'm kicking myself for all of this.
Well...did you install clockwork mod recovery? Not the manager app in android, but the actual recovery? If so, did you do a nandroid backup? If you did, restore it. If you never bothered to do a backup but do have cwm recovery, do a factory reset. If no cwm then last thing is boot into normal recovery and try a reset from there. You will likely lose root, and will need to root the phone again, and keep your friend out of your OS.
Tapatalked from my A100 - Flex Reaper RF1.
recovery isn't working
When I tried to restore the nandroid backup, it repeatedly failed saying it couldn't (I can't remember if it was mount or unmount) the system. So I did the factory restore as you suggested, and when I turned on the phone, I received a text message. However, I'm getting a force close message that's preventing me from doing anything: "The application TwLauncher (process com.sec.android.app.twlauncher) has stopped unexpectedly...") When I click Force close, it just pops right back up, cutting off functionality of the phone.
Ok reboot back into recovery, wipe cache, go to advanced, wipe dalvik, fix permissions, reboot.
Sent from my LG-P999 using Tapatalk 2
didn't work =(
I did all those things and the system repeatedly wouldn't unmount. I had to just go back to Froyo 2.2 with Odin. The good news there is now I can install Ice Cream Sandwich. I figure I can't do too much damage, and if I do, I still have the backup
I said to reboot not restore or flash, but I'm glad you got it all figured out. The fix permissions and caches being wiped was to try to fix the current install, not prep for a new rom or restore. At least I assumed flash or restore since you mentioned system not unmounting which only happens for that.
Sent from my LG-P999 using Tapatalk 2
Sent from my LG-P999 using Tapatalk 2
I downloaded TWRP 2.8.6.0 and installed it. Then I downloaded cm-12.1-20150405-UNOFFICIAL-xt897.zip ...put both on the SD card...went into TWRP, wiped the system, installed CM12.1 and it stayed at the boot logo for about 20 minutes. I rebooted, wiped again, and now I am stuck at the warning screen about the bootloader being unlocked....can't get into the phone OS at all....
Go back to TWRP and restore that backup you took before wiping...
If you didn't take a backup, try flashing another ROM and question why you didn't take a backup of your working setup.
Or just get back to TWRP, do a factory reset, reboot system and wait longer than 20 minutes (it can take longer to boot the first time, give it a while).
arrrghhh said:
Go back to TWRP and restore that backup you took before wiping...
If you didn't take a backup, try flashing another ROM and question why you didn't take a backup of your working setup.
Or just get back to TWRP, do a factory reset, reboot system and wait longer than 20 minutes (it can take longer to boot the first time, give it a while).
Click to expand...
Click to collapse
I didn't do a backup due to lack of space available.....plus i've had plenty of experience with flashing phones/ROMS....this one was supposed to be so easy.....but its proven to be very difficult.....I did flash another ROM on it and its at the loading screen......never seen a phone take so long to load.....sadly, I was wanting Lollipop and this one that I'm loading up now is KitKat......been loading for over 10 minutes now.......I have two of these phones, I guess I could do a backup of the other one and restore onto this phone....not sure if that will work......
Same problem here and I did restore a backup and it wouldn't boot either anymore
4218kris said:
Same problem here and I did restore a backup and it wouldn't boot either anymore
Click to expand...
Click to collapse
There's always RSDLite as a last resort.
My cousin flashed a nightly early this week and now it's stuck in a bootloop. I tried flashing latest recovery en formatting /repairing data and internal storage. But I always get an error on format DATA and trying to repair Internal Storage is not even an option.
Next I tried CM recovery. Nada, same effect. Flashing is possible, it even boots, but then it also loops.
Just flashed using RSD LITE 6.1.5 icw asanti_c_sprint-user-4.1.2-9.8.2Q-122_XT897_FFW-5-6-release-keys-cid9.xml.zip. Still, this baby won't boot!
So unless someone comes with a fix... This baby is dead. Something very wrong with internal memory I guess.
I finally got it to boot, I do get the error on formatting data too but try a couple times and it seems to work. It always has an error the first try. I also flash the ROM with data and cache on ext4 then changed it after flash and after first boot it will factory reset the phone when changing from ext4 to f2fs. That's what I did and it worked for me.
Wel I manually changed all partitions to EXT4. Let it bootloop untill the battery was dead. Also tried formatting a gazillion times. Still no succes here.
BTW, digitizer doesn't respond anymore after flashing TWRP. So nothing to test for me. CM recovery doesn't have these options.
So eternal bootloop. Time to move on.
Die Bruine said:
Wel I manually changed all partitions to EXT4. Let it bootloop untill the battery was dead. Also tried formatting a gazillion times. Still no succes here.
BTW, digitizer doesn't respond anymore after flashing TWRP. So nothing to test for me. CM recovery doesn't have these options.
So eternal bootloop. Time to move on.
Click to expand...
Click to collapse
Did you try sbf'ing back to stock?
Sent from my ATRIX HD using XDA Free mobile app
palmbeach05 said:
Did you try sbf'ing back to stock?
Sent from my ATRIX HD using XDA Free mobile app
Click to expand...
Click to collapse
Yes, as stated eralier. RSD Lite original firmware. Installs just fine. But that also goes into bootloop until the battery runs dry.
Die Bruine said:
Yes, as stated eralier. RSD Lite original firmware. Installs just fine. But that also goes into bootloop until the battery runs dry.
Click to expand...
Click to collapse
Ok, just checking. Did you wipe data and cache when doing that?
Sent from my SM-T320 using XDA Free mobile app
Yes I did. I would like to try 4218kris' suggestion. But without touch input that's not an option. Switched fronts to be sure, digitizer is ok. I'll leave this one for what it is. Still two users left in te family with XT897. When those break down I won't be replacig them.
Wokeup this morning and decided to restart my phone as i usually do every morning, but after the restart the phone has remained in safe mode since then. I have tried restarting the phone several times to no avail.
I believe phone has been rooted about 2 years ago or so. I dunno what kind of recovery im running also.
I am still running 5.1.1
J700HXXU1AOG6 (baseband version)
LMY48B.J700HXXU1AOI3 (build number)
Please any help to resolve this would be greatly appreciated
NOTE:
Im a noob, so please try to be clear as possible.
THANKS
UPDATE
Just realized the volume down button is not working(clicks but doesnt lower the volume). So im guessing this is what makes it enter safe mode all the time
What recovery are you using?
souvikghosh915 said:
What recovery are you using?
Click to expand...
Click to collapse
Well im not too sure, but when i was factory resetting the phone some blue/dark screen showed with TEAM WIN underneath it
Ekwere said:
Well im not too sure, but when i was factory resetting the phone some blue/dark screen showed with TEAM WIN underneath it
Click to expand...
Click to collapse
You have backups ?
What kind of ROM are you using ?
Anyways best is gonna be download any rom and wipe system, data, cache, dalvik...then flash it.
If you don't have backup and you're on stock then just download the firmware from Sammobile and then flash it via Odin, remember don't factory reset, else your all data will be wiped out.
Then start your phone, take a backup of the things you'll need and then reset and flash it again.
And if you're on a custom ROM and you don't have backups then flash the ROM on your recovery again without wiping anything. Restart your device then, you'll see your datas intact, then take a backup but most likely you'll see a lot of force stops of several apps while in this process. Then complete by flashing it again after wiping data system cache dalvik.
souvikghosh915 said:
You have backups ?
What kind of ROM are you using ?
Anyways best is gonna be download any rom and wipe system, data, cache, dalvik...then flash it.
If you don't have backup and you're on stock then just download the firmware from Sammobile and then flash it via Odin, remember don't factory reset, else your all data will be wiped out.
Then start your phone, take a backup of the things you'll need and then reset and flash it again.
And if you're on a custom ROM and you don't have backups then flash the ROM on your recovery again without wiping anything. Restart your device then, you'll see your datas intact, then take a backup but most likely you'll see a lot of force stops of several apps while in this process. Then complete by flashing it again after wiping data system cache dalvik.
Click to expand...
Click to collapse
No, i dont have any backups(most things were saved on SD card)
I believe its stock rom. The only thing i remember doing is rooting the phone long time ago when i got it.
I just realized that the volume down button is not functioning(clicks in but doesnt lower the volume) and i believe this is where the issue is as the volume down activates the safe mode feature
Im still gonna flash the phone none the less cos im still on older android and i hope it works
That volume down button is broken, stuck ON. Get it fixed.
Sent from my SM-J700M using Tapatalk
Thanks a lot to everyone who tried to help.
Will be taking the phone for repairs by Monday and will drop a feedback on how that goes
Fixed the volume down button and the phone is back to normal now.
Time to close this thread and go search on how to root the 6.0.1
Thanks guys
Cheers!
Sent from my SM-J700M using Tapatalk