Log in

Google Login Error 400 'malformed request' in TAC — sign-in fails even after format

HighTenstore Android ConnectCall of Duty: Mobile5 solutions

When trying to sign into Google services inside TAC (Play Store, YouTube, anything that requires Google OAuth), the login flow shows a Google error page:

400. That's an error.

The server cannot process the request because it is malformed. It should not be retried. That's all we know.

This blocks Play Store sign-in, account-bound CODM features, cross-device save sync, and friend lists. Reported framing:

  • "buenas estoy teniendo este problema.. alguien mas le paso? ya borre cache, desintale gameloop lo volvi a instalar y hasta formatie la computadora pero me sigue apareciendo igual" — re22 (formatted Windows install, problem persists)
  • The exact 400 dialog appears regardless of which Google account you try.
  • Reinstall + cache clear + Windows format — none resolve the error.

Root cause: Google's OAuth endpoint detects an emulated client signature mismatch — TAC's OAuth handshake sends device-fingerprint headers that don't match a real Android device. Google rejects with 400 instead of a more helpful "device not supported" because the request body fails their schema validation entirely.

Last updated 1 week ago0 users reported this issue0
Sign in to interact

Solutions

solution #617

Factory-reset TAC's Android instance, not just the Windows app. TAC's internal Android instance keeps a stale OAuth state. Reinstalling TAC on Windows doesn't reset it — only an in-emulator factory reset does:

  1. Open TAC.
  2. Click the 4-squares menu → Settings → Engine.
  3. Find "Restore Defaults" or "Factory Reset Android" (varies by TAC version).
  4. Confirm — this wipes the emulated Android storage including Google OAuth tokens.
  5. Restart TAC, retry Google sign-in.
Jun 4, 2026
Was this helpful?0

solution #618

Disconnect ALL VPNs and retry sign-in. Google's OAuth checks the device fingerprint against the IP geolocation. If your VPN exit doesn't match the device's locale + timezone settings, Google fails the handshake with 400. Disable VPN, set Windows time zone to your real one, retry. Once login succeeds, you can reconnect VPN.

Jun 4, 2026
Was this helpful?0

solution #619

Skip Google entirely — install CODM via APKPure. If Google sign-in remains blocked, install the CODM APK directly:

  1. Download CODM APK from apkpure.com (or APKMirror).
  2. Drag-drop the APK onto the TAC emulator window.
  3. TAC installs without Google's involvement.
  4. Inside CODM, log in with Activision / Facebook ID instead of Google. (Google login from inside CODM may still fail — Activision ID always works.)
Jun 4, 2026
Was this helpful?0

solution #620

Change TAC's reported device model. Smart Tool can swap the simulated device model — some models pass Google's OAuth handshake, others don't. Default "ROG Phone 9 Pro" sometimes fails; try:

  1. Smart Tool → Device Model dropdown.
  2. Change to Pixel 7 Pro or Samsung Galaxy S23.
  3. Apply Settings, restart emulator.
  4. Retry Google sign-in.
Jun 4, 2026
Was this helpful?0

solution #621

Check if Google flagged your account. If Google has security-locked your account due to "suspicious activity" (which sometimes happens after a few emulator login attempts), the 400 will persist regardless of fixes. Visit myaccount.google.com/security on a regular browser, look for "Recent security activity", clear any blocks, then retry.

Jun 4, 2026
Was this helpful?0
Experiencing a different problem?Report a new issue to help the community find solutions.

Comments (0)

No other comments yet. Be the first to share your thoughts.

Sign in to_leave_comment

On This Page