Monday, November 27, 2017

How to Solve Vas5054a ODIS-E Error ODS8024E

Purpose: solve ODS8024E error in ODIS-Engineering 6.7.5 for 5054a head

Hardware: OKI VAS5054A unit, firmware version 1.20.37
Software: ODIS-S perfectly
         ODIS-E 6.7.5...get an error when select a module for flashing

Operation system: running ODIS-E and ODIS-S natively on Windows 10 x64

Error message:

Infrastructure. Vehicle (EcuCom):
An error occurred during communication with the MCD system:
The MCD job <SinglJob_StandECUIdent>
did not delivery any results after completion.

How to setup ODIS Engineering 6.7.5:

I believe with odis-e 6.7.5 you have to use the projects found in odis-s 3.1.3.

That is one way of doing it. Admin--->diagnostic data--->ODX update index file 1

I am using the other method Admin- Save Locations - Diagnostic data - engineering odx projects (...) Target directory. Just select the project directory of odis-s 3.1.3.

In case you have o-e 6.6.1 do the same with odis-s 3.0.3

I am not sure if it will create problems if one tries to use newer project versions than the ones I have paired with above. Not tested. I try to be consistent, to have compatible pdu-api with hardware in hand.

In case you want to install a newer odis-s first install the odis you need for the odis-e version you have, copy the projects to project engineering project folder and then uninstall that odis-s in order to install the newer version you wish. Use new folder directory were you copied the projects to.


The Q7 4M platform requires the use of the project file "AU73X" and NOT MLBEvo, and my bro’s Q5 8R requires Au48x. Was able to successfully flash the gearbox! 

Flash with help of the following tip. I copied here -

Information on ODIS report up in the vehicle data:

Then inside ODIS go and choose your engineering "project vehicle" as follows:

AU56X in this case

Click on the green triangle

the list of computers with different options on the right

Select the computer to update and double click on Flashing right

Then select the computer you want to update and click File local Flashing. In

principle on the DVD of Flash, you can only select the flash file on your computer

Note: you can also select an older version; that is, maybe the software will allow flashing with.

on system No 17, which corresponds to the instrument cluster is version 0120

So, select the 0240 release

Also, ok to select the updates to the other computers that it be done in the future without

further intervention.

(Personally, this would not be recommended unless you follow the precautions.)

click Start Flashing:

Now a security window will appear:

Click YES, and Flashing begins:


Once completed, cut and replace the contact and validate the window, by software pop-up

erase all memories of events on all systems, click YES.

And then the report window is displayed:

The flash was successful, system 17 passed on new version

On a side note: VAG Audi ECU Flash: VAS5054A or VAG CAN PRO

Vas 5054a full chip good quality with odis-e (Vxdiag vcx nano 5054- a redesign of vas5054a) and VAG CAN PRO with VCP can do it.

With 5054, ODIS Service is the "normal" diagnostic software. Without Geko account you won't be able to do any updating/flashing.

So either need 5054, and purchase subscription from VW and use ODIS Service to perform these jobs. That is, you must have valid license and valid online account for online flash.

Or without subscription, need 5054 and ODIS Engineering and offline flash files. Odis 6.0.9, odis 5.0.14 or odis 3.0.3 should be ok......old OIDS-E is working fine with it..

For offline flash you must use the Odis Engineering. For online flash you must have valid license and valid online account........

Be careful when updating VAG ECU's. It is best to read all relevant TPI when flashing VW cars, as some flashes require other work to be performed to work correctly, and not all flash files are appropriate for all cars/engines. TPI is the only source of information I know to check for this info.

Wednesday, November 15, 2017

VAS5054A ODIS-S 4.2.3 full with Keygen license & Launcher Postsetup

Crack ODIS-Service 4.2.3 with Keygen + full license + Launcher Postsetup is tested working 100% OK.

