I thought magic numbers were only the first bit of a file
But my knowledge is minimal..

Can I confirm what OP is please? And by copying bytes to a new file will it change to a .dat like it originally was or will it stay at a .db?

You are brilliant thank you so much I have been stuck on this for some time now

Appreciate your time so much!

Thanks for your reply.

I ran file and it did print

"Berkeley DB (Btree, version 9, native byte-order)"

Then I ran hexdump -C



So Testdisk (photorec) found the files based on the photorec.sig for -
"Berkeley DB (Btree, version 9, native byte-order)"

And the file command confirmed that is it Berkley DB

So now how do I turn these files into wallet.dat or what can I do testdisk recovered a few GB worth of files in .db format

What I have noticed is the first file will be few KB and out put "b1 main" and the next file will be 741 MB of heaps of data keys pool ect and then again the next file is few KB "b1 main" and so on...if that makes any sense

Hi,

I ran testdisk (photorec) to recovery wallet files from a formatted usb. Photorec was able to recovery .db files using berkeley signature which is great but now I don't know how to extract just the wallet file out of the .db files and convert it to .dat or make it readable for bitcoin core.
Any suggestions would be greatly appreciated?