so i rooted my fascinate. also installed the ryanZs one click lagfix V1.0 that i got off the market. i also installed the EXT2 tools that it said to install. well everything was working great till today. verizon pushed a update to my phone and i had no choice but to accept it. i tried to remove the battery to get rid of the update option but it kept coming up as soon as it booted. so i accepted it. now my phone wont boot properly. i tried to do a wipe of the partition and a factory reset also a wipe data thru the recovery mode. but nothing happend.
now i get:
TwLauncher (process com.sec.android.app.twlauncher) has stopped unexpectedly.
The process android.process.media has stopped unexpectedly.
The process android.process.acore has stopped unexpectedly.
plus a bunch more. now i cant access anything but the recovery mode.
WTF? what do i do now?
Make Odin your friend using Adryn's method
fixed it. that freaked me out for a bit. i called verizon to complain about the update issue. they are sending me a new phone. said i can keep this one too. after a search for the .TAR file i used odin to replace the file. now im back in buisness and i got a new phone comin for free.
Seems without adding anything to my A7, in the past day it is literally non stop FC'ing on the above process. I hit Force Close and it keeps coming back (not immediately, more like randomly without 10-25 seconds). Only thing I've did extra n the tablet lately is play Angry Birds. Should I try to clear it's DB even though I haven't loaded it today? Also would like to state that I have rebooted and even shut down the tablet, and it still does it.
what have you done to it? stock firmware update? DexterMod? Stock fresh out of the box?
netstat_EVO said:
what have you done to it? stock firmware update? DexterMod? Stock fresh out of the box?
Click to expand...
Click to collapse
Guess in my first version of this thread, before I edited it, I had that information (morning brain fart).
DexterMod v1.3 + BT Fix
Worked fine yesterday morning then it started FCing out of the blue. I've begun (even though none of the apps were installed immediately prior to the FCs) uninstalling widgets that I installed. Next is to start on programs (I did however uninstall Button Savior as I know it loads on startup so I was thinking that was causing it even though it had been on the device for a couple days running flawlessly).
Got tired of messing with it. Did a Cache Partition Wipe and Device Wipe and it's back to normal DexterMod v1.3. This seems to have resolved the issue so it must have been something with one of the databases on the applications that I had installed. Will see once I reload all my apps.
I'm running the latest version of ACS, and I keep getting a force close loop for "com.sec.android.provider.logsprovider", when I boot. Meaning I tap force close, and it comes right back, giving me no access to my phone. This is after two crashes (using the phone then it turns off). Does anyone have a suggestion? My father's Evo did this too, and he had to scream at Sprint before they'd swap the phone, but it's working fine now. I have the insurance thing on my plan, should I try that? If so, would I have to use Odin first?
Did you try to restore a backup with titanium backup??? I would boot to clockwork recovery and try to fix permissions by going to advanced in the menu.
Already done. I wiped user settings or whatever too. I'm now trying to reflash ACS and it says can't open /sdcard/foo/bar/syndicatefro110-standard-signed.zip (bad) could it be my sdcard? Does Sprint cover those under my hardware thing? I'm using ext4 afaik.
Im not sure if the cover the sd card I want to say no unless it is under a month old. However I wouldnt bring the phone in like that I would odin to a stock unrooted rom. Try to recopy the acs rom to the root of your sd card and then wipe data/factory reset 3 times in clockwork and then try to reinstall the rom.
I've been having issues on all my roms, so I'm thinking it could be my sd card. I'll bring it in as a last resort. Don't want to Odin if I can avoid it. Thanks for the help.
the logs provider has to do with mms and call logs and the sd card shouldn't affect it since it is a system app data/data/com.sec.android.provider.logsprovider. Did you try to clear the dalvik in advanced within clockwork???
That's crazy, I'm having the same exact problem. I was running the latest ACS fine for weeks and then I just rebooted it and BAM, 'Force closes' like crazy!
I reformatted, cleared all cache and factory reset to no avail. I still kept getting the same things pop up. I finally installed it through the zip file the 3rd time and somehow iit's working fine. I lost all my apps and evidently they didn't back up to my google account.
I'm too scared to reboot myphone now since that's what seems to trigger the problem.
Anybody know the source of the problem?
Curious if your getting any oneDram errors in dmesg? Seems like you guys are starting to have those odd errors were seeing in the Bonsai 4.1.0 beta.
Sent from Bonsai 7.0.3
I don't think i saw a oneDram error message, I remember seeing force closes for most of the services or processes that usually run in the background like phone and DRM service.
The persistent force close message that kept popping up was the logs.provider one.
This problem is currently happening to me now
I'm to lazy to fix it now though by the end of the week I'll do something
This happened to me while I had very bad/varying signal
(0-2 bars on a six bar scale)
And low battery
(40%ish)
I clicked on my email app and while it was loading I locked my phone and walked toward a window for better signal
When I looked back at my phone it rebooted by it self and everything is force closing like email and messaging.
Sent from my SPH-D700 using XDA Premium App
Yeah that's very similar to how out started with me too. Actually it might be exactly how it started.
Please let us know what you find out, because I've actually had this problem once before with an ACS rom.
I had my phone do this the other day with the logs provider. Reinstalled the rom (ACS Latest) and the issue went away...
Brother has been having the same issue for weeks on his epic too. He was running Bonsai 4.0.1 getting the same force closes, only his started first when he tried to open his mms app... He installed the latest ACS to see if it was Bonsai, about an hour later got the force closes again until he had an endless loop again.
We checked our memory blocks just for giggles and noticed he has 3 bad blocks while i have 11... cant be the issue...
He would get those force closes on EB13 and DK28 too.
We always do the 3x 3x 3x dance in clockwork before installing a rom too...
Dont know if this info helps or not. He thought about going stock and hitting up a Sprint store today and taking out an insurance claim....
Sorry I missed this thread.
Here's what I want you guys to do.
Back up your sdcard to your pc. ( just the files you wanna save.
Format your sd card with your phone
put the rom zip on your sdcard
Back up everything with your favorite back up program. titanium or mybackup root.
Reboot into cwm make sure it's 3.0.0.6
Wipe data, cache, dalvik 3x's ( don't cheat )
Flash your rom.
Boot your phone.
Restore your back up from your backup program. ( apps only no data )
Reboot into cwm again.
This time only wipe cache and dalvik 3x's ( no cheating )
Reboot and you should be good to go
Sent from my SPH-D700 using Tapatalk
^ This is a guaranteed solution to any unexpected FC problems.
k0nane said:
^ This is a guaranteed solution to any unexpected FC problems.
Click to expand...
Click to collapse
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Top Nurse said:
I wish it was, but it isn't a guaranteed solution. It might work 99% of the time.
Sent from Bonsai 7.0.3
Click to expand...
Click to collapse
I said for FCs, not bricks.
I'm having the exact same problem with the same ROM. The other day it froze after I took a picture and wouldn't respond. Had to do a battery pull after which I was stuck in an endless boot loop.
Tried just reflashing the ROM from SD and no dice, then cleared all caches 3 times and reflashed and I had a working phone again.
Then about 10 minutes ago I was using the phone and it shut down out of nowhere, after that booted back up with a tone of force closes and now the log provider force close won't go away. I'm just going to switch ROMs cause this is ridiculous.
No need to do that. The solution for freezing is excrutiatingly simple - and if it only freezes when you're in the camera, you need only format your SD card.
Do that, wipe data, and reflash, and everything will work 100% perfectly.
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
darksideauto said:
i had this issue more than once. and any kind of restoration of a backup made after the fc started resulted in continued fc's. i had to start fresh no backup and restore.
Click to expand...
Click to collapse
As expected - Nandroid bad data, and your bad data will remain. Use MyBackup Root for that.
Just take a Nandroid backup and restore it when you're running properly - or use the zip in the development section to turn journaling on. No problem.
I'm getting the error "Unfortunately, the process android.process.a core has stopped." about every 8-20 seconds. The only thing that stops it is deleting my Google account under settings>accounts.
Earlier, I had OAPK4 and backed up my apps and settings with Titanium. I then installed Smoothrom3.1 and cleared cache partition and Dalvik after flashing. I then restored my apps and settings. Everything was fine for a couple hours and then the problem started out of the blue. Like I said, delete my Google acct and it goes away. Sign back in and it immediately comes back
AFAIK, that process is for home launcher mate, try installing other launcher, nova or apex is recommended BTW, hehehe.
Tapatalked from my N7
bossfrog said:
I'm getting the error "Unfortunately, the process android.process.a core has stopped." about every 8-20 seconds. The only thing that stops it is deleting my Google account under settings>accounts.
Earlier, I had OAPK4 and backed up my apps and settings with Titanium. I then installed Smoothrom3.1 and cleared cache partition and Dalvik after flashing. I then restored my apps and settings. Everything was fine for a couple hours and then the problem started out of the blue. Like I said, delete my Google acct and it goes away. Sign back in and it immediately comes back
Click to expand...
Click to collapse
You must not switch between different ROMs without wiping because it may lead to unexpected behaviour, but even restoring ROM internal settings from a different ROM may cause force closes. Wipe everything, log in again and your force closes should no longer appear.
Sent from my Nexus 7 using xda app-developers app
Fixed. I started clearing caches on Google related stuff and it finally stopped when I did a Clear Data on Contacts Storage and that seems to have fixed it. Been good for over an hour now. Fingers are crossed.
Has anyone else encountered problems running Fix Permissions from Rom Manager lately?
After Steven's warning here http://forum.xda-developers.com/showpost.php?p=49990427&postcount=62, I did a clean install and did not replace Browser or Gallery, all went well for a while, but then I began getting Trebuchet FC errors, rebooted to recovery to run Fix Permissions, but it is not avalible in the 6.0.4.7 CWM recovery, so I tried it through Rom Manager - noticed that it now has "toasts" rather than the old console type display, set it aside and let it run. Came back to my homescreen rather than the "reboot now" message that I was expecting. Re-booted and noticed a few user apps were missing, also got a few "android.process.media has stopped" errors as well as Trebuchet FC's. Convinced that I had a bad install, I formatted system, data and cache and flashed the latest nightly - 2/19 - oops, see http://forum.xda-developers.com/showpost.php?p=50470383&postcount=119 - getting stuck on the bootloader convinced me that I had something wrong with the EMMC, so I followed Leapinlar's (thanks again) Partition Repair guide at http://forum.xda-developers.com/showthread.php?p=28457126#post28457126 - of course, the same thing happened again because of the bad nightly. Finally re-flashed the 2/15 nightly and got everything working again, ran fix permissions just to make sure. Actually sat and watched about a half dozen "toasts" and then my display went black, with occaisional SU "toasts" popping up until my homescreen came back on after about 10 minutes - not back to Rom Manager, no reboot warning, just sitting at my homescreen. I let it sit for another 10-15 minutes and rebooted, after starting, a few user apps missing, "android.process.media has stopped" errors as well as Trebuchet FC's. I started a Logcat and ran Fix Permissions again, same thing. Logcat is at https://dl.dropboxusercontent.com/u/20993724/lc022014.txt if anyone is interested, I am going to report to ClockworkMod.
After re-formatting system, data and cache, 2/20 nightly installed fine, all has been well for the last few days, but have not run fix permissions.
I believe koush and cm decided that fix permissions is not needed anymore.