Database Info

android.process.acore keep crashing after fresh RUU flash

I was having this issue where I couldn't make calls or get my contacts to come up without seeing
Unfortunately, the process android.process.acore has stopped
keep crashing. I finally decided it was best to RUU the 1.85 image and start from scratch. Well that didn't solve the problem! Any ideas what is going on? I can't bring up my contacts, make phone calls, and my google acct won't sync contacts. Any ideas anyone?

google.com
see if that works huh
http://www.shaneycrawford.com/2011/...d-process-acore-problem-on-an-android-device/
Your Android device (tablet, phone, Android TV) gives you the following message.
“The process android.process.acore has stopped working.”
The solution:
Settings –> Applications –> Manage Applications –> All (button on the top that lets you see all applications) –> scroll down to “Contacts Storage” –> Click on “Clear Data”.
This worked on my Android TV and I have seen reports of it working on other Android devices.
Click to expand...
Click to collapse

expertzero1 said:
google.com
see if that works huh
http://www.shaneycrawford.com/2011/...d-process-acore-problem-on-an-android-device/
Click to expand...
Click to collapse
i tried all that already. clearing all the data off apps. factory wipes, master resets. ran out of ideas to try.

I am in the same boat right now. Was having some different issues so I decided to RUU 1.85 and then rooted and unlocked. After installing cleanrom, I start getting phone, contacts, and messages to start crash with no error message. After a while it started giving android.process.acore errors. I've tried:
-Factory wipe, cache and dalvik wipe
-Re-flashing the ROM
-Flashing a different ROM
-clearing app data for contacts, Google framework services, etc.
-fixing permissions
All with no fix. Next step for me was RUU again, but it sounds like that won't do it. Any thoughts out there would be appreciated.
Sent from my HTC One XL using xda app-developers app

this happened when i first installed clean rom 4.0. I immediately re-installed 4.0 and it fixed it. strange... I see some devs say you must wipe 3 times before installing any rom. its worth a try. Also maybe use a different recovery than you have been using. most important thing is to re-download the rom and check the MD5. dude the other day downloaded the rom 6 times with different MD5 before he got a good download. If that is the case, check the memory on your computer as well as hard drive. either of those bad could be corrupting the download. Good luck.

nugzo said:
this happened when i first installed clean rom 4.0. I immediately re-installed 4.0 and it fixed it. strange... I see some devs say you must wipe 3 times before installing any rom. its worth a try. Also maybe use a different recovery than you have been using. most important thing is to re-download the rom and check the MD5. dude the other day downloaded the rom 6 times with different MD5 before he got a good download. If that is the case, check the memory on your computer as well as hard drive. either of those bad could be corrupting the download. Good luck.
Click to expand...
Click to collapse
+1..thats why i always verify md5
Sent from my HTC One X using XDA

Verified the MD5 on the ROM, all checked out there. I'm re-downloading the RUU from a different mirror, so we'll see how that goes. May give switching recoveries a try in the meantime.

Well I was able to get mine to work. I switched back to CWM from TWRP, wiped and installed CleanROM (had Nocturnal running). After the wipe and then flash of CleanROM, I was shocked to see the Nocturnal boot animation. I figured something had gone screwy, and I wiped 5 times in recovery, and then installed CleanROM on top of itself 2 extra times. Rebooted and now all is working again. Not sure what the main issue was from the beginning, but hope this helps you out a little OP. Maybe run RUU again?

ddebart2 said:
Well I was able to get mine to work. I switched back to CWM from TWRP, wiped and installed CleanROM (had Nocturnal running). After the wipe and then flash of CleanROM, I was shocked to see the Nocturnal boot animation. I figured something had gone screwy, and I wiped 5 times in recovery, and then installed CleanROM on top of itself 2 extra times. Rebooted and now all is working again. Not sure what the main issue was from the beginning, but hope this helps you out a little OP. Maybe run RUU again?
Click to expand...
Click to collapse
i'll try switching back to cwm from twrp. what version of cwm worked for you?

trant01 said:
i'll try switching back to cwm from twrp. what version of cwm worked for you?
Click to expand...
Click to collapse
ok well after switching back to cwm and doing wipes for 5 times before installing cleanrom 4.1 it finally worked. can make calls and text without having that error. thanks for the input!!

