Technician helping troubleshoot Fire TV automation and Alexa routine issues for seniors

Steve H.

Reviewed for technical accuracy

Specialities: “identity verified but still locked out” triage, account access not restored after verification, review/cooldown status checks, session/cookie.

If your identity was verified but you still can’t get in, check review status, cooldown delays, and device/browser sessions before trying again

Technician avatar Technician
Hi! If you’re seeing “Identity verified” but your access is not restored, that can feel maddening — especially when you did the hard part already.

Quick trust note: I don’t want you to keep clicking “verify again” or resetting everything. That can cause extra cooldowns or new security checks. We’ll start with the safest checks first.

Tell me what you see on screen right now:
• “You’re verified” but still “account locked / disabled / suspended”
• “Review pending” / “We’re checking your information”
• It loops back to login, or says “try again later”

And which service is it (email, banking, social media, Microsoft/Google/Apple, etc.)?
Customer
It says my identity is verified, but I still can’t access my account. It keeps saying I’m locked out or under review. I’m older and I’m worried I’ll lose everything. I tried logging in a lot because it didn’t make sense.
Technician avatar Technician
I hear you. Two things can be true at the same time:
1) Your identity verification succeeded, and
2) The account access is still restricted due to a separate security review, cooldown, or policy/lock status that hasn’t cleared yet.

A few gentle questions (not in any special order):
• Did the message mention a waiting period, like “try again later,” “review pending,” or “it may take time”?
• Are you trying on a computer browser, a phone app, or both?
• Did this start after a password change, new phone, travel, or an update?
Customer
It started suddenly after I got a new phone. I verified with my ID and it said success. But then I’m still blocked. On my laptop it says “try again later,” and on my phone it loops back to sign in.
Technician avatar Technician
That “new phone” detail is a common trigger. Many services treat a new device as higher risk until it becomes “trusted.”

Also, “try again later” usually means the system has you in a cooldown window. Repeated login attempts can extend that window, so we want fewer attempts, not more.

Safe check #1: are you signing in through a saved bookmark or an email link that might be old? Sometimes people land on an old sign-in page and get stuck in a loop.

Safe check #2: do you see any option like “Continue,” “Back to account,” or “Return to sign-in” after the verification success message — or does it just redirect?
Customer
It redirects. I verified, it said approved, then it brought me back to sign-in and I’m blocked again. I’m using Chrome on the laptop and the app on my phone.
Technician avatar Technician
That “verified → redirect → still blocked” pattern usually points to one of these buckets:
• Status delay: verification succeeded, but account restoration is still processing (review queue, sync delay).
• Session problem: the browser/app can’t keep the “verified” session (cookies blocked, corrupted session, private DNS/ad blocker).
• Separate restriction: identity is verified, but the account is still limited for another reason (lock, policy, unusual activity, too many attempts).

Trust moment: I don’t want you to “wipe everything” on your devices. First we’ll do a safe, controlled test that doesn’t change the account.

Are you using any ad blocker, strict tracking protection, or “privacy” add-ons in Chrome?
Customer
Yes, I use an ad blocker and my grandson set up some privacy stuff. I don’t want to break anything. Also, I tried so many times yesterday that I’m afraid I made it worse.
Technician avatar Technician
You didn’t “ruin” it — but extra attempts can create a cooldown, which feels like the system is ignoring you.

Here’s a safe approach that keeps your normal setup intact:
Low-risk diagnostic: try one sign-in attempt in a clean Chrome profile (or an Incognito window) with extensions not running the same way. This tests whether cookies/extensions are blocking the “access restored” handoff.

Another very safe check: confirm your device date/time is correct. A wrong clock can break secure logins and cause “verified but not restored” loops.

When it says “try again later,” does it show a time, or just that message?
Customer
It doesn’t give a time. Just “try again later.” And yes, the time might be off because my laptop sometimes changes time zones.
Technician avatar Technician
That’s a real cause, and it’s easy to overlook. If the system time is wrong, security tokens can fail and you can get redirected back to login even after a “success” message.

Next, a question seniors often ask (and it’s smart): do you have access to the same email/phone used for sign-in and codes? If recovery options changed with the new phone, some services keep the account limited until the change “ages” a bit.

Also — are you seeing the problem on both the phone app and the laptop browser, or does one behave better than the other?
Customer
The phone app sometimes lets me in, but then it says my account has restrictions. The laptop is worse. I still have the same email, but my phone number changed when I got the new phone.
Technician avatar Technician
That combination explains the “identity verified but access not restored” situation really well:
• Phone number change can trigger extra review time.
• App vs browser differences often point to browser cookies/extensions or device trust issues.
• “Restrictions” can mean the account is partially restored but still limited until checks finish.

Trust moment: I don’t want you to remove recovery options, change passwords repeatedly, or keep submitting forms. Those can create new flags.

Safe tests (choose only one or two):
1) One clean browser attempt (Incognito or new profile).
2) One device trust test: use the device that “almost works” (your phone) on the same Wi-Fi and see if the restriction message changes.
3) Pause attempts after any “try again later” message and write down the exact wording.
Customer
How do I know if it’s just waiting time, or if something is actually wrong? I don’t want to wait forever.
Technician avatar Technician
Great question — you want evidence, not guesswork.

It’s often a waiting/review situation when:
• The message uses words like “review,” “processing,” “we’re checking,” or “try again later.”
• The app can partially sign in, but features are restricted.

It’s more likely a session/device issue when:
• One device works and the other always loops back to sign-in.
• A clean browser session behaves differently than your normal browser.

Your safest next step is to do one controlled test, then stop. If you want, tell me the exact words of the restriction message — even a short quote helps.
Customer
It says “Your identity is verified” but “access will be restored after review” and then it still blocks me. Okay, I’ll stop trying repeatedly and do the clean browser test once.
Technician avatar Technician
That wording strongly suggests a review/processing delay — not that your verification “didn’t count.”

One last safety note: if anyone contacts you asking for a verification code, password, or “support PIN,” don’t share it. Real recovery stays inside the provider’s sign-in and help pages.

After your one test, keep these notes (they’re helpful if you must escalate): device, browser/app, exact message, and whether it changes on phone vs laptop. That’s the fastest way to get the right kind of help.
Customer
Thank you. This is the first time it’s made sense. I’ll do one test and then wait instead of panicking.

Quick answer: the accepted fix

Accepted safe steps when identity is verified but access is not restored:
• Stop repeated sign-in attempts if you see “try again later” or “review pending” (cooldowns can extend delays).
• Confirm your device date/time is correct and set automatically (wrong time can cause login loops).
• Try one controlled sign-in in a clean browser session (Incognito/new profile) to rule out cookies/extensions blocking the “restored access” handoff.
• Compare phone app vs computer browser once; if one works better, it points to device trust/session issues rather than failed verification.
• Write down the exact message and where it stops (locked, restricted, review pending) before escalating to the provider.


Why access may not return right after identity verification

Many services separate identity verification from account restoration. You can be verified and still be limited while the system finishes a review, clears a cooldown, or updates device trust after changes like a new phone number or new device. Sometimes the “verified” result doesn’t carry over if the browser can’t keep the secure session (cookies blocked, strict tracking protection, corrupted session). The goal is to identify whether you’re facing a normal processing delay or a device/browser session problem — without triggering more security checks.

What to check first (safe checks that don’t make things worse)

Start with low-risk steps: pause after “try again later,” confirm correct time/date, and use a clean browser session to rule out stuck cookies and extensions. Avoid changing passwords repeatedly or removing recovery options while access is restricted. Compare one attempt on phone vs one attempt on computer to see if the restriction is device-specific. If messages mention “review pending” or “processing,” it’s often best to wait and keep notes rather than keep retrying.

Security tip: don’t share codes or “support PINs” while you’re locked out

Lockout messages can attract scams.

If anyone asks you for a one-time code, password, recovery link, or a “support PIN,” treat it as suspicious. Legitimate recovery stays inside the provider’s sign-in and help pages. Stick to safe checks (cooldown awareness, time/date, clean session, device comparison) and record the exact wording you see.

Disclaimer: This information is AI-generated and intended for general guidance only. Steps vary by device, region, and service. For exact instructions for your setup, consult a verified expert or the manufacturer’s support site.

Understand what these prompts mean


Getting Started Is Easy

Low-risk diagnosis

Figure out whether this is a review delay, a cooldown, or a device/browser session issue after identity verification.

Reduce lockout loops

Learn why repeated attempts can extend “try again later,” and how to test safely without escalating restrictions.

Escalation-ready notes

Collect exact messages, timestamps, and device differences so the provider can see what’s happening faster.

FAQ

Why did this start suddenly (I was verified, then still locked out)?

This often happens after a new phone, phone number change, travel, or a security update. Some systems verify identity first, then place the account in a short review or cooldown before full access returns. Repeated login attempts can extend “try again later.” A single controlled test is safer than many retries.

Can this happen after an app or browser update?

Yes. Updates can change cookie rules, tracking protection, or sign-in sessions, which can cause “verified” to not carry over. A clean browser session can show whether your normal browser profile is the problem. If the app works but the browser fails, it often points to cookies/extensions. If both fail, it’s more likely a status/review delay.

Is this a hardware problem, or is it settings/account status?

Usually it’s settings or account status, not hardware. The most common causes are cooldowns, review pending, or a session problem (cookies blocked, time/date incorrect). Hardware only matters if you can’t receive codes or can’t use required verification methods. Comparing phone app vs computer browser helps narrow it down quickly.

Can this be fixed without using a service?

Often, yes. Many cases resolve after waiting out a cooldown and doing safe checks like time/date and a clean session. Avoid repeated password resets or changing recovery options while access is restricted. If it remains stuck, your notes (exact message + device/app used) help the provider process it faster. Stay cautious with scams asking for codes or PINs.

Sources

Filed under: Account Access Help

Matt Verified Icon
Matt ● replies in < 1 min
Technician Expert
⭐⭐⭐⭐⭐ Trusted by 27,000+ customers
Avatar
Alex · Expert's Assistant