[GH-ISSUE #96] Error -3 while decompressing data: incorrect header check (after crypt14 update) #86

Closed
opened 2026-02-25 20:34:37 +03:00 by kerem · 8 comments
Owner

Originally created by @maiqueg on GitHub (May 4, 2021).
Original GitHub issue: https://github.com/B16f00t/whapa/issues/96

Around 1 May, Whatsapp began to use crypt14 instead of crypt12 on the msgstore.db backup.

Since then I'm getting this error when trying to decrypt:

[i] Starting to decrypt...
[e] An error has ocurred decrypting 'msgstore.db.crypt14' -  Error -3 while decompressing data: incorrect header check

I saw that the key is exactly the same used for crypt12, maybe only the decrypt method that changed? Any ideas?

Originally created by @maiqueg on GitHub (May 4, 2021). Original GitHub issue: https://github.com/B16f00t/whapa/issues/96 Around 1 May, Whatsapp began to use crypt14 instead of crypt12 on the msgstore.db backup. Since then I'm getting this error when trying to decrypt: ``` [i] Starting to decrypt... [e] An error has ocurred decrypting 'msgstore.db.crypt14' - Error -3 while decompressing data: incorrect header check ``` I saw that the key is exactly the same used for crypt12, maybe only the decrypt method that changed? Any ideas?
kerem closed this issue 2026-02-25 20:34:37 +03:00
Author
Owner

@Roly855 commented on GitHub (May 6, 2021):

I have exactly the same problem, some help please. Thank you very much in advance

<!-- gh-comment-id:833166576 --> @Roly855 commented on GitHub (May 6, 2021): I have exactly the same problem, some help please. Thank you very much in advance
Author
Owner

@ElDavoo commented on GitHub (May 9, 2021):

Offsets need to be updated. Take a look at:

andreas-mausch/whatsapp-viewer#114 (comment)

the following code results:

andreas-mausch/whatsapp-viewer@7035b9c

<!-- gh-comment-id:835848938 --> @ElDavoo commented on GitHub (May 9, 2021): Offsets need to be updated. Take a look at: andreas-mausch/whatsapp-viewer#114 (comment) the following code results: andreas-mausch/whatsapp-viewer@7035b9c
Author
Owner

@Roly855 commented on GitHub (May 9, 2021):

Thanks a million ElDavoo!!!!

<!-- gh-comment-id:835901735 --> @Roly855 commented on GitHub (May 9, 2021): Thanks a million ElDavoo!!!!
Author
Owner

@maiqueg commented on GitHub (May 11, 2021):

I've opened a pull request with the new offsets, but only for decryption.

#97

<!-- gh-comment-id:837562307 --> @maiqueg commented on GitHub (May 11, 2021): I've opened a pull request with the new offsets, but only for decryption. #97
Author
Owner

@B16f00t commented on GitHub (May 11, 2021):

Thanks to @ElDavoo for look for the problem and @maiqueg for the fix.

<!-- gh-comment-id:837937694 --> @B16f00t commented on GitHub (May 11, 2021): Thanks to @ElDavoo for look for the problem and @maiqueg for the fix.
Author
Owner

@ElDavoo commented on GitHub (May 28, 2021):

Did your offset change again in this night's backup? I noticed IV now starts at byte 67, but don't know about the rest.

<!-- gh-comment-id:850196338 --> @ElDavoo commented on GitHub (May 28, 2021): Did your offset change again in this night's backup? I noticed IV now starts at byte 67, but don't know about the rest.
Author
Owner

@ElDavoo commented on GitHub (May 30, 2021):

The new offsets are:

data = db_data[191:]
iv = db_data[67:83]

"Server salt" also changes from byte 14 to byte 15, but... you don't use server salt in your code ?? wtf? Can someone explain plz?

Not opening a pull request because I think this needs to be further improved: Format may change again in the future, users might be able to input their own offsets, there should be a list of offsets to try, and so on.

<!-- gh-comment-id:850997115 --> @ElDavoo commented on GitHub (May 30, 2021): The new offsets are: data = db_data[191:] iv = db_data[67:83] "Server salt" also changes from byte 14 to byte 15, but... you don't use server salt in your code ?? wtf? Can someone explain plz? Not opening a pull request because I think this needs to be further improved: Format may change again in the future, users might be able to input their own offsets, there should be a list of offsets to try, and so on.
Author
Owner

@ElDavoo commented on GitHub (Jun 22, 2021):

The new offsets are:

data = db_data[191:]
iv = db_data[67:83]

@B16f00t

<!-- gh-comment-id:866073332 --> @ElDavoo commented on GitHub (Jun 22, 2021): > The new offsets are: > > data = db_data[191:] > iv = db_data[67:83] @B16f00t
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/whapa#86
No description provided.