Topic: wallet password invalid after upgrade (Read 498 times)
im still wanting this to work, keeping this thread open
btc recover can brute force the password that is being used to encrypt the seed i.e. that seed: line in the wallet file. you could also build your own custom tool using something like hashcat.
2.7.18 can't sync with electrum servers anymore so that's why it's showing a blank history tab.
2.7.18 can't sync with electrum servers anymore so that's why it's showing a blank history tab.
So basically, I'm stuck here, with a ?corrupted wallet?, as my password functionality has broken, I must surrender my small fun money to lost seeds. using btc-recover on unsaved seeds is not really feasible right?
So, back on track.... I used 2.7.18, opened my only upgraded/current todays standards wallet, and electrum is just blank, password does not work as expected, seed unavailable.
as previously mentioned, I seem to know my password, as my previous tests show, but I may have to btc-recover the whole mess if cleanup of wallet is not possible.
cool to read the above stuff, but still wondering. thx
Lost in Electrum Land
as previously mentioned, I seem to know my password, as my previous tests show, but I may have to btc-recover the whole mess if cleanup of wallet is not possible.
cool to read the above stuff, but still wondering. thx
Lost in Electrum Land
If the HCP method doesn't work try to add /d parameter between cd and the directory path you want.
Here's the sample command below.
Now the directory should show something like this
If it is the right directory for the BTCrecovery.
Then after that to check if the btcrecover.py is on the same path use this command to show all files inside the directory.
Once you confirm that the btcrecover.py is on the list apply the command that suggested above.
Which is this below.
Now it should be work. If not update here and maybe you will need the same path of both python and the btcrecovery.py to put on the command. Or let me guide you through a screen mirror/sharing if needed.
Here's the sample command below.
Code:
cd /d d:\distr\btcrecover-master\btcrecover-master
Now the directory should show something like this
Code:
D:\distr\btcrecover-master\btcrecover-master>
If it is the right directory for the BTCrecovery.
Then after that to check if the btcrecover.py is on the same path use this command to show all files inside the directory.
Code:
dir
Once you confirm that the btcrecover.py is on the list apply the command that suggested above.
Which is this below.
Code:
python btcrecover.py --wallet default_wallet --tokenlist token.txt --typos-capslock --typos-swap --typos-repeat --typos-delete --typos-case --autosave savefile
Now it should be work. If not update here and maybe you will need the same path of both python and the btcrecovery.py to put on the command. Or let me guide you through a screen mirror/sharing if needed.
It seems that I did everything right ..
but I have such an error ...
C:\Users\user>CD d:\distr\btcrecover-master\btcrecover-master
C:\Users\user> C:\python27\python btcrecover.py --wallet default_wallet --tokenlist token.txt --typos-capslock --typos-swap --typos-repeat --typos-delete --typos-case --autosave savefile
C:\python27\python: can't open file 'btcrecover.py': [Errno 2] No such file or directory
The problem is that you are still in "C:\Users\user"...but I have such an error ...
C:\Users\user>CD d:\distr\btcrecover-master\btcrecover-master
C:\Users\user> C:\python27\python btcrecover.py --wallet default_wallet --tokenlist token.txt --typos-capslock --typos-swap --typos-repeat --typos-delete --typos-case --autosave savefile
C:\python27\python: can't open file 'btcrecover.py': [Errno 2] No such file or directory
Windows has this 'awesome' feature where you cannot use "CD" (Change Directory)... to change to a different drive and directory at the same time.
So your first command:
Quote
CD d:\distr\btcrecover-master\btcrecover-master
Simply changed the default starting location on D: in the background.
Try these commands one at a time:
Code:
D:
CD \distr\btcrecover-master\btcrecover-master
C:\python27\python btcrecover.py --wallet default_wallet --tokenlist token.txt --typos-capslock --typos-swap --typos-repeat --typos-delete --typos-case --autosave savefile
NOTE: After you use the "D:" command to switch to D: drive... Make sure that the prompt starts with "D:\>"
Also, make sure a copy of your "default_wallet" file is in the "d:\distr\btcrecover-master\btcrecover-master", otherwise btcrecover will fail saying that it can't find the wallet file.
I tried, all the same error
There seems to be an issue with python v2.7 when it comes with finding the correct directory?
Try to copy all of the contents of "btcrecover-master" into the root of python27 so both btcrecover and python use the same directory.
It should work.
Try to copy all of the contents of "btcrecover-master" into the root of python27 so both btcrecover and python use the same directory.
It should work.
It seems that I did everything right ..
but I have such an error ...
C:\Users\user>CD d:\distr\btcrecover-master\btcrecover-master
C:\Users\user> C:\python27\python btcrecover.py --wallet default_wallet --tokenlist token.txt --typos-capslock --typos-swap --typos-repeat --typos-delete --typos-case --autosave savefile
C:\python27\python: can't open file 'btcrecover.py': [Errno 2] No such file or directory
but I have such an error ...
C:\Users\user>CD d:\distr\btcrecover-master\btcrecover-master
C:\Users\user> C:\python27\python btcrecover.py --wallet default_wallet --tokenlist token.txt --typos-capslock --typos-swap --typos-repeat --typos-delete --typos-case --autosave savefile
C:\python27\python: can't open file 'btcrecover.py': [Errno 2] No such file or directory
Ok, thanks everyone, I'll try all of the above
BTW, I've tested a sample wallet with 1 lower-case letter typo and possible 2 missing numbers using the same setup:My test:
wallet file: bananapeal12
Password: bananapeal12
token file: bananapeal-token.txt
Contents:
Code:
bananapear
0
1
2
0
1
2
Command used: python btcrecover.py --wallet bananapeal12 --tokenlist bananapeal-tokens.txt --typos-replace %a --typos 2
Results:
Code:
C:\Python\Python27>python btcrecover.py --wallet bananapeal12 --tokenlist bananapeal-token.txt --typos-replace %a --typos 2
Starting btcrecover 0.17.10 on Python 2.7.17 64-bit, 16-bit unicodes, 32-bit ints
btcrecover.py: warning: can't find PyCrypto, using aespython instead
Wallet difficulty: 2 SHA-256 iterations
Counting passwords ...
Done
Using 4 worker threads
814676 of 2024605 [##############----------------------] 0:00:39, ETA: 0:00:58
Password found: 'bananapeal12'
Starting btcrecover 0.17.10 on Python 2.7.17 64-bit, 16-bit unicodes, 32-bit ints
btcrecover.py: warning: can't find PyCrypto, using aespython instead
Wallet difficulty: 2 SHA-256 iterations
Counting passwords ...
Done
Using 4 worker threads
814676 of 2024605 [##############----------------------] 0:00:39, ETA: 0:00:58
Password found: 'bananapeal12'
And I said above, you need more than 8GB of RAM if you want to bruteforce higher than 2 typos with that password length.
Ok, thanks everyone, I'll try all of the above
P.s. TC, sorry for the flood in topic
P.s. TC, sorry for the flood in topic
Can you help me with password recovery?
If yes, do you have any other way to contact you?
Just use BTCRecover, there's a tutorial on how to set it up, it's outdated but working.If yes, do you have any other way to contact you?
If you got any problem, create your own thread with the question and information (this is quite off-topic).
To get you started, after setting-up btcrecover, use this command:
Code:
python btcrecover.py --wallet wallet_name --tokenlist tokens.txt --typos-replace %a --typos 12
Change "wallet_name" into your wallet file's name, --typos-replace '%a' into '%A' if you think you've used uppercase& --typos' value depending on how many characters you think is wrong;
Take note: The higher the number of possible passwords, the higher RAM you will be needing.
And a 'tokens.txt' file in the same directory as btcrecover.py with the lines:
Code:
"possible_password"
1
7
1
7
It can be improved as I'm not an expert when it comes with btcrecover.
If you need help with the token file, there's also a guide on how to set it up: https://github.com/gurnec/btcrecover/blob/master/TUTORIAL.md#btcrecover-tutorial
Or typos: https://github.com/gurnec/btcrecover/blob/master/docs/Typos_Quick_Start_Guide.md
As for me, I can only bruteforce weak passwords (there's no other way to contact me),
you can contact this guy though: walletrecoveryservices He's got positive reviews and trust rating.
@Igrok222
Have you tried entering your password with CAPS LOCK turned on?
Are you maybe using a non-English keyboard that could have changed a few letters around, like the letters 'Z' and 'Y'
Maybe you disabled NUM LOCK so when you were setting up your password it didn't recognize your numbers (1/7).
Try with these options in mind and see if it helps.
Have you tried entering your password with CAPS LOCK turned on?
Are you maybe using a non-English keyboard that could have changed a few letters around, like the letters 'Z' and 'Y'
Maybe you disabled NUM LOCK so when you were setting up your password it didn't recognize your numbers (1/7).
Try with these options in mind and see if it helps.
I remember that when I created the password, when I re-entered, a password error appeared, maybe there was a typo in the password, I remember 2 options for the password that could be there (these are only letters, if there were numbers then this is only 1 or 7)
Can you help me with password recovery?
If yes, do you have any other way to contact you?
Can you help me with password recovery?
If yes, do you have any other way to contact you?
If it's encrypted, it will be hard to gain access to your funds even if he got the wallet file.
If it's strong (long, numerals, lower/upper-case letters & symbols) and you don't have an idea of the possible missing characters, it's almost impossible.
But it depends on how strong is your password because it's fairly easy to bruteforce a weak password like 8-character-password which is purely composed of numbers.
If it's strong (long, numerals, lower/upper-case letters & symbols) and you don't have an idea of the possible missing characters, it's almost impossible.
But it depends on how strong is your password because it's fairly easy to bruteforce a weak password like 8-character-password which is purely composed of numbers.
I have the same problem, but I am not good at it
Can anyone restore access to my wallet using my default_wallet file?
I did not save the password (if there was one), and the seed phrase is also lost
Can anyone restore access to my wallet using my default_wallet file?
I did not save the password (if there was one), and the seed phrase is also lost
TY for the clarification, I like learning the correct terms. 
I highly doubt I have a non-upgraded wallet file, but will look, and try that version either way. Thx again for the thoughts, you guys are the stuff legends are made of, helpful and smart. I had previously tried to reopen with 3.1.2, but wallet version was like already 18, too new.
so revise/downgrade the wallet, or maybe btc-recover, yet I seem to have already confirmed my password I think.
I highly doubt I have a non-upgraded wallet file, but will look, and try that version either way. Thx again for the thoughts, you guys are the stuff legends are made of, helpful and smart. I had previously tried to reopen with 3.1.2, but wallet version was like already 18, too new.
so revise/downgrade the wallet, or maybe btc-recover, yet I seem to have already confirmed my password I think.
Do you still have a virgin copy of the wallet file?
If you have, disable your internet, then create a copy of it and open the copy using Electrum version 2.7.18, then export your seed from it.
Download the previous releases here: https://download.electrum.org/
If you have, disable your internet, then create a copy of it and open the copy using Electrum version 2.7.18, then export your seed from it.
Download the previous releases here: https://download.electrum.org/
I go to see seed, it shows me the hashed stuff. -snip-
It's not hashed, it's your encrypted seed, in Base-64.
ok, weird......
(testA) I just d'l'd 3.3.4, and open my of my copies(enc), and it asked me for password to even open the wallet. it opens with my expected password. I go to see seed, it shows me the hashed stuff. The fact I could open the copy where I changed seed:enc to TRUE, opens with my expected password. WILD.
(testB) so then, I open 3.3.4 again, with a wallet copy(like orig);seed:enc=false, and it opens, but "password" still invalid, if I try to see my seeds or change password. what gives? Oh well, it's great to see different behavior, and at least re-assuring......
so this info is a valid test and all, right? the wallet does open in scenario A, but still doesn't allow me access to my funds..
is it possible these "wallet or hardware" type changes affected my wallet like this?
(testA) I just d'l'd 3.3.4, and open my of my copies(enc), and it asked me for password to even open the wallet. it opens with my expected password. I go to see seed, it shows me the hashed stuff. The fact I could open the copy where I changed seed:enc to TRUE, opens with my expected password. WILD.
(testB) so then, I open 3.3.4 again, with a wallet copy(like orig);seed:enc=false, and it opens, but "password" still invalid, if I try to see my seeds or change password. what gives? Oh well, it's great to see different behavior, and at least re-assuring......
so this info is a valid test and all, right? the wallet does open in scenario A, but still doesn't allow me access to my funds..
is it possible these "wallet or hardware" type changes affected my wallet like this?
BittMaxz, interesting. The original wallet was from around ~2014 as you stated, then my transactions show I used it last in 2016, but yes, the original version was likely very old. thanks for the info guys, I will have to try btc-recover I guess. I hope it works and there's not some other issue. I shouldn't have to have backup files, and I never forget passwords, but this lesson is one I get to learn again. I will try 3.3.4....
Jump to: