The transaction log doesn't clear the contents of the log (simply marks the virtual log files as reusable or not), so it's possible that the data is still in the transaction log. This assumes that there hasn't been sufficient write activity in the log since the problem occurred to wrap around and overwrite these log records.
However, given that your question is now 5 days old now, I don't hold out much hope for the log records still being in the file. Even if you immediately stopped SQL Server and made a copy of the LDF file, you'd need to know the internal structure of the transaction log, and to be able to locate the rows. It would be possible, but it'd be expensive to get someone to do! As Lekss said, I'm not sure if a log explorer tool would have the smarts to read log records that are marked as "not there".