This is for anyone that is currently trying to use Techstream software to change dealer settings on their BRZ/FRS with a MINI-VCI cable and software. I know there are a few threads out there already on the subject, but they don't contain any useful guides on how to actually succeed in activating and using this software, it's mostly just download links. I got stuck doing Google searches for about 2 hours trying to figure out if this could be done on a Windows 64-bit computer without the use of annoying Dual Boot or Virtual Machines on XP, and despite what most of these threads say, IT CAN BE DONE! The software works on any OS, but the drivers are the problem so instead they just have to be downloaded manually.
- Mvci Driver For Toyota Cable 2.0.1
- Xhorse Mvci Driver Windows 10 7
- Xhorse Electronics Mvci Driver Windows 10
- Xhorse Mvci Driver Windows 10 Free
I hope this helps some of you guys out. Download all of the files from this Dropbox link: (Even if you have the mini cd, and have the software already, you still need to download the ' mvci-x64.reg' and ' TechstreamUpdateV8.10.021.exe' files from that link. Also, make sure your cd comes with the same version that is listed as mine; 8.00.034.
- How to install MINI VCI Toyota TIS Techstream 10.10.018? Open “MVCI Driver folder”. Xhorse MVCI 3 in 1 Toyota MVCI obd2 interface program keys manua. Mercedes Star diagnosis Windows 7 software C4 12/2015 Xentry Das. 2015A Cat Caterpillar et adapter iii software download, free cat. How to set up Xhorse mvci 3 in 1 original mvci interface driver.
- To fix this, I had to extract the file “MVCI Driver for TOYOTA.msi” using 7zip or the msiexec command. Extract MSI After the extraction, copy all files to the folder: “C: Program Files (x86) XHorse Electronics MVCI Driver for TOYOTA TIS”.
And completely uninstall any traces of previous attempts to download the software) Equipment Needed:. MINI VCI cable for TOYOTA TIS Techstream. I bought mine from Amazon for $25. The cable is about 4’ long, with translucent casing and “MINI-VCI J2534 Standard OBDII Communication Interface” sticker: The cable comes with a mini CD with drivers and Toyota Techstream software. Mine was advertised as “Newest V8.00.034 MINI VCI for TOYOTA TIS Techstream Diagnostic Cable & Software”. The “newest” refers to the version of bundled Techstream, rather than the cable firmware, as cable shows serial number “MVCI006000001” and firmware version 1.4.1, which is widely known as “cheap clone of the original XHorse MVCI cable”.
A laptop running 64-bit version of Windows 7/8. Mine is actually Windows 7 x64, but for Windows 8 the configuration procedure should be identical. The content of bundled mini-CD: The Techstream, MVCI drivers and TIS Key all can be found on the mini disk, but I will leave a.zip download containing them if you guys need them. Steps:.
Download and install a trial version of if you don't already have it. Using WinRAR Unpack the following files from either the mini-CD or the download to a temp folder on your hard drive (Use c: temp). Toyota Techstream 8.00.034 - TechstreamUpdateV8.10.021 - MVCI Driver for TOYOTA - TIS KEY. Now open WinRAR again.
After I installed the software, my Windows 10 didn’t recognized the Mini VCI driver. The instillation CD included “MVCI Driver for TOYOTA.msi”, but when trying to install, I received this error.
Using the program, navigate to the temp folder with unpacked files and double click the TISKey.exe in WinRAR. The TISKey.exe is actually a self-extracting (SFX) RAR archive file.
Once executed, it simply unpacks and copies the IT3System.ini file to the Techstream folder. Extract the IT3System.ini file to desktop for now. Installing MVCI Driver for TOYOTA: This is the step most people stumble on as “MVCI Driver for TOYOTA.msi” installer indeed does not work on Windows x64. The workaround is to install it manually, as follows: Open the Command Prompt in Administrator Mode, and run the following command line: msiexec /a 'C: temp MVCI Driver for TOYOTA.msi' /qb TARGETDIR=c: temp mvci This will extract the content of the MSI file to the c: temp mvci folder. Go ahead and close the Command Prompt window, and open up the c: temp mvci folder:. Delete the “MVCI Driver for TOYOTA.msi” there. (Now go into C: Program Files (x86) and then create a new folder called 'XHorse Electronics' and then inside of that folder create another called 'MVCI Driver for TOYOTA TIS') Then copy the whole content of c: temp mvci to 'C: Program Files (x86) XHorse Electronics MVCI Driver for TOYOTA TIS'.
- Sep 17, 2013 - Mine is actually Windows 8 x64, but for Windows 7 the configuration. The Techstream, MVCI drivers and TIS Key all can be found on the Internet as well. Name: SCI_A_ENGINE Type: REG_DWORD Data: 0.
- TIS 10.10.018 MVCI Driver for TOYOTA.msi Ran 'Xhorse Firmware Update Tool 1.4.8', device info. Can anyone provide a CD with or a downloadable file with the Mini VCI driver for Techstream 10.10.018 or 10.20.030? Or ANY driver that is known to work with the J2534 cable? It also knocked out any internet connectivity when the firewall.
4.1 Click the Setup menu, then click the VIM Select, then select the Xhorse-MVCI in the drop down list of 'Interface Setup', then Click OK Notes: 1. Be sure to disable/uninstall anti-virus software Please note,anti-virus software can flag up this item software as having a virus. If you select that device, Select Update driver, Select Let me Pick From a list of device drivers on my computer (letting windows scan a specific location doesnt work), then click have disk and browse to the location of your MCVI drivers (Should be C:Program Files (x86)XHorse ElectronicsMVCI Driver for TOYOTA TIS) and go to the ftdibus directory and select the ftdibus.inf file.
Plug the MINI VCI cable to the USB port. Open the Device Manager and locate the two failing devices in the list. Both will appear with yellow icon (usually under “Other”), indicating that Windows failed to install drivers for them. Now, right click each failing device, select Install Driver, then “Browse my Computer” and point it for 'C: Program Files (x86) XHorse Electronics MVCI Driver for TOYOTA TIS' (enable the “include subfolders” flag).
Click “Next” and wait until drivers are installed. You should now see two new devices: “Universal Serial Bus Controllers USB Serial Converter” and “Ports (COM & LPT) USB Serial Port (COM5)”. Run the FirmwareUpdateTool.exe from the 'C: Program Files (x86) XHorse Electronics MVCI Driver for TOYOTA TIS'. Click “Device Info”. You should see the “device connected” screen like this:. If you see this, it means your MINI VCI is up and running under Windows x64 and can be used by other programs, such as Techstream.
IMPORTANT: Some people have reported that updating firmware on this “cheap clone” cable may render it dead. So, the Firmware Update Tool should NOT be used for anything, but checking that the device is connected and working properly. Stanley garage door 7200 51 instruction manual. Now install the Techstream software using 'Techstream 8.00.034.exe' and then after installation, open up the 'TechstreamUpdateV8.10.021.exe' file to update it. DO NOT launch it yet. To activate it, drag the IT3System.ini you extracted before to the desktop over into 'C: Program Files (x86) Toyota Diagnostics Techstream Env '. When prompted, overwrite the preexisting file with the new one you are dragging over.
Registry Hack: for Techstream to recognize MINI-VCI under Windows x64, the Registry has to be modified as: Windows Registry Editor Version 5.00 HKEYLOCALMACHINE SOFTWARE Wow6432Node PassThruSu pport.04.04 HKEYLOCALMACHINE SOFTWARE Wow6432Node PassThruSu pport.04.04 XHorse - MVCI 'Name'='XHorse - MVCI' 'Vendor'='XHorse ELECTRONICS Co.,Ltd.' Hello jhood, Sorry for the duplicate msg, but was not sure if first one went through because of being a new member to forum. Thanks for the great detailed write-up on the install. I followed it closely, and every thing really seemed to work just rite. However when I went to run the program I get an error msg. 'unable to connect to VIM' I got the XHorse utility to recognize the VIM, and the program to start, but when connect to vehicle is selected the error msg pops up. I guess I suspect I did not do something correct with the registry hack???
Again thanks, and if you have any ideas that would be great. May need to just get a vista computer for this program, but was hopping to get it going on this one Matt. Hello jhood, Sorry for the duplicate msg, but was not sure if first one went through because of being a new member to forum. Thanks for the great detailed write-up on the install. I followed it closely, and every thing really seemed to work just rite. However when I went to run the program I get an error msg. 'unable to connect to VIM' I got the XHorse utility to recognize the VIM, and the program to start, but when connect to vehicle is selected the error msg pops up.
Mvci Driver For Toyota-cable 2.0.1 Windows 10
Mvci Driver For Toyota Cable 2.0.1
I guess I suspect I did not do something correct with the registry hack??? Again thanks, and if you have any ideas that would be great. May need to just get a vista computer for this program, but was hopping to get it going on this one Matt Mine had the same problem I'm not sure fixed it but I 1) performed the update that Jhood told you to open but not execute ( never actually said to run the update in the write up ) 2) followed the steps after you open the tech stream program under settings to change the VIM it was to look at ( one of the last steps on the writeup) Then mine worked. I'm not sure how relevant this is but there is a seller on the Bay that says ' For toyota and lexus before 2005, we recommend the Original Mini VCI Cable with latest v2.0.4 firmware ( K-line Supported)' which they just happen to sell.
I have a 2001 Land Cruiser and I had ordered the Newest V8.00.034 MINI VCI for TOYOTA TIS Techstream cable and I could get it to connect via your method and my Win 64 laptop (but not my Win 32 laptop oddly enough) but it would not see all of the systems. I could not see a Smart Key or when it ran the Health Data it could not connect to all of the Systems. I just kept searching and searching to find out why I could not and ran across this. So I have returned my other cable and have bought one that supports K-line instead. I hope it will detect a Smart Key this time. Thank you for your write up. Hey ft86!If everything works, you will be prompted to confirm car year/model after which you'll get to the diagnostic interface.
Works great thanks. Followed this to a T on a Lenovo W530 operating Windows 7 64bit. I purchased my cable off of Ebay 'White Mini VCI 16 Pin OBD2 Diagnostic Cable for TOYOTA TIS Techstream' from seller 'nycom-tech' The menu is a little counter-intuitive, but seem to be able to access all features. Also when I ran the firmware update tool, all the device information matched yours exactly.
Hello, everyone! Recently I‘ve got myself the MINI VCI cable to play with. As it turned out, with little manual tweaking it is possible, contrary to the popular belief, to get it working under Windows 64-bit.
Mvci Driver For Toyota Windows 10 Driver
So, I decided to share the instructions, which hopefully will save someone a headache of dealing with dual boot and virtual machines with Windows XP. Equipment:. MINI VCI cable for TOYOTA TIS Techstream. I‘ve bought mine from Amazon for around $30. The cable is about 4’ long, with translucent casing and “MINI-VCI J2534 Standard OBDII Communication Interface” sticker: The cable comes with a mini CD with drivers and Toyota Techstream software.
Mine was advertised as “Newest V8.00.034 MINI VCI for TOYOTA TIS Techstream Diagnostic Cable & Software”. The “newest” refers to the version of bundled Techstream, rather than the cable firmware, as cable shows serial number “MVCI006000001” and firmware version 1.4.1, which is widely known as “cheap clone of the original XHorse MVCI cable”. A laptop running 64-bit version of Windows 7/8.
Mine is actually Windows 8 x64, but for Windows 7 the configuration procedure should be identical. The content of bundled mini-CD: The Techstream, MVCI drivers and TIS Key all can be on the Internet as well. Steps:.
Download and install a trial version of. Using WinRAR Unpack the following files from mini-CD to a temp folder anywhere on your hard drive (e.g. Toyota Techstream 8.00.034.rar - TechstreamUpdateV8.10.021.rar - MVCI Driver for TOYOTA.rar - TIS KEY.rar. Now open WinRAR again, navigate to the temp folder with unpacked files and double click the TISKey.exe in WinRAR. The TISKey.exe is actually a self-extracting (SFX) RAR archive file. Once executed, it simply unpacks and copies the IT3System.ini file to the Techstream folder.
Extract that IT3System.ini to the same folder for now. Installing MVCI Driver for TOYOTA This is the step which most people stumble upon as “MVCI Driver for TOYOTA.msi” installer indeed does not work on Windows x64. The workaround is to install it manually, as follows:. Open Command Prompt in Administrator Mode. Navigate to the c: temp folder and run the following command line: msiexec /a 'C: temp MVCI Driver for TOYOTA.msi' /qb TARGETDIR=c: temp mvci This will extract the content of the MSI file to the c: temp mvci folder:.
Delete the “MVCI Driver for TOYOTA.msi” there and then copy the whole content of c: temp mvci to 'C: Program Files (x86) XHorse Electronics MVCI Driver for TOYOTA TIS'. Plug the MINI VCI cable to the USB port. Open the Device Manager and locate two failing devices in the list. Both will appear with yellow icon (usually under “Other”), indicating that Windows failed to install drivers for them. Now, right click each failing device, select Install Driver, then “Browse my Computer” and point it for 'C: Program Files (x86) XHorse Electronics MVCI Driver for TOYOTA TIS' (enable the “include subfolders” flag). Click “Next” and wait until drivers are installed.
You should now see two new devices: “Universal Serial Bus Controllers USB Serial Converter” and “Ports (COM & LPT) USB Serial Port (COM5)”. Run the FirmwareUpdateTool.exe from the 'C: Program Files (x86) XHorse Electronics MVCI Driver for TOYOTA TIS'. Click “Device Info”.
![Xhorse Mvci Driver Windows 10 Xhorse Mvci Driver Windows 10](https://i.ytimg.com/vi/M0m2frwDbLE/maxresdefault.jpg)
You should see the “device connected” screen like this: If you see this, it means your MINI VCI is up and running under Windows x64 and can be used by other programs, such as Techstream. IMPORTANT: Some people have reported that updating firmware on this “cheap clone” cable may render it dead. Cloudwerx data solutions software for mac download.
So, the Firmware Update Tool should not be used for anything, but checking that the device is connected and working properly. Now install Techstream software using 'Techstream 8.00.034.exe' and then update to 8.10 with 'TechstreamUpdateV8.10.021.exe'. Do not launch it yet. To activate it, copy the IT3System.ini you extracted before to 'C: Program Files (x86) Toyota Diagnostics Techstream Env '. Alternatively, you may copy two files from the C: Program Files (x86) XHorse Electronics MVCI Driver for TOYOTA TIS ProgramFilesFolder Toyota Diagnostics Techstream Env' to 'C: Program Files (x86) Toyota Diagnostics Techstream Env ', which seem to do the trick as well. Registry Hack: for Techstream to recognize MINI-VCI under Windows x64, the Registry has to be modified as: Windows Registry Editor Version 5.00 HKEYLOCALMACHINE SOFTWARE Wow6432Node PassThruSu pport.04.04 HKEYLOCALMACHINE SOFTWARE Wow6432Node PassThruSu pport.04.04 XHorse - MVCI 'Name'='XHorse - MVCI' 'Vendor'='XHorse ELECTRONICS Co.,Ltd.' I too bought the adapter from Amazon for $27 with the intention of either running a VM with XP or a dual-boot with Win7-32 bit in order to utilize the adapter and Techstream.
That was until I found your post, followed your directions and VOILA!! Everything works as you described.
There was a few hickups with the driver update since I tried to install it before without the registry hack and got stuck with a non-working driver for the USB port but I forced it to use the driver using your method and I got thru it. I ran a health check on my wife's 2007 RX400h and everything checks out. Thanks again, you the man! Great instruction Alex, Thanks. I may have a slightly different version, most things look the same as above but not everything.
![Xhorse Mvci Driver Windows 10 Xhorse Mvci Driver Windows 10](https://ae01.alicdn.com/kf/HTB1j2TDJr1YBuNjSszhq6AUsFXab/DHL-Latest-Design-V9-30-002-Original-XHORSE-MVCI-3in1-For-Tis-Techstream-MVCI-J2534-Diagnostic.jpg_640x640.jpg)
I am having some trouble with step 4d, I don't see any failing devices. When I plug and unplug the MVCI cable I can see a USB device come and go, so it must be the cable. I try to install the new driver, but it says the correct driver is already installed.
It try it again, same thing, Ok, maybe it is, so I move on. The firmware update tool works, and I can see the cable, so it must be good. Now #6, Registry hack. In my version, under Pass Thru Support.04.04. Hello everyone, I read here about how to make it work on 64bit, not sure if it helps now but when I ordered mine on ebay some time ago it was from a romanian seller and it has a custom installer: mine works on 64 bit without having to do anything, until now I tested it on win7 64 bit and 32bit and works great. Any chance you can share that installer? I got the cable installed and the firmware tool can see it.
Xhorse Mvci Driver Windows 10 7
When I run Techstream and go to setup - vim, it sees the xhorse. But when I connect connect it still doesn't work. This is on a Windows 8.1 64-bit laptop with a cable bought off Amazon. Any chance you can share that installer?
Xhorse Electronics Mvci Driver Windows 10
I got the cable installed and the firmware tool can see it. When I run Techstream and go to setup - vim, it sees the xhorse. But when I connect connect it still doesn't work. This is on a Windows 8.1 64-bit laptop with a cable bought off Amazon. Ok, I got it so that it connects now fine and I can get real-time and sensor data.
However, when I go to set options it acts like it is getting a list of them and then comes back with nothing. Any ideas how to fix this?
Xhorse Mvci Driver Windows 10 Free
I have techstream 9.x something installed not 8.x.