Same here - I’ve used it many times before, on the same Mac running VirtualBox VM - not network connected, no updates made.
Did a quick search and found a new key. Everything worked after that.
Last edited:
How-To: TechStream In 5 Minutes (24 Viewers)
- Thread starter getco
- Start date
This site may earn a commission from merchant affiliate
links, including eBay, Amazon, Skimlinks, and others.
Did a quick search and found a new key. Everything worked after that.
sleepycruiser
I will get by….I will survive -Touch of Grey LC200
Might be a dumb question....I've gotten Techstream to work on a Mac before...but it has been a few years and I don't remember the process. Do I need a Windows disc? I've tried running VirtualBox but it seems like it is asking me for a disk. I am almost positive I never had a disc the other time I set it up.
My cable gets here today from amazon, I'm trying to get rid of the Parking Brake warning on my Rav4 2019. Would I be able to do this with Techstream V12 from the first post?
theferg
SILVER Star
Is Techstream just a buggy, POS application that is constantly crashing for everybody else?
I've used it for a good few years now, across 3-4 different laptops, and across several different Toyota and Lexus vehicles, and now on a 4th laptop but using the VM image this time. But I've experienced constant crashes of the application across every single setup I've used over the last ~8 years. Sometimes I can get in fine and work thru tests and poke around and not really have any issues. But most times, after I've checked one system and start poking into another system, or poking further into any programmable areas, it seems to always crash. Restarting everything will usually get me back in, but seems to always still end up giving me issues.
I had just been chalking it up to it being cracked software and rigged up on older laptops... and the older laptops being somewhat POSes. But with the VM setup (and a MUCH newer and nice laptop), I was hoping I would have a better experience. But its not looking that way so far.... plenty of crashing out when i'm running tests etc.
Or maybe its my cable? I've treated the cable pretty well. Stored it nicely in a drawer. But I guess it could be "worn out" from being old. Though like I said, I've seemed to always have this experience,even when the cable was new. The cable I have was the "recommended" one (back in 2016).....
Thoughts? Recommendations? Ideas?
I've used it for a good few years now, across 3-4 different laptops, and across several different Toyota and Lexus vehicles, and now on a 4th laptop but using the VM image this time. But I've experienced constant crashes of the application across every single setup I've used over the last ~8 years. Sometimes I can get in fine and work thru tests and poke around and not really have any issues. But most times, after I've checked one system and start poking into another system, or poking further into any programmable areas, it seems to always crash. Restarting everything will usually get me back in, but seems to always still end up giving me issues.
I had just been chalking it up to it being cracked software and rigged up on older laptops... and the older laptops being somewhat POSes. But with the VM setup (and a MUCH newer and nice laptop), I was hoping I would have a better experience. But its not looking that way so far.... plenty of crashing out when i'm running tests etc.
Or maybe its my cable? I've treated the cable pretty well. Stored it nicely in a drawer. But I guess it could be "worn out" from being old. Though like I said, I've seemed to always have this experience,even when the cable was new. The cable I have was the "recommended" one (back in 2016).....
Thoughts? Recommendations? Ideas?
Last edited:
Open virtual box. There should be already a window xp machine image on the left hand pane. Launch that and xp should start to boot up in another window. I have better luck pluging in the usb after xp has fully loaded. Let xp acknowledge the usb being plugged in. Launch techstream from the desktop.
I experienced the same thing using multiple windows based laptops of varying age. I now use an old MacBook Air from 2013 w and have never had an issue. Start to finish the VB boot up process is under 5 min. If you have a ios device with a usb give it a try. I doubt its your usb cable. They are all the exact same chinesium clone.
sleepycruiser
I will get by….I will survive -Touch of Grey LC200
I haven't looked at the procedure for installing VirtualBox, so this is just a guess: there is (at least used to be) an extension pack that (historically) never shipped with the VirtualBox software, but had to be downloaded/installed separately, to enable additional functionality. I just took a look at the virtualbox dot org site, it's called Guest Additions or Extension Pack, and it is version specific (i.e. you must download the version corresponding to your specific version of VB).
If the issue is that the virtualized Windows system isn't seeing the (USB) adapter, then you may need to first allow control of the device to be handed over to the running virtual Windows system. This can be done from the VirtualBox window (once the virtual Windows system is running)—it's one of the menu options, although I don't remember which one (I haven't used it in years...). It will show all connected USB devices as separate menu items and allow you to hand over control for each one individually.
Probably worth pointing out: once properly set up, the virtual system should be fully capable of seeing the connected device, the same way it would if it were not virtualized. In other words, if you're having trouble getting this procedure to work, and your host system can see the device, then it's probably just a configuration issue (i.e. fixable with the right settings).
I may end up going through this procedure myself in the near future, in which case I'll try and remember to come back and reply to any questions.
I finally tried to get it working on a Win10 laptop, however I am getting this error every time I try to open TS.
I noticed that this question was asked before but never answered and after 18 pages I stopped reading.
What is the solution to this?
I noticed that this question was asked before but never answered and after 18 pages I stopped reading.
What is the solution to this?
Got TIS running, haven't connected to the car yet but will try tomorrow.
I had to go back a few pages where it was mentioned to enable visualization in the BIOS.
I had to go back a few pages where it was mentioned to enable visualization in the BIOS.
Update: it is connecting and working.
Only thing is I can't get access to the engine ECU.
Only thing is I can't get access to the engine ECU.
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.
- These are out of stock everywhere, or priced crazyily, so I'm selling them to mud members for $39, ships free - Order Cable - https://buyminivci.com (Can also PM me to order via paypal/venmo)
Step 2: Download VirtualBox for Your Operating System:
- Windows: https://download.virtualbox.org/virtualbox/6.1.18/VirtualBox-6.1.18-142142-Win.exe
- MacOS: https://download.virtualbox.org/virtualbox/6.1.18/VirtualBox-6.1.18-142142-OSX.dmg
Step 3: Install VirtualBox Software You Just Downloaded
- Windows: Double-Click downloaded file
- MacOS: Double-Click downloaded file, run installer
Step 4: Download TechStream Image:
- MEGA (V2! Click to download)
Step 5: Double-Click downloaded file.
Connect & Enjoy.
-g
Edit (4/8/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
Will the mini-vci work with TIS if I spend the $65 for a 2-day professional diagnostic subscription? Or will it know the cable is a clone? I'd like to customize some stuff in my 2020 tundra and 2022 GR 86.
tried to download on my MacBook, have virtual box but won't let me open it, says my OS is too old (i just updated to 13.1.2) and it says that in my apps where you download updates etc. but when i click apple and about my computer it says its still 10.13.6 and needs to be at least 10.15.1
i have restarted computer and everything no idea whats going on
i have restarted computer and everything no idea whats going on
I don't know specific one but you will likely need to install one of the older VB 6.x builds
www.virtualbox.org
Download_Old_Builds_6_1 – Oracle VirtualBox
So I used my wife’s MacBook Air and was able to proceed with downloading everything
I opened up Techstream and selected “connect to vehicle” it says it’s unable to do so (I have attached picture of the issue)
The MacBook Air doesn’t come with a USB, just a micro USB so I have an adapter to accept the USB
I believe I have saw others using MacBook Air and had no issues? Is this correct?
I opened up Techstream and selected “connect to vehicle” it says it’s unable to do so (I have attached picture of the issue)
The MacBook Air doesn’t come with a USB, just a micro USB so I have an adapter to accept the USB
I believe I have saw others using MacBook Air and had no issues? Is this correct?
Has anyone gotten this to work on an M1 Mac?
I'm pulling out what little hair I have trying to get Techstream to launch. I keep getting stuck at "Unable to Connect to VIM". (Screenshot below)
UTM & VM install fine. I can connect to the USB. I can get Xhorese to recognize the cable but I just can't get techstream to start.
Absolutely nothing works.
I'm sure I'm missing something simple. Any help or advice would be much appreciated.
I'm pulling out what little hair I have trying to get Techstream to launch. I keep getting stuck at "Unable to Connect to VIM". (Screenshot below)
UTM & VM install fine. I can connect to the USB. I can get Xhorese to recognize the cable but I just can't get techstream to start.
Absolutely nothing works.
- I'm on a 2021 M1 Macbook Pro.
- Using UTM Techstream v17.20.utm uploaded by @getco a couple of days ago
- I also bought the cable from @getco
I'm sure I'm missing something simple. Any help or advice would be much appreciated.
Bump
Similar boat but I snagged whatever the most non-crappily-reviewed Amazon cable I could get for 20ish bucks. I see an error log icon pop up in the windows task bar for a minute but haven't spent any time looking into it really. Briefly saw something about mileageunit.dll but I'm a newb with techstream. For what it's worth, I fired up the provided virtualbox image on an intel macbook pro with the same cable, and techstream actually opens up but I haven't investigated beyond that yet. There's a virtualbox beta for M1 macs, but the VMs crash attempting to launch any application so that's a no-go at the moment. Wish I had something helpful, but at least you're not alone.
Quick update - started from scratch with a new UTM VM. Snagged the recommended XP iso (hash verified) and techstream from obdii365. No clue if this is clean or not, but it was just for poops n' giggles. After the initial installation, I was having similar issues as before with UTM/M1 MBP. Installed the provided Mini Vci driver x86, and TS17 launched and appears to be working. Haven't hooked it up to the vehicle yet, but at least the application is launching. Too many variables across systems and whatnot, but it couldn't hurt trying to install a different driver or start fresh if you continue having issues with your M1 mac. I'll update if it appears to connect to the vehicle later today.
