Everyday (well, almost) a new ROM comes out that I can’t resist trying. Flashing ROMs for those of us in the know (and I hope this blog has gone a long way in helping you know how to easily go about that) is something that is fun and exciting. Yesterday I tested something to boost the Wi-Fi speeds on my Galaxy S4 (not Crossbreed for those who know what Crossbreed is. Just something else, details much much later) and it broke the Wi-Fi scanning ability of my device. So I switched the firmware on the device promptly. This time round, I ended with a new ROM. However something was amiss. All I was getting as I tried to update my core apps on the Play Store was the RPC:S-5:AEC-0 error, see screenshot below. The error has been encountered by a number of Android users accessing the Play Store either to install updates for their apps or download new ones so it has nothing to do with my ROM flashing mannerisms.
How do you overcome this? It’s pretty easy. I have seen suggestions online about clearing the cache and all data on your Google Play services framework and the like but doing that alone, won’t be of much help. You need to go an extra step. Deleting data and cache in the Google Play Service Framework should be so that you don’t get restrictions from your device when wiping the main Google account through which the device is tied to the Google services franchise.
Google admits knowledge of the error and is yet to issue a fix and recommends just what this article is about. While the problem was widely prevalent and still is (just like the Play Store error 921 has been) with users on older versions of Android when a newer Play Store version is released, it seems it is not just restricted to those. I encountered the error with the latest update of the Play Store so it is still a problem even with newer versions of Play Store. While we wait for Google to fix the RPC:S-5:AEC-0 error, here’s what you do:
Go to your Settings app and check your Google account. You should find an option to Remove Account. Select it and wait for your Google account to be wiped off your device. You won’t lose anything. All your Google-synced stuff like the reminders and notes on Keep, contacts and applications stay intact (albeit temporarily). Upon clearing your Google account, I recommend that you also go to the Play Store app, still in Settings > Applications/Application Manage and delete the app data. I also wiped data from the Google Play services app but I don’t think it is that necessary. Either way, you can do it too. It won’t mess things up, it will just make sure you start on a clean front once you restore your main Google account. After doing this go to Settings > Accounts again and add a new or existing Google account (different from what you just wiped. It is just or testing purposes) and log in with your credentials. Restart the device, connect to your Wi-Fi/3G/LTE network and go to the Play Store. Try updating your apps and even installing new ones to see that you no longer get the RPC:S-5:AEC-0 error. If all is positive, go to Settings > Accounts and remove the account you just added. After it is removed, add your main Google account (the one you had previously deleted), login and restart the device again. Go to the Play Store again and see if you can update and install apps without encountering any errors.
Let me know if this works. There isn’t much information online about how to go about fixing this in other more convncing ways that guarantee that it won’t reoccur and Google is yet to fix it but whatever I just shared at least worked for me. Don’t go about clearing cache and Dalvik cache in your device’s recovery, that won’t help much (been there, done that). Some lucky phandroids are reporting that the RPC:S-5:AEC-0 resolved itself after several days so if patience is your cup of tea and you are not that interested in finding out what latest changes Twitter has introduced to its Android app then patience, not removing your Google account, is your best bet.
This error’s handling mechanism is similar to that of the infamous error 921 and error 428. If you are a long time Android user you have probably encountered these too.
Note: I use the Galaxy S4 as my daily driver so some of the sequenced steps here may not be the same as in your device. Whichever way find everything in your Settings app, the Application Manager in the Settings app and the Accounts/Sync or similar apps, all found in Settings.