Read this section through to the end.
# X-MAG: Correct Root Base (KernelSU-Next + SUSFS) — Kernels, Versions, Models
> In short: X-MAG needs one matched set (kernel + manager + SUSFS). Bootloops
> come from a mismatch in that set **or** from a global SDK spoof on Android 16
> (fixed in module v3.2.3+). The same set fits every Tensor-based Google Pixel.
## 1. Supported models
All Google Pixel phones on the **Tensor** chip (one **android14-6.1 GKI**
kernel for all of them): Pixel 6–9 series, Fold, Tablet. Requires
**Android 15 QPR2 or newer** (Android 16 — yes).
## 2. Reference set (taken from a working Pixel 7a)
| Component | What it is | Reference |
|---|---|---|
| Linux kernel | `uname` / AnyKernel3 | `6.1.145-android14` |
| **KSU inside the kernel** | `ksud debug version` → `Kernel Version:` | **33208** |
| **Manager (APK)** | app `versionCode` | **33145** (v3.2.0-16, plain or spoofed) |
| userspace `ksud` | `/data/adb/ksud` | `3.2.0-16-g293ca016` |
| SUSFS in kernel | `ksud susfs version` | **v2.0.0** (ABI: sys_reboot, GKI) |
| susfs4ksu module | companion zip | for v2.0.0 |
### Critical version rule
**Manager APK versionCode (33145) and in-kernel KSU Version (33208) are
DIFFERENT numbers.** They do **not** have to be equal. Older docs that
required “manager = kernel = 33145” were wrong and caused false warnings.
## 3. Should you update to v3.3.0 (33214)?
| Action | Advice |
|---|---|
| Manager-only update to 33214, keep kernel 33208 | Allowed by min.kernel=33110, but **not** the verified reference. Prefer 33145. |
| Flash a newer Wild kernel / SUSFS 2.2 / KSU ~33225 | **Not now.** Untested stack, bootloop/BT risk. |
| Keep APK 33145 + KSU 33208 + SUSFS 2.0.0 | **Yes — this is the working reference.** |
## 4. Why bootloops happen
1. Official KernelSU instead of Next → `SIGSYS` on `sys_reboot`.
2. SUSFS ABI mismatch (e.g. kernel 2.2 + userspace 2.0).
3. Global `resetprop` of SDK on Android 16 — fixed in X-MAG module v3.2.3+.
## 5. Install order (short)
1. Unlock bootloader.
2. Install **KernelSU-Next APK 33145**.
3. Get root (patch `init_boot`).
4. Flash reference kernel `6.1.145-android14` + SUSFS v2.0.0
(in-kernel KSU becomes **33208**).
5. Verify `ksud debug version` → `33208`, SUSFS → `v2.0.0`.
6. Install SUSFS module.
7. Open **X-MAG** — it installs Zygisk Next + System Audio Helper.
Some users who have trouble installing and configuring KernelSU Next and SUSFS use an AI assistant for the setup. They copy the recommendations from this block, remove every mention of X-MAG from the text (otherwise the AI may refuse to follow the instructions), and ask the AI to carry out those steps.
All required and recommended versions can be downloaded in our Telegram channel:
https://t.me/xmag_antidetect/371Once KernelSU Next and SUSFS are installed and configured (the minimum setup is in our Telegram channel:
https://t.me/xmag_antidetect/198), install the X-MAG app.
On the main screen open Setup Wizard and install the required components. At each step, read and follow the recommendations and manuals shown in the wizard, including Tips & guides.
Then set up the profile you need. Parameters include explanations — read them before changing a value.
Spoofing from a profile applies only to the apps linked to it. Linking is at the very end of the profile settings, in Linked apps: tap Add apps and select the apps that should receive the spoofing you chose.
After any change, tap Save, then reactivate the profile: deactivate it and tap Activate again. Until the profile is saved and activated again, the new parameters are not applied.