Thanks for this post. Had the exact same issue. Reverted to the 1.85 RUU and still had it. CWM + Flashing a rom a couple of times and wiping multiple times did the trick.

Glad to be of help. I was stressing over this issue for about 2 days myself. Good to hear it helped someone else too.
Sent from my HTC One X using xda app-developers app

[Q] BlackBean (BAKED) ROM - apps stopping

I wanted to post this in the BAKED thread in the developer section but I don't have enough poststo do it there, so hopefully someone here can help.
I just flashed crespo BlackBean 7 (BAKED) ROM (on my Nexus S) and inverted gapps. It seems to have installed properly but whenever I reboot I get a message that several processes have stopped such as YouTube and GMail, and when I go in to system settings -> storage I get a message saying "Unfortunately, Settings has stopped". I get that message every time consistently. I've tried re-flashing the ROM but to no avail. When I installed the ROM I wiped "Dalvik cache", wiped "Battery Stats" and wiped "Cache partition".
It appears I've not done something or done something wrong, so if anyone here can help I'd appreciate it.

Did you full wipe before installing the rom? That means factory reset/data wipe.

polobunny said:
Did you full wipe before installing the rom? That means factory reset/data wipe.
Click to expand...
Click to collapse
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?

volan1 said:
I did not do a factory wipe because the last time I did that I lost everything, even after using Titanium backup to back up all my apps first. When I tried to restore there was nothing there to restore. Is there a way to use Titanium backup so that after doing a full wipe I can still get my stuff back?
Click to expand...
Click to collapse
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.

volan1 said:
So I bit the bullet and did a full factory wipe, but I still get the "Unfortunately settings has stopped" error showing up. I wonder if it's a bug in the ROM.
Click to expand...
Click to collapse
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S

anshumandash said:
Storage settings fc is a bug in the ROM. It will be fixed in the next version. You should not get fc for any other settings. Back to kill is faster than normal. Everything else works fine on bb7.
Sent from my Nexus S
Click to expand...
Click to collapse
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?

volan1 said:
Thank you!
I saw the back to kill thing, someone else had mentioned it on the BAKED thread too. Thanks for the info on the fc.
I got another problem though, that made me revert to my previous ROM. I was about to put my phone away for the night and decided to do one more reboot, but it never went past the BAKED splash screen. Even after pulling the battery it wouldn't boot. Is this a known bug too? Or did something happen to my machine? After booting to recovery and re-installing my previous ROM, everything seems to be fine.
Any thoughts?
Click to expand...
Click to collapse
There isn't any boot issue with the ROM. If you decide to try this ROM again, try to do a clean install.
Boot into recovery, do a factory wipe, go to advanced & wipe dalvik cache, go to mounts & format /systems. Flash ROM & gapps, reboot.
Sent from my Nexus S using xda app-developers app

Seriously at a loss for what has been happening with my phone.

Ive been having some issues pop up with my phone in the last few weeks. Sorry but be prepared for a lengthy post haha.
It all started in Dec with the OTA of JB. After than my Maps/Nav constantly force close. I am not the only one with this issue because looking at recent reviews of Maps in the Play store, a lot of GS3 users are experiencing it too.
I made this thread: http://forum.xda-developers.com/showthread.php?t=2115108 to try and see if there was a fix. Never solved the problem.
My friend was running the latest AOKP Milestone ROM and said his Maps/Nav worked fine. So I rooted, bootloader, recovery and flashed AOKP Milestone. Well Maps/Nav still didnt work. Found out my friend never installed the official OTA to JB and went from ICS to AOKP. So it only lead me further to believe that it was something with the update.
Figured I would wait it out till there was a fix, until I started having another issue. I use Handcent as my primary SMS app. All of the sudden one day my notification ringtone stops working. Was working fine then poof doesnt work. Tried redoing all the settings and got nothing. Uninstalled and reinstalled nothing. Cleared cache, uninstall/reinstall nothing.
So now with this problem persisting for a few days I got sick of it. Thought I should be able to flash an MD5 thru Odin back to ICS, get Maps/Nav working (along with txt tones) and then flash to AOKP. First I flashed I535VRALF2 and Maps/Nav worked fine, flashed AOKP and didnt work. So today I flashed I535VRALG1 and again Maps/Nav/Txt worked fine. Flashed back to AOKP and Maps/Nav didnt work, BUT txt tones did (for a while). Driving from home to work (15mins) somehow my txt tones stopped working again!
Between each flash I would factory reset/wipe cache/dav data ect. Not sure why these problems are being so persistent. Even on the last time back to ICS, I wiped everything in CWM and booted the phone AND did a factory reset from within the phone settings.
Anyone have any ideas? Did accepting the JB OTA just perma F me on Maps/Nav?

