No dependable universal list of LSPosed modules works on “temporary root.” The phrase does not name the root implementation, and the official KernelSU and LSPosed documentation does not certify arbitrary temporary-root setups. What you can do is check a specific module against a specific setup. This guide explains the documented KernelSU route, the requirements that decide compatibility, and how to test a module without assuming it works.
Why there is no universal module list
A list of “modules that work on temporary root” would need to name the root method, the device, the Android release, and the kernel. Temporary root is not one standard. Each implementation can grant root in a different way, keep it alive for a different length of time, and mount or hook system components differently. A module that runs on one of these setups may fail on another, and a module’s own page rarely says whether it has been tested with a temporary-root method at all.
As an Amazon Associate I earn from qualifying purchases.
Module pages and project documentation can still tell you what each module needs. Use those requirements as a checklist rather than treating any module as guaranteed to work in a temporary-root environment.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
What to check before installing anything
Gather these details about your setup first:
- Root method: the exact tool or implementation that provides temporary root, not just the phrase itself.
- Root manager: whether you are on KernelSU, Magisk, or another manager, since each module page may name a different one.
- Device model and Android version: the model matters because kernels and vendor builds differ even within the same Android release.
- Kernel version and architecture: KernelSU’s documented support depends on these, as described below.
- Session persistence: whether root and the LSPosed framework remain active for as long as the target apps run.
If you cannot identify the root method, you cannot verify compatibility for any module. Label the result as unverified instead of inferring it from general KernelSU or LSPosed support.
#1 Best Overall
- YOUR CONTENT, SUPER SMOOTH: The ultra-clear 6.7" FHD+ Super AMOLED display of Galaxy A17 5G helps bring your content to life, whether you're scrolling through recipes or video chatting with loved ones.¹
- LIVE FAST. CHARGE FASTER: Focus more on the moment and less on your battery percentage with Galaxy A17 5G. Super Fast Charging powers up your battery so you can get back to life sooner.²
- MEMORIES MADE PICTURE PERFECT: Capture every angle in stunning clarity, from wide family photos to close-ups of friends, with the triple-lens camera on Galaxy A17 5G.
- NEED MORE STORAGE? WE HAVE YOU COVERED: With an improved 2TB of expandable storage, Galaxy A17 5G makes it easy to keep cherished photos, videos and important files readily accessible whenever you need them.³
- BUILT TO LAST: With an improved IP54 rating, Galaxy A17 5G is even more durable than before.⁴ It’s built to resist splashes and dust and comes with a stronger yet slimmer Gorilla Glass Victus front and Glass Fiber Reinforced Polymer back.
The documented KernelSU route to LSPosed
KernelSU does not include Zygisk itself. The official KernelSU FAQ says LSPosed can run on KernelSU through ZygiskNext, and it states the point directly: “Yes, you can use LSPosed (or other modern Xposed derivatives) with ZygiskNext.” The FAQ text is in English, although the page you find may be a localized version.
KernelSU’s documentation also sets kernel and architecture requirements. It officially supports GKI 2.0 devices running kernel 5.10 or newer. Older kernels may need manual integration. KernelSU lists arm64-v8a and x86_64 as supported architectures. Android version alone does not settle compatibility, so check the kernel on your actual device.
Rank #2
- Carrier: This phone is locked to Tracfone, which means this device can only be used on the Tracfone wireless network. Tracfone plan required, activating is easy, just 3 steps.
- DISPLAY: Immersive viewing on a 6.7-inch super-bright 120Hz display with powerful stereo speakers and Bass Boost for cinematic entertainment.
- CAMERA SYSTEM: Advanced 50MP Quad Pixel camera captures sharp, detailed photos and videos in any lighting condition
- PERFORMANCE: Lightning-fast 5G connectivity paired with a powerful processor and RAM Boost for smooth multitasking.
- BATTERY LIFE: Long-lasting 5000mAh battery with TurboPower charging technology delivers hours of power in minutes.
Module requirements by type
Modules differ in what they touch, and that difference decides what you need. Sort each module into one of the following groups before judging compatibility.
App-scoped LSPosed hooks
Many LSPosed modules only hook the apps you select. These depend on the LSPosed framework being active and on root access for the session in which the target apps run. Compatibility here turns on whether the framework survives in your root setup, not on KernelSU’s file mounting.
Rank #3
- YOUR CONTENT, SUPER SMOOTH: The ultra-clear 6.7" FHD+ Super AMOLED display of Galaxy A17 5G helps bring your content to life, whether you're scrolling through recipes or video chatting with loved ones.¹
- LIVE FAST. CHARGE FASTER: Focus more on the moment and less on your battery percentage with Galaxy A17 5G. Super Fast Charging powers up your battery so you can get back to life sooner.²
- MEMORIES MADE PICTURE PERFECT: Capture every angle in stunning clarity, from wide family photos to close-ups of friends, with the triple-lens camera on Galaxy A17 5G.
- NEED MORE STORAGE? WE HAVE YOU COVERED: With an improved 2TB of expandable storage, Galaxy A17 5G makes it easy to keep cherished photos, videos and important files readily accessible whenever you need them.³
- BUILT TO LAST: With an improved IP54 rating, Galaxy A17 5G is even more durable than before.⁴ It’s built to resist splashes and dust and comes with a stronger yet slimmer Gorilla Glass Victus front and Glass Fiber Reinforced Polymer back.
KernelSU modules that change system files
KernelSU’s documentation says that a module changing /system needs a metamodule to supply mounting infrastructure. meta-overlayfs is the example the documentation names. Scripts, sepolicy rules, and system.prop changes can work without a metamodule. If a module that edits system files does nothing after installation, a missing metamodule is one of the first things to check.
Modules that rely on persistent boot scripts
A module that expects a boot script or a setting to persist needs root that survives reboots. If your temporary root does not persist, a module of this kind may appear to work until the next restart and then stop. Treat that behavior as a limitation of the root method, not a module bug.
Rank #4
- PRIVACY DISPLAY: Automatically hide your screen from those beside you. The built-in privacy display can be preset¹ to turn on when receiving notifications, typing passwords, or using specific apps
- TYPE IT IN. TRANSFORM IT FAST: Enhance any shot in seconds on your smartphone by using Photo Assist² with Galaxy AI.³ Add objects, restore details, or apply new styles by simply typing or tapping
- NIGHTS, CAPTURED CLEARLY: From gigs to city lights, record and capture moments after dark with clarity using Nightography so your photos and videos stay crisp and clear on your Samsung Galaxy
- MAKE IT. EDIT IT. SHARE IT: Turn everyday moments into something personal with creative tools built right into your mobile phone, whether it’s a special contact photo, custom wallpaper, an invitation or more⁴
- HELP THAT KEEPS UP: Stay in the moment while Now Nudge with Galaxy AI helps you respond faster and stay organized with smart suggestions⁵ that appear exactly when you need them on your phone
Magisk and KernelSU conflicts
KernelSU’s FAQ warns that its module mounting conflicts with Magisk’s magic mount when KernelSU modules are enabled. If your setup mixes both systems, decide which one controls mounting before you install module files, and do not expect both to handle system changes at the same time.
Reading a module page: a worked example
YumyHook is a current example of how a module page states its requirements. Its repository page describes an LSPosed module built on the libxposed API. It requires root, lists KernelSU as one possible root manager, requires LSPosed with libxposed API 100 or newer (the page recommends API 102), and lists Android 8.0 or newer. These requirements describe the module. They do not confirm that it works with any particular temporary-root implementation.
Best Value
- Carrier: This phone is locked to Tracfone, which means this device can only be used on the Tracfone wireless network. Activating is easy, just 3 steps.
- ACTIVATION Promotion: Includes 1500 min, 1500 texts & 1500 MB Data + add more as you need it
- CAMERA SYSTEM: 50MP Quad Pixel camera. Capture sharper, more vibrant photos day or night with 4x the light sensitivity.
- PERFORMANCE: Blazing-fast Qualcomm performance. Get the speed you need for great entertainment with a Snapdragon 680 processor and 4GB of RAM.
- 64GB built-in storage. Get plenty of room for photos, movies, songs, and apps. Made for US
Its listed installation steps are:
- Install the module APK.
- Grant superuser access to the module in your root manager.
- Enable the module in LSPosed.
- Choose the target apps the module should hook.
- Force-stop each target app and reopen it to confirm the hook is active.
Use the same steps for any LSPosed module, substituting its own requirements and target list. The force-stop and reopen step is the practical check: if the hook does not take effect, the problem is usually a missing framework, an unselected target, or a root session that did not hold.
Troubleshooting when a module does not work
- Module shows no effect in the target app: confirm the module is enabled in LSPosed, the target app is selected, and the app was force-stopped and reopened.
- LSPosed is not running at all: confirm the framework is installed for your setup and that the module’s libxposed API and Android version requirements are met.
- System-file module has no effect: check that the required metamodule is installed and that Magisk magic mount is not competing for the same mounts.
- Module works until reboot: the root method may not persist across restarts. Use the module only where that limitation is acceptable.
- Kernel or architecture is unclear: confirm the kernel version and architecture before troubleshooting further, because KernelSU’s documented support depends on them.
What remains unverified
The available documentation does not establish compatibility for any named module on an unspecified temporary-root implementation. Before relying on a specific module, you need the root method, device model, Android version, kernel version and architecture, and the module names. With those details, you can check each module’s stated requirements and test one module at a time.
KernelSU’s documented compatibility and the LSPosed module requirements listed above are the best current references. Check them against your exact setup rather than assuming that broad support covers your case.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minuteQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
