Database Info

[HELP] Cannot add google account - can't establish reliable connection

I have been using my XT926 for some months in the UK now and have to say its a brilliant phone. Since yesterday however i have been unable to sync anything related to google (gmail, contacts, etc). I had rooted a little over a week ago so thinking something had gone wrong i performed a factory reset. The reset went fine and the phone booted up to a stock state but when it came to adding my google account i got the error "cant establish a reliable connection to the server...". At first i figured this must be a connection issue but after loading up the web browser i'm able to load all sites including google web mail so my connection is perfectly fine. I then got hold of my galaxy tab 2 and checked my google sync status on there - it was working fine. I'm now sat here with a phone that has no google services and i'm wondering what has gone wrong ? I've searched online and many have similar problems where clearing the cache or factory resetting has solved it but in my case this hasnt helped. Any ideas ?

checked this thread already, I assume!?
http://forum.xda-developers.com/showthread.php?t=2110225

StefanGA said:
checked this thread already, I assume!?
http://forum.xda-developers.com/showthread.php?t=2110225
Click to expand...
Click to collapse
Hi Stefan, I hadnt seen that thread prior to you linking it so havent tried the solution. I'll re-root my device and give it a go but after factory resetting i'm sceptical to this working. Something would appear to be seriously wrong with my phone.

Hi Stefan,
Just wanted to say thanks for pointing me in the right direction. Rooted, deleted hosts file and all is working again. I guess the factory reset didnt restore the hosts file from when i previously rooted. I'm just happy to have this amazing phone back working again !

Great to hear I could help. thanks for the feedback - that's why I like this community. Have fun!
Sent from my XT925 using Tapatalk

Contact sync not working?

i'm stock rooted and thats it. happens when unrooted as well and even after performing a factory reset and wiping everything.;
Google Contact sync is broken, on my nexus 5 every time I check it it says ""Sync is currently experiencing problems. It will be back shortly"
it has said this since 6/5/2014 and its now 6/10. what gives? anyone else have this issue?
im looking in Settings>Google>Accounts>Contacts

nextelbuddy said:
i'm stock rooted and thats it. happens when unrooted as well and even after performing a factory reset and wiping everything.;
Google Contact sync is broken, on my nexus 5 every time I check it it says ""Sync is currently experiencing problems. It will be back shortly"
it has said this since 6/5/2014 and its now 6/10. what gives? anyone else have this issue?
im looking in Settings>Google>Accounts>Contacts
Click to expand...
Click to collapse
It has been going in and out for me as well the past couple days. It'll fix itself my manually forcing it to sync for me. Must be an issue server side.

It has been a common occurence for me - so I switched to using my outlook.com contact list instead. Somehow, that works, all the time, without any issues

My google sync was giving me the same issues. I manually pressed sync and after the third of fourth time it seems to have worked normally.

[Q] android.process.acore has stopped, on ALL lollipop roms, after complete wipe!

Okay, guys, here's the problem. I have been pulling my hair out for days over this. On any Lollipop ROM I install, no matter what combination of gapps and AOSP ROM I install on my OPO, after completely and totally formatting caches, system, data, and /data/media, the problem persists:
Always after logging into an account, but not always the same one, I start to get an error "android.process.acore has stopped." It happens every few seconds and renders the device unusable. I have tried every fix I could find online, including wiping contacts storage data, contacts data, etc. I have formatted my phone several times, and each time the problem comes back. It only stops when I disable Contacts Storage in settings, which then in turn disables all contacts functionality.
This is getting totally ridiculous, and the only thing I can think of is that the AOSP version of contactsprovider.apk is totally corrupt. Any ideas?

I have the same problem... Did you succeed in resolving it?

