Skip to main content

Esys Fix 2014 M5 Crash after ISTA/P update(like flash module)

I have a 2014 M5 and flashed the car, the junction box and a bunch of other modules too, with ISTA/P 2.52.4 and an BMW ICOM clone A2 from www.obd2tool.com. It was the fourth or fifth car that I had flashed with this equipment.
It seemed that ISTA/P crashed during flashing. ISTA/P is now not able to read the VO from VCM (also E-sys) and if you load the stored VO and read out the ECU with E-Sys (read VCM isn’t possible) you see 0 ECUs.
It looks like that all ECUs are unavailable and in programming mode. He can open and close the car but nothing more.
Connection via E-Sys is only possible by Gateway/Url (OBD Ethernet cable) or ICOM IP. ZGW is of course not available.
What I did to fix it is, I used Esys to fix the BMW Diagnostic Tool.
I need to use the Psdzdata that was on the module before it was flashed.
Run these step like flashing a module
Here are the basic steps:
Go to Comfort Mode => TAL-Calculating
– Read and Save FA
– Activate FA
– Read and Save SVT Actual as SVT_ist
– Create an SVT Target
Under KIS/SVT Target Calculation Strategy, select Complete Flash
Select I-Step (shipm.) to match your original I-Level as read and shown in VCM I-Step (Shipment)
I-Step (target.) will be unselectable as it is fixed based on current PSdZData I-Level
Do a KIS/SVT Target Calculation and Save as SVT_soll
– Do a TAL Calculation and Save as SVT_tal
Go to Expert Mode => TAL-Processing
Load TAL (SVT_tal)
Load SVT Target (SVT_soll)
Select “Read FA” button.
Check radio button for “read VIN out of FA”
On ECU Tab, uncheck let top box in column “All” (All checked boxes should toggle to unchecked)
On ID Base Row for Modules, make check boxes in blFlash, swDeploy, cdDeploy, and ibaDeploy columns.
Press Check software availability
Press Start and it will proceed with processing TAL to flash
blFlash, swDeploy, cdDeploy, and ibaDeploy uncheck all boxes but these in the modules it finds.
Then Esys finds the modules its strange mine were half on 53.5 and half on 53.2 in some strange state.
after doing this I was able to restore them back to a working state before the upgrade. And everything was normal again
Mine looked like the attached picture. It was pretty bad. I really don’t trust Ista/p on a BMW ICOM A2 clone doesn’t seem to cause more issue then good during programming on these new model cars. ICOM clone from reliable sellers sometimes can be nice also.

Comments

Popular posts from this blog

How to Solve VW Amarok Caddy 2018+ Remote Not Working After Programming

Here comes the general problem of VW Amarok Caddy etc. 2018+ UDS protocol vehicles: 2019 VW Caddy. I spent a few hours programming the Xhorse key using VVDI2 . Also tried TDB1000. Remote function could not be obtained. Every time the programming failed, the original remote stopped working until I scanned and cleared errors. I expected it to work when the transponder was added (Megamos AES). I can’t access remote learning with any of my tools, nor did vvdi2 let me program the remote. I was wondering if anyone could confirm remote learning with transponders or how to learn it if not. Solution: It is not possible for BH remote controls after 2018 at the latest. You will not get any communication with the central locking remote control customization. You need a dealer key 100% and then learn from ODIS. There is no after-market solution, VAG blocked the remote channel on UDS vehicles 2018+. Had the exact same issues with new caddies. So merchant key and Odis ATM since the c...

Lonsdor K518 Program Mini Cooper CAS3+ Remote Smart Key by OBD

Here’s the guide to program remote smart keys on a  Mini Cooper CAS3+ immobilizer  with Lonsdor K518  obd key programmer via OBD. Lonsdor K518ISE Key Programmer  host with vehicle via OBD socket Turn on device Select Immobilizer function on main menu Select BMW->Select from type->CAS2/CAS3 series->Program Key Will start to make dealer key Insert key into card slot and press on Start button once Lonsdor K518 ISE key programmer will display CAS part number and type. Reading RAM… wait for 1 minute Remove key from ignition switch. For smart eym take it outside car. Click OK to continue Safety checking Reading key inforamtion Select a key position to program If car key has been programmed but failed, please unlock the key and restore CAS data first Press OK to continue Select Remote Key Pull Lonsdor K518 key on  OBD2 slot to the right and insert the key to program (to identify if the key is legal and to pre-p...

How Does a Car Code Reader Work?

Computer controls started to show up on cars in the late 1970s and early 1980s, and these systems rapidly grew in complexity. Even very early computer controls included basic “on board diagnostic” functionality, and these early, OEM-specific systems are collectively referred to as OBD-I. In 1995, for the 1996 model year, automakers around the world started transitioning toward the universal OBD-II standard, which has been in use ever since. Both OBD-I and OBD-II systems work in essentially the same way, in that they monitor a variety of sensor inputs and outputs. If the system determines that anything is out of spec, it sets a “ Auto Scanner Tools ” that can be used in diagnostic procedures. Each code corresponds to a specific fault, and there are also different types of codes (i.e. hard, soft) that represent both ongoing and intermittent problems. When a trouble code is set, a special indicator on the dashboard typically lights up. This is the “malfunction indicator lamp” and it essen...