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

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

Anyone figured out how to get this to work on a mac running Big Sur? I keep getting a kernel error and I've tried everything that Google says to no avail
 
I’m having an epic failure of a time trying to get this to work. I have followed the steps in the original post exactly. TS won’t boot up in the VB and gives me an error code immediately. I tried on my old MacBook Pro. Then booted up my Dell laptop. Did the exact steps and still nothing. It looks to almost boot up but then gives me this error. Can anyone help me and explain what I’m doing wrong or how to get this to work? Thank you!

View attachment 2814888

View attachment 2814889

"If your 0x80004005 error in VirtualBox includes VT-x and/or AMD-v terms within the error description, this solution will help you fixing your version of VirtualBox.

In order to work, every virtual machine software needs CPU virtualization feature. Enter your BIOS settings (keep pressing DEL key after turning on your PC) and seek for this feature among settings.

For INTEL based systems, virtualization feature is called VT-x, while AMD uses term AMD-v."


Anyone figured out how to get this to work on a mac running Big Sur? I keep getting a kernel error and I've tried everything that Google says to no avail

Yeah, I've got it running on a '14 MacBook Air that's on Big Sur. Post a pic of the kernel error.
 
"If your 0x80004005 error in VirtualBox includes VT-x and/or AMD-v terms within the error description, this solution will help you fixing your version of VirtualBox.

In order to work, every virtual machine software needs CPU virtualization feature. Enter your BIOS settings (keep pressing DEL key after turning on your PC) and seek for this feature among settings.

For INTEL based systems, virtualization feature is called VT-x, while AMD uses term AMD-v."




Yeah, I've got it running on a '14 MacBook Air that's on Big Sur. Post a pic of the kernel error.

It's this

1634932137235418960847564079931.jpg




When I check some things listed online I get some errors that "incompatible architecture" binary is for x86_64 but needed arch arm64e
 
Last edited:
It's this

View attachment 2818632



When I check some things listed online I get some errors that "incompatible architecture" binary is for x86_64 but needed arch arm64e

I had the same issue when I updated to Big Sur. Have you tried my troubleshooting in post #744? Specifically starting with a reboot?
 
I had the same issue when I updated to Big Sur. Have you tried my troubleshooting in post #744? Specifically starting with a reboot?
I've rebooted about 50 times, uninstalled and reinstalled multiple times, disabled kernel consent...nothing works

I started getting this error that the architecture was incompatible, and read a post that Virtual Box wont work if you have the M1 chip...and virtualbox's user manual says "intel hardware is required"
 
I don’t have a Mac with M1 but Parallels does run on that chip and IIRC it can import VirtualBox VMs…. Not free of course but perhaps an option to try

 
"If your 0x80004005 error in VirtualBox includes VT-x and/or AMD-v terms within the error description, this solution will help you fixing your version of VirtualBox.

In order to work, every virtual machine software needs CPU virtualization feature. Enter your BIOS settings (keep pressing DEL key after turning on your PC) and seek for this feature among settings.

For INTEL based systems, virtualization feature is called VT-x, while AMD uses term AMD-v."




Yeah, I've got it running on a '14 MacBook Air that's on Big Sur. Post a pic of the kernel error.
Thank you for the help, unfortunately it looks like my laptop does not support VT. I cannot find it in bios. Should I try something else in the article?

Also in VB settings, it gives me errors for VT since I assume my system does not support it. It will not let me apply the settings when I choose to deselect VT
AFA04201-4CB9-43B0-B21C-584C41828A7A.jpeg
 
Last edited:
5 minutes......until you get to dealer code and registration key number crap. Exactly why I have been avoiding techstream. I knew if wouldn't be a five minute delight.
 
5 minutes......until you get to dealer code and registration key number crap. Exactly why I have been avoiding techstream. I knew if wouldn't be a five minute delight.

I have the same registration window come up when attempting to use TS and VB on an old Macbook Pro.

I have been using TS on an old PC and it works-- but very very slow.

For the heck of it, I loaded VB and TS on an old 2009 MacBook Pro. Unlike on my PC which did not require a Keycode to use, TS would not connect to my truck because a registration window came up requiring a keycode.

Is there a way to get around the registration window when using a Mac?
 
An alternative for some people here. I bought this exact cable off Amazon: Amazon product ASIN B097YC5LSR
Pairing this cable with the TechStream download in the original post here (VBox on Windows 10 64Bit, mega) worked perfectly, I had no issue whatsoever. Sometimes the cable could be bad... Did AHC check procedure two days ago, no issues.
 
An alternative for some people here. I bought this exact cable off Amazon: Amazon product ASIN B097YC5LSR
Pairing this cable with the TechStream download in the original post here (VBox on Windows 10 64Bit, mega) worked perfectly, I had no issue whatsoever. Sometimes the cable could be bad... Did AHC check procedure two days ago, no issues.

Sorry, it doesn't look like the link posted. Which cable was it?

Or is does anyone else have a cable suggestion for 2004 LX470?
 
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. One option:
- Mini VCI J2534 16Pin OBD2 Diagnostic Cable For Toyota Lexus TIS Tech Car Scanner | eBay - https://www.ebay.com/itm/265057592363 ($20, Ships Free)

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.

:santa:

-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
getco,

Thank you! It probably helps that I am 100% Apple ecosystem and run Windows Instances for proprietary apps in Parallels all the time. I was able to get up and running in ~ 5 mins as advertised. Now off to spending a fair amount $$ on all the deferred maintenance of my new to me LX470.

Regards.
 
getco,

Thank you! It probably helps that I am 100% Apple ecosystem and run Windows Instances for proprietary apps in Parallels all the time. I was able to get up and running in ~ 5 mins as advertised. Now off to spending a fair amount $$ on all the deferred maintenance of my new to me LX470.

Regards.
I'm having trouble with the mega TS image download linked in the original post. The download freezes up around 500mb in, has happened three times in a row now. Did you you the OPs link to DL the image recently? Thx!
 
I have my ABS, VSC and trac lights on due to a faulty front left wheel speed sensor. I replaced it and used the techstream to clear the lights but the lights are still lit when I turn the car on. Also the codes are still visible on techstream. Is there something I am missing here?
 
I've rebooted about 50 times, uninstalled and reinstalled multiple times, disabled kernel consent...nothing works

I started getting this error that the architecture was incompatible, and read a post that Virtual Box wont work if you have the M1 chip...and virtualbox's user manual says "intel hardware is required"
I was getting a kernel error after upgrading OS to Big Sur. Upgrading to the latest version of Virtual Box resolved my kernel issues. My Mac does have in Intel processor.
 
Wanted to document another issue that occurred with Virtual Box on my Mac in case someone else experiences the same issue.

I had not used Virtual Box or Techstream in a few months and my VCI cable, that never had a problem connecting before, was not being recognized.

The fix was to go into the system files on my Mac after uninstalling Virtual Box and delete the all remaining supporting files on the Mac. I then started with a fresh install of Virtual Box and haven’t had any cable connection issues since.
 
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. One option:
- Mini VCI J2534 16Pin OBD2 Diagnostic Cable For Toyota Lexus TIS Tech Car Scanner | eBay - https://www.ebay.com/itm/265057592363 ($20, Ships Free)

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.

:santa:

-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


Thank you very much!
 

Users who are viewing this thread

Back
Top Bottom