Pywallet 2.2: manage your wallet [Update required] - page 11.

elsteve

newbie

Activity: 8

Merit: 0

Quote from: jackjack on January 04, 2017, 07:30:38 PM

Quote from: qvqgg on January 03, 2017, 02:12:15 PM

Pywallet responds with 'Error with Dump Page'. What should I do ?

If it's a recent wallet it's because pywallet can't read them
It will handle them in the next version, no ETA though (a few weeks maybe)

Any update on this? I had a VM crash recently (it was running my Bitcoin Cash client - BitCoin Classic 64 bit) - I've recovered a ton of 'wallet.dat' files but as indicated above, Pywallet can't read 'em. (Verified this on a known good wallet from the client)

GummyDwarf

newbie

Activity: 36

Merit: 0

My friend dumped his wallet with pywallet, the wallet is corrupted, and there are way too many addresses to check by hand. Is there some way to check them all at once quickly?

morbius55

full member

Activity: 217

Merit: 109

Quote from: Osten on September 01, 2017, 10:17:06 AM

Quote from: morbius55 on September 01, 2017, 10:05:26 AM

How did you install this for windows 10 if you don't mind me asking?, Thanks. I really really need to run it on a corrupt wallet.dat that I have.

I followed this post here: https://bitcointalksearch.org/topic/m.13238007

For the command line stuff I ran PowerShell as administrator and used Set-Location instead of the Shift-Right Click stuff.

For example: Set-Location C:\Python27\Scripts

Hope this helps!

Thanks for the reply but I need someone to do a detailed run through for Windows 10 for a computer novice. Thanks again.

Osten

newbie

Activity: 4

Merit: 0

Quote from: morbius55 on September 01, 2017, 10:05:26 AM

How did you install this for windows 10 if you don't mind me asking?, Thanks. I really really need to run it on a corrupt wallet.dat that I have.

I followed this post here: https://bitcointalksearch.org/topic/m.13238007

For the command line stuff I ran PowerShell as administrator and used Set-Location instead of the Shift-Right Click stuff.

For example: Set-Location C:\Python27\Scripts

Hope this helps!

morbius55

full member

Activity: 217

Merit: 109

Quote from: Osten on September 01, 2017, 09:55:36 AM

Hi, I just found an old wallet from August 2011. I've tried using this tool to recover it and it creates the following files:

_db.001 24k
_db.002 64k
_db.003 264k
_db.004 96k
_db.005 512k
_db.006 48k
wallet.txt 0k

I couldn't find any information as to why it comes out as empty nor did I find any fix to this problem. I also tried using Bitcoin Core to recover it but it didn't work, and also tried bitcoin-qt 0.7.0 but it didn't work either. These are both newer than my wallet but I couldn't find any older clients anywhere.

Does this mean it's completely corrupt? Thankful for any help trying to recover this as I haven't found anyone else with this particular problem.

How did you install this for windows 10 if you don't mind me asking?, Thanks. I really really need to run it on a corrupt wallet.dat that I have.

Osten

newbie

Activity: 4

Merit: 0

Hi, I just found an old wallet from August 2011. I've tried using this tool to recover it and it creates the following files:

_db.001 24k
_db.002 64k
_db.003 264k
_db.004 96k
_db.005 512k
_db.006 48k
wallet.txt 0k

I couldn't find any information as to why it comes out as empty nor did I find any fix to this problem. I also tried using Bitcoin Core to recover it but it didn't work, and also tried bitcoin-qt 0.7.0 but it didn't work either. These are both newer than my wallet but I couldn't find any older clients anywhere.

Does this mean it's completely corrupt? Thankful for any help trying to recover this as I haven't found anyone else with this particular problem.

gnode

sr. member

Activity: 492

Merit: 250

Quote from: madmartyk on February 21, 2014, 08:09:06 AM

pywallet.py --dumpwallet --datadir g:\ --wallet=wallet.dat --recover --recov_device=g:\wallet.dat --recov_size=40Gio --recov_outputdir=c:\recover

