777JILI Authenticator App Setup and Moving Codes to a New Phone

An authenticator app shows a short-lived code that proves a sign-in is yours, even when a password has leaked. This 777JILI page sets one up step by step and explains what happens to the codes when you change phones. It is one of the phone browser settings for game pages that stays useful long after the session ends.

How an authenticator app makes a code

The code comes from a shared secret and the clock, with no network involved. RFC 6238 defines the time-based method and gives the time step a default of 30 seconds. That is why Google’s page says Google Authenticator keeps producing codes without an internet connection or mobile service.

Google’s page adds one detail about the clock: the time correction setting is gone from version 7.0, and the app now uses the time setting on your operating system. If codes fail, Google’s page asks you to confirm the time on your device is synced and correct for your local time zone.

Set up Google Authenticator for your Google Account

Google’s page covers both phone families. The steps below follow it.

1. Go to the 2-Step Verification settings for your Google Account, and sign in if asked.
2. Tap “Set up authenticator”. On some Android devices, tap “Get Started”.
3. Follow the on-screen steps.
4. Wait if the option is missing: Google says it may take up to 7 days for Google Authenticator to appear as a sign-in option.

Google’s page says Android needs version 6.0 or above, and iPhone needs the latest operating system. Never read a code to anyone: Google’s 2-Step Verification page warns that scammers may try to take over your account with shared codes.

Google Authenticator sync and use without an account

Google says you can “synchronize your verification codes across all your devices, simply by signing in to your Google Account”. The page lists “Version 6.0 or above on Android” and “Version 4.0 or above on iOS” as the requirement.

You can also skip the account. Tap “Use without an account” when you first open the app. Google warns that this removes codes from all your Google Accounts, stores them on the device, and makes them unavailable on your other devices.

Move your codes to a new phone

If you sync with your Google Account, sign in to Google Authenticator on the new phone and the codes arrive. If you use the app without an account, transfer them by QR code. Google’s iPhone page words the menu as below.

1. Get Google Authenticator onto the new phone and tap “Get Started”.
2. On the old phone, tap “Menu”, then “Transfer accounts”, then “Export accounts”.
3. Confirm with your device lock when asked, select the accounts, and tap “Next”.
4. On the new phone, tap “Menu”, “Transfer accounts”, then “Import accounts”.
5. Scan the QR code from the old phone and wait for the confirmation.

Google’s Android page prints “Transfer codes”, “Export codes” and “Import codes” for the same menu, so follow the labels on your own screen.

When a code stops working

Keep codes private during a session

A code is useful for seconds, so interruptions are how people get rushed into typing one. Three small habits help.

1. Turn on Do Not Disturb for a planned session before you play.
2. On an iPhone, turn on Privacy Screen: Google’s page gives Menu, Settings, Privacy Screen, and says it asks for biometric verification such as Face ID or Touch ID before the app opens.
3. Sync the codes to your Google Account, which Google lists among its best practices. You must be 21+ to play.