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

This site may earn a commission from merchant affiliate
links, including eBay, Amazon, Skimlinks, and others.

I've been searching for a solution else where for a week, found solution here on 1st page. I really appreciate getco for his brilliant idea to containerise the package in a virtual machine and sharing here.

I just wanna share my set-up experience.

Installed the VM and XP image with TS given on first page, when the OS spun up, it worked right out of the box.

I have recent windows 11 Pro, on Yoga9, installed the Oracle VM, got warning to install python, ignored anyway and continued to spin up TS, but XP crashing as soon as that loading bar appeared. Then I updated VM and this time installed python and other dependencies (found how to guide by simply searching online), then I got that nostalgic boot up sound from my childhood, then I got connected USB sound, then I opened xhorse, clicked connect, it connected immediately.

Then I opened TS, it says VIM not connected. Then I changed the device to xhorse, then it's connected!

It's got my vehicle profile Rav4 hybrid until 2018, but I got 2024 variant. I don't think any option missing on this. I changed optional settings today. Probably explore other options later.

Cheers!
 
I've been searching for a solution else where for a week, found solution here on 1st page. I really appreciate getco for his brilliant idea to containerise the package in a virtual machine and sharing here.

I just wanna share my set-up experience.

Installed the VM and XP image with TS given on first page, when the OS spun up, it worked right out of the box.

I have recent windows 11 Pro, on Yoga9, installed the Oracle VM, got warning to install python, ignored anyway and continued to spin up TS, but XP crashing as soon as that loading bar appeared. Then I updated VM and this time installed python and other dependencies (found how to guide by simply searching online), then I got that nostalgic boot up sound from my childhood, then I got connected USB sound, then I opened xhorse, clicked connect, it connected immediately.

Then I opened TS, it says VIM not connected. Then I changed the device to xhorse, then it's connected!

It's got my vehicle profile Rav4 hybrid until 2018, but I got 2024 variant. I don't think any option missing on this. I changed optional settings today. Probably explore other options later.

Cheers!
By the way, I disabled VM network option at the moment when I'm importing the TS XP image
 
I recently got this.

Dell Latitude E6440 14-inch Laptop - Intel Core i5 4310M 4th Gen 8GB - 256GB SSD DVD-RW Windows 10 Pro (Renewed)​

and this

VCI J2534 Cable Fit for Toyota TIS Techstream - Latest Version V17.00.020, Firmware V1.4.8, OBD2 to USB Diagnostic Cable, Support Win XP WIN7 WIN10 32/64bit​


Everything was simple to install and figure out how to operate. No VM needed. Just use the 64 bit patch. I was able to see everything in all the ECUs and make sure there were no codes, no misfires and everything is in spec.
And tonight, after years of having the VSC and Traction Control lights on my dash in my 2003 Camry, I finally got rid of it! DTC C1336. Went into the VSC ECU, cleared the code, reset memory and did a calibration test. Only took a few minutes. The Techstream investment has already paid for itself.
The adapter gets crappy reviews…is it because people are trying to use the crappy software that comes with it rather than the VM on page 1?
 
@getco
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
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.

:santa:

-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
Hi there.

Thank you posting this and keeping it updated.

I have a cable and have downloaded and installed all the software as recommended. It all runs well, and boots up and connects as per.

I only have one issue. When selecting the vehicle (I have a 2005 LC with a 1HD-FTE engine), the only engine options I can find for any Land Cruiser is the 2UZ-FE (4.7L V8 petrol). I've looked in as many places as I can, but can't find a 1HD-FTE (or any diesel) option. If I try to change my Location/Region I get asked for the new key, and the one supplied has expired. (I have to delete that image and start again to get it to go anywhere.)

What am I missing?

Cheers,

Chris.
 
@getco

Hi there.

Thank you posting this and keeping it updated.

I have a cable and have downloaded and installed all the software as recommended. It all runs well, and boots up and connects as per.

I only have one issue. When selecting the vehicle (I have a 2005 LC with a 1HD-FTE engine), the only engine options I can find for any Land Cruiser is the 2UZ-FE (4.7L V8 petrol). I've looked in as many places as I can, but can't find a 1HD-FTE (or any diesel) option. If I try to change my Location/Region I get asked for the new key, and the one supplied has expired. (I have to delete that image and start again to get it to go anywhere.)

What am I missing?

Cheers,

Chris.
Chris, you need to select the Europe region, to see the 1HD-FTE. (See expired key solution below)
I have a 1HD-FTE 2005 and a 2UZ-FE 2009 and both work 100% on Techstream.

The key expiry problem when selecting Europe is date related.

This is what I did: (From my Post #1,331)

I disconnected my PC from the internet.
Then I switched off "Set time Automatically" under Settings/Date & Time.
Then manually set the date to 01 Jan 2024.
Then ran the setup OVA file and installed Techstream as per normal procedure.
Then Launched Techstream and under the "Setup/Techstream Configuration" Tab set the area, etc to: Europe, English, 111, 111, 111, United Kingdom, Authorized Repairer, then click "OK"
Then close/exit Techstream. (Exit/Close Techstream only, not the Virtual Machine)
Then launch Techstream again.
Then click "Connect to Vehicle"
Enter the given Key

And now it works !!

Set PC time to automatically update time again, reconnect to the internet and everything should be back to normal and work.

Enjoy !!
 
Chris, you need to select the Europe region, to see the 1HD-FTE. (See expired key solution below)
I have a 1HD-FTE 2005 and a 2UZ-FE 2009 and both work 100% on Techstream.

The key expiry problem when selecting Europe is date related.

This is what I did: (From my Post #1,331)

I disconnected my PC from the internet.
Then I switched off "Set time Automatically" under Settings/Date & Time.
Then manually set the date to 01 Jan 2024.
Then ran the setup OVA file and installed Techstream as per normal procedure.
Then Launched Techstream and under the "Setup/Techstream Configuration" Tab set the area, etc to: Europe, English, 111, 111, 111, United Kingdom, Authorized Repairer, then click "OK"
Then close/exit Techstream. (Exit/Close Techstream only, not the Virtual Machine)
Then launch Techstream again.
Then click "Connect to Vehicle"
Enter the given Key

And now it works !!

Set PC time to automatically update time again, reconnect to the internet and everything should be back to normal and work.

Enjoy !!
Thank you. I was SO close. I'd deduced that it was date related. I did 'air gap' the computer and change the date, but that was AFTER I'd run the Techstream, and I was using 'Other' region (I'm in Australia).

Thanks again. I'll give that a try.

Chris...
 
Chris, you need to select the Europe region, to see the 1HD-FTE. (See expired key solution below)
I have a 1HD-FTE 2005 and a 2UZ-FE 2009 and both work 100% on Techstream.

The key expiry problem when selecting Europe is date related.

This is what I did: (From my Post #1,331)

I disconnected my PC from the internet.
Then I switched off "Set time Automatically" under Settings/Date & Time.
Then manually set the date to 01 Jan 2024.
Then ran the setup OVA file and installed Techstream as per normal procedure.
Then Launched Techstream and under the "Setup/Techstream Configuration" Tab set the area, etc to: Europe, English, 111, 111, 111, United Kingdom, Authorized Repairer, then click "OK"
Then close/exit Techstream. (Exit/Close Techstream only, not the Virtual Machine)
Then launch Techstream again.
Then click "Connect to Vehicle"
Enter the given Key

And now it works !!

Set PC time to automatically update time again, reconnect to the internet and everything should be back to normal and work.

Enjoy !!
Did you you said and now it works!! Thank you.

Chris.....
 
Many thanks to getco for compiling this and making it available to all of us.

My application - 2016 Tacoma SR5 Double Cab Long Bed 3.5L V6/Auto. Will this version of Techstream support my vehicle? Can we update TS to newer versions and have this method work? I doubt it because getco packaged this in a specific manner. It would be nice to be wrong here!

Concerns/Questions - Please respond to any you can answer definitively.
I just downloaded all the files indication in Post #1. I'm using a Win 10 Pro laptop and may need to repeat this for my dual-boot Win 7 Pro based on some comments I read early in the thread - I have not read each post yet.

Installation of VirtualBox creates issues to be solved/questions. The answers to the issues I faced are as follows:

1 - Visual C++ Redistributable 2015-2019 x86 and 2015-2022 x64
VirtualBox noticed the Win10 pc I am using had an older version of this application and forced me to upgrade it before I could perform the installation. See here (Latest supported Visual C++ Redistributable downloads - https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170#latest-microsoft-visual-c-redistributable-version)

2 - MissingDependencies Python Core/win32api
Requires Windows users to install Python. Reference this url, read it thoroughly, and perform each of the steps described (How to Fix Python win32api in VirtualBox | Quick Solution! - https://www.sysnettechsolutions.com/en/fix-python-win32api-virtualbox/).

That's it. I hope this works for me but I will not know until I receive the mini VCI cable. I am not initially going to purchase the VXDiag unit.
 
I see no means for me to edit my previous post so I'll have to add this. Do I need to purchase a VCI cable with the same version number as the Techstream version we obtain? These cables are marketed in this manner so it poses a question as to what we must purchase.
 
Thought I would share my experience with this wonderful tool as a user in the USA.

The first time I fired it up, it said the license key for the software was expired. Nothing changed that, even copying the code from the text file on the desktop didn't work.

So I removed the virtual machine and imported the machine again. On the reload, I disabled the audio and the network for the virtual machine from the start.

After it loaded and was ready to be launched, I edited the USB settings so the data cord was shared to the VM.

Opened/launched the VM, it booted up just wonderfully and when I clicked on the app, it loaded without any issues.

Connected right up to my 2014 Sequoia.

Huzzah!!
 
  • Like
Reactions: Eph
so i managed to get version 12 and version 18 of tech stream to work.

i have a 1998 LC, and there doesn't seem to be many options. i was wondering if any of guys could compare the options i have to yours in a similar 1998

only ECU's available are :

Engine ECT

Cruise Control

ABS/VSC/TRAC

Immobiliser

SRS Airbag

no options under Customize Setting

could it be since its a 1998 i dont have power options like windows or lights?
 
Yes. There are no ECUs for what you don't have.

You probably don't have the immobiliser either. If you do have it, you can program a key with T.S.
Gotcha , I figured , just wanted to double check. Luckily I do have the immobilizer. So brake bleeding and key programming is good enough for me lol
 
Hello all,
I'm on Apple sillicon. I downloaded the proper UTM from page 1, but my cable is not recognized by XHorse firmware update tool.
Screenshot 2024-12-09 at 7.11.22 PM.png

I am able to see the USB connection on the VM top right options, but cannot find it in the USB Manager menu. Any idea why?
Screenshot 2024-12-10 at 8.49.10 AM.png
 
TechStream v18.00 – working & connected - how I did it.

After several (many), false starts, dead-ends, and a few peeks into sketchy corners of the internet – TechStream is up and working for my ’21 LC200 LE. Thought it might be helpful to lay out the path that ended up working for me. I'm sure there are easier ways, but this was my not-so-easy way

Again, this is not the “Easy” button in any way, or the 5min solution. The beginning of this thread seems to have the easy way covered – but that was only for TechStream v12. I wanted the latest TechStream version I could run so it captured everything with my ’21.

[Note: Yes, I tried converting the Mac-based VM for TechStream v17 (UTM file) into something that worked on a PC-Based VM, but that was a dead end for me after several attempts at different VM clients, conversion software, etc.. Maybe this 65 page thread had the answer somewhere, but I couldn’t find it.]

Here is my setup & path

Basics / System / Setup:
  1. PC / Machine: 8 year old Lenovo X1 Carbon Gen 3 laptop. Running Windows 10 Pro (old work laptop). Lives in the garage – if it totally dies or gets corrupted, no biggie to me.
  2. All of the below was done using a Virtual Machine (VM) – running on VMware Workstation 17 Player. Most of the connections to different websites were done via VPNs from inside the VMs. The why will become apparent below.
  3. VM – I started with a plain vanilla Windows 10 Enterprise LTSC VM image that was working. This came from getting my Volvo’s VIDA system up and going (VIDA is Volvo’s equivalent to Toyota’s TechStream). Got it here https://volvodiag.com/ for $5
TechStream:
  1. Found a downloadable source for TechStream V18 in the forum below (begin journey to sketchy internet places) https://mhhauto.com/Thread-TOYOTA-Techstream-V18-00-008-02-2023-Activation
  2. First post on the above forum thread has the download link as: Яндекс - https://disk.yandex.ru/d/_RosgIIDNM9vrQ (Yes, that is dot .ru of Russia fame)
  3. Had to set up an account on Yandex.ru to get a “disk” account, and then could download the file (this is the second step down an internet dark alley) Suggest having some ‘disposable’ e-mail addresses ready – and again, ALL of this was done inside the VM. Also, handy to have one of the “autotranslate” browser extensions working as Yandex is natively Russian.
  4. Downloaded (into VM ONLY – not into any real machine) Techstream v18 from the yandex.ru link above.
  5. Installed TechStream on VM, ran it, and it Opened!! YAY. However, no software key.
  6. Back to mhhauto.com. It seems you can “post” your software ID on the forums in mhhauto.com, and someone somewhere has a software key generator that works. However, to “post”, you first need to “register” an account with mhhauto.com. Registration costs $30 or 200RMB. Few methods to pay (PayPal being one), and yes, it appears you are sending this website “registration” payment to China (third step into internet dark corners).
  7. Once you pay the $30, half a day later or so you will get an e-mail with a “Registration ID”. You can use this to set up your account on mhhauto.com to be able to post
  8. Same thread mentioned in #1 above, post the TechStream Software ID that comes up when you open TechStream (again in the VM) to the mhhauto.com forum thread. Half a day or so, a nameless post responds with a software “key”
  9. Start TechStream, and put said key into the blank field in TechStream. Voila – it worked! I was shocked quite frankly. I saved the Software ID and Key in a text file I’ve kept on the VM’s desktop.
Hardware / ODBII to PC connection
  1. I had previously purchased a “Super J2534” vehicle to USB cable as part of my Volvo VIDA project. Reading a lot of the posts on this forum, it seems a ton of problems arise from cheapie / knockoff of knockoff hardware. So, was happy I’d spent probably more than I needed to have a pseudo-reputable vehicle to USB cable. You can find it here: https://d5t5.com/eshop/detail/180/super-j2534-volvo-dice-9513000-replacement
  2. This ships from Czech Republic and was remarkably fast shipping – like 5 days or so when I selected the next up from cheapest shipping option (recall $30 or so). I was impressed.
  3. You MUST download & install the driver for the cable. It is on the same page as the cable above (the d5t5.com site). Make sure to install this INSIDE the VM. I installed the driver on both the VM and the actual machine just for belt & suspenders to make sure the PC 'saw' the USB device. This was the only software that “crosses” over between the actual PC machine and the Virtual Machine
TWO important details regarding getting the Vehicle to USB cable working.
  • In the VM, you must make sure its ‘showing up’. In VMware 17 player, do this by the following menu tree
    • Player -> Removable Devices -> Drew Technologies Inc. -> Connect (disconnect from host)
    • It will give you a notification box that its going to disconnect & reconnect. Click “OK”
  • In TechStream – this menu tree to select the right Vehicle to USB cable
    • Setup -> VIM Select. It will open a box
    • Top pull down labeled “Interface Set” – select “MongoosePro JLR”
After all that - it WORKS! Celebrated by customizing my keyfob unlock to roll down all the windows and open the sunroof with a long press of the unlock button.

Again, given some of these places / forums – be really careful in terms of internet security. That said, nothing overtly sinister popped up or occurred (yet). But – proceed at your own risk.

Lastly – TechStream runs somewhat slow, be patient. Old laptop, with a Virtual Machine, with a probably bloated piece of software – it is understandable.

If you head down this path, good luck. Let us know how it works. Hope this helps a few other people.

If it is any help to anyone - the above system worked for both my 2021 LC200 HE, as well as with a newly acquired 2015 Tacoma (Gen2 - model code GRN245L-PRADKA). Moral of the story is that this V18 of TechStream appears to be backwards compatible. Happy to have solved this for two of our Toyotas!

Cheers - VailOG
 
Hello all,
I'm on Apple sillicon. I downloaded the proper UTM from page 1, but my cable is not recognized by XHorse firmware update tool.
View attachment 3789992
I am able to see the USB connection on the VM top right options, but cannot find it in the USB Manager menu. Any idea why?
View attachment 3789993
Fixed it yesterday. Just deleted the VM on UTM and created a new one. This time, the cable was properly recognized.
 
This is getting on my ****ing nerves.

All day to only arrive this this point: I've downloaded VM and TS from page 1 on to my W10 laptop. When I hit start in the VM to open TS, I get the following error message on the right:

Screenshot 2024-12-12 165309.jpg


I've turned off audio settings in VM as I've seen mentioned here, but still haven't figured out the trick.

I've found this error mentioned a few times in the thread but haven't really seen an answer. I hate to just post up a blunt "what's the problem?" but I don't have the capacity to go through 70 pages of this beyond searches. So, anyone know what's my problem?

I also tried downloading an older (v6) version of VM, but that won't even import TS at all without an error.

I have this cable: https://www.amazon.com/dp/B07ZCC8QG9?ref=ppx_yo2ov_dt_b_fed_asin_title which came with a disc. I have no clue what the disc is for.
 

Users who are viewing this thread

Back
Top Bottom