Recovery Phrase Not Working - $200 Reward

[elliesama]

I'm completely baffled by the events that occurred a few days ago. For one, I tried to send a transaction and I kept clicking confirm on the ledger then before I knew it the device was reset (I did not type the PIN wrong 3 times). I simply clicked confirm transaction but it still didn't go through.

I figured I was fine as I had the 24 word recovery phrase but I tried it out and it did not work whatsoever. I have all 24 words.

Things to note:
- All words are on the english.txt list.
- I used seedrecover.py and my xpub key from Ledger Live to check if there was 1 big typo (one completely different word) and no luck
- I'm going to try 2 but it will take a significant amount of time and I'm still confused as to how I passed the second verification step if the words I have written down were not in order.

Starting to lose hope.

[1715234175]

1715234175

[1715234175]

1715234175

[1715234175]

1715234175

[1715234175]

1715234175

[1715234175]

1715234175

[HCP]

I'm completely baffled by the events that occurred a few days ago. For one, I tried to send a transaction and I kept clicking confirm on the ledger then before I knew it the device was reset (I did not type the PIN wrong 3 times). I simply clicked confirm transaction but it still didn't go through.

Never heard of a device resetting itself unless you enter the wrong PIN... very odd.

I figured I was fine as I had the 24 word recovery phrase but I tried it out and it did not work whatsoever. I have all 24 words.

How did it "not work"? Did the wallet say it was an invalid seed? or did it just generate an empty wallet?

Also, did you utilise the "2nd PIN" option and/or extra passphrase option that Ledger provides? Refer: https://support.ledger.com/hc/en-us/articles/115005214529-Advanced-passphrase-security

[elliesama]

I'm completely baffled by the events that occurred a few days ago. For one, I tried to send a transaction and I kept clicking confirm on the ledger then before I knew it the device was reset (I did not type the PIN wrong 3 times). I simply clicked confirm transaction but it still didn't go through.

Never heard of a device resetting itself unless you enter the wrong PIN... very odd.

I figured I was fine as I had the 24 word recovery phrase but I tried it out and it did not work whatsoever. I have all 24 words.

How did it "not work"? Did the wallet say it was an invalid seed? or did it just generate an empty wallet?

Also, did you utilise the "2nd PIN" option and/or extra passphrase option that Ledger provides? Refer: https://support.ledger.com/hc/en-us/articles/115005214529-Advanced-passphrase-security

It said it was an invalid seed and to my knowledge I did not go in and enable any extra options.

[HCP]

It said it was an invalid seed and to my knowledge I did not go in and enable any extra options.

It would seem that you have copied one (or more) of the words down incorrectly.

I would advise to check each of your 24 words against this list: https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt

If you find a word that isn't on that list, have a look for very similar words... If that doesn't help, you'll need to use seedrecovery.py.

- I used seedrecover.py and my xpub key from Ledger Live to check if there was 1 big typo (one completely different word) and no luck

NOTE: the default version of seedrecovery.py will ONLY work with older legacy ("1" addresses)... and, unfortunately, Ledger Live defaults to using "3-type" (p2wpkh-p2sh) addresses these days. However, the good news is that there is a version of seedrecovery.py that works with SegWit addresses.

The pull request hasn't been accepted into the main btcrecover repo as yet... but you can find the modified version that supports the p2wpkh-p2sh (3-type) addresses here: https://github.com/madacol/btcrecover

Also, I'd say that the "xpub" you get from Ledger Live probably isn't the best way to search either... I'd suggest searching for a known address from Ledger Live (perhaps look through your transaction history and pick the first "3" address from your first transaction). The reason why is that you're using p2wpkh-p2sh addresses, which should be generated from a "ypub"... but Ledger Live still exports it as an "xpub"... and i don't think seedrecovery.py will generate the test addresses correctly.

[Pmalek]

If you typed the words by hand check for common mistakes that can happen like:

Mistakenly typing the letter 'u' to look like an 'a' by hand. I've seen people do that where both letters are almost identical. Instead of clump you might be entering clamp instead.

Mistakenly typing the letter 'q' to look like a 'g'. I can't think off an existing word where you can replace these two letters but they look similar when you write it down so it might be possible to get it wrong.

[Lucius]

Actually there is another way to reset Nano S, it can be done from device menu -> Settings->Device->Reset all. But this option requests that such request is approved with PIN. Since OP is claim that he is only try to confirm transaction and he "kept clicking confirm" there is probably some unknown combination of button clicks which may result in resetting the device. I also have not found even one such case, so this is something completely new.

elliesama, I know you have problem with your seed also, but it would be good to report resetting problem to Ledger support, maybe something is wrong with your device. Although not recommended, but you can test your seed in some desktop wallet, just be 100% sure that it is not fake wallet.

[elliesama]

Actually there is another way to reset Nano S, it can be done from device menu -> Settings->Device->Reset all. But this option requests that such request is approved with PIN. Since OP is claim that he is only try to confirm transaction and he "kept clicking confirm" there is probably some unknown combination of button clicks which may result in resetting the device. I also have not found even one such case, so this is something completely new.

elliesama, I know you have problem with your seed also, but it would be good to report resetting problem to Ledger support, maybe something is wrong with your device. Although not recommended, but you can test your seed in some desktop wallet, just be 100% sure that it is not fake wallet.

Wait which seed? Also if I made payments and received payments through Ledger Live doesn't that mean it's 100% authentic, (I did buy it off a friend).

When I made a new wallet and tested the seed with a online desktop it worked, so I have no idea what went wrong.

It said it was an invalid seed and to my knowledge I did not go in and enable any extra options.

It would seem that you have copied one (or more) of the words down incorrectly.

I would advise to check each of your 24 words against this list: https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt

If you find a word that isn't on that list, have a look for very similar words... If that doesn't help, you'll need to use seedrecovery.py.

- I used seedrecover.py and my xpub key from Ledger Live to check if there was 1 big typo (one completely different word) and no luck

NOTE: the default version of seedrecovery.py will ONLY work with older legacy ("1" addresses)... and, unfortunately, Ledger Live defaults to using "3-type" (p2wpkh-p2sh) addresses these days. However, the good news is that there is a version of seedrecovery.py that works with SegWit addresses.

The pull request hasn't been accepted into the main btcrecover repo as yet... but you can find the modified version that supports the p2wpkh-p2sh (3-type) addresses here: https://github.com/madacol/btcrecover

Also, I'd say that the "xpub" you get from Ledger Live probably isn't the best way to search either... I'd suggest searching for a known address from Ledger Live (perhaps look through your transaction history and pick the first "3" address from your first transaction). The reason why is that you're using p2wpkh-p2sh addresses, which should be generated from a "ypub"... but Ledger Live still exports it as an "xpub"... and i don't think seedrecovery.py will generate the test addresses correctly.

So you're saying that the results I got with the xpub from Ledger Live could potentially be inaccurate? I will go ahead and try the modified version. Thanks for the help! And yes as I mentioned in the thread I crosschecked each word and all were on the list.

If you typed the words by hand check for common mistakes that can happen like:

Mistakenly typing the letter 'u' to look like an 'a' by hand. I've seen people do that where both letters are almost identical. Instead of clump you might be entering clamp instead.

Mistakenly typing the letter 'q' to look like a 'g'. I can't think off an existing word where you can replace these two letters but they look similar when you write it down so it might be possible to get it wrong.

That's where I figured seedrecover.py --big-typos 1 would cover but if, as the other user mentioned, I was testing wrong then that may be the case. Cause it baffles me that all words are on the list and I doubt the ordering is wrong otherwise I wouldn't have passed the second checkpoint.

[HCP]

Question for you... did you write your 24 words on the "official" Ledger recovery sheet?

I'm wondering if you wrote them on the card as:
1   2
3   4
5   6
...
19 20
21 22
23 24

But they should be written on the card as:
1  13
2  14
3  15
...
10 22
11 23
12 24

But at the time you first set it up and did the second checkpoint you knew which way you had written it down and so re-entered it in correct order... but now that time has passed, you've just entered them in the number order as written on the card?

Just another possibility to consider... as I know of one user who did exactly this.

And yes as I mentioned in the thread I crosschecked each word and all were on the list.

It's quite possible you also have the "similar word" issue... kit vs. kite... kid vs kind etc...

[bob123]

Wait which seed? Also if I made payments and received payments through Ledger Live doesn't that mean it's 100% authentic, (I did buy it off a friend).

What do you mean with 'authentic' ?

You did generate the seed yourself, right ? If not, regard the seed as compromised and move your funds to a new one (generated by you) as soon as possible.

When I made a new wallet and tested the seed with a online desktop it worked, so I have no idea what went wrong.

And you are 100% sure that you used that exact mnemonic code ?
You might try entering it into a desktop wallet again. But regard that seed as compromised afterwards. If you will be able to access your coins, move them to a new seed.

But i doubt it will be accepted as a valid seed in a different wallet, if the nano s doesn't accept it.

[Lucius]

Wait which seed? Also if I made payments and received payments through Ledger Live doesn't that mean it's 100% authentic, (I did buy it off a friend).
When I made a new wallet and tested the seed with a online desktop it worked, so I have no idea what went wrong.

You should just have one seed from Nano S, and that seed should be your backup. If you put that 24 words in any supported wallet (hardware, desktop or mobile) then your wallet will be recovered. Fact that you use Nano S with Ledger Live does not necessarily mean that you have the correct seed, device can be used only if you have access to it, respectively correct PIN.

You say that you bought Nano S from friend, is that new or used device, did you reset it and set new seed / PIN? Than new wallet in which you test seed is Ledger Live seed checker or some other wallet?

[elliesama]

Question for you... did you write your 24 words on the "official" Ledger recovery sheet?

I'm wondering if you wrote them on the card as:
1   2
3   4
5   6
...
19 20
21 22
23 24

But they should be written on the card as:
1  13
2  14
3  15
...
10 22
11 23
12 24

But at the time you first set it up and did the second checkpoint you knew which way you had written it down and so re-entered it in correct order... but now that time has passed, you've just entered them in the number order as written on the card?

Just another possibility to consider... as I know of one user who did exactly this.

And yes as I mentioned in the thread I crosschecked each word and all were on the list.

It's quite possible you also have the "similar word" issue... kit vs. kite... kid vs kind etc...

Yeah sadly I didn't use the official Ledger sheet, I just used a notecard and wrote it left to right. It could be the second one but I thought seedrecover.py would figure that issue out.

Wait which seed? Also if I made payments and received payments through Ledger Live doesn't that mean it's 100% authentic, (I did buy it off a friend).
When I made a new wallet and tested the seed with a online desktop it worked, so I have no idea what went wrong.

You should just have one seed from Nano S, and that seed should be your backup. If you put that 24 words in any supported wallet (hardware, desktop or mobile) then your wallet will be recovered. Fact that you use Nano S with Ledger Live does not necessarily mean that you have the correct seed, device can be used only if you have access to it, respectively correct PIN.

You say that you bought Nano S from friend, is that new or used device, did you reset it and set new seed / PIN? Than new wallet in which you test seed is Ledger Live seed checker or some other wallet?

Yeah I did reset it with a new seed / PIN. And when I created the new wallet to test I tested with MyEtherWallets/BIP39 websites mnemonic phrase section and it worked.

Wait which seed? Also if I made payments and received payments through Ledger Live doesn't that mean it's 100% authentic, (I did buy it off a friend).

What do you mean with 'authentic' ?

You did generate the seed yourself, right ? If not, regard the seed as compromised and move your funds to a new one (generated by you) as soon as possible.

When I made a new wallet and tested the seed with a online desktop it worked, so I have no idea what went wrong.

And you are 100% sure that you used that exact mnemonic code ?
You might try entering it into a desktop wallet again. But regard that seed as compromised afterwards. If you will be able to access your coins, move them to a new seed.

But i doubt it will be accepted as a valid seed in a different wallet, if the nano s doesn't accept it.

Sorry if I'm making it confusing but essentially I am still unable to utilize my 24 word passphrase to access my coins again. Making a new wallet on the Ledger was just confirmation for myself to see if the seed it generated would work on a desktop wallet.

It said it was an invalid seed and to my knowledge I did not go in and enable any extra options.

It would seem that you have copied one (or more) of the words down incorrectly.

I would advise to check each of your 24 words against this list: https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt

If you find a word that isn't on that list, have a look for very similar words... If that doesn't help, you'll need to use seedrecovery.py.

- I used seedrecover.py and my xpub key from Ledger Live to check if there was 1 big typo (one completely different word) and no luck