Part 1: ODIS-S 4.2.3 crack: with keygen + Launcher PostSetup
It’s the latest crack version tested by professionals. It packs with keygen without send HW ID for activation. Works good.
odis-s-4.2.3-download-free-1 odis-s-4.2.3-download-free-1
ODIS-S 4.2.3 works on below hottest VAS 5054A and VAS6154:
sp33-c: good one, green pcb with OKI chip
SP33-BO: share the same manufacturer as sp33-b, blue pcb with OKI chip
sp33-b: cheapest one with green pcb
sp308: VAS 6154 VAG Diagnostic Tool for VW Audi Skoda
OS restriction:
  • VAS 5054, VAS 5054A and VAS 5055 work on Windows 7 client on existing systems until 2019 or acquire the Windows 7 client from IT Client Support for replacement devices.
  • new diagnostic interface VAS 6154 (known as the WLAN remote head) works on Windows 10, win7.
ODIS-S 4.2.3 License:
Audi, FAW Volkswagen, Shanghai Volkswagen, Skoda and Volkswagen, same as ODIS 4.1.3.
All license can be installed in one same computer.
ODIS-S 4.2.3 installation:
same as ODIS-S 4.1.3.
Youtube video is coming.
Part 2: ODIS 4.2.3 released notes
Functions in version 4.2
The key features newly added or revised in release 4.2 are described briefly in this section and the additional CCB_DS IDs implemented are cited.
CCB 1127 The update check when starting ODIS Service should be “silent”.
CCB 1140 Functional Tester Send Present Request only once
CCB 1589 support of new VW cross section load books
CCB 2004 Display of a support guideline
CCB2015 Farsi (RTL) language support
CCB1692 Display connection quality VAS6154
CCB1968 trace records for DoIP
CCB2038 Read and display DTC snapshots
Defect resolution in version 4.2 The problems resolved in release 4.2 are described briefly in this section. 19502 In the case of end-of-life vehicles (European market), the start of diagnostics remains “waiting for synchronization”
16858 Update OS 2.2.4: VAS 6558-6558A ODIS is available twice in the program and functions after the update.
18569 Flash abort while flashing the climate control unit via DoIP
18648 OS 3.1 TPI Reference to diagnostic object (extend inspection plan) partially not functional
18751 Metrology is not automatically removed or uninstalled using ODIS Service Uninstall
18891 Softing feature on Windows 10 computer
19131 Control unit 0025 Immobilizer is not automatically identified when boarding the A8_2003
19171 Network status is not detected correctly on OS 4.0 and VAS6154 USB
19182 ODIS Service 4.0.0: The green arrow is missing on the Finish / Next button
19207 Read identification data, ident status is not displayed in the print log.
19227 log files are filled with ArrayList messages
19247 ODIS S: different tester present behavior between diagnosis and flashing
19251 OS 4.1.0 Build 41_3_0_1 contains the wrong Diagnostic_Data_Hook
19278 Entry of a special character “_” or “-” (underscore, hyphen) is not possible when installing in the hostname of VAS 6154
19289 Evaluation of unauthorized event memory incorrect
19296 Saved diagnostic session can not be loaded
19298 Error while logging in to CPN via the button Info-medium because of certificate VW-CA-Proc-07
19302 Information about the VCI at the top of the user interface disappears when the language is switched
19313 ODIS Service 4.1.3: The diagnostic protocol does not state that the communication is via DoIP.
Defect resolution in version 4.2
19318 OS 4.0.0 and 4.1.0: A not yet translated standard text is not displayed in the execution system when using a language as Created, it does not use fallback mechanism
19319 OS 4.0.0 and 4.1.0: A text module is not displayed in the execution system when using a language other than Created
19325 OS 4.1.0: When using placeholders with TextIDs, text blocks or ANSI text blocks, a NULL is returned instead of these texts. The placeholder (variable) is displayed correctly.
19350 Spelling errors in the setup.configurator: Special characters instead of special characters
19370 OS 4.1.3 Malfunction of the status display of the network

