Ensure you have a mechanism to disable modules via custom recovery if your device gets stuck on the boot animation.
Why? Because thermal-engine and power HAL initialize in between. If you set max freq too early, those services overwrite it. Wait 15 seconds. Let the system lie down first, then whisper the truth.
Thus, most "overclock Magisk modules" are actually or removing thermal limits — not true overclocking. overclocking magisk module better
Disables modules if they cause your phone to crash during boot. 💡 Key Concepts to Understand True Overclocking vs. Performance Boosting:
rakarmp/CPULock-Magisk: Increase your cpu speed by locking it down Ensure you have a mechanism to disable modules
A Magisk module cannot force a processor to run at a frequency that the underlying kernel does not support. If your stock kernel caps the CPU at 2.8 GHz, a Magisk module cannot magically make it run at 3.2 GHz unless it modifies the kernel parameters directly. Therefore, many "overclocking" modules are actually that maximize the time your processor spends at its highest existing factory clock speed. Thermal Throttling Realities
Save as module/service.sh and make executable. Use when you want settings applied after boot completion and can add logging. If you set max freq too early, those services overwrite it
To understand the limitations of these modules, one must first understand how Android hardware functions. Unlike desktop computers, where BIOS settings allow granular control over voltage and frequency, Android devices are tightly locked down by manufacturers. The frequency tables for the CPU and GPU are hardcoded into the kernel. Consequently, most Magisk modules that claim to "overclock" are not actually overriding hardware firmware. Instead, they are primarily manipulating kernel governors—the scripts that determine how fast the processor ramps up or down. A "better" module, therefore, is rarely one that breaks hardware limits, but rather one that optimizes the existing frequency tables by keeping the device in higher performance states more often.
But a directly (no zImage replacement). So how do "overclocking Magisk modules" work?