How-To: TechStream In 5 Minutes (30 Viewers)

[ladymcnei]

Was able to get this working today after a few trouble shooting items. Sorry to hear for all those that are having issues. I was nervous I was going to also be in that bucket, but thankfully made it work.

• The Rig: 2001 LX470
• The Computer: 2012 Macbook Pro Retina (Intel)
• The Cable: I ordered the v18 version on amazon (same link as the post above) "VCI J2534 Cable Fit for Toyota TIS Techstream" Given the firmware is the same (V1.4.8) between the three options listed there, it probably doesn't matter which one you get?
• I followed @getco instructions in the first post and everything installed well
• I got the "Unable to connect to VIM" message with the first attempt out of the box. I found this post (How-To: TechStream In 5 Minutes - https://forum.ih8mud.com/threads/how-to-techstream-in-5-minutes.1034923/post-14687527) which had the fix for me:
  • "1. You need to make sure your cable can be seen by Windows. Make sure the USB device is mounted in VirtualBox settings: VirtualBox -> Devices -> USB -> Select your cable (mine had M-VCI or similar in the name - via USB-C adapter). Windows will beep you once it's found it."
• I got it to all load up, but AHC wasn't there! Doh! Then I read you have to make sure you select LX470 when you start Techstream. Once I did that, I got it all to work!

Huge thanks to getco and all those that have helped trouble shoot this. And sending good vibes to those out there still struggling with this that you too can figure it out.

Was able to check my AHC pressures today, did some torsion bar turns, and what a nice improvement!!!

I ran into this as well with my 2017 Mac. I was able to follow the provided links for the download.
- The Rig: 2008 Toyota Prius Touring, and 2007 Toyota Prius Base,
- The Computer: 2017 macOSMonterey Intel HD Graphics 6000 1536 MB
- The Cable: Amazon product ASIN B097YC5LSR same as above
- The instructions are the same as above, but I want to make them more explicit for newbs like me.

• • "1. You need to make sure your cable can be seen by Windows. Make sure the USB device is mounted in VirtualBox settings ((look at the top of your mac) there should be a dropdown device next to where VirtualBox is controlling your computer that says devices)) ( this took a while for me to find, just look to the top of the mac 0.o): VirtualBox -> Devices -> USB -> Select your cable (mine had M-VCI or similar in the name - via USB-C adapter). Windows will beep you once it's found it." (mine did not beep but it did show via a little USB icon thingy in the bottom right corner of the VB Window)
• I got it to all load up, but AHC wasn't there! Doh! Then I read you have to make sure you select your vehicle name and if needed type in the vin when you start Techstream. Once I did that, I got it all to work!
• THANKS AGAIN to the person who uploaded these links and instructions. You saved us $160 today on Toyota diagnostics.

 

[r2550g]

I figured out what went wrong and it's working now.

My install was based on the instructions on VXDIAG. A few things that I've changed from previous install:

1. Plugged in the dongle before running VX manager. Make sure you see the dongle in the VX manager app.

2. Do NOT open Techstream using the the real Techstream icon that was created on your desktop. You have to go to the BIN folder and use the Toyota Launcher application, it will automatically bring up Techstream. By doing it this way, Techstream no longer ask for the Key. I created a shortcut to put on my desktop so I will not need to dig through the folders to find the Toyota Launcher next time.

3. After Techstream is loaded, go to Setup>VIM Select> open the dropdown and choose TOYOTA-J2534. This is something that's not listed in the instruction but it's super important because the default is TIS Techstream VIM. If you don't choose TOYTO-J2543, your dongle will not talk to your Techstream.

4. I have a press button start car. Press the start button on the car twice. Connect your car to the dongle. Click connect to vehicle in Techstream and you should see your car's information automatically populated.

Good luck!

Thank you for the info! I am trying to get TechStream on my computer too and wonder if you still have the link to buy the interface that really works. There are too many sellers on eBay/Amazon, I bought one a few years but never got it work, si I gave up that time. Thanks a lot!!

 

[Jimmu]

I am trying to perform a 'Headlight ECU Sub-Assembly LH Initialization' in techstream (12.20.024) on a 2016+ LC200 Australian Model.
The instructions direct me to Body Electrical / AFS / Utility / Height Sensor Initialization but there is no Height Sensor Initialization utility there.
I have tried all the various vehicle options at the connection screen without success.

Can anyone point me in the right direction please?

TIA Jimmy

 

[SteveH]

I got Techstream working, and I can see all the AHC components (for example), but I can't actual values (like current pressure values). Techstream seems to want my VIN entered - should I do that, and would that affect this? Thanks!

 

[LowDrag82]

I got Techstream working, and I can see all the AHC components (for example), but I can't actual values (like current pressure values). Techstream seems to want my VIN entered - should I do that, and would that affect this? Thanks!

Yes do the vin that way it knows the specific revision of your truck

 

[SteveH]

Edit: - problem solved: VIN not needed, but to see AHC pressures in Techstream while the truck is running, you must cycle the AHC from 'Low' to 'High' and then Techstream will display the pressures. Cycling from 'N' to 'Lo' did not cause the pressures to show up.

Anyway - I cycled my AHC several times and watched the pressures, which sometimes were the same, and sometimes slightly different.

I entered the VIN and it still won't show AHC pressures. I can do things like command the AHC solenoids and turn the fuel pump on/off. I'm running Techstream 17 on Windows 10.

 

[j404]

I've read through 15-20 pages and not seeing this question:

The OP includes instructions/link for techstream 12.

All of the cables sold seem to be for either techstream 16, 17, or 18.

2020 heritage, is there any benefit to buying the v18 cable and tracking down v18 software?

Primarily for key programming, but don't want to be limited in what I can do after spending the time to get everything working

 

[magikaram]

What's the trick to get the Windows XP VM to boot up in something besides Safe mode? If I try anything else, it aborts the operation...

I can get to TS in safe mode, but I don't think the USB ports are on in that mode, so I get the "unable to connect to VIM" error like above.

I may be too late for the specific user I'm replying to, but I'm on Windows 10, not MacOS like some of the recent users who've been successful in getting the #1 post techstream running.

I delved into figuring out why the Windows XP VirtualBox image, it would crash upon loading. Safe Mode would run, but prohibit access to the USB devices, especially the mVCI cable.

Turns out, that Windows 10 often is enabling Virtualization-based Security by default, so you want to disable that for the virtual machine to run and have access to your USB devices when starting normally (and not in safe mode):

1. Check if virtualization is enabled.
   1. Windows Key > Type 'system information' > enter.
   2. Scroll down in 'System Summary' to the record "Virtualization-based Security | Running"
2. Disable VBS/HVCI
   1. Windows Key > Type 'core isolation' > enter
   2. Toggle 'Memory Integrity' to 'off'. (Keep it off if it is already off) then reboot (don't need to if it's already off)

   3. ---

      Win + R > 'regedit' > enter
   4. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\DeviceGuard
   5. Set EnableVirtualizationBasedSecurity to 0 (zero). (if it does not exist, then do not worry about editing this registry key, and proceed to the next direction).

   6. ---

      Windows Key > Type 'turn windows features on or off' > enter.
   7. Scroll down to 'Virtual Machine Platform' and uncheck the box.
   8. Reboot your machine.
3. Redo step 1.1 & 1.2 to confirm that the entry says 'Not Running'.

It took until 2.6 for me - but others it may be one of the prior steps to disable VBS. With VBS disabled, I'm now successfully able to start the Techstream virtual machine without issue.

 

[veiloctane]

Techstream Install Files - Google Drive

drive.google.com

 

[j404]

Techstream Install Files - Google Drive

drive.google.com

This is version 8? Any point in using the newer 17 or 18?

 

[j404]

Correct, just be careful which "launcher" you use, or run Techstream in a VM or on a machine you don't care about.

Okay, can you link to the correct "launcher" please

 

[veiloctane]

Okay, can you link to the correct "launcher" please

I shared what is Version 18

compatible with

Tactrix Openport 2.0 (id pay a bit more for legit one than knockoff version)​

 

[tjb]

This is version 8? Any point in using the newer 17 or 18?

I found this to be the same - Version 8. It wouldn’t run without an ID.

I’ve used Techstream for a few years, but suddenly I was prompted for a new ID And was forced to upgrade the version by the software. (Might have been the other order - forced to upgrade, then new ID.)

I’ve not been successful in installing a different version that works. Does anyone have a link to a version with either a launcher or a valid ID? (I’m running Windows 95 in a VBOX on a MacBook.)

I’ve had CEL and VSC TRAC and VSC OFF lights on (that checked to an 02 sensor on a standard ODBII dongle) but yesterday my AHC failed and is stuck in low. Really could use Techstream right now.

 

[irubix]

Hi folks, thanks for this awesome thread.

I can't get the Apple Silicon (UTM) version working- it says "Unable connect to VIM" (despite the other tool saying it's connected).

