MicroG “App Not Installed” Error? The Package-Conflict Fix (Complete Guide)

You downloaded MicroG, tapped the APK, and instead of an install screen you got two cold words: “App not installed.” No reason, no error code, no hint about what to do next. If you are trying to set up MicroG on a Xiaomi, Samsung, or Realme phone in India, this is the single most common roadblock — and in almost every case it is not a broken phone or a broken APK. It is a package conflict: Android has found something already on your phone that clashes with the MicroG file you are trying to install, and it refuses to overwrite it.

This guide explains exactly why that happens, how to diagnose your own case in under a minute, and how to fix it without root — including the stubborn cases where the old MicroG does not even appear in your app list.

Why Android says “App not installed” for MicroG

Every Android app has a package name — a unique ID. MicroG’s GmsCore uses com.google.android.gms, the same ID as Google Play Services. Android enforces two hard rules:

• One package name, one app. You cannot have two apps with the same package name installed at once. So you cannot keep Vanced MicroG and install MicroG RE alongside it — one must go first.
• Same package name, same signature. An update to an installed app must be signed with the same key as the original. MicroG RE, Vanced MicroG, and the original GmsCore are signed with different keys, so Android treats the new file not as an update but as a conflicting app — and blocks it silently with “App not installed.”

That is why the error is so confusing: the APK itself is usually fine. Android is protecting you from a signature mismatch, but it does not explain that in plain words. If you install through ADB instead of tapping the file, you get the honest version of the same error: INSTALL_FAILED_UPDATE_INCOMPATIBLE.

Before you start, it helps to know which builds you may have installed before. Our comparison of the three main builds — MicroG RE vs GmsCore vs Vanced MicroG — explains which one suits Morphe apps, ReVanced, and general use, so you can pick one build and stick with it rather than swapping back and forth.

Diagnose your case in 60 seconds

What you see	Most likely cause	Fix to use
“App not installed” immediately, no progress	Old MicroG installed with a different signature	Fix 1 or Fix 2 below
MicroG is nowhere in Settings → Apps	Installed for another user profile, or as a system app	Fix 2 (ADB, all users)
“Package appears to be invalid”	Corrupt or incomplete download	Fix 3
“App isn’t compatible with your phone”	Wrong architecture build for your processor	Fix 3
Install starts, then fails near the end	Low storage, or Play Protect / MIUI Optimizations blocking it	Fix 4

Fix 1: Uninstall the old MicroG completely (the fix that works most often)

Do this before anything else. A half-removed MicroG — uninstalled for the main user but still present for a work profile, second space, or dual-apps clone — still blocks the new install.

1. Open Settings → Apps → See all apps. Tap the three-dot menu and turn on Show system apps if your phone offers it.
2. Search for MicroG, MicroG Services Core, GmsCore, or Vanced MicroG. If you find one, open it and tap Uninstall.
3. If the button says Disable instead of Uninstall, the build is a system app — do not force it; jump to the system-app note in Fix 2.
4. Also check Settings → Apps → Dual apps / Second space / Work profile (names vary by brand) and remove any MicroG clone there.
5. Restart the phone. Then install the new MicroG file fresh — do not install it over anything.

One practical warning: uninstalling MicroG will sign you out of patched apps that depend on it, such as ReVanced or Morphe clients. That is expected. After the fresh install, you add your Google account again in MicroG → Accounts. Our Morphe setup guide walks through that order — MicroG first, then the patched apps — which avoids a second round of the same error.

Fix 2: When the old MicroG will not uninstall — the ADB method

Sometimes the old build is installed but invisible: it was installed under a different user, or a previous owner/profile left it behind. ADB (Android Debug Bridge) can see and remove it. This does not require root, and it does not wipe your phone.

1. On the phone, turn on Settings → About phone → tap Build number 7 times to enable Developer options, then turn on USB debugging in Developer options.
2. On a computer, install the platform-tools package for your system (from Google’s official Android developer pages) and connect the phone with a USB cable. Accept the “Allow USB debugging?” prompt on the phone.
3. Run: adb devices — your phone should appear as “device”.
4. Check what is installed: adb shell pm list packages | grep gms — if com.google.android.gms appears, MicroG (or Play Services) is present.
5. Remove it for the current user: adb uninstall com.google.android.gms
6. If that reports failure because the app is installed for other users, remove it for all users: adb shell pm uninstall --user 0 com.google.android.gms
7. Disconnect, restart the phone, and install the new MicroG APK again.

System-app warning: if your phone runs a ROM that ships MicroG as a system app — for example LineageOS for microG — do not remove it this way unless you know what you are replacing it with. A ROM-bundled GmsCore is part of the system; removing it can break apps that expect it. In that case the correct move is usually to keep the bundled build and update it only from the same source/ signature, or to switch ROMs deliberately — not to force a different build over the top.

Fix 3: Rule out a bad file — corrupt download or wrong architecture

If no old MicroG exists and the install still fails, suspect the file itself:

