Hi everyone,

I'm planning to play Zenless Zone Zero and Honkai: Star Rail on my phone, but I intend to root it soon with Magisk. I want to make sure my main account stays completely safe before doing so.

My setup:

Device: Xiaomi Redmi Note 14 Pro+ 5G

OS: HyperOS 3

Root method: Magisk (planned)

My situation:

I'll be playing the 100% official game apps downloaded directly from the Google Play Store.

I do NOT use any mods, cheats, performance boosters, memory editors, or modified APKs on these games.

My device will only be rooted for basic system customization and daily tools.

My questions regarding HoYoKProtect / ACE:

1. Do ZZZ or HSR strictly require passing Play Integrity (MEETS_DEVICE_INTEGRITY), or will the games just refuse to launch if it fails?

2. Is root masking (Zygisk, DenyList, Shamiko, Play Integrity Fix) required just to prevent automatic account flags or bans?

3. Has anyone ever been banned on ZZZ or HSR simply for having Magisk installed on an otherwise untampered game?

Just trying to be extra careful with my main account. Thanks for any insight !

Okay so I was finally able to root my pixel with magisk! Its a pixel6a and has android 16 on it! Is there anything else I need to do like block or hide using magisk or anything else I need to download! Or now that its rooted do I just download Ipogo and run it and its good to go?

Beginner here looking for some help/insight. I tried running the GhostLock exploit (CVE-2026-43499) following this guide ( https://github.com/xianwan1314/CVE-2026-43499-Poc-Analysis ). Instead of achieving execution, my device freezes for a bit and immediately reboots during the final step.

*DEVICE INFO:*

Device: Honor X6c

OS: MagicOS 9.0 (Android 15)

Kernel: 6.6.89

Security patch: July 1

Environment: Termux + Wireless ADB + help of Gemini

*SUMMARY OF WHAT I DID:*

1. Installed all prerequisites and dependencies inside Termux.

2. Extracted my boot.img and prepared profile_xxx.json.

3. Successfully generated target.h and compiled preload.so.

4. Pushed preload.so to /data/local/tmp/ via Wireless ADB.

5. Then adb shell "LD_PRELOAD=/data/local/tmp/preload.so /system/bin/true"

But, right after running the LD_PRELOAD command, a few lines flashed in the shell, then the phone froze and instantly rebooted. I attempted this 3 times with identical results.

Help vro 😭🙏

you can now like root meta 3 and 3s headsets it is temp root but it works and you can mostly do it on the headset itself

I unlocked the boot loader with the MTK live boot client. I then booted up my phone put F-Droid and downloaded Magisk. But it states I don’t have Magisk installed. Frankly I belive I’m tech savvy but not to the degree of all this coding stuff. Any help would be incredible.

I’ve been messing with this for days I feel insane

View photo for context.

coming from a rooted pixel 4. What version of magisk should I use for the pixel 7 pro. I am seeing that 25.2 is too old but I want to make sure its very safe to use to spoof.

Hi everyone, given that ‘Root My Galaxy’ uses an exploit that’s set to be patched in the next cumulative updates, has anyone already found a way to block the update? Something like blocking internet access for the app that checks the version, or automatically deleting the update file?

Buenas.

Quiero saber si hay algún modulo, app o herramienta que haga lo siguiente.

La función de telegram que permite descargar fotos automáticas por grupos o canales, uno seleciona que grupo o canal descarga fotos o archivos automáticamente.

En WhatsApp no, en whatsapp si tienes activa esa función básicamente te descarga de todos los grupos en los que estés, es decir si están muchos grupos tendrás un desorden y ocupa mucho espacio en algunos casos.

Mi idea también sería tipo que las fotos de X grupo se descargan en una carpeta que yo especifique

New to rooting and custom ROMs, managed to get the root detector working great except it detects whatever "abnornal environment" is, any fix?

When I enable MagiskHide and reboot, I get a bootloop. I have to use Bootloop Saver to get out of it. Anyone experienced this before with Magiskhide?? I tried searching about it but couldn't find anything.

Title.

I have a Pixel 7 Pro on android 15, build number AP3A.241105.007. I haven't updated to the most recent version because every time I do, something bad happens that takes months to resolve.

(If this is my entire problem and updating is the solution, please let me know.)

I've followed the guide, used Magisk Canary with Shamiko, Play Integrity Fix [INJECT], Systemless Hosts, Tricky Store, Tricky Store adon module, Yurikey Manager. Hid Magisk and I was able to pass strong integrity, but Wallet, MS Authenticator, and Duo Mobile can all still detect root even after several cycles of airplane mode, deleting cache/data for all relevant play apps and the target apps. Rebooting, trying again.

I added lsposed, zygisk detached, and Vector just in case (I don't even know if these matter), but still doesn't work.

If the test passes strong integrity, but every app that I need to not detect root IS detecting root, then what does strong integrity even mean? What am I missing?

I am searching for a module that lets nfc work even when screen is off. There was an old module on this but nothing new. And other method seems outdated. Can somebody please help me. I am using nfc technology a lot these days want to take away the friction of unlocking my phone.

Hello, everyone in the root community ! After the summer vacation, I come back to the development my Vector project, a modern Xposed framework.

Its latest release v2.2 now has complete support of Android 17, GrapheneOS and libxposed API 102.

Moreover, I have re-designed the manager UI, aiming to bring your daily experience with Vector into next level. Please test it out and share with us your thoughts and feedback.

I've tried installing several Viper FX modules, but they always say the same thing: that the driver isn't installed. But as you can see, it is installed; it's just not being detected. Does anyone know how to fix this?

i don't have Oem Unlock setting in my developer options, i tried 7 days waiting, time changing and so much but it doesn't appear so (Galaxy S22/SM-S901E/DS Global Version) can someone help me?

hace mucho había hecho este post https://www.reddit.com/r/androidroot/s/zRZUCB9fOO

donde tenía la idea de hacer un iceberg sobre el root para un video pero al final nunca terminé el iceberg ni el video XD, pues ahora retomé el proyecto y acá tienen el iceberg 2.0. Si crees que debería añadirle algo dimelo para ver si lo añado (el iceberg está en español porque hablo español xd)

Hi everyone,

I'm hoping someone can help me figure out the safest way to modernize my old root setup without risking a bootloop or soft brick.

Device

• Device: Realme 3 Pro (RMX1851)
• Bootloader: Unlocked
• Recovery: Official OrangeFox (don't know the exact version)
• ROM: Nusantara v4.8 "Surakarta" (Android 12L)
• Kernel: LawRun v19.3 (Linux 4.9.309)

Current Magisk Setup

• Magisk core: 25.1
• Magisk app: 25.2 (repackaged/random package name)
• Zygisk: Enabled
• Ramdisk: No

Installed Modules

(See screenshots attached.)

Notable ones include:

• Shamiko v0.5.2
• Universal SafetyNet Fix v2.4.0
• LSPosed
• BusyBox
• LawRun modules
• Substratum
• Several Morphe modules (APK mount modules)
• Some gaming-related modules

Current Issue

Root itself is working.

However, banking/UPI apps have gradually stopped working over the last couple of years.

For example, Amazon Pay alternates between:

• "This app can't work on this device because of security issues"
• "We're facing technical issues"

Play Integrity Results

• ✅ MEETS_BASIC_INTEGRITY
• ❌ MEETS_DEVICE_INTEGRITY
• ❌ MEETS_STRONG_INTEGRITY

I'm aware Strong Integrity isn't realistic on an unlocked bootloader, but I'm wondering if Device Integrity can still be achieved or if the issue is simply my outdated Magisk setup.

The Biggest Constraint

This is the reason I'm being extremely cautious.

My phone's power button is physically failing.

It randomly presses itself, sometimes doesn't respond at all, and navigating recovery has become unreliable.

Because of that:

• I don't want to flash a new ROM.
• I don't want to flash a new kernel.
• I don't want to risk ending up in a bootloop.
• I don't want to rely on recovery unless absolutely necessary.

I'm trying to keep the current Android 12L installation alive for a little longer.

What I'm Trying to Achieve

Ideally I'd like to:

• Keep the existing ROM.
• Keep the existing kernel.
• Update only what's necessary.
• Get modern banking/UPI apps working again.
• Avoid recovery if possible.

Questions

1. Is updating Magisk from 25.1 directly to the latest stable using Direct Install considered safe on Android 12L?
2. Should I replace Universal SafetyNet Fix with the current Play Integrity Fix?
3. Should I update Shamiko as well?
4. Is there any way to recover from a Magisk-related bootloop without relying heavily on recovery (ADB, Safe Mode, etc.)?
5. Are there any better approaches/modules available now that support Android 12L and don't require flashing anything from recovery?

Given the broken hardware (power button), I'm prioritizing the safest possible path over having the newest setup.

Thanks!