Process.acore FC - Thunderbolt Q&A, Help & Troubleshooting

"The process android.process.acore has stopped unexpectedly. Please try again."
When I flash Das Bamf Stripped 1.8, I originally didn't get this error until restoring my titanum backup. I'm assuming that something I restored on the backup is causing this error, but I can't say for sure. Every time I do data wipe, this error goes away, but after restoring, it comes back again. This only applies to Froyo roms, and not to GB roms (same thing happened for Cubed Rom)
I've flash the rom with and without ROM manager, both with the same result.
Edit: Fixed by clearing contacts data

Related

[Q] Bootloop with das BAMF 1.10 PLEASE HELP!

Hello everyone,
I have been reading these threads for a while, getting prepared to root my Thunderbolt. I rooted about a week ago with Revolutionary and had no problems whatsoever. A couple days ago I flashed my first ROM (Gingeritis) using the instructions on this forum, and everything worked great, except that I accidentally restored some system data with Titanium Backup, which I read can cause FCs, etc.
Therefore, I restored the stock ROM by booting into recovery and following those steps. Again, everything went well.
This morning, I wanted to try out a different ROM, so I followed the same steps with das BAMF 1.10, and I flashed the ROM successfully with no problems. However, after restoring my contacts (one of the green pieces of system data that I thought were ok to restore) with Titanium Backup, the popup "Sorry!" repeatedly came up saying that the application.com.android was not responding and needed to be force closed. It came up again so fast after clicking "close" that I couldn't even reset. Finally, I pushed the power button at the exact right time to be able to see the menu of options, and I clicked restart (not in recovery).
Now, the phone is running through the das BAMF and HTC startup screens repeatedly. The battery is pretty low. What do I do???
Thank you so much! I really really want to resolve this and avoid bricking my phone like an idiot.
-Matt
Turn it off. Charge to atleast half or so battery. Boot into recovery, wipe cache, data, dalvik cache, and format system. Load up whatever ROM you want and only restore user apps and data.
Sent from my ADR6400L using XDA App
Just what he said but let google restore the contacts, this us unless you never allowed google to let th them sync.

[Q] android.process.media has stopped.

Hi Guys!
Everytime I flash the latest version of CM9, I am encountering a problem. It flashes fine and everything works, but when I try to re-install all my apps using Titanium Backup Pro, it asks for a reboot and from that point onwards, I keep getting several messages saying "Unfortunately, the process android.process.media has stopped."
Can someone please tell me why this is happening? Thank you in advance.
Rich
coolrich1234 said:
Hi Guys!
Everytime I flash the latest version of CM9, I am encountering a problem. It flashes fine and everything works, but when I try to re-install all my apps using Titanium Backup Pro, it asks for a reboot and from that point onwards, I keep getting several messages saying "Unfortunately, the process android.process.media has stopped."
Can someone please tell me why this is happening? Thank you in advance.
Rich
Click to expand...
Click to collapse
Try to make a clean install of the rom, then restore apps only from Titanium of everything is still ok try restoring data.

Downgrade from LFB, flashed back: Very weird ISSUES!!

