Several factors can contribute to the MTK-SU failed critical init step 3 error. Some common causes include:
The community response was unanimous: mtk-su is dead for this device. The only workaround was to physically open the device, short the test points, and flash an old bootloader via Mediatek SP Flash Tool —a procedure too dangerous for 99% of users. mtk-su failed critical init step 3
mtk-su was largely patched by Google and MediaTek by mid-2021. If your device has a security patch level (SPL) dated after , the kernel likely contains a fix for the specific CVE-2020-0069 variant. However, the "step 3" error often appears even on slightly older kernels because Google backported "hardened memory copying" ( copy_to_user mitigations) into the Linux kernel 4.14+. Several factors can contribute to the MTK-SU failed
: The binary must be executed from a directory where the system allows execution, typically /data/local/tmp . Move the file there using: adb push mtk-su /data/local/tmp/ . mtk-su was largely patched by Google and MediaTek
If you encounter this error, try the following steps to resolve or bypass it:
He looked at the motel door. Locked. Window closed. But somewhere, on the other end of that SPI bus, someone—or something—was waiting for him to finish what they’d started.
Open an ADB shell and run: