Bootloop Protector Fork is wahyu6070's fork of Yet Another Bootloop Protector. It retains automatic boot-failure and SystemUI monitoring, and adds a simple recovery trigger: placing an empty file named bootloop in a recognized location requests module removal on the following startup.
Boot Monitoring with a Manual Trigger
Automatic thresholds handle repeated failures, while the trigger file gives recovery users a way to request cleanup without flashing the module again.
Repeated-Boot Detection
Uses sequential markers, a two-minute default timeout, and zygote observation to identify a boot that modules may be preventing.
Optional SystemUI Watch
Can disable modules and reboot when SystemUI remains unavailable or enters a repeated crash cycle.
Recovery Trigger File
Recognizes an empty bootloop file placed on an accessible recovery-mounted path before the next boot.
Using the Recovery Trigger
From a recovery file manager or shell, create an empty file named bootloop in one of the paths checked by the fork. Documented examples include /cache/bootloop, /data/media/0/bootloop, /sdcard/bootloop, /sdcard1/bootloop, /system/bootloop, and /product/bootloop.
The location must actually be mounted and readable in that recovery. On the next startup, the module can use the trigger to disable root modules and neutralize general boot scripts, after which the suspected module should be isolated before re-enabling anything.
Whitelists and Logs
Protect essential entries with module IDs in /data/adb/YABP/allowed-modules.txt and script filenames in allowed-scripts.txt. Disable optional SystemUI monitoring by creating /data/adb/systemui.monitor.disable.
The service log is stored at /data/local/tmp/service.log. Preserve it before clearing or re-enabling modules because it can show which detection path activated.