MicroG Login Failed? Google Account Won’t Add — Every Working Fix

You tap “Add account” in MicroG, type your Google email and password, and instead of a signed-in account you get an error, a spinning loader, or a screen that dumps you straight back to where you started. ReVanced or Morphe YouTube then refuses to sign in too, because there is no Google account for it to use. This guide walks through every fix that actually works, in the order you should try them — so you stop guessing and get signed in.

Why MicroG login fails: the real causes

MicroG is not the official Google Play Services. It stands in for them so that apps like ReVanced YouTube can sign you in without Google’s own services on your phone. That means sign-in depends on more moving parts than a normal login: the right MicroG build, permission for MicroG to pretend to be Play Services (signature spoofing), an account added in the right place, and a phone that does not kill MicroG in the background. When any one of those breaks, Google’s servers may never even see your login attempt — which is why retyping the same password ten times changes nothing.

Symptom	Most likely cause	Fix below
Error straight after entering your password	Wrong MicroG variant, or signature spoofing off	Fixes 1 and 2
Loader spins, then nothing happens	Battery optimisation, or a weak/blocked connection	Fixes 5 and 6
“Account already exists” but no account shows in the app	Half-added account stuck in the system	Fix 3
Sign-in worked yesterday, fails today	MicroG updated, battery settings reset, or an old build	Fixes 4 and 7
Works on Wi-Fi, fails on mobile data (or the reverse)	Network, VPN, or date-and-time problem	Fix 6

Before you start: the 2-minute checklist

Do these first. They rule out the silly causes and save you a full reinstall.

• Confirm your password works elsewhere. Open a browser, go to a Google sign-in page, and sign in there. If that fails too, the problem is your Google account, not MicroG — reset the password first and come back.
• Check the date and time. Go to Settings > System > Date & time and turn on automatic date and time. Google sign-in rejects logins from a phone whose clock is far out, and this is a surprisingly common cause after a battery swap, a factory reset, or a trip.
• Use a stable connection. Try Wi-Fi first. If you are on a VPN, turn it off for the sign-in attempt — some VPN exits are blocked or throttled by Google.
• Know which app you are signing into. ReVanced YouTube and Morphe YouTube need different MicroG builds. Signing into the wrong combination is the single most common cause of this error, and it is covered in Fix 1.

Fix 1: Install the MicroG variant that matches your app

This is the fix that solves the majority of login failures, so do not skip it even if MicroG “seems installed”. ReVanced apps patched for the standard MicroG expect the standard build (often called GmsCore), while some forks expect their own companion build. If the app and MicroG do not match, the app cannot hand the login over to MicroG at all.

1. Uninstall every MicroG build currently on your phone. Having two builds installed side by side is itself a cause of sign-in conflicts.
2. Download the build that matches your app from our MicroG APK download page and install that one build only.
3. Open the app you want to sign into (for example ReVanced YouTube) and tap Sign in. It should hand you over to MicroG’s account screen. If it opens a browser or shows a different login screen, the app and MicroG still do not match — recheck which build your app’s patcher or provider recommends.

If you are setting up YouTube Music specifically, our MicroG for YouTube Music setup guide spells out which build goes with ReVanced and which goes with Morphe, step by step.

Fix 2: Turn signature spoofing on and pass the Self-Check

Signature spoofing is what lets MicroG stand in for Google Play Services. Without it, MicroG cannot register your account, and sign-in fails no matter how correct your password is. This setting lives in your ROM, not in MicroG itself, so the exact path depends on your phone — on LineageOS-based ROMs look under Settings > System > MicroG or in the privacy/trust settings for a signature-spoofing toggle; on other ROMs it may be under developer or security settings.

1. Open MicroG Settings > Self-Check.
2. Work down the list until every core item is ticked — especially the signature-spoofing permission and the account-related items.
3. If signature spoofing is unticked and there is no toggle anywhere in Settings, your ROM does not support it. That is a ROM problem, not a MicroG problem: you need a ROM with signature-spoofing support, or a patch module for your current setup. No amount of reinstalling MicroG will fix it on an unsupported ROM.
4. Grant every permission MicroG asks for during this check. Denying a permission and hoping sign-in still works is a common self-inflicted cause of this error.

Fix 3: Remove the half-added account, then add it again properly

A failed sign-in often leaves a ghost behind: Android thinks the account exists, MicroG thinks it does not, and every new attempt collides with the old one. The fix is to clear it out completely and start the addition from the right place.

1. Go to Settings > Passwords & accounts (on Samsung phones: Settings > Accounts and backup > Manage accounts) and look for the Google account you tried to add.
2. If it is there, remove it. Confirm the removal — a half-removed account causes the same collision.
3. Restart your phone. This clears the stuck sign-in session.
4. Now add the account from inside MicroG, not from the app: open MicroG Settings > Google Accounts > Add account, and sign in there.
5. Only after the account shows in MicroG Settings should you open ReVanced or Morphe and sign in. The app should now pick up the account without asking for your password again.

Our verdict: adding the account from inside MicroG first, and letting the app pick it up second, is more reliable than signing in from inside the app. If you have only ever tried the app route, try the MicroG route before anything more drastic.

Fix 4: Clear MicroG data in the right order (not just cache)

Clearing cache alone rarely fixes a login failure, because the broken state lives in MicroG’s stored account data. Clearing data is safe — it removes MicroG’s local state, not your Google account — but do it in this order so you do not recreate the same broken state:

1. Remove the account as described in Fix 3.
2. Go to Settings > Apps > MicroG Services > Storage & cache and tap Clear storage (or Clear data).
3. Restart your phone.
4. Open MicroG Settings, run the Self-Check again, then add the account from MicroG Settings > Google Accounts.