No ideas?

I don't run aokp but found this in the faq on rootz: "Fix permissions in CWMR.Uninstall maps updates/clear cache and data."
No idea if it will help but it won't hurt to try.
Sent from my SCH-I535 using xda app-developers app

Ya I tried that already and it didnt work
And Ive also tried running older versions of Maps as well with no results

Try doing a superwipe. Completely erases internal memory. I know some roms have the option, specifically synergy to my knowledge. It is also available as a zip. Just make sure everything on internal you want to save it backed up to external or a computer. A fresh wipe can do wonders.
Sent from my SCH-I535 using xda app-developers app

NZitney said:
Try doing a superwipe. Completely erases internal memory. I know some roms have the option, specifically synergy to my knowledge. It is also available as a zip. Just make sure everything on internal you want to save it backed up to external or a computer. A fresh wipe can do wonders.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I did (I think haha). I installed a fresh MD5 thru Odin, then once my phone booted, I used the internal factory reset option to completely wipe the internal storage. Or is that not the same thing?

http://forum.xda-developers.com/showthread.php?t=2121347
Try running the mega wipe zip with the Rom on external sd. If you are restoring
Apps, do so without data first to see if everything works.
Sent from my SCH-I535 using xda app-developers app

NZitney said:
http://forum.xda-developers.com/showthread.php?t=2121347
Try running the mega wipe zip with the Rom on external sd. If you are restoring
Apps, do so without data first to see if everything works.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Will it work on the GS3? That thread is for the Note2
And im running the latest touch CWM and that thread is a bit confusing, it says:
Requirements: You need to have
1. TWRP Recovery installed
Quote:
How to use:
Just copy the required zip to your External SDcard and reboot into CWM recovery. Install the zip and you are good to go!
Click to expand...
Click to collapse
It says you have to have TWRP recovery but then says boot into CWM, so not sure what to think.

any more ideas?

Anyone else?

[Q] Constant app lock ups - even after reinstalling

Hi all. I've had an issue for a few weeks now. I have apps that are constanly locking up and force closing on my phone. I'm currently running Jelly Beans 11 with a rooted and unlocked GS3.
All different apps force close: gmail, play store, kik messenger, system processes. It seems it's not centralized to gapps for instance.
I've installed Beans 5, 6, 8, 9 once. 10 about 2 times, and version 11 i think 3 times. Each time I do a delvik cache wipe, a cache wipe, and a factory reset via CWM. Some times even the initial setup wizard will lock up after first boot.
I've tried flashing different modems as well, and i'm currently on the newest verizon one, the K3.
If anyone has any information on how to fix this it would be much appreciated. Even a full phone wipe or something... I'm going to try clean rom and CM 4.2 tonight.
In a seperate issue, that may or may not be related:
I'm currently in iraq and i'm using the world phone exploit to get cell service and data here in Baghdad. It used to work great, but now the data connection will be connected, but no data will upload or download for long periods of time. For example i could send a kik message while connected to EDGE network, but it might take an hour for it to actually send. It didn't used to do this...
All things considered i'm wondering if I actually physically damaged the phone somehow...
If I haven't provided enough information, please let me know and i'll be happy to reply.

Ok, i tried CM 4.2 and there weren't any lockups. But i couldn't keep the rom, doesn't seem to be any way to get cell service. it won't let me change the band to global.
Going to try clean rom now.

