Can anyone help me out with Techstream activation
Version 16.20.023
software id : F0FF69B17632BF6A52DB7BC19DD93606
Thanks in advance
Version 16.20.023
software id : F0FF69B17632BF6A52DB7BC19DD93606
Thanks in advance
Offical TechStream software thread( settings and such)
Offical TechStream software thread( settings and such)UPDATED 1-31-2015
I updated my OP today 1/31/15
I have TechStream installed on 2 Pc's windows 8 or 7 non pro 64 bit. Im using cable MINI-VCI J2534 (Bought this when I originally posted this thread/Post in 06-26-2012
here is the work around link for windows 7/8 64 bit I did not update the firmware on the cable. I would leave yours alone.
http://www.ft86club.com/forums/showthread.php?p=1920724
Follow the Directions to a T and it works! big thanks to mendonsy and Robert_W and others.
Software Download link for TechStream version toyota-techstream-v9.30.002
https://www.dropbox.com/s/gl6r90tvw8uuee7/toyota-techstream-v9.30.002.zip?dl=0
Here are the 64 Bit drivers
https://www.dropbox.com/s/029qetxp67kg70z/Toyota Techstream V9.30.002.exe?dl=0
I did not intall or click on the Video guide(for 64bit)
Your antivirus software might come on and detect a trugan horse. I disabled it before I began. No problems that I can see by doing this. Do so at your own risk. :nerd:
this seller has the cable and software
http://www.chinaobd2.com/
thanks
SP
---------------------------------------------------------------------------------------------------------------------------
edited: I have not tested these driver and "current" drivers and software but here they are as of 6-24-2017
I updated my OP today 1/31/15
I have TechStream installed on 2 Pc's windows 8 or 7 non pro 64 bit. Im using cable MINI-VCI J2534 (Bought this when I originally posted this thread/Post in 06-26-2012
here is the work around link for windows 7/8 64 bit I did not update the firmware on the cable. I would leave yours alone.
http://www.ft86club.com/forums/showthread.php?p=1920724
Follow the Directions to a T and it works! big thanks to mendonsy and Robert_W and others.
Software Download link for TechStream version toyota-techstream-v9.30.002
https://www.dropbox.com/s/gl6r90tvw8uuee7/toyota-techstream-v9.30.002.zip?dl=0
Here are the 64 Bit drivers
https://www.dropbox.com/s/029qetxp67kg70z/Toyota Techstream V9.30.002.exe?dl=0
I did not intall or click on the Video guide(for 64bit)
Your antivirus software might come on and detect a trugan horse. I disabled it before I began. No problems that I can see by doing this. Do so at your own risk. :nerd:
this seller has the cable and software
http://www.chinaobd2.com/
thanks
SP
---------------------------------------------------------------------------------------------------------------------------
edited: I have not tested these driver and "current" drivers and software but here they are as of 6-24-2017
tdi200 said:Hello i bought techstream software and seller from ebay sent me a link to download the latest software and i wish to share it V12.00.125
https://mega.nz/#!twRCVRaK!BqNvjIf2QCUygoAgxI1t2xNyhhlCqlc9YHUYW03qzOU
32bit
https://mega.nz/#!9hgSkITS!be1K9yKCHZEAaFajishFYa5oLQUmWvgsbJSA8MVMFfA
winRAR32bit https://mega.nz/#!Vs4A3ZDQ!0UGD2ez8dTQIBxpNKIEB4r7SPkZBYNToexvT4kEcmkc
winRAR64bit https://mega.nz/#!0tJgxDxK!2cosP4qSv9ShHkIBWWDhFiIl8jU2Wv8ltZIG2ZuKh8c
unzip it by winrar or other program , you will get a floder with all files , Just follow the instruction step by step .
2641 - 2660 of 2670 Posts
I am debating whether I should get this or spend 10x more for the Xtool D8....mine is MY22 Highlander xleVirtual-Chris
64.72US $ 10% OFF|Real Firmware V2.0.4 Mini Vci Newest V16.00.017 Mini-vci Ftdi Ft232rl Multi-language For Toyota Tis Techstream Code Reader - Diagnostic Tools - AliExpress
Smarter Shopping, Better Living! Aliexpress.comwww.aliexpress.com
New guy here. struggling with the infinite mystery of techstream, the agonies & Ecstasies!
I appreciate this thread, it's the closest we get to tech support.
Two observations (perhaps already covered, I'm not yet done plowing through all the biblical passages)
1. As versions of techstream progress, each covering more and more models, with more & more features, the code in the program gets more complex, therefore perhaps more tempermental. I'm concerned with my 2011 Highlander and a friend's 2006 Camry, so maybe I should be looking for version 8 or so, instead of the 13 or 14 I'm wrestling with.
2. Toyota seems to be using the same address https://techinfo.toyota.com/techInf...chinfo/html/prelogin/tsrss/ts_known_bugs.html
for the "known bugs" in each latest version. Using this address on the internet archive Internet Archive: Digital Library of Free & Borrowable Books, Movies, Music & Wayback Machine
I think the "known bugs" can be downloaded for each older version.
There are some surprising glitches, this from the bulletin for ver 6.10.041
11. Vibration or Movement Causes Comm Errors
I appreciate this thread, it's the closest we get to tech support.
Two observations (perhaps already covered, I'm not yet done plowing through all the biblical passages)
1. As versions of techstream progress, each covering more and more models, with more & more features, the code in the program gets more complex, therefore perhaps more tempermental. I'm concerned with my 2011 Highlander and a friend's 2006 Camry, so maybe I should be looking for version 8 or so, instead of the 13 or 14 I'm wrestling with.
2. Toyota seems to be using the same address https://techinfo.toyota.com/techInf...chinfo/html/prelogin/tsrss/ts_known_bugs.html
for the "known bugs" in each latest version. Using this address on the internet archive Internet Archive: Digital Library of Free & Borrowable Books, Movies, Music & Wayback Machine
I think the "known bugs" can be downloaded for each older version.
There are some surprising glitches, this from the bulletin for ver 6.10.041
11. Vibration or Movement Causes Comm Errors
- Vehicle(s): All
- Device(s): Techstream (when using the VIM via USB - no backpack) and Techstream Lite (Mongoose VIM)
- Description: Certain laptops with HDD vibration protection software experience intermittent communication loss when the laptop is jerked or moved, which forces the user to restart Techstream.
- Status: Issue is under investigation.
- Work Around: Though each PC is different, at your own risk, the HDD vibration protection software may be adjusted to be less sensitive, which may increase the risk of HDD damage during abrupt movement or if the PC is dropped.
Can anyone help me out with Techstream activation
Version 15.00.028
software id : EA94A7D87E4D2BFC925395D839E5BE05
Thanks in advance
Version 15.00.028
software id : EA94A7D87E4D2BFC925395D839E5BE05
Thanks in advance
Hi....Does anyone know if the win 10 64bit driver for this will work on win 11 or if there is a win 11 driver...thanks
Mini VCI J2534
Mini VCI J2534
It will also work for Windows 11.Hi....Does anyone know if the win 10 64bit driver for this will work on win 11 or if there is a win 11 driver...thanks
Mini VCI J2534
hello, can you send the registration key?
Software Version 17.20.013
ID: E133A181499DBFF1236B7724CE955E00
I'll be very thankful!
Software Version 17.20.013
ID: E133A181499DBFF1236B7724CE955E00
I'll be very thankful!
Is it possible to make new keys with techstream?
I only have the valet key...
I only have the valet key...
Hi all. Just looking to share my experience and ask for some additional advice.
Much thanks to @tdi200 for clarifying some things here and uploading as it has streamlined my install process a bit.
I have a 2007 Camry and I have setup the following on my Windows 10 x64 machine:
I was able to pass through the cable USB port to an XP virtual machine to run the FirmwareUpdateTool and confirm my cable is Firmware 1.4.1. My cable is properly shown under my Device Management as a USB Serial/COM port and a USB Serial Converter both using the FTDI drivers.
With this configuration I have tested on multiple versions of Techstream from v10 to v17. While I haven't tried to do every single option on both it would appear that all of these versions work just fine for me to be able to do Health Checks on the ECUs in my vehicle.
For the most part, it appears my cable and software all work properly, but I do have a few questions:
1) It seems that in order to connect to the ECUs my ignition has to be ON (not engine start, just ON position). Is this normal behavior?
2) On my 2007 Camry I cannot contact the ECUs named "Theft Deterrent" and "Accessory Gateway." I definitely have an alarm installed in the vehicle, but perhaps there is no ECU for these? All of the other ECUs can be communicated with no problem. Is this normal? Is it likely that I don't have these 2 ECUs? I will also note that my vehicle is properly detected when starting TS (correct model, etc.).
My last question/comment/observation has to do with all the talk of patches and getting serial #s for Techstream. I'm not sure if it was discussed on this thread, but there is the ability to simply add another shortcut for TS to the following:
"C:\Program Files (x86)\Toyota Diagnostics\Techstream\bin\Techstream.exe" /395070/VM:1
Adding those 2 parameters on the end allows to bypass the main validation check and connect right to the vehicle. This appears to work for me for every version I tested, and I'm not sure why it isn't the preferred method instead of people having to ask about keys for different versions or worry about hacks which may or may not be virus infested.
For the record many of the files I have found here and elsewhere have tested positive in multiple AV scanners and thus I refuse to use them. I use a sandboxed system to confirm. However on a modern Windows 10x64 install the only file I needed was the TS install (never seen one with a virus) and the VCI driver from @tdi200 mentioned above (also virus free unlike so many of the others out there). Using the shortcut hack listed above allows me to launch directly without validation (after registering and configuring VIM by launching the main shortcut once).
I appreciate any answers and hope my experience here helps someone else out!
Much thanks to @tdi200 for clarifying some things here and uploading as it has streamlined my install process a bit.
I have a 2007 Camry and I have setup the following on my Windows 10 x64 machine:
- Techstream v17 (more on this in a moment)
- The "setup for MVCI-64bit Cable Driver.exe" that @tdi200 uploaded previously.
I was able to pass through the cable USB port to an XP virtual machine to run the FirmwareUpdateTool and confirm my cable is Firmware 1.4.1. My cable is properly shown under my Device Management as a USB Serial/COM port and a USB Serial Converter both using the FTDI drivers.
With this configuration I have tested on multiple versions of Techstream from v10 to v17. While I haven't tried to do every single option on both it would appear that all of these versions work just fine for me to be able to do Health Checks on the ECUs in my vehicle.
For the most part, it appears my cable and software all work properly, but I do have a few questions:
1) It seems that in order to connect to the ECUs my ignition has to be ON (not engine start, just ON position). Is this normal behavior?
2) On my 2007 Camry I cannot contact the ECUs named "Theft Deterrent" and "Accessory Gateway." I definitely have an alarm installed in the vehicle, but perhaps there is no ECU for these? All of the other ECUs can be communicated with no problem. Is this normal? Is it likely that I don't have these 2 ECUs? I will also note that my vehicle is properly detected when starting TS (correct model, etc.).
My last question/comment/observation has to do with all the talk of patches and getting serial #s for Techstream. I'm not sure if it was discussed on this thread, but there is the ability to simply add another shortcut for TS to the following:
"C:\Program Files (x86)\Toyota Diagnostics\Techstream\bin\Techstream.exe" /395070/VM:1
Adding those 2 parameters on the end allows to bypass the main validation check and connect right to the vehicle. This appears to work for me for every version I tested, and I'm not sure why it isn't the preferred method instead of people having to ask about keys for different versions or worry about hacks which may or may not be virus infested.
For the record many of the files I have found here and elsewhere have tested positive in multiple AV scanners and thus I refuse to use them. I use a sandboxed system to confirm. However on a modern Windows 10x64 install the only file I needed was the TS install (never seen one with a virus) and the VCI driver from @tdi200 mentioned above (also virus free unlike so many of the others out there). Using the shortcut hack listed above allows me to launch directly without validation (after registering and configuring VIM by launching the main shortcut once).
I appreciate any answers and hope my experience here helps someone else out!
Yes (most likely). You need to reset the immobilizer ECU and program all new keys:Is it possible to make new keys with techstream?
I only have the valet key...
You need to get a PIN based off your VIN. I'm not sure if there is anyway to get this for free, but you should be able to get the code for no more than $10 from online.
IIRC, you can only reset the ECU a certain number of times before it needs to be removed and professionally rebuilt/reset.
Anyone help with a registration?
ID: 1B91BCEF6ABA11193C12D51B2D70C204
Version: 17.00.020
ID: 1B91BCEF6ABA11193C12D51B2D70C204
Version: 17.00.020
1= yes that is normal all my toyotas doing thatHi all. Just looking to share my experience and ask for some additional advice.
Much thanks to @tdi200 for clarifying some things here and uploading as it has streamlined my install process a bit.
I have a 2007 Camry and I have setup the following on my Windows 10 x64 machine:
- Techstream v17 (more on this in a moment)
- The "setup for MVCI-64bit Cable Driver.exe" that @tdi200 uploaded previously.
I was able to pass through the cable USB port to an XP virtual machine to run the FirmwareUpdateTool and confirm my cable is Firmware 1.4.1. My cable is properly shown under my Device Management as a USB Serial/COM port and a USB Serial Converter both using the FTDI drivers.
With this configuration I have tested on multiple versions of Techstream from v10 to v17. While I haven't tried to do every single option on both it would appear that all of these versions work just fine for me to be able to do Health Checks on the ECUs in my vehicle.
For the most part, it appears my cable and software all work properly, but I do have a few questions:
1) It seems that in order to connect to the ECUs my ignition has to be ON (not engine start, just ON position). Is this normal behavior?
2) On my 2007 Camry I cannot contact the ECUs named "Theft Deterrent" and "Accessory Gateway." I definitely have an alarm installed in the vehicle, but perhaps there is no ECU for these? All of the other ECUs can be communicated with no problem. Is this normal? Is it likely that I don't have these 2 ECUs? I will also note that my vehicle is properly detected when starting TS (correct model, etc.).
My last question/comment/observation has to do with all the talk of patches and getting serial #s for Techstream. I'm not sure if it was discussed on this thread, but there is the ability to simply add another shortcut for TS to the following:
"C:\Program Files (x86)\Toyota Diagnostics\Techstream\bin\Techstream.exe" /395070/VM:1
Adding those 2 parameters on the end allows to bypass the main validation check and connect right to the vehicle. This appears to work for me for every version I tested, and I'm not sure why it isn't the preferred method instead of people having to ask about keys for different versions or worry about hacks which may or may not be virus infested.
For the record many of the files I have found here and elsewhere have tested positive in multiple AV scanners and thus I refuse to use them. I use a sandboxed system to confirm. However on a modern Windows 10x64 install the only file I needed was the TS install (never seen one with a virus) and the VCI driver from @tdi200 mentioned above (also virus free unlike so many of the others out there). Using the shortcut hack listed above allows me to launch directly without validation (after registering and configuring VIM by launching the main shortcut once).
I appreciate any answers and hope my experience here helps someone else out!
2= could be your installed alarm was a dealer addon option specially you said when u connect techstream the program detects your car i doubt there is going to be two ecu in the car
3=
"C:\Program Files (x86)\Toyota Diagnostics\Techstream\bin\Techstream.exe" /395070/VM:1 <<<<<<<<this is good news and excellent contribution i didnt know this thing works out on all version like that we should suggest everyone to do that instead of asking for key all one needs to do is after installing techstream of your choice, open techstream from original shortcut configure everything exit out and than
go to C:\Program Files (x86)\Toyota Diagnostics\Techstream\bin\Techstream.exe right click and send to desktop as shortcut and than going to the desktop right click the shortcut that you just created than go to property and under target after exe" leave one space and paste this /395070/VM:1
and yes i agree the vci drivers that i had uploaded are 100% clean we also have a key generator that was dedicated to the forum it works great too the developer confirmed that the virus detected is a false positive
go to C:\Program Files (x86)\Toyota Diagnostics\Techstream\bin\Techstream.exe right click and send to desktop as shortcut and than going to the desktop right click the shortcut that you just created than go to property and you will see "target" after exe" leave one space and paste this /395070/VM:1Anyone help with a registration?
ID: 1B91BCEF6ABA11193C12D51B2D70C204
Version: 17.00.020
Hey guys, I've been scouring the internet regarding Techstream technical info regarding cable needed etc. I came across this forum which seems to be the most conclusive. I've managed to get version 17 of the software. I've read about adding the shortcut to the end of the .exe to get it to run w/o being activated. I'm in the process of purchasing the cable. Can someone tell me the "cheapest" source for the cable that will allow me full use for all functions. I've been seeing the Mini VCI J2534 cables on both Amazon and Ebay, however I'm seeing a lot of hit or miss issues with firmware version 1.4.7 and 2.0.4, they are saying that the older firmware cable is unstable and the newer is best, but the 2.0.4 cable is like over 100 bucks!!! Then I'm seeing this VXDIAG VCX cable that apparently is better than the Mini VCI cable.
BTW, this is for my 2011 Avalon, I need to replace the TPMS sensors (bad batteries) and register all 5 (one in spair) TPMS with the vehicle.
BTW, this is for my 2011 Avalon, I need to replace the TPMS sensors (bad batteries) and register all 5 (one in spair) TPMS with the vehicle.
steppinthrax: I have a 2011 Camry and using Techstream v.11.20.019 on an old Dell D610 XP SP3 computer with a cable that has 1.4.1 firmware. User Type is "US Dealer" although "Corporate" seems most recommended. Most of the time I get access to everything. The cable check says I don't have the K or L line access but I don't know in what way that limits me. I haven't heard of or found a cable that connects without fail every time. Glitches are standard. I did buy those cables when they were half the price they are now; they've all gone up. I also have the same version Techstream on a Dell laptop running Windows 10 Pro 64 bit and have access to everything most of the time. I've loaded Techstream v.17 on XP just to see if it makes any difference but so far I can't connect. Maybe it needs the 2.0.4 firmware. Anyway, you could try the 1.4.1 cable and it will likely work. If not, try v. 11.20.019 which covers vehicles to 2016 or thereabouts. Good luck.
Update - Got TS 17 to connect on the old XP but have "Reduced Functionality" so no Active Test, Customization, Health Check or Utility. May try the 2.0.4 cable.
Update2 - Got TS 17 to connect on Windows 10 x64 with the same cable with firmware 1.4.1. Now, it did not connect when I chose the generic Xhorse driver so I installed Autokent's application that gives you a selection of drivers, The first one I tried, 2.0.1 worked so I left it there. Although the "Reduced Functionality" message popped, all tabs were available and working. Like a box of chocolates....
Update - Got TS 17 to connect on the old XP but have "Reduced Functionality" so no Active Test, Customization, Health Check or Utility. May try the 2.0.4 cable.
Update2 - Got TS 17 to connect on Windows 10 x64 with the same cable with firmware 1.4.1. Now, it did not connect when I chose the generic Xhorse driver so I installed Autokent's application that gives you a selection of drivers, The first one I tried, 2.0.1 worked so I left it there. Although the "Reduced Functionality" message popped, all tabs were available and working. Like a box of chocolates....
Thanks for posting that. A good video, but does seem a bit fishy how he glances over the pin/token section.Yes (most likely). You need to reset the immobilizer ECU and program all new keys:
You need to get a PIN based off your VIN. I'm not sure if there is anyway to get this for free, but you should be able to get the code for no more than $10 from online.
IIRC, you can only reset the ECU a certain number of times before it needs to be removed and professionally rebuilt/reset.
Has anyone used one of these code/token generator sites?
Also, what is the common use for Techstream in general? My truck being a 2008, I don't see a whole lot more functionality from Techstream than a generic code scanner. A bit more info, yes, and options for 'customizing' length of time before cabin lights go off, but that's about it.
Any idea why resetting the memory on my transmission controller doesn't work?
Are you still using the vcx nano device? Is it more reliable than the mini vci? I saw one for $67 and thinking about it.If you have a VCX device, this may be of interest to you. I installed TS 15.0.026 and got the passcodes with the displayed ID. I then installed the XHorse MiniVCI drivers. Everything good. This is on Windows 10 x32 OS and a 64bit CPU.
Then I installed VX Manager for my VCX-NANO device. I checked both Toyota and Passthrough options. When I opened VX Manager the two installed drivers where listed but required activation. I 1st activated the Toyota option. When I reopened TS, my ID had changed and I needed a new code. Bummer.........
So I decided to activate the Passthrough option also to see if that would change it again. If so I wouldn't have to go back for another code. It did change it again, but it changed it back the the original code and the previously obtained codes work fine.
I have not car tested yet, but both options are available for selection along with the original so I am assuming all is good. I'll update if not.
Thanks.
привет нужен ключ благодарю вас за ранние 8E59B7456EFAFD03F451794F5E709D03
привет нужен ключ благодарю вас за ранние 8E59B7456EFAFD03F451794F5E709D03
[/ЦИТИРОВАТЬ]
V17.20.013
2641 - 2660 of 2670 Posts
Toyota Tundra Discussion Forum
TundraTalk.net forum offers the most comprehensive collection of Toyota Tundra information. Find discussions on the Toyota Tundra Diesel, TRD Pro, SR5, lift kits, towing capacity, classifieds, and more!
Full Forum Listing