NOTE: the default version of seedrecovery.py will ONLY work with older legacy ("1" addresses)... and, unfortunately, Ledger Live defaults to using "3-type" (p2wpkh-p2sh) addresses these days. However, the good news is that there is a version of seedrecovery.py that works with SegWit addresses.

The pull request hasn't been accepted into the main btcrecover repo as yet... but you can find the modified version that supports the p2wpkh-p2sh (3-type) addresses here: https://github.com/madacol/btcrecover

Also, I'd say that the "xpub" you get from Ledger Live probably isn't the best way to search either... I'd suggest searching for a known address from Ledger Live (perhaps look through your transaction history and pick the first "3" address from your first transaction). The reason why is that you're using p2wpkh-p2sh addresses, which should be generated from a "ypub"... but Ledger Live still exports it as an "xpub"... and i don't think seedrecovery.py will generate the test addresses correctly.

I grabbed a few addresses from my Ledger Live transactions but it said it wasn't a valid Bitcoin P2PKH address.

------------------

Okay update. I made a new wallet on Ledger Nano S with a new seed and I got the xpub key from Ledger Live. I ran seedrecover.py by taking out one word from the seed and it couldn't find it, so perhaps I did miswrite something in the original. Not sure why seedrecover.py isn't working properly.

[HCP]

I grabbed a few addresses from my Ledger Live transactions but it said it wasn't a valid Bitcoin P2PKH address.
------------------
Okay update. I made a new wallet on Ledger Nano S with a new seed and I got the xpub key from Ledger Live. I ran seedrecover.py by taking out one word from the seed and it couldn't find it, so perhaps I did miswrite something in the original. Not sure why seedrecover.py isn't working properly.

OK... my bad... I forgot that madacol's "master" branch was actually just default btcrecover!!?!   ... So, you need to switch to the "p2wpkh-p2sh" branch first, THEN download the .ZIP file from github:



Apologies for that!   

You also need to specify a non-default derivation path... as seedrecovery defaults to m/44'/0'/0'/0 and you need m/49'/0'/0'/0

So, I just ran a quick test using a 24 word seed generated on Ian Coleman's mnemonic code converter.

Code: (Original 24 word seed)

version vanish add search lucky polar buddy wasp image trophy bright educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy

Code: (generated addresses)

m/49'/0'/0'/0/0	3QpdYZkyW6a5GGFVVGAQRprvNfkUWfiSc6
m/49'/0'/0'/0/1	3KRsYk5aQVPELD8x6MCDDJLb5EPsZr7bvZ
m/49'/0'/0'/0/2	37g3kfip54i91YSS9KSPhQkaFPxr95unfB
m/49'/0'/0'/0/3	38p4SgCkDNGRjWNzUmZyoaAEejbsfvHgkj
m/49'/0'/0'/0/4	31wz2V9aRvSn4zmQGSxTdEuwoyHSQikPHb

Code: (Missing one word)

version vanish add search lucky polar buddy wasp image trophy educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy

Code: (seedrecovery.py commandline (running on Windows))

python .\seedrecover.py --wallet-type bip39 --addrs 31wz2V9aRvSn4zmQGSxTdEuwoyHSQikPHb --addr-limit 5 --mnemonic-length 24 --mnemonic-prompt --bip32-path "m/49'/0'/0'/0"

Gives this output:

Code:

PS C:\Crypto\btcrecover-p2wpkh-p2sh> python .\seedrecover.py --wallet-type bip39 --addrs 31wz2V9aRvSn4zmQGSxTdEuwoyHSQikPHb --addr-limit 5 --mnemonic-length 24 --mnemonic-prompt --bip32-path "m/49'/0'/0'/0"
Starting seedrecover 0.7.3, btcrecover 0.17.10 on Python 2.7.15 64-bit, 16-bit unicodes, 32-bit ints
terminal does not support UTF; mnemonics with non-ASCII chars might not work
Please enter your best guess for your mnemonic (seed)
> version vanish add search lucky polar buddy wasp image trophy educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy
Using the 'en' wordlist.
Seed sentence was too short, inserting 1 word into each guess.
Phase 1/3: up to 2 mistakes, excluding entirely different seed words.
Not enough entirely different seed words permitted; skipping this phase.
Seed not found
Phase 2/3: 1 mistake which can be an entirely different seed word.
Using 4 worker threads
20695 of 49129 [################-----------------------] 0:00:00, ETA:  0:00:00
Seed found: version vanish add search lucky polar buddy wasp image trophy bright educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy

Addtionally, you *might* actually be able to also use the "xpub" from Ledger Live instead of using addresses... Out of curiosity, I ran a quick test that seems to indicate it will work OK

Code: (seedrecovery.py commandline (running on Windows))

python .\seedrecover.py --wallet-type bip39 --mpk xpub6DBZvWvR1bgKmk6k5JvweNRD1QhKXzGroqZWAETadaz5BWauEGwptwn4o2jeFknZxKhe9dCA9NYk1TfjPiesg5tJG6xF5ymBogS8fHKVsiL --mnemonic-length 24 --mnemonic-prompt --bip32-path "m/49'/0'/0'/0"

yielded:

Code:

PS C:\Crypto\btcrecover-p2wpkh-p2sh> python .\seedrecover.py --wallet-type bip39 --mpk xpub6DBZvWvR1bgKmk6k5JvweNRD1QhKXzGroqZWAETadaz5BWauEGwptwn4o2jeFknZxKhe9dCA9NYk1TfjPiesg5tJG6xF5ymBogS8fHKVsiL --mnemonic-length 24 --mnemonic-prompt --bip32-path "m/49'/0'/0'/0"
Starting seedrecover 0.7.3, btcrecover 0.17.10 on Python 2.7.15 64-bit, 16-bit unicodes, 32-bit ints
terminal does not support UTF; mnemonics with non-ASCII chars might not work
Please enter your best guess for your mnemonic (seed)
> version vanish add search lucky polar buddy wasp image trophy educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy
xpub depth:       3
xpub fingerprint: D04C4361
xpub child #:     0'
Using the 'en' wordlist.
Seed sentence was too short, inserting 1 word into each guess.
Phase 1/3: up to 2 mistakes, excluding entirely different seed words.
Not enough entirely different seed words permitted; skipping this phase.
Seed not found
Phase 2/3: 1 mistake which can be an entirely different seed word.
Using 4 worker threads
20695 of 49129 [################-----------------------] 0:00:00, ETA:  0:00:00
Seed found: version vanish add search lucky polar buddy wasp image trophy bright educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy

NOTE: For this test, I used the "Account Extended Public Key" ypub from the BIP49 tab on Ian Coleman, and ran it through the converter here: https://jlopp.github.io/xpub-converter/ to convert to an the xpub. (The xpub from Ian Coleman BIP44 tab is actually different and didn't work). However, this converter seems to supply the same "xpub" that Ledger Live provides... which would imply that Ledger Live is doing a similar ypub to xpub conversion.


Good Luck! 

[elliesama]

I grabbed a few addresses from my Ledger Live transactions but it said it wasn't a valid Bitcoin P2PKH address.
------------------
Okay update. I made a new wallet on Ledger Nano S with a new seed and I got the xpub key from Ledger Live. I ran seedrecover.py by taking out one word from the seed and it couldn't find it, so perhaps I did miswrite something in the original. Not sure why seedrecover.py isn't working properly.

OK... my bad... I forgot that madacol's "master" branch was actually just default btcrecover!!?!   ... So, you need to switch to the "p2wpkh-p2sh" branch first, THEN download the .ZIP file from github:
https://i.imgur.com/Ble0iue.png


Apologies for that!    

You also need to specify a non-default derivation path... as seedrecovery defaults to m/44'/0'/0'/0 and you need m/49'/0'/0'/0

So, I just ran a quick test using a 24 word seed generated on Ian Coleman's mnemonic code converter.

Code: (Original 24 word seed)

version vanish add search lucky polar buddy wasp image trophy bright educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy

Code: (generated addresses)

m/49'/0'/0'/0/0	3QpdYZkyW6a5GGFVVGAQRprvNfkUWfiSc6
m/49'/0'/0'/0/1	3KRsYk5aQVPELD8x6MCDDJLb5EPsZr7bvZ
m/49'/0'/0'/0/2	37g3kfip54i91YSS9KSPhQkaFPxr95unfB
m/49'/0'/0'/0/3	38p4SgCkDNGRjWNzUmZyoaAEejbsfvHgkj
m/49'/0'/0'/0/4	31wz2V9aRvSn4zmQGSxTdEuwoyHSQikPHb

Code: (Missing one word)

version vanish add search lucky polar buddy wasp image trophy educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy

Code: (seedrecovery.py commandline (running on Windows))

python .\seedrecover.py --wallet-type bip39 --addrs 31wz2V9aRvSn4zmQGSxTdEuwoyHSQikPHb --addr-limit 5 --mnemonic-length 24 --mnemonic-prompt --bip32-path "m/49'/0'/0'/0"

Gives this output:

Code:

PS C:\Crypto\btcrecover-p2wpkh-p2sh> python .\seedrecover.py --wallet-type bip39 --addrs 31wz2V9aRvSn4zmQGSxTdEuwoyHSQikPHb --addr-limit 5 --mnemonic-length 24 --mnemonic-prompt --bip32-path "m/49'/0'/0'/0"
Starting seedrecover 0.7.3, btcrecover 0.17.10 on Python 2.7.15 64-bit, 16-bit unicodes, 32-bit ints
terminal does not support UTF; mnemonics with non-ASCII chars might not work
Please enter your best guess for your mnemonic (seed)
> version vanish add search lucky polar buddy wasp image trophy educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy
Using the 'en' wordlist.
Seed sentence was too short, inserting 1 word into each guess.
Phase 1/3: up to 2 mistakes, excluding entirely different seed words.
Not enough entirely different seed words permitted; skipping this phase.
Seed not found
Phase 2/3: 1 mistake which can be an entirely different seed word.
Using 4 worker threads
20695 of 49129 [################-----------------------] 0:00:00, ETA:  0:00:00
Seed found: version vanish add search lucky polar buddy wasp image trophy bright educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy

Addtionally, you *might* actually be able to also use the "xpub" from Ledger Live instead of using addresses... Out of curiosity, I ran a quick test that seems to indicate it will work OK

Code: (seedrecovery.py commandline (running on Windows))

python .\seedrecover.py --wallet-type bip39 --mpk xpub6DBZvWvR1bgKmk6k5JvweNRD1QhKXzGroqZWAETadaz5BWauEGwptwn4o2jeFknZxKhe9dCA9NYk1TfjPiesg5tJG6xF5ymBogS8fHKVsiL --mnemonic-length 24 --mnemonic-prompt --bip32-path "m/49'/0'/0'/0"

yielded:

Code:

PS C:\Crypto\btcrecover-p2wpkh-p2sh> python .\seedrecover.py --wallet-type bip39 --mpk xpub6DBZvWvR1bgKmk6k5JvweNRD1QhKXzGroqZWAETadaz5BWauEGwptwn4o2jeFknZxKhe9dCA9NYk1TfjPiesg5tJG6xF5ymBogS8fHKVsiL --mnemonic-length 24 --mnemonic-prompt --bip32-path "m/49'/0'/0'/0"
Starting seedrecover 0.7.3, btcrecover 0.17.10 on Python 2.7.15 64-bit, 16-bit unicodes, 32-bit ints
terminal does not support UTF; mnemonics with non-ASCII chars might not work
Please enter your best guess for your mnemonic (seed)
> version vanish add search lucky polar buddy wasp image trophy educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy
xpub depth:       3
xpub fingerprint: D04C4361
xpub child #:     0'
Using the 'en' wordlist.
Seed sentence was too short, inserting 1 word into each guess.
Phase 1/3: up to 2 mistakes, excluding entirely different seed words.
Not enough entirely different seed words permitted; skipping this phase.
Seed not found
Phase 2/3: 1 mistake which can be an entirely different seed word.
Using 4 worker threads
20695 of 49129 [################-----------------------] 0:00:00, ETA:  0:00:00
Seed found: version vanish add search lucky polar buddy wasp image trophy bright educate rubber tell control crystal rude letter erosion thank advance magnet veteran buddy

NOTE: For this test, I used the "Account Extended Public Key" ypub from the BIP49 tab on Ian Coleman, and ran it through the converter here: https://jlopp.github.io/xpub-converter/ to convert to an the xpub. (The xpub from Ian Coleman BIP44 tab is actually different and didn't work). However, this converter seems to supply the same "xpub" that Ledger Live provides... which would imply that Ledger Live is doing a similar ypub to xpub conversion.


Good Luck! 

You sir are a legend! I don't know what happened but I wrote animal instead of annual. Silly me. Please send BTC address so I can reward you.