Need VAS5054A firmware dumps

[veloseeped]

Need dumps of XC161 CPU and 29F160DB Flash.

Especialy from device real working with UDS-protocol.

FYI. Both dumps can be read in XC161 boot-mode

[veloseeped]

Nobody has?
If sombody will help i'll can explain how to read dumps from device.

[miha99]

OK explain how to read.

[hadrian]

I have 2 VAS5054A interface. One ok and second not ok. Writing only external flash 29LV160 does not help. Please explain how to read XC161. I tried with FlashHit program and interface without success.
Thanks.

[veloseeped]

Please explain how to read XC161. I tried with FlashHit program and interface without success.

Use minimon soft in boot mode.
Connect PC to device with RS232TTL inferface according picture.
MCU dump example is attached.
http://www.digital-kaos.co.uk/forums/attachment.php?attachmentid=290616&stc=1

[impactops]

This is a waste of time

Regards
Impactops

[Zohar]

Some data and serial number of device is stored in ext. eeprom
Flash without eeprom is nothing :)

BR

[ozzy_rp]

I have some flash from VAS5054
Readed from old vas
292318
292319

and from unknown vas
292315
292316
292317

[impactops]

Some data and serial number of device is stored in ext. eeprom
Flash without eeprom is nothing :)

Well, it's not stored in the 29f160, so like I said that is a waste of time. Even if you read the serial eeprom where the serial number is stored, then what? What are you going to change it too? the same to that of the software you have registered to a particular serial? and your going to keep doing this each time you have software registered to a different serial or maybe change it to a genuine serial and try to sell it as a genuine interface??

All of these scams belong to the abu dhabi, JC con men across the road

All software that is serial specific in using the VAS5054 is either modified so that the serial of the interface you want to use is added to the license or modified so that it is not serial specific so that any VAS5054 can be used, that way no mods to the interface are required.

Merry Christmas

Regards
Impactops

[gwh11]

Excuse me,
The firmware is read by any software,
Dump

[impactops]

Excuse me,
The firmware is read by any software,
Dump

You mean once you have dumped the eeprom(s)?

Regards
Impactops

[adolf80]

I have some flash from VAS5054
Readed from old vas
292318
292319

and from unknown vas
292315
292316
292317

Tell me how to download these files?

[adolf80]

and these files to

[adolf80]

Who can share the XC161 dump?

[donjuan020]

http://www.perschl.at/minimon/minimon_v2228.zip


http://www.perschl.at/minimon/minimon_usermanual.pdf


http://www.perschl.at/minimon/minimon2119.zip

[Stalkerwd]

Hello friends. I can not download cpu_xc161cj.rar from post 5. Please send it to xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

[ZoOr]

I Need am Dump from 5640a Chip... Can any help?

[ricked]

I Need am Dump from 5640a Chip... Can any help?

use D-PDU API software for this, you can up and downgrade with it

[ZoOr]

The content of my 5640A is faulty and prevents the Bluetooth module from booting. So I need a dump to flash it with my serial number and to flash it.

[sfernandes]

hey trying to revive my vas5054a clone writing the dumps posted in the thread. It connects via bluetooth and usb. Failing on "pdu connect error" in test application. In vci info on odis s and odis e firmware details are blank. Bought another clone and it works perfectly. Hoping these dumps would help me fix the broken clone. Any one got any suggestions?

[impactops]

hey trying to revive my vas5054a clone writing the dumps posted in the thread. It connects via bluetooth and usb. Failing on "pdu connect error" in test application. In vci info on odis s and odis e firmware details are blank. Bought another clone and it works perfectly. Hoping these dumps would help me fix the broken clone. Any one got any suggestions?

I would say you haven't configured the API properly,


If you say my other clone works perfectly,i would say i'm not there to see what you have done


You can't brick the vas head through firmware

Regards
Impactops

[gobftald]

You told that "You can't brick the vas head through firmware".
I really want to believe you. But what is your opinion about my experience.

I have an old cheap Chinese VAG5054 dongle, of course without AMB2300, till now used with the good old VAS-PC 19.01.01 SW. But a new (used) 2016 Audi came into my family so I gave it a try doing a big jump and install ODIS-S 7.2 on Windows 10. To my greatest surprise it worked. I had a more than one hour stable diagnostic session. OK it was a minimal use, reading, clearing DTCs, trying GFFs, monitoring some paramters, no any flashing. But it has been working flawlessly.

When I finished and closed my Win10 VirtualBox session, made some cleaning stuff, e.g. merging of its snapshots, then I tried to start ODIS again, it did not work, and never worked again. I tried the PDU-API test app and the PDUModuleConect always failed with the general PDU_ERR_FCT_FAILED error.

Both Bluetooth or USB connection was working well. VCI manager/configurator was able to detect the VCI with the appropriate communication channel, so the device drivers worked well, so when any of the connection was established the blue LED switched from flashing to continuous lighting. But when I pushed the appropriate button in the test app and send the PDUModuleConect command/function call to the VCI the blue LED was flashing one or more time, so dongle got the request, but no any response, and finally I got the PDU_ERR_FCT_FAILED messages.

I first though that the problem is about the VirtualBox stuff, when I merged the snapshot some driver were injured. Although this was not very likely, but maybe. So I fully reinstall the whole ODIS stuff from scratch, on a fresh and virigin Windows image, exactly the same as before. Did not help.
I tried thousands of other things but nothing helped, I lost the PDU_API communication with my dongle without any rational explanation.
I tried with many older ODIS versions, with Win7 32 and 64 bit combinations. I tried many older PDU-API versions/firmwares, e.g. the latest stable 1.20.020 for these clones, even I tried my very old VAS-PC 19.01.01 with version 1.10.48.
The test app always showed that none of the PDU API firmware versions could connect to the VCI. But once in the past even a very new one, the 1.20.042 could do it. But never again.

So, I'm quite clueless. It is unlikely that the dongle suddenly went bad at that time. The conspiracy theory that ODIS ruined VW's hated VAS5054 clone is also unlikely. Although I have no other dongle to test my attempts, but I'm pretty sure the problem is on VCI side. I was carefully cleaning and reinstalling many version of drivers and firmwares. VirtualBox helps to make tidy environments and configurations. Nothing helped.

But then what is the explanation for this behaviour?

If you have any experience how to reflash the dongle without a working PDU-API and the Test app, please let us know your thoughts.

[oops1vc]

Use minimon soft in boot mode.
MCU dump example is attached.
http://www.digital-kaos.co.uk/forums/attachment.php?attachmentid=290616&stc=1
If you still have a dump, please attach it again.
I change the processor in my adapter, I want to understand how to flash it, and how to flash it

[janhot]

Hello. Tell me, did you manage to sew on the XC161CJ controller and what is the result? I have a similar story with the adapter: "internal error: 700.2101".