We now know how Android 17 wants you to prove your phone is the real thing
It's coming to Pixels first, and getting that answer takes a little friction.
OS verification is one of the security features still rolling out with Android 17. | Image by PhoneArena
Android 17 reached stable this month, though not all of its features came with it. One still on the way is OS verification, a tool that confirms your phone runs a real, unmodified copy of Android. It reaches Pixels first, starting with the Pixel 10 Pro, before rivals like the Galaxy S26 Ultra get their turn.
Google announced OS verification in May, and a new report, based on a teardown of the Android 17 QPR1 Beta 5 build, gives our most detailed look yet at how it works. It targets a real problem: bad actors push modified copies of Android that hide malware, so this confirms your phone runs the version Google signed off on.
It runs across two devices and a couple of QR codes, which I will walk through below. Since it is built on beta code Google has not shipped, the steps could still change.
For most people who buy their phone new from Google or a carrier, this is reassurance more than a daily tool. It earns its keep with used, refurbished or gray-market phones, where you cannot be sure what the last owner left running.
If you are on a Galaxy or another non-Pixel phone, you just get it later, once stable Android 17 reaches your device. The custom ROM crowd worried this might nudge them toward Google's walled garden, but Google says it does not apply to custom ROMs or forks.
The one real ask is that you have two devices, not one. For that reason, this process can be a bit clunky, but reasonable, when the whole point is trust.
While this isn't the flashiest part of Android 17, it is the kind of quiet security feature I'm glad Google is building in rather than leaving to third-party apps.
What I'd like to see is this reaching beyond Pixels soon. Budget and used-phone buyers, the ones most likely to hit a sketchy build, should not be last to get the tool that protects them.
Android 17 wants to prove your phone is the real deal
Google announced OS verification in May, and a new report, based on a teardown of the Android 17 QPR1 Beta 5 build, gives our most detailed look yet at how it works. It targets a real problem: bad actors push modified copies of Android that hide malware, so this confirms your phone runs the version Google signed off on.
Walking through OS verification, from the QR handshake to the boot hash check. | Images by Android Authority
It runs across two devices and a couple of QR codes, which I will walk through below. Since it is built on beta code Google has not shipped, the steps could still change.
When would a tool that checks if your Android is legit matter to you?
Who this is for, and who doesn't need to worry
For most people who buy their phone new from Google or a carrier, this is reassurance more than a daily tool. It earns its keep with used, refurbished or gray-market phones, where you cannot be sure what the last owner left running.
If you are on a Galaxy or another non-Pixel phone, you just get it later, once stable Android 17 reaches your device. The custom ROM crowd worried this might nudge them toward Google's walled garden, but Google says it does not apply to custom ROMs or forks.
This feature provides transparency for users on Google Mobile service licensed devices and does not apply to custom ROMs or forks.
Google, official statement, May 2026
What you'll need to run a check
The one real ask is that you have two devices, not one. For that reason, this process can be a bit clunky, but reasonable, when the whole point is trust.
Here's how OS verification works
- On the phone you are checking, tap "I'm ready".
- Scan the QR code it shows with a second device you trust, or open verify.android there.
- Scan the bigger QR code that appears with the phone you are checking.
- Compare the boot hash on the trusted device with what your phone reports. A match means your Android is legit.
A quiet security win, two-phone shuffle and all
While this isn't the flashiest part of Android 17, it is the kind of quiet security feature I'm glad Google is building in rather than leaving to third-party apps.
What I'd like to see is this reaching beyond Pixels soon. Budget and used-phone buyers, the ones most likely to hit a sketchy build, should not be last to get the tool that protects them.
If you want more on the Pixel and Android 17 front:
- Our Pixel 10 Pro review covers what the phone first in line is like to live with.
- Here's everything that arrived when Android 17 reached Pixel phones.
- For more hot takes and behind-the-scenes coverage, come find me, @jojothetechie, on X and Threads.
Popular stories
Latest News
Things that are NOT allowed:
To help keep our community safe and free from spam, we apply temporary limits to newly created accounts: