Possible resolutions to the [DF-RPC-01] ( Remote Procedure Call Failure error)
Well certainly I too believe it has nothing to do your device, even a lot of people have complained about the issue:
Based on the following evidence;
Google Play Help Forum
It is usually occurring when there is no payment method linked to your account (as suggested on Google Play Help forum). Users have noted it appears to be a back end issue with Google.
You may wish to check your current payment options including any updated information such as address, payment choices (especially credit cards because of late Google has beefed up its security on use of credit cards for making app purchases).
- One user did resolve the problem by reactivating the Credit card which had been blocked due to the suspected tampering. The incident is described here:
How to resolve "Error retrieving information from server DF - RPC - 01" on the android phone? .
You may need to contact Google support to present your query.
- From the above discussions this error is said to be different from other errors which are normally fixed by clearing data, clearing cache or updating google play services, based on evidence above.
Strangely some users claim the problem was caused by having several google accounts on the device some of which weren't linked to Google Play and removing these extra accounts resolved the problem (however I don't think it’s too convenient but if that’s the only way out then it’s worth a try).
- Opening up settings
- Navigating to accounts settings
- Selecting "google accounts"
- Delete all unnecessary accounts
- Re syncing all accounts and making sure none of them fail to sync properly because the device doesn't notify of any failures.
For some reasons, it can happen that checkin expires. Here are some independant tricks you can use to force new device checkins: Google Checkin is the service responsible for “checking in” to google servers (also readies important updates and syncing of data(dropbox etc))
Compose ##2432546## (which stands for ##CHECKIN##)
If you don't want to dial or can't because there is no dialer on your device, use an ADB shell as root and type this:
# am broadcast -a android.provider.Telephony.SECRET_CODE -d android_secret_code://2432546
Somehow this fix helped me fix one of the infamous errors: "Error retrieving information from server. [RH-01]" Which is the reason I am attributing the issue to be related to syncing issues with Google servers.
- Check if debit/credit card(s) have expired. When these cards have expired you can longer be able to make new purchases and this error appears so you need to renew/reactivate these. After which you need to enter new details.
When entering new card details make sure you clear cache of play store and google play services:
Settings >> Applications >> Google play store :Force close >> Clear cache/data
Settings >> Applications >> Google play services : Force close >> Clear cache.
Reboot device, then when re-opening Google Playstore you made need to reenter details (account with payment info). Afer successful sign-in you should see your billing info.
Error retrieving information from server [DF-RPC-01] While making IAP
If you are using google wallet check if you not accidentally disabled
the payment services. You can add debit cards or link bank accounts to your Google Wallet. Fore details see here: Add, update, or delete a debit card
Make sure your google account address is the same as the address you had your my google wallet payments
Possible syncing issues between google play store and other google apps
Other workarounds : Using VPN connection
Through some seroius experiments, one user claims that after changing the connection and using VPN tunnel solved the issues with this error.
Getting error [DF-RPC-01], cannot purchase apps or in-app purchases
Remarks: I myself have not yet encountered this error, but other minor errors which were resolved by basic troubleshooting (i.e. clearing cache, data, and updating google apps),
however have taken time to research on possible fixes and from my understanding this kind of error is likely to be related to Google itself, based on the evidence that it still appears on web interface apart from device. Hope that helps.
(Some Included in body text)