Develop Bugs

[Q&A] [STOCK] [NO ROOT] android.system.acore crash after 20b OTA

Hey all.
At my whits end. I just got the OTA for 5.0.1 (20b) to upgrade from 4.4.2 (10r). I was quite happy with the stability of 4.4.2 since my previous phone was an HTC One M8 with 4.4.4. I really like 5.0.1, unlike most people, I like the interface and added features, even though not all 3rd party apps can still not write to External SD.
But ever since I installed the official update, "android.system.acore" keeps crashing, preventing me from using any Google service, Dialer, Contacts, composing Email (through AquaMail), and using LG Backup. Called T-Mobile tech support and they said that this process is part of the central Android system and affects basically everything. That they have never had a report of this on any recent phone and haven't seen it since very early Android systems (Pre-ICS). They said the only sure way of fixing this is a Factory Reset.
Obviously I would prefer NOT to do that. Any solutions? Please. Prefer not to root, but will if I have to, especially if I can easily unroot.
HELP! [emoji29] [emoji24]

bluealchemy17 said:
Hey all.
At my whits end. I just got the OTA for 5.0.1 (20b) to upgrade from 4.4.2 (10r). I was quite happy with the stability of 4.4.2 since my previous phone was an HTC One M8 with 4.4.4. I really like 5.0.1, unlike most people, I like the interface and added features, even though not all 3rd party apps can still not write to External SD.
But ever since I installed the official update, "android.system.acore" keeps crashing, preventing me from using any Google service, Dialer, Contacts, composing Email (through AquaMail), and using LG Backup. Called T-Mobile tech support and they said that this process is part of the central Android system and affects basically everything. That they have never had a report of this on any recent phone and haven't seen it since very early Android systems (Pre-ICS). They said the only sure way of fixing this is a Factory Reset.
Obviously I would prefer NOT to do that. Any solutions? Please. Prefer not to root, but will if I have to, especially if I can easily unroot.
HELP! [emoji29] [emoji24]
Click to expand...
Click to collapse
Unfortunately when stuff like that happens after an update, a factory reset is a must. Especially to a big update like lollipop that has a lot of systems changes.

The same thing just happened to me this morning. Last night I started getting massive duplicate text messages - 1 every 15 minutes for the whole night. I tried clearing the messaging app and storage data and cache, multiple resets, different text apps, etc and nothing worked. This morning the acore message started running every 5 seconds. I've tried clearing the contants app and storage cache and data and that doesn't work either.
I'm mentally gearing up for a factory reset unfortunately. Given that I generally dislike all of the user interface and behavior changes in v5, this is just adding insult to injury. I'll probably end up rooting just to get things back to where I liked them...

TD22057 said:
The same thing just happened to me this morning. Last night I started getting massive duplicate text messages - 1 every 15 minutes for the whole night. I tried clearing the messaging app and storage data and cache, multiple resets, different text apps, etc and nothing worked. This morning the acore message started running every 5 seconds. I've tried clearing the contants app and storage cache and data and that doesn't work either.
I'm mentally gearing up for a factory reset unfortunately. Given that I generally dislike all of the user interface and behavior changes in v5, this is just adding insult to injury. I'll probably end up rooting just to get things back to where I liked them...
Click to expand...
Click to collapse
If you don't like the interface, not to dissuade you from rooting, but you could always install an alternative launcher. That doesn't 3ven require root or a custom ROM.

vel0city said:
Unfortunately when stuff like that happens after an update, a factory reset is a must. Especially to a big update like lollipop that has a lot of systems changes.
Click to expand...
Click to collapse
So then should I just reset and not upgrade to 5.0.1, stay at 4.4.2? Or reset and reupgade back to 5.0.1? Or stay at 4.4.2 until the next update after 5.0.1 (which at the rate LG goes, could be years)? Or would it be safe to use a custom or stock ROM with Lolly? Or should I just assume that 5.0.1 is completely toxic for my phone.

bluealchemy17 said:
So then should I just reset and not upgrade to 5.0.1, stay at 4.4.2? Or reset and reupgade back to 5.0.1? Or stay at 4.4.2 until the next update after 5.0.1 (which at the rate LG goes, could be years)? Or would it be safe to use a custom or stock ROM with Lolly? Or should I just assume that 5.0.1 is completely toxic for my phone.
Click to expand...
Click to collapse
if you do factory reset after you upgrade ROM, it will stay at whatever ROM you have, in your case 5.0.1.

