Mini VCI Toyota Techstream V14 Setup on WinXP 32BIT

Here's the customer feedback on setting up Mini VCI Toyota Techstream V14 software on Windows XP 32bit system.

"I finally got it to work.   I had to use the Techstream 14 files and use the 32bit patch as a connection button. 

For Windows XP 32bit:
1. Install "Techstream_GTS_14.20.019_NDSI"

2. Install "Mini VCI Driver for TOYOTA"

3. Copy and Paste "Techstream Patch 32bit" & place it next to your Techstream Icon on Desktop

4. Hook MINI VCI J2534 Cable to vehicle OBDII port and computer

5. Turn car key to "On" position, lighting up dashboard

6. Start MVCI Firmware Update Tool

7. Start Techstream Software

8. First try connecting to vehicle byway of Techstream software

9. If unsuccessful, try connecting byway of clicking "Techstream Patch 32bit"

10. If #9 is successful, always use it as your connection icon 

https://www.obdii365.com/wholesale/mini-vci-for-toyota-with-toyota-tis.html

Techstream Software Version & Required Adapter

Best I can tell the only XHorse interface firmware version that I used that worked with it is mini vci cable 2.0.4, these are cloned versions of Techstream and the XHorse cable interface, the real Toyota Techstream costs nearly $2000.

Using Techstream 12.30.017 (newest: v14.20.019) with the cheap Mini VCI Cable J25345 over here (Firmware 1.4.1) on a HP-Zbook with Windows 10-64bits prof.
Installed it using the 64bit for Windows 7/8 instructions previously mentioned and on

blog.obdii365.com

You can actually check all stages of the installation without connecting to the car:
First make sure to follow the unpacking/copying instructions in the 64-bit installation instructions before plugging in the cable in the USB port. When installed correctly you should be able to run the firmware update tool to check the firmware. Just do NOT update, only use it to see if the cable is recognized and reports back its firmware version + “connected” status.
If this is OK then at least your interface should be installed correctly, showing a red LED in the process.

Then install Techstream and apply the registry fixes (either manually or by the downloadable registry mod file), also previously mentioned. You can also manually point the original Techstream interface entries in the registry (same location) to the same Xhorse files just to be sure. These settings point Techstream to the correct location of the XHorse driver used for the MVCI Cable.
Also do not forget the TISFUNCTION=0 modification in the IT3System.ini file. If you get “unable to connect to MCI” when connecting to a vehicle most likely these registry settings are not fully correct.

When you now start Techstream with the TSloader make sure the correct interface is selectable (not grayed out) and selected, otherwise re-check the previous setting. Then just connect to vehicle (without actually being connected, just have the MVCI cable connected to the USB port) and you should get no errors but Techstream should eventually (after time out…) come up with a window where you can manually select your vehicle code etc etc.
When I then connected to my RAV4 it connected nicely and I could readout my TPMS sensor ID’s which was my main objective. The interface is flashing green during communication with the vehicle.

So be assured: Techstream can work on a Windows-10 64bit Prof. laptop without the need of a virtual machine.

www.obdii365.com

Techstream Fixed 2007 Lexus LS 460 VSC Lights on

Car model and year: 2007 LS 460 Base model

Symptom: I have had the front two wheel hubs replaced , however I have the VSC, ABS and AFS Off lights on. I used BlueDriver ODD II Bluetooth scanner to get trouble code C1236 LEXUS – Foreign Object Attached On Tip Of Left Front Sensor. When I clear the code it comes right back when I drive the car.

Code is coming back because the problem is still not solved.

What to do next?

Thinking about also ordering a Mini VCI Toyota Techstream cable so I can see more detailed facts about the code.

Update:
Last night I did not have time to jack up the car and put a multimeter to the wire harness connector at the ABS sensor, so I did some other troubleshooting.
I opened the fuse box on the passenger side and checked all the fuses and they all seemed in tact none were blown.
Then I tried looking at the ABS ECU connectors but could not fully pull it and disconnect all the connectors and clean it, so I decided to pull the grey connector that sits on top of it. Once I did that I started the car to see what I got and I got the message of “Break Malfunction pull over immediately…” you know the message.
So that tells me that that ECU is working as it should, I shut the car off , plugged the connector back and started the car again and that message went away.
As noted before I plan on checking the voltage to the connector for the correct reading to eliminate that, if it reads correct then it must be the sensor itself and I will have to pay to get the hub taken off and replaced. (my garage tool arsenal is not that vast!).

I ordered the part off of RockAuto so I want to exhaust all the possibilities.The shop just installed the part, I have a re-order/warranty replacement on standby from RockAuto but will still have to pay for labor.

This is where Toyota TIS Techstream would really help you out.