This is what I used, if you want a file with the keys (what I did) add a >> dump.text at the end. You will see nothing on the screen but you have to enter newpassphrase, oldpassphrase, enter
It will scan the drive (make sure the ##Gio is bigger than the drive) and dump any keys it finds to the text file. You can then take the private keys and import them into a new wallet.

I did this on a corrupt wallet, it says I have 14,000 possible unencrypted keys. The wallet won't dump because it is corrupted. How do I see the unencrypted keys. The text file doesn't show any keys.

Thanks,

Gnode

rijsje91

newbie

Activity: 1

Merit: 0

Hello jackjack I've been redirected to the page to ask you for help. I have a problem i removed my wallet from cloakcoin and can not return it with pywallet Embarrassed. I have turned multiple scans but all I get is bitcoin keys and not my cloakcoin wallet. I have scanned with pywallet: pywallet.py --recover --recov_device c: --recov_size 240Gio --otherversion = 27 --recov_outputdir c: \ recu

The new wallet c:\recu/recovered_wallet_1498320264.dat contains the 300 recovere
d keys

-----------------------------------------------
This is with otherversion 28

Found 36 possible wallets
Found 13376 possible encrypted keys
Found 3196 possible unencrypted keys
Can't decrypt them as you didn't provide any passphrase.
Traceback (most recent call last):
File "pywallet.py", line 4875, in
db_env = create_env(options.recov_outputdir)
File "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.DBRunRecoveryError: (-30974, 'DB_RUNRECOVERY: Fatal error, run database
recovery -- c: No such file or directory')
-------------------------------------------------

I tried 27, 28 and 29 but without a result.
Can i search directly to a adress? I know the address I've deleted.

I hope you can help me.

Sincerely ,

Sven

tspacepilot

legendary

Activity: 1456

Merit: 1078

I may write code in exchange for bitcoins.

ice2097, did you try this tool? https://bitcointalk.org/index.php?topic=25091.0

It just loops through the file and tries to find concurrent sections which could be keys. Might be useful since you said the file isn't parseable as a wallet anymore.

ice2097

newbie

Activity: 7

Merit: 0

Quote from: HCP on June 22, 2017, 11:54:41 PM

Sorry for the delay... I suspect that either the wallet is badly corrupted or it is indeed encrypted and the password you are using is wrong, hence the script being unable to read it properly...

Especially in light of the message you're getting from current Bitcoin Core saying that it is corrupted.

I'm wondering if could be struggling with an old wallet format? What version of bitcoin-qt were you using originally with this wallet?

Yeah, I think it probably is a very old version... I think the wallet was started around 2011 or 2012, but I'm not positive.

HCP

legendary

Activity: 2086

Merit: 4314

Sorry for the delay... I suspect that either the wallet is badly corrupted or it is indeed encrypted and the password you are using is wrong, hence the script being unable to read it properly...

Especially in light of the message you're getting from current Bitcoin Core saying that it is corrupted.

I'm wondering if could be struggling with an old wallet format? What version of bitcoin-qt were you using originally with this wallet?

ice2097

newbie

Activity: 7

Merit: 0

Quote from: HCP on June 19, 2017, 09:30:37 PM

Have you tried specifying the full path to the wallet file rather than just . ?? It's possible that the script is attempting to parse this as a full path and may not be locating the file correctly? I haven't looked at the actual code to see how the script is handling the --datadir argument, so I'm not 100% sure of the format required here.

When I get home from work tonight I'll have a proper look and and a bit of a play around with it and see if I can replicate and/or figure out some more specific solutions for you.

Yeah, unfortunately I've tried the full path as well, and get the same response.
I don't think its an issue with the path, as if I put in an malformed path I get a different "bsddb.db.DBNoSuchFileError: (2, 'No such file or directory -- /Users/user/notpywallet/__db.001: No such file or directory')" error.

HCP

legendary

Activity: 2086

Merit: 4314

Quote from: ice2097 on June 18, 2017, 05:16:38 AM

Sorry I should have been more clear, I'm running this on a computer that doesn't have any bitcoin software installed, just the wallet.dat file from my old computer, and pywallet.
For the wallet dump the command I ran was:

$ python pywallet.py --datadir=./ --wallet=wallet.dat --dumpwallet --dumpwithbalance > keys.txt ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.

I've tried changing the permissions of the wallet file with chmod, and running the command as sudo to make sure its not a permissions issue, but it still gives the same response...

Have you tried specifying the full path to the wallet file rather than just . ?? It's possible that the script is attempting to parse this as a full path and may not be locating the file correctly? I haven't looked at the actual code to see how the script is handling the --datadir argument, so I'm not 100% sure of the format required here.

When I get home from work tonight I'll have a proper look and and a bit of a play around with it and see if I can replicate and/or figure out some more specific solutions for you.

matsmyth

member

Activity: 61

Merit: 10

Quote from: madmartyk on June 17, 2017, 03:51:18 PM

Have you tried to import the keys you have found?

I can't import because the program doesn't get that far. It literally crashes the moment after trying passphrase #1 on wallet #1, without any error message. So it never starts decrypting to create the wallet.dat. Only the partial, which only contains locations of the keys. I see another user, @Praxis, had the exact same problem earlier in this thread, and they were able to fix it, but he didn't mention how he got over that hump. And I haven't gotten a response yet via pm from him or jackjack.

silverkamote

newbie

Activity: 28

Merit: 0

nice software i wana try it. thanks

ice2097

newbie

Activity: 7

Merit: 0

Thanks for the fast replies!

Quote from: madmartyk on June 17, 2017, 03:51:18 PM

Have you tried to import the keys you have found?

No, sorry, I don't really understand the format of the output:
{'\x00\x01\x03key': [(Here there is a list of 142 comma-separated 5- and 6-digit numbers, in ascending value) ], '\t\x00\x01\x04mkey': [], 'PRFdevice': './wallet.dat', 'PRFsize': 139264, 'PRFdt': 0.02301478385125293, "'\x00\x01\x04ckey": []}

Is there something I can do with the list of 5/6 digit numbers?

Quote from: HCP on June 17, 2017, 11:55:52 PM

You likely need to use the following commandline options to get it to point to the wallet.dat you want to work on:

Sorry I should have been more clear, I'm running this on a computer that doesn't have any bitcoin software installed, just the wallet.dat file from my old computer, and pywallet.
For the wallet dump the command I ran was:

$ python pywallet.py --datadir=./ --wallet=wallet.dat --dumpwallet --dumpwithbalance > keys.txt ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.

I've tried changing the permissions of the wallet file with chmod, and running the command as sudo to make sure its not a permissions issue, but it still gives the same response...

Quote

Just as an FYI...
Recover is used when you're effectively scanning a drive to try and find accidentally deleted wallet files and/or keys... it probably isn't what you want to be using...
--recov_device needs to be set to a disk (ie. harddrive or maybe usb). The --recov_size is used to specify the size of the device in Gigabytes...

Ah good to know. Thanks for the clarification!

HCP

legendary

Activity: 2086

Merit: 4314

Quote from: ice2097 on June 17, 2017, 11:15:54 AM

I have the wallet.dat file in the same directory as pywallet.py
If I try to dump the wallet, I get:

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

By default... pywallet works on the default Bitcoin directory and wallet.dat file (Hence the error telling you to shut it down, it doesn't want to work on a "live" wallet).

You likely need to use the following commandline options to get it to point to the wallet.dat you want to work on:

Quote from: jackjack on August 03, 2011, 12:41:56 PM

Read a device to find deleted keys (CLI only)
- Assuming that:
  - The device you want to read is /dev/sda3
  - The size of /dev/sda3 is 30.1Gio
  - You want pywallet to write the new wallet containing the found keys in /home/jackjack/recovered_wallets
- Run "sudo ./pywallet.py --recover --recov_device /dev/sda3 --recov_size 30.1Gio --recov_outputdir /home/jackjack/recovered_wallets"
- Then replace your wallet (back it up before) with the recovered wallet and run "bitcoin -rescan"

--recov_device needs to be set to a disk (ie. harddrive or maybe usb). The --recov_size is used to specify the size of the device in Gigabytes...

madmartyk

legendary

Activity: 2674

Merit: 1030

Yes I am a pirate, 300 years too late!

Have you tried to import the keys you have found?

matsmyth

member

Activity: 61

Merit: 10

Quote from: madmartyk on June 16, 2017, 06:44:50 AM

Quote from: matsmyth on June 16, 2017, 02:00:04 AM

Quote from: matsmyth on April 18, 2017, 03:15:33 AM

Could anyone help? I did a photorec recovery of all .dat files from an old drive and put them on a flash drive. The pywallet recovery process gets this far but then just quits:

"Read 16.4 Go in 42.0 minutes

Found 21 possible wallets
Found 5850 possible encrypted keys
Found 843 possible unencrypted keys

Possible wallet #1
with passphrase #1 "

It just quits there. It does produce a pywallet_partial_recovery_xxx.dat file, but I cannot dump it or load it with any litecoin client.

Any assistance would be very appreciated.

^bump

at the end of your command line use a >text.txt
this will dump the info to a text file. You have to know what questions is asks because the screen doesn't echo.

@madmartyk

unfortunately it only dumps the exact same thing. no new info...

ice2097

newbie

Activity: 7

Merit: 0

I'm trying to recover an old bitcoin wallet.dat from ~2011 or so. I tried loading it with the current bitcoin-qt, and just get a "wallet.dat corrupt, salvage failed" error.
I didn't think I had a passphrase on my wallet, but I'm not positive.

I'm trying to use pywallet to get something usable out of the file, but I'm having some trouble and would really appreciate any help anyone here can provide.

I have the wallet.dat file in the same directory as pywallet.py
If I try to dump the wallet, I get:

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

If I try to recover, I get:

$ ./pywallet.py --recover --recov_size 30.1Gio --recov_device ./wallet.dat --recov_outputdir ./rec2/ Enter the passphrase for the wallet that will contain all the recovered keys: q Enter the possible passphrases used in your deleted wallets. Don't forget that more passphrases = more time to test the possibilities. Write one passphrase per line and end with an empty line. Possible passphrase: Starting recovery. Read 0.0 Go in 0.0 minutes Found 0 possible wallets Found 0 possible encrypted keys Found 141 possible unencrypted keys Segmentation fault: 11

at which point python crashes....
I'm not really clear on if these 141 keys should be useful or not... also I have no idea what the recov_size variable means, so this could be incorrect.

I'm not really sure where to go from here... any suggestions would be highly appreciated!

Topic: Pywallet 2.2: manage your wallet [Update required] - page 11. (Read 207945 times)