-
-
Save jbinto/8876658 to your computer and use it in GitHub Desktop.
| ### 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:[email protected]|XXXXXXXXXXXXXXXXXXXXXXXX|0|0|0|| | |
| 2|Google:[email protected]|XXXXXXXXXXXXXXXXXXXXXXXX|0|0|0|Google|Google:[email protected] | |
| 3|Dropbox:[email protected]|XXXXXXXXXXXXXXXXXXXXXXXX|0|0|0|Dropbox|Dropbox:[email protected] | |
| ### 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. |
Unfortunately, this no longer works as of 12.07.2022. The secret in database seems to be encrypted somehow, and authenticator doesn't want to accept it (says + and / are invalid characters). Secrets are between 61 and 83 characters long in my case. I created my own secret to find out how it's encrypted, but I didn't succeed.
Example: Secret TEST1234TEST1234TEST1234TEST1234
gets encrypted to:
JoSYvgknFqwiMMQqEKbeZtPQ8gBppUdTbArhnsN3+fCAua0UqfqYHVHYchNWwyvSDY/BoHmUQsgRgf6W.
Lucky patcher or manual copying and pasting database file does not work - authenticator simply does not show the codes.
Also, QR codes generators don't work, as they try to create a QR code with this weirdly encrypted secret.
Just here to confirm the same issue as blazej222, manual backup of Google Auth database did not allow me to restore any keys.
ugh, I also just got hosed by this issue where the account.secret column is encrypted. The fact that Google Auth has no easy transfer (the QR Code way does not work if you are trying to flash your phone with the latest Android OS... and they don't even allow you to screenshot it!).
I've lost access to probably 20-30 services now. Thankfully had an export of my bitwarden vault.
If anyone finds the private key location (and hopefully its in one of the files that I backed up of the Authenticator's app data), maybe there is hope.
A solution with the encrypted accounts.secret column, there is in https://github.com/scito/extract_otp_secret_keys
Link is dead
copy and paste the link instead, but he didn't specify how he did the simulated restore but then again I don't really understand sqlite3 that well.
copy and paste the link instead, but he didn't specify how he did the simulated restore but then again I don't really understand sqlite3 that well.
he did mention the procedure at scito/extract_otp_secrets#24 , but the solution is misleading.
his solution is based on database of google authenticator version prior 5.10 which doesn't encrypt the secrets.
so the problem of encrypted secrets still persists.
I searched Google and accidentally found this website that can decode secrets from the newer Apps. I tested myself and it did work.
I searched Google and accidentally found this website that can decode secrets from the newer Apps. I tested myself and it did work.
It requires the QR codes, so it doesn't decrypt them "just by the database file".
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!
Really thanks. You just save my life. Still works.