Browse
Log in / Register
Share
March 29, 2025 — A growing number of device owners are encountering a persistent “Verification failed. Please try again.” message when attempting to authenticate their hardware, following a widespread system update rolled out earlier this week. The error, which first appeared on March 27, has affected users across major smartphone brands, including Google Pixel, Samsung Galaxy, and OnePlus, causing devices to become temporarily unusable for certain services.
The issue manifests immediately after a user initiates device verification—a process typically required after a factory reset, a SIM change, or an OS update. Instead of completing within seconds, the screen displays a spinning indicator for several minutes before returning the same failure prompt. Some users report being locked out of their primary accounts, while others can bypass the check only after multiple attempts.
Industry sources indicate the root cause may be tied to a backend authentication server change associated with the latest Android security patch (March 5, 2025 security update). An internal memo, viewed by our editorial team, confirms that Google’s SafetyNet Attestation API experienced intermittent timeouts starting March 27. The memo, sent to OEM partners late Thursday, advises manufacturers to push a hotfix within 72 hours.
Affected users are not without recourse. A support bulletin issued by Samsung on March 28 recommends clearing the Google Play Services cache, then restarting the device. “If the error persists, users should remove and re-add their Google account under Settings > Accounts,” the bulletin states. Google’s official support forums now list the issue as “investigating,” with a status update expected by Monday.
In a statement provided to us, a Google spokesperson said: “We are aware of a small number of users experiencing verification failures. Our teams are working to restore full functionality. No user data has been compromised.” This aligns with the company’s typical stance, though the volume of complaints suggests the problem is broader than “small.”
Third-party security researcher Jane Morrison, co-founder of DeviceSecurity Labs, analyzed the server logs from the weekend. “We saw a 400% spike in failed attestation requests between March 27 and 29,” she said. “The timeout pattern suggests an overloaded certificate validation server, not a compromise. The fix likely involves scaling that backend.” Her analysis, published on her Substack, offers a step-by-step workaround for users comfortable with ADB commands.
For most users, the recommended path is patience. However, for those who need immediate access—such as employees using corporate devices—alternative verification methods exist. Enterprise MDM (Mobile Device Management) profiles can authenticate a device without relying on the public attestation API. IT administrators should contact their device provider for a bypass token.
As of press time, the verification failure problem has not spread to iOS or Huawei’s HarmonyOS devices. Analysts speculate that the issue is limited to Google’s own attestation service, which is predominantly used by Android and Android-based devices.
The incident underscores a fragile dependency: a single cloud authentication endpoint can bring device verification to a halt for millions. Google has promised a permanent fix in the upcoming April 2025 update, but for now, users must repeatedly tap “Try Again” or apply manual workarounds.
What to do if you see “Verification failed”:
Carriers and manufacturers are expected to release carrier-specific patches throughout next week. Users are advised to check for system updates daily until resolved.
We will continue to monitor this developing story and update as more information becomes available. If you have experienced this verification error, share your device model and Android version in the comments below.
