whatsapp Msgstore Viewer

Free, open source and cross-platform app to decrypt, read and view the Whatsapp msgstore.db database.

Features

• View contact and group chats.
• View call logs with their durations.
• Easy access to media files (images, audios and videos) from inside the chat, if the local Whatsapp directory has been provided.
• Decrypt and view the database if you have the decryption key (Should support crypt12, crypt14 and crypt15).
• Cross-platform (Should work on Linux, Windows and Mac)

Installation

• Download pre-built binaries

Pre-built binaries are available on the releases page. (Soon)

• From source

  • Ensure Python (version 3.9 or higher) is installed (Or better yet create and activate a virtual environment).
  • Clone the repository

  git clone https://github.com/abdeladim-s/whatsapp-msgstore-viewer 
  

  • Install the requirements

  pip install -r requirements.txt
  

  • Run the main script

  python main.py 
  

Usage

To use the app, you will need:

• The msgstore.db (msgstore.db.cryptX if it is encrypted) database: It is a database where Whatsapp is storing all your messages.
• The wa.db database: It is a database where Whatsapp is storing contact names. It is optional, so if it is not provided you will just see phone numbers.
• The Whatsapp directory: The directory of Whatsapp in the local storage of your phone. This will be used to view the media files (Optional as well).
• The key: If your database is encrypted, you will need to provide the decryption key to decrypt it first. The decrypted database will be stored in the same directory of your encrypted database suffixed with -decrypted.db (See bellow for more information).

Notes

• Where to find the databases

Check the great tutorial "Retrieving WhatsApp Databases" made by @Dexter2389.

• About the decryption process

The app is using the WhatsApp-Crypt14-Crypt15-Decrypter by ElDavoo under the hood. Please check their repository if you face any issues with the decryption.

• About the Database schema

Because this app is only a reverse engineering attempt of the Whatsapp database, it is very likely that it might break in case there have been any updates to the msgstore database.
For now it supports just the schema of my personal msgstore.db file.
So I made it easy to allow the community to add support to more schemas (It's a simple SQLite exercise :D).
All contributions are welcome. Feel free to let me know if you need any help.
Follow these steps in order to add support to other schemas (see db/v1/db.py as an example):

• Create a package in the dbs package and give your schema a name (for example v2).

• Inside the newly created package, create a python module db.py.

• Inherit the abstract class AbstractDatabase located in the dbs/abstract_db.py module.

• The app will dynamically load existing schemas when starting.

• Submit a pull request.

• About different languages

You might face an issue where the messages are being displayed in a wierd way (square characters). This is probably a font issue. To fix that, search for a font that supports your language, and on the login screen, go to advanced settings and provide the path to your font.

Contributing

If you find a bug, have a suggestion or feedback, please open an issue for discussion.

Credits

• kivy & KivyMD for the UI framework.
• WhatsApp-Redesign for the design inspiration and some UI components.
• WhatsApp-Crypt14-Crypt15-Decrypter for the decryption algorithm.
• Sbk2605 for the Whatsapp logo (Licenced under Creative Commons Attribution-Share Alike 4.0 International).
• whatsapp-chat-parser-website for the background image.
  And so many more libraries and frameworks.

License

This project is licensed under the GNU General Licence version 3 or later. You can modify or redistribute it under the conditions of these licences (See LICENSE for more information).

DISCLAIMER

This project is not endorsed or certified by WhatsApp Inc. and is meant for personal and educational purposes only.
It is provided as is without any express or implied warranties.
The authors/maintainers/contributors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.