How to Install DRVCAM on Rooted Android (Magisk, KernelSU or APatch)

This guide walks you from a freshly rooted phone to your first app showing a DRVCAM feed, with real screenshots from two different setups: a Magisk phone and a KernelSU phone. Both end up at the exact same place — a Zygisk-based Xposed framework (Vector) with DRVCAM loaded into it — the only difference is how you get Zygisk itself running. It takes about 15 minutes if your phone is already rooted. When you are set up, the complete DRVCAM user manual covers every screen and control with screenshots. If your phone is not rooted yet, start with our rooting guides or let our remote rooting service handle it.

Step 1: Check your Android version and pick your file

Open Settings → About phone and note the Android version. DRVCAM supports Android 9 to 17 with a single file, so there is nothing to match. You only choose between two files:

• Phone or tablet (arm64): the phone file, for every version from Android 9 to 17.
• Emulator on a PC (x86_64): the emulator file, for every version from Android 9 to 17.

An Android version older than 9 cannot run DRVCAM.

Step 2: Make sure root is working

DRVCAM works with the three popular root managers: Magisk, KernelSU and APatch. Open your root manager and confirm it reports root as active.

Step 3: Get Zygisk running

Vector (the Xposed framework DRVCAM uses) runs on Zygisk. How you turn Zygisk on depends on your root manager — pick your path below. We rebuilt both of these from scratch on real phones for this guide: we removed Vector and Zygisk entirely first, then reinstalled everything step by step so every screenshot below is the real UI, not a mockup.

Magisk: use the built-in Zygisk toggle

Current Magisk versions (31.x and newer) still ship a native Zygisk switch. On our Pixel test phone, Magisk showed Zygisk: Disabled after we removed the old modules:

Open Magisk → Settings, scroll to the Magisk section, and turn on Zygisk:

Reboot. When the phone comes back, Home shows Zygisk: Enabled:

KernelSU or APatch: install a Zygisk implementation module

KernelSU and APatch do not ship their own Zygisk, so you install one as a module first — this is normal, not a workaround. Zygisk Next is the current standard implementation and is what we used:

1. Download the latest Zygisk Next release zip from the link above (the .zip asset, not the source code).
2. In your root manager's app, open the Modules (or Superuser → Modules) tab and tap the + / Install from storage button.
3. Pick the Zygisk Next zip you downloaded and confirm the install.
4. Reboot.

After the reboot, open your root manager app and check its Modules tab. Here is our KernelSU phone right after installing both Zygisk Next and Vector this way, both showing enabled with a one-tap toggle each:

Step 4: Install Vector, the Xposed framework

With Zygisk running (built-in or via Zygisk Next), install Vector — the Zygisk-based, LSPosed-family framework DRVCAM is built and tested against. Download the latest Release.zip asset from the link above, then install it as a module the same way: your root manager's Modules → Install from storage, pick the Vector zip, then reboot.

After the reboot, open your root manager's Modules tab again. You should see Vector listed and enabled — as it is here on our Magisk test phone, installed and active with one tap of the toggle (the KernelSU screenshot above shows the same end state, reached the KernelSU way):

DRVCAM talks to Vector for you afterwards, so there is no need to tick scopes by hand.

Step 5: Download and install DRVCAM

Open the download window on the DRVCAM page. Choose phone or emulator, and it recommends the right file. If Android asks, allow installs from your browser or file manager.

Step 6: Open DRVCAM and grant root

Open DRVCAM. Your root manager will ask whether to grant it root access. Tap Grant straight away. Some root managers deny the request automatically after a few seconds. If that happens, open your root manager, allow DRVCAM in its superuser list, then return to DRVCAM and tap Check.

Step 7: Sign in

Tap Try Free to use the free version, which needs no account, or sign in with your DRVCAM account if you have a plan. To get a plan, use the contact buttons on the sign-in screen or see pricing. Once you are signed in and have valid offline authorization, temporary network loss does not immediately stop the app.

Step 8: Check the environment

Once Vector is active and DRVCAM has root, Home itself shows your status — no separate check screen needed. You want Root: Ready and Module: Active, both lit up, before you try to enable a target:

If you plan to use the floating controller, also allow Display over other apps when DRVCAM asks.

Step 9: Your first virtual camera feed

1. Open Library and tap Import image (or Import MP4 on a paid plan). You can pick several files at once. The free version works with images only.
2. Tap Use on the file you want. It becomes your Main source — you will see it appear in the Live Source preview on Home.
3. Under Target App, tap More, tick the apps that should get the feed, and tap Done.
4. Tap Enable.
5. Force-close the target app first if it was already running, then open it fresh and go to its camera. You should see your media.

Here it is actually working — the same photo showing up live inside a third-party camera app's own viewfinder, in place of the real camera:

Camera feed not showing? See virtual camera not working on Android: a 10-minute fix guide.

Troubleshooting

"Root not granted"

Open your root manager, allow DRVCAM, return to DRVCAM and tap Check.

Module shows as off

Confirm Vector is active in your root manager's Modules tab, then use Settings → Recheck Module & Scopes in DRVCAM. A reboot after installing Zygisk Next or Vector is required — skipping it is the most common reason this shows Off.

The target app still shows the real camera

Close the target app completely (swipe it away or force-stop it) and open it again. Also check that Camera Source on Home is set to Virtual.

A manufacturer camera app does not work

Some built-in camera apps (including Google Camera on Pixel phones) use proprietary, multi-camera session modes that DRVCAM deliberately refuses rather than risk a crash — this is expected, not a bug. Try another camera app; open-source camera apps like Open Camera are a good first choice, and that is exactly what we used for the working screenshot above.

DRVCAM is a tool. You are solely responsible for how you use it, and DroidRooter is not responsible for any illegal use.