• Re-download from the official source. Get MicroG from our MicroG download page or the project’s official pages at microg.org. Do not use random mirror APKs — a repacked file may be corrupt or, worse, tampered with.
• Check the download completed. If the file size looks far smaller than expected, or your browser shows the download as interrupted, delete it and download again on stable Wi-Fi rather than a weak mobile signal.
• Match the architecture. Most phones sold in India in the last few years are arm64 (arm64-v8a). An armeabi-v7a-only build on a 64-bit-only device, or vice versa on very old hardware, can fail. If your phone is from 2020 or later, the standard arm64 build is almost certainly the right one.
• Do not use split APK installers for MicroG unless the source explicitly ships it that way. A partial set of split APKs produces the “package appears to be invalid” error even when every part downloaded fine.

Fix 4: Brand-specific blockers on Xiaomi, Samsung, and Realme

Indian-market phones add their own layers on top of Android’s rules:

• Xiaomi / Redmi / POCO (MIUI & HyperOS): Go to Settings → Privacy protection → Special permissions → Install unknown apps and allow your browser or file manager. Also check Settings → Additional settings → Developer options → turn off MIUI optimization temporarily if installs keep failing — remember to note the original setting so you can restore it. MIUI’s own security scan can also block the install; if it prompts, choose to install anyway only for a file you downloaded from a trusted source.
• Samsung (One UI): Allow Settings → Biometrics and security → Install unknown apps for the app doing the installing. Samsung’s Auto Blocker (Settings → Security and privacy → Auto Blocker) blocks sideloading when on — turn it off for the install, then back on afterwards if you use it.
• Realme / OPPO (Realme UI / ColorOS): Same unknown-sources permission as above, plus check Settings → Password & security → System security for any install-blocking toggle. On all three brands, free up at least 1 GB of storage before retrying — Android can silently fail an install when storage is nearly full.
• Google Play Protect: Play Protect sometimes flags MicroG because it uses the Play Services package name. If it blocks the install, that is a warning to check your source, not a button to tap blindly. Only proceed when you are certain the file came from the official project or our download page.

Verify the fix: the MicroG Self-Check

After a successful install, do not just assume it worked. Open MicroG Settings → Self-Check and confirm the core items are ticked: system spoofs the Play Services signature (on ROMs that support signature spoofing), MicroG has the permissions it needs, and battery optimization is off for MicroG so it is not killed in the background. Then open MicroG → Accounts and add your Google account. If sign-in works and the patched app opens your subscriptions, the conflict is genuinely resolved — the install screen alone is not proof.

If the Self-Check shows signature spoofing as unsupported, that is a separate ROM limitation, not an install failure: stock Xiaomi, Samsung, and Realme firmware does not allow signature spoofing, and MicroG on those phones works for account sign-in in patched apps even without it. Do not chase a spoofing fix on a locked stock ROM — it requires a custom ROM or a patched framework, which is a much bigger decision than fixing an install error.

What not to do

• Do not install two MicroG builds “just in case.” Android forbids it, and trying is exactly how this error starts.
• Do not clear data hoping it fixes a signature conflict. Clearing data does not change the signature; only a full uninstall does.
• Do not factory-reset the phone for this error. It is almost never necessary — Fixes 1 and 2 resolve the overwhelming majority of cases, and a reset costs you everything else for no benefit.
• Do not mix builds across apps. Pick one build — RE, GmsCore, or Vanced — and use it for all your patched apps. Swapping builds means uninstalling and re-adding accounts every time.

Our verdict

For most Indian users on non-rooted Xiaomi, Samsung, and Realme phones, the winning routine is simple and boring — which is exactly why it works: uninstall every trace of the old MicroG, restart, install one current build fresh, then install the patched apps after it. The error message makes the problem look mysterious, but once you know Android is enforcing a one-package-one-signature rule, the fix is mechanical. If Fix 1 fails, Fix 2 (ADB, all users) is the step most guides skip — and it is the one that rescues the “but I already uninstalled it” cases.

Frequently asked questions

Why does MicroG say “App not installed” but other APKs install fine?

Because other APKs do not collide with an existing package name and signature. MicroG uses com.google.android.gms, so any previous MicroG build — even one you forgot installing years ago for Vanced — blocks the new file, while unrelated apps install normally.

Can I keep Vanced MicroG and install MicroG RE at the same time?

No. Android allows only one app per package name. Uninstall Vanced MicroG completely first, then install MicroG RE, then reinstall your patched apps so they connect to the new build.

I uninstalled MicroG but the error persists. What now?

Check other user profiles, Second Space, Dual Apps, and work profiles, then use the ADB commands in Fix 2 to confirm com.google.android.gms is truly gone. In most “already uninstalled” cases, a copy is still installed for another user.

Is the “App not installed” error a sign my phone is damaged?

No. It is Android’s normal signature-protection behaviour, not hardware damage and not a virus warning. Treat it as a housekeeping problem: remove the old build, install the new one clean.

Will uninstalling MicroG delete my patched apps?

No, it does not delete them, but they will lose Google sign-in until you reinstall MicroG and add your account again. Your downloads and local settings inside those apps are generally unaffected, but subscriptions and sync return only after you sign in again.

Should I factory-reset if nothing works?

Almost certainly not. Work through Fixes 1–4 in order first, including the ADB check. A factory reset is a last resort for a broken system, not for a package conflict that a single uninstall command resolves.

For the clean, verified download and the full setup sequence, see our MicroG homepage.