I've got a new FTDI that worked once then no more .... wondered why https://www.youtube.com/watch?v=eU66as4Bbds Found this.... "If you have a counterfeit chip and plug it into windows with the updated driver, your counterfeit chip will be bricked. Once bricked, you can NOT use it on OSX or Linux boxes. However, if you manually install the drivers on Windows, you can use it on that windows box. However, the chip is still bricked. You can un-brick the device with the MProg3.5 Programmer on the FTDi site. Once un-bricked, it will work again on OSX and Linux But if you plug it into the Windows box….BRICKED again."
lunithy wrote:I've got a new FTDI that worked once then no more .... wondered why https://www.youtube.com/watch?v=eU66as4Bbds Found this.... "If you have a counterfeit chip and plug it into windows with the updated driver, your counterfeit chip will be bricked. Once bricked, you can NOT use it on OSX or Linux boxes. However, if you manually install the drivers on Windows, you can use it on that windows box. However, the chip is still bricked. You can un-brick the device with the MProg3.5 Programmer on the FTDi site. Once un-bricked, it will work again on OSX and Linux But if you plug it into the Windows box….BRICKED again."
It's not bricked. Just uninstall the latest FTDI driver & install older version that is probably already on your PC or from various sites. A similar situation occurred with the USB to serial chips on clone Arduino boards from China. Using older driver that did not check for the protection bit in genuine chip worked perfectly. If you are running Win8 or 8.1 you will be prevented from loading some of these earlier drivers as "not signed". There are ways around this with easiest to hold down shift & do a restart. You will then be given many advanced tools & one is to turn off driver signing by hitting F7. This will allow you to load driver & these advanced options reset after PC is booted. Have fun