There's not really anything you can do. Your database is going through crash recovery, and it needs to process the transaction log. I've written about this exact scenario more in depth here.
If SQL Server hadn't completed a CHECKPOINT recently, there would be database changes that were committed, but had only been made in memory & in the transaction log, but not in the data files. These changes need to be redone from the log file so that the changes aren't lost. This is what your server is doing right now. I describe the phases in more detail in the article I linked to earlier.
If your transaction log is unnecessarily very large, this can cause SQL Server to do checkpoints less frequently. A too large log file, or too many VLFs can both result in a longer recovery time after a crash.
For a planned restart you can minimize/eliminate the delay by performing a manual
CHECKPOINT; before shutting down and by allowing the SQL Server service to gracefully stop. Rebooting the server without first stopping the service can result in a forced termination of the sqlservr.exe process, leading to recovery like you're seeing on startup.
To get your database back online, just be patient. Don't restart, don't try to get rid of your log file. Just be patient. That estimated recovery time is notoriously incorrect, so hope that it's online sooner, rather than later.