How to Check for Android Security Updates and Avoid Data Loss from the “SMS of Death”

Quick Start

Open Settings → About phone → Android version.
Confirm you are running Android 14 or newer and the security patch is from October 2026 or later. If both are true, the "SMS of Death" fix is already on your device.

Prerequisites

Verified backup of all important data (Google Drive, local PC, or encrypted SD card). A factory reset may be required later.
Charged phone (≥50 %).
Wi‑Fi or mobile data for downloading updates.
Computer with Android Debug Bridge (ADB) installed only if you need to clear the malicious message manually.
USB cable that supports data transfer.

1. Check Android Version & Security Patch Level

1.1 Find Android version (stock Android / Pixel)

Open Settings.
Scroll to About phone.
Tap Android version – note the number (e.g., 14, 15, 16, 17).

1.2 Find security patch level (Samsung, OnePlus, etc.)

In Settings, go to Software update (or System → Advanced → System update on some OEMs).
Look for Security patch level – it should read Oct 2026 or later.

Result: If you see Android 14‑17 and a patch level of Oct 2026+, the vulnerability is patched.

2. Install the Latest Security Update

2.1 Check for OTA updates

Open Settings → Software update (or System → Advanced → System update).
Tap Check for updates.
If an update is offered, read the changelog for "security patch" and confirm it includes Oct 2026.
Tap Download and install.
Allow the phone to restart when prompted.

2.2 Verify the update installed correctly

Repeat steps in 1.1 and 1.2.
Ensure the version and patch level match the latest OTA.

Result: Your device now contains Google’s fix for CVE‑2026‑58882.

3. Verify the Fix Is Active

Open Settings → About phone → Android version.
Confirm the version is 14, 15, 16, or 17.
Open Settings → Software update → Security patch level and verify it reads Oct 2026 (or a later month in the same year).
(Optional) Visit the device‑manufacturer’s support page for a list of patched builds – use the exact model number you can find under Settings → About phone → Model number.

If both conditions are met, the phone will ignore the malformed WAP‑Push SMS that triggers the crash.

4. If Your Phone Is Already Crashing or Stuck in a Boot Loop

You can clear the offending message with ADB without wiping the whole device. This works only if you can boot the phone long enough to enable USB debugging.

4.1 Prerequisites for ADB recovery

Developer options enabled:
1. Open Settings → About phone.
2. Tap Build number seven times until “You are now a developer” appears.
USB debugging turned on:
1. Go to Settings → System → Developer options.
2. Toggle USB debugging to On.
ADB installed on your computer (download the platform‑tools package from the official Android developers site).

4.2 Connect and clear the malicious SMS

# 1. Verify the device is detected
adb devices
# You should see a serial number; if not, check USB mode (choose "File Transfer") and drivers.

# 2. Reboot into normal mode (if stuck, try "adb reboot" once the device is recognized)
adb reboot

# 3. After the phone finishes booting (you have ~30 seconds before the crash repeats), delete the WAP‑Push queue:
adb shell "pm clear com.android.phone"
# This clears the telephony app’s data, removing the queued message.

# 4. Re‑enable the phone service (optional, may happen automatically)
adb shell "am start -n com.android.phone/.PhoneApp"

Note: pm clear com.android.phone removes all call‑history data; you may lose recent call logs but not personal files.

4.3 Verify recovery

Make a test call.
Send a normal SMS to yourself.
If the call stays connected and the phone no longer reboots, the fix worked.

5. Troubleshooting

Problem	Likely Cause	Fix
No OTA update appears	Manufacturer has not yet rolled out the patch for your model.	1. Check the OEM’s support website for a manual firmware download (use the exact model number). 2. Contact the carrier or OEM support for an estimated rollout date.
ADB reports "device unauthorized"	USB debugging not authorized on the phone.	On the phone, tap Allow USB debugging when the prompt appears. If the prompt never shows, enable Revoke USB debugging authorizations in Developer options, then reconnect.
Phone still crashes after ADB clear	The malicious message is re‑queued from the carrier after each boot.	1. After clearing, immediately disable mobile data (Airplane mode) and re‑enable after the phone stabilises. 2. Contact your carrier and ask them to stop resending the WAP‑Push message.
Device stuck in bootloop despite ADB steps	System partition corrupted or the fix never applied.	Back up any removable storage, then perform a factory reset: `Settings → System → Reset → Factory data reset`. After reset, immediately install the latest OTA before restoring apps.
Lost call logs after `pm clear com.android.phone`	The command intentionally wipes telephony app data.	Restore call logs from a recent Google backup (if you enabled Backup & sync).

6. When to Seek Professional Help

Your device is bricked and does not enter fastboot or recovery mode.
The OEM does not provide any security update for your Android version (e.g., Android 12/13 devices no longer receiving patches).
You are uncomfortable using ADB or cannot enable USB debugging because the phone never stays on long enough.

In these cases, contact the manufacturer’s official support (use the phone’s model number to locate the correct page) or visit an authorized service center.

7. Final Verification Checklist

[ ] Android version ≥ 14 (or the specific patched build for Android 12‑13, if your OEM released a back‑port).
[ ] Security patch level Oct 2026 or later.
[ ] OTA update installed without errors.
[ ] Device boots normally and can place/receive calls.
[ ] No unexpected reboots after receiving a normal SMS.

If all items are checked, your phone is protected against the "SMS of Death" vulnerability.