If mtk-su is permanently patched on your firmware and you cannot downgrade, the development community has built newer, more powerful tools that bypass OS-level patches entirely by targeting the boot ROM (BROM) hardware layer.
For 64-bit devices, use the arm64 binary version; for 32-bit devices, use the standard arm version.
When users encounter "Failed critical init step 3," the exploit cannot complete its initialization sequence. The "init step 3" refers to the third phase of MTK-SU's startup process, which involves establishing the necessary environment for root access.
Some newer MediaTek devices are vulnerable to other exploits such as: mtk-su failed critical init step 3
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
| Device | Chipset | Result | | :--- | :--- | :--- | | LG K10 (2017) | MediaTek MT6750 | Success | | LG K8 | MediaTek MT6735 | Fail | | Motorola Moto E4 | MediaTek MT6737 | Success | | Alcatel 1 | MediaTek MT6739 | Success | | ZTE Blade A7 Prime | MediaTek MT6761 | Success | | LG K50 | MediaTek Helio P22 | Success |
: Users have reported that the exploit is occasionally unstable and may fail randomly on the first few attempts. about.gitlab.com Potential Fixes and Workarounds Re-issue Permissions : Ensure the file is executable. Users on suggest running chmod 755 mtk-su If mtk-su is permanently patched on your firmware
Understanding the limitations of mtk-su is essential for anyone using this tool.
If you are trying to root, it is recommended to focus on conventional methods, such as unlocking the bootloader via fastboot , rather than relying on mtk-su on modern Android security patches.
Run the following command again to ensure it is executable: chmod 755 mtk-su The "init step 3" refers to the third
Device manufacturers quickly incorporated these patches into their over-the-air (OTA) updates. Users who updated their devices after March 2020 found that MTK-SU would no longer work—even if it had functioned previously on older firmware versions.
If you see this error, accept that the exploit will not work on your current firmware. Do not download random "updated mtk-su 2025" binaries from sketchy forums; they are almost certainly malware. Your time is better spent investigating the official bootloader unlock process for your device or embracing the limitations of a secure, up-to-date system.
For users who successfully achieve root access with MTK-SU, preventing future failures requires careful management of system updates:
Navigate to . If the date listed is 2020-03-01 or later, your current firmware cannot be exploited using this method. Working Alternatives and Solutions