Toyota Tundra Discussion Forum banner

2241 - 2260 of 2309 Posts

·
Registered
Joined
·
16 Posts
Got my 1.4.1 cable. Using TS 14.30.023 on Win10, 32bit, NA as region. 2019 Camry. When connected, TS does not automatically report the car info, so I manually selected everything. TS shows the odometer reading. I can select the ECU's and I get data reported back that looks reasonable. But I don't have Health Check or Customize options. Can anyone tell me why the car is not automatically selected, and why I don't have Health or Customize? Thanks for any help.
 

·
Registered
Joined
·
9 Posts
Yea buddy I understand keygen always triggers false positive. As far as 32bit'drivers goes does that'belong to'me I had just combined it in the folder (got'the drivers when I bought the cable). but that 64bit drivers are legit and that's what I been'using. That 64bit driver was developed by one of the member in here. I was lucky to save his file and been using it.

Sent from my LG-H811 using Tapatalk
I have been trying for literally years to make this work under 64bit OS. Techstream seems to run fine but it will not talk to the mini VCI or a VCX-NANO. I have both of them working on W7 32bit. So, I have done every thing needed to get it working on 32bit. Add to that the reg mode for 64bit. I have followed the How To Install on 64bit "bible" to a T dozens of times, but no success. The firmware upgrade tool (FUT) also does not work under 64 bit system.
Every time I get serious about making it work, I read "yes I got it to work" and "NO it does not work". So what is the magic pill?
I am using 14.30.023, but have also tried 8.., 9.., 10.., 12.., 13.., I have tried all the drivers I could come up with, 1.4.1, 1.4.6, 1.4.8, 2.0.1, 2.10, and currently have FTDI 2.12.28, which I don't find anyone mentioning but it is the latest 64bit driver. The registry has both adapters listed in the passthrough section.
What am I doing wrong that you are doing right?
 

·
Registered
Joined
·
243 Posts
I have been trying for literally years to make this work under 64bit OS. Techstream seems to run fine but it will not talk to the mini VCI or a VCX-NANO. I have both of them working on W7 32bit. So, I have done every thing needed to get it working on 32bit. Add to that the reg mode for 64bit. I have followed the How To Install on 64bit "bible" to a T dozens of times, but no success. The firmware upgrade tool (FUT) also does not work under 64 bit system.
Every time I get serious about making it work, I read "yes I got it to work" and "NO it does not work". So what is the magic pill?
I am using 14.30.023, but have also tried 8.., 9.., 10.., 12.., 13.., I have tried all the drivers I could come up with, 1.4.1, 1.4.6, 1.4.8, 2.0.1, 2.10, and currently have FTDI 2.12.28, which I don't find anyone mentioning but it is the latest 64bit driver. The registry has both adapters listed in the passthrough section.
What am I doing wrong that you are doing right?
mvci works great on 64 bit
download this link and run the 64BIT DRIVERS follow instruction provided under the 64 bit drivers AND also check post #2,080 u gotta have the cable plugged in go to device manager and look for the cable that u connected right click and update drivers and navigate to the folder where you just installed the 64 bit drivers from the mega file bellow and u should be up and running: MEGA
 

·
Registered
Joined
·
243 Posts
Got my 1.4.1 cable. Using TS 14.30.023 on Win10, 32bit, NA as region. 2019 Camry. When connected, TS does not automatically report the car info, so I manually selected everything. TS shows the odometer reading. I can select the ECU's and I get data reported back that looks reasonable. But I don't have Health Check or Customize options. Can anyone tell me why the car is not automatically selected, and why I don't have Health or Customize? Thanks for any help.
are u sure that u have setup techsteam as corporate
 

·
Registered
Joined
·
25 Posts
mvci works great on 64 bit
download this link and run the 64BIT DRIVERS follow instruction provided under the 64 bit drivers AND also check post #2,080 u gotta have the cable plugged in go to device manager and look for the cable that u connected right click and update drivers and navigate to the folder where you just installed the 64 bit drivers from the mega file bellow and u should be up and running: MEGA
Above will make sure the drivers are installed, but there's a 2nd part to having techstream actually being able to use the cable. The mega you posted, I have used, and automatically will do this if you run the installer. Some people though are just extracting, which will miss a step. If you read the first post here you can see the registry changes that need to happen

 

·
Registered
Joined
·
243 Posts
Above will make sure the drivers are installed, but there's a 2nd part to having techstream actually being able to use the cable. The mega you posted, I have used, and automatically will do this if you run the installer. Some people though are just extracting, which will miss a step. If you read the first post here you can see the registry changes that need to happen

and also not forgetting selecting the MVCI cable by going to techstream, hit setup than VIM select than make sure X-horse MVCI is selected as interface setup
 

·
Registered
Joined
·
25 Posts
and also not forgetting selecting the MVCI cable by going to techstream, hit setup than VIM select than make sure X-horse MVCI is selected as interface setup
This too. I've been mucking around trying to make a live bootable usb with techstream on it, the drivers alone do not allow techstream to see the cable from the dropdown. Those reg values have to be present in both 32 and 64. Whoever made the 64 installer, did it all correct, and if you just run it, it will do everything for you. If you extract it, and manually change the drivers, it will not work. I've seen a lot of posts on other forums where people were doing that. I can't figure out why everyone was posting that's how to do it... I can only assume because the original 32 exe was flagged for viruses, and it does look like there are real ones in it. Extracting it, and manually doing it, would be a round-about way to not get a virus. Honestly, I would bet the x64 would just work on 32. I don't know who made it, but the only difference is the reg edit, there's no actual install or driver difference.
 

·
Registered
Joined
·
9 Posts
I ran the install 64 EXE. The reg entries did not change. IE, it overwrote the same thing that was already in there. The FUT tool still does the same thing. When I run it, it starts up but does not open a window and is running in the task manager with 25% CPU usage. I have no clue what it is doing.
I have not yet put it on the car, but I have no hope it will do any different since nothing changed.
 

·
Registered
Joined
·
25 Posts
I ran the install 64 EXE. The reg entries did not change. IE, it overwrote the same thing that was already in there. The FUT tool still does the same thing. When I run it, it starts up but does not open a window and is running in the task manager with 25% CPU usage. I have no clue what it is doing.
I have not yet put it on the car, but I have no hope it will do any different since nothing changed.
FUT did the same thing on my laptop. I disregarded it because my laptop is so full of garbage and so many versions of things like java etc, I figured it was something with my machine. My laptop is so messed up it's almost not usable in general... Anyways, I grabbed another one and it worked fine, that's why I assumed it was something specific to me. But the FUT isn't really a needed step, all it does is show you a pretty screen showing the cable is installed.

I noticed on my main laptop, when I plugged the cable in, the light was red. When I used the other laptop, it was green. Not sure what that was about. TS seemed to work fine either way. I just couldn't run the FUT.
 

·
Registered
Joined
·
9 Posts
well I figured if FUT didn't work TS wouldn't either. It all works on W7 32. I believe sometime in the past I tried a virgin 64 system and it still didn't work. I may try it one more time.
 

·
Registered
Joined
·
243 Posts
This too. I've been mucking around trying to make a live bootable usb with techstream on it, the drivers alone do not allow techstream to see the cable from the dropdown. Those reg values have to be present in both 32 and 64. Whoever made the 64 installer, did it all correct, and if you just run it, it will do everything for you. If you extract it, and manually change the drivers, it will not work. I've seen a lot of posts on other forums where people were doing that. I can't figure out why everyone was posting that's how to do it... I can only assume because the original 32 exe was flagged for viruses, and it does look like there are real ones in it. Extracting it, and manually doing it, would be a round-about way to not get a virus. Honestly, I would bet the x64 would just work on 32. I don't know who made it, but the only difference is the reg edit, there's no actual install or driver difference.
took me an hour to look for it please check post #1,265 the user 2010 was the one who made it lucky enough i saved the copy of it and got it running on here because the original link is no more there
 

·
Registered
Joined
·
243 Posts
I had saved it I even mentioned that on my previous comment. I have included in it in this mega file under 64bit folder that I had told u to download

Sent from my LG-H811 using Tapatalk
 

·
Registered
Joined
·
9 Posts
I previously downloaded that and ran it (#2248). It is called setup for MVCI-64bit Cable Driver.exe as I stated I have not tried it in the vehicle yet but I do not see anything that changed in the registry that I already had in there from the reg file that is floating around. I also have entries for a VCX-Nano that won't connect either.
 

·
Registered
Joined
·
243 Posts
I previously downloaded that and ran it (#2248). It is called setup for MVCI-64bit Cable Driver.exe as I stated I have not tried it in the vehicle yet but I do not see anything that changed in the registry that I already had in there from the reg file that is floating around. I also have entries for a VCX-Nano that won't connect either.
setup for MVCI-64bit Cable Driver.exe thats the same file the person had uploaded it in 2015 its his file i just renamed it
 

·
Registered
Joined
·
16 Posts
are u sure that u have setup techsteam as corporate
Thanks for the reply. Yes, it was set up as Corporate. I got some guidance from a Camry forum and, after previously trying 14.30 and 14.20, I was successful with 14.10. Win10, 32 bit, 1.4.1 cable, TIS 14.10.028, region: North America, User: dealer. Manually entered the car info and Health check and Customize showed up.
 

·
Registered
Joined
·
25 Posts
Thanks for the reply. Yes, it was set up as Corporate. I got some guidance from a Camry forum and, after previously trying 14.30 and 14.20, I was successful with 14.10. Win10, 32 bit, 1.4.1 cable, TIS 14.10.028, region: North America, User: dealer. Manually entered the car info and Health check and Customize showed up.
Could you post a link to the other forum? Just curious about what was going on.
 
2241 - 2260 of 2309 Posts
Top