I flashed cyanogen 5.0beta. It was working great.....then i went to compress cache in one of the new apps(can't remember the name) the phone reset itself about 3 times so I wiped it and restored it. Now it completely boots, but then I get a "force close" message that won't go away. If someone could help I would appreciate it.
When you wiped, did you reflash the google stuff and the cyan rom?
I tried wiping it and the re-flashing cyan but I still get the same messages. Thts the only rom I flashed
I mean after you wiped did you also flash the Google Add on supplied in Cyanogen's thread (http://www.mediafire.com/file/jmmzywtlnjd/gapps-passion-ERE27-2-signed.zip) along with the ROM after you wiped?
Also, what is force closing? Is it specific apps? If so, are they system apps are market/3rd party apps? Is it processes that are force closing?
I just wiped and reflashed cyan and then downloaded and flashed the google addon and the I rebooted just fine. now i want to see if i can restore. Plus the force close message was google startup wizard
I think I gotta start from scratch if my titanium backup failed me
Damn. Well at least it's fixed. Thanks for the help. I don't know why the google add on helped but it did.
Related
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
obelisk79 said:
Simplest way to fix this should be clearing the dalvik/boot cache from fresh's kitchen. I really should write up a guide on how to do these simple tasks manually.
Click to expand...
Click to collapse
Will that work on MCR 2.2 as well? I'll look into that. Is it something I can do from recovery?
Ceger
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
obelisk79 said:
yes should work on mcr 2.2 and can be done manually from recovery, I know recovery does dalvik cache, not sure if it also kils the boot cache as well though. The older version only did dalvik.
Click to expand...
Click to collapse
Do you need to do both? Wiping the dalvik cache created lots of app fc issues, which would be fine if the phone actually worked. Still won't make or receieve calls.
And thank you for the assistance.
Ceger
Edit. Clearing the boot cashe got rid of the FC issues. However, still have same issue with the phone app. This is so annoying.
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Ceger said:
I have been having this issue ever since my phone booted up and all my apps sequentally had force close dialogs happen. I am running my apps from the SD and figured something went wrong with the boot up sequence. I tried doing a nandroid backup, reinstall fresh 1.1, but no luck.
I then used my backups to reinstall over all my apps, then went into Market to install them via that. Everything seemed to be just fine, but the phone app would still not dial anything and when I recieved a call, it gives the error "The process com.android.phone has stopped unexpectedly" and then proceeds to try to reset the phone connection. Most times I lose all data connection and need to reboot.
Recently, I tried installing the latest Modoco CDMA rom. No luck. I then did a Titanium backup and force reinstalled everything again. Still no luck.
Anyone have this issue and get it resolved? My Hero can do everything but make and accept calls. I really don't want to do a wipe as this problem can just happen again, so I would rather understand the process.
Thanks in advance.
Ceger
Click to expand...
Click to collapse
use these commands to clear cache
rm -r /data/boot-cache/
rm /data/dalvik-cache/
once you finish then reboot.everything should go away...
he's done that already.
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
obelisk79 said:
honestly the best bet to clear up the issues would be to do a full wipe from recovery. Wipe the phone clean then run the stock RUU and re-root and install your custom rom. Do a nandroid backup first just to prevent losing any of your info.
Unfortunately despite the many well written guides here on XDA there are always a few issues most likely a result of slight hardware quirks or unfortunate circumstances at the time of flashing.
Just for '****s and giggles' have you tried pulling your battery for 30 seconds, reinstalling it and booting the phone up?
Heck sometimes just a reflash of the rom right over top of itself. I've been tinkering with this phone since the day root came out and I still don't fully understand all of it's quirks.
Click to expand...
Click to collapse
Done and done and no difference.
reddick said:
then i suggest to extract the rom zip file, and get into command on your device and go under the system/lib or app and see what is listed in the folders. and compare it to the rom folder.
That's how i was able to fix the voice search on my device, one of the lib file was missing and got it to work after that.
Click to expand...
Click to collapse
Done, even manually moved some files in case they were corrupted at one point. Very bad move, nandroid backup was my friend there.
Guess a wipe will be the only option then. How annoying.
Thanks for all of your inputs.
Ceger
Another thought... would updating my phone with latest kernal compile possibly do the trick? Or how about a replacement process for google.com.phone?
Ceger
Interesting theory.... worth a try.
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
toastcfh said:
i had this issue once and it was because of somehow the uids for the apps got messed up. a wipe should fix this in most cases. but for me it went like ur issue. i almost event went back stock. then i looked into it and found that in my packages.xml file the the uids were all messed up. i had multiple uids and certs for the apps i was having issues with. so what i did was pulled the packages.xml from the device and erased the apps i was having issues with. then pushed it back and rebooted. that cleared the issue. so if i were u i would research that. do a google search on it. then if it doesnt work do the ruu and reroot. good luck man. i know how u must be feeling. i was there
Click to expand...
Click to collapse
Actually, the fix was much simpler. I wiped the SD ext partition and just did a Recovery Wipe. It went back to stock modded rom that remained rooted. I then used Titanium to reinstall my apps with data and then MyBackup to get back some settings such as my scenes, etc. and all was good. Took all of 30 minutes to get my Hero back up and running in better condition than before.
Thanks all for the assists.
Ceger
com.android.phone
com.android.phone
i am facing this prob on cyanogen mod10....when ever i reboot my optimus 2x....i face this damn problem
help plzzzzzzzzzz.....!!!!!
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.
Hello guys, I'm facing a problem.
So I recently made a nandroid backup. I installed just a small mod but didn't liked so I restored
my backup. When I started up I did get a google play services and google process gapps stopped message.
As I clicked OK I immediately tried to open other apps but they all FC. I didn't get error on recovery and
also wiped cache and dalvik. Still facing this problem, what could be the problem? I'm on stock deoxed rom
Well thats normal when you didn't fully wipe. Always fully wipe before restoring backups.
I got a error message: android_secure.img not found
Sounds like this is the proble, but can't seem to find how to fix it..
Oh nice -.- was about to flash stock rom but won't work, write protection is enabled wtf!??
can't do it with odin anybody knows something??
Every single time I try to restore a backup I always wipe data, cache and dalvik and then I restore the backup made with clockwormod in the clockworkmod recovery. But I always get the next message: ''Unfortunately the process com.google.process.gapps has stopped'' which is very frustrating because I have to press ok everytime it appears and every time I close it, it opens again; so I can't use my phone. Also, Google Play, Dropbox, Googe partner setup and I get those messages too. I've searched for help on many sites and they keep telling me to go to apps manager and stop download manager, google play services, google framework, etc. And I managed to go to settings and do it in the only second I have between closing the message and it opening itself again. But it didn't work. Also I wiped cache and dalvik after restoring but still get the loop. The only thing I can do to stop the loop is wiping data but I don't want to lose my data (that's why I made the backup that doesn't work now). I also tried advanced restore and restored everything but data, I didn't get either the loop or the data. And when I restored only data in advanced restore I got the loop. Also I tried flashing the gapps for Android 4.4.2 Kit Kat from recovery but still got the loop. Maybe it happens because I had uninstalled most of the google apps that came as system apps using ROM ToolBox pro?
Hi,
I had been using Temasek's Unofficial CM 11 ROM on my SM-N9005, then I decided to update to lollipop. So I backed up with Titanium Backup Pro, wiped data and dalvik and cache, flashed the AICP ROM, and now I'm trying to restore apps.
Restoring has been difficult in TB - it kept freezing/getting stuck on what seemed like random apps, and then it started to give me "Unfortunately, System UI has stopped" messages, which reappear a few seconds after they're dismissed.
I've somehow reached the point where if I install ONE more app (no matter what it is or whether it's restored from TB or downloaded from Play Store), I get "Unfortunately, System UI has stopped", but if I uninstall it I'm fine.
I know that apps should use more space with the ART runtime, but I have ~7GB of free storage so it can't be that. It seems silly, but is there some kind of app limit in lollipop that I'm unaware of?
Thanks in advance!
Actually the most important thing is what method are you using for restore? I mean are you using the only restore missing apps method or something else? Cause if you are using a method other than that then you will have problems.
elewint said:
Hi,
I had been using Temasek's Unofficial CM 11 ROM on my SM-N9005, then I decided to update to lollipop. So I backed up with Titanium Backup Pro, wiped data and dalvik and cache, flashed the AICP ROM, and now I'm trying to restore apps.
Restoring has been difficult in TB - it kept freezing/getting stuck on what seemed like random apps, and then it started to give me "Unfortunately, System UI has stopped" messages, which reappear a few seconds after they're dismissed.
I've somehow reached the point where if I install ONE more app (no matter what it is or whether it's restored from TB or downloaded from Play Store), I get "Unfortunately, System UI has stopped", but if I uninstall it I'm fine.
I know that apps should use more space with the ART runtime, but I have ~7GB of free storage so it can't be that. It seems silly, but is there some kind of app limit in lollipop that I'm unaware of?
Thanks in advance!
Click to expand...
Click to collapse
Did you take a nandroid backup? If so, Restore it after wiping then use TB to make an Apps Update.zip and copy it across to your ExtSDCard. THEN flash the ROM and GApps - i also flash SuperSU.zip at the same time. Then I start the phone and set up basic info. Then Back to Recovery and run the Apps.zip file.
I also use Nova Launcher so once in I restore the backup and Voila! I have almost everything back as I like it.
Another thing to check is the SDCardfix - you might want to download a zip of it and flash it while in Recovery. Once it is done and you are in LP version it seems OK, but I had to restore and older version of Temasek's ROM and promptly had SDCard access issues until I ran the fix again.
Thanks for your replies!
I am definitely doing "restore missing apps with data", though I am deselecting some of the apps (the very large ones) before restoring if that's an issue.
I didn't take a Nandroid backup unfortunately, I usually don't as I have no need for the data other than apps. Using an "apps.zip" sounds like an interesting approach - I might try that next time.
I'll try to work with the SD card - should I try to find and flash an LP version of SDCardFix or just use the KK one?
I tried reflashing the rom after a data, dalvik, cache, and /system wipe. Then I restored all apps, but the same problem came back, so the problem seems to be replicable.
Some people in the forums have suggested doing a "Fix permissions" in CWM, however that feature was obviously removed. There's a flashable zip that restores the feature apparently. Do you think I should try that or will it have no effect?
Thank you!