Do you remember which bluez5-dev version did you have? And which version you have now?
The release you are using has BlueZ5.24 so you shouldn't have to install that package. I suggest you to flash the board using the flashall script. Which OS are you using? In this thread you will see the steps you need to follow to do this in the OS you are using: Re: No Edison Drive After Failed Flash
This could be due to a conflict between different BlueZ versions, so I recommend you to flash again the board with the default configuration.
Which was the purpose of install bluez5-dev? You should be able to use Bluetooth in your board without doing this.
I actually can't run /flashall.sh
base:edison-image-ww36-14 jnoble$ sudo ./flashall.sh
./flashall.sh: line 170: flash.log: Permission denied
Using U-Boot target: edison-blank
Now waiting for dfu device 8087:0a99
Please plug and reboot the board
Nothing happens. I guess the board is completely bricked now?
My experience is from using OS X, but hopefully it helps your situation as well. I am using the Sparkfun breakout board. There are two USB micro port. I don't plug them into the computer until "Please plug and reboot the board" is displayed on Terminal. Once it is displayed, I first plug into the USB port that is for serial console, then I plug in the USB port for OTG. Usually, the script will detect them being plugged in and move to flashing the board.
Have you been able to run the flashall script? The board should not been bricked as you mentioned because you are able to get into the Terminal Console without problems (Has this changed?).
Which expansion board are you using? Is the breakout board, arduino expansion board or a SparkFun block?
If the flashall doesn't work for you, you can also try with the Flash Tool Lite: IoT - Flash Tool Lite User Manual | Intel® Developer Zone