Google is preparing to roll out a crucial new security tool for Android 17, “OS Check.” The function, previously announced, began to have its working details revealed in Beta 5 of Android 17 QPR1, recently released to Pixel device users. The main objective is to offer users a robust way to confirm the authenticity of the operating system version installed on their devices, combating modified and potentially malicious versions.
Google improves protection against spoofed systems
Growing concerns about digital security and the proliferation of unofficial versions of Android motivated the development of this functionality. “OS Check” serves as a barrier against tampered software, which may appear legitimate but hides harmful intentions. The initiative aims to ensure the integrity of devices, protecting user data and system stability.
The Technology Giant plans to introduce the tool initially on Pixel smartphones, ensuring that owners of these devices have priority access to this extra layer of security. The intention is to provide a simple and effective way to check whether the operating system in use is an official version and widely distributed by the company.
Authentication procedure requires two devices
To perform the verification, users will need two devices: the device that will be authenticated and a second device considered “trusted”, which must have access to the internet. This cross-checking approach seeks to increase process security by minimizing manipulation risks.
The new feature was identified by specialist AssembleDebug in Beta 5 of Android 17 QPR1, who was able to provide a detailed preview of its operation, published by Android Authority. The evidence points to an intuitive system, despite the technical complexity involved.
Steps to check Android authenticity
The “OS Check” process involves some practical steps that users will need to follow:
- Preparation on the device to be checked:The function displays introductory information about its purpose. After reading, the user must confirm that they are ready to start.
- Second device configuration:A screen on the device to be verified instructs the user to pick up the second device (the “trusted” one) and access the `https://verify.android`. portal
- Generation of QR code on the portal:In the second device’s browser, the web page will display a unique QR code, which will serve as a bridge for verification.
- QR code reading:The device to be verified must scan the QR code displayed on the screen of the second device.
- Conclusion of the analysis:After reading and processing, the verified smartphone will present a summary screen with the detected information. Simultaneously, the web page on the second device will update with more in-depth details such as bootloader status.
Alerts or warnings during scanning, especially in beta versions, are considered normal and do not necessarily indicate a problem, as noted by the insider.
Importance of “boot hash” and future perspectives
One of the key elements for confirming authenticity is the “boot hash”. This information, displayed both on the summary screen of the verified device and on the web page of the second device, must match. The “boot hash” match is the final indication that the operating system in use is a secure and official version of Android.
Development appears to be at an advanced stage, indicating that the tool could be released soon. The expectation is that this functionality will be made available with the next launches of Google Pixel devices, possibly debuting with the Pixel 11, which should hit the market during the summer. This measure reinforces Google’s commitment to keeping the Android platform safe for its millions of users.