(Solution) Mini VCI + Toyota TIS Techstream 8.x on Windows 7/8 64-bit.

Well I just spent the last 3 hours monkeying around with my M-VCI chord that I bought off eBay. I was installing it on a Windows 7 /64 bit machine. Got it to install and the chord to be recognized, but was getting the dreaded Unable to connect to VCI message. It was driving me crazy. Finally as someone mentioned in this thread and on other sites, I realized that one of my folders was barely mislabeled. Once that was fixed I finally got in and was able to customize.

Big thing was turning off the annoying ECO-bar on the display. Also turned off the driver seat belt off buzzer. I was hoping there would be an option for one button unlock, but I didn't see that option available on there.

Overall worth the $16.95 and the hassle.
 
Stupid Questions

I have to start by saying I have search all afternoon before I decided to post here. I got a TIS cable from ebay (probably from China who knows). I installed the TIS software 12.01.019 and got it working no problem. The seller on ebay did tech support and got it working on my Windows 10 tablet. So yea! Now the problem is the cable. It is not working. I can plug it in and windows find drivers. There are no yello ! in device manager after I plug it up. The light ont eh cable stays green after I plug it up. But, the firmware update tool (to check and see if it is working ) will not work. AT ALL.

So undeterred, I went ahead and plugged it into my OBD port on my 2014 limited and told the TIS software to connect to vehicle. And error, no VIM cable. I double checked the directory names, they seem fine, double checked the registry hack to make sure all the information was there, seems fine. Now I am stuck.

Oh and I should point out, that when I disconnected it from the truck, the truck did weirdness. The warning lights for key in the truck came on and it pinged at me for a while. I undid the positive on teh battery for an hour or so and that was fixed.

Any suggestions here would be greatly appreciated.
 
I have to start by saying I have search all afternoon before I decided to post here. I got a TIS cable from ebay (probably from China who knows). I installed the TIS software 12.01.019 and got it working no problem. The seller on ebay did tech support and got it working on my Windows 10 tablet. So yea! Now the problem is the cable. It is not working. I can plug it in and windows find drivers. There are no yello ! in device manager after I plug it up. The light ont eh cable stays green after I plug it up. But, the firmware update tool (to check and see if it is working ) will not work. AT ALL.

So undeterred, I went ahead and plugged it into my OBD port on my 2014 limited and told the TIS software to connect to vehicle. And error, no VIM cable. I double checked the directory names, they seem fine, double checked the registry hack to make sure all the information was there, seems fine. Now I am stuck.

Oh and I should point out, that when I disconnected it from the truck, the truck did weirdness. The warning lights for key in the truck came on and it pinged at me for a while. I undid the positive on teh battery for an hour or so and that was fixed.

Any suggestions here would be greatly appreciated.

I program modules for cars, as a hobby.

For Techstream, did you go to VIM select and choose your cable?
 
TIS stream questions

Thanks so much for the follow-up. I decided that I should just take the time and call tech support. Or more correctly email them. They got on teamviewer and got it working for me. So now the cable works and the software works. They were great.
 
I got a cheap cable from eBay and was pleasantly surprised when I got tech support. He came on TeamViewer and helped get it working on my windows surface running Windows 10 and then helped me with the driver for the cable. If anyone needs help in Richmond shot me a PM. I would be happy to help.
 
Anyone have a recent cable they bought that worked? I am looking to buy and it sure looks like I need to make sure i get the 'right one' to start before trying to make it work with Win10. I had been looking at the Mangoose VCI and the Mini VCI as options but I have Win10. Sounds like some have gotten it to work and I have a few computer whiz friends that might be able to help. I just want to make sure to get one that gives me the best chance to make it work.

Can anyone with Win 10 who has made it work chime in with what OBDII connector cable you used.
 
Just got my cable today (ordered this one for $16) and did not have a CD/DVD drive in any laptop, so I thought I was screwed. However, I d/l an even newer version of Techstream, 12.20.024, from this link and followed the directions in the OP in this thread. I did it on Windows 10 and there were a few hiccups.

