Search content
Sort by
Showing 3 of 3 results by Booth21209
Re: [Choose the new Pywallet name] - Pywallet 2.1.6: manage your wallet
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.
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 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.
Re: [Choose the new Pywallet name] - Pywallet 2.1.6: manage your 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?
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?
Re: [Choose the new Pywallet name] - Pywallet 2.1.6: manage your wallet
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.
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.