Updated Troubleshooting (markdown)

Troubleshooting.md

@@ -11,10 +11,11 @@ Headphones does not turn on verbose logging (also known as debug information) fo
 The second option will be the easiest option in most cases, especially for Synology users.
 
 ## Second of all: rule-out human error ##
-There are a lot of issues that can be solved by just reviewing your settings. Before continuing (or posting an issue), consider the following:
+There are a lot of issues that can be solved by just reviewing your settings. Before continuing (or posting an issue), consider the following general advice:
 
 * Am I connected to the internet?
-* Did I spell the URL correctly (note that some URLs require `http://` in front, while others may not)
+* What settings did I change from the default installation?
+* Did I spell the URL correctly (note that some URLs require `http://` in front, while others may not)?
 * Do I have write permissions to the directory Headphones tries to move files to?
 * Does Google know it?
 
@@ -50,19 +51,22 @@ _Solutions_:
 
 ## (Auto) update does not work ##
 _Symptons_:
-
 Headphones tells you there is a new version available, but an update fails. The version number does not change.
 
+Or:
+
+Headphones does not start anymore, after an update.
+
 _Solutions_:
 
 First of all, make sure Headphones has write access to the installation.
 
-The auto-update function of Headphones uses [Git](http://en.wikipedia.org/wiki/Git_(software)) to update to the latest version. It may happen that the auto update will fail, and manual action is required. It is assumed that you have a recent version of Git installed. 
+The auto-update function of Headphones uses [Git](http://en.wikipedia.org/wiki/Git_(software)) to update to the latest version. It may happen that the auto update fails, and manual action is required. It is assumed that you have a recent version of Git installed. 
 
 For Synology users it may be necessary to specify the full path to the `git` binary.
 
 ### Manual update ###
-Use the following commands to _reset_ your repository.
+Use the following commands to _reset_ your repository. Backup your configuration and database files, just in case.
 
 * `cd /path/to/heapdhones`
 * `git branch` should list either `master` or `develop`.
@@ -72,7 +76,7 @@ Use the following commands to _reset_ your repository.
 * `git pull origin master` or `git pull origin develop`
 
 ### Reinstallation ###
-There are some issues with specific version of Headphones for Synology, where the first method will not work (see issues #1770, #1742 and #1774). The following provides some steps to reinstall Headphones, but should be tailored to your specific installation. 
+There are some issues with specific version of Headphones for Synology, where the first method will not work (see issues #1770, #1742 and #1774). The following provides some steps to reinstall Headphones, but should be tailored to your specific installation.
 
 * `cd /path/to/heapdhones`
 * Backup your database and config file. In my case, I just copy them to the parent folder. Make sure you have copied them!
@@ -84,6 +88,14 @@ There are some issues with specific version of Headphones for Synology, where th
 * In case you run Headphones as a different user, make sure the Headphones user owns the directory for writing.
   * `chown -R headphones:headphones /path/to/headphones`
 
+### Reset to previous version ###
+Sometimes, you just want to go back to an older version. Either because there is no update or fix available for a problem you did not have in an older version. Backup your configuration and database files, just in case.
+
+* `cd /path/to/heapdhones`
+* `git log`, which should give a list of all changes. 
+  * Pick a commit hash (long string of letters and digits)
+* `git reset --hard PUT_HASH_HERE` — this WILL overwrite all local changes! It will spare your config and database.
+
 ## SSL-enabled servers/indexers/search providers don't work ##
 _Symptons:_