1) There was no Firmwearupdatetool.exe so I had to skip that step.

2) The names of the devices were not the same. I found "Universal Serial Converter" under the "Universal Serial Bus Controllers" heading and "USB Serial Port" under "Ports (COM & LPT)" and made sure it was COM4 (use the advanced button under port setting of the properties to change it. I tried to do the update driver on each and point to the xhorse directory, but both said the current driver was newer.

3) I did do the registry update/merge and once I did that it worked.

4) As to the key, there is a txt file that has the key in it that you have to use to activate it. (Instructions.txt)

I connected my 2012 Camry as it sit the newest Toyota we have and TEchstream worked flawlessly. For reference, the DLC3 cable diagnostic showed only K and L as red, while all the rest, including CAN-L and CAN-H as green. So, no ECU flashing. Still trying to figure out what the K line does.

So, I can confirm that it DOES work in Win 10, you just need to "wiggle it a bit" to make it work. :-)
 
Just wanted to confirm that these instructions do work on Windows 10 Pro 64-bit with V12.10.019. Thanks again to [MENTION=99758]alex4wd[/MENTION] for the write up!
 
Awesome thanks, just installed 12.20.024 version and it worked. Struggled with the thing all day till came across this thread. Did not have any device installation issues, but did have to merge the reg key to make this work.
 
I have a BRZ and the techstream platform is pretty new to most of us. As far as i know none of us have been able to program TPMS id's with one of the cheap cables. Do you know if the L line is needed for this function?
^^ This. I have the same question. Been struggling for a while trying to registering TPMS IDs with Techstream using a knock-off cable.


Also, anyone come across a free download of TS 13 yet?
 
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. 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:
  1. 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:

    attachment.php


    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”.

  2. 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:

attachment.php


The Techstream, MVCI drivers and TIS Key all can be found on the Internet as well.

