Revanced gmscore

What Is ReVanced GmsCore?

New to the ReVanced ecosystem? Start with our YouTube Vanced vs. ReVanced comparison to understand how the projects differ.

When ReVanced users talk about signing into a patched YouTube app, they are using ReVanced GmsCore — a downstream fork of the upstream microG project. It is the authentication layer that lets you sign into YouTube ReVanced with your Google account on a non-rooted phone.

Upstream microG is an open-source reimplementation of Google Play Services created by Marvin Wißfeld (mar-v-in) for custom ROMs like LineageOS and /e/OS. The ReVanced Team forked this project, changed its package name to app.revanced.android.gms, stripped out unnecessary components, and tailored it specifically for ReVanced apps. Huawei users should also see our microG for Huawei setup guide.

The Old “Vanced microG” Is Dead

How ReVanced GmsCore Works

When you patch YouTube with ReVanced Manager, you must include the GmsCore support patch. This patch modifies YouTube to look for app.revanced.android.gms instead of the official com.google.android.gms. Here is the actual flow:

1. YouTube ReVanced requests Google sign-in.
2. The GmsCore support patch redirects the request to ReVanced GmsCore.
3. ReVanced GmsCore handles the OAuth login flow with Google’s servers.
4. Your account token is returned to YouTube ReVanced.
5. Subscriptions, playlists, and watch history sync normally.

Key Entities in the ReVanced GmsCore Ecosystem

The ReVanced Team

Led by oSumAtrIX, they maintain:

• ReVanced Manager (the patching tool)
• ReVanced Patches (the modification bundle)
• ReVanced GmsCore (the microG fork for ReVanced)

The ReVanced Team maintains the core patching tools, GmsCore, and patch bundles used across the ecosystem.

inotia00 & ReVanced Extended (RVX)

inotia00 maintains ReVanced Extended, a popular fork with more aggressive patches. RVX uses mMicroG (also called GMSCore by inotia00) — a different microG fork with the legacy package name com.mgoogle.android.gms. For the music-focused build, check out RVX YT Music Extended.

Upstream microG Project

Led by mar-v-in, this is the source project. ReVanced GmsCore is derived from it. If you want microG for a custom ROM (LineageOS, /e/OS), see the upstream microG documentation instead. This article focuses specifically on ReVanced use.

ReVanced Manager v2: What’s New in 2026

In March 2026, the ReVanced Team released ReVanced Manager v2.0.0, a complete rewrite using Jetpack Compose. As of mid-2026, development builds have progressed significantly. For early access builds, see our ReVanced Manager beta guide.

Key changes for GmsCore users:

• Auto-download APKs: Manager can now fetch compatible YouTube APKs automatically via a plugin system.
• Faster patching: Improved performance on low-end devices.
• Better error reporting: Clearer logs when GmsCore support patch fails.

The Auto-Download System

ReVanced Manager v2 includes a plugin-based APK downloader system:

• APK Downloader Plugin — Fetches compatible YouTube APKs and automatically merges .apkm bundles into a single .apk file.
• Play Store Downloader — Logs into your Google account to download the APK directly. Warning: Due to technical limitations, this only fetches the latest YouTube version, which may not match the suggested patch version. If the latest version is newer than what the patches support, supply an offline APK manually.

Pre-Flight Checklist

Before you start patching, verify every item on this list to avoid common failures:

Prerequisites & Official Downloads

Before you start, you need:

• An Android device running Android 8+ (Android 16 supported).
• ReVanced Manager — the official patching tool. See our ReVanced Manager setup guide or the v2 feature overview.
• ReVanced GmsCore — the companion authentication service.
• A compatible YouTube APK (if not auto-downloaded by Manager). As of February 15, 2026, the latest supported YouTube version is 20.14.43. Always check the ReVanced Patches documentation for the current target version range.

Where to Get ReVanced GmsCore

Step-by-Step: Install ReVanced GmsCore (Non-Root)

This guide assumes you are using ReVanced Manager v2 on a non-rooted device running Android 14, 15, or 16.

Patching Time Benchmarks

Based on community speedrun data:

Default Patches & The Dangerous Patches List

Default Selection for Beginners

The official ReVanced Team recommends a default patch selection for noobs and starters. Unless you have a specific reason and understand the consequences, do NOT disable the default patches. Once you are comfortable, explore advanced customization options.

Rooted Devices: Do You Need ReVanced GmsCore?

If your device is rooted with Magisk, you generally do not need ReVanced GmsCore. On rooted devices, YouTube ReVanced can use the official com.google.android.gms (Google Play Services) directly because root access allows signature spoofing at the system level. Need root help? See our Magisk Manager guide.

However, some users still prefer ReVanced GmsCore on rooted devices to:

• Avoid modifying system-level Google components.
• Maintain a cleaner separation between official and modified apps.
• Use ReVanced alongside banking apps that detect Play Integrity API failures.

ReVanced Extended vs. Official ReVanced

Not sure which mod to pick? Our ReVanced vs. other YouTube mods comparison breaks down all the options.

If you are using ReVanced Extended by inotia00, the setup differs:

ReVanced CLI vs. ReVanced Manager

Most users should use ReVanced Manager. However, power users may prefer the CLI:

If you are new to ReVanced, stick with ReVanced Manager v2.

Troubleshooting ReVanced GmsCore

Even with correct setup, Google’s evolving anti-tampering measures (including Play Integrity API and PoToken validation) can cause issues. Here are verified fixes for 2026. For a broader overview, see our full YouTube Vanced troubleshooting guide.

Sign-In Loop or “Can’t Sign In” Error

If you are seeing persistent login failures, also read our dedicated account login error fix guide for device-specific solutions.

1. Match your versions. Ensure ReVanced Manager, ReVanced Patches, ReVanced GmsCore, and your YouTube base APK are all from the same time period. Mismatched versions are the #1 cause of auth failures.
2. Update GmsCore. In February 2026, Google changed authentication endpoints that broke login. The ReVanced Team merged fixes from upstream microG. The GmsCore support patch now includes a version check that prompts you to update GmsCore if it is outdated. If you prefer not to receive update prompts, you can disable the version check in the patch options, though this is not recommended.
3. Disable Private DNS. Go to Settings > Network > Private DNS and set it to Off temporarily.
4. Disable VPN. Some VPN IP ranges are flagged by Google.
5. Clear data. Clear storage for both ReVanced GmsCore and YouTube ReVanced, then retry sign-in.
6. Exempt from Battery Optimization. Go to Settings > Apps > ReVanced GmsCore > Battery > Unrestricted. Do the same for YouTube ReVanced.
7. Check system time. Incorrect device time breaks TLS certificate validation. Use network-provided time.

“App Not Installed” Error

• Uninstall old Vanced MicroG (com.mgoogle.android.gms) completely.
• Uninstall any previous ReVanced GmsCore builds.
• Ensure you downloaded the correct APK for your CPU architecture (ARM64 for most modern phones).
• Free up storage. You need at least 1 GB free for patching to complete.
• Verify you did not select any patches from the Dangerous Patches List above.

GmsCore Crashing on Android 16

• Update to the latest ReVanced GmsCore release. The ReVanced Team syncs with upstream microG regularly to maintain compatibility with new Android versions.
• If crashes persist, capture an adb logcat during sign-in and report it to the ReVanced GitHub issues page with your device model and patch version.

Not Syncing Subscriptions or History

• Confirm you are signed into the correct account.
• In YouTube ReVanced settings, ensure sync is enabled for history and subscriptions.
• Update both ReVanced GmsCore and the patched YouTube app. Google frequently changes internal APIs that break sync on older patch versions.

Patching Fails or Freezes

Connection drops during patching are a common cause of freezes. See our network connection error guide for connectivity fixes before you retry.

• Low RAM: A documented issue on devices with limited RAM (e.g., 1.48 GB used out of 3.82 GB total) causes Could not decode attr value warnings and patching failure. Close all background apps and ensure at least 2 GB free RAM before patching.
• HyperOS / Xiaomi Bug: On devices like the POCO X8 Pro running HyperOS 3.0.5.0 / Android 16, the built-in APK downloader in ReVanced Manager fails indefinitely. Workaround: Download the target APK manually using your browser, then patch it through Storage instead of using the built-in downloader.

ReVanced Manager Download Failed

• If the auto-downloader fails, manually source the YouTube APK as a single .apk file (not .apks or .xapk).
• Ensure you are selecting a version that matches the current ReVanced Patches target (e.g., 20.14.43).

Privacy & Security: What ReVanced GmsCore Actually Does

ReVanced GmsCore is not an “anti-ban” tool, and it does not “hide your usage from Google servers.” These are myths propagated by outdated guides.

What it actually does:

• Implements a subset of Google Play Services APIs (primarily sign-in and push notifications).
• Reduces data collection compared to full Google Play Services by omitting Ads, Firebase Analytics, DroidGuard, and other heavy components.
• Allows signature spoofing so modified apps can authenticate without root.

What it does NOT do:

• Hide the fact that you are using a modified client from YouTube’s server-side detection.
• Guarantee immunity from account warnings or bans. Google uses behavioral analysis, PoToken validation, and traffic fingerprinting that operate independently of the local GmsCore layer.

Best practices:

• Use a secondary Google account for modified apps if you are risk-averse.
• Keep ReVanced GmsCore updated. Security patches from upstream microG are merged regularly.
• Do not grant unnecessary permissions. ReVanced GmsCore requires minimal permissions for basic authentication.

YouTube ReVanced vs. YouTube Premium

If you can afford YouTube Premium and want to support creators directly, it is the safer, simpler choice. ReVanced is for users who want features like SponsorBlock and dislike counts that Premium does not offer, or who cannot access Premium in their region. You can also explore YouTube Premium mod alternatives for other setups.

Frequently Asked Questions

Conclusion

If you want to use ReVanced GmsCore for YouTube in 2026, you need ReVanced GmsCore — not the dead Vanced MicroG. By using the official ReVanced Manager v2, patching the GmsCore support patch, selecting the default patches for beginners, avoiding dangerous patches, and downloading GmsCore from the official ReVanced GitHub, you can restore personalized features like subscriptions, playlists, and watch history on any non-rooted Android device.

Always verify your sources. Never install pre-patched APKs from third-party sites, as they are a known vector for malware and account compromise. Stick to official release channels only.