Clean rom works fine as well...
So why would Jelly Beans ROM, that's worked fine for quite a while for me, through various versions of ICS and JB, to suddenly cause apps to force close and general instability?
I've checked MD5's and they're correct...
I think i still need a few more posts before i can post in the dev section as well.
Any help is appreciated, thanks

Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app

bobAbooE said:
Have you tried fixing permissions?
Here's how I flash a rom:
Wipe data/ factory reset
Wipe cache
Wipe dalvic
Format system
Flash rom
Boot the phone, wait 5 min and then wipe cache and dalvic again. I then fix permissions and then boot the phone and profit.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
+1
fixing permissions is a must after a flash/restore.

ok i'll try installing beans again and using fix permissions afterwards.
Thanks

still not working
Ok, i've tried fixing permissions and i'm still having problems. Gapps has stopped working... System UI has stopped working... I followed the above posts exactly.
Any other suggestions?

Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app

bobAbooE said:
Are you flashing gapps or just using that term to describe the apps from Google?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
gapps was the term that the phone said when it crashed. But no i'm not flashing the gapps, they're included on most of the roms like Jelly Beans 11. I've had a few different gapps force close, like the store and gmail. but i've also had the system ui and kik force close.

Sorry man, it's beyond my knowledge. Never had a bunch of apps stop working that fixing permissions or a clean install didn't fix.
Sent from my SCH-I535 using xda app-developers app

How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.

SlimSnoopOS said:
How did Beans build 10 work for you, was that running fine? There are only two things I could suggest since you've tested normal suggestions already:
1) Beans removed a few files from System/Bin on Build 11, these are all included in Build 10. Maybe your phone needs those in order to work properly:
gsiff_daemon
mpdecision
qosmgr
smdexe
This is why I ask was Build 10 working fine for you? If so, maybe pulling these files from the Build 10 zip then putting them into System/Bin, setting permissions as rw r- r-, and rebooting could help. Or it could not.
2) Try flashing with TWRP recovery and see if the FC issue pops up.
Click to expand...
Click to collapse
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?

Icewolf69 said:
Well I think 10 was when the issue started but i'm not sure anymore. I've flashed so many versions in the past week, from 5 to 11 that i've forgotten. I'll see if I can't do that though and see what happens.
should I do a factory reset? i mean is there an equivelant to formating a hard drive and reinstalling windows that i can do on an android?
Click to expand...
Click to collapse
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.

