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
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
Hello there, I have a huge issue with my Motorola Xoom.
I ran the #156 TeamEOS 4.2 Nightly Rom for my European 3G Xoom when all of a sudden my tablet started acting really weird.
Apps were crashing, Google Play wasn't working, Browser as well, and so on.
I decided to do a hard reset, formatting cache, Dalvik Cache, Hard Reset...but nothing was cancelled. As soon as i rebooted my device, everything was back the way it was with the same issues. I noticed my tablet was costantly updating the same apps and even if I updated them the following reboot they were back re-updating themselves.
I have no idea what to do, I tried everything, including RSD Lite. Nothing.
Can somebody help me figuring out what to do and how to at least format my Xoom completely so that I can re-install my rom and then re-install the apps?
Thanks.
I would boot into recovery and do a full wipe the reflash the rom a gapps. you should be good to go.
No can do, sorry. What's weird is that even when I go to change the performance settings on the rom, to overclock it more or less, the changes are not recorded. I can set whatever I want but it doesn't change it. It's like the tablet is in a loop, always stuck doing the same things, charging the same rom, the same settings. I really don't know what to do, I don't want to throw it away but I don't know how to solve it.
Which xoom do you have? We can always flash the stock img with fastboot to restore it. It will be back to complete stock.
Can you get into recovery at all by powering off then press the power button wait till 3 sec's after the logo appears and press volume down. You will see android recovery at the top press vol up to select. If you can and you have a backup restore it. If you use an external sd card you can load a rom on to it and flash it in recovery.
"I decided to do a hard reset, formatting cache, Dalvik Cache, Hard Reset...but nothing was cancelled. As soon as i rebooted my device, everything was back the way it was with the same issues. I noticed my tablet was costantly updating the same apps and even if I updated them the following reboot they were back re-updating themselves."
this is the same exact problem i'm having. I cannot get my xoom to reset. It always goes back to where it was before.
danman1835 said:
"I decided to do a hard reset, formatting cache, Dalvik Cache, Hard Reset...but nothing was cancelled. As soon as i rebooted my device, everything was back the way it was with the same issues. I noticed my tablet was costantly updating the same apps and even if I updated them the following reboot they were back re-updating themselves."
this is the same exact problem i'm having. I cannot get my xoom to reset. It always goes back to where it was before.
Click to expand...
Click to collapse
Sounds like your data has gotten corrupted somehow. You can take the boot.img out of whatever Custom ROM ur using, and via terminal -
fastboot flash boot boot.img
fastboot reboot
I'm not using any custom roms. I'm using factory settings for almost everything.... also i don't know how to use terminal
Mjamocha said:
Sounds like your data has gotten corrupted somehow. You can take the boot.img out of whatever Custom ROM ur using, and via terminal -
fastboot flash boot boot.img
fastboot reboot
Click to expand...
Click to collapse
I have the same problem.
The Xoom is a european with android 3.1 kernel version 2.6.36 and build H.6.3-25-9 <- this i dont understand but i think that is no correct.
I try flash the H.6.1-38-1_Retail_Europe version, all the process finish ok, but when i restart the tablet everything continues as before.
I not know what else to do, Heeeelp.
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
Hey! About two weeks ago I rooted my Samsung Galaxy S 4G and installed "Valhalla Final" Gingerbread 2.3.6. Everything has been great until today :crying:... I was talking on the phone and the battery went dead, I got home and charged it then tried to turn it back on. When I did it started to boot up and then got stuck on the "Team Kang" unicorn animation. I'm a noob and not sure what to do? I have tried removing the battery, etc. and still same result. HELP!! What should I do?? Thanks in advance...
Try doing a factory reset in recovery.
To get to recovery:
pull out your phone's battery
put the battery back in
hold BOTH volume keys and do NOT let go of them
Press the power button long enough for the phone to turn on
Once you are in recovery you can let go of the volume keys
What I ended up doing was going to recovery mode, wiping the cache and then flashed the same rom again.. Question is what would have made it do this to begin with? Is there a problem with this rom that im not aware of? After I did the above it now works fine other than having to go through and redo apps, etc..
jevanstintshop said:
What I ended up doing was going to recovery mode, wiping the cache and then flashed the same rom again.. Question is what would have made it do this to begin with? Is there a problem with this rom that im not aware of? After I did the above it now works fine other than having to go through and redo apps, etc..
Click to expand...
Click to collapse
There is no problem with the rom, if you wipe cache before upgrading. I usually wipe dalvik as well. Wipe factory if you are coming from a different rom.
I do the previous three for each rom I use, on any phone I own. I don't always trust that the developer wrote in the updater-script to attempt to wipe cache & dalvik when flashing.
Hi there!
After about a week ago, I’ve turned off my Note 3. Then two days later, when I wanted to use it, I’ve turned it on. After CM logo appears, its says:
“Android is starting
Optimizing x apps of x”
I know this is because of ART, but after it finishes, my phone reboots, and CM logo appears again, and nothing happens. After a while, it starts optimizing apps again. Now I left it for 2 hours, my phone didnt boot up.
What should I do? I didnt flash any new kernel, rom, recovery or anything else. Im on CyanogenMod, with CWM recovery. I dont want to factory reset, because of my photos and videos.
Even I tried to start in safe mode, but I couldnt get to it, and Im not really sure that I tried to enter safe mode properly.
Please help!
Just dirty flash the rom again through cwm.
See if it works
It's high time you flashed TWRP already.
Bence98007 said:
Hi there!
After about a week ago, I’ve turned off my Note 3. Then two days later, when I wanted to use it, I’ve turned it on. After CM logo appears, its says:
“Android is starting
Optimizing x apps of x”
I know this is because of ART, but after it finishes, my phone reboots, and CM logo appears again, and nothing happens. After a while, it starts optimizing apps again. Now I left it for 2 hours, my phone didnt boot up.
What should I do? I didnt flash any new kernel, rom, recovery or anything else. Im on CyanogenMod, with CWM recovery. I dont want to factory reset, because of my photos and videos.
Even I tried to start in safe mode, but I couldnt get to it, and Im not really sure that I tried to enter safe mode properly.
Please help!
Click to expand...
Click to collapse
Ahh I would suggest you to get TWRP, The world has moved on and I think you should too! It's just a little better at things overall. TWRP can be flashed through ODIN. As for the Bootloop, try dirty flashing the ROM. Just wipe the dalvik/ART and cache and leave the rest as it is.
Dinara° said:
Ahh I would suggest you to get TWRP, The world has moved on and I think you should too! It's just a little better at things overall. TWRP can be flashed through ODIN. As for the Bootloop, try dirty flashing the ROM. Just wipe the dalvik/ART and cache and leave the rest as it is.
Click to expand...
Click to collapse
What do you mean on “dirty flashing”? Do I lose my data if I flash my rom again?
Bence98007 said:
What do you mean on “dirty flashing”? Do I lose my data if I flash my rom again?
Click to expand...
Click to collapse
No you don't, dirty flashing = installing the same ROM without wiping or resetting any data sets, just reflashing that zip again, JIC some files got corrupted, if that doesn't help you might have to give it a fresh start.