Topic: HEEEELP ME, 2000$ R E W A R D FOR the right solution timestamp .bak wallet away (Read 3738 times)
March 08, 2016, 07:16:22 AM
Honestly, the only thing you can do is try to remember if you have one more fine backup, other than that, I guess all is lost. Even if I carry just half of bitcoin in my wallet, I keep it's backup like at 5 different places.
March 08, 2016, 05:29:44 AM
@ totohasproblem and everyone new around here
You better not deal with noobs from this forum, chance is very high that people who have a new accounts here are scammers and not trustworthy. "I need access to your computer" and so on, to steal your wallets and infect machine with some malware. "I can fix it but PM me" and such bullshits. Do not buy into such schemes. Anyone who is worthy of dealing with in cryptocoin community already has some Full, Senior or higher rank member account, for everyone else just asume they are up for no good and you will be fine.
You better not deal with noobs from this forum, chance is very high that people who have a new accounts here are scammers and not trustworthy. "I need access to your computer" and so on, to steal your wallets and infect machine with some malware. "I can fix it but PM me" and such bullshits. Do not buy into such schemes. Anyone who is worthy of dealing with in cryptocoin community already has some Full, Senior or higher rank member account, for everyone else just asume they are up for no good and you will be fine.
March 06, 2016, 09:13:09 PM
So you do not have backup of a new wallet nor backup of wallet.1457257429.bak?
NO,
i renamed the bak file to wallet file
so it is normally not lost
but the system replaced it with a new wallet file
the normal procedere is that the system will only replace if in the folder is no wallet.dat available
in my case the system see a wallet.dat, but knowing that this was a wallet.2314234.bak before and then removes it
(not really replace, because it goes away a second after start the app, and the new one is coing after all the checks.)
so, where the system send the file, is htere any backup or so,
i think here we need experts in the software itself right, is there any support for bitcoin core that is highly advanced, i even will pay them 500$ per hour for that. i need it to be solved.
First of all, do not mess with partition and HDD where you have Bitcoin wallet.dat files! Second, download Recuva https://www.piriform.com/recuva or some other file recovery software to different computer, install it there then shutdown your computer with Bitcoin wallet.dat files. Remove HDD from it, attach it to computer with file recovery software and do a full deep scan of HDD. All found deleted files must be copied to different HDD, not the one that have Bitcoin wallet.dat files! Unless you are perfectly aware of what you are doing better just take HDD to file recovery specialist or service.
Bitcoin Core simply deleted your new wallet.dat (wallet.2314234.bak) file but possibly there is a chance it is not unrecoverably overwritten.
Hi, thank you
but the file is not really deleted, the bitcoin core system send it somewhere, i dont think they delete it.
if you follow the steps you can see it in your wallet happen, its a Bug maybe
the bitcoin core app creates a new wallet.dat file and there is not my money, the bitcoin core program send 1. the wallet.dat (what was renamed to wallet.dat from the wallet-4343.dat) to nirvana, and i don´t know where it is
You should still do what totohasproblem suggests. If you really think you have the file somewhere, you could download a tool that searches inside files. Open a proper file in an editor and search for something that appears in the beginning of the file. If you find the right tool and configure it to read file correctly it will find any wallet file that was originally created by your bitcoin client.
March 06, 2016, 09:01:53 PM
i could have the right Solution for your Problem. just send me Pm if u interested sombody should take care about the reward
regards
regards
March 06, 2016, 08:38:12 PM
You should *never* be renaming "wallet.dat" full stop and most especially not while the program is running.
March 06, 2016, 08:24:36 PM
Right, but there are differences at OS level when it comes to handling of files. In any case, there are no traces of .bak file on my computer.
If there are no traces of the "wallet.XXX.bak" file after being renamed to "wallet.dat" (assuming you deleted the empty "wallet.dat" first) then it is because Bitcoin Core didn't find a problem with it when it restarted (i.e. the file wasn't corrupt).
There is no wallet.dat file at the stage when you are renaming .bak file to .dat file.
i checked it, if i do it with another wallet and i leave the program open for 10 min and then rename it, even if programm is running, than the wallet.dat is still OK
March 06, 2016, 06:16:28 PM
I've done what you've done on your computer. I managed to bring back the wallet.timestamp.bak file with "Ctrl+Z" command (Of course I didn't delete anything so it brought back from memory I guess)
But I don't think you're able to recover it if you closed your computer since then.
edit: Damn you don't have the .bak file either 
Hi,
Can you try these steps please?
1- Download this Hex editor: http://www.macupdate.com/app/mac/17562/hexedit (or any other hex editor)
2- Back up your .bak file somewhere (corrupted one) and work on it.
3- Open a normal wallet.dat file with this hex editor. It should look like this:
4- Open the *.bak file (corrupted wallet)
It should look like this:
if the shown bytes are different than normal wallet.dat file than copy the correct header info to *.bak file.
Then save .bak file, then rename & place it as wallet.dat to blockchain directory. Try to run core wallet with this new wallet.dat
(I'll try this a few minutes later).
But I don't think you're able to recover it if you closed your computer since then.
Hi,
Can you try these steps please?
1- Download this Hex editor: http://www.macupdate.com/app/mac/17562/hexedit (or any other hex editor)
2- Back up your .bak file somewhere (corrupted one) and work on it.
3- Open a normal wallet.dat file with this hex editor. It should look like this:
4- Open the *.bak file (corrupted wallet)
It should look like this:
if the shown bytes are different than normal wallet.dat file than copy the correct header info to *.bak file.
Then save .bak file, then rename & place it as wallet.dat to blockchain directory. Try to run core wallet with this new wallet.dat
(I'll try this a few minutes later).
March 06, 2016, 05:30:50 PM
I can help, but I'd need to be on your machine to do it. If all else fails, let me know.
March 06, 2016, 05:25:37 PM
Hi you need to do search on your computer for the wallet.dat or bak file it could be in your temporary or junk folder. Try finding or download a program called undelete and download on your Mac and see if it finds it. Check to see if you sent wallet to dbox. If this helps please send me $2000 or btc amount to 1N6d2118Ki4bNxKjF5MbECGDLSE5SPSuLo I really need it.
March 06, 2016, 05:23:04 PM
Hello,
thanks for all help but here a Video what happened so you can see more detailed what the problem is.
https://www.youtube.com/watch?v=H6veuKuCl2k
thanks for all help but here a Video what happened so you can see more detailed what the problem is.
https://www.youtube.com/watch?v=H6veuKuCl2k
March 06, 2016, 02:53:53 PM
There is no wallet.dat file at the stage when you are renaming .bak file to .dat file.
Are you sure your .bak file is a corrupt wallet?
i don´t have the bak file at all. i renamed it and then it was deleted or moved by the programm
March 06, 2016, 09:53:10 AM
What exactly happens is, in this case, secondary to the fact that file is gone. So I have nothing more to add to this thread but again point back to procedure for file recovery at the first page.
March 06, 2016, 09:27:12 AM
I think the key point was renaming stuff "while Bitcoin Core was running" (and that is where the bullet entered the foot).
Clearly the final state of the DB became problematic due to what had happened - but as an end-user you should never rename things like "wallet.dat" only make copies (that is just plain commonsense).
My guess is that some other state file (at the DB level) could be the reason for this problem but it isn't a Bitcoin Core problem really.
I have batch files (for Windows versions of Bitcoin) to work with different wallets - I never "rename" files though (they always use copies and overwrite "wallet.dat" before Bitcoin Core is started or copy "wallet.dat" after Bitcoin Core has shutdown).
Clearly the final state of the DB became problematic due to what had happened - but as an end-user you should never rename things like "wallet.dat" only make copies (that is just plain commonsense).
My guess is that some other state file (at the DB level) could be the reason for this problem but it isn't a Bitcoin Core problem really.
I have batch files (for Windows versions of Bitcoin) to work with different wallets - I never "rename" files though (they always use copies and overwrite "wallet.dat" before Bitcoin Core is started or copy "wallet.dat" after Bitcoin Core has shutdown).
March 06, 2016, 09:24:02 AM
Because original corrupted wallet.dat file was renamed to wallet.(timestamp).bak file which is then renamed back to wallet.dat file which is subsequently deleted it shows that wallet.(timestamp).bak file is not the same as original corrupted wallet.dat file or Bitcoin Core handles .dat and .bak files differently, deleting the later (after it was renamed) for no obvious reason. Put differently, original corrupted wallet.dat and wallet.dat file created by renaming wallet.(timestamp).bak files were not treated equally for some reason. Why simply not rename to .bak and exit, as previously?
March 06, 2016, 09:19:04 AM
Still it is unclear why and unexpected that Bitcoin Core deleted corrupt wallet.dat file. It should create a copy of it no matter what or not mess with wallet file at all if it is unreadable or whatever.
The Bitcoin Core code clearly does this - but if BerkleyDB decides to open the file (after your rename) and then not report an error then Bitcoin Core is left unable to do anything (it is relying upon the 3rd party software).
The mistake was renaming rather than copying (and that was a "user error").
March 06, 2016, 09:15:57 AM
Still it is unclear why and unexpected that Bitcoin Core deleted corrupt wallet.dat file. It should create a copy of it no matter what or not mess with wallet file at all if it is unreadable or whatever.
March 06, 2016, 09:11:20 AM
True but in any case Bitcoin Core should keep a copy of corrupt wallet.dat file.
It did (i.e. it created the "wallet.XXX.bak" file for just this reason) but then you went and renamed it (it can only do so much to predict what silliness a user might get up to).
Typically when something breaks you should stop and ask for help then (not try and fix it yourself if you've got no idea what you are actually doing).
March 06, 2016, 09:09:48 AM
Issue thread created at https://github.com/bitcoin/bitcoin/issues/7647 let's see what devs have to say about it.
Okay but I think you are going to cop it when they read this step:
Code:
6. Rename wallet.(random numbers).bak back to wallet.dat and start Bitcoin Core again.
(quite clearly it was *you* that got rid of the "wallet.XXX.bak" file not Bitcoin Core by renaming it)
True but in any case Bitcoin Core should keep a copy of corrupt wallet.dat file.
March 06, 2016, 09:07:16 AM
Issue thread created at https://github.com/bitcoin/bitcoin/issues/7647 let's see what devs have to say about it.
Okay but I think you are going to cop it when they read this step:
Code:
6. Rename wallet.(random numbers).bak back to wallet.dat and start Bitcoin Core again.
(quite clearly it was *you* that got rid of the "wallet.XXX.bak" file by renaming it - not Bitcoin Core)
Perhaps you should clarify that the issue you are raising is why did the supposedly corrupt "wallet.dat" suddenly seem to not be identified as corrupt (but was replaced with a new one) as this is more to the crux of the issue.
March 06, 2016, 09:03:48 AM
Issue thread created at https://github.com/bitcoin/bitcoin/issues/7647 let's see what devs have to say about it.
Jump to: