mirror of
https://github.com/B16f00t/whapa.git
synced 2026-04-25 10:55:56 +03:00
[GH-ISSUE #128] Error -3 while decompressing data: incorrect header check #117
Labels
No labels
enhancement
help wanted
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whapa#117
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SW33TSHOT on GitHub (Jul 25, 2021).
Original GitHub issue: https://github.com/B16f00t/whapa/issues/128
Starting to decrypt...
[e] An error has ocurred decrypting 'C:\Users\Hardik\Desktop\007\WhatsApp\Databases\msgstore-2021-07-23.1.db.crypt14' - Error -3 while decompressing data: incorrect header check
[e] An error has ocurred decrypting 'C:\Users\Hardik\Desktop\007\WhatsApp\Databases\msgstore-2021-07-24.1.db.crypt14' - Error -3 while decompressing data: incorrect header check
[e] An error has ocurred decrypting 'C:\Users\Hardik\Desktop\007\WhatsApp\Databases\msgstore.db.crypt14' - Error -3 while decompressing data: incorrect header check
[i] Decryption completed
#125
@SW33TSHOT commented on GitHub (Jul 28, 2021):
@B16f00t ??
@B16f00t commented on GitHub (Jul 29, 2021):
You have a not valid key for that backup or you have a different offset #96, #113, #120
@SW33TSHOT commented on GitHub (Aug 1, 2021):
i put valid key but every time same error occurred!
please help me
is there any other salutation.
@B16f00t commented on GitHub (Aug 2, 2021):
Are you sure it is a valid key?
@SW33TSHOT commented on GitHub (Aug 13, 2021):
i am 100% sure put valid key !
@B16f00t
@B16f00t commented on GitHub (Aug 23, 2021):
If you follow this thread #113, maybe @ElDavoo can solve your problem.
Be careful when extracting the Key because if you are not root the key can change.
@khalidco commented on GitHub (Aug 30, 2021):
I am trying to know if the key file is identical for both crypt12 and crypt14. If you install the latest version of WA and restore from old crypt12, the App will not convert the db to crypt14.
The decryption works for old crpt12 db, but not for old crypt14 db. Are the key file different for each?!
@ElDavoo commented on GitHub (Aug 30, 2021):
no.
@khalidco commented on GitHub (Aug 30, 2021):
Can you elaborate? ☺
Is it possible to use the key file associated with crypt12 to decrpt a crypt14 db at all?
I read somewhere that changing the offsets may work.
@ElDavoo commented on GitHub (Aug 30, 2021):
the key is always the same, unless it changed for other reasons. you need to use recent versions of programs to have updated offsets
@khalidco commented on GitHub (Sep 8, 2021):
I registered again using an emulator and pulled a different key file!
The decryption process still fails..
I think I am using the last updated version of the script. Installing the pycrypto and pycrypto dome was failing due to vcvar...bat and was later fixed by getting an MSI version of the binary. However, it gives run errors for some odd reason.
Regards..
@mrmc-mc commented on GitHub (Dec 12, 2021):
same error
OS : Kali linux
key and database are same
@Frischid commented on GitHub (Feb 14, 2022):
Had the same problem, but decrypting worked with https://github.com/ElDavoo/WhatsApp-Crypt14-Decrypter/blob/master/decrypt14.py
After comparing the offsets, I got whacipher.py working by changing the offset in line 79 to
data = db_data[190:](notice: 190 instead of 191)Hope this can help someone
@ElDavoo commented on GitHub (Feb 14, 2022):
Basically in the database header you have the WhatsApp version, whose length often changes.
Example:
"2.21.24.22" => 11 bytes => offset=191
"2.22.3.77" => 10 bytes => offset=190
"2.22.5.7" => 9 bytes => offset=189
So yeah using a fixed offset won't work.