wallet.dat corrupt. help! bounty 100$

[aqwark]

Hey everyone!

I just deleted wallet.dat file from PC. And recovered several old wallet.dat files. I'm trying to dump/access by pywallet by --dumpwallet and --recover (i already install pip, twisted, zope, bsddb). Useless unfotunately.

If i use --dumpwallet (code: python --passphrase='pass' --otherversion=48 [LTC wallet] --datadir=C:\pathtowallet --dumpwallet), everytime i get error:

ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this
again.

If i use --recover (code: python --recover --recov_device=C:\Path\wallet.dat --otherversion=48 --recov_size 10Gio --passphrase='pass' --recov_outputdir C:\Path\foundkeys):

Read 0.0 Go in 0.0 minutes

Found 0 possible wallets
Found 0 possible encrypted keys
Found 0 possible unencrypted keys

It is noteworthy that the program does not even respond, the correct password or not. (on noncorrupt wallet.dat correctly respond)

Both commands work fine with fresh files.

Guys, who can help? How this possible, i have good (hope) files, big size (1.6 MB), not damaged (respond from recovery utility).

Please answer here or pm me.
Skype aqwark

Bounty with pleasure I will grant

[mrb000]

Was your wallet encrypted with passwrod?

[Btcspot]

 Hi try downloading file recovery, then scan your computer. http://www.undelete360.com/download.html  also try this https://www.reddit.com/r/litecoin/comments/5amayl/importing_old_walletdat_into_litecoin_core
 If it helps please send reward .

[cellard]

Where were these wallet.dat files sitting? in a CD/DVD, HDD, SSD? did you find them and one of them was corrupt? or did you accidentally delete a wallet.dat? Are you on Linux or Windows? Are they all BTC wallets or some altcoin wallets? (you mention LTC)

If you are on Windows you can use recuva:

https://www.ccleaner.com/recuva

In Linux look one of these:

https://alternativeto.net/software/recuva/?platform=linux

Deleted files are accessible the faster you try to recover them, otherwise if they become overwritten by other files it's over, maybe if you have access to really sophisticated forensics stuff you would still have a chance.

And be sure to know that the wallet.dat you are trying to decrypt corresponds to the software you are using otherwise that's why it may be crashing.

[HCP]

Hey everyone!

I just deleted wallet.dat file from PC. And recovered several old wallet.dat files. I'm trying to dump/access by pywallet by --dumpwallet and --recover (i already install pip, twisted, zope, bsddb). Useless unfotunately.

If i use --dumpwallet (code: python --passphrase='pass' --otherversion=48 [LTC wallet] --datadir=C:\pathtowallet --dumpwallet), everytime i get error:

ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this
again.

