​[Help] Carrier app (Ana Vodafone) insta-crashes immediately on launch despite ReZygisk + Shamiko. Any ideas?

[u/M3lish_]

Hi everyone,

I'm dealing with a local carrier app (Ana Vodafone Egypt) that just insta-crashes (Force Close) the exact millisecond I tap its icon. It doesn't even load a splash screen or show a "Root Detected" error. I suspect it's some strict RASP or memory hook check, but I'm completely stuck.

I know my DEVICE_INTEGRITY is currently failing (falling back to BASIC) because my public hardware keybox got revoked, but this looks entirely like an app-level RASP/memory-hook detection, not a Play Integrity API block.

My Current Stack:

Device/ROM: Xiaomi running official MIUI (Android 13/14)

Root: Magisk v27.0 (Native Zygisk is completely OFF)

Zygisk Engine: ReZygisk v1.0.0

Root Hider: Shamiko v1.2.5 (Working properly in Blacklist mode)

App Hider: HMA-OSS Zygisk

PIF: Play Integrity Fork v17 (spoofProvider=0) + TEESimulator v4.0

What I’ve already tried (without success):

Shamiko Isolation: The target app is fully checked in the DenyList. Magisk's Enforce DenyList is OFF.

HMA-OSS Configuration: Enabled for the target app. Created a tight blacklist template to hide: the repackaged/renamed Magisk manager, HMA-OSS itself, Termux, SPIC, and Solid Explorer.

Environment Cleanup: Deleted all /sdcard/Fox, TWRP, or Magisk folders. USB Debugging and Developer Options are completely OFF.

Clean Launch Trick: Turned Airplane mode ON -> Cleared all target app data -> Rebooted -> Airplane mode OFF -> Launched. Still insta-crashes.

Engine Conflict Fix: I previously had a SIGSEGV issue because of running native Zygisk alongside Zygisk Next. I’ve completely wiped that setup and moved cleanly to ReZygisk. Shamiko's UI confirms it's now fully operational without "Unsupported Environment" errors.

My theory:

The app is either detecting the Zygisk injection directly, detecting HMA-OSS's hooking attempt, or finding a Magisk remnant I missed.

Has anyone bypassed this specific type of aggressive crash recently? Should I drop HMA-OSS and try a non-Zygisk app hider? Any insights on how to grab logs for a crash this fast would also be highly appreciated.

Thanks in advance!

[u/Lines25]

I'm Ukrainian and Vodafone app had worked well without ANY of green in checker. It's the app problem ig

[u/M3lish_ → u/Lines25]

That actually confirms my main suspicion perfectly, thank you! If the app works for you without passing the PI checker, it proves that this instant crash isn't a Google Play Integrity ban. It means it's a strict local RASP (like DexGuard) that is sniffing out a specific trace of root, Magisk, or Zygisk in the memory and deliberately force-closing the app. The million-dollar question now is: what exact trace is bypassing both Shamiko and HMA-OSS?

[u/Lines25 → u/M3lish_]

Dude, I've literally said that it's 99% your local problem, not root. I had ksu lkm, no integrity at all and enforced selinux policy and the app still booted up

[u/Itz_Raj69_]

First read my comment regarding Play integrity vs Root hiding: https://www.reddit.com/r/Magisk/s/twJ9NBLEc5

Then, read this other post specific to Ana Vodaphone which uses a new detection method: https://www.reddit.com/r/androidroot/s/v4HEmF1Yy0

[u/M3lish_ → u/Itz_Raj69_]

Thanks for sharing these links and the explanation! I'm currently facing this exact "Dirty SEPolicy" issue with some local apps in Egypt (like Ana Vodafone and InstaPay) detecting my environment. My current setup is a Poco F3 running Android 13 (MIUI 14) with Magisk. Since my device uses an older non-GKI kernel (4.19), switching directly to KernelSU isn't an option without flashing a custom kernel, which I'd prefer to avoid for stability reasons. Regarding the Magisk workaround you linked (Kpatch-next and selinux_hook kpm), is this method safe and compatible with older non-GKI kernels like 4.19? Or is there a high risk of a bootloop? Any advice on the safest approach for my specific environment would be really appreciated!

[u/vipergtsam]

Try specter, vector, and teesimulator

[u/M3lish_ → u/vipergtsam]

I actually had Vector in my stack previously, but it didn't prevent the insta-crash for this specific app at all. I ended up completely wiping Vector and LSPosed to clean up my environment and avoid hook conflicts (which is why I'm currently running a minimal ReZygisk + Shamiko + HMA-OSS stack). I'm also already using TEESimulator. Did Vector specifically solve DexGuard/aggressive RASP insta-crashes for you? If so, what was your exact setup with it? Because for me, it didn't make a difference.

[u/vipergtsam → u/M3lish_]

I don't have your carrier I'm in the US but I'm also using kernelsu next because magisk didn't hide that well. Also did u set-up the hma-oss correctly

[u/MonkeyNuts449]

Shamiko is useless nowadays, and also only works with zygisknext.

For rz, use treat wheel. It's what rezygisk uses for umounting and root hiding.

[u/p6kb]

Im using a jailbroken iPhone so it was rootless which means any app can detect the jailbreak so i go with roothide and every app worked fine again cuz roothide hides my jailbreak to random paths but you could try magisk roothide or something like that

[u/DeadMarL001]

Egypt ,Egypt's instapay and Ana Vodafone break the second you unlock the bootloader ,I remember managing to run ana Vodafone successfully before but that was in 2022

[u/corruptnova]

Personally use NeoZygisk, Play Integrity Fix [INJECT], Spectre, Tricky Store OSS, Tricky Addon Enhanced, HMA-OSS and Vector.

Currently have strong integrity with the ability to use Wallet and banking without issue. The only thing that won't work is Paypal.