Search content
Sort by

Showing 5 of 5 results by aqwark
Post
Topic
Board Development & Technical Discussion
Re: wallet.dat corrupt. help! bounty 100$
by
aqwark
on 03/07/2018, 18:09:50 UTC
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? Huh

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     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     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...  Cry

Who has any thoughts on this matter?
Post
Topic
Board Development & Technical Discussion
Re: wallet.dat corrupt. help! bounty 100$
by
aqwark
on 02/07/2018, 16:11:23 UTC
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.



Quote
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! Tongue)... 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. Undecided

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".

 Cry Cry Cry

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  Cry Cry Cry

Bounty up to 200$.

I will send my wallet to anyone who will respond to help
Post
Topic
Board Development & Technical Discussion
Merits 1 from 1 user
wallet.dat corrupt. help! bounty 100$
by
aqwark
on 01/07/2018, 15:55:48 UTC
⭐ Merited by LoyceV (1)
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

Post
Topic
Board Development & Technical Discussion
Re: wallet.dat Recovery help! (Solved)
by
aqwark
on 01/07/2018, 13:49:36 UTC
hey i've had a lot of experience with recovering keys, I'm almost certain I could help you (as long as it's possible to recover).  Pm me your skype or something and we can have a live chat because it's easier to go back and forth.  At no point will you be at risk and I will source all of my advice from third parties.

I'll do it for free you can donate if you want but i enjoy helping people with things that are super niche like this. 

Before you hit me up, try a couple things. 

I AM REALLY SURE THE FOLLOWING WILL WORK FOR YOU.  It has a gui so no fucking around with command line shit.

https://github.com/prof7bit/wallet-key-tool/releases

I haven't found a better tool for getting keys from many types of wallets.  just run the .jar and load the .dat (make sure to select .dat filetype because it defaults to .wallet for multibit wallets).  It will load in every key (and ask for password if its encrypted). 

seriously i bet it would work with that. 

but pywallet can be weird.  Theres lots of different versions out there and the one i put in the pastebin below is the one that works for me.  put the wallet.dat on a flash drive, find the device name (on windows it would be like D:/ on unix it could be /dev/sda3 on mac /disk/disk2s3) and use pywallet recover.  It scans your storage device byte by byte looking for potential privkeys and you specify any passwords that might possibly decrypt the keys.  It outputs all the keys into a .dat file but also shows the keys as it goes through them in the console window.
https://pastebin.com/Uh5myMxM
I can walk you through what you need to do but it depends on what os you're on.  i would just get a debian live image to run it on to avoid any potential issues.  For some reason on my mac it doesnt actually put the keys into the wallet like it should.   

you just do python pywallet.py --recover --recov_device=*seebelow --recov_size=10Gio (uses french terms for sizes, ctrl+f within the code to see it, look at line 99.  Gio = Gb 1024 Mb Go for 1000Mb etc) --recov_outputdir=./

Like I said i'm happy to walk you through it.  the original pywallet is no longer on github but i think my copy is from somewhere on there, just make sure its the 345kb version not the 60kb version.  you can read through it to know theres no sketchy shit in it. 



Let me know how it goes.  I am almost certain that if its just a typical wallet.dat then the .jar should work.  That tool is a godsend.  It's  only for bitcoin so if you want to do litecoin, you have to convert the WIF key into it's bare hex key then redo the WIF conversion process with a different prefix.


1NQJycjngNzSxxDsoEv5fXEoW5K2qu8rXU if you feel enclined, but no need to.  pm me a means of live chatting.  you will not have to trust me at any point with anything sensitive, please google all instructions i give you to make sure i'm not pulling something.  there are bad people out there.


Hi Butense!

Need your help! You are my last hope
Please text me! skype - aqwark.
Post
Topic
Board Bounties (Altcoins)
Re: wallet.dat corrupt (bounty)
by
aqwark
on 29/06/2018, 13:38:21 UTC
hello

i need some help i got a wallet.dat from gulden from 2 year ago
i stored it on a USB
i have download a new gulden wallet and when it was done i have closed the wallet deleted the new wallet.dat and paste the new one

when i try to open the wallet it says
wallet.dat corrupt, salvage failed

the debug report say
2018-01-12 19:49:26 CDBEnv::Open: LogDir=D:\guldenblock\database ErrorFile=D:\guldenblock\db.log
2018-01-12 19:49:27 Failed to rename wallet.dat to wallet.some numbers.bak

what i think have go wrong is that i took the wallet.dat out without closing the program
this the only copy i got i already tried recuva

i tried python pywallet.py

when i try walletrecover program from bitcoin

without code i get this error
C:\pywallet>pywallet.py --datadir=C:\(folder where my wallet.dat is)\ --dumpwallet
Traceback (most recent call last):
  File "C:\pywallet\pywallet.py", line 5004, in
    db_env = create_env(db_dir)
  File "C:\pywallet\pywallet.py", line 1269, in create_env
    r = db_env.open(db_dir, (DB_CREATE|DB_INIT_LOCK|DB_INIT_LOG|DB_INIT_MPOOL|DB_INIT_TXN|DB_THREAD|DB_RECOVER))
bsddb.db.DBNoSuchFileError: (2, 'No such file or directory -- C:\\yourbkpwallet\\__db.001: No such file or directory')

and with what i guess is the right code i get this error
C:\pywallet>pywallet.py --passphrase=(MyCode) --datadir=C:\(folder where my wallet.dat is)\ --dumpwallet
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.

i think the bitcoin recovery script dont work on a wallet.dat from gulden
i know gulden is a fork of litecoin LTC
but i could not find any scripts for litecoin

so i dont know what to do anymore

i bought 60k coins few year ago and its worth a lot now so the one who can help me out will earn a good bounty

im a windows user


I have such a problem! Have you found a solution?