The error you are getting (Couldn't open wallet.dat/main) indicates that PyWallet is unable to parse your "wallet.dat" file as a wallet file. It's possible the file is corrupted beyond PyWallet's ability to simply read/parse it as a wallet.dat file. This is not uncommon in the case of recovered files that may have had parts of them overwritten.

If i use --recover (code: python --recover --recov_device=C:\Path\wallet.dat --otherversion=48 --recov_size 10Gio --passphrase='pass' --recov_outputdir C:\Path\foundkeys):

Read 0.0 Go in 0.0 minutes

Found 0 possible wallets
Found 0 possible encrypted keys
Found 0 possible unencrypted keys

Again, it seems like the wallet.dat file you are attempting to recover is damaged beyond PyWallets ability to recover the keys from it. I've run this on a known "good" wallet.dat and get:

Code:

Starting recovery.

Read 0.0 Go in 0.0 minutes

Found 1 possible wallets
Found 312 possible encrypted keys
Found 0 possible unencrypted keys

If I try and damage the file (deleted last half of the file), it still works... even randomly replacing large chunks of data with random text still works:

Code:

Starting recovery.

Read 0.0 Go in 0.0 minutes

Found 1 possible wallets
Found 234 possible encrypted keys
Found 0 possible unencrypted keys

Note how the number of possible encrypted keys is different (looks like I deleted a few! )... I was even able to delete the file and PyWallet was still able to "recover" it from the usb stick:

Code:

Starting recovery.
0.10 Go read
0.20 Go read
0.30 Go read
0.40 Go read
0.50 Go read
0.60 Go read
0.70 Go read
0.80 Go read
0.90 Go read
1.00 Go read

Read 1.0 Go in 1.3 minutes

Found 1 possible wallets
Found 235 possible encrypted keys
Found 0 possible unencrypted keys

Possible wallet #1
    with passphrase #1  .......................

So, if it isn't working, then either your recovered "wallet.dat" isn't actually a wallet.dat or it is really corrupted.

Also, how "new" were the wallet.dat files? Pywallet can sometimes have issues with newer wallets due to wallet file format updates in more recent versions of "Core".

[aqwark]

Was your wallet encrypted with passwrod?

Yes ofc

Hi try downloading file recovery, then scan your computer. http://www.undelete360.com/download.html  also try this https://www.reddit.com/r/litecoin/comments/5amayl/importing_old_walletdat_into_litecoin_core
 If it helps please send reward .

useless, cuz i have corrupt wallet.dat

Where were these wallet.dat files sitting? in a CD/DVD, HDD, SSD? did you find them and one of them was corrupt? or did you accidentally delete a wallet.dat? Are you on Linux or Windows? Are they all BTC wallets or some altcoin wallets? (you mention LTC)

If you are on Windows you can use recuva:

https://www.ccleaner.com/recuva

In Linux look one of these:

https://alternativeto.net/software/recuva/?platform=linux

Deleted files are accessible the faster you try to recover them, otherwise if they become overwritten by other files it's over, maybe if you have access to really sophisticated forensics stuff you would still have a chance.

And be sure to know that the wallet.dat you are trying to decrypt corresponds to the software you are using otherwise that's why it may be crashing.

on HDD. all of them corrupt, i already found 3 versions this file, and all of this corrupted. Yes, im accidentally deleted wallet.dat. Im on Windows. They only used by Litecoin core.

Im used Recuva, GetDataBack (most helpful), TestDisk, R-undelete.

How wallet.dat cannot corresponds to the software?

Hey everyone!

I just deleted wallet.dat file from PC. And recovered several old wallet.dat files. I'm trying to dump/access by pywallet by --dumpwallet and --recover (i already install pip, twisted, zope, bsddb). Useless unfotunately.

If i use --dumpwallet (code: python --passphrase='pass' --otherversion=48 [LTC wallet] --datadir=C:\pathtowallet --dumpwallet), everytime i get error:

ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this
again.

The error you are getting (Couldn't open wallet.dat/main) indicates that PyWallet is unable to parse your "wallet.dat" file as a wallet file. It's possible the file is corrupted beyond PyWallet's ability to simply read/parse it as a wallet.dat file. This is not uncommon in the case of recovered files that may have had parts of them overwritten.

If i use --recover (code: python --recover --recov_device=C:\Path\wallet.dat --otherversion=48 --recov_size 10Gio --passphrase='pass' --recov_outputdir C:\Path\foundkeys):

Read 0.0 Go in 0.0 minutes

Found 0 possible wallets
Found 0 possible encrypted keys
Found 0 possible unencrypted keys

Again, it seems like the wallet.dat file you are attempting to recover is damaged beyond PyWallets ability to recover the keys from it. I've run this on a known "good" wallet.dat and get:

Code:

Starting recovery.

Read 0.0 Go in 0.0 minutes

Found 1 possible wallets
Found 312 possible encrypted keys
Found 0 possible unencrypted keys

If I try and damage the file (deleted last half of the file), it still works... even randomly replacing large chunks of data with random text still works:

Code:

Starting recovery.

Read 0.0 Go in 0.0 minutes

Found 1 possible wallets
Found 234 possible encrypted keys
Found 0 possible unencrypted keys

Note how the number of possible encrypted keys is different (looks like I deleted a few! )... I was even able to delete the file and PyWallet was still able to "recover" it from the usb stick:

Code:

Starting recovery.
0.10 Go read
0.20 Go read
0.30 Go read
0.40 Go read
0.50 Go read
0.60 Go read
0.70 Go read
0.80 Go read
0.90 Go read
1.00 Go read

Read 1.0 Go in 1.3 minutes

Found 1 possible wallets
Found 235 possible encrypted keys
Found 0 possible unencrypted keys

Possible wallet #1
    with passphrase #1  .......................

So, if it isn't working, then either your recovered "wallet.dat" isn't actually a wallet.dat or it is really corrupted.

Also, how "new" were the wallet.dat files? Pywallet can sometimes have issues with newer wallets due to wallet file format updates in more recent versions of "Core".

 

New wallet.dat - from 01.07.2018
Old (corrupted) wallet.dat - from May and June this year
I also think that the files were partially overwritten  

Bounty up to 200$.

I will send my wallet to anyone who will respond to help

[Btcspot]

 Ok, you can send me them. I will try. Send a pm ok?

[HCP]

New wallet.dat - from 01.07.2018
Old (corrupted) wallet.dat - from May and June this year
I also think that the files were partially overwritten  

Wierd that it isn't detecting it as a wallet file at all though... even if it was partially overwritten.

It could be that changes to Litecoin since PyWallet was last updated have "broken" Litecoin recovery in PyWallet and it isn't able to recover newer Litecoin wallets... as my Litecoin wallet is quite old.

I will send my wallet to anyone who will respond to help

I've sent you a PM... I'm happy to take a look, but obviously, based on what you've stated and tried so far, I can't guarantee a successful recovery.


EDIT: for the record, the OP sent me 3 .dat files... Based on my investigations none of these .dat files are wallet.dat files.

The file contents is in no way consistent with the contents of a wallet.dat file, LTC or otherwise... It doesn't even look like a corrupted wallet.dat file.

@OP, did you just do a file recovery on *.dat files? Or did you explicitly search for wallet.dat files? Or did you just do a search for deleted files?

[aqwark]

EDIT: for the record, the OP sent me 3 .dat files... Based on my investigations none of these .dat files are wallet.dat files.

The file contents is in no way consistent with the contents of a wallet.dat file, LTC or otherwise... It doesn't even look like a corrupted wallet.dat file.

@OP, did you just do a file recovery on *.dat files? Or did you explicitly search for wallet.dat files? Or did you just do a search for deleted files?

I found the deleted files (*wallet*.dat, and found only wallet.dat) and restored them by recovery utilities (GetDataBack/Recuva/R-undelete/TestDisk - GTB most helpful)


NEWS:

I made a serious mistake when building the recovery code on the program (thanks to Marcelo Bianchi). Wrong recovery directory specified. So I was get:

Read 0.0 Go in 0.0 minutes

Found 0 possible wallets
Found 0 possible encrypted keys
Found 0 possible unencrypted keys


NOW, with correct code, i get this reports like this (on both 2 pc, where i found wallet.dat files):

Read 119.9 Go in 68.7 minutes

Found 0 possible wallets
Found 276 possible encrypted keys
Found 0 possible unencrypted keys
Traceback (most recent call last):
  File "pywallet.py", line 4870, in <modul
    recoveredKeys=recov(device, passes, si
  File "pywallet.py", line 1532, in recov
    list_of_possible_keys_per_master_key[t
IndexError: list index out of range


Read 499.5 Go in 108.0 minutes

Found 0 possible wallets
Found 2040 possible encrypted keys
Found 0 possible unencrypted keys
Traceback (most recent call last):
  File "pywallet.py", line 4870, in <mo
    recoveredKeys=recov(device, passes,
  File "pywallet.py", line 1532, in rec
    list_of_possible_keys_per_master_ke
IndexError: list index out of range

Marcelo Bianchi told me that there is no more hope...  

Who has any thoughts on this matter?

[HCP]

It looks like you've scanned the whole hard drive for your keys... and it has found possible keys. Not exactly sure why PyWallet is crashing though, as you have cut the error messages off.

[Evil-Knievel]

If you want I can give it a try