Pros of Magisk

• More established and widely used in the Android rooting community
• Extensive module ecosystem for customization and feature enhancement
• User-friendly GUI for managing root access and modules

Cons of Magisk

• Requires modification of boot image, potentially triggering SafetyNet checks
• May be detected by some banking apps and other security-sensitive applications
• More complex installation process for some devices

Code Comparison

Magisk (init.cpp):

static int magisk_main(int argc, char *argv[]) {
    if (argc > 1 && strcmp(argv[1], "-c") == 0) {
        printf("%s\n", MAGISK_VERSION ":MAGISK");
        return 0;
    }
    // ... (additional code)
}

KernelSU (ksu.c):

int ksu_main(int argc, char **argv) {
    if (argc == 2 && strcmp(argv[1], "-v") == 0) {
        fprintf(stdout, "%s\n", ksu_get_version());
        return 0;
    }
    // ... (additional code)
}

Both projects implement root access management for Android devices, but KernelSU focuses on kernel-level modifications, potentially offering better compatibility with some security measures. However, Magisk provides a more comprehensive set of features and a larger community support base.

Pros of LSPosed

• More established project with a larger user base and community support
• Offers a wider range of customization options and module support
• Provides a user-friendly GUI for managing modules and settings

Cons of LSPosed

• Requires a custom recovery (e.g., TWRP) for installation
• May have compatibility issues with some devices or Android versions
• Potentially higher impact on system performance due to its extensive features

Code Comparison

LSPosed:

public class XposedBridge {
    private static final String TAG = "LSPosed";
    private static final CopyOnWriteSortedSet<XC_LoadPackage> sLoadedPackageCallbacks = new CopyOnWriteSortedSet<>();
    // ...
}

KernelSU:

int ksu_handle_execve(struct pt_regs *regs) {
    u64 ret = 0;
    struct filename *filename;
    // ...
}

LSPosed uses Java and focuses on app-level modifications, while KernelSU is written in C and operates at the kernel level, providing root access and system-level modifications.

Pros of Shizuku

• Does not require kernel modifications, making it more compatible with a wider range of devices
• Provides a more user-friendly interface for managing app permissions
• Offers better stability and less risk of system-wide issues

Cons of Shizuku

• Requires ADB or root access to set up initially
• May have slightly higher battery consumption due to running as a separate service
• Limited to specific API functions, unlike KernelSU's full root access

Code Comparison

Shizuku (Java):

@RequiresPermission(Manifest.permission.MANAGE_EXTERNAL_STORAGE)
public static boolean setExternalStorageManager(Context context, boolean allowed) {
    return StorageManager.from(context).setExternalStorageManager(allowed);
}

KernelSU (C):

int su_daemon_main(int argc, char *argv[]) {
    // Initialize KernelSU
    ksu_kernel_init();
    // Start the daemon
    return daemon_main(argc, argv);
}

Both projects aim to provide elevated privileges on Android devices, but they approach the task differently. Shizuku focuses on a more controlled and user-friendly method, while KernelSU offers deeper system integration at the kernel level.

Pros of MagiskHidePropsConf

• More user-friendly and easier to configure for non-technical users
• Offers a wider range of device fingerprinting options
• Integrates seamlessly with existing Magisk ecosystem

Cons of MagiskHidePropsConf

• Requires Magisk to be installed, limiting compatibility with some devices
• May not provide as deep-level system modifications as KernelSU
• Potentially less secure due to reliance on userspace modifications

Code Comparison

MagiskHidePropsConf:

MODDIR=${0%/*}
MAGISKTMP="$(magisk --path)"
MIRROR="$MAGISKTMP/.magisk/mirror"

KernelSU:

int ksu_execve(const char *filename, char *const argv[], char *const envp[])
{
    return ksu_handle_execve(filename, argv, envp, NULL);
}

The code snippets highlight the different approaches:

• MagiskHidePropsConf uses shell scripts to interact with Magisk's environment
• KernelSU operates at the kernel level, modifying system calls directly

Both projects aim to enhance Android customization, but KernelSU provides lower-level modifications, while MagiskHidePropsConf offers more user-friendly options within the Magisk framework. The choice between them depends on the user's technical expertise and specific requirements for system modification.