I dont' think it's my cable, as it works fine on an Intel machine.

Has anyone else had this issue on an Apple Silicon?

View attachment 3439833

Same issue, techstream wants to immediately connect, without launching the main window to properly configure it.

Ive tried to change the launch params in the shortcut but this doesnt work. Hoping @getco can assist.

 

[tjb]

I found this to be the same - Version 8. It wouldn’t run without an ID.

I’ve used Techstream for a few years, but suddenly I was prompted for a new ID And was forced to upgrade the version by the software. (Might have been the other order - forced to upgrade, then new ID.)

I’ve not been successful in installing a different version that works. Does anyone have a link to a version with either a launcher or a valid ID? (I’m running Windows 95 in a VBOX on a MacBook.)

I’ve had CEL and VSC TRAC and VSC OFF lights on (that checked to an 02 sensor on a standard ODBII dongle) but yesterday my AHC failed and is stuck in low. Really could use Techstream right now.

I went back to post 1 and did a complete reinstall - it’s working again.

 

[GXgeorge]

Getting Techstream up and running can be a bit of a pain. Hopefully this helps someone get started quickly.

Step 1: Purchase an OBD-II / Mini-VCI interface.
- I have sold out of my cables and supply chains are back in order, so no reason to purchase more. Anything like this will work: Mini-VCI cable on eBay

