Google's account-recovery flow asks people who cannot sign in to answer questions and prove ownership through information already linked to the account. The strongest first attempt uses a familiar device, browser and location rather than a newly reset phone or an unfamiliar network.
A lost phone does not automatically end every recovery route. Depending on what was set up earlier, another signed-in phone, a backup code, a hardware security key, a passkey or a trusted device may still work. APPI News has a separate guide to passkeys and SMS verification; this article focuses on recovering a Google Account when the usual phone is unavailable.
How to retry account recovery
Google recommends using a computer, phone or tablet where you frequently sign in, the browser you usually use and a familiar location such as home or work. It also says to answer as many questions as possible, make the best guess when an answer is uncertain and enter the most recent password you remember.
Google says wrong guesses do not remove a person from the recovery process and that there is no limit to the number of recovery attempts. That does not mean every attempt will produce the same questions. The account-recovery page may ask for a reachable email address, and Google says a recovery, alternate or contact email already attached to the account can be used.
Use Google's account-recovery page directly. If Google sends an expected message that does not appear, check the spam or junk folder for an email titled “Your Google support inquiry.” Google says passwords and verification codes should be entered only at accounts.google.com, not given to a caller, message sender or paid recovery service.
Options after losing the primary phone
Google lists another phone already signed in to the account, another number added for two-step verification, a saved backup code, a hardware security key and a passkey created on another device. A previously trusted computer may also allow sign-in without a second verification step if the account holder selected the option not to be asked again on that computer.
If the number itself is still yours, Google says to ask the mobile carrier to transfer it to a new phone or SIM card. The carrier's identity checks, replacement fee and timing are not set by Google. If the phone was stolen, sign out of it and change the Google Account password after regaining access.
Google says each backup code is eight digits and can be used once; a new set contains 10 codes and makes the old set inactive. A downloaded file may be named `Backup-codes-username.txt`, but that file helps only if it was saved on a computer the account holder can still access.

Google says an account protected by two-step verification may take 3 to 5 business days to verify when no additional second step is available or the password is forgotten. That estimate applies to the situation described on Google's page; it is not a published deadline for every recovery failure.

Why verification codes may not arrive
Open the sign-in screen and choose “Try another way” when it is offered. The available choices depend on the account's earlier settings. A new code request does not create a new recovery method, and a code sent to a number controlled by someone else should be treated as a possible account or SIM compromise.
Do not read a code to an unsolicited caller or enter it into a page reached from a message. Google says it never asks for passwords or verification codes by email, phone call or message, and its recovery page says Google does not work with services that claim to provide account or password support.
Why a new recovery phone may still be delayed
Google says a newly added or changed recovery phone may take up to seven days to take effect. During that period, Google may send codes to previous recovery information. The same page says recovery information cannot be added while the account is locked or already in the recovery process.
Recovery contacts have their own waiting rule. Google says an accepted recovery contact must be in place for seven days before it can be used for account recovery. A recovery contact does not receive the account's security alerts or notifications.
How this plays out outside Taiwan
The first local question is whether the problem is a lost handset or a stolen phone number. A lost handset leaves the mobile account under the subscriber's control; a SIM-swap or unauthorized port can move calls and text messages to somebody else. That distinction matters because Google may still offer SMS as one of several routes, while the carrier must control the number before an SMS route can be trusted again.
In the United States, the US Federal Trade Commission describes a SIM-swap warning pattern as a sudden loss of calls, texts and data or an unexpected notice that a SIM was activated on another device. Its consumer guidance says to contact the mobile provider immediately to regain the number, then change account passwords and inspect bank and credit accounts for unauthorized activity. A US reader trying to recover a Google Account should therefore call the carrier through a number from the carrier's known website or bill, ask whether a replacement SIM or port was issued, and request the carrier's account-protection options. The FTC says a cellular-account PIN or password may help protect against unauthorized changes, but it does not promise that every provider offers the same control.
The US route is not a Google support escalation. The FTC can take a report about fraud, but it cannot restore a Google Account or decide whether a carrier should release a number. The immediate sequence is carrier, Google recovery page, then banks or other services that used the number for sign-in. A passkey, authenticator app or hardware key that was registered before the incident can reduce reliance on the number; our passkey guide explains why a passkey is not copied when a number moves to another SIM.
In the United Kingdom, the UK National Cyber Security Centre describes SIM swapping as a transfer of a phone number to a new SIM that lets an attacker receive calls and text messages. The NCSC notes that a SIM swap can also happen during an ordinary handset change, so the event alone does not prove fraud. A UK reader should ask the mobile provider to confirm whether a recent SIM change or number transfer occurred, use the provider's account-security route, and then retry Google recovery from a familiar device. The NCSC also notes that not every network supplies the same SIM-swap data, so a help-desk agent may not be able to provide a timestamp or a definitive explanation.
Australia adds a more specific consumer rule. The Australian Competition and Consumer Commission says a provider must verify a customer's identity before transferring a phone service and advises people to contact the provider quickly after an unauthorized transfer. It calls SIM-swap fraud a form of mobile-porting fraud and directs affected consumers to contact their bank, seek support from IDCARE and report scams to Scamwatch. An Australian reader who has lost both the phone and Google access should use the provider's independently verified contact details, ask for the number to be restored, and treat any new bank or email alerts as a separate incident.
Singapore has a different warning to add. The Singapore Police Force says local SIM cards and eSIMs must not be handed over or registered for another person's criminal use. It describes offences involving subscribers, intermediaries and retailers who knowingly facilitate fraudulent registrations. For a Singapore reader, a phone-number problem should be reported to the mobile provider and, where a scam or fraudulent registration is suspected, to the Singapore Police Force or ScamShield. The rule is about misuse of local SIM cards; it does not create a Google recovery shortcut. The account holder still has to use the Google options that were previously attached to the account.
What to set up after access is restored
Start with a recovery phone and email that you can use, then add a recovery contact if the account offers it. Google says recovery options are not available for every region, account or device, so check the actual Security & sign-in page rather than assuming that another account has the same menu.
Create backup codes and store them away from the phone. Add a second sign-in route, such as a hardware security key or passkey, and test it while the account is still accessible. Keep the old route until the replacement route works, and review the account's devices after any recovery event. If recovery still fails, Google says a person can create a new Google Account; its published personal-account recovery guidance does not promise a phone agent or guaranteed manual review.
Common questions
Can I try Google recovery again after a failed attempt?
Yes. Google says wrong guesses do not end the process and that there is no limit to recovery attempts. The questions and available methods can still vary by account.
Will Google call me to recover the account?
No. Google says it does not provide phone help for signing in and does not work with account or password recovery services. Keep passwords and verification codes private.
Why is the old recovery number still receiving codes?
Google says recovery-information changes may take up to seven days to take effect, and previous recovery information may still be used during that period.
Sources and further reading
- How to recover your Google Account or Gmail(Google Account Help)
- Tips to complete account recovery steps(Google Account Help)
- Fix common issues with 2-Step Verification(Google Account Help)
- Sign in with backup codes(Google Account Help)
- Set up recovery options(Google Account Help)
- Avoid getting locked out of your Google Account(Google Account Help)
- SIM Swap Scams: How to Protect Yourself(US Federal Trade Commission)
- Protecting SMS messages used in critical business processes(UK National Cyber Security Centre)
- Misuse of SIM Card Offences(Singapore Police Force)
- Unauthorised transfer of phone or internet services(Australian Competition and Consumer Commission)