
Facebook Checkpoint Loop: Why It Keeps Asking to Verify
Stuck in a Facebook checkpoint loop in Malaysia? Why the security check keeps coming back, how to break it with Meta's own steps, and the scams to avoid.
Facebook keeps repeating the security check when it still does not trust the login. Stop retrying, wait a day if you requested several codes, then make one attempt on a device and network you have used before, with your sign-up date of birth. If the account was taken over, use facebook.com/hacked instead. Meta decides.
Summary- A checkpoint loop usually means Facebook still does not trust the login, often because of repeated attempts, a new device or network, or someone else holding a session.
- Stop retrying, then make one calm attempt on a phone or computer you have logged in from before, on your usual network, and give the date of birth you used at sign-up.
- If you have requested several codes, wait a day before asking again, and if a check has just finished, Facebook may make you wait 24 hours to log in.
- If your password, email or phone were changed, leave the checkpoint and use facebook.com/hacked or Meta's Account Recovery hub instead.
- Nobody can unlock a checkpoint from outside, so ignore anyone selling a checkpoint unlock or asking for your password, login codes, backup codes or remote access.
- Meta makes the final decision, and some accounts stay locked even after every official step has been tried.
Table of contents11 sections
- 01Why Does Facebook Keep Asking You to Confirm Your Identity?
- 02Which Loop Are You In?
- 03Why the Security Check Keeps Coming Back
- 04How to Break the Loop: A Calm 24-Hour Reset
- 05When the Loop Is a Two-Factor Code Screen
- 06When the Loop Means Someone Else Is Still In
- 07"Buka Checkpoint" Sellers and Other Scams
- 08Mistakes That Restart the Loop
- 09If Nothing Breaks the Loop
- 10When a Case Review Makes Sense
- 11Frequently Asked Questions
You finish Facebook's security check, tap continue, and land on the same screen again: "Your account has been locked", then "Get started", then confirm your identity. You do it a second time, then a third. In Malaysia people call this kena checkpoint, and after an hour of it the account feels gone.
It usually is not gone. A repeating check normally means Facebook still does not trust the login, and every quick retry from a new phone, a new network or a fresh code request can make that worse. The way out is to stop, reset the conditions, and try once in the way Meta's pages describe.
This guide is about the loop itself. It covers why the check repeats, a calm reset plan, what to do when the loop is a code screen, how to tell whether someone else is still in the account, and the "buka checkpoint" sellers who target people stuck here. If this is your first lock, start with our guide to a Facebook account locked for unusual activity.
Last checked: 5 October 2026.
#Why Does Facebook Keep Asking You to Confirm Your Identity?
Because it still thinks the account may not be safe. Meta's page on security checks says it asks for one when it thinks your account's security might have been affected, and its unlock page says it may lock an account when it sees unusual activity. Meta does not publish a list of triggers, but its pages keep pointing to the same fixes: use a device you have logged in from before, give the date of birth you used at sign-up, and wait a day if you have requested several codes. When the email, phone or password were changed by someone else, the checkpoint is the wrong door, and Meta sends you to facebook.com/hacked instead. Only Meta can lift the lock.
#Which Loop Are You In?
"Checkpoint loop" covers several different screens. The exact wording varies by app version, language and region, so match the meaning rather than the words. Meta does not publish a page about loops as such, so the reasons and fixes in this table are our reading of its help pages at the time of writing, not Meta's own explanation.
| What keeps happening | Likely reason | What usually breaks it |
|---|---|---|
| "Get started" returns you to the lock screen after every attempt | The check is not being accepted, or each attempt comes from a device or network Facebook does not know | Stop for a day, then one attempt on a familiar device and your usual network |
| You finished the check and now cannot log in at all | Facebook's 24-hour wait after a security check | Wait the full day without starting anything new |
| Codes never arrive, so you request more and the check restarts | Codes are delayed or going to an old number or inbox | Wait a day before requesting again, then check the right inbox, spam and blocked texts |
| The date of birth or security question is rejected | You entered the birthday now on the profile, not the one given at sign-up | Use the sign-up date of birth, or pick a different question if offered |
| Every login asks for a two-factor code, even on your own phone | Private browsing or history clearing stops Facebook remembering the browser | Use a normal browser window you keep, or the app, and save the browser |
| The lock comes back days after you cleared it | Someone else may still have a session, or the password is still known | Treat it as a takeover: facebook.com/hacked, then log out unknown sessions |
#Why the Security Check Keeps Coming Back
Facebook decides whether a login looks like you. Meta does not explain its signals, so the points below are practical reasoning from its own advice rather than a published rule list.
- Repeated attempts. Ten tries in an hour do not look like a calm owner. Meta's unlock page says that if you have requested several codes already, you should wait a day before trying again.
- New devices and networks. Meta's recovery hub says that for best results you should use a device you have used to log in before. Hopping between a borrowed phone, office Wi-Fi and mobile data gives Facebook a new picture each time.
- VPNs and proxies. Meta does not mention them on these pages, so this point is our inference: a VPN makes your login appear to come from somewhere else, which works against the familiar-device advice. Switch it off for the attempt.
- Wrong answers. The security check page says the date of birth it asks for is the one you gave when you signed up, which may not match the profile today.
- A browser Facebook cannot remember. Meta's page on two-factor authentication says private browsing, or a browser that clears its history when it closes, may mean you are asked for a security code each time.
- Someone else in the account. If an attacker still has a session or your password, new suspicious activity can trigger a fresh lock after you clear the old one.
#How to Break the Loop: A Calm 24-Hour Reset
The aim is one clean attempt that looks exactly like your normal login. Do it in this order.
- Stop. Close Facebook on every device and do not request another code. If a check has just finished, Meta's page on the 24-hour wait says you will have to wait 24 hours to log in, as an extra precaution, and friends can still see your profile in the meantime.
- While you wait, check the email inbox and phone number on the account still work. Read Facebook's recent emails and screenshot anything about a changed email, phone or password.
- Pick your attempt device: the phone or computer you normally use for Facebook, with the app updated or a normal browser window, not private mode.
- Use your usual network, such as home Wi-Fi or your own mobile data. Turn off any VPN, which keeps the login looking familiar even though Meta's pages do not mention VPNs.
- After a full day, open Facebook, tap "Get started" and follow each step once, slowly. Give the date of birth from sign-up. If a security question is impossible, Meta says you may be able to pick a different one or try again another time.
- If a screen shows a login or change you do not recognise, say it was not you. If offered a new password, choose one you have never used elsewhere.
- If the check finishes and Facebook asks you to wait, wait. Do not start the process on another phone.
In Malaysia, an expired prepaid line can also stop codes arriving. If the line has expired or your phone shows no service out of nowhere, contact your carrier from another phone. Our guide to a Facebook login code that never arrives covers delivery problems in more detail. If the check that keeps failing is a video selfie, read our page on a Facebook video selfie that is not working.
#When the Loop Is a Two-Factor Code Screen
Some loops are not a lock at all. If Facebook accepts your password and then asks for a two-factor code you cannot get, follow Meta's two-factor troubleshooting page. It suggests trying these in order: wait a few minutes for a delayed SMS, approve the login from another phone, tablet or browser that is still logged in, then enter one of your saved recovery codes.
If none of those work, the same page says to go to the code screen and look for the help link: "Need another way to authenticate?" on a computer, "Having trouble?" on Android or a mobile browser, and "Need help?" on iPhone or iPad. That starts an identity confirmation, which Meta says is not available in Facebook Lite, so use the full app or facebook.com in a browser.
#When the Loop Means Someone Else Is Still In
A lock that keeps returning after you clear it is a warning sign. Meta's page on recovering a hacked account lists signs such as a changed profile picture, posts or messages you did not write, two-factor that stops working, and emails saying an email address, phone number or password was changed when it was not you.
- Leave the checkpoint and go to facebook.com/hacked on a device you have used to log in before.
- If an email says your address was changed, open it in your old inbox. Meta says it sends a special link to the previous address that can reverse the change.
- If you cannot reach the email or phone, use Meta's Account Recovery hub, choose your issue, and follow the steps. Meta notes it may prompt you to find your hacked account and says to proceed even if you were not hacked.
- Once you are in, open Where you're logged in under Password and security. Meta's page on logging out of other devices shows how to select unknown sessions, or all of them, and log them out.
- Change the password and turn on two-factor authentication before you do anything else.
Our walkthrough of what to do when the hacker changed your email and phone goes further into that case.
#"Buka Checkpoint" Sellers and Other Scams
Search "buka checkpoint facebook" or post about a loop in a group, and offers often follow, in Malay, English or Chinese. Some claim a tool that skips the check. Some claim a contact at Meta. Many ask for your password, the code Facebook just sent, your backup codes, or remote access to your phone so they can "do it for you". Those details are exactly what an attacker needs to take the account, or to keep it.
- Red flag: a promise to unlock or recover the account for certain.
- Red flag: a claim of special access or a contact inside Meta.
- Red flag: any request for a code, a password, backup codes, a screen share or a remote access app.
- Red flag: payment demanded before anyone has looked at what happened.
- What legitimate help looks like: a case review first, only Meta's own forms and flows, best effort, and an honest statement that Meta decides and some accounts do not come back.
Meta's page on checking whether an email is really from Facebook lists the domains it uses, such as facebookmail.com and meta.com, and lets you confirm a message under Recent emails in Password and security. The government's NSRC 997 page says to call within 24 hours of discovering a scam so banks can act, contact the bank and make a police report. A phishing page or fake support account can be reported to CyberSecurity Malaysia's Cyber999, which helps Malaysian internet users escalate abuse reports. Our explainer on fake hackers offering account recovery shows the common scripts.
#Mistakes That Restart the Loop
- Requesting a new code every few minutes instead of waiting a day.
- Trying on a friend's phone, a cybercafe computer or a brand new handset.
- Logging in through a VPN or swapping between networks during the check.
- Using an incognito window, so Facebook cannot remember the browser.
- Entering the birthday now on the profile instead of the sign-up date.
- Starting the process again on another device during the 24-hour wait.
- Clearing the lock but leaving unknown sessions logged in and the old password in place.
#If Nothing Breaks the Loop
Sometimes the loop continues after a clean day's wait and a careful attempt. At that point, change route rather than repeating the same screen: the Account Recovery hub, facebook.com/hacked if anything was changed, or the two-factor help link if the loop is a code screen. Keep a short log of each attempt with the date, device and what the screen said, because it helps you avoid repeating what failed.
#When a Case Review Makes Sense
The steps above are the official route, and you can follow every one of them yourself. Nobody can skip Meta's check for you. A second opinion is worth having when the account runs your business Page or ads, when a takeover and a lock seem to have happened together, or when every route keeps landing on the same screen. SocialSafe by AwareXone, our recovery service, reviews what you have already tried and tells you honestly which official route is still open, if any. Our Facebook account recovery service explains how the review works, and our Trust Center lists what we will never ask for, starting with your password and codes.
#Frequently Asked Questions
How long does a Facebook checkpoint last?
Does a VPN cause the Facebook checkpoint?
Why does Facebook reject my date of birth during the check?
Will creating a new Facebook account help me get the old one back?
Is it safe to pay someone to buka checkpoint for me?
Official sources
- Facebook Help Center: Unlock your Facebook account (read 5 October 2026)
- Facebook Help Center: Get back into your account if you're being asked to do a security check (read 5 October 2026)
- Facebook Help Center: Account recovery and support hub (read 5 October 2026)
- Facebook Help Center: Troubleshoot login with two-factor authentication on Facebook (read 5 October 2026)
- Facebook Help Center: Wait 24 hours to access your Facebook account for security check (read 5 October 2026)
- Facebook Help Center: Recover your Facebook account if you were hacked (read 5 October 2026)
- Facebook Help Center: How two-factor authentication works on Facebook (read 5 October 2026)
- Facebook Help Center: Check whether an email is really from Facebook (read 5 October 2026)
- Facebook Help Center: Log out of Facebook on another device (read 5 October 2026)
- MyGOV Malaysia: NSRC 997 Hotline (read 5 October 2026)
- CyberSecurity Malaysia: Cyber999 Cyber Incident Response Center (read 5 October 2026)
Need help with your account?
Tell us the platform and what you have already tried. We review the case first, work only through official platform processes, and never ask for your password, OTP or backup codes. The platform makes the final decision. Related service: Facebook account recovery.