Steps:

  • Download and install a trial version of WinRAR

  • Using WinRAR Unpack the following files from mini-CD to a temp folder anywhere on your hard drive (e.g. c:\temp).

    - Toyota Techstream 8.00.034.rar
    - Techstream_Update_V8.10.021.rar
    - MVCI Driver for TOYOTA.rar
    - TIS KEY.rar

    attachment.php


  • Now open WinRAR again, navigate to the temp folder with unpacked files and double click the TISKey.exe in WinRAR.

    98108d1379403636-solution-mini-vci-toyota-tis-techstream-8-x-windows-7-8-64-bit-04-unpack-tiskey-jpg


    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:

      98109d1379404181-solution-mini-vci-toyota-tis-techstream-8-x-windows-7-8-64-bit-05-unpacked-msi-jpg


    • 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”. You should see the “device connected” screen like this:

      98110d1379404547-solution-mini-vci-toyota-tis-techstream-8-x-windows-7-8-64-bit-07-status-check-jpg


      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.

  • Now install Techstream software using "Techstream 8.00.034.exe" and then update to 8.10 with "Techstream_Update_V8.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

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PassThruSupport.04.04]

    [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PassThruSupport.04.04\XHorse - MVCI]
    "Name"="XHorse - MVCI"
    "Vendor"="XHorse ELECTRONICS Co.,Ltd."
    "ConfigApplication"="C:\\Program Files (x86)\\XHorse Electronics\\MVCI Driver for TOYOTA TIS\\FirmwareUpdateTool.exe"
    "FunctionLibrary"="C:\\Program Files (x86)\\XHorse Electronics\\MVCI Driver for TOYOTA TIS\\MVCI32.dll"
    "APIVersion"="04.04"
    "ProductVersion"="1.1.0"
    "ProtocolsSupported"="J1850VPW:1, J1850PWM:1, CAN:1, ISO9141:1, ISO14230:1, ISO15765:1"
    "J1850VPW"=dword:00000001
    "J1850PWM"=dword:00000001
    "ISO9141"=dword:00000001
    "ISO14230"=dword:00000001
    "CAN"=dword:00000001
    "ISO15765"=dword:00000001
    "SCI_A_ENGINE"=dword:00000000
    "SCI_A_TRANS"=dword:00000000
    "SCI_B_ENGINE"=dword:00000000
    "SCI_B_TRANS"=dword:00000000


    The attached "mvci-x64.zip" contains the *.REG file that has to be imported to the Registry (extract, right click, then Merge)

    A trick here is the "Wow6432Node" in key path, which is the location the 32-bit applications running on 64-bit OS get redirected to when accessing Registry. The "PassThruSupport.04.04" seems to be the place Techstream looks into for available VIMs (sub-keys appear in the "VIM Select" menu in Techstream).

  • Run Techstream. Go to Setup | VIM Select menu and select the “XHorse - MVCI”

  • Connect MVCI cable to your car’s OBDII interface, turn ignition on, then click “Connect to Vehicle” in Techstream. Wait. Then wait again (by the way, you'll be doing that a lot with this cable :)). If everything works, you will be prompted to confirm car year/model after which you'll get to the diagnostic interface.

The built-in Techstream cable diagnostics shows:

98113d1379406655-solution-mini-vci-toyota-tis-techstream-8-x-windows-7-8-64-bit-06-cable-test-jpg



So far, I tested the cable with 2013 4Runner, 2004 Sienna and 1997 Camry LE/4cyl, and it seems to work fine with all of them. Absence of (L) line connection means no support for ECU re-flashing (which is not something I'm comfortable doing myself anyway). Option customization/clearing DTC is possible (already verified).

Overall, not bad for a $30 gadget, in my opinion.

Good luck!

Alex.

Hello Alex4wd. Really appreciate the trouble you have gone to to get Techstream working on a 64bit computer.

I'm having trouble with the MVCI program. The drivers are installed - according to Device Manager - but the XHorse Firmware Update Tool isn't working. Might this be something to do with the registry you provided differing to the install file versions I have?

Any other reasons why I should be having trouble at that one hurdle?
 
Error codes

Hope this helps?

Log Name: Microsoft-Windows-Kernel-PnP/Configuration
Source: Microsoft-Windows-Kernel-PnP
Date: 22/02/2019 22:34:24
Event ID: 442
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer: Snuffs-PC
Description:
Device USB\VID_0403&PID_6001\A62YRDF8 was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\VID_152D&PID_2337\DCAA0969709F
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: PCIROOT(0)#PCI(1D00)#USBROOT(0)#USB(1)#USB(3)
Migration Rank: 0xF000FFFFFFFF0023
Present: false
Status: 0xC0000719
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Kernel-PnP" Guid="{9C205A39-1250-487D-ABD7-E831C6290539}" />
<EventID>442</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x4000000000000000</Keywords>
<TimeCreated SystemTime="2019-02-22T22:34:24.014282900Z" />
<EventRecordID>826</EventRecordID>
<Correlation />
<Execution ProcessID="4" ThreadID="5460" />
<Channel>Microsoft-Windows-Kernel-PnP/Configuration</Channel>
<Computer>Snuffs-PC</Computer>
<Security UserID="S-1-5-18" />
</System>
<EventData>
<Data Name="DeviceInstanceId">USB\VID_0403&PID_6001\A62YRDF8</Data>
<Data Name="LastDeviceInstanceId">USB\VID_152D&PID_2337\DCAA0969709F</Data>
<Data Name="ClassGuid">{36FC9E60-C465-11CF-8056-444553540000}</Data>
<Data Name="LocationPath">PCIROOT(0)#PCI(1D00)#USBROOT(0)#USB(1)#USB(3)</Data>
<Data Name="MigrationRank">0xf000ffffffff0023</Data>
<Data Name="Present">false</Data>
<Data Name="Status">0xc0000719</Data>
</EventData>
</Event>
 

Members online

Forum statistics

Threads
278,316
Messages
3,554,120
Members
248,016
Latest member
Advally Service

Trending content

Back
Top