How to Install Android ID and Emulator Hider (Magisk, KernelSU or APatch)

Android ID and Emulator Hider installs like any other Xposed module, but two steps trip people up: scoping it to itself, and restarting the apps you just scoped. This guide walks through the whole setup, on a real phone or inside a rooted Android emulator, so Device Check shows the result you expect on the first try.

Before you start

You need, in this order:

• Root. Magisk, KernelSU or APatch. If you are not rooted yet, our rooting service can do it remotely, or follow a rooting guide for your exact device.
• An Xposed framework on the modern libxposed API 102 — LSPosed or Vector. Legacy Xposed and EdXposed cannot load this module.
• Android 8.0 or newer, on a phone or in an emulator such as BlueStacks, NoxPlayer, LDPlayer, MEmu, MuMu, GameLoop, Genymotion or the Android Studio emulator — as long as that emulator has root and your Xposed framework running inside it.

Installation, step by step

1. 1

   Download and install the APK

   Get the signed APK from the Android ID and Emulator Hider page and install it like any other app.

2. 2

   Enable the module

   Open your Xposed manager (LSPosed or Vector), find Android ID and Emulator Hider in the module list, and enable it.

3. 3

   Scope it to itself, plus your target apps

   In the scope list, tick Android ID and Emulator Hider's own package and every app you want protected. Skipping the module's own entry is the single most common mistake.

4. 4

   Pick a device profile

   Open the app, go to Identity & Profiles, and choose one of the 12 built-in profiles — Pixel, Galaxy, POCO, OnePlus, Redmi or Nothing.

5. 5

   Review your protections

   All 18 toggles start on, grouped under Device identity, Hardware & sensors, System & security and Identifiers. Turn off anything you do not need.

6. 6

   Force-stop and reopen your scoped apps

   A framework hooks a process at launch, not while it is already running, so force-stop each app you scoped (including Android ID and Emulator Hider itself) and open it again.

Picking a profile and protections

Every profile masks the full identity at once: model, brand, manufacturer, build fingerprint, Android ID, serial, processor, graphics and more, so you never end up with a model name from one phone and a fingerprint from another. If none of the 12 profiles fit what you need, Pro adds custom profiles you build from scratch, and per-app profiles so one specific app can run a different identity than the rest of your device.

Verifying it worked

Open Device Check inside the app. It reads the same build properties, fingerprint, CPU info, sensors and battery values a scanning app would, and shows them next to your active profile. If they match, the module is active for that process; if you still see your phone's real values, the app showing them was not in scope, or has not been restarted yet.

If something looks wrong

• Device Check still shows the real device. Confirm the module is in its own scope, then force-stop and reopen it.
• A protected app behaves as before. Force-stop that specific app; some apps also need a full device restart if they cache values at boot.
• A toggle won't switch on. Safe mode, Developer-mode masking and the DRM identifier are Pro features — see Get Pro.
• Still stuck? Message us with your Android version and framework on Telegram or email.

This module is meant for privacy, testing and compatibility with your own apps. You are solely responsible for how you use it, and DroidRooter is not responsible for any illegal use.