Step 2: Download Hypervisor

• Windows / Intel Mac [Download Virtualbox]
  • Windows: https://download.virtualbox.org/virtualbox/7.0.2/VirtualBox-7.0.2-154219-Win.exe
  • MacOS: https://download.virtualbox.org/virtualbox/7.0.2/VirtualBox-7.0.2-154219-OSX.dmg
• Apple M1/2 Mac [Download UTM]
  • MacOS: https://github.com/utmapp/UTM/releases/latest/download/UTM.dmg

Step 3: Install Software You Just Downloaded

• Windows: Double-Click downloaded file
• MacOS:
  • Intel Mac: Double-Click downloaded file, run installer
  • M1/M2 Mac: Double-Click downloaded file, drag to Applications folder

Step 4: Download TechStream Image:
- Windows / Intel Mac: LINK
- M1/M2 Mac: LINK

Step 5: Double-Click downloaded file.

Connect & Enjoy.



-g

Edit (04/08/18): I removed the more expensive cable, as I received a new Mini-VCI cable that works 100% at 1/4 the cost.
Edit (02/28/21): Updated links to new versions of Virtualbox & new link to cheap Mini-VCI cable
Edit (10/30/22): M1 Compatible workflow / updated virtualbox links

This is potentially a life saver, I have 2003 GX470 I plan to DIY full brake master cylinder assembly replacement. There is some useful texturing and bleeding capability in Techstream that Dealers and shops make hard to figure out without going to them. Bought a cable to connect and will follow your M1 MBP protocol and cross my fingers this connects!!

I have heard here Toyota Techstream for ALL Windows | How to Install and get it WORKING Everytime | Landcruiser 200 (youtube.com)
that it might be wise to get 32 bit Windows virtual machine to be safe, so if I run into issues I'll try that. Will update here how it goes - thank you!!

 

[j404]

I received my vxdiag nano usb cable. The vxdiag supplied vx manager and drivers are windows 7+ only. It won't install on XP. Has anyone found a workaround that works with the virtual image version provided in this thread?

 

[DilzToyotaGuy]

Hello everyone I have downloaded all the necessary files for M1 Mac when I open tech stream in my UTM Virtual box I immediately get a msg saying tech stream is out of date and it will not allow me to use the program. Can anyone help please? thank you

 

[tjb]

Hello everyone I have downloaded all the necessary files for M1 Mac when I open tech stream in my UTM Virtual box I immediately get a msg saying tech stream is out of date and it will not allow me to use the program. Can anyone help please? thank you

I was fighting this for a few days on an Intel based Mac and finally went back and reinstalled the TechStream image, deleting the first image that I had been using. It worked then. Can't explain why that worked.

 

[DilzToyotaGuy]

I was fighting this for a few days on an Intel based Mac and finally went back and reinstalled the TechStream image, deleting the first image that I had been using. It worked then. Can't explain why that worked.

I will delete everything and try again then