Overview
This guide covers common issues, error messages, and their solutions. Issues are organized by feature area for quick reference.ADB Connection Issues
Device Not Detected
Symptom: “No devices found. Connect a device and enable USB Debugging.” Causes & Solutions:USB Debugging Not Enabled
USB Debugging Not Enabled
Solution: Enable Developer Options and USB Debugging on your Android device:
- Go to Settings → About Phone
- Tap Build Number 7 times to enable Developer Options
- Go to Settings → Developer Options
- Enable USB Debugging
- Reconnect device and accept the authorization prompt
USB Cable Issues
USB Cable Issues
Solution:
- Use a data cable, not a charge-only cable
- Try a different USB port (prefer USB 2.0 ports)
- Avoid USB hubs—connect directly to computer
- Test cable with another device to verify functionality
Driver Issues (Windows)
Driver Issues (Windows)
Solution: Install proper USB drivers:If shows “unauthorized” or “offline”:
- Install manufacturer-specific USB drivers (Samsung, Xiaomi, etc.)
- Or install Universal ADB Driver: https://adb.clockworkmod.com/
- Restart computer after driver installation
- Open Device Manager (Win+X → Device Manager)
- Look for device under “Portable Devices” or “Other Devices”
- Right-click → Update Driver → Browse → Select driver folder
ADB Server Issues
ADB Server Issues
Solution: Restart ADB server:If using multiple ADB instances (Android Studio, other tools):
Device Shows as 'Unauthorized'
Device Shows as 'Unauthorized'
“ADB not installed” Error
Symptom: Tool cannot find ADB executable. Solution: The tool should auto-download ADB. If it fails:core/device_manager.py:43-47):
adb/platform-tools/adb[.exe]adb/adb[.exe]
Multiple Devices Connected
Symptom: “error: more than one device/emulator” Solution: The tool handles this automatically in menu option “Scan Connected Devices”. It will prompt you to select a device. For manual ADB commands, specify device serial:Backup Extraction Issues
Empty Backup Directories
Symptom: “No backup files found” when dumping. Causes & Solutions:Android 11+ Scoped Storage
Android 11+ Scoped Storage
Cause: Modern Android versions restrict access to app-specific directories.Solution: Backups may be in scoped storage path:Paths checked by tool (
core/device_manager.py:165-170):- Legacy:
/storage/emulated/0/WhatsApp/Databases - Scoped:
/storage/emulated/0/Android/media/com.whatsapp/WhatsApp/Databases
WhatsApp Not Installed
WhatsApp Not Installed
Solution:
- Install WhatsApp or WhatsApp Business on device
- Launch app at least once to initialize directories
- Enable chat backup in Settings → Chats → Chat Backup
No Backups Created Yet
No Backups Created Yet
Solution: Create a manual backup:
- Open WhatsApp
- Go to Settings → Chats → Chat Backup
- Tap Back Up to create a local backup
- Wait for backup to complete
- Re-run tool’s dump feature
Multi-User Device
Multi-User Device
Cause: Device has multiple user profiles (Work Profile, Guest, etc.)Solution: Tool scans all users automatically. Check if WhatsApp is installed in correct user profile:
Permission Denied During Dump
Symptom: “Permission denied” when pulling files. Solution:Media Dump Incomplete
Symptom: “Media dump failed” or partial media extraction. Causes:- Large media folders (10GB+): May timeout or fail
- Storage space: Insufficient disk space on computer
- Connection interruption: USB disconnect during transfer
Decryption Issues
Wrong Key Error
Symptom: “Decryption failed” or “MAC check failed” Cause: Incorrect decryption key. Solutions:Extract Key from Device
Extract Key from Device
For crypt14/15 (requires root or special exploit):Without root (use Termux mode):
- Deploy tool to Termux (Menu Option: Deploy to Termux)
- Run tool inside Termux app (has direct access to WhatsApp directory)
Key File Location
Key File Location
Device paths checked:
/data/data/com.whatsapp/files/key(Standard WhatsApp)/data/data/com.whatsapp.w4b/files/key(WhatsApp Business)
crypt15 Passphrase
crypt15 Passphrase
For crypt15: You need the 64-digit backup passphrase, NOT the device key file.Find passphrase:
- Open WhatsApp
- Settings → Chats → Chat Backup
- Tap “End-to-end encrypted backup”
- View or reset 64-digit key
Corrupt File Error
Symptom: “Error -3 while decompressing data” or “Invalid SQLite database” Cause: File corruption or incomplete transfer. Solution:Offset Scanning Timeout
Symptom: Decryption hangs on “Scanning offsets…” Cause: Large file + extensive offset scanning. Solution: Offset scanning typically completes in 1-5 seconds. If longer:- Wait: Scanning range is limited (0-190 for IV, +300 for data)
- Check system resources: High CPU usage is normal during scan
- If truly stuck (>60 seconds): Kill process and try again
core/crypto_manager.py:174:
Python Environment Issues
Import Errors
Symptom: “ModuleNotFoundError: No module named ‘Crypto’” Solution:Virtual Environment Issues
Symptom: Packages installed but still getting import errors. Solution: Ensure virtual environment is activated:Python Version Issues
Symptom: Syntax errors or unexpected behavior. Solution: Tool requires Python 3.7+Platform-Specific Issues
Windows
'adb' is not recognized
'adb' is not recognized
Solution: Add ADB to PATH or use full path:
Permission Denied Writing Files
Permission Denied Writing Files
Solution: Run PowerShell/CMD as Administrator, or change output directory:
Antivirus Blocking ADB
Antivirus Blocking ADB
Solution: Add ADB directory to antivirus exclusions:
- Windows Defender: Settings → Virus & threat protection → Exclusions
- Add folder:
<tool_directory>\adb\
Linux
Device Access Denied
Device Access Denied
Solution: Add udev rules:
ADB Permission Denied
ADB Permission Denied
Solution: Make ADB executable:
macOS
'adb' cannot be opened
'adb' cannot be opened
Solution: Remove quarantine attribute:
USB Debugging Authorization Loop
USB Debugging Authorization Loop
Termux (Android)
Permission Denied Accessing WhatsApp Files
Permission Denied Accessing WhatsApp Files
Solution: Grant Termux storage permission:
'No space left on device'
'No space left on device'
Solution: Termux has limited internal storage:
Database Viewing Issues
”Table ‘chat’ not found”
Symptom: Error when listing chats. Cause: Old database schema or corrupt decryption. Solution:core/viewer.py:73-135). If error persists, database may be from very old WhatsApp version (pre-2015).
No Messages Displayed
Symptom: Chats listed but no messages when viewing. Solution: Viewer tries multiple strategies (core/viewer.py:137-313):
messagetable (primary)available_message_view(view)messagestable (legacy)
Debug Logging
Enable Verbose Mode
Add debug output incore/crypto_manager.py:
core/utils.py:39):
app.log in the tool directory.
View Real-Time Logs
Getting Help
Collect Diagnostic Information
When reporting issues, include:Common Support Scenarios
Decryption Fails
Provide:
- Backup file size
- File extension (.crypt12/14/15)
- First 200 bytes of file (hex)
- Error message from tool
ADB Connection
Provide:
adb devicesoutput- Device manufacturer/model
- Operating system
- USB debugging enabled status
Python Errors
Provide:
- Full error traceback
- Python version
pip listoutput- OS and version
Database Issues
Provide:
- SQLite version:
sqlite3 --version - Database integrity check output
- WhatsApp version when backup created
Related Documentation
ADB Operations
Deep dive into ADB internals and command execution
Crypt Formats
Understanding WhatsApp encryption formats and decryption
Key Management
How the tool securely stores and manages encryption keys
