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
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
Earlier tonight I was on Valhalla Final Lightning Zapped. After using titanium backup to integrate some system app updates to rom and adjusting my SD Read Ahead to 4096 I then restarted my phone just to see if any system changed needed to take place because of a needed reboot. But once I rebooted everything kept on crashing and I was instantly bogged with app FC and something about Android Log provider crashed please retry again. Every time I tried to restart the log provider it kept on crashing preventing me from doing anything. So I said let me go back to my lock screen and long press power button to reboot into recovery using advance power menu. So my phone then rebooted into recovery so I tried formatting data, cache and dalvik and reflash my back up of Valhalla Final but when I went to do so I kept on receiving a error saying fail to unmount system partition. So I went to advance settings in recover and clicked on show log then after looking at the log it said system read only so I said dammit man .-. Since the partition was no read only I couldn't flash any rooms at all. Even if I did it would just restore the boot image and restart Valhalla final which kept on crashing because of the stupid android log provider. At the time I was away from my computer so I just decided to try flashing a ics. Risky but bleh at this point my options are slim, I flashed cm9 but phone restarted and showed Android logo with some crazy crash image. So I said to myself I wonder if I could access CM9 Recovery. So I took of my battery cover and pull the battery out and reinsert it. 3 button combo my way into cm9 recovery and install a fresh copy of cm9. I figured though the system partition was read only and at the time a BML state if I try to convert it to MTD it should everything should go back to normal. So on I had went with proceeding to flash cm9. Phone booted perfectly luckily I had a nand backup of cm9 before I had downgraded back to GB. I then went back to recovery to wipe everything and restore from backup phone is run completely back to normal now. Does anyone have any insight on this strange fiasco?
Sent from my SGH-T959V using Tapatalk 2
VillaCastana321 said:
Earlier tonight I was on Valhalla Final Lightning Zapped. After using titanium backup to integrate some system app updates to rom and adjusting my SD Read Ahead to 4096 I then restarted my phone just to see if any system changed needed to take place because of a needed reboot. But once I rebooted everything kept on crashing and I was instantly bogged with app FC and something about Android Log provider crashed please retry again. Every time I tried to restart the log provider it kept on crashing preventing me from doing anything. So I said let me go back to my lock screen and long press power button to reboot into recovery using advance power menu. So my phone then rebooted into recovery so I tried formatting data, cache and dalvik and reflash my back up of Valhalla Final but when I went to do so I kept on receiving a error saying fail to unmount system partition. So I went to advance settings in recover and clicked on show log then after looking at the log it said system read only so I said dammit man .-. Since the partition was no read only I couldn't flash any rooms at all. Even if I did it would just restore the boot image and restart Valhalla final which kept on crashing because of the stupid android log provider. At the time I was away from my computer so I just decided to try flashing a ics. Risky but bleh at this point my options are slim, I flashed cm9 but phone restarted and showed Android logo with some crazy crash image. So I said to myself I wonder if I could access CM9 Recovery. So I took of my battery cover and pull the battery out and reinsert it. 3 button combo my way into cm9 recovery and install a fresh copy of cm9. I figured though the system partition was read only and at the time a BML state if I try to convert it to MTD it should everything should go back to normal. So on I had went with proceeding to flash cm9. Phone booted perfectly luckily I had a nand backup of cm9 before I had downgraded back to GB. I then went back to recovery to wipe everything and restore from backup phone is run completely back to normal now. Does anyone have any insight on this strange fiasco?
Sent from my SGH-T959V using Tapatalk 2
Click to expand...
Click to collapse
Maybe it all started w/ a bad Valhalla Final or Lightning Zap download, check the md5, also if u r trying to flash ics I would recommend using a one-click first (It just seems like it always works better for me when I do that)... and I assume u know about the kernel version b4 flashing ics, right?
Yeah. Seems like I do have to do a one click. Everytime I go to make a call on pics it just ring once and then automatically hangs up
Sent from my SGH-T959V using xda premium
ya I would try that 1st
So here is a quick rundown of what happened:
-DL Beats audio, opened it, it was supposed to restart my phone, but it froze it.
-Could not power off or reset it, had to pull battery
-Was then stuck on the 4G LTE rainbow and would not load. Tried pulling battery nothing.
-Went into recovery mode and tried loading, nothing happened and I read someone say the only way out of it was to wipe everything and start over, so I wiped Data and Cache and Dalvik Cache with Clockwork. Nothing happens.
-Finally I Odin it supposedly back to stock. Hooray I can get into my phone, weird thing is all of my apps are there, email is set up, contacts are there with pics from FB, syncmypix, etc. It even retained the fact that I had disabled the stupid ongoing Wi-Fi notification. Just the homescreens are blank again.
-I never made a CWM backup, I think I made a Titanium backup, I know I used MyBackupRoot (the one that is a life preserver). That being said I thought I wiped everything in CWM. It said it had formatted the internal and external SD.
Question is should I go ahead and try to wipe everything clean again?
Am I going to run into issues using my phone how it is?
Should I back it up and then load a recovery from this or would that be pointless?
Or do I leave it alone and consider myself lucky?
Thank you and by no means am I a developer or anything, just getting back into android after 2 years on iOS and apparently know just enough to get myself into trouble.
If everything is working fine then you sgould be good. You must haved had the restore thing checked or verizon backup crap restored your stuff. When you odin that will flash the file system img so there is no way that your data survived
Did you check the md5 on the beats audio thing before you flashed it? Cause i have ran that fine.
Sent from my CleanRom'd Galaxy SIII
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
Earlier today, I got an error upon starting up my Samsung Galaxy S5 (T-Mobile) that says "Unfortunately, System UI has stopped." My background has been turned to black and none of the buttons work properly. The phone IS rooted (and has been for about a week), but runs on stock OS (5.0 Lollipop) and stock recovery. I have never flashed a rom on this phone. I already tried restoring from a Titanium Backup I made yesterday before this error ever showed up, but it did nothing. Perhaps it's relevant that this error first happened after I booted the phone in recovery mode (to see what stock recovery looked like), then selected "reboot phone." I also already tried wiping the cache partition, wiping the System UI cache, and rebooting is Safe Mode. None of these worked. I thought unrooting the phone might help, but I accidentally uninstalled SuperSU without removing the root. With the System UI down, I can't install any apps at all, such as SuperSU again or a file explorer that would allow me to remove the "su" folder in /system/bin/. Now I have no way of unrooting, short of wiping the phone. I DO NOT want to do that. How do I get my phone back to normal?
--EDIT-- I finally gave in and did the factory reset. I rooted it again using the same method as before (in order to use Titanium Backup), and just to see what would happen I went to recovery mode. Sure enough, I was greeted with the same error as before. I had already rebooted the phone normally multiple times before trying to use recovery mode, so I have no doubt that the stock recovery mode is the cause of these issues.
Signal2Noise said:
Personally, I don't like Titanium Backup. I seem to be in the minority with that opinion, but it's given me issues in the past. Try flashing a non-stock recovery like TWRP for your S5 and either wiping your phone or wiping and flashing another ROM.
Samsung phones seem to dislike rooted users for some reason
Click to expand...
Click to collapse
Too late, I already wiped the phone. I re-rooted using Chainfire's auto-root, then flashed CWM so that stock recovery doesn't screw me over again. Before restoring from the backup, I booted into CWM recovery and restarted the phone. No error. I hope it stays that way, this whole thing is a huge hassle. There really needs to be a disclaimer with Chainfire's auto-root telling people to get rid of stock recovery!
Hi there
You'd be best served asking for help from the experts who own your device, here:
T-Mobile Galaxy S 5 Q&A, Help & Troubleshooting
Good luck