I was disappointed with the LFB performance etc so today I tried flashing back to LF2.
Process I followed was this:
1) Directly from LFB, I fashed LF2 tar with Odin without wipe
Problem faced: "android.process.acore has stopped unexpectedly" and "contacts has stopped". Phone remained in a hung state with these messages popping up continuously and totally unusable.
2) Went back to CWM, wiped cache and dalvik cache, rebooted
Problem faced: Still same as above
3) Flashed back to LFB to make phone usable, took full Titanium backup. Then went back to CWM, wiped data (factory reset). Flashed LF2 again with Odin. Worked fine for a bit, then restored Titanium backup to get my apps and settings. Rebooted.
Problem faced: Still same as above.
4) Restored nandroid backup I had of LFB.
Problem faced: None, all working but I am still on LFB and back where I started.
Is there a way to go back to LF2 and keep my apps and data?
Any help will be appreciated and thanked.
Did you restore System apps? You can only use Titanium for non-system apps, since it will otherwise cause these issues.
d4fseeker said:
Did you restore System apps? You can only use Titanium for non-system apps, since it will otherwise cause these issues.
Click to expand...
Click to collapse
Restored only user apps + data.
Could you try installing the apps one at a time until you find the issue?
Titanium shows 294 items.
I don't think I have the patience to install them one by one.
There's another MAJOR problem I'm facing now after doing the nandroid restore.
When I'm on a call, THE OTHER PERSON CAN'T HEAR ME!!
I'll try flashing the ROM again through Odin and see if that solves this issue. If it doesn't, I have no clue how to proceed from there.
Sent from my GT-I9300 using Tapatalk 2
You probably have LFB modem with known problem .
Solutions mess for hours or wipe phone flash clean rom .
jje
Did you have Samsung or Google, or third party app restore settings?
The fact that LFB introduced new settings that it attempts to restore on an rom without these options may cause issues.
OK, this is getting weirder.
I wiped phone clean, then flashed LFB because of above problem. Restored user apps+data with Titanium.
Phone was working fine, until someone called just now. The screen went black and I could hear the ringtone but name wasn't shown. After sometime I got a pop-up message "com.android.phone stopped working". And I couldn't see who called as it wasn't logged either.
Now it gets weirder.
I tried to replicate this issue by calling from my landline and another mobile but it worked perfectly for the 5-10 times I tried. Then I tried another different mobile and the problem occurs again!!! And this is when I have flashed LFB after clean wipe (in CWM) and not restored system apps.......!
Please HELP!! I am getting desperate now!
Lennyuk said:
Did you have Samsung or Google, or third party app restore settings?
The fact that LFB introduced new settings that it attempts to restore on an rom without these options may cause issues.
Click to expand...
Click to collapse
Could this explain the above problem?? Where do I disable it? I haven't enabled anything that's not on by default.
JJEgan said:
You probably have LFB modem with known problem .
Solutions mess for hours or wipe phone flash clean rom .
jje
Click to expand...
Click to collapse
I did a clean wipe and I'm getting a different issue! Pls help!
g4rvd4 said:
OK, this is getting weirder.
I wiped phone clean, then flashed LFB because of above problem. Restored user apps+data with Titanium.
Phone was working fine, until someone called just now. The screen went black and I could hear the ringtone but name wasn't shown. After sometime I got a pop-up message "com.android.phone stopped working". And I couldn't see who called as it wasn't logged either.
Now it gets weirder.
I tried to replicate this issue by calling from my landline and another mobile but it worked perfectly for the 5-10 times I tried. Then I tried another different mobile and the problem occurs again!!! And this is when I have flashed LFB after clean wipe (in CWM) and not restored system apps.......!
Please HELP!! I am getting desperate now!
Try and flash lfb again could just be a bad flash something like this happened to me today
if i helped say thanks
Click to expand...
Click to collapse
g4rvd4 said:
I was disappointed with the LFB performance etc so today I tried flashing back to LF2.
Process I followed was this:
1) Directly from LFB, I fashed LF2 tar with Odin without wipe
Problem faced: "android.process.acore has stopped unexpectedly" and "contacts has stopped". Phone remained in a hung state with these messages popping up continuously and totally unusable.
2) Went back to CWM, wiped cache and dalvik cache, rebooted
Problem faced: Still same as above
3) Flashed back to LFB to make phone usable, took full Titanium backup. Then went back to CWM, wiped data (factory reset). Flashed LF2 again with Odin. Worked fine for a bit, then restored Titanium backup to get my apps and settings. Rebooted.
Problem faced: Still same as above.
4) Restored nandroid backup I had of LFB.
Problem faced: None, all working but I am still on LFB and back where I started.
Is there a way to go back to LF2 and keep my apps and data?
Any help will be appreciated and thanked.
Click to expand...
Click to collapse
Your answer is in number one "contacts has stopped". Don't restore your [CONTACTS/CALLS] in Titanium backup. I have had this same problem before. I hope that helped.

com.android.phone fails every time when accessing Call Settings.

Hi Guys,
I got my S3 a few weeks back and had one of the Omega JB roms on it (think it was v17) and then com.android.phone just started failing all the time. So I took it back to the Stock backup i had done before installing the Rom and wiped/ factory reset before that reinstall. The Nandroid backup was made using CWM recovery.
The phone has been fine since then for the last week, but today I was trying to go into Call settings in Phone and every time I press the call settings link in the menu in Phone i get the "com.android.phone has stopped" error. I had facebook synced to the phone but only when on the Omega Rom and not since I've been back on the stock Rom.
I searched a few things for this and it always seems to come back to FB sync issues which cause com.android.phone errors, but I can't work out what else could be affecting it. I tried reinstalling the phone.apk by using the no-increase-ringing mod, but this also doesn't sort it either. I'd rather not go through a full stock rom re-flash if i can help it as well, but feel I might have to. I can make and receive calls no problem as well.
Any ideas?
UPDATE: Have reinstalled the stock phone.apk from Omega files (the one with the increasing volume) and the problem is now solved.

Bunch of issues, but ended up with : Data not working.

Started with stock, then S-off'd, rooted, and flashed a custom AOSP (can't remember the name). Everything went swimmingly for months.
Out of nowhere, I started getting "internal storage" issues. Internal storage was listed at 1GB, and started filling up regardless of if I deleted things. It seemed to cause slight problems, but nothing serious. Shortly after, I stopped receiving texts altogether. Tried flashing a new ROM, went with MIUI V5, it worked, but still no texts. Decided to start from scratch. RUU, re-root, re-flash recovery, etc etc. Ended up flashing MIUI V5 again, but got stuck in a bootloop. Tried 4-5 different hboots/recoveries/every setting imaginable, nothing. Started over again (RUU >>>), flashed MIUI V5 again, and this time it worked. Load it up, ask a friend to text me, BOOM, text received!
Open up the browser... "403 Forbidden". Wat. Nothing to do about it, it seems. I've tried fiddling with all of the relevant settings, I've downgraded/upgraded radio, nothing. I've flashed to a different ROM and back again, nothing. Just crip-crapity-crap.
As of right now, the rest of my night is going to be spent backing up/flashing to sense to do system upgrades/restoring backup and hoping it works. Anyone know what would cause "forbidden" errors, data wise? Calling/texting works both wase (not MMS, obv).
I think you should try a new kernel
Sent from my HTC EVO 3D X515m using xda app-developers app
Problem was solved by backing up my current MIUI build (working minus data), full wipe, then flashing Harmonia 3.17, doing all available System Updates, full wipe, then restoring my MIUI backup. I now have data, send/receive MMS, and calling, + MIUI V5 totally working.
Finally!
Case closed. Thanks!

Categories

Resources