When you run mtk-su , it executes in sequential phases. If a phase fails, it halts the program and throws an explicit error message (e.g., Step 1, Step 3, Step 4). 1. Security Patches and Fixed Exploits
Run cat /proc/sys/kernel/security/lockdown in an ADB shell. If it returns integrity or confidentiality , the kernel is in lockdown mode, which explicitly prevents runtime kernel exploits like mtk-su .
If you continue to see "Step 3" or "Step 4" failures after verifying these steps, the exploit is likely on your current firmware. In these cases, your only option is typically a hardware-based "brick-and-short" method (if available for your model) to unlock the bootloader via XDA Developers guides .
Re-open the app, tap the option menu, and verify if a prompt asks to download or update internal assets.
mtk-su modifies kernel memory directly. If you continue to force it after failures, there is a small risk of causing a kernel panic, which will force the device to reboot. It will not permanently brick the device, but exercise caution. mtk-su failed critical init step 3
The "mtk-su failed critical init step 3" error is a common obstacle for those attempting to root MediaTek devices using the CVE-2020-0069 exploit. Understanding the root cause—whether it's the security patch level, SELinux enforcement, architecture mismatch, or corrupted binaries—is essential to resolving it.
In this guide, we will break down what “critical init step 3” actually means, why it fails, and what you can do about it.
or firmware update. MediaTek-su relies on a specific vulnerability in MediaTek chipsets (often referred to as a "rootkit" or exploit) to bypass security measures. Firmware Updates : Many manufacturers released updates after March 2020
The most common trigger for Step 3 is running mtk-su from an improper folder path. The Android operating system blocks execution from user-facing storage directories like /sdcard . The binary must reside and execute directly within the temporary local data storage directory ( /data/local/tmp ). When you run mtk-su , it executes in sequential phases
Find an official stock ROM for your exact phone model dated . Download a MediaTek flashing tool, such as SP Flash Tool . Flash the older firmware to your device.
"mtk-su: failed critical init step 3" is a known issue encountered when using the
To determine why you’re seeing the “failed critical init step 3” error, follow these diagnostic steps:
If the date is , mtk-su will consistently fail with Step 3 errors. In these cases, your only option is typically
./mtk-su: invalid option -- h Failed critical init step 3
If you hit this error, try these sequential troubleshooting methods to get the exploit working. Method 1: Verify and Match Architecture
Notice the pattern: Patch date is king.
What or security patch date is it currently running?