Xiaomi Mi 11 Pro - Installing this module boots into the recovery continuously

[Hot12345]

Describe the bug A clear and concise description of what the bug is.

After having Root enabled by TWRP OR Flashing Magisk_modified_boot.img, there is no problem with Root on this device. But after installing the module and reboot, the phone keeps rebooting into the Recovery MUIU 5.0 (NON-TWRP) after a couple reboots (10min later) the phone boots into the phone normally and disable this module V.2.3.1 in Magisk, and reboots, there is NO problem with booting into the phone. This only happens when enable/installing the module and reboots.

This also happens with TWRP being installed. The phone keeps booting into the TWRP recovery, after a couple reboots the phone boots into the phone normally. Once I been boot normally into the phone and give the phone a normall reboot, it keeps booting into the Recovery TWRP OR Recovery MUIU 5.0 with NON-TWRP

I can reproduce this problem.

To reproduce Steps to reproduce the behavior:

1. Having the phone Xiaomi Mi 11 Pro - MIUI 13 - 13.0.7.0 Stable - EEA (Europe) Xiaomi SKAEUXM
2. Getting Root by installing Magisk.zip by TWRP OR patch the Boot.img of the current ROM to get the Magisk_moddified_boot.img and patch this by ADB.
3. Once Magisk is being installed (Version 25.2 - 25200), install only this module V.2.3.1 (latest at this moment)
4. Give the phone a reboot when this module is being installed, then the phone boots into the recovery. Stock it boot into the MUIU Recovery 5.0 It keeps restarting automaticly, after 10min a reboots cycle further the phone will boot normally. But if you reboot your phone or shutdown, it will be booting automaticly into the recovery.

TWRP installed, it will boot into the TWRP recovery. Give manually a reboot a couple times. then the phone will boot normally.

Device info Device model: Xiaomi Mi 11 Pro Chinese - Flashed EEA (europe) Xiaomi ROM - MIUI Global 13.0.7 Stable - 13.0.7.0 (SKAEUXM) Android version: Android 12 - 12 SKQ1.211006.001 ROM name/version: star_eea_global_images_V13.0.7.0.SKAEUXM_20220507.0000.00_12.0_eea_dffd02e396

Logs Connect your phone to a computer and run adb logcat > issue.log. Attach the log file to this issue.

• Enable this Module, by enable Zygisk in the settings, otherwise the module is not active.
• Reboot
• Phone gets boot into the Recovery / TWRP automaticly.
• Give this phone another reboot, phone boots again into the recovery / TWRP
• In TWRP - Advanced - Copy Log - Check, Include Logcat, Include Kernal Log, - Swipe
• Add 3 log files to this case: dmesg.log, logcat.txt, recovery.log Additional context I always hide my Magisk with Magisk Hide Props Config - SU - Props fingerprint - Xiaomi 11 (china) - This process gets me passing Safetynet.

So basicly I need these 2 modules to pass my Safetynet coming anything different then the official stockROM.

That being said, there more people / users having this issue: https://forum.xda-developers.com/t/mi-11-ultra-reboots-to-recovery-mode-several-time-before-rebooting-to-miui.4477991/ dmesg.log logcat.txt recovery.log

Then I suddenly install ONLY this module, fresh, stock after flashing ROM, then the phone booting into the recovery so the cause is this module.

For the record; I can be a tester if there is a new module available, just let me know.

Checklist

• [x] All information is present
• [x] Logs are attached
• [x] I have tried installing and configuring MagiskHide Props Config

[czernihoviensis]

This issue happens to me as well, so I can be a tester if a newer version is available.

[Doomski99]

To disable the module, you clean install your ROM or what?

[czernihoviensis]

Magisk manager for TWRP does its job in this case.

sob., 12 lis 2022, 20:46 użytkownik Ali Kawtharani @.***> napisał:

To fix it, you clean install your ROM or what?

— Reply to this email directly, view it on GitHub https://github.com/kdrag0n/safetynet-fix/issues/216#issuecomment-1312558741, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASY3TNJN22ANWG6D54KSNBLWH7XY3ANCNFSM57MQMWBA . You are receiving this because you commented.Message ID: @.***>

[Hot12345]

To disable the module, you clean install your ROM or what?

Yes, but not passing safetynet because you need this module. If enable this module the phone boots in to recovery, after several times the phone boots normally.

Yes, also clean installed rom, same issue on the Official ROM globally.

[Hot12345]

Magisk manager for TWRP does its job in this case. sob., 12 lis 2022, 20:46 użytkownik Ali Kawtharani @.> napisał: … To fix it, you clean install your ROM or what? — Reply to this email directly, view it on GitHub <#216 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASY3TNJN22ANWG6D54KSNBLWH7XY3ANCNFSM57MQMWBA . You are receiving this because you commented.Message ID: @.>

Nope, problem still exist when the module of this same version is enable. Bootloop in to the recovery.

[shperrung]

Hi! I confirm the same for Xiaomi Mi11 Ultra: bootloop after the module install MIUI 13 Global ROM. I have custom recovery and tried resotre boot, system, data volumes but not success. Still bootloop. Finally, I formatted /data and made clean setup.

[Deses]

I'm having the same issue! Just installed this pluing and now I'm bootlooping into recovery. Googled the issue and quickly came to this XDA thread discussing the issue: https://forum.xda-developers.com/t/mi-11-ultra-reboots-to-recovery-mode-several-time-before-rebooting-to-miui.4477991/.

After some retries (usually just one retry) it works successfully into system and everything works alright.

Please take a look at this issue. :(