Right backup authenticity how to#
Right backup authenticity install#
Right backup authenticity android#

OR, you can use a free Open source SQLite GUI editor like 'SQLite Database Browser Portable' to open the 'databases' file inside the '.authenticator2' folder. Now, whenever you need to reinstall your firmware/ buy a new phone just follow the steps above and copy that folder to the exact same directory once you've installed the Google Authenticator app.

Right backup authenticity android#

Once you open the file explorer in System root > Click 'data' folder > Click 'data' folder (inside the other data folder) > Copy the folder named .authenticator2 > Exit System root folder > Open normal Main storage / SD storage space and Paste the Folder here.Ĭonnect your android device to a PC and Backup the folder to a secure USB / external HDD. This app makes it possible for us to access the Android system as a root user. I use the popular and free FX file explorer with its free FX root access addon.

Right backup authenticity install#

This method is more useful for the not-so tech savvy people or the people like me > who don't want to waste time installing Android SDK + JDK from scratch just to run the adb command.ĭownload and install any 'Root explorer' app from Google Play store. The following method will only work on rooted Android devices. * Disclosure: I work for the website linked above.

Right backup authenticity how to#

Have a look at this article on the blog of Protectimus (the company where I work) to get more information how to backup Google Authenticator: How to Backup Google Authenticator or Transfer It to a New Phone. They can be in the form of key fob or credit card. Then if you lose your phone you could restore tokens in Google Authenticator on your new device.Īlso, you can use hardware tokens. The best solution is to save the QR codes (or the secret keys) in the moment of token enrollment and keep them in some safe place. For these services, you should save backup codes. Only small amount of services offer backup codes (particularly Google). Two-factor authentication provides an additional layer of protection and by rooting you bring it to naught since different viruses could get an access to protected memory areas. But it isn't recommended to root your device if you don’t want to make it vulnerable. There are a lot of advice for rooted phones. Now I'm covered in the case of phone loss and can configure other devices if need be. I'm satisfied with this result as I didn't have to do anything more than reconfigure MFA (I had to do this anyway in my circumstances) and simply add all the tokens to lastpass. Thus, so long as you securely control the tokens, you can configure MFA on any device. I verified that you can setup clones of the authenticator using the same key on independent devices running simultaneously. Rather than going through the trouble of taking screen shots of the QR codes, labeling them appropriately and then GPG encrypting them and securely storing them somewhere I just store the tokens in an encrypted vault and setup my MFA manually. Every service I've used so far allows you to opt for the token-based setup rather than QR. The simplest solution I came up with is to ignore the QR code based setup and just use the token based setup itself (it's the 'manual' option in most authenticator apps). I realized that if I lost my phone or did the factory data reset I'd have been totally borked. I just went through this process after my Nexus 6P stopped connecting to data and I had to setup all my MFA again on a Pixel. As a preface this is an approach for configuring MFA ahead of time so that it is always backed up, not recovering or backing up existing codes.