Using a Bricked faux-FTDI under Windows 8.1

subtitled … Windows 8.1 demoted me to a lesser god.

I bricked an faux-FTDI last year before I swapped out the XP development notebook (now Linux) to a Windows 8.1 notebook. Fixing the issue last year on XP was easy … seems that I am a user in the Admin group, so I could do anything I needed. When crap hit yesterday and I plugged in a new Chinese FTDI USB-serial device, the FTDI drivers bricked the device by writing PID_0000 to the adapter… kiss of death! Now, I had taken great pains on NOT doing any driver updates to the 8.1 notebook, so obviously something I installed did the FTDI update … blast ’em.

I went to edit the two necessary files in C:\Windows\System32\DriverStore\FileRepository
according to this article. I then found out that Microsoft had protected the DriverStore\FileRepository and even with Administrator rights, I could not edit and save the necessary changes to ftdi.port.xxx and ftdi.bus.xxx.

I attempted to take add myself into the rights group (remember I am an Administrator) but the system would not permit. I attempted to take ownership and the system would not permit. I am moving to Linux, so far 4 machines in the lab, but the coding/development box is the last that I had planned on doing. After yesterday, I may change the priorities!

So, what is one to do? Boot from a Linux preview DVD or course! That solves the lesser god issue. After editing the necessary files and adding the lines (abbreviated here for brevity. File ftdiport.inf shown below, similar edits must be accomplished to ftdibus.inf
[Version] ; Changed version from 04/10/2012 to 04/10/2022 in effort to avoid newer versions automatically overwriting ... no guarantees with Microsoft!
DriverVer=04/10/2022,2.08.24
<...>
[FtdiHw] %VID_0403&PID_0000.DeviceDesc%=FtdiPort.NT,FTDIBUS\COMPORT&VID_0403&PID_0000
%VID_0403&PID_6001.DeviceDesc%=FtdiPort.NT,FTDIBUS\COMPORT&VID_0403&PID_6001
<...>
[FtdiHw.NTamd64] %VID_0403&PID_0000.DeviceDesc%=FtdiPort.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_0000
%VID_0403&PID_6001.DeviceDesc%=FtdiPort.NTamd64,FTDIBUS\COMPORT&VID_0403&PID_6001
<...>
[Strings] VID_0403&PID_0000.DeviceDesc="USB Serial Port 0000"
VID_0403&PID_6001.DeviceDesc="USB Serial Port"


Pictures tell the story of the next steps for installing and using the “bricked” modules:

Bricked_faux-FTDI.jpg (82.17 KiB) Viewed 1438 times

Step3.jpg (69.86 KiB) Viewed 1438 times

Part6.jpg (38.38 KiB) Viewed 1438 times

Ray,

Very interesting to see how MS now locks you out of your own system.

This will really start to annoy anyone who has to do system support for a large organisation, unless they are on some ultra enterprise level system on all their machines. But I suspect there are loads of SMEs which just run one or two Windows servers e.g one for mail and one for file storage, and have the staff using Windows 8.1, who will come across the same sorts of lockout issues.

Btw. Wasn’t there a Linux way to unbrick the FDTI clone, by somehow changing its PID back to the correct value

RogerClark wrote:
<…>
Btw. Wasn’t there a Linux way to unbrick the FDTI clone, by somehow changing its PID back to the correct value

Hi Ray

OK. I see what you mean.

For personal use, I can’t see a problem with unbricking the device using Linux.

People can google for it, e.g. Fixing a bricked FTDI from Linux and find ways to do it.

Of course the Windows driver will brick it again immediately, if they have not updated the driver to the version that no longer bricks it.

RogerClark wrote:Hi Ray

OK. I see what you mean.

For personal use, I can’t see a problem with unbricking the device using Linux.

People can google for it, e.g. Fixing a bricked FTDI from Linux and find ways to do it.

Of course the Windows driver will brick it again immediately, if they have not updated the driver to the version that no longer bricks it.

Thanks Ray,

I must confess to not reading your posting in detail

But if someone didnt change the date etc and just attempt to use an unbricked device I presume it would get bricked again

BTW. I have two FT232 based usb to serial devices, but Windows 7 didnt recognize and install the default firmware, so I presume they are clones and perhaps it no longer installs the virtual serial driver.

There was some alternative SW/ Driver etc I tried downloading from from FTDI but the devices didnt appear as virtual serial, they appear as some useless USB device.

At which point I coudlnt be bothered wasting any more time on them. And went back to using one of my many Non-FDTI devices

I will not buy a FT232 again, as I have no way of knowing if its real or not.
I could spend a fortune and buy from Adafruit etc and hopefully it would be guaranteed to be genuine, but as the Sil Labs devices and the others work fine for me, its just not worth the cost and hassle to get hold of FTDI devices any more.

I heard about the FTDI drivers that brick the fake chips but I read also that they changed so that the last drivers simply refuses to work (like Prolific, you get error code 10) and don’t brick fake chips any more. But your experience seems different!

Ray,
Have you tried to edit the files in another folder, and then move again, or in the same folder where they are (C:\Windows\System32\DriverStore\FileRepository) ?

zoomx wrote:

Ray,
Have you tried to edit the files in another folder, and then move again, or in the same folder where they are (C:\Windows\System32\DriverStore\FileRepository) ?

I buy USB/serial cables (logic level as there’s little need for RS232 now), marketed as FTDI and carry the FTDI logo on the packaging, and from reputable companies in the US.
No issues.

I did buy a Prolific chipset adapter and wasted a lot of time with driver issues, then s-canned it.

stevech wrote:I buy USB/serial cables (logic level as there’s little need for RS232 now), marketed as FTDI and carry the FTDI logo on the packaging, and from reputable companies in the US.
No issues.

I did buy a Prolific chipset adapter and wasted a lot of time with driver issues, then s-canned it.

I agree Ray. What if someone invested a lot into a product in the market and then suddenly have stuff bricked? I also use devices with the CP2102 device. I bought some NodeMCU devices and picked the ones with the CP2102.

mrmonteith wrote:I agree Ray. What if someone invested a lot into a product in the market and then suddenly have stuff bricked? I also use devices with the CP2102 device. I bought some NodeMCU devices and picked the ones with the CP2102.

Judging from messages I’m seeing on the internet people haven’t forgotten. Guess we will see what ones show up on new devices. At least there is a fix and move on. I know if I design anything which I’ll choose.

I’ve also decided that FTDI devices are now too risky to use in ether personal or commercial projects.

It’s impossible to guarantee that any component is official, ( just google the U.S senate enquiry into the widespread proliferation of counterfeit parts into the US military).
So if Mil procurement can’t guarantee genuine parts, there is very little hope that cost conscious consumer manufacturing will be able to do so.

And who knows what drivers are still kicking around in the wild on consumer’s machines, waiting to brick your company’s products and cause an expensive support and recall program

What should I say…. my FTDI on my Melzi board (3d-printer) is a fake one. It was driving my nuts to get win7 NOT to load the actual drivers. I searched the whole system for any FTDI drivers (all labeled by “FTDI”) deleted them, cut the internet connection and manually installed the cdm_v2.10.00 version (NOT from the FTDI homepage). Finger crossed: Everything is working at the moment.

Another reason to stay with Linux …

martinayotte wrote:Another reason to stay with Linux …

ahull wrote:martinayotte wrote:Another reason to stay with Linux …

mrmonteith wrote:I agree Ray. What if someone invested a lot into a product in the market and then suddenly have stuff bricked? I also use devices with the CP2102 device. I bought some NodeMCU devices and picked the ones with the CP2102.

stevech wrote:mrmonteith wrote:
<…>
A hobbyist/student can cut the cord. I hope to someday.
<…>
I must say though I don’t like Microsoft’s monopoly, it is necessary for me, now.

HackADay are now reporting the latest Windows driver injects extra characters into the data on fake chips

This beggers belief.

Such an arrogant company.

RogerClark wrote:HackADay are now reporting the latest Windows driver injects extra characters into the data on fake chips

This beggers belief.

Such an arrogant company.

RogerClark wrote:HackADay are now reporting the latest Windows driver injects extra characters into the data on fake chips

This beggers belief.

Such an arrogant company.

Lets hope no system which is safety critical uses FTDI parts.

As I’m not sure who would be liable for the injury caused by injecting data

e.g. Industrial machines e.g. laser cutters, milling machines etc, can have these sorts of devices in them.

Roger, I’ve edited my post. Keyword: medical devices

Hi Matthias

My laser cutter has some sort of UART interface that controls it. I’m not sure if its an FDTI part or not, I’ll need to check the driver, but I know its not a FT232.

Fortunately I’m controlling the laser cutter from an old WIndows XP machine that is not connected to a network, and I manually loaded the drivers from USB stick. So there is no chance it can update.

Boy there is smoke rolling on Hackaday

Adafruit Interviews The CEO Of FTDI

Thought I’d share what’s going on.

Michael

mrmonteith wrote:Boy there is smoke rolling on Hackaday

mrburnette wrote:
IMO, it should be a f’n barnfire of all devices using the FTDI chip. It would be more fun than burning a Beatles record in the ’60’s!

Ray

IMHO: This CEO is shoveling a big grave for the company. There is a little thing he forgot: The most people are using the fake FTDI chips are pupils and students and/or young people with less money BUT: – the opinion leads of the next generation (as multiplicators). And they will avoid using FTDI chips in their designs of the future. Just my guess…

madias wrote:IMHO: This CEO is shoveling a big grave for the company. There is a little thing he forgot: The most people are using the fake FTDI chips are pupils and students and/or young people with less money BUT: – the opinion leads of the next generation (as multiplicators). And they will avoid using FTDI chips in their designs of the future. Just my guess…

The winner has to be Microsoft and their “Bend Over, your windows 10 is coming like an enema you can’t refuse.”

madias wrote:IMHO: This CEO is shoveling a big grave for the company. There is a little thing he forgot: The most people are using the fake FTDI chips are pupils and students and/or young people with less money BUT: – the opinion leads of the next generation (as multiplicators). And they will avoid using FTDI chips in their designs of the future. Just my guess…

stevech wrote:madias wrote:IMHO: This CEO is shoveling a big grave for the company. There is a little thing he forgot: The most people are using the fake FTDI chips are pupils and students and/or young people with less money BUT: – the opinion leads of the next generation (as multiplicators). And they will avoid using FTDI chips in their designs of the future. Just my guess…

ahull wrote:
<…> One of the first rules of business is that if you loose a customer (for *any* reason), you will rarely get them back. One they have dropped you, they are very unlikely to admit they were wrong by coming back to you.