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

Flashed boot.img but still at spinning CM10 logo? This might help...

Earlier this week, I had flashed a Rohan's kernel for CM10. For unrelated reasons - I decided to go back to a previous backup of CM10. The backup was of a previous nightly. That nightly was running the stock CM10 kernel.
I did factory reset, restored backup, cleared cache, dalvik, then loaded the boot.img using the One XL All in One Toolkit. I could not get past the spinning CM10 logo. I tried just installing the stable CM10 package, same install procedure and couldn't get anywhere. Just for fun, I tried installing ViperXL to see if I could get *something* to install, and it worked just fine. Hmmm...
Tried CM10, a nightly this time, no luck. Because I was running out of ideas (and had read so many threads here, thanks all :good I decided to try something else. I downloaded the HTC Auto Boot.ini installer (see the thread here http://forum.xda-developers.com/showthread.php?t=1962428) I installed the same nightly I had been trying before, using the same procedure - but this time flashed the boot.img using the HTC Auto Boot.ini one click tool. Well....it worked
Who knows, may have been coincidence but I really feel like I had tried everything else, and maybe for whatever reason, the All in One Toolkit wasn't getting the boot.img to stick.
I just wanted to mention this as something to try if anybody else was experiencing the same problem. The problem could very well have been me, or some other odd situation I created by trying to revert to a backup with a different kernel. The All In One Toolkit was *very* helpful for rooting, etc so I don't want to speak ill of it. It may work just fine for flashing boot.img in most cases. But if you get stuck, well, try the HTC Auto Boot.ini installer and see if it helps you out.

Re: [BeanStalk][1.179] Phone freezes after call

Re: [BeanStalk][1.179] Phone freezes after call
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app

bretcb said:
I am currently running Beanstalk 1.179. I've noticed with this build, and with at least one prior build I can't recall, that after an incoming phone call of at least a few minutes, the caller hangs up, and shortly after, my phone freezes. I'm all cases that I've noticed it, I've answered the phone while it was locked, and it returns to the lock screen before freezing. I've got the lock screen configured to use a password.
I can't recall anyone else mentioning this previously, so I thought I'd mention it. If it's not happening to anyone else, I'll assume it's my own problem.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over

qkster said:
prolly bad flash..wipe it all and flashed the rom and gapps again
if that doesn't work, go back to gb stock and start over
Click to expand...
Click to collapse
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.

bretcb said:
Thank you for the idea. I was just going over in my mind the ROMs that I have installed since I purchased the phone with an early version of scott.hart.bti's ParanoidAndroid already installed, and while I did not experience the issue with any of the ParanoidAndroid versions I installed, I believe I did also experience it while I was running Unofficial CM10 briefly between PA and BeanStalk. Perhaps the problem is indeed my own device, or something more deeply in the build source than with the build(s) themselves.
FWIW, in almost all instances when I installed a ROM, I always followed the entire procedure recommended by scott.hart.bti, including wiping the dalvik cache, as I did with my most recent install of Beanstalk 1.179.
Click to expand...
Click to collapse
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.

qkster said:
as you become more familiar with flashing a rom and the principles, you will find that the cook book process may help but some times you may have to deviate from it to make it work.
ex: sometimes you may have to flash cm9 twice to get into the boot screen ..or flashing cm10 twice or reboot twice..or wipe a few extra time.
from my own experience, you have noticed something not working correctly..(sd not recognized, calls being dropped, app FC's and no one else had the same) you may need to start over...back to gb stock via heimdall or odin and work your way up.
the more i had screwed up and had to go back, there more i learned each time.
Click to expand...
Click to collapse
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.

bretcb said:
Interesting. I remember that it took me forever to build up the courage to update ParanoidAndroid the first time, and scott.hart.bti's clear and complete cook book process certainly helped get me there. I have broken one of the Beanstalk ROMs once, too, and had to look up how to boot into CWM from power off to reflash.
I'm curious why going back to stock would make a difference. It seems to me that if I a doing a complete flash, wiping everything, than it shouldn't matter if it's a stock ROM or a new ROM. I'd be more nervous about breaking something if I going back to stock, since is a more complete and drastic change.
Click to expand...
Click to collapse
yeah...for the most part, while in cwm, factory reset, wipe system, data, cache, dalvik and then flashing a new rom work very well.
occasionally, for what ever reason that i'm not sure, going back to stock..changing file system back to rfs and then changing back to ext4 may be needed to fix certain problems...not common and not routine practice, but is needed...at least imo

OK, fair enough. I will read up more on going back to stock so I'm not unfamiliar with it. Which tool do you prefer?
For completeness of troubleshooting info for anyone else who may be reading, I received a phone call yesterday while the lock screen was disabled, and the phone still froze after the caller hung up. I received another call today, and made sure I hung up first, and no freeze, my phone was fine.
Sent from my SGH-I997 using xda app-developers app

bretcb said:
I will read up more on going back to stock..
Which tool do you prefer?
Click to expand...
Click to collapse
Everyone has their own prefs...I prefer heimdall. It doesn't matter. Whatever it takes to get the job done. You prolly should buy a usb jig too.
http://forum.xda-developers.com/showthread.php?t=1437548

Flash Kernel

So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.

Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
I see that I have the Cyanogenmod Kernel installed currently which I suppose either is installed with Slimbean or it may have been installed because I tried the CM10 rom first, but it wouldn't boot.

what are you doing before flash the new rom?

juancaperez2000 said:
what are you doing before flash the new rom?
Click to expand...
Click to collapse
Wiping the device. Always best in the long run.
Sent from my Nokia RinGo far far away...

Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.

Cobinator said:
So a while back I rooted my S3 i535, and started trying to install customer roms. The only one that would work was Slimbean so I have been using that for a while, but it has begun to occasionally freeze on me.
I would like to try switching over to maybe Liquidsmooth or ParanoidAndroid. My problem is whenever I flash these roms the phone won't boot, and just sits at the splash screen. I am kind of thinking maybe it is because I need to flash a different kernel, but I have never done that and am unsure of which Kernel I should use or the steps I should take in doing this. Any advice is appreciated.
Click to expand...
Click to collapse
Restore your stock rom format internal memory and flash clean rom ASAP brother you will be straight !!!
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 05:45 PM ---------- Previous post was at 05:44 PM ----------
And all the necessary wipes of course
Sent from my SCH-I535 using xda app-developers app

Cobinator said:
Well when I originally rooted and flashed the device it was brand new out of the box. Even then the only custom rom that I could get to work was Slimbean.
Pretty sure I tried all the other custom roms listed here:
http://forum.xda-developers.com/showthread.php?t=1850506
I have installed Slimbean a few time because I started getting errors, and keyboard kept crashing and things like that. I always wipe cache, and dalvik cache.
Click to expand...
Click to collapse
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash

andybones said:
Sorry to hear this, there is no reason why my sg3 would work and yours doesnt though
a ODIN reflash back to stock I assume will fix things.
if you'd like to try a clean stock TouchWiz ROM, please give mine a try and let me know how you like it.
http://forum.xda-developers.com/showthread.php?t=2275376
but from the sound of it, it sounds as though either
you are not waiting long enough for it to boot (first boot can take up to 10-20 mins..)
or not wiping fully in recovery before the flash
Click to expand...
Click to collapse
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.

Cobinator said:
Oh wow can it really take that long for first boot? I know I waited probably somewhere close to 10 minutes, but def no where close to 20.
Click to expand...
Click to collapse
in theory AOSP ROMs should load faster than a Touch Wiz ROM as TW ROMs are around 1 gig for the ROM.zip and AOSP ROMs are about half that, but still I've had ROMs take over 15 mins to load, I know one time I thought it was the phone, but then I wiped fully again, and waited 20 mins and it loaded. I would say anything after 20 mins though, then it's definitely something wrong.

Ok backing stuff up then going to flash back to stock then try LiquidSmooth and see if it will let me boot up. Will let ya know how it goes.

So I install stock un-rooted rom. Then installed a stock rooted rom, then installed liquidsmooth and all I get is the Samsung symbol flashes then it goes black. Then it vibrates and the Samsung symbol flashes then blackness. Just repeats this over and over =(

I noticed you said that you're wiping cache and dalvik, but make sure you're also wiping data and system too.
Sent from my SCH-I535 using xda premium

Please read forum rules before posting
Questions and help issues go in Q&A and help sections
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

My apologies moderator.
Anyways. I wiped everything on the phone before every rom installation. System restore, dalvik, and cache. The custom rom still won't boot.

Flashing new roms

I have tried to do this a couple of times since the new version of BMM came out. I followed all of the instructions to make it work. Then I flashed PACman and I got stuck on the loading (seemed like a bootloop) screen for like half an hour. And no matter what ROM that I use this seems to be happening. I would like to use either the PACman or AOKP that alerted has up. Any suggestions?

at2smithjason said:
I have tried to do this a couple of times since the new version of BMM came out. I followed all of the instructions to make it work. Then I flashed PACman and I got stuck on the loading (seemed like a bootloop) screen for like half an hour. And no matter what ROM that I use this seems to be happening. I would like to use either the PACman or AOKP that alerted has up. Any suggestions?
Click to expand...
Click to collapse
Did you flash the gapps too?
If it were me, I'd FXZ back to stock ICS then root, install BMM, boot into BMM, factory reset, flash ROM, flash gapps then reboot. Works for me every time.
Brought to you by time and relative dimensions in space.

I always make sure that I get the proper gapps.apk file for the version of the rom that I am installing. I think that the only thing that you are doing different than me is the factory reset. Thanks. I will give this a try and i will keep my fingers crossed.

at2smithjason said:
I always make sure that I get the proper gapps.apk file for the version of the rom that I am installing. I think that the only thing that you are doing different than me is the factory reset. Thanks. I will give this a try and i will keep my fingers crossed.
Click to expand...
Click to collapse
You no do factory reset before flashing ROM? That's the cause for bootloop.
And if you have BMM set up and different ROMs on various systems, then doing a factory reset on any system wipes other systems too. You just have to delete the partitions for that system in order to delete it.
And btw Gapps come in flashable zip and not apk

Remember, if you're trying to flash any of the Kexec based ROMs (like anything posted by deveshmanish) and you keep getting stuck at the boot screen, then you may be one of the unlucky "Kexec - rejects" like myself.
If so, then none of those ROMs will work for you. You need to try one of the non-kexec versions. There are several by different devs.
Sent from my personal phone thingy.