[spido]

Thanks Gadget but i think broken my Win7x64...before try this Odis i dont have any problems but now...i got this error with C++...Vas Pc run under XP Mode and run ok but without 19 upgrade programs..and Odis 5 under Win7x64 not see Vci.Problems,problems...
Akte10-you dont have any tutorial? How do-it?

[Akte10]

Spido, for what you need tutorial?

VAS PC you need correct .stt tu become 19 Update Programming.
With .sgo file allone it dosent worke-

With Odis E you do not need .stt for flashing but it cannot flashing the SW index to another index, only with VAS and correct .stt

[asmodaios63]

Dear friend
the answer for your problem is.
for the odis version 3.0.0 you must first recover the windows or reinstall windows again and after the recovery or the new installation the first wat to do is the odis v3.0.0 .
it works.

[spido]

Akte10-how correct .stt ? I have vw flash disc and inside is flashdata with .sgo.Where is .stt and how correct this? Moved flashdata to c/sidis/home flashdata.PM pls.

[malikud23]

Hi Fantomel,
I have the same Vas 5054A with OKI. I am using a windows 7 32bit VM on macbook. First I tried ODIS 3.0.1 on windows 8.1 64Bit and it worked the very first time. Its show me error codes in OBD section. I tried perform coding which technically I can't without an online account. But I just give it a try. I see a blue light on VAS not blinking and I wasn't able to connect vas to ODIS again. Then I tried it on windows 7 32bit no luck. Fresh install and software install connect for first time and then getting not getting VIN information error. Tried so many time fresh VM and ODIS installs. Then Tried
ODIS 3.0.3
ODIS 2.2.4
ODIS 2.0.2

still no luck. even tried replacing 5054 folder in cheap clone section lol.

Should I give it a try on real windows 7 32bit on a real laptop with replacing 5054 folder or just buy one with AMB2300. Your reply will be appreciated

IMRAN

[SCOTT]

Hi Fantomel,
I have the same Vas 5054A with OKI. I am using a windows 7 32bit VM on macbook. First I tried ODIS 3.0.1 on windows 8.1 64Bit and it worked the very first time. Its show me error codes in OBD section. I tried perform coding which technically I can't without an online account. But I just give it a try. I see a blue light on VAS not blinking and I wasn't able to connect vas to ODIS again. Then I tried it on windows 7 32bit no luck. Fresh install and software install connect for first time and then getting not getting VIN information error. Tried so many time fresh VM and ODIS installs. Then Tried
ODIS 3.0.3
ODIS 2.2.4
ODIS 2.0.2

still no luck. even tried replacing 5054 folder in cheap clone section lol.

Should I give it a try on real windows 7 32bit on a real laptop with replacing 5054 folder or just buy one with AMB2300. Your reply will be appreciated

IMRAN

i would run PDU_API Test and see if your 5054a is working .

it is very easy to brick a vas5054a because every different version of odis you use it upgrades/downgrades the firmware when odis starts, Some people don't release this and think its not working so pull the usb lead to try another usb port or pull the vas5054a from DLC to check it and inadvertently Brick it.

[malikud23]

Hi Fantomel,
I have the same Vas 5054A with OKI. I am using a windows 7 32bit VM on macbook. First I tried ODIS 3.0.1 on windows 8.1 64Bit and it worked the very first time. Its show me error codes in OBD section. I tried perform coding which technically I can't without an online account. But I just give it a try. I see a blue light on VAS not blinking and I wasn't able to connect vas to ODIS again. Then I tried it on windows 7 32bit no luck. Fresh install and software install connect for first time and then getting not getting VIN information error. Tried so many time fresh VM and ODIS installs. Then Tried
ODIS 3.0.3
ODIS 2.2.4
ODIS 2.0.2

still no luck. even tried replacing 5054 folder in cheap clone section lol.

Should I give it a try on real windows 7 32bit on a real laptop with replacing 5054 folder or just buy one with AMB2300. Your reply will be appreciated

IMRAN

i would run PDU_API Test and see if your 5054a is working .

it is very easy to brick a vas5054a because every different version of odis you use it upgrades/downgrades the firmware when odis starts, Some people don't release this and think its not working so pull the usb lead to try another usb port or pull the vas5054a from DLC to check it and inadvertently Brick it.

PDU-API Test Application - V 1.20.037 I replaced the 5054 folder from Bad Clone folder.

EDIC_D_PDU_API_OS -----> Parse MDF File

Select VAS5054 Softing AG 082145725 --------> PDUMODULE/COnnect

VAS5054A Bliking and I see following Information

Return of PDUModuleConnect:
PDU_STATUS_NOERROR: PDU function call successful

************* Get module version Info **************

----------------------------------------------------
Module Short Name : VendorName='Softing AG' ModuleName='VAS5054' SerialNumber='082145725'
Module Vendor Name : Softing Automotive Electronics GmbH
Module HwName : VAS5054
Module SerialNumber : 82145725
Module FW Name : VeCom
Module FW-Version : 2.20.37
Module FW-Date : 15.1.2016 (Calendar week 2)
Module PDU-API SW Name : Softing D-PDU API for VCIs
Module PDU-API Version : 1.20.37
Module PDU-API SW Date : 15.1.2016 (Calendar week 2)
----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 81
----------------------------------------------------
Return of PDUGetResourceIds:
PDU_STATUS_NOERROR: PDU function call successful
----------------------------------------------------
Number of matching resource IDs: 1
----------------------------------------------------
Selected resource ID: 81

[malikud23]

Because of that shit BT module your clone can't upgrade it's firmware, and this is why you are limited, because in china one of those shit modules is so cheap and they adapted it to many tools like cdp+ and vas5054a.
This is why when you want to run newer versions you will need one like that, with AMB2300, nothing else.
Old firmware may work for now, but how it is working and for how much time ........ that is the real question.

You're 100 percent right. I returned that cheap garbage clone. I ordered new one with AMB2300. Working like a charm. Detecting car with no issue. I bought from ALiExpress. The link is following if someone want to buy it.
https://www.aliexpress.com/item/2014-New...e507e0ba1d

[KingKerosin]

Because of that shit BT module your clone can't upgrade it's firmware, and this is why you are limited, because in china one of those shit modules is so cheap and they adapted it to many tools like cdp+ and vas5054a.
This is why when you want to run newer versions you will need one like that, with AMB2300, nothing else.
Old firmware may work for now, but how it is working and for how much time ........ that is the real question.

You're 100 percent right. I returned that cheap garbage clone. I ordered new one with AMB2300. Working like a charm. Detecting car with no issue. I bought from ALiExpress. The link is following if someone want to buy it.
https://www.aliexpress.com/item/2014-New...e507e0ba1d

Which ODIS version do you use? I have the same Clone but he does not recognize the ignition.