SlimSnoopOS said:
To be consistent, its best to clean flash (factory reset/dalvik/cache) build 10 just to see if it works fine.
The equivalent to a Windows reinstall would be using Odin to flash a stock image. Using Odin, you would reset your phone back to fresh out of the box, bloated Verizon OTA. I feel that's unnecessary though cuz you flashed CleanRom and had no issues. If you flash another TW JB rom and have no issues, then it's more telling. As of now, something specific in Beans Build 11 (we'll verify b10 soon) is causing issues for you. Are you restoring any apps with Titanium Backup or restoring text messages using another app?
Edit: to detail a little more about the Odin route. After flashing the stock image, then you would need to root, unlock, install a custom recovery all over again and THEN flash Beans build 11. Idk if you want to do all that, esp if you haven't confirmed if this is something that's been happening with prior builds or with other roms.
Click to expand...
Click to collapse
I just did a fresh install of 10, including cache, delvik, factory reset, system partition, and after first boot i went back and fixed permissions. I'm still getting force closes. media service, google play, etc. I don't have many apps on it yet to see what else will force close since i'm not using titanium backup to restore anything. Everything is fresh and coming from the play store...
I should be hitting 10 posts soon so i'll be able to try and post in the beans thread, or the dev section. But any other ideas would be appreciated. Thanks.

I also seem to be getting a lot of "invalid file" and "file couldn't be downloaded" when i try to install apps from the store. Not sure what this means

Beans 12 came out today and I tried installing that and i'm getting the same issue.
Tomorrow i'm going to do a full wipe to stock verizon image. and go through the unlock and root motions unless someone has any more ideas.
Thank you for the help so far, i appreciate it.

I did a complete stock OTA flash last night to verizon's jelly bean, and went through the root and unlock process again. flashed beans 12, and i'm still getting the same error.
I'm on beans 6 right now and it's working great. Going to try changing a few settings in 12 to see if it works and then maybe see if 10 works.

[Q] Need Help after rooting implosion

UPDATE: 07-04-14 5:25pm EST:
I was able to get all my data off using a mac. I re-flashed Purity ROM after doing a full wipe. I have now re-installed all most of my apps and have begun normal use. For now this is resolved hopefully I have no further issues. Thanks for the response @Kreateablaze Much appreciated.
So here is a brief history about what I did and what I am experiencing. I am pretty much a newb here so please be gentle and excuse my ignorance.
Just in case you don't want to read my book below:
TLDR: rooted phone, Installed TWRP, installed Purity Rom, system failed hardcore, cant get data off my phone because explorer crashes. I just want to get my data off so I can re-install a ROM or just flash back to stock and re-lock the bootloader.....
-Unlocked bootloader, rooted, and installed TWRP using "Wug's Nexus Root Toolkit"
(just want to give props to any one involved in that tool, it is an amazing tool and worked flawlessly!)
-After running the toolkit, I was successfully rooted and running TWRP.
-I ran a back up using TWRP. Is that what is referred to as a "Nandroid" back up?
-After running this back up I installed "Purity ROM"
-For the first 24 hours everything was fine.
-I had to reboot my N5 due to an app that was acting up and a reboot usually cleared up the issue if force stopping didn't. (an app I used before rooting and I knew how to fix the issue I was having, I don't think this is related to my issue.)
-After rebooting the phone, I was faced with a pop up stating something along the lines of android UI has stopped working. I clicked okay, unlocked the phone it flashed black with my home screen icons and everything went back to normal. I rebooted the phone again just to make sure that was a one time fluke. This time The phone was in an endless crash cycle. Every process I could think of was crashing non stop the phone was unusable. I did some research and found something that said to go into TWRP and run a permissions repair.
-After running permissions repair my phone booted back up and was working relatively okay.
-After the repair rebooting my N5 results in that same UI crash I got the first time. BUT the phone is usable, and that process never crashes again unless I reboot.
-After running that permissions repair some of my apps disappeared. Trying to re-install them results in a -24 error. I got a few of them to re-install by clearing related data in data/data folder. A few of my apps refuse to re-install even though there is no trace of the data in the data/data folder.
-Another issue I am having after all of this is that I can NOT pull any data off of the phone. I plug it in, Windows recognizes the phone but it takes about 10-15 minutes to load the folder structure. I am then unable to copy any of the data off of the phone. Explorer crashes and I cant get the data off. UPDATE: I was able to get the data of the phone by using a friends Mac. I will post an update with some more info.
-I need to get my data off the phone before I can continue but am unable to. Any help would here would be greatly appreciated.
-Also if any one knows a more stable ROM with a similar feature set to Purity that is fast, has good battery life and isn't packed to the gills with features tht may one day cause more issues that they are worth. Please let me know.
Thanks in advance for any help you guys may be able to offer me.

Well I'm not too sure what your issue could be, but purity is one of the most stable roms on here... Have you looked in the purity thread for posts saying the same thing happened? I highly doubt it is the rom.
Sent from my Nexus 5 using xda app-developers app

Kreateablaze said:
Well I'm not too sure what your issue could be, but purity is one of the most stable roms on here... Have you looked in the purity thread for posts saying the same thing happened? I highly doubt it is the rom.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
I would definitely agree that something went wrong rather than the ROM being unstable..... Any idea about how to get my data off the phone. at this point that is my main concern so I can re-flash purity....

basik17 said:
I would definitely agree that something went wrong rather than the ROM being unstable..... Any idea about how to get my data off the phone. at this point that is my main concern so I can re-flash purity....
Click to expand...
Click to collapse
I'm not too sure, I never had to get the data off my phone using a computer, always just used titanium backup. Maybe try reflashing purity, just wipe cache not any data.
Sent from my Nexus 5 using xda app-developers app

Kreateablaze said:
I'm not too sure, I never had to get the data off my phone using a computer, always just used titanium backup. Maybe try reflashing purity, just wipe cache not any data.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thanks for your response. I was able to get my data off using a friends Mac... I am going to reflash Purity and see how things go. If they dont go well I may go back to stock. I never seem to have good luck with these things...