flolep said:
I have the same problem... Did you succeed in resolving it?
Click to expand...
Click to collapse
Somewhat. The issue manifests itself when Facebook is synced with your contacts, and you use Facebook OAuth to sign into another app. For whatever reason, this causes the contacts app to go nuts, and the only way to fix it once it happens is to get rid of the Facebook app. It's a bug that is quite beyond me to fix. There is a modded Facebook apk floating around somewhere, that has had permissions modded so it's not allowed to use your contacts or register as an account in your phone. That works. It also works if when you install a new ROM, you sign into any apps that use your Facebook login before you install the Facebook app, that way you log into them with the browser and they never talk to the contacts app. Once you have installed the Facebook app, DO NOT EVER click "Sign in with Facebook" in any app on your phone, or you're screwed again.
That's pretty much what I've come up with thus far. Hope that helps.
EDIT: Here's the link to the thread with the modded Facebook apk: http://forum.xda-developers.com/showthread.php?t=2333637

I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.

prometheus1010 said:
I have the same issue on all CM12 based roms. It seems to happen for users with many contacts (hundreds). Uninstalling facebook seems to fix the problem for me. I have no such problems on my Nexus 5 with the same setup and facebook installed, so I wonder if it's not something specific to the bacon CM12 code.
Click to expand...
Click to collapse
It happens for other phones users... See here : https://productforums.google.com/forum/m/#!msg/nexus/Ip-hdFEQccY/OSFCz4Qj59oJ
Thanks for your partial solution @jkotzker... For me it's a no go because I am a big facebook user and I can install app with Facebook account linked at anytime... It's really really annoying to not log with Facebook account if the Facebook app is installed I don't know what to do... I tried everything like you.

I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help

marcviado said:
I've recently been getting the same issue but mine says "unfortunately the process com.android.phone has stopped" everything was fine had this phone for about a month was on a lollipop ROM and that just randomly popped up. At first I thought it was the ROM so I switch to another lollipop ROM and got the same issue. So I went back to the latest ota kk ROM and til now I'm still getting the pop up. What's going on here? Please help
Click to expand...
Click to collapse
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app

pablo1215 said:
Oh yeah I've been trying to figure this out since cm12 unofficially came out for the note 4. Like all of you said it's fine for a while or sometimes it's messed up right away. I've had it work for two or three days then out of nowhere just have the error pop-up and never go away. Disabling google contacts storage also got rid of the error for me but of course I can't have the phone without google contacts and sync. This last time it happened just by downloading and signing into Dropbox, which isn't related to Facebook at all. This is belong frustrating because nobody seems to have a fix and it's the only thing stopping me from using cm 12. Is there any Dev that can help or work on this with a logcat?
Sent from my SM-N910T using XDA Free mobile app
Click to expand...
Click to collapse
I didn't find one...
I talked about this problem in xda temasek rom thread and ak kernel thread without success. I even sent a message on official cyanogenmod website, with last crash and logcat attached. No success. The problem happened in 2012 too... And since then, Google didn't have a solution for it.
It seems that Google is finally aware about this problem and the correction could arrive in "a future version"... Well. I want it now... Indeed, there seems to be only to increase the buffer transaction between applications and contact storage from 1MB to 2MB for example, to have it corrected. But no dev wants to do it because the problem cannot be reproduced! And it's rare! But we have it! It's incredible to have it back after a full wipe... And happening randomly, just after a random sync between application and Android system...

Any more updates on this issue/ anything else we can do to get this resolved? Even my partial, temporary solutions have stopped working, and I am getting really frustrated.

Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.

t3chn0s1s said:
Glad to see I'm not the only one here with this issue. Took different search terms to eventually land me here since this such an old and somewhat common issue. Nonetheless... Same problem. OnePlus One running Temasek CM12. Disabling contacts storage.... Blah blah blah. Its rather disappointing there's no actual solution instead of a workaround. But, I'm finally happy to know its Facebook. An app I rarely use but do need unfortunately.
Edit: wondering if anyone has had any luck fastboot flashing the factory image? I know it's a pain in the ass to have to back up all your files, etc off the device so I'd like to know if anyone has had success or even tried this. Cuz, I really won't feel satisfied until I've resorted to this last measure if there's the possibility of eradicating the problem.
Click to expand...
Click to collapse
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.

