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

The easist way I have found is to extract everything to a .txt file and then reimport the keys.  I can go into more detail on what to do if you like.  I have helped recover a few wallets for myself and other people.  Haven't had any issues yet.

Hey, I dropped my laptop which caused the hard drive to be unpartitioned. It spent a week scanning and I was able to recover several wallet.dat files, but when I load them into the correct folder, it tells me "wallet.dat corrupt, salvage failed." Running with -rescan or -salvagewallet returns the same error.

It's very important to note that I also recovered some files called wallet.h, wallet_tests.cpp, walletdb.cpp, walletmodel.cpp, walletview.cpp, walletframe.h, and walletstack.h. It's almost as if the recovery split some C functions off of wither the qt program or wallet.dat itself. I'm not sure.

I'm getting an "Error in dump page" error when I try to dump the contents of my wallet. Bitcoin is not open. Here is the log. Can anyone help? I will tip. Thanks:

C:\>cd Python27

C:\Python27>pywallet.py --web
WARNING:root:pycrypto or libssl not found, decryption may be slow
'ecdsa' package is not installed, pywallet won't be able to sign/verify messages

2014-05-02 13:09:52-0400 [-] Log opened.
2014-05-02 13:09:52-0400 [-] Starting server: 2014-05-02 13:09:52.214000
2014-05-02 13:09:52-0400 [-] Site starting on 8989
2014-05-02 13:09:52-0400 [-] Starting factory at 0x026C83C8>
2014-05-02 13:09:55-0400 [HTTPChannel,0,127.0.0.1] 127.0.0.1 - - [02/May/2014:17
:09:54 +0000] "GET / HTTP/1.1" 200 231720 "-" "Mozilla/5.0 (Windows NT 6.1; WOW6
4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537.36"
2014-05-02 13:09:55-0400 [HTTPChannel,0,127.0.0.1] 127.0.0.1 - - [02/May/2014:17
:09:55 +0000] "GET /favicon.ico HTTP/1.1" 200 14 "-" "Mozilla/5.0 (Windows NT 6.
1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.131 Safari/537
.36"
2014-05-02 13:10:00-0400 [HTTPChannel,0,127.0.0.1] Wallet Dir: C:\Users\BlahBlah\AppData\Roaming\Bitcoin
2014-05-02 13:10:00-0400 [HTTPChannel,0,127.0.0.1] Wallet Name: wallet.dat
ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this
again.
2014-05-02 13:10:00-0400 [HTTPChannel,0,127.0.0.1] Unhandled Error
        Traceback (most recent call last):
          File "C:\Python27\lib\site-packages\twisted\web\http.py", line 826, in
 requestReceived
            self.process()
          File "C:\Python27\lib\site-packages\twisted\web\server.py", line 189,
in process
            self.render(resrc)
          File "C:\Python27\lib\site-packages\twisted\web\server.py", line 238,
in render
            body = resrc.render(self)
          File "C:\Python27\lib\site-packages\twisted\web\resource.py", line 250
, in render
            return m(request)
        --- ---
          File "C:\Python27\pywallet.py", line 3664, in render_GET
            read_wallet(json_db, create_env(wdir), wname, True, True, "", bal, v
ersion)
          File "C:\Python27\pywallet.py", line 2442, in read_wallet
            db = open_wallet(db_env, walletfile, writable=FillPool)
          File "C:\Python27\pywallet.py", line 2006, in open_wallet
            sys.exit(1)
        exceptions.SystemExit: 1

2014-05-02 13:10:00-0400 [HTTPChannel,0,127.0.0.1] 127.0.0.1 - - [02/May/2014:17
:09:59 +0000] "GET /DumpWallet?dir=C:\\Users\\Blah%Blah\\AppData\\Roami
ng\\Bitcoin&name=wallet.dat&bal=false&version=0 HTTP/1.1" 200 18 "http://localho
st:8989/" "Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like G
ecko) Chrome/34.0.1847.131 Safari/537.36"

Have you tried importing the private keys back into a blank wallet?  That has worked 95% of the time I have done it.

You should do a --recover of your damaged partition. I also accidentally formatted my only backup with wallets. Once the wallets are recovered with recover software like Recuva,... they seem to get damaged in some way. I am still not finished recovering them completely, but --recover is the first step.

