Help me access my friends corrupt litecoin wallet.dat

[scutzi128]

Long story short my friend reinstalled windows and did not realize that the wallet.dat file was on his c drive. He used recuva to read the old wallet.dat file but when used in litecoin it says it is corrupted. I tried using pywallet with no success. He had around 30 ltc in it and anyone that can help access it will get a 20% bounty. Any help would be greatly appreciated. Thanks.

[1714006144]

1714006144

[1714006144]

1714006144

[1714006144]

1714006144

[atchoum6760]

Rename bitcoin.dat in wallet.dat et put in  the dossier bitcoin de appdata normaly it's good.

[scutzi128]

Thanks for the reply but I do not understand what you just said.

[pedrog]

Try recovering the file with GetDataBack.

[scutzi128]

Tried it with no luck.

[tomthgrk]

Install a new litecoin wallet
let it sync
close wallet
name your old data file wallet.dat
copy and past wallet.dat at appdata folder to replace the existing wallet.dat file
open run litecoin wallet

[stefan80]

Just paste the old wallet file in  the folder  %APPDATA%\Litecoin\    it should work.

This folder is usually located in C:\Users\..... (user name).... \AppData\Roaming\Litecoin

[scutzi128]

think the problem is not how to get old wallet to new client
problem is corrupted wallet file

you are correct...it says its corrupted and the wallet just closes

[tomthgrk]

think the problem is not how to get old wallet to new client
problem is corrupted wallet file

you are correct...it says its corrupted and the wallet just closes

ok...then, follow this directions.


Corrupt wallets used to cause a DB_RUNRECOVERY uncaught exception and a
crash. This commit does three things:

1) Runs a BDB verify early in the startup process, and if there is a
low-level problem with the database:

*Moves the bad wallet.dat to wallet.timestamp.bak
*Runs a 'salvage' operation to get key/value pairs, and writes them to a new wallet.dat
*Continues with startup.

2) Much more tolerant of serialization errors. All errors in deserialization
are tolerated EXCEPT for errors related to reading keypairs
or master key records-- those are reported and then shut down, so the user
can get help (or recover from a backup).

3) Adds a new -salvagewallet option, which:

*Moves the wallet.dat to wallet.timestamp.bak
*extracts ONLY keypairs and master keys into a new wallet.dat
*soft-sets -rescan, to recreate transaction history

[scutzi128]

I am getting this error in the debug log file:

Litecoin version v0.8.5.1-beta (2013-09-11 17:46:33 -1000)
Using OpenSSL version OpenSSL 1.0.1c 10 May 2012
Startup time: 2014-01-16 23:04:31
Default data directory C:\AppData\Roaming\Litecoin
Using data directory C:\AppData\Roaming\Litecoin
Using at most 125 connections (2048 file descriptors available)
Using 8 threads for script verification
init message: Verifying wallet...
dbenv.open LogDir=C:\AppData\Roaming\Litecoin\database ErrorFile=C:\AppData\Roaming\Litecoin\db.log
Failed to rename wallet.dat to wallet.1389913471.bak
Flush(false)
DBFlush(false) ended               1ms
StopNode()
Flushed 0 addresses to peers.dat  3ms
Flush(true)
DBFlush(true) ended               0ms




This is the db.log file:

Page 0: metadata page corrupted
Page 0: could not check metadata page
wallet.dat: DB_VERIFY_BAD: Database verification failed
__db_meta_setup: C:\AppData\Roaming\Litecoin\wallet.dat: unexpected file type or format
__db_meta_setup: C:\AppData\Roaming\Litecoin\wallet.dat: unexpected file type or format
__db_meta_setup: C:\AppData\Roaming\Litecoin\wallet.dat: unexpected file type or format
__db_meta_setup: C:\AppData\Roaming\Litecoin\wallet.dat: unexpected file type or format

[iGotSpots]

Just use private keys

Code:

dumpprivkey <address here>

^ Copy that key

Open on new machine

Code:

importprivkey <priv key you copied> <label>

Remove all the < and > obviously

[scutzi128]

Just use private keys

Code:

dumpprivkey <address here>

^ Copy that key

Open on new machine

Code:

importprivkey <priv key you copied> <label>

Remove all the < and > obviously

I don't know what the private key is and I can't determine it from the wallet.dat because it is corrupted.

some topic:
https://bitcointalk.org/index.php?topic=25091.0

I found that topic earlier and I'm having him try it as we speak.

[scutzi128]

some topic:
https://bitcointalk.org/index.php?topic=25091.0

I found that topic earlier and I'm having him try it as we speak.

He tried this and it failed looks like its lost forever. At least he learned to backup his wallet from now on.

[samysamy1]

some topic:
https://bitcointalk.org/index.php?topic=25091.0

I found that topic earlier and I'm having him try it as we speak.

He tried this and it failed looks like its lost forever. At least he learned to backup his wallet from now on.

Try to run Windows system restore and restore to a previous point OR you might want to restore to the previous Windows version. That wallet might not be corrupted.

[cryptomining]

litecoin-qt -reindex