How to prevent and recover from Android boot loop caused by malicious sms of death ☠️ text messages?
The Android Debug Bridge API (ADB) via a USB cable physically connected to a PC computer is an option.
An Android boot loop caused by a malformed “SMS of Death” (such as a poisoned WAP Push payload stuck in the internal raw SMS queue) triggers a crash in com.android.phone immediately upon startup, forcing Android’s RescueParty crash protection to continuously reboot the device.
Because the device briefly boots up or reaches an ADB-accessible state before crashing and restarting, you can intercept and clear the malicious queued messages via a connected computer without performing a factory reset. Recovery Procedure via ADBTo break the crash loop, you must act quickly during the short window right after the phone boots, before the telephony service crashes and triggers another reboot.
Step by step:
Prerequisite: Plug your phone into your computer via a USB cable. Open your computer’s terminal or command prompt and verify your device is detected by running adb devices.
Timing is critical:
Allow the phone to boot up. The moment the device boots and starts responding to ADB commands, you must rapidly execute commands before the crash handler forces a reboot.
Tip: You can use a loop command in your terminal to automatically issue commands the second ADB connects:
adb wait-for-device
Required for cleanup: Run the following command to allow the shell to modify the SMS provider storage.
adb shell cmd appops set com.android.shell WRITE_SMS allow
Query the raw SMS database provider to identify the malformed message entries (typically WAP Push entries with specific destination ports), targeting raw SMS content:
adb shell content query --uri content://sms/raw --projection _id:destination_port:date:deleted
adb shell "content delete --uri content://sms/raw --where \"address=''\""
Note: Adjust the WHERE clause parameters depending on the specific address or row ID returned by your query.
Reset permissions and reboot to finalize cleanup.
Install the available Android security updates (rolled out starting October 2026), though users depend on individual device manufacturers (like Samsung, Xiaomi, etc.) to distribute them.
Android 12 and 13 are past their official support lifecycle and will not receive patches from Google, leaving devices running those versions permanently vulnerable unless manufacturers issue custom patches.
Discovered by security researcher Mark Blaszczyk, tracked as CVE-2026-58882 (“SMS of Death”). It is a zero-click denial-of-service vulnerability affecting Android versions 12 through 17.
Exploits a WAP Push message parsing error where a manipulated length field is interpreted as a negative number. The message remains entirely invisible, appearing nowhere in the normal SMS inbox.
Causes the telephony service to crash immediately, interrupts calls (including emergency calls), and can trap the device in a continuous boot/reboot loop (roughly every 90 seconds) because the system tries to re-process the stuck message upon startup.
Note: this text was generated by LLM AI, inspired by a Heise news article („SMS des Todes“: Sicherheitslücke lässt Android-Smartphones abstürzen), after researching Cybernews: Invisible “SMS of Death” crashes Android phone, traps victim in reboot loop until factory reset and Workaround/Fix for anyone stuck in a reboot loop #2 by Mark Blaszczyk (MarkBlah) on GitHub. AI and can make mistakes.