The official WhatsApp login error is a check on your phone, and the app you installed has almost nothing to do with it. That is why reinstalling from the Play Store, which is the advice sitting at the top of every result you have read, changes nothing whatsoever. WhatsApp is refusing a combination: this number, on this handset. Ten minutes and two spare items will tell you which half is causing it. You need one other phone and one other SIM, borrowed is fine, and the test below is the fastest diagnostic anyone has produced for this.
Table of Contents
Run the four way test before you change anything
People lose weeks to this error because they start fixing before they know what is broken. Do not touch your phone’s software yet. Do this instead.
- Your number on your phone. This is the failure you already have.
- A different number on your phone. Any spare SIM will do.
- Your number on a different phone. Borrow one for five minutes.
- Your number on your phone with the manufacturer’s software restored, if you have ever flashed anything. Save this one for last, because it wipes the device.
Then read the pattern.
| Other number on your phone | Your number on another phone | What it means |
| Works | Works | Neither one is blocked on its own. WhatsApp has flagged this number on this specific device. Overwhelmingly the commonest result, and almost always a phone whose bootloader is not locked, or one running a custom ROM. |
| Fails | Works | Your handset is being refused. Your number is fine and your account is intact. |
| Works | Fails | Your number is the problem. This is usually a ban, and no work on the phone will touch it. |
| Fails | Fails | Two separate problems at once. Deal with the number first, since the phone fix is worthless until the account is usable. |
What the check is really looking at
Android exposes a device integrity check that any app can call. The passing verdict is granted when the app is running on a genuine, certified Android device, and from Android 13 onwards that requires hardware backed proof that the bootloader is locked and the operating system is a certified manufacturer image. Where there are signs of system compromise such as root, the verdict comes back empty. Emulators fail it too.
There is a completely separate field in the same response that reports where the app came from. Installed or updated through Google Play, it reads as licensed. Sideloaded, it reads as unlicensed. Those are two different signals and they answer two different questions.
So the fix is to reinstall from the Play Store, right? That is what every ranked article opens with, and it addresses the second signal while the one that fails here is the first. You can check the first one yourself in about thirty seconds without going near WhatsApp. Open the Play Store, tap your profile picture, go to Settings, open About, and read Play Protect certification. If it says your device is uncertified, you have found your cause.
Four causes, and how to tell them apart
A bootloader that is not locked, or a custom ROM
This is the big one, and it is the cause behind the works, works pattern in the table above. One user posted his results in exactly that form: his number failed on his own custom ROM phone, a spare number worked on the same phone, his number worked on a spare phone, and his number worked again on his own phone once the original manufacturer ROM was back on it. That is a clean isolation. Nothing was banned. The device simply could not prove it was what it claimed to be, and the flag attached to that pairing.
The supported fix is to restore the manufacturer’s software and relock the bootloader. It wipes the phone. Back up first, including your WhatsApp chats, and expect to spend an evening on it.
The number was once used with a modded client
GB WhatsApp, FM WhatsApp and WhatsApp Plus all get numbers flagged. Someone tested this properly with three numbers and a freshly factory reset spare handset. His result: the flag follows the number rather than the phone. A flagged number refused every modded client on a clean device, while his other numbers ran the same modded apps on that same device without a murmur. The flagged number worked with official WhatsApp, but only after the modded app and its leftover data were completely gone from the phone.
If that describes you, the job is deletion rather than reinstallation. Uninstall the modded app. Then open internal storage and remove the folders it left behind under Android/data and Android/media, which carry the modded package name instead of com.whatsapp. Copy those folders somewhere safe first if you want your history, because removing them removes your chats.
The number itself is banned
The identical screen appears for numbers that are simply banned, and that overlap is the single biggest reason people spend a month applying device fixes to an account problem. Test three settles it. If your number fails on a clean second phone, nothing you do to your own handset matters. Request a review through the app or through support, describe what happened in ordinary language, and then wait. One person documented a number that came off the list by itself roughly six months later with no further action from him.
One warning while we are here. Wherever this error gets discussed, someone turns up offering a paid unban. There is no such service. What they want is money, and often your number and a verification code, which is how numbers get stolen outright. Ignore every one of them.
You are on an iPhone
None of the Android explanations apply. There is no bootloader to relock and no Play Protect status to read. The community thread people treat as the reference on this error opens by admitting there is no definitive solution, and confirms it reaches iOS too. For an iPhone what remains is the four way test, which still tells you whether the number or the handset is being refused. After that, a review request and a long wait.
The part I want to be serious about
The workarounds circulating for the device side of this involve rooting the phone, then installing Magisk and LSPosed alongside a module whose entire purpose is to lie to apps about the bootloader state. They do work. I am still going to tell you to leave them alone if this number matters to you.
Hiding root from apps is a maintenance job that never ends, and it breaks on the next update at the worst possible moment. Your banking app runs that same integrity check. So does your payment app, and increasingly so does anything holding a ticket or a boarding pass. A phone that receives your two factor codes is a poor place to run experiments. If this number is how customers reach your business or how your family reaches you, take the boring supported route: manufacturer software back on, bootloader locked, phone backed up beforehand.
When there is no fix, and what to do meanwhile
Some of these cases never resolve, and no honest answer can leave that out. People have sat with the same error for over a year across multiple reinstalls and multiple support tickets, receiving the same automated reply about unofficial apps every time. At least one gave up and bought a different phone. That is a real outcome and it happens to people who did nothing wrong.
While you work through it, the usable stopgap is to log the account in on a second phone and link your daily phone as a companion device. It is imperfect. Live location sharing and some profile controls behave differently on a linked device, contacts do not carry across, and a fair number of people report the linking step failing with its own error. It still beats being unreachable.
| Play Protect says uncertified | Restore the manufacturer ROM and relock the bootloader, after a full backup |
| You ran GB, FM or Plus on this number | Delete the modded app and its Android/data and Android/media folders, then install the official app |
| Your number fails on a clean spare phone | Treat it as a ban. Request a review and stop working on the handset |
| Everything works except this pairing | Device integrity on your phone. Same fix as row one |
| iPhone, no jailbreak, no history of mods | Run the four way test, request a review, use a linked device meanwhile |
| Someone offers to unban you for a fee | Walk away and never share a verification code |