bluealchemy17 said:
So then should I just reset and not upgrade to 5.0.1, stay at 4.4.2? Or reset and reupgade back to 5.0.1? Or stay at 4.4.2 until the next update after 5.0.1 (which at the rate LG goes, could be years)? Or would it be safe to use a custom or stock ROM with Lolly? Or should I just assume that 5.0.1 is completely toxic for my phone.
Click to expand...
Click to collapse
According to your post you upgraded to the Lollipop rom already via OTA. So by factory reseting your phone now it will still be on the lollipop. But I am saying that by reseting the phone, you will have all your errors fixed and lollipop should be stable as KitKat if not better. If factory reset does not fix your issues that means that the updating process on your phone did not finished correctly, which is rare, then you would need to flash via KDZ. But if you are not against rooting and custom recovery, I highly recommend you do that instead of flashing KDZ.

Update for folks: I ended up doing a factory reset (what a pain) which fixed the problem. A few hours later as i was logging back in to all my apps and accounted, acore started failing every 5 seconds again. I read on a different forum that it was liked to Facebook trying to sync contacts which killed the contacts app. I uninstalled Facebook and everything works fine. So it looks like a bug in Contacts that something in Facebook is hitting and causing it to die.

Has anyone managed to install 6.0.1 OTA on 100% stock device?

I am 100% stock, I repeat, 100% stock. The bootloader is unlocked. I got an OTA yesterday for 6.0.1 MMB29K but this morning I found my Nexus completely drained so I charged it and powered on. Seems it was drained by a bootloop. I tried flashing 6.0.1 manually again today with fastboot (bootloader.img, boot.img and system.img). I'd prefer to not reset my device until someone can confirm that something isn't wrong with 6.0.1. Thanks!

mertzi said:
I am 100% stock.... I'd prefer to not reset my device until someone can confirm that something isn't wrong with 6.0.1. Thanks!
Click to expand...
Click to collapse
Same here. 100% stock with unlocked bootloader.
I got the OTA update yesterday and got stuck in a bootloop on the 'spinny circles' animation after the 'optimising apps' stage. The only thing that was not completely 101% stock was that I had disabled several of the Google bloat apps like Docs, Show, News, etc. etc. Whether that makes any difference or not, I don't know.

im on stock 6.0 and my tablet doesn't boot up after the 6.0.1 update install.
its stuck in infinite boot loop.
tired clearing the cache partition from recovery but in vain!
any help?

Mine is 100% stock and upgraded to 6.0.1 without any problems.

strumf666 said:
Mine is 100% stock and upgraded to 6.0.1 without any problems.
Click to expand...
Click to collapse
Same here on mine...NO problems with the OTA update.

Still waiting on the OTA for my completely stock N7... I feel like mine is always at the back of the cue. Will let you know when I get the update of I have a problem with it.
Sent from my Nexus 7 using XDA Free mobile app

Just finished sideloading the ota on mine and I've had no issues on the tablet but I had issues on my laptop with a no protocol error so a heads up if anyone runs into that error.

$!> said:
im on stock 6.0 and my tablet doesn't boot up after the 6.0.1 update install.
its stuck in infinite boot loop.
tired clearing the cache partition from recovery but in vain!
any help?
Click to expand...
Click to collapse
6.0.1 running fine on my very stock unrooted N7/2013. Installed via OTA.

Bob Denny said:
6.0.1 running fine on my very stock unrooted N7/2013. Installed via OTA.
Click to expand...
Click to collapse
mine was never rooted,bootloader was never unlocked,nothing done to my tab which the manufacturer hadn't done!
it was fine till 6.0 update and i got a notification to download and install the new update i.e 6.0.1 which was around 63mb in size and now all my tablet is stuck in infinite boot loop till the battery drains.
tried clearing cache from recovery but in vain!
i don't want to format/factory reset as i have data which is very important.
any help would be much appreciated!

Yeah i'm having the same issue too. 100% stock 32gb Nexus 7 stuck on bootloop after installing the update.

Couldn't be lack of space in /system could it? Just a SWAG believe me.

The OTA worked fine for me on a stock, unlocked and unrooted razorg (LTE), coming from MRA58V.

I have the same issue. Stuck after app optimisation during boot. 100% stock, no root, not twrp recovery. I have the feeling that this is somehow connected to disabling google apps (applications-> disable, no titatium backup or the like), since it happened after I rebooted after disabling most of the google apps. Can someone who got 6.0.1. working flawlessly confirm that no google apps have been disabled in the system?

I'm rooted but I did notice that there is *0* mb left in /system after I updated to 6.01, maybe use the Uninstall System Apps app and delete Google Sheets Docs and Slide and see what happens?

