The 500 status is because it is trying to make calls to functions it is no longer tied to so it actually ends quite quickly in a php fatal error. You will see that if you look in your servers error log.
I do have one other thought.
You said you set file/folder permissions to 777. Somer servers are set – in our experience – to fail at 777 because it is just too open. But – I also note you did that after it failed to load the first time around.
However – there are two more security permissions that are set on Unix based files and folders called GUID and UID. These control ownership. I.e., does a file belong to the system (like the root user) so can not be called and opened by a simple user. It is rare but we have encountered users whose servers have coughed at the wrong time and set either the UID/GUID or both incorrectly. If this has happened then WP would not be able to open them.
It is not recommended to change these if you do not know what you are doing but you should be able to look at them. A decent ftp client will usually allow you to view the full permissions. GUID and UID should basically be the same as the parent wp-content folder.
If in any doubt I would ask your host to take a look.