Here is the GM Tech 2 Scanner PATHING DOCUMENT that every TECH 2 Owner should have. You work BACKWARDS from what you want to see.


See the attach PDF Document:

Look at MISFIRE in the chart and on the Tech2 Go to Special Functions, Powertrain and then misfire graphic

Misfire Graphic – Engine > Engine Controls > Special Functions > Powertrain Control Module
Misfire Graphic – Powertrain > Special Functions
Misfire Graphic – Powertrain > Special Functions > Special Functions (PCM)!JEwwXCLR!5EGrMvZegLzKzjB8pdJ_3ahPwNi2sdejVtmjAcob3eE

How to use JLR DOIP VCI SDD Pathfinder for Land Rover 2017

What for Land Rover the 2017 year?

JLR DoIP VCI (original or china clone) running Pathfinder or SDD software
It’s verified to read and clear codes of Range Rover L405 2007. Worked good!


This is a unit compatible with Pathfinder / JLR SDD software and all JLR vehicles with new vehicle architectures (from Range Rover/Range Rover Sports (L405/L494) Year 2017 onwards) or allow the enhanced diagnostics that Pathfinder will offer the retailer. In addition to the 2017 vehicle line application, the DoIP VCI will be capable of interfacing with the 2014-2016 Multi-CAN architecture vehicle lines on the Pathfinder diagnostic system. Pre-2014 and vehicles not detailed here will continue to use the current diagnostic system and VCIs.

How to use Pathfinder software to read/clear fault codes:
Vehicle: Land Rover Range Rover L405 2007

Run Pathfinder
Enter user name and password to log in


To use this maintenance tool, you should agree with items below:
– you’ve already read Garage Maintenance User Guide, the first section “Basic information”
– know how to use this tool to perform PDI, maintenance, diagnostics, etc.
– only used for Jaguar Land Rover vehicles
– finish junior training of JLR diagnostic tools
– obey laws & rules of vehicle health and security in your areas
– obey all policies & procedures of the dealer repairing

Search your vehicle via VIN
Auto scan
Automatic ignition switch not supported
Click on OK

Vehicle information:
Land Rover Range Rover L405 (DoIP)
YEAR: 2007
MILEAGE: 5804km
DRIVER: LHD (left-hand driver)
Go to ECU Diagnostics
Reading fault codes
Read All DTCs
Go to clear all DTCs
Then refresh DTCs

JLR DOIP VCI Car List: (14-16MY)
XE (X760)
F-Pace (X761)
F-Type (X152)
XF (X260)
XJ (X351) – 16MY only
Evoque (L538)
Discovery Sport (L550)
Range Rover (L405)
Range Rover Sport (L494)

Disclaimer: All about JLR DOIP VCI and Pathfinder here is China clone version. But it can works as good as the original.

Lexia3PP2000 on VMware12 XP Pro SP3

Content includes: VMware 12 image with XP Pro SP3 32bit English and pre-activated Diagbox 8.55 (v07.855) Multilanguage ; as well as VMware 12 image with XP Pro SP3 32bit English and pre-activated PP2000 V25 and Lexia 3 V48 Multilanguage.

Part 1: VMware 12 image with XP Pro SP3 32bit English and pre-activated Diagbox 8.55 (v07.855) Multilanguage
– VMware 12 image with XP Pro SP3 32bit English
– Diagbox 8.55 (v07.855) Multilanguage | 09/2017 (20 languages: Chinese, Croatian, Czech, Danish, Dutch, English, Finnish, French, German, Greek, Italian, Japanese, Hungary, Polish, Portuguese, Russian, Slovenian, Spanish, Swedish and Turkish)
– PSA XS Evolution Interface Drivers
– PSA XS Evolution Interface Automatic Firmware 4.3.7 updating, Launcher_850 by Simple
– Diagbox Language Switcher
– Diagbox Killer
– PSA Interface Checker + All Firmware’s from 2.0.1 to 4.3.7
– Backup APPDIAG.sys activation file in Desktop
Lexia3-PP2000-on-VMware12-XP-Pro-SP3-1 Lexia3-PP2000-on-VMware12-XP-Pro-SP3-2 Lexia3-PP2000-on-VMware12-XP-Pro-SP3-3 Lexia3-PP2000-on-VMware12-XP-Pro-SP3-4 Lexia3-PP2000-on-VMware12-XP-Pro-SP3-5

