Transfer Google Authenticator to New Phone: A Step-by-Step Guide

Transferring Google Authenticator Credentials to a New Device

A significant portion of the data associated with applications on your Android device is typically synchronized online, facilitating automatic transfer to a new phone or tablet. However, Google Authenticator credentials are an exception to this process.

Synchronization is intentionally disabled for these credentials due to inherent security considerations.

Moving Your Authenticator Data

Whether you are performing a factory reset, acquiring a new smartphone, or simply wish to duplicate your credentials onto a secondary device, the following steps will assist in migrating your Authenticator data.

This process ensures you maintain access to your accounts and avoid losing vital access codes.

• The specific method for transferring codes varies depending on your Android version and the Google Authenticator app version.
• Always prioritize security during this process and avoid screenshots or storing codes in insecure locations.

Successfully completing these steps will allow you to seamlessly continue using two-factor authentication on your new device without interruption.

Transferring Google Account Access to a New Phone

Google has implemented a feature enabling users to transfer their account credentials to a new mobile device. This process is initiated through the 2-Step Verification settings page.

Locate and select the "Move to a different phone" option. You will then be prompted to either scan a provided QR code or manually input your credentials on the new device.

Following successful transfer, the authentication application previously used on your old phone will no longer function.

Compatibility with Other Services

It's important to note that not all services utilizing Google Authenticator support this direct transfer method.

For such services, alternative procedures may be necessary, including disabling and re-enabling the account or retrieving your verification codes.

The methods detailed below also provide a means of activating Google Authenticator on multiple devices, such as both a smartphone and a tablet.

While Google officially states that simultaneous use on multiple devices isn't supported, these methods can circumvent this limitation.

• Consider these alternative methods if direct transfer isn't available.
• Ensure you have a backup method for accessing your accounts during the transition.

Google Authenticator offers enhanced security, but requires careful management during device changes.

Deactivating and Reactivating Two-Step Verification

Prior to undertaking a factory reset, particularly if you wish to avoid utilizing stored security codes or SMS verification, consider temporarily disabling two-step authentication. This can be accomplished by selecting the "Remove" link located on the 2-step verification settings page.

This action will suspend two-factor authentication functionality.

Following the factory reset, you can then re-add an authentication application from the same settings page. When prompted, scan the provided QR code with your phone, or manually input the associated code.

If you intend to utilize Google Authenticator across multiple devices, ensure you enter the code into each device before closing the window.

Although recording the displayed code for safekeeping might seem practical, it’s generally not recommended. Access to this code would allow unauthorized individuals to generate your time-based authentication codes.

Protecting your authentication codes is crucial for maintaining account security.

Safeguarding Your Google Authenticator Data with Root Access

For Android users with root access, a comprehensive backup of your Google Authenticator application data is achievable through tools like Titanium Backup. We have previously detailed the functionalities of this application.

Due to security protocols, direct access to this data by other applications is typically restricted. Root privileges are therefore necessary to facilitate the backup process.

Backing Up and Restoring Your Data

Within the Backup/Restore tab of Titanium Backup, locate the Google Authenticator application. Initiate the backup procedure to securely store its data.

Subsequently, transfer the backup file from the TitaniumBackup directory on your device to a personal computer for safekeeping.

• This allows for easy transfer to a new device.
• Restoration can then be performed on the new device.

It’s important to understand that compatibility issues may arise when attempting to restore backups across different Android operating system versions.

However, this method proves particularly effective for restoring your Google Authenticator setup following a factory reset of your device.

Retrieving Credentials Manually with Root Access

For users possessing root privileges on their Android devices, a manual extraction of Google Authenticator credentials is possible. While more involved than utilizing Titanium Backup, this method provides direct access to the necessary data.

Successful execution requires root-level access for the adb tool. If a custom ROM is installed, root-enabled adb functionality may already be present. Otherwise, a tool such as adbd Insecure will be necessary.

This application, adbd Insecure, can be obtained from the Google Play Store or directly from the XDA Developers forums. Its purpose is to place the adbd daemon into an insecure mode, allowing access to system files.

Accessing the Databases File

With root access established, the Google Authenticator databases file can be located at /data/data/com.google.android.apps.authenticator2/databases/databases. A root file explorer can be used to copy this file to a computer for further analysis.

After enabling insecure mode for adb, connect your Android device to your computer. Then, employ the following adb command to retrieve the databases file:

adb pull /data/data/com.google.android.apps.authenticator2/databases/databases

Viewing Account Information

Once the file is transferred, an SQLite editor can be used to examine its contents. For those comfortable with the command line, the sqlite3 program offers a direct method for querying the database.

sqlite3 ./databases

select * from accounts;

Executing these commands will display the Google Authenticator keys, which can then be re-entered into another device.

Fortunately, Google has ceased the practice of resetting application-specific passwords. Consequently, even if Google Authenticator is disabled and re-enabled, existing passwords will remain functional.

Credit for the inspiration behind much of this information is due to Dan at cadince.