Created
February 8, 2014 04:20
-
-
Save jbinto/8876658 to your computer and use it in GitHub Desktop.
Recovering Google Authenticator keys from Android device for backup
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ### Last tested February 7 2014 on a Galaxy S3 (d2att) running Cyanogenmod 11 nightly, with Google Authenticator 2.49. | |
| ### Device with Google Authenticator must have root. | |
| ### Computer requires Android Developer Tools and SQLite 3. | |
| ### Connect your device in USB debugging mode. | |
| $ cd /tmp | |
| $ adb root | |
| $ adb pull /data/data/com.google.android.apps.authenticator2/databases/databases | |
| $ sqlite3 ./databases "select * from accounts" > /Volumes/TRUECRYPT_ENCRYPTED_VOLUME/google_authenticator_backup.txt | |
| $ rm ./databases | |
| ### If you look at the file, you see a pipe-delimited file with entries looking like the following. | |
| ### The X's mark the key. | |
| 1|Google:me@gmail.com|XXXXXXXXXXXXXXXXXXXXXXXX|0|0|0|| | |
| 2|Google:me@domain.org|XXXXXXXXXXXXXXXXXXXXXXXX|0|0|0|Google|Google:me@domain.org | |
| 3|Dropbox:me@gmail.com|XXXXXXXXXXXXXXXXXXXXXXXX|0|0|0|Dropbox|Dropbox:me@gmail.com | |
| ### To restore the keys, you can key them in manually in Google Authenticator: | |
| ### Menu -> Set up account -> Enter provided key. | |
| ### Enter the key exactly as it appears, case sensitive, and choose Time-based. |
You can try disabling selinux. Tried the earlier suggestions, but Authenticator kept crashing. Restoring through Titanium backup that way, while upgrading from Android 10 to Android 13, I managed to recover my passwords.
Link is dead
the link isn't dead.
actually, it works!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It requires the QR codes, so it doesn't decrypt them "just by the database file".