Supported vehicles with Version 4.2 Approved AUDI vehicles
  • All AUDI vehicles are supported Approved Volkswagen vehicles
    •All Volkswagen vehicles are supported Approved Volkswagen Nutzfahrzeuge vehicles
    •All Volkswagen Nutzfahrzeuge vehicles are supported Approved Seat vehicles
  • All Seat vehicles are supported Approved Skoda vehicles
  • All Skoda vehicles are supported Approved Bentley vehicles
  • All Bentley vehicles are supported Approved Lamborghini vehicles

The following Lamborghini vehicles are supported: Gallardo from MY09-MY14 (only immobilizer and Radio PIN Code) Aventador und Huracán Approved Bugatti vehicles
Bugatti Veyron and Bugatti Chiron are supported Approved MAN vehicles
MAN-TGE is supported

Part 3: Free download ODIS-Service 4.2.3 on Mega 
ODIS 4.2.3 Offboard DiagSetup:!5coSwAyb!KfVPxVtmTxTNoXOuWnC4VCtsJpYjFdtRNKmZ-FhGFlc
ODIS 4.2.3 Post setup:!dcYyWTIb!5hDllZnh8W_2r1-On437ypvusQ4G7-O7FuOCfzqRdLo
AUDI+VW+SKODA+SEAT offboarddiag launcher:!kAoFlDTJ!gk-dMjiia0_kCQNYKoDgnH-LpjMDYTGkffj_YMjjRwo
Part 2: Where & How to activate ODIS 4.2.3

ODIS 4.2.3 Free Activation:
(Write your HW ID and you’ll get ODIS activation keys)

That’s all.

Wednesday, October 25, 2017

How to use VAS 5054A via USB

How to connect, install, use VAS 5054A via USB?

Look here:

When you use vas5054a via USB connection?

In special cases you can also operate the VAS 5054A using a USB cable connection:
- To configure the VAS 5054A in the Diagnostic Interface Configuration Utility program (Bluetooth settings, activation of the built-in buzzer, auto power off),
- For use in areas in which wireless communication is not permitted,
- For applications that require a high-performance connection to the vehicle.

How to install vas 5054a via USB?

If you want to install the VAS 5054A only via USB when installing the application software, do not yet connect the VAS 5054A to your PC. When the Select EDIC to install dialog box opens, click Cancel. The application software is completed without installing a diagnostic interface.

Plug the VAS 5054A into the diagnostic connector. Open the rubber cover on the front of the VAS 5054A and attach the mini USB connector of the supplied USB cable. Connect the USB cable to a USB port on your application PC.

The following description assumes that the diagnostic application has already been installed.


(Fig. 3-25 Windows Found New Hardware Wizard )
Windows automatically detects the VAS 5054A through Plug and Play. In Windows 2000 the drivers are installed without a confirmation prompt, in Windows XP the Found New Hardware Wizard launches (see Fig. 3-25). When prompted if you want to connect to Windows Update, select No, not this time (Fig. 3-25). Click Next> to continue installation. Select the Install the software automatically radio button and click Next> (Fig. 3-26). Click Finish to close the wizard (Fig. 3-27).

(Fig. 3-26 Automatic installation of the driver files for the VAS 5054A )

(Fig. 3-27 Completing the wizard )
Your PC is now set up for a USB connection to the VAS 5054A and ready for use with your diagnostic application.

Thread: Vas5054a USB not showing up on device manager 


I have brought a vas5054a cable with ok cool, good board and good Bluetooth.
The problem is that I tried to connect it over Bluetooth, which I was able to in the manager. Then I opened odis and would try diagnostics but odis could not find the interface
So I would try with USB. But when I turn off Bluetooth and plug in the USB, then nothing happens. I have also tried on Linux and it does not seem like the interface gets an connection to the computer at all.
I have tried different USB cables and I have looked on the PCB, but everything looks ok.
What can it be?

Rely: you have to re-identify ur interface by odis it self in diagnostic option to the right side column when you wanna change the connection.

Sunday, October 22, 2017

VAS 5054A Odis-E 7.2.2 cant run under VMware

Topic: VAS5054A Odis-E 7.2.2 cant run under VMware?


When I try to run Odis-E 7.2.2 it says "This program cannot be run under VMWARE"


Close VMWare
Go to your virtual machine folder
Make a backup of your VMWare virtual machine file (.vmx) and rename it xxxx_backup.vmx or something like that
Open the original .vmx file in Notepad and add the following text all the way at the bottom:

Code: = "TRUE" = "TRUE" = "TRUE" = "TRUE"
monitor_control.disable_directexec = "TRUE"
monitor_control.disable_chksimd = "TRUE"
monitor_control.disable_ntreloc = "TRUE"
monitor_control.disable_selfmod = "TRUE"
monitor_control.disable_reloc = "TRUE"
monitor_control.disable_btinout = "TRUE"
monitor_control.disable_btmemspace = "TRUE"
monitor_control.disable_btpriv = "TRUE"
monitor_control.disable_btseg = "TRUE"
usb:0.present = "TRUE"
usb:0.deviceType = "hid"
usb:0.port = "0"
usb:0.parent = "-1"

Save it, close it.
Then it will work again. I've got ETKA8, Elsawin 6, ODIS-S 4.2.3 and ODIS-E 7.2.2 running in just one virtual machine at Windows 7 x86.

Warning: VMware Tools will not work anymore, so no easy/copy paste anymore. Be creative on that problem, for example use your automatic syncing cloud-storage or something like that.

Video: Odis-E Windows 7 native install



This solution worked for me

I added this to my .vmx files and seems to do the trick
Odis 7.2.2 now running in virtual machine
monitor_control.restrict_backdoor = "TRUE"

Saturday, October 21, 2017

Cloned VAS 5054A PCB rework

Cloned VAS 5054A PCB rework... here you go.

the bluetooth module is a fake one since it has no capacitors and no resistences on the back.
Open these images if you are interested and save them on your computer. Then you can zoom on them and see more clear all parts.

This is the original bluetooth without shield AMB2300 and back of it.

Credits to fantomel

If you’re not equipped with technical knowledge and experience, better not take a risk to try it. Maybe there will be some damages on your car. VAS5054 genuine should be your best solution. But, if your budget is limited, have a try with a HQ VAS 5054 clone! Attention please! Various VAS5054A clone flood into the market, some good and some bad. You should make a decision yourself.

Most VAS5054A clones are one of the biggest lottery of all.

A lot of fake chips, fake amb's , fake infineons......or missing or reinterpreted projects.
As you well know prices for chips and making a pcb has evolved in - a lot and all these tools use old and cheap chips. Same as a new car has a price, has exited factory min -500 eur. In old days all tools were made at hand, now because of tech is done automatic, so less costs, same for pcb's and funny same for old chips.

Most Chinese do not want to make them proper, that is all. They all have projects and projects of projects, all remade to cut costs and sell some more reinvented stuff. 

SO take a good look when you buy, take a very good look at what you get when you get it and in 90% of cases you will need to do more or less rework on it.

This is Quality A+++ VAS 5054 china clone with GREEN pcb, with real amb2300 and oki

The green version has made up a item number in china to subdivide the different products and qualities.

It is supposed to be the best quality clone. Everything that is needed. The quality looks fine and the AMB2300 Bluetooth (AMB2300 IS THE MAIN THING!!!) as well as the OKI Chip (w/o leg cut) are on the green PCB.

Practice says otherwise, different sellers have different qualities! Best advice is to be sure through clear pictures of the PCB, and even then they can send you something else. 

Vas 5054a clone above is verified to:
have the real AMB2300 and OKI chip.
works perfect with ODIS 4.1.3 software crack
it’s OEM, so it fully supports every VAG model
and it’s best for flashing
online coding service also OK

Other VAS5054 copy with bad reviews! Forget it! !!!!!!!!!

Vas5054a with white PCB:

Vas5054a with blue PCB: