Module auto-disable too aggressive on failed boots due to low battery

[mrydzak]

Device: LG V60 V600VM
Android version: Android 13
Magisk version name: v30.4
Magisk version code: 30400

When my phone battery dies completely during the boot process, all Magisk modules get automatically disabled on the next successful boot. This happens frequently due to the phone running out of battery and tries to boot up while its charging; making the built-in magisk bootloop protector believe it's bootlooping due to the modules.

Here is the issue that I am facing:

-Phone battery dies completely
-Phone attempts auto reboot but fails due to insufficient power
-After charging and booting normally, all Magisk modules are disabled automatically
-I have to manually reenable all modules, Zygisk, and configure DenyList again

It would be nice to have a setting to disable this bootloop protection feature. I don't require this safety net since I have FBE (File-Based Encryption) disabled and can easily disable modules via recovery if needed. The bootloop protector is a bit too aggressive for power-related boot failures and creates unnecessary maintenance.

Here are some steps if you want to create the problem in the LG V60, or other phones that boot up while charging the battery:

- Let phone battery die completely
- Phone attempts auto-reboot but fails due to low power (repeats until charged)
- Charge phone and boot normally
- All Magisk modules are disabled automatically, requiring manual re-enabling

It would be nice to have a toggle in Magisk settings to disable the automatic module disabling feature. This would allow users who have recovery access and understand the risks to opt-out of this protection. Honestly, I do not believe I need to fork every single new version to create a fix for this. If I can disable this another way, a solution would be appreciate it. Thank you for maintaining Magisk.

[hhihhio]

It's the magisk feature. Need add way to disble

[canyie]

I have asked to add a toggle to disable bootloop protection years ago, but got rejected by another maintainer

[vvb2060]

This is a safety measure and cannot be turned off. I recommend charging the device promptly.

[hhihhio]

This is a safety measure and cannot be turned off. I recommend charging the device promptly.

it also needs a way, if the user really wants and understands. case no one cares about having to delete all data or will know how to solve it themselves: debugging, disabling all modules manually via recovery terminal, file explorer... as a overclock avid expert experience, I suggest undervolt the phone. My j5 2016 samsung stupid add 1.35v, I undervolt to 1.2 or 1.15 and my phone can't get hot

[osm0sis]

This is a safety measure and cannot be turned off. I recommend charging the device promptly.

Any way to have the feature poll the battery state and not disable things if it's <2% or something?