Root The process android.process.acore has stopped unexpectedly

[Meerky]

Over the weekend I was playing around with the MT and installed MIUI on it. Love the look of it and a lot of the extra functions and settings. But there were a few things I didn't like over the stock rom that I probably could have adjusted to, but it was just generally slower than the stock rom for me so I finally changed it back the next day to stock rom. Since I installed LauncherPro on the stock rom, it's been much more responsive than the stock launcher.

I noticed though when I went to make a call I got the error message "The process android.process.acore has stopped unexpectedly" and couldn't dial out. The phone would accept incoming calls and connect but I couldn't hear anything at all. After Googling about the issue, what worked for me was to uninstall the updates only for Dialer and Dialer Storage, Contacts and Contact Storage, and Facebook. Then the phone worked perfectly again.

I did have problems going back to stock rom, the backup I made wouldn't work, a few others I found on the net didn't work as well, only the one from this thread finally worked. When I'd restart the phone, it would hang on the initial logo bootscreen and just never go any further (yes, I gave it as much as 30 minutes a few times to be sure I wasn't being impatient). I have since read that flashing the same rom a 2nd time sometimes will work, but I hadn't tried that. I then used my Titanium backups to restore some things, like my contact list, and a few special apps.

Is this a common error on the phone and/or did I do something wrong during the flashing process going back to stock rom (my money is on that I probably did something stupid)? And is there a way I can update those services again one by one to see which one might have been the problem? Although everything is working perfectly now, I've given it a few days to be sure nothing else was wrong, maybe I should just leave those apps alone. I'll admit that Facebook is no longer constantly running in the background!

 

[thangfish]

Hey, what recovery are you using?
I've had the same problem before, and fixed it the same way you did (the going back to stock issue).

 

[Meerky]

I ended up using the recovery.img from this thread, [ROM]Bone Stock & Stock Deodex ROM's Triumph-Now Resets Splash.img!!, the Complete Stock Triumph ROM. It's the only one that would let the phone start up correctly. All the others I tried, including my own backup I had made before doing anything to the phone, would just hang at the initial startup logo screen.

I wish I had read the tip about trying to do the recovery twice sooner, that that often gets it flashed correctly. But I don't want to redo everything again to try and recreate the problem to test if that would have worked with the other ROMs.

Edit: What I think was the major error for me was flashing with that particular stock ROM, and then possibly using Titanium backup to restore my settings... maybe there was something different between that ROM and what was I originally had on the phone? Is that possible how it happened?

 

[BSydz]

I ended up using the recovery.img from this thread, [ROM]Bone Stock & Stock Deodex ROM's Triumph-Now Resets Splash.img!!, the Complete Stock Triumph ROM. It's the only one that would let the phone start up correctly. All the others I tried, including my own backup I had made before doing anything to the phone, would just hang at the initial startup logo screen.

I wish I had read the tip about trying to do the recovery twice sooner, that that often gets it flashed correctly. But I don't want to redo everything again to try and recreate the problem to test if that would have worked with the other ROMs.

Edit: What I think was the major error for me was flashing with that particular stock ROM, and then possibly using Titanium backup to restore my settings... maybe there was something different between that ROM and what was I originally had on the phone? Is that possible how it happened?

The issue you are having with the backup is recovery related. Recoveries above 5.0.2.7 backup stock ROMs as ext4 instead of ext3. This is the fix:

Stock backups made with higher recoveries than 5.0.2.7:
Find your nandroid and rename all files to ext3 from ext4 then open md5 file and change the names there also, then it should work.


I haven't done this in a while and am going off the top of my head but it should work.

Also, the stock ROM you mention essentially does a factory reset, i.e. it wipes data and cache, so flashing over a messed up restore will just put you back to square one, bone stock.

Hope this helps.

 

[Meerky]

I installed 5.5.0.4... would it just be easier to avoid the problem in the future to install either 5.0.2.6 or 5.0.2.7 instead?