If MicroG itself will not install or update cleanly while you are doing this, the package-conflict causes in our “App Not Installed” fix guide are the next place to look — a conflicting leftover build blocks a clean reinstall just as surely as it blocks sign-in.

Fix 5: Stop your phone killing MicroG during sign-in

Xiaomi, Samsung, and Realme phones are the worst offenders here. Their battery managers kill background apps aggressively, and MicroG needs to stay alive through the whole sign-in handshake. If your login spins forever or dies halfway, this is the likely culprit.

• Xiaomi / HyperOS & MIUI: Settings > Apps > MicroG Services > Battery saver > No restrictions. Also open the recent-apps screen, find MicroG if it appears there, and lock it so it is not swiped away.
• Samsung / One UI: Settings > Battery > Background usage limits — make sure MicroG is not in sleeping or deep-sleeping apps. Then Settings > Apps > MicroG Services > Battery > Unrestricted.
• Realme / ColorOS: Settings > Battery > App battery management > MicroG Services > Allow background running and allow auto-start.
• On any phone, also check that Data Saver is not blocking MicroG: Settings > Network & internet > Data Saver, and allow unrestricted data usage for MicroG if Data Saver is on.

Do this before retrying sign-in, not after — a battery kill mid-login can leave exactly the half-added account described in Fix 3, and you will end up chasing your own tail.

Fix 6: Rule out network, VPN, and Google-side blocks

If sign-in fails on one network but works on another, the network is the problem. Switch between Wi-Fi and mobile data and retry. Turn off any VPN or ad-blocking DNS for the attempt, and if you are on a college, office, or hostel network with a captive portal or firewall, try a personal hotspot instead — some networks block the endpoints MicroG uses.

On the Google side, two things are worth checking in a browser at myaccount.google.com: first, that 2-Step Verification is not demanding a method your MicroG sign-in cannot complete (if it is, complete a normal browser sign-in first so the device and session are recognised); second, that Google has not flagged the sign-in as suspicious and asked you to confirm it was you. A flagged sign-in looks exactly like a MicroG failure from the phone’s side, and only the browser prompt reveals it.

Fix 7: Update MicroG — and reinstall cleanly if it is old

Very old MicroG builds stop signing in when Google changes something on its side. If you have not updated in a long time, a clean update is worth doing: remove the account, uninstall MicroG, install the current build from our download page, restart, and add the account again. Do not install a new build over a broken one and hope it heals — the broken account state survives an over-the-top update, which is why Fix 3 comes before this one.

For the record, the official MicroG project documents its components and setup on microg.org. If a guide you find elsewhere quotes a version number or feature that does not appear there or in the release notes of the build you installed, treat it with suspicion — stale guides are a real source of bad login advice.

Verify it worked: the Self-Check test

Do not call it fixed because one app opened. Verify properly:

1. MicroG Settings > Google Accounts shows your account.
2. MicroG Settings > Self-Check shows its core items ticked.
3. Open ReVanced or Morphe YouTube and confirm you are signed in — your subscriptions and history should load.
4. Lock the phone, wait a minute, and reopen the app. If you are still signed in, the battery fix held. If you are signed out again, go back to Fix 5 before anything else.

What will not fix this (so you can stop trying)

• Retyping the same password repeatedly. If the password works in a browser, it is not the password.
• Installing a second MicroG build alongside the first. That creates conflicts; it never resolves them.
• Factory-resetting the phone before trying Fixes 1–5. A reset wipes your data for a problem that is almost always a setting, and the same setting will be wrong again after the reset.
• Expecting MicroG sign-in to unlock banking apps or apps that demand Play Integrity. Those apps check for genuine Play Services, not just a signed-in account, and MicroG does not pass that check. That is a separate limitation, not a login bug.

Frequently asked questions

Why does MicroG say my password is wrong when it works on Google’s site?

Usually it is not checking your password at all — it is failing earlier, on the variant mismatch, signature spoofing, or a stuck account. Confirm the password in a browser, then work through Fixes 1–3 in order.

Should I add my Google account in Android Settings or in MicroG Settings?

In MicroG Settings, under Google Accounts. Adding it in Android’s generic account screen can create an account MicroG does not manage, which the app then cannot use. Add it in MicroG first, then let the app pick it up.

Can I use two Google accounts with MicroG?

Yes — add each one in MicroG Settings > Google Accounts. If the second account fails while the first works, remove only the failing one and re-add it; do not clear all MicroG data, which would disturb the working account too.

Does MicroG login work on Xiaomi, Samsung, and Realme phones in India?

Yes, on all three, but those brands’ battery managers are the most likely cause of a stalled sign-in. Apply the brand-specific battery steps in Fix 5 before retrying, and remember that a software update on these phones can silently re-enable battery restrictions you already turned off.

I signed in, but the app signs me out after a restart. What now?

That is a background-kill problem, not a login problem. Reapply Fix 5, lock MicroG in the recent-apps screen if your phone supports it, and check that a recent system update has not reset the battery setting.

Is signing into MicroG safe for my Google account?

You are entering your Google credentials into MicroG’s sign-in flow rather than Google’s own app, so only use a MicroG build from a source you trust, keep 2-Step Verification on, and review signed-in sessions at myaccount.google.com afterwards. If anything about a build looks off, do not sign in with your main account until you have verified the source.

The bottom line

Work the fixes in order: matching variant, signature spoofing, clean account removal and re-add from inside MicroG, then battery and network checks. Most login failures are fixed by the first three. If you have worked through all seven and sign-in still fails, the remaining suspects are your ROM (no signature-spoofing support) or a Google-side security flag — both are diagnosable from the Self-Check screen and a browser sign-in, and neither is fixed by reinstalling the same build again. Grab the current build from our MicroG download page and start from Fix 1.