What I used is:

pywallet.py --recover --recov_size 931Gio --recov_device f: --recov_outputdir d:\recovered


It will ask you then to put in a new password (for the finished encrypted wallet.dat). That is where I found a bug. Whatever password I chose, at the end I am able to get my coins to show up, but I cannot send them because the password I chose when starting the --recover does not get accepted. First I thought I misspelled something and started the whole process again. Each time it takes about 6 hours... But even when I was absolutely correct with my password, it still would not accept the password at the specific wallet for decryption.

Is there another step I can do?

I also tried the --dumpwallet command with the recovered wallet, but I am not able to find the correct address that was used on the wallet I am trying to recover.

pywallet.py --dumpwallet --datadir d:\recovered --wallet wallet.dat --otherversion=34 > dump.txt

(I have tried otherversions 34 - 37)


That lists all key pairs, but none of them is the correct one I am looking for. What am I doing wrong? Obviously the right keys must be in the recovered wallet, as I am able to see the correct balance once I am doing the -rescan command. But when I am specifically looking for the address and it's private key, I am unsuccessful.


Can somebody point me to the right path?

hello.. im stuck in recovering a dogecoin wallet!

i write /home/myname/Desktop/pywallet.py --datadir=/home/myname/Desktop/ --wallet=wallet.dat --dumpwallet

(both files are in desktop folder)

but i get a error message ERROR:root:Couldn't open wallet.dat/main. Try quitting Bitcoin and running this again.

i havent any bitcoin or derivates running. someone can help in telling me if im or the file is too much damaged?

i damaged my windows partition and this is a file recovered by a file recovery software. the wallet says is corrupted

If you want generics on useage there is this:
http://www.devtome.com/doku.php?id=pywallet

also at the bottom of the first post of this very thread:
https://bitcointalksearch.org/topic/m.424586

for specific case needs there is the amazing Google search.

and if you have a specific problem you may able to get better help, if you actually post specifics of your problem, like:

• What syntax error?
• Doing what?
• Trying to do what?
• Steps?

Moreover, I am sure that you are more then welcome, by the author and the community at large, to ultimately write or paste a guide of your liking and satisfaction.

And anyway even about that I do not understand what you are looking for... again... step by step guide for what?... bulletproof guide for what?... usage, installation, integration... your post is so vague that this is probably the only reply you will receive until you explain yourself more clearly and detailed.

Does anybody have astep by step guide. Ones i have tried doesnt seem to work.

Install software, etc and try and run cmnd lines but just syntax errors and other problems.

Is there a bulletproof idiot guide at all.

Thanks.

Almost everything work fine when I use the CLI, but I have a problem with the web interface which I would like to use for simplicity and curiosity.
When I try to use it, this is what it shows in the browser:

and this is on the console:



EDIT (after more testing...)
This is mainly happening in IPython with the %run magic; also causing the IPython instance to not function correctly after pywallet.py is interrupted by CTRL+C or forcing a quit by directing the browser to 'http://localhost:8989/quit.'
Control and escaped characters can be noticed at its prompt:

http://i.imgur.com/YrFrD1bl.png

But instead, if we call the pywallet.py from the actual python executable called as a escaped IPython console command instance. by '!python(.exe) pywallet.py --web', then in this nested-Russian-Dolls-mode everything works.
... not optimal, since almost all of the IPython feature are defeated, but it works.

So could anybody help troubleshoot and fix this?  

The "--version" CLI option does not return the correct info... I don't know if you want me to file a bug report: then where? Or clone your GIT repo apply changes and push? Or just tell you here the correction:

Ask or check your addresses and use any of these charts:

http://cryptolife.net/upwg/
https://en.bitcoin.it/wiki/List_of_address_prefixes

If someone wants to fix my wallet, I'll give you 0.5btc (quick almost 300$ for most of you). It only has 2.8btc on it (possibly more)

Looking for trusted members only, you have to have good rep and I gotta see what you're doing via teamviewer.

PM me.

I would do this myself but it keeps fucking up.

Is it really required to run -rescan every time I want to remove unconfirmed transactions? I did it today on my desktop, and a few hours later the thing is still scanning! Any way to get around this? How handle businesses this downtime?