I'm totally stock and never had an issues updating

SM-T800 after root all apps crashes

I've rooted my galaxy tab s 10.5 SM T-800 with android version 5.0.2
after rooting the tablet everytime it boots display message "unfortunately <application> has stopped"
and even pressing ok keeps appearing for other message for other app nonstop
I cannot access android home screen even

I doubt it's because of root. Try wiping dalvik cache. If that doesn't fix it you may have to flash the stock firmware.

When I had this issue I found that doing a factory reset helped temporarily.
It's temporary because when I rebooted the device the same crash happened

ashyx said:
I doubt it's because of root. Try wiping dalvik cache. If that doesn't fix it you may have to flash the stock firmware.
Click to expand...
Click to collapse
I've wiped the dalvik cache
but still the same problem
is there any solution other than stock firmware?

bsquared938 said:
When I had this issue I found that doing a factory reset helped temporarily.
It's temporary because when I rebooted the device the same crash happened
Click to expand...
Click to collapse
so what was the ultimate solution there?

anybody?

Had this same issue, as I said...
My intention was to root the device and get it working, so I started this thread...
http://forum.xda-developers.com/galaxy-tab-s/help/samsung-galaxy-tab-s-10-5-wifi-semi-t3242433?
(I got some help, including from ashyx who posted above (thanks again!) and have had a working tablet for 4 months now )

sony smartwatch 3 unfortunately bluetooth share has stopped with ROM_SW3_6.0.1_M1D64

I happen that he installed a stable rom and the start after selecting the language and sale unfortunately the bluetooth part has stopped and I can not link my watch with my phone thanks greetings

Same problem here, some tips?

Hello,
I had the same problem. You need to do a factory reset / wipe data in recovery mode on your watch.

But if I have stock rom with no custom recovery?

BeStMaker said:
But if I have stock rom with no custom recovery?
Click to expand...
Click to collapse
In stock recovery you can also reset to factory defaults.
Or boot in twrp recovery from fastboot mode (fastboot boot twrp.img).
Sent from my SM-G935F using XDA-Developers Legacy app

sony smartwatch3 bluethooth problem
is there a way to make work bluetooth module of sw3, or flashing a older firmware will help?

bluetooth has stopped
Hi, I have the same problem, tried few things like factory reset and pc companion repair, but bluetooth still not works

bluetooth not working after update
guiller199210 said:
I happen that he installed a stable rom and the start after selecting the language and sale unfortunately the bluetooth part has stopped and I can not link my watch with my phone thanks greetings
Click to expand...
Click to collapse
i to have same problem, after factory reset i not able to find my watch over any bluetooth connection, im using sony xperia xz .
some one plz fix this bug,
thanku..

OnePlus 3 - Android Oreo Camera Unknown Error!

Hi,
Today im facing a strange issue with camera
Actually all the applications related to camera are not working
It seems there is a problem in the physical camera it self !
Snapchat, instgram once i open its cam, original camera, and google camera..
It shows me this message
"Unknown Error"
My phone is already updated to stable version 5.0 which is oreo.

By the way, I already restart my phone, and also clear the data & cach of the camera : it doesn't work

Just to be safe, have you tried other ROM? If that still doesn't work, then try downgrading to Oreo. If all fails, then welp, at least you know that ROM isn't the cause of it.

dream2poet said:
By the way, I already restart my phone, and also clear the data & cach of the camera : it doesn't work
Click to expand...
Click to collapse
same happened with me on open beta 27.
i clean flashed ob 28, everything good so far.
try a factory reset or a clean flash.

I've had this issue before where I flashed nougat modem onto marshmallow and it gave me this error..it took accidentally wiping my phone to figure this out.
So try reflashing 5.0 rom or check whatever zip you flashed is not the culprit.

F4uzan said:
Just to be safe, have you tried other ROM? If that still doesn't work, then try downgrading to Oreo. If all fails, then welp, at least you know that ROM isn't the cause of it.
Click to expand...
Click to collapse
LELBOT said:
same happened with me on open beta 27.
i clean flashed ob 28, everything good so far.
try a factory reset or a clean flash.
Click to expand...
Click to collapse
tofuboi01 said:
I've had this issue before where I flashed nougat modem onto marshmallow and it gave me this error..it took accidentally wiping my phone to figure this out.
So try reflashing 5.0 rom or check whatever zip you flashed is not the culprit.
Click to expand...
Click to collapse
Thank you guys for helping me,,
I did Factory Reset (without internal storage) and all working fine now..
I think the problem happen because I did not do factory reset once i updated to Oreo