Aditya Srinidhi said:
I initially had this problem when I switched to lollipop, not sure how it fixed itself but I'm guessing it's the contacts sync like you posted here; only the first time I accidentally synced Fb contacts, and due to the massive number of friends on it, it crashed. But you can disable any sort of sync services on Fb and continue using the app for everything else, I've had no issues since.
Do you mean luck with fixing this issue after flashing the factory image or only returning to stock? Because I've had no issues returning to stock from lollipop by flashing the factory images through fastboot.
Click to expand...
Click to collapse
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.

t3chn0s1s said:
I meant with flashing the factory image via fastboot to stop the frustratingly obnoxious pop ups of the process stopping (w/o uninstalling FB). You answered my question.
So, get this... Resolved the error by uninstalling Facebook. Today I picked up a Moto 360 and you HAVE to install Motorola Connect to really personalize the device... Once I allowed it to see my Google+ account info the android.process.acore started again. I'm SO annoyed. Gonna try a factory reset again and see if that helps. The only way to stop it is to uninstall Motorola Connect and that really sucks cuz I want to (of course) mess with my watch. I know nothing of Android Wear yet or how to root, etc the 360 so.... Here I go. Boldly. Lol
I'm just curious why I haven't seen more people having this issue. It's been plaguing me now for almost 2 weeks. I'm ready to throw my Bamboo OPO out the effing window. WTF.
Click to expand...
Click to collapse
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you

Aditya Srinidhi said:
It's mostly not because of lollipop, but might be the app itself, I read a few others having this problem on other forums with HTC, the solution they found was to clear data on contacts storage. Give that a try and see if it works, if not I'd suggest going back to Stock or probably the new OxygenOS which is supposed to be out by now. Check out @timmaaa index thread in the general section, it has all the necessary stock images you need. Report back and let us know if it fixed the issue for you
Click to expand...
Click to collapse
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.

t3chn0s1s said:
Yea, I tried clearing contacts storage numerous times to no avail. I can live without the app... At first I thought it was a requirement to change watch faces... But, I do have a backup of stock, rooted but I can't go back to KK after being so used to LP. I'm def going to jump on Oxygen just to try it out but I'm guessing I'll end up running stock CM12s. I can't wait. I'd much rather have a stock (w/root of course) or mostly stock device that actually works completely.
Click to expand...
Click to collapse
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.

flolep said:
The bug has been corrected by Google themselves with Android 5.1. Finally!.. So, like me, just try omni 5.1 or last cm12.1 unofficial and the error has gone! So good to use my phone.... Hmmm... How to say... Normally... Lol.
Click to expand...
Click to collapse
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?

Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.

t3chn0s1s said:
Very nice. Glad to hear this... Xposed isn't compatible with 5.1 yet, right?
Click to expand...
Click to collapse
No. Not yet. But. Well. CM12 is already good functionality wise. And with this bug disappeared it's really a happiness.
---------- Post added at 12:42 AM ---------- Previous post was at 12:39 AM ----------
tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Yeah, yeah. Already tried... Lol. I think I tried every single advice given in all the Android forums of the world on this bug lol. Well. Google finally heard us. +++

tmjm28 said:
Two things to try…
Go into settings/apps , press the menu button and select "reset app preferences". Reboot
You Can also try entering the following in your commands:
Su (enter)
Killall rild (enter)
reboot
Should have read the entire post, glad that has been fixed by google, I experienced the same thing and it's a huge pain in the butt.
Click to expand...
Click to collapse
Neither worked but thanks for the suggestion. I did find a Facebook work around. Found the Lite Version via a Google search (since its technically not available in the US) , installed it and it works fine. No android.process.acore FC's or repeated pop ups.

Update: This problem reared its ugly head again on CM12 and I ended up having to uninstall Twitter this time. So, now I'm on CM12s and as soon as I logged into my other Google account user Boxers email app I got the android.process.acore crash again. Uninstalling that app immediately stopped it. God I can't wait for 12.1 for our OPOs. This problem is absolutely ridiculous. I can't take this anymore. I really can't use ANY social media apps unless its like Tinfoil for FB or Twitter. I don't have any connected accounts except Google & Cyanogen.. Which I truly can live without but... Just for the hell of it.... Knowing I have a backup and I'm about to clean flash the latest stock build I tried to add Waze and it caused the crash all over again. Uninstalling Waze didn't help. I shouldn't have to deal with this. Only way to stop it is to disable contacts storage. Once it begins it doesn't stop. Effing Google with their half baked crap.

I restored my phone using Mobile Upgrade Q, but now I'm locked out

After doing a full reset on my phone using Mobile Upgrade Q (which successfully removed CM and TWRP from my phone) I get an error message when trying to set up Android saying "sign in with a google account that was previously synced on this device." I've only ever used one google account with this device, so I'm not sure what the problem is.

passaloutre said:
After doing a full reset on my phone using Mobile Upgrade Q (which successfully removed CM and TWRP from my phone) I get an error message when trying to set up Android saying "sign in with a google account that was previously synced on this device." I've only ever used one google account with this device, so I'm not sure what the problem is.
Click to expand...
Click to collapse
Its factory reset protection, you have to log in with the google account associated with the phone prior to reset.... To avoid this in future or if you sell phone just remove your Google account in settings... accounts before factory reset... It's the equivalent of iCloud locking on Apple, designed to cut down on theft.... If you cant remember the password you can go to the Google account recovery page for assistance
https://accounts.google.com/signin/recovery

I don't understand. I WAS logged into the account prior to the reset, on CM. It's the only account I've ever used on this phone, and I haven't changed the password.
How do I unlock it? Is it even possible, or does it think I stole the phone?
Is it possible to reinstall TWRP and CM now? Just to have a useable phone?

passaloutre said:
I don't understand. I WAS logged into the account prior to the reset, on CM. It's the only account I've ever used on this phone, and I haven't changed the password.
How do I unlock it? Is it even possible, or does it think I stole the phone?
Is it possible to reinstall TWRP and CM now? Just to have a useable phone?
Click to expand...
Click to collapse
If you reset it any other way than from settings reset phone (i.e. Recovery mode or something like mobile upgrade Q) without first removing your Google acct your locked out for 24 hours(used to be 72 hours).

kal250 said:
If you reset it any other way than from settings reset phone (i.e. Recovery mode or something like mobile upgrade Q) without first removing your Google acct your locked out for 24 hours(used to be 72 hours).
Click to expand...
Click to collapse
But if it locked me out with the correct information, how can I be sure it will let me in after 24 hours?

passaloutre said:
But if it locked me out with the correct information, how can I be sure it will let me in after 24 hours?
Click to expand...
Click to collapse
Here is a writeup on how and why frp works like it does....
http://www.pcnexus.net/2015/12/what...gle-72-hour-lockout-android-lollipop.html?m=1
There are some hacks around it, but I have never tried them, best method to avoid frp headaches is to simply remove your Google acct prior to any reset

Is there anything special I have to do to login in 24 hours? Is it 24 hours from the first time I reset or the last time I reset (I wiped it a few times trying to get in)?

kal250 said:
Here is a writeup on how and why frp works like it does....
http://www.pcnexus.net/2015/12/what...gle-72-hour-lockout-android-lollipop.html?m=1
There are some hacks around it, but I have never tried them, best method to avoid frp headaches is to simply remove your Google acct prior to any reset
Click to expand...
Click to collapse
Thank you for the link. Just to be clear, in case future people ever find this thread: during the 24 hour lock out, you cannot unlock the phone, EVEN WITH THE CORRECT ACCOUNT NAME AND PASSWORD. Oddly enough, the device can still receive phone calls, and displays the caller's contact name. So it's definitely logged into my account, it's just locked out of doing anything except receiving calls. Also, I can hear that the phone is receiving text messages, though I have no way to read or reply to them.
Once I unlock it, I will update this thread with how and what it looks like, again, just in case someone finds this thread in the future, because this information is hard to find.

Same
passaloutre said:
Thank you for the link. Just to be clear, in case future people ever find this thread: during the 24 hour lock out, you cannot unlock the phone, EVEN WITH THE CORRECT ACCOUNT NAME AND PASSWORD. Oddly enough, the device can still receive phone calls, and displays the caller's contact name. So it's definitely logged into my account, it's just locked out of doing anything except receiving calls. Also, I can hear that the phone is receiving text messages, though I have no way to read or reply to them.
Once I unlock it, I will update this thread with how and what it looks like, again, just in case someone finds this thread in the future, because this information is hard to find.
Click to expand...
Click to collapse
I have the same issue were you able to unlock it? The only way I got back in was by installing cm12.1 but I would like to go back to stock.

Yes. 24 hours after my last reset, I was able to log in and unlock the phone.

dereks1989 said:
I have the same issue were you able to unlock it? The only way I got back in was by installing cm12.1 but I would like to go back to stock.
Click to expand...
Click to collapse
Before running mobile upgrade Q just remove your Google account in settings, I believe that will allow you to safely reset without triggering FRP...

Nice!!!
passaloutre said:
Yes. 24 hours after my last reset, I was able to log in and unlock the phone.
Click to expand...
Click to collapse
This happened to me yesterday so I hope it works for me as well.

You know what, I just happened to be looking for the official Alcatel factory flash tool and came across this post because after a few factory resets I was able to get the phone to boot up......BUT, as described above, the phone will only accept the PREVIOUS password which I forgot.... I simply requested a new password be created and it doesn't unlock the phone.
So now I too must wait 24, wow.
This is BS.. I mean, yeah I factory reset the phone because after my son accepted a system update, his phone kept bootlooping and his battery doesn't want to accept a charge now (so it seems per the display).....but what if I want to sell my phone? We have to remove the gmail account prior??????? Wow way to go Alcatel. And if this is actually an Android feature, it sucks.
Now, can anyone direct me to the actual official Alcatel upgrade tool????? I want to just flash this stock unrooted phone to out of box condition so we can trade his phone in. The Alcatel website no longer offers it from what I can see. Thanks!

igotroot said:
You know what, I just happened to be looking for the official Alcatel factory flash tool and came across this post because after a few factory resets I was able to get the phone to boot up......BUT, as described above, the phone will only accept the PREVIOUS password which I forgot.... I simply requested a new password be created and it doesn't unlock the phone.
So now I too must wait 24, wow.
This is BS.. I mean, yeah I factory reset the phone because after my son accepted a system update, his phone kept bootlooping and his battery doesn't want to accept a charge now (so it seems per the display).....but what if I want to sell my phone? We have to remove the gmail account prior??????? Wow way to go Alcatel. And if this is actually an Android feature, it sucks.
Now, can anyone direct me to the actual official Alcatel upgrade tool????? I want to just flash this stock unrooted phone to out of box condition so we can trade his phone in. The Alcatel website no longer offers it from what I can see. Thanks!
Click to expand...
Click to collapse
It's an android security feature introduced in 5.1 LP, it only triggers the wait if you reset any way other than from settings. It's similiar to an iCloud lock, so yes if you sell phone remove google account, or if your buying a used phone make sure the google account is removed prior to reset, or boot up phone and make sure you can get passed the lockout before buying it!!
http://www.alcatel-mobile.com/global-en/support/softwareUpgrade/list

kal250 said:
It's an android security feature introduced in 5.1 LP, it only triggers the wait if you reset any way other than from settings.
Click to expand...
Click to collapse
at last i understand why i never ever heard of it
my 6039y is still on 5.0.2 and i never removed gmail accout before made a reset with mobile q or any other way and google never did anything.

Can't Reset the phone - Keep flashing teamwin...

I can't do much with this phone right now. It keeps flashing teamwin. I am able to get to recovery, but it doesn't erase the phone. I haven't touched this phone for close to a year. I remember I had problem with the GPS and kept getting Google crash report with the calendar and email app...
I don't know how to deal with this. Can I send you the phone, and you would be nice enough to fix it back to stock for me?
......

axesd said:
I can't do much with this phone right now. It keeps flashing teamwin. I am able to get to recovery, but it doesn't erase the phone. I haven't touched this phone for close to a year. I remember I had problem with the GPS and kept getting Google crash report with the calendar and email app...
I don't know how to deal with this. Can I send you the phone, and you would be nice enough to fix it back to stock for me?
......
Click to expand...
Click to collapse
What are u trying to do? Explain further more