If one fails, try another.
The guide below comes from a very helpful Australian forum.
This guide implies:
1) You know what you’re doing around computers and have the basic necessary skills to create directories, copy files, and import registry keys.
2) You download the file linked below (or have a Mini-VCI CD with the contents roughly matching the included files)
Win64 MVCI Driver for TOYOTA TIS
3) Your Techstream version doesn’t matter as far as I can tell, I’m using V12 (search v12 download on our blog).
4) Windows 10, 64bit (other 64 bit versions, 7, 8, etc should all work too)
5) Tested on Mini-VCI cable J2534 with firmware 1.4.1 (should also work on newer cables too)
Grab the file above, it contains the necessary Mini-VCI 64 bit files. Make sure you copy and paste the entire link and doesn’t parse the URL correctly.
For your own safety, feel free to verify the file is safe from viruses using https://www.virustotal.com/ or any other of the various online virus testing tools.
All right, let’s get to it.
1) Create some new folders under your C:\Program Files (x86) folder and copy some files there.
C:\Program Files (x86)\XHorse Electronics
C:\Program Files (x86)\XHorse Electronics\MVCI Driver for TOYOTA TIS
2) Copy the files FirmwareUpdateTool and MVCI32.dll from the linked ZIP file to the “MVCI Driver for TOYOTA TIS” folder.
It should look like this
If those files aren’t in those folders, then Techstream won’t work with 64bit Windows and the Mini VCI cable. In fact, if you’ve done everything else on your 64bit system, check this first, and if those files aren’t in that folder try doing this step and test Techstream, it may just work.
Now, my version of Windows (Win 10 Creators Update – 1709) detected and loaded the drivers for the Mini VCI cable automatically. I’ve found that these drivers don’t always work, so I manually installed the drivers supplied in the ZIP linked above. To install them and enable them on your devices you do the following:
1) Under the ftdibus folder, right click the ftdibus.inf file and click install, and accept any warnings that appear.
2) Under the ftdiport folder, right click the ftdiport.inf file and click install, again accept any warnings that appear.
Get those out of the way before moving onto the next section.
1) Plug in your Mini-VCI cable and wait for windows to recognize it and load the drivers.
2) Open the device manager (Win Key+X then select Device Manager) and open the node “Ports (COM & LPT)” and double click the “USB Serial Port (COM?)” device, and then go to the “Driver” tab.
3) Refer to this image
– if the driver version is 220.127.116.11 then you don’t need to change anything, otherwise go to the next step.
4) If the driver version isn’t 18.104.22.168 then click on the “Update Driver” button.
5) Next click “Browse my computer for driver software”
6) Next click “Let me pick from a list of available drivers on my computer”
7) It should list two drivers,
– the one Windows likes (22.214.171.124) and the one installed manually in step 2 which is 126.96.36.199. Select the driver version 188.8.131.52 and click “Next” wait for the drivers to install then close that window. It should now display the driver version as 184.108.40.206 as installed.
Now, it’s time to do the same with the USB Serial Converter device. So keep that MiniVCI cable plugged in.
1) With the device manager open, expand the “Universal Serial Bus controllers” node.
2) Double click the “USB Serial Converter” device and go to the “Driver” tab.
3) Following the same process in the previous section, check for and change if necessary the driver to version 220.127.116.11. It’s the same process, just replace the device name appropriately.
4) Once both the Port and Converter are on 18.104.22.168 you can now go back to the FirmwareUpdateTool.exe file that you copied and open it, once open click the “Device Info” button and it should say it’s connected, and return the firmware version of the cable.
That’s the Mini VCI cable taken care of.
Now, you need to import the mvci-x64.reg file included in the ZIP. Without this imported, Techstream won’t know how to load the necessary files for the MiniVCI cable, namely the MVCI32.dll done in the first section. So simply double click it, and import it when prompted. It’s that easy.
It’s implied you already have Techstream installed and licensed, this guide won’t cover that step (there’s tons of guides out there that cover it if you need it). You may also need the IT3 ini files in the zip for your Techstream. They go in the ENV folder inside the Techstream install folder.
Now, you should be safe to open Techstream and verify operation. So with the MiniVCI cable still plugged in, open Techstream.
1) Go to “Setup” then “VIM Select”. It should open with the Interface setup of “XHorse – MVCI”
2) Refer to this image at the bottom, with the arrow
Techstream should show “VIM – Xhorse – MVCI J2534 DLL v1.4.7” (dll version may differ if you used your own files) the key is, if you get this far and it’s not just saying “VIM – Xhorse – MVCI” (which happens when you open Techstream without the MiniVCI cable plugged in) then you should be right to connect to the car. So turn on the ignition and connect.
3) If it has all gone well, then you should be presented with a progress window and if you get this far then Techstream is talking to the MiniVCI cable on your 64bit Windows.
That’s it all done, have fun.
Get the correct driver from FTDI website. The document is to get Windows 10 64-bit computer to recognize the Mini VCI J2534 with 1.4.1 firmware (FT232RQ chip). This is not a comprehensive guide but rather should be used as a supplement to the plethora of driver + Techstream instructions available online. Hopefully, this will help others by reducing the number of hours it takes to get this damn thing to work.
The Mini VCI J2534 (aka MVCI) device is a OBDII to USB “dongle” used to connect laptops to Toyota/Lexus vehicles, often for the purpose of using Techstream. This device utilizes a USB to serial signal converter produced by FTDI (ftdichip.com). The chip is essentially a translator so that the computer can communicate with the vehicle, and vice versa. The MVCI I bought had the 1.4.1 firmware (not the 2.0.4) which has the FTDI chip part# FT232RQ.
1) I first started with a freshly reformatted burner laptop with 64bit Windows 10. Never connected to the internet, disabled auto update of drivers using three methods (1. Device installation settings – > “No, let me choose”, 2. gpedit.msc, and 3.regedit), and uninstalled the preinstalled/bloat anti virus.
2) Connected the MVCI to the laptop and saw an unknown device in the Device Manager. Note that only one unknown device was listed, NOT TWO! Many guides state that there should be two: one unknown/warning within the “Universal Serial Bus controllers” and one in the “Ports (COM & LPT)”. I was beginning to think that my dongle was somehow damaged since I only saw one.
3) The two commonly suggested methods for installing the driver for the FTDI chip is to either extract the driver files into C:\Program Files (x86)\XHorse Electronics\MVCI Driver for TOYOTA TIS or to use the AutoKent program, followed by the registry edit program. I did both extract and AutoKent, and ran the registry edit (mvci-x64.reg).
4) Updated the driver of the unknown device by Device Manager -> Right click -> Update Driver -> Browse my computer for drivers -> Let me pick from a list of available drivers on my computer -> Have Disk -> Browse -> [now navigate to XHorse or Autokent folder]. Neither worked as it now showed a yellow exclamation mark.
5) Download/transfer onto the laptop the 22.214.171.124 driver from (ftdichip.com/drivers/d2xx-drivers/) which is the most recent driver for 64 bit Windows. As soon as I dropped the driver onto the burner laptop, the Device Manager picked it up and auto updated, even though it shouldn’t have. The USB Serial Converter no longer has the yellow exclamation mark and the properties of the Converter shows a Driver Version of 126.96.36.199. The red LED of the dongle is now permanently on! Constant red led = computer understands how to use the dongle.
6) Install techstream.
Probably the two important steps were to 1) disable auto update of drivers and/or disconnect from internet and 2) download the latest FT232RQ driver. I was able to get this same cable to work on a 32bit Win7 machine months ago, but the cable would spontaneously work then not. I wonder if it was because the driver was automatically being replaced.
Anyways, all of that work so I can program a new key. The analog on-off (x5), open-close (x6) method to add immobilizers only works if there are 3 or less keys registered.
Although the site was listed version 18. I do not need this program, just for information.
I encountered such a problem that in the disk “MVCI Driver for TOYOTA.msi” the driver was only for 32-bit Windows OS, and I have Windows 10, x64 bit installed on my laptop.
I searched for a driver on the Internet for a long time and came across one, where he left a link to the desired driver and thanks to him for that!
Download “Mini-VCI-Setup.exe” and run, the installation is standard. After installation, this cord appeared in the MMCodingWriter settings and connected to the car without any problems.