FYI:

I solved my problem with the 2000 tiny transactions - without pywallet, by scripted sending of ~50 small transactions.

Here's today's logbook ... what an interesting day - problems are great :-)
https://bitcointalksearch.org/topic/m.5396066

and below it my script that solved it.

I have tried this, but whenever I use the --dumpwallet function, it says that Bitcoin-QT is running and needs to be closed.


The Bitcoin-QT is not running, so I think it might just be that the wallet is too corrupted to salvage using pywallet  


As far as I can tell, my only hope is to take the hex that is in the file and find some way to extract the keys from my encrypted wallet. So if anyone can tell how to decrypt the wallet (I have the passphrase) without the Litecoin-QT, then what string of bytes to look for, that would be great.


Thanks to everyone for all the help, though.

Is there an elegant way in your pywallet to solve that?

I have not yet used pywallet - perhaps that this happens to me means that I should start to look into it now?  :-)


More details there:
https://bitcointalksearch.org/topic/m.5378737

It must be a well known problem.

I guess I understand where it comes from - but not how to solve it.

Perhaps by "renormalization"?  Make 100 tx of 20 inputs, then 5 tx of 20 inputs? then 1 tx of 5 inputs? Ready?  
Do you have such a scrypt? What are good numbers to try with?

Hi I am seeking some help

What is the version for LTC addresses?

I found out the 55 is the volume number for PPC.

Also how do you point the pywallet at different block chains.

when you want to check and address e.g. LTC and PPC.

How can you make a transaction with pywallet can this be done?

Thank you in advance.
I think

DogeCoin is volume 30
LTC is volume 48
PPC is volume 55

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.

So I did that and it gave me access to the f: drive (my thumb drive), but if I directed it to a specific folder in f:, it said permission denied again.

Scanning the whole drive worked, though, and returned 0 keys. Even when I gave it the correct passphrase for the encrypted.

Although, I still have not given up hope.

When I was looking at the hex for the file, I found alot of lines that begin and end with the same series of bytes.

If these are my encrypted wallet keys (all keys begin and end with the same bytes, right?), would I be able to decrypt them with my passphrase?

I used pywallet to recover my wallets for piratecoin, batcoin, klondikecoin and a bunch others.  I had a bunch of corrupt wallets, what worked best for me is to format a small thumb drive.  Drop the wallet file on it, and scan the drive for keys.  Long process, but it worked like a champ.  Wrote a batch file to put the private kays back into a new wallet and everything was back. 
Got to thank JackJack for providing this tool, and the millions of threads around the internet for different ways of using it!!

Hello JackJack,

Sorry if there is a better way to go about asking you for help, but.......

For some reason, whenever I attempt to run pywallet --recover (with all the other parameters, and the correct passphrase for the encrypted wallet) in my %appdata% folder, it tells me that it pops out an "Error (13, Permission Denied)" and tells me it can't access any of the directories on my HDD.


Although, if I point it directly towards one of the recovered wallet.dat files that I retrieved using Recuva (they had been deleted on Feb.7th due to a system refresh that did not create a windows.old folder for me to restore my Appdata for reasons unbeknownst), no matter what --passphrase I use, it tells me that it was correct and that 0 keys were found.


I was forced to use the recovery option in the first place because I was not able to dump the private keys from the recovered wallets (it told me that Bitcoin-qt was running and that I needed to shut it down, even though I have Litecoins), although I could recover the keys fine from a brand new wallet. So I assumed that that meant the wallets are damaged beyond repair and I just need to let the recovery brute force the keys. The problem is, though, that pywallet somehow is not being given access, even though I am the admin, and have even given the ownership of the entire c: drive to my user account. I input the recovery parameters for pywallet according to what you posted earlier (adjusting the recover size from 30gb, putting in my User directory, and adding --otherversion=48 because these are litecoins) to no avail.


the strangest thing about all of this is when I used --dumpwallet, pywallet had to have been able to gain access to my C:\ drives otherwise  it wouldn't have been able to extract any keys from the fresh wallet.dat that I created to make sure that pywallet was working.


Sorry for the wall of text, I hope this is sufficient enough, the only debug info I have gotten is that it thought that bitcoin-qt was still on, and that it cannot access my C:\ drive.