Info of Launcher_850:
Contents of the “C:\AWRoot\bin\launcher” folder, this release includes firmware versions:

LX = Lexia and PP2000
DB = DiagBox

1- Make a backup of all files in your “C:\AWRoot\bin\launcher” folder, no need to include folders inside \launcher.
2- Extract all files of the “” into “C:\AWRoot\bin\launcher” overwriting existing files.
3- Connect your XS Evolution VCI and start DiagBox
4- DiagBox will check current firmware version and (upgrade/downgrade) using the file APPLI.COM, if necessary.

To change the Firmware version, rename the desired Firmware file from APPLI_X.X.X.COM to APPLI.COM.     17.9 MB!N1kA3bza!qgrVOsWJQZJIW1QwUOXVl8MAbZuhO6gdf-EOKO3-E6M

The update function can be disabled by setting “MAJ_COM=TRUE” to “MAJ_COM=FALSE” in “C:\AWRoot\bin\Launcher\ap.ini”

In case reverting to the original setting is needed,
1- Delete all files (only) inside “C:\AWRoot\bin\launcher”.
2- Restore backed-up files back to their original state.

Part 2: VMware 12 image with XP Pro SP3 32bit English and pre-activated PP2000 V25 and Lexia3 V48 Multilanguage
– VMware 12 image with XP Pro SP3 32bit English
– PP2000 V24.99 [V25] Multilanguage (24 languages: Chinese, Croatian, Czech, Danish, Dutch, English, Finnish, French, German, Greek, Hebrew, Indonesian, Italian, Japanese, Hungary, Norwegian, Polish, Portuguese, Russian, Slovenian, Spanish, Swedish, Thai and Turkish)
– Lexia3 V47.99 [V48] Multilanguage (20 languages: Chinese, Croatian, Czech, Danish, Dutch, English, Finnish, French, German, Greek, Italian, Japanese, Hungary, Polish, Portuguese, Russian, Slovenian, Spanish, Swedish and Turkish)
– PSA XS Evolution Interface Drivers
– Lexia3/PP2000 Language Switcher
– KeyGen

Lexia3-PP2000-on-VMware12-XP-Pro-SP3-6 Lexia3-PP2000-on-VMware12-XP-Pro-SP3-7 Lexia3-PP2000-on-VMware12-XP-Pro-SP3-8 Lexia3-PP2000-on-VMware12-XP-Pro-SP3-9 Lexia3-PP2000-on-VMware12-XP-Pro-SP3-10

Unzip using 7-Zip and run with VMware Player version 12 onwards.

All software’s activated and PSA XS Evolution interface USB drivers installed.

When open these to your VMware use “I moved it” option, then pre-activated Diagbox works. PP2000/Lexia3 might need re-activate using included KeyGen. If needed see Youtube video, how to activate PP2000 with KeyGen.

No password required, Reputation, Thanks or Donations are appreciated!

You can change the Diagbox/Lexia3/PP2000 language using my PSA Language Switcher tools (Read details in the following parts).

Toyota Techstream V14 reviews failure or success

Do you have any good success with TOYOTA Techstream V14 latest version? Here are Techstream V14 reviews.


Related Contents:

TOYOTA Techstream V14.00.018 (02/2019) free download on win7

Review 1: failed

Have weird issue with Techstream (v14.00.018). I can’t see any interface  when I go into ‘VIM Select’.
I use MongoosePro cable and it works with other software. So this in not an issue with a cable or drivers.
I have also Xhorse 3in1 and the same problem.

Review 2: failed

I had the same problem – can’t see any interface although I can’t remember exactly what I did to resolve it. I believe I did a uninstall, clean with ccleaner and reinstall. You can edit a config file in the tech stream directory to manually select your interface as a way around it.  I’ll have to look at which file it was exactly when I get back to work Monday

Review 3: failed but works now

