need help with wallet issues

Hey there, I’m having some trouble with my wallet. The addresses aren’t showing the correct balance... So, I messed around with my wallet.dat file like this: First, I used a program to change the file type, Then I tweaked a letter in the file. After that, I encrypted it with bitcoin-qt, And finally, I reset it back to the original. I’ve got an HD wallet and I made a new address to get my bitcoins! I suspect that’s where things went wrong. Here’s my question: Do you think the issues are because I changed the structure of my .dat wallet? Like, maybe it’s become unreadable by bitcoin core? But I’m also considering another possibility: I used an address from my HD wallet, but can’t find it in the pool or during the wallet rescan... I’ve tried some tests, but no luck. Honestly, I can't think of other issues... Now, I can’t access my bitcoins in my "old wallet" anymore. Can anyone help me out?

I am kind of having trouble with understanding what you are trying to say, I assume you modified your wallet dat file and it is showing an error/not recognized by core. But you are supposed to have a backup of your wallet dat file before making any changes. If you do then try replacing it. Another problem is entirely different, your address created by HD Wallet will be there so either you send funds to the wrong address or copied the wrong address which is the reason you can't see the address. You can try to import the HD wallet into another HD wallet using the mnemonic phrase so it will work in case if the previous wallet is having any issues related to syncing. Check the address on https://www.blockchain.com/explorer to see the balance.

One question: why?! You've corrupted your wallet.

Is the address balance you see in your wallet the same value you see in a block explorer? Such mempool.space

first off if you did all that you likely lost your coins 🪙 unless you have clean backups so do you have backups?

One simple question, where did you get the wallet file originally from? If you bought it from someone, you've been scammed! Second, do you have a backup seed phrase for that wallet?

I don't have a backup of the file from before the .dat file was modified in its strict usage of bitcoin core... What is the problem ? problematic ? I can search but I don't think... ...... I feel bad I had this file a while ago...

Based on his posts history the wallet was generated from an old bitcoin-qt wallet. And the 2nd one since it was generated from Bitcoin-QT I'm sure he does not have a backup seed. @OP is this the wallet from your previous threads about corrupted dbcache? You keep creating a new thread but no response? I hope you can go back to your previous thread because maybe someone already posted the right solution for your problem.

I didn't follow their answers well, but the fact that the file is not "pure" or "corrupt", we can also say... This was not mentioned, and I did some research ... I have a HD seed, yes, what more can I say, apart from how do we deal with this "non-pure" file? Is a simple backup wallet enough? should I activate the software option "activate or not activate parts control"? I made a few unsuccessful attempts... but I don't want to miss the train with FALSE manipulations!! or otherwise, apart from forcing, "rescan and rescan", I don't see?! help requested! Sincerely !

If you have the HD seed you should be able to recover the wallet by importing it into supported wallets like Electrum but how did you get the HD seed? Since BitcoinQT/Bitcoin core doesn't generate a seed I'm sure it was not from this wallet. About simple backup you don't need to activate anything, If you talking about Bitcoin core then copying the wallet.dat file is enough but make sure you turn Bitcoin core and Bitcoind off because if you copy the wallet.dat file while these two are running there is a big chance that the backup wallet you just made may become corrupted. So make sure to close them properly before making a backup. I don't understand this part below I think it would be better if you create a thread in your local language or use a translator like Google translator.

It's the "HDSeed" of Bitcoin Core (non-descriptor) wallet files which is exported in WIF format. It cannot be imported to Electrum even if it's converted to (xprv) master private key since it doesn't support hardened address derivation path. Your original HDSeed's keystore was flushed with the wallet encryption, then if you generated new addresses to receive those missing transactions, then that's the issue. Encrypting the wallet file will trigger it to set a new HDSeed; so after reverting to the original, you essentially removed the new HDSeed where the new addresses are derived from. In this case, the solution is to find a backup of that encrypted wallet file.

You reason but, I saw a wiki, the encrypted wallet does not modify Hdseed! It's true / or false ? (more below) I modified a letter, to put it back in its place, it's a test! I just changed the creation date of my wallet (here) If false, : if I have a backup or a "pywallet recovery" or a dumpwallet of my file, before encryption, it may seem stupid, "BUT HOW TO PROCEED"? Please !? I wasn't very "in the know", when I started this recovery, I didn't have the blockchain... I thought it would be easier but this log once again showed me that it wasn't! I had to be more careful, that's it... but here I am listening...?! an idea, ? I have to do what ? If it's too old and recently modified, could that mean that's the problem? I modified it a long time ago now... 1 time dump, 2 times modify, and tree times encrypt, but no coins... after import dump ?? what I do import ?

False, you might have seen an entry about "changing passphrase", which is already an encrypted wallet. How about this? The actual message that you'll see when encrypting a wallet: As you can see, the unencrypted backup is useless once you've used the encrypted wallet to generate new keys. The reason for that message is because the HDSeed and keystore are replaced with a new one after encryption (setting a passphrase for the first time).

That's not entirely accurate: The coins that were already in the wallet before encryping it are still there, also in the backup. But the moment you use a new receiving address, or create a transaction which sends funds to a change change, those aren't in the old backup anymore.

That's why "backup" is mentioned, I and it didn't mentioned anything about the previously received bitcoins in the unencrypted backup. The point is the newly generated keys wont be recoverable using the unencrypted backup. Based from OP's situation, it looks like the case.

I just remember Bitcoin Core have separate program called bitcoin-wallet which can be used to obtain some data from your corrupted wallet. Here's short example how to use it (i already tested it before writing this post), Above command will create salvage.txt file which can be opened with any text editor. Unfortunately i don't know how to interrupter or process the output file. Above command will create wallet.dat.[TIMESTAMP].bak on path where wallet.dat is located. You can either attempt to load wallet.dat.[TIMESTAMP].bak on Bitcoin Core or other recovery software.

I don't have the answer I wanted!

How did you change a letter in a .dat file? Because if you opened the .dat file in a text editor and then started modifying the text, you may have already broken the "data" in it since .dat file is not a plain-text to be modified this way. Not to mention that depending on the text editor you may have even changed the encoding of the represented "text" that would end up corrupting the file even further.

Try to get your hand on a wallet from the same build as yours. Install on a different pc and copy the .dat  file. That way you have a virgen .dat file.

After peeking at Op's post history here is what he did. It's clear that he made some changes to the file while converting its been done via the software or by himself which corrupted the wallet.dat file and then qt created a new wallet which is why he is seeing different addresses. I am afraid there is an undo button for OP's fault and at least he should have created a backup before making changes so its a lesson and I assume the file is irrecoverable now.