You open the Play Store and see a bold warning: “This device isn’t Play Protect certified.” Maybe it popped up on a brand-new phone. Maybe it showed up right after you flashed a fresh custom ROM.
Either way, Google just locked the front door. Sign-in fails, apps won’t update, and your bank app may stop talking to you. One reader on a tech blog wrote that his OnePlus 6 got the same error, and he was far from alone.
The good news? Most cases have a clear cause and a clear fix. This guide helps you find your cause first, then fix it step by step.
To fix a Play Protect certification error, tap Fix device issue in Play Store settings, update Play services and Android, and restart. If your phone has a custom ROM, root, or an unlocked bootloader, go back to stock software. Custom ROM users can also register their GSF ID.
What Is a Play Protect Certification Error?
It’s a message that says Google can’t confirm your phone passed its Android tests. You may see it as “This device isn’t Play Protect certified” or as “Device is not certified” in Play Store settings.
Here’s the simple version. Google keeps a record of phones that passed its Android compatibility tests, and only those phones can ship with Google apps like the Play Store. Think of it as an ID card for your phone. No card, no entry.
Is This the Same as Play Protect Scanning?
No. Play Protect is the tool that scans your apps for bad stuff. Certification is a separate check on the phone itself.
Google says it plainly: turning off Play Protect will not fix a “Device is not certified” issue. Don’t waste your time in that menu.
Also Read: How to Enable Android Theft Protection and Find a Lost Phone
Why Does the Error Happen?
The error shows up when your phone isn’t on Google’s certified list, or when its software fails the check. The most common causes are an unlocked bootloader, root, or a custom ROM. Old Play services or a bad connection can also trigger it.
Let’s break down each cause in plain words.
Unlocked Bootloader
The bootloader is the small program that starts your phone. Unlocking it is like breaking the factory seal on a box. Google can see the seal is broken, and the check fails.
Rooted Phone
Root gives you full admin control over Android. It’s powerful, but it changes the system files that Google wants to stay untouched. A rooted phone often fails the check for that reason.
Custom ROM
A custom ROM is a different version of Android, made by a community instead of your phone maker. It often brings the unlocked bootloader and root along for the ride. Google’s help page lists a modded Android OS as one of the most common reasons for the error.
A Phone That Never Passed the Tests
Some phones, tablets, and TV boxes were never certified at all. Cheap no-name devices, some imports, and phones sold without Google apps all fall here. If your phone isn’t on Google’s list, it isn’t certified, and no setting can change that.
Old Play Services or a Glitch
Sometimes the phone is fine and the problem is small. Google’s own table points to a missing network connection, outdated Google Play services, or a temporary error. These are the easiest to fix.
How Do You Check Your Certification Status?
Open the Play Store, tap your profile icon, tap Settings, then tap About. Look under Play Protect certification. It will say either “Device is certified” or “Device is not certified.”
- Open the Google Play Store.
- Tap your profile icon at the top right.
- Tap Settings.
- Tap About.
- Read the Play Protect certification line.
Next, check if your phone is on Google’s list of certified devices. If it’s not on the list, jump to Fix 7.
Also Read: Google Play System Update vs Android Security Update: What’s the Difference?
Which Fix Should You Try?
Pick the row that matches your phone, then jump to that fix.
| Your situation | Best fix |
|---|---|
| Phone is on Google’s list, and the error looks like a glitch | Fix 1, Fix 2, and Fix 3 |
| Bootloader is unlocked, software is original | Fix 4 |
| Rooted or custom ROM, and you want to go back to stock | Fix 5 |
| Custom ROM, and you want to keep it | Fix 6 |
| Phone is not on Google’s list | Fix 7 |
| Phone is on the list, but the error still shows | Fix 8 |
Fix 1: Tap “Fix Device Issue”
If your phone is on Google’s list, start with the Fix device issue button. It runs a few checks and either repairs the problem or tells you what’s wrong.
Android Authority first spotted this button in an early 2024 Play Store build, and it has since rolled out. Here’s how to use it:
- Open Play Store, then your profile icon, then Settings.
- Tap About.
- Scroll to Play Protect certification.
- Tap Fix device issue.
If it doesn’t fix everything, read the message it shows. Here’s what each one means, based on Google’s official table.
| Message | What it means | What to do |
|---|---|---|
| Your device has no network connection | The phone can’t reach Google’s systems | Connect to stable internet and try again |
| Google Play services is out of date | Your Play services version is too old | Update Google Play services |
| Google Play services can’t be found | It’s turned off or not installed | Turn it on in Settings |
| Lock bootloader to fix issue | Your bootloader is unlocked | Lock it again (see Fix 4) |
| Reset device to fix issue | Your phone may be rooted or running a custom OS | Unroot, update, reset, or flash the original build (see Fix 5) |
| Install the latest system updates | Updates often fix device issues | Update Android, then restart |
| There was an issue found with your device | The phone failed the checks. Common reasons: unlocked bootloader, modded OS, root | See Fix 4 and Fix 5 |
| Something went wrong. Please try again later. | An unknown error, often a short glitch | Wait at least 10 minutes and try again |
Fix 2: Do the Basic Checks
These take five minutes and fix more cases than you’d think. Work through them in order.
- Check your internet. Switch between Wi-Fi and mobile data to test.
- Turn on automatic date and time. Go to Settings, then System, then Date & time, and switch on Set time automatically. A wrong clock can break Google checks.
- Update the Play Store. In Play Store, go to Settings, then About, then tap Update Play Store.
- Update Google Play services. Google has a short guide for this.
- Install system updates. Go to Settings, then System, then Software update. Google says updates often fix device issues, though it’s not a sure thing.
- Restart your phone.
Menu names change from brand to brand. If you can’t find a setting, use the search bar at the top of Settings.
Also Read: Why Wireless CarPlay Keeps Disconnecting and Reconnecting (And How to Fix It)
Fix 3: Clear Play Store and Play Services Data
Old, broken data inside these apps can cause false errors. Clearing it gives them a clean start, like wiping a foggy window.
- Open Settings, then Apps.
- Tap Google Play Store, then Storage.
- Tap Clear cache, then Clear data.
- Go back and repeat for Google Play services.
- Restart your phone and check the status again.
Don’t clear data for Google Services Framework. That app holds your device’s Android ID, and clearing it can create a new one. You may have to register again if you use Fix 6.
You may need to sign in again in a few Google apps after this. That’s normal.
Fix 4: Lock the Bootloader Again
If the error says your bootloader is unlocked, locking it again is the official fix. But do this only on your phone maker’s original software. Google says to follow the maker’s own instructions.
Big warning: locking the bootloader while a custom ROM is installed can leave some phones unable to start. Locking also wipes your data on most phones. Back up first, go back to stock software (Fix 5), and only then lock it.
Fix 5: Unroot and Go Back to Stock Software
If your phone is rooted or runs a custom ROM, this is the real fix. Google suggests trying these steps in order and checking after each one:
- Unroot your phone. Use the unroot option of your root tool, or flash the original system files.
- Update Android. Check your Android version and install any update.
- Do a factory reset. This erases your data, so back up first.
- Flash the original build. Install the signed Android build your phone maker shipped. Google says it must be the original, maker-signed version.
For step 4, use your phone maker’s support site. They have the right files and the right steps for your exact model.
Picking the wrong file is the fastest way to a dead phone. Double-check your model name before you flash anything.
Also Read: Windows Detects Webcam but Apps Cannot Use It? 11 Fixes
Fix 6: Register Your Device With Google (Custom ROM Users)
If you want to keep your custom ROM, you can register your phone’s ID with Google. This usually brings back Google sign-in and Google apps. It does not make your phone officially certified.
The ID is called the GSF ID (Google Services Framework ID). It’s a long code that belongs to your phone. Here’s the process:
- Install the Device ID app and open it.
- Copy the code next to Google Service Framework (GSF).
- On any browser, go to
google.com/android/uncertifiedand sign in with your Google account. - Paste the code, solve the captcha, and tap Register.
- Restart your phone.
- Wait a few minutes, and up to an hour if it doesn’t work right away.
Two tips from people who’ve done this. If your phone can’t sign in, do steps 3 and 4 on a PC or another phone. And if your browser blocks the Device ID download, Customrombay suggests getting Firefox on another device and moving the file over.
Set your expectations. XDA and other guides all say the same thing: the Play Store still shows “not certified” after this. All it does is whitelist the device for Google apps. On some newer Android versions the Device ID app also fails to install, and you’ll need a PC and ADB instead.
Fix 7: Contact the Seller or the Maker
If your phone isn’t on Google’s certified list, no app or setting will fix it. Google’s advice is to contact your device maker for a certified device.
If you just bought it, send it back. A new phone that isn’t certified is a bad deal, plain and simple. Don’t wait around while the return window closes.
Fix 8: Report a False Alert
What if your phone is on the list and still shows the error? You can tell Google. Here are the steps from Google’s help page:
- Open Settings and tap your profile picture.
- Tap Give feedback at the bottom.
- Describe what happened. Add the hashtag #deviceintegrity and your phone model.
- Tap System logs to include more detail.
- Tap Send.
It’s not instant, but it gives Google the data it needs to review the alert.
Why Do Banking Apps Still Fail?
Because certification and Play Integrity are two different checks. Fixing one doesn’t always fix the other. Customrombay points out that registering your device does not fix Play Integrity, so some banking and government apps may still say no.
You’ll see “Play Integrity Fix” modules online. They need root, they’re unofficial, and they can stop working any week. My honest opinion: don’t build your money life on a trick that Google can break overnight. For banking apps, stock software with a locked bootloader is the safest bet.
Mistakes to Avoid
- Turning off Play Protect and expecting the error to vanish. Google says it won’t.
- Clearing Google Services Framework data. It can change your device ID.
- Locking the bootloader on a custom ROM. This can brick some phones.
- Installing random “certified bundle” APKs. Some guides push these for Huawei phones, but files from unknown sources can hide bad code.
- Doing a factory reset with no backup.
Is It Safe to Use an Uncertified Phone?
Not really. Google lists several risks for devices that aren’t Play Protect certified:
- The device may not be secure.
- It may not get Android or app updates.
- The Google apps on it aren’t licensed and aren’t the real thing.
- Apps and features may not work right.
- Your data may not have a secure backup.
If you handle money or private files on that phone, take this seriously.
Frequently Asked Questions
Why does my phone say “This device isn’t Play Protect certified”?
Google can’t match your phone to its list of tested devices, or the phone failed the software check. The usual reasons are an unlocked bootloader, root, a custom ROM, or a phone that was never certified.
Does turning off Play Protect fix the error?
No. Play Protect scans apps, and certification checks the device. Google says turning off Play Protect will not fix a “Device is not certified” issue.
Does registering my GSF ID make my phone certified?
No. It only whitelists the phone so Google apps can work. The Play Store will likely still show “not certified,” and banking apps may still fail.
Will locking the bootloader fix it?
It can, if the rest of your software is the original from your phone maker. If you have a custom ROM, go back to stock first, or the phone may not start.
What if my phone is certified and still shows the error?
Try Fix device issue, install updates, and wait 10 minutes if you see “Something went wrong.” If it still shows up, send feedback with the hashtag #deviceintegrity.
Can I fix it without a PC?
Often, yes. Fix 1, 2, 3, and 8 need only your phone. Going back to stock software usually needs a PC.
Final Thoughts
A Play Protect certification error sounds scary, but the cause is usually simple. Start with Fix device issue and the basic checks. If your phone has root, a custom ROM, or an unlocked bootloader, the clean fix is to go back to stock software.
If you want to keep your custom ROM, registering your GSF ID gets Google apps working again. Just remember it’s a pass, not a real certificate.