Had this problem also some time ago.
Something about software conflict. If you have HDs, IDS or JLR installed on the same computer, I’d start by getting an OS where none of them is installed. It’s not happening for everyone so I can’t tell which exact circonstances Makes this happens

Review 4: failed

It does not matter if it works with other software,techstream need to recognise the cable with the drivers for techstream…
Try installing in a laptop that does not have other software for mongoose,to see if its fixed…If it is,then drivers confict between the programs

Review 5: failed but reworked

I had the issue but got it to work again.
As suspected issue was triggered by me when playing with Honda HDS/i-HDS.
To make it fun, in my system problem occures when I uninstall SPX MVCI drivers(I don’t have such interface at all) which are part of HDS.  That’s the moment I lose all interfaces in Techstream.
That in theory should have nothing to do with Techstream, but it does. I can easily reproduce it. I tried that.
I can’t explain why it happens exactlly.Probably there is still some conflict in Windows,since such correlation shouldn’t exist. At least I have now Techstream and HDS working again on my machine.
I still would like to know in which file of Techstream there is an option to force which interface it willl use.


So, what is the latest version should you use for Toyota diagnostics?

Techstream v13.

v14 is only for vehicles made after jan 2019 and also it have some programming issue…

v13 (even the crack sw) can be used with relief coz it has been tested by real professionals. success on Windows 7 for Toyota customization, diagnostics, programming. works perfectly with MINI VCI cable and VXDIAG VCX NANO Toyota …

Look here: Techstream v13 tested successfully

How to Install Toyota Techstream V13.00.022 on Win7

?Cómo resolver FVDI 2018 en 2014 BMW 3 “No se pudo sincronizar HW”

Cuando probé mi FVDI 2018 para programar la llave para el BMW 3 2014, recibí el mensaje de error “Al realizar la sincronización de HW a través de Internet … No se pudo sincronizar HW, quedan horas: 0.


Compruebe si la conexión a Internet está disponible para realizar la sincronización de hardware.

Si el hardware no está sincronizado en las próximas 0 horas, no podrá comunicarse con el vehículo.

Por favor, confirme que ha leído y comprendido esta advertencia.


?Alguien tiene el mismo problema?

Finalmente, recibí la respuesta del ingeniero de, me dijeron que este es un mensaje normal, simplemente haga clic en “Aceptar” para continuar.

One laptop with 9 boot systems can work for Allscanner Vxdiag

One device of VXDIAG Porsche Piwis III and one laptop with 9 boot systems to support all of those dealer tools software together, please refer to the following images:


How to solve GM MDI Interface not connecting errors

Here are all solutions aimed to help fix GM MDI Scanner multiple diagnostic interface connection/communication issues (connection by usb, wireless ethernet, wired ethernet)… big thanks to all contributors and

For mdi not connecting…

First, you should make sure that the MDI Manager software should be installed on the PC and the MDI must be powered up before you use it to communicate.
Also the MDI should be configured for wired ethernet or wireless communication. If the USB is available, the MDI will connect by using the USB and if not, the MDI will connect by using wired ethernet and if neither of them is available, the MDI will connect by using wireless.
If the MDI can not communicate with the MDI, you should check the cables if they are securely attached to the MDI, if the MDI has completed its power up sequence, if the connector pins are clean and if the MDI Manager software is running.

In detail…. mdi connection can be discussed in the following 4 parts:

Part 1: GM MDI USB connection
Part 2: GM MDI connection by wireless ethernet
Part 3: GM MDI connection by wired ethernet
Part 4: Tech support: GM MDI not connecting

Part 1: GM MDI USB connection

And if you connect them by USB, you need to check the MDI USB connection is detected by windows. About the solutions, you can connect the MDI to the PC USB port and power up the MDI. Open the Network and Dial-up Connections Window from the Windows Control Panel. Then check for the device name ETAS USB Remote NDIS Network Device. If it is not running, check all USB ports on the PC and verify that the MDI is powered on.

GM MDI Manual: What if MDI fails to connect on USB
*   Check USB cable connections.
*   Check Firewall Settings on your PC.
*   Verify a USB Hub is not being used (MDI has a fixed USB address).
*   Verify that only one MDI is connected to your PC using USB.
*   Verify the USB driver has been installed on the PC (look for device name ‘ETAS USB Remote
NDIS Network Device’ under Network Connections).
*   Try connecting to other USB ports on the PC.

Part 2: GM MDI connection by wireless ethernet

If you connect them by wireless ethernet, you should make sure that wireless communication is enabled and the IP configuration is properly set using the MDI Manager software. Then what you need to check is that the USB cable is not plugged in, the MDI is not being used via wired ethernet and the wireless card is properly seated in the MDI. You can contact your IT department and check that your PC is detecting the wireless access point and the correct security settings have been configured for the MDI.

GM MDI Manual: What if MDI fails to connect on Wireless
*   Check the wireless card is properly seated in the WiFi GM MDI.
*   Confirm LEDs on the wireless card are lighted when the MDI is powered.
*   Verify the MDI and PC are within range of the Access Point or Router.
*   Verify that the PC is connected to the Access Point or Router.
*   Verify signal strength of the wireless network from the PC.
*   Check Firewall Settings on your PC
*   USB connection takes precedence, unplug USB cable.
*   Wired Ethernet connection takes precedence, unplug Ethernet cable.
*   Connect to MDI using USB and run MDI Manager to verify the Wireless Settings are
configured correctly.
o Wireless interface is enabled.
o AP settings configured for proper security (authentication, encryption).
o Signal Quality (fair, good, excellent) indicates connected to AP.
o The MDI, PC and AP are on the same subnet
o If using static IP, verify the IP Address and Subnet mask are correct (supplied by network

Part 3: GM MDI connection by wired ethernet

And if you connect then by wired ethernet, you need to ensure that the wired ethernet communication is enabled and configured using the MDI Manager software. Then you should check that the USB cable is not plugged in and the MDI device detects wired ethernet activity by viewing the lights blinking on the wired ethernet port of the MDI. And also you can contact your local IT department and check that the MDI and the PC are on the same subnet.

GM MDI Manual: What if Car Diagnostic Tool MDI fails to connect on Wired
*   Check Ethernet cable connections.
*   Check Firewall Settings on your PC.
*   Verify the MDI and the PC are cabled into separate LAN connections on the same network.
*   Verify that the PC is properly configured and can communicate on the network.
*   USB connection takes precedence, unplug USB cable.
*   Connect to MDI using USB and run MDI Manager to verify the Wired Ethernet Settings are
configured correctly.
o Wired Ethernet interface is enabled.
o If using static IP, verify the IP Address and Subnet mask are correct (supplied by your
network administrator).

Part 4: GM MDI not connecting

This is professional technical support for the error ” not connected to MDI”.

All what you need do is to refresh the GM MDI firmware

*   Press this button and connect the power:

*   Keep press this button and connect it to power, the power light will be on, wait about 10 seconds:

gm-mdi-not-connecting-1 gm-mdi-not-connecting-2

*   When all light is on, then you can release the button, and it will enter firmware refresh status:


*   Connect GM MDI with your PC via USB cable, prepare to refresh the firmware:


*   Open “GM MDI Manager”, choose “Recover”:


Program A New ECM Module to Nissan Murano with Consult 3

Background information:

A Nissan Murano Z51 3.5L CVT 2012Y  had an accident.  The lower part of the connectors of the original engine control unit moved by 7-8mm inside the board, half of the pins are broken off, one heating channel of the upper lambda does not work, although the field effect transistor is jerky. Got and most lambda, but it has already changed.

Bought a new ECM, there were no problems with snapping, software is different. The old module stands still, the new Nissan Consult III Plus lies on top:


Disclaimer: The tutorial was translated from Russian. Credit to Car-Buster. You are at your risk.

Marking the old ECM module: 23710-1AA4B
Marking the new ECM module:  23710-1TJ0A


Well visible recessed connectors:


Back of the control modules


During this procedure, all previously programmed keys are erased, so it is strongly recommended to register all keys at a time:

Device used:  original Consult-III diagnostic without the Immo card , and with the correct software:
If you using the clones, better go for Consult III Plus, Nissan Consult 3 Plus adds ECU programming function without working with immobiliser card since software version v65.12.


There are many step-by-step screenshots, so I’ll lay out the most basic.
After installing a new unit, the car naturally won’t start, there will be an active error due to mismatch of ID keys recorded in the ECM and Immo , in short, there is no sync P1611 ID DISCORD IMMU-ECM :


Yes, the ignition turns on, the starter turns but the car no start
Let’s go.
Turn off the ignition, turn on the emergency light, connect to the car, choose vehicle model Murano Z51 after 2010.v. and press the Select button :


Confirm the choice with the Confirm button , but now select Repair :
Click on the tablet (top left):

We drop down the list and select NATS :

Click Start :

In the menu that appears, click Pin Read and Next :

We get the PIN 14A06 , press END :

You also need the generic code Immo , in our case variant is 1211 :

After this, select STRG LCK RELES (KEY ID ERASE) , this procedure will erase the keys and pre-lock the steering column latch:

Enter the Immo code, 1211, and run the procedure:

Everything is carried out with the ignition off and with the emergency lights on. We hear how the steering column is unlocked, and the ignition is now turned on only when something (key) is inserted into the emergency key slot. And one more thing, the ACC mode disappears , this is normal, that is, immediately switch ignition OFF-ON and not like people OFF-ACC-ON :

The next step, turn on the ignition with any key, and in the NATS menu we already choose C/U Initialization :

Enter the immo code 1211, and go to the last screen, claiming that initialization is completed:
Turn off the ignition, take out the key (it has not yet been registered, but served only to start the procedure). Now we insert the first key into the slot, turn on the ignition, turn off the ignition, pull out the key, the immo indicator flashes 5 times. Repeat this procedure for keys 2-5.
In my case, only 2 keys. Turn off the ignition, check the operation of the radio channel from each key. Works. Now remove the first key away from the car, and leave the second inside, start the engine – with a half kick. For the second key is similar.
As a result, there is no error in heating one of the upper lambda, and in the current data adequate readings. Engine speeds develop adequately without kicks. New engine control module was replaced successfully.

2009 Chevrolet HHR key fob program Tech 2 china clone done!

Success! Have tested Tech 2 clone for 2009 Chevrolet HHR key fob!

The detail… Here you go.
Install the GM Tech 2 scan tool
Turn ON the ignition with the engine OFF
Power On the Scan Tool
Hit Enter
Vehicle identification – Model Year > (9) 2009
Vehicle identification – Product Type > Passenger Car
Vehicle identification – Product Make > (1) Chevrolet
Vehicle identification – Product Line > A
Diagnostics > F1: Body
Body> F5: Remote Control Door Lock Receiver
Module Setup > F1: Program Key Fobs
Program Key Fobs > F0: Invalidate all key fobs

The procedure will replace the previously programmed key fob with the key fob requiring programming.

(Follow Instructions, if it don’t work repeat entire procedure)



All desired key fobs must be present.

When the first key fob is programmed, the module will erase the rest of the slots.

The module will fill slots until [Done] or [Exit] is selected.

Note: Only select [Start] once. If the procedure is started again, the control module will start over.

Job’s done!

This was my order of GM Tech2 scan tool with TIS2000 software:

This is how GM Tech 2 looks out of the box:


Turned on:


The following 3 paragraphs are what I mail to
I tested device and it works well. Problem is the screen. I believe for return I would have to send back and pay for shipping. This would take a long time and I have work to do using the tool.
Right now I am using a laptop connected so I can see the full screen


I would rather do partial refund or try replacing the screen myself.
Will you do a partial refund?
Can you send or help me find a replacement screen?
I have been happy so far with so far. The price, service and shipping speed was good.
I hope we can reach a positive solution.

Finally, ship me a new package.

Just want to let you know, I finally took the time to really test out the replacement I was sent and it appears to work perfectly.

One small issue is that I was sent a Car Diagnostic Tool GM PC Card and not a Saab one. I tried to write the GM Card in my laptop to Saab software but I ended up damaging the card. It was my fault. I know that I could have contacted you for help and you would have taken care of me.

I was able to find another Saab Card and get it working so I am very happy now. I do not need any more help.