After installing LSPosed on the Pixel 4 XL, the manager app appears but fails to open when tapped. How should I troubleshoot this?
1. Test Environment
Device model: Google Pixel 4 XL (coral)
Android version: Android 13
CPU architecture: arm64-v8a
Root: Magisk 30.7
LSPosed: 1.9.2
Zygisk: Configured
2. Issue Encountered
I installed LSPosed on my Pixel 4 XL. After installation, the LSPosed manager entry shows up in the app list, yet it will not launch when tapped.
3. Steps Already Taken
Bootloader is unlocked.
Magisk is installed and root access is obtained.
Zygisk components are set up; I also tried Zygisk-Next.
The LSPosed module is flashed via Magisk.
After rebooting, the LSPosed icon is visible in the app list, but tapping it does nothing.
4. Assistance Requested
How can I verify whether the LSPosed module is actually running?
How do I check the runtime status of LSPosed via ADB or Magisk?
What further troubleshooting steps apply when the manager cannot be opened?
I would appreciate guidance from developers with experience installing LSPosed on Pixel 4 XL or Android 13.
First, a conclusion: If the LSPosed icon appears but cannot be opened, this means the module package was installed successfully, yet Zygisk injection failed. The manager relies on the module process to provide services. When the module is not running, the icon is merely a dead shortcut. Therefore, the focus is not on “fixing the icon”, but on “getting LSPosed to load properly”.
Additionally, there are two obvious conflicts in your environment that should be resolved first:
Magisk’s built‑in Zygisk and Zygisk‑Next cannot be enabled at the same time. When both attempt to take over Zygisk injection, they contend with each other. The most common symptom is modules being installed but not working. Choose one only: either disable Zygisk in Magisk settings and keep Zygisk‑Next, or uninstall Zygisk‑Next and use the official Zygisk. The latter is recommended for best compatibility.
LSPosed 1.9.2 is an older version. It has a high injection failure rate on devices running Android 13 with newer security patches. It is recommended to switch to 1.9.3 or newer, or directly use 1.10.x.
Below are the detailed troubleshooting steps.
1. Verify whether the module is actually loaded
# Check whether the module directory exists and has no disable flag adb shell su -c "ls -l /data/adb/modules/" adb shell su -c "cat /data/adb/modules/zygisk_lsposed/module.prop"
The directory name may be `lsposed` or `zygisk_lsposed`, check the actual name. If a file named `disable` exists inside the directory, the module is disabled. Delete it and reboot.
2. Check LSPosed native logs (most direct evidence)
adb shell su -c "ls -l /data/adb/lspd/log" adb shell su -c "tail -n 120 /data/adb/lspd/log/modules.log"
The logs clearly show initialization status, injected processes, and failure reasons. This method is much faster than checking Magisk logs.
3. Capture crashes at the moment of tapping
adb logcat -c # Then tap the icon on the phone, and run this immediately: adb logcat | grep -iE "lsposed|ActivityManager|FATAL"
Focus on errors such as `ActivityNotFound`, `ClassNotFound`, and `UnsatisfiedLinkError`. They correspond to broken shortcuts, version mismatches, and incorrect SO architecture respectively.
4. Bypass the icon and launch the manager directly
adb shell am start -n org.lsposed.manager/.ui.activity.MainActivity
Launched successfully → Only the launcher shortcut was reclaimed by the system (Android 13 enforces stricter shortcut management). Reinstall the manager APK or open it via LSPosed’s persistent notification.
Failed to launch → The module is indeed not running. Go back to steps 1 and 2.
5. Clear manager app data
adb shell pm clear org.lsposed.manager
Clear the data then launch it again. Note that this will erase your scope configurations, and you will need to reselect the hooked scopes. Take screenshots for backup if you have many scopes configured.
6. If the issue persists
Narrow down the problem following this sequence; avoid changing multiple variables at once:
Uninstall Zygisk-Next and use Magisk’s official Zygisk together with a stable LSPosed build;
Disable other Zygisk modules (such as Shamiko) and test them one by one;
Verify that the SELinux state matches your Magisk version. Magisk 30.x has signature or API differences with some older modules;
As a last resort, try switching to a different LSPosed version.
Additional note: Pixel 4 XL uses arm64-v8a. Make sure you flash the universal module package, not a 32-bit-only build.