This happened soon after I had my EB185 hooked up to the laptop for the first time. I've been asked by a top forum contributor to document it. I had just installed CleanFlight and was running it for the first time ever. I was very unfamiliar with it (being my first exposure to Naze32 and CF) but quad seemed to be calibrated and working. The 3D model in CF was responding on the laptop screen as I moved the quad on desk.
I thought I needed to change the uart ports to be more like in EB185 manual. Well, you do ... but I mis-interpreted what they were talking about. After I inadvertently changed UART-1 Data away from MSP/115200 (by changing something else on that line) ... I could no longer Connect to quad. Basically, it appeared to be bricked.
As it turns out, the Naze32 is supposedly un-brickable. All you have to do is carefully short test-point Boot/Boot0 to 3.3volts, and plug-in it's power at the same time. The problem is that on the EB185, the Boot signal is not brought out to an easy to access test-point pad. So, in this case, you must use Pin#5 on STM32F chip itself.
Understanding what must be done, it seemed pretty hard to hold a probe on a single STM32F pin without it slipping and shorting to a nearby one ... not to mention holding a short while connecting power. Luckily, I ohmed-out Pin#5 and found it goes directly to the top solder-leg of the resistor right by it on the PCB.
Therefore, I carefully shorted these 2 points (marked in above pic in violet color) with a pair of sharp tweezers, while simultaneously connecting USB cable coming from laptop. Windows laptop detects Naze32 device in "Devices and Printers", but no sound from quad. Carefully lift and remove tweezers shorting the 2 points. At this point you should be done. It should connect now or the next time you reset the power (or re-connect USB).
I started CleanFlight and Flashed to: 1.12.1 NAZE 2016-4-10 (Stable). Recalibrated and reprogrammed. Good as new and back on-track. Note to self : Never do that again! Hope this helps.