Tutorial [ULTIMATE GUIDE] MuMu 12 (Maintained CN Version) Complete Setup: Root + LSPosed + HMAL + CorePatch + Performance (up to 240 FPS) + LIAPP Bypass

Still detect LIAPP
Yes because they made more changes to liapp. Only native real devices can bypass it and most people use kernel SU and other tools only available on real devices. This WAS just an exploitation on the emulator that existed but emulators were always harder and more limited on how we can bypass root and other emulator detections such as play integrity
 
But even then this is still as of today the max on how much u can hide an emulator so it's still a good guide but liapp u can clearly see literally no one is modding liapp games on emulator. And even so it would have to be somehow bypassing it through hooking the app runtime in some way if possible at all
 
it works but some games still detect it, it says LIAPP ALERT access denied *random numbers*-MUMU

Still detect LIAPP
Additionally, I have investigated and it also has to do with the vendor su mumu injects in
Apparently, mumu injects vendor su strangely even after root is turned off, thus I will need to apply several patches. A summary is provided below of what I have fixed so far and some context but I can and will try to get it to work bc I truly think mumu12 is way more efficient for low end and even high end pcs.

  • MuMu’s incorrectly unconditional mu_bak root daemon is disabled.
  • Its kernel interception of /system/bin/su was neutralized.
  • The underlying vendor su that reappeared inside hidden-app namespaces was removed.
  • Kitsune’s /sbin/su and /system/bin/su both provide u:r:magisk:s0 root.
  • MuMu’s mu_bak -c id fails, while magiskd remains running.
  • MagiskHide was verified: the hidden application sees no Magisk or su artifacts.
  • This survived three complete MuMu cold boots with vendor root off.
 
Important Notice

Unfortunately, this program will almost certainly trigger antivirus detections because it performs invasive and version-sensitive modifications to both the MuMu host and guest environment.

Why these modifications are required:

1. The built-in Root toggle is incomplete


On the tested guest system, disabling Root only changed the following properties:

Code:
persist.nemu.root_state
nemu_debug

It also restarted ADB. However, the init declaration for the following daemon remained unconditional:

Code:
/system/xbin/mu_bak --daemon

As a result, the command below could still obtain root access:

Code:
mu_bak -c id

It returned:

Code:
uid=0

This remained possible even after the MuMu interface reported that Root was disabled and after running:

Code:
adb unroot

2. The MuMu kernel intercepts standard su paths

The MuMu guest kernel contains literal checks for:

Code:
/system/bin/su
/system/xbin/su

It also contains the following diagnostic string:

Code:
hit do_open_execat %s, hide it

Because of this behavior, the kernel may hide or reject Kitsune’s legitimate
Code:
su
path before Android userspace is able to process it.

3. MuMu includes a vendor su binary in the base system

Kitsune normally overlays its own binary at:

Code:
/system/bin/su

When MagiskHide removes Kitsune-related mounts from a hidden application’s mount namespace, MuMu’s original vendor
Code:
su
binary may become visible underneath.

This means that the vendor binary can appear precisely inside applications where no
Code:
su
binary should be visible.

Antivirus Warning

Antivirus protection may need to be temporarily disabled while running the program because the required modifications can resemble malicious behavior.

Only proceed after reviewing and verifying the source code yourself. Do not run builds obtained from unofficial mirrors or unknown third parties.

The complete source code will be publicly available through the GitHub link attached to this post and included in the YouTube video description.

The project is not fully released yet.

I will update this post when the complete version is available.
 
Back
Top Bottom