I recently rooted my stock ATT 4.3 UCUEMJB with CF-AutoRoot which worked like a charm. However I get my work email on this phone which uses Google Apps Device Policy. I now regularly get the "Account Action Error" error constantly, though my email is still working fine. Clicking on the error simply takes me to the download page for Google Apps Device Policy (which of course I have).
Any suggestions on what to try? Thanks!
Related
Hi,
I new to rooting and android and have some questions.
I think I corrupted the google framework on my phone.
I rooted my TMobile SGN2 using the*toolkit and Odin and SU on my phone. I used Option#2-Flash insecure boot image, root and install busybox" . I also installed Titanium Backup Pro and backed up all of my apps but I didnt do a full image backup using CWM or anything*similar*
http://www.youtube.com/watch?v=O6BweCW5ck8.
I also used this method to add the wifi hotspot:
http://forum.xda-developers.com/showthread.php?t=1974109
The phone worked fine for about 1 week but then*I then decided to call Tmobile support because I was having data speed issues on vacation and they told me to reset the APN and Search for Mobile Operators in the Mobile Network settings. *I forgot about the APN changes I had made and it restored the original APN to the factory settings. *
Now I have the following issues with my phone.
1) I constantly get this error and it freezes my phone for 15 seconds. "Unfortunately, the process com.google.process.gapps has stopped"
2) If I goto the gmail app it says, "gmail has stopped" and it doesnt load
3) Now I cannot*load google play store any more so cannot install apps or do updates.
4) My*AllShare Cast Wireless physical Hub tries to connect to phone but doesnt connect anymore.
I have tried emptying the google files cache and stopped and restarted all of the google services, tried rebooting phone, taking out sim card and even went back the the original APN but the problem is still there.
What should I do?
1) Call Tmobile and see if they will send me a new phone? *I do have insurance but the phone is now rooted.
2) Just do a factory restore using this method?*http://www.youtube.com/watch?v=UaZiO8vfrME
If I do a factory restore and the phone still has issues, will they be able to tell I rooted if I decide to use my insurance and get a new phone?
3) Try to use SU or some other way to just fix the issues I have?
PS, when I try to use my wifi hotspot now, the Tmobile Tethering wants me to active and setup their service, so Im no longer able to use my hack.
Please help me.
Thanks!
Sent from my SGH-T889 using xda app-developers app
Try flashing this in odin, http://forum.xda-developers.com/showthread.php?t=1975560 pre rooted odin will fix your errors just factory reset. then odin. let me know.. .... leave tmobile out of it
deeznutz1977 said:
Try flashing this in odin, http://forum.xda-developers.com/showthread.php?t=1975560 pre rooted odin will fix your errors just factory reset. then odin. let me know.. .... leave tmobile out of it
Click to expand...
Click to collapse
I figured it out! It turned out to be some kind of an error while updating the apps from play store. In the application manager there was a disabled update process which after turning it back on worked liked a charm (scroll all the way down to the bottom in the APP MANAGER-->ALL and it will show any disabled apps. Renable the app. I also decided to clear cache of all of the google services, gmail, app store, internet, etc. and then I deleted my google account. I rebooted the phone and added the google account back and viola... Its all back to normal.
But now that my wifi hotspot is not working, should I try this hack instead?
This application requires a "rooted"-device and (probably) a custom-kernel which supports netfilter (iptables). I only rooted my device but no custom kernel? Will it still work for me?
http://www.youtube.com/watch?v=JGWqLRNoJLg
or
http://code.google.com/p/android-wifi-tether/
Last night I tried to flash the Cyanogenmod Installer without success. I tried multiple times and each time I kept on getting this Security Information message on my phone: "An application attempted to access system on your device without authorization. This attempt has been blocked...."
I did delete the antivirus app on my phone and so I know that it isn't that. Could this possibly be Knox? We had been told that the CM team had a workaround for those I747 on Android 4.3, like mine.
Capa1970 said:
Last night I tried to flash the Cyanogenmod Installer without success. I tried multiple times and each time I kept on getting this Security Information message on my phone: "An application attempted to access system on your device without authorization. This attempt has been blocked...."
I did delete the antivirus app on my phone and so I know that it isn't that. Could this possibly be Knox? We had been told that the CM team had a workaround for those I747 on Android 4.3, like mine.
Click to expand...
Click to collapse
If you're rooted, download SuperSU from the Play store (I rooted, but the version of SuperSU that was installed was an old version and needed to be updated by manually downloading from the store). When you run it, it will detect that Knox is running and offer to disable it for you.
WearySky said:
If you're rooted, download SuperSU from the Play store (I rooted, but the version of SuperSU that was installed was an old version and needed to be updated by manually downloading from the store). When you run it, it will detect that Knox is running and offer to disable it for you.
Click to expand...
Click to collapse
I am not rooted.
Capa1970 said:
I am not rooted.
Click to expand...
Click to collapse
I wasn't able to find any way to get around Knox without rooting, but I may not have looked hard enough.
If you're willing to root first, CF Auto Root was super easy to do:
http://forum.xda-developers.com/showthread.php?t=1963790
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Capa1970 said:
Thanks for the reply. I have never rooted not flashed a rom and so I thought that the CM Installer would be an easy way to get started. However, basically like everyone else, they ran into issues with phones that had been upgraded to JB 4.3. They recently posted that they had found a way around it but I started to wonder if in fact they had when I got the message:
"An application attempted to access system on your device without authorization. This attempt has been blocked...."
I was trying to ascertain whether the message was due to Knox or another program?
Click to expand...
Click to collapse
That *is* a Knox message, for sure.
So it looks like the Cyanogenmod team were not able to circumvent Knox for their CM installer. It's probably just a matter of time. Here is the full Knox notification:
"An application attempted to access system on your device without authorization. This attempt has been blocked. Updating your security policy may solve this problem. Deleting applications obtained from unauthorized sources may improve security."
There are three options at the bottom of the screen: Cancel, Update, and View Apps.
Update: I was able two days ago to use the Cyanogenmod Installer and I am now running CM!! First time for me to ever root and flash a Rom (I was an iPhone guy).
The phone is faster and smoother. I never liked the Touchwiz lag and most of the Touchwiz features worked inconsistently. The only thing that I miss is the camera. I have not found any bugs yet and so am very happy thus far.
Alright, this is an interesting one.
So I was on CM 10.2 for the longest time, then I tried CM 11, then finally used SlimKat for a while. Everything was working pretty well on the 4.4 ROMs, except for occasional LTE drops where it just refused to go back to LTE.
Anyway... I decided to go back to a 4.3 ROM. I flashed SlimBean 4.3 first via TWRP. No issues on boot up, LTE works, IMEI intact, WiFi, data, all working. I'm also able to sign in to my Google account - but it only partially works (see screenshot). I also can't sign into any Google services... Play Store, Play Music, Ingress... I just keep getting the "problem communicating with Google servers" error.
Now, I've since tried CM 10.2 again and I've even Odin'ed back to TW 4.3 (MK5). I've fully wiped each time - including full data and sdcard wipe. Every single 4.3 ROM is giving the connection error. I tried going back to a KitKat ROM (CM11) - and it works! No sign in error!
Any ideas what could be causing this?
This same thing happened to me just last night on my Galaxy Nexus after attempting to go back to 4.2.2. The problem turned out to be something to do with 2-step verification. I went to accounts.google.com and disabled 2-step verification, deleted my account on my phone, rebooted, then added my account again and it worked as it was supposed to.
Lakewell said:
This same thing happened to me just last night on my Galaxy Nexus after attempting to go back to 4.2.2. The problem turned out to be something to do with 2-step verification. I went to accounts.google.com and disabled 2-step verification, deleted my account on my phone, rebooted, then added my account again and it worked as it was supposed to.
Click to expand...
Click to collapse
Wow, I owe you one. I would never have thought to try that... But that was indeed my problem. Thanks!
Edit: So after setting up my account on my phone, I then re-enabled 2-factor verification and the error comes back. Did you ever manage to re-enable 2-factor for you account and have it work on your non-KitKat phone?
radeon_x said:
Wow, I owe you one. I would never have thought to try that... But that was indeed my problem. Thanks!
Edit: So after setting up my account on my phone, I then re-enabled 2-factor verification and the error comes back. Did you ever manage to re-enable 2-factor for you account and have it work on your non-KitKat phone?
Click to expand...
Click to collapse
I did re-enable it and it works, although I did change it from text message to google authenticator.
Hello,
I had to reflash CM 10.2.1-d2att after a failed OTA 4.4 update but I haven't been able to properly sync my Google account with 2-step auth enabled. Wiping and re-flashing new ROMs hasn't fixed anything so my temporary fix has been to disable the 2-step auth. I have tried switching code methods (from app to text message and back) but that hasn't worked. Syncing with password only then enabling 2-step also fails.
Any other suggestions?
Have a stock S3, Sprint-branded, running 4.4.2. As of yesterday, I can't get mobile data (apps say no internet connection). It works fine on WiFi.
I noticed on startup, towards the end of the process, a "could not obtain root" message briefly flashes.
Only recent change was I tried an app called "Automate". I have since uninstalled it, but the problem still exists.
Any suggestions? Help would be appreciated.
retiredguy1945 said:
Have a stock S3, Sprint-branded, running 4.4.2. As of yesterday, I can't get mobile data (apps say no internet connection). It works fine on WiFi.
I noticed on startup, towards the end of the process, a "could not obtain root" message briefly flashes.
Only recent change was I tried an app called "Automate". I have since uninstalled it, but the problem still exists.
Any suggestions? Help would be appreciated.
Click to expand...
Click to collapse
Sounds like it was rooted at some point, and an app requiring root access is still installed. Install SuperSU from playstore and see which app it is
When I got my Note 4, I have been unable to download my paid email app (Enhanced Email) from Google Play.
It tries, but gets a 505 error part way through. Research shows that this apparently happens with the update to Lollipop on some phones. My old phone is able to use the email program and update from the play store just fine after Lollipop - it is apparently just the initial download that gets stuck.
The developer says I need to remove the stock email app first, then try again. If that doesn't work the next plan is to somehow install it with ADB/ABD(?). Others have made this work, so I am willing to try it. I can see this is going to be a process, but I need help with the first step - removing the original email app. Without rooting the phone, how do I do that?