1. Edit SVT_ist, and for applicable ECU(s) to be flashed, change Main, Sub, and Patch versions to 000 for the CAFD, BTLD, and SWFL entries (Do NOT Change HWEL.), e.g.:

id 00000792
mainVersion 000
subVersion 000
patchVersion 000

Then calculate SVT_soll, TAL, and then flash.

2. Flash with older psdzdata.

3. Old versions not maintained.

 

1. Edit SVT_ist, and for applicable ECU(s) to be flashed, change Main, Sub, and Patch versions to 000 for the CAFD, BTLD, and SWFL entries (Do NOT Change HWEL.), e.g.:

id 00000792
mainVersion 000
subVersion 000
patchVersion 000

Then calculate SVT_soll, TAL, and then flash.

2. Flash with older psdzdata.

3. Old versions not maintained.

Again Shawn, THANK YOU for all your contributions on so many forums!!! much appreciated!!!

I got a 2013 328xi sulev that had muffler delete, vrsf down pipe, and a hole in the piston... after rebuild and returning exhaust to stock, I updated iLevel... got 201101 code for manipulated dme.. by following your instruction, i was able to flash the dme and get rid of the code.... ISTA must not flash the btld file when programming unless needed....

 

thanks shawn for that info
i just got to try that editing SVT_ist out. do you edit it in esys or save it and edit it in wordpad

am i right i expand the "standard SVK" folder as i see the main sub and patch version there in DME as example

but when i right clicked 1 of them"version" and clicked edit in the standard SVT folder i didnt see anything happening or open to perform a edit

and would it be ok/safer to change just SWFL files and only flash them first to see if it fixes problem instead of doing the bootloader and i already tried recoding the ecu

 

In E-Sys.

Do all as I worte. Read and Edit SVT in SVT editor, and change all to 000 and save as svt_ist.

 

does this look right for DME

 

Yes.

 

thanks shawn, i flashed DME all went well thanks to your guidance,

If i want to do a full downgrade do i have to go through every ecu and change the main version sub version and patch version same as above or is there another way for a full downgrade.

 

You do if I-Step of ECU and PSdZData is the same.

 

Hi shawn
about reflashing/downgrading as above, what about ECU`s that have a FLSL file ?? do i change there main /sub / patch versions to 000 as well or leave them alone

and what about the HU NBT
IBAD ,ENTD and NAVD files do i change there main/sub/ patch version to 000 as well if reflashing/downgrading

thanks in advance

 

Hi shawn
about reflashing/downgrading as above, what about ECU`s that have a FLSL file ?? do i change there main /sub / patch versions to 000 as well or leave them alone

and what about the HU NBT
IBAD ,ENTD and NAVD files do i change there main/sub/ patch version to 000 as well if reflashing/downgrading

thanks in advance

Same thing, else they won't downgrade.

You can do the same for IBAD. Flash does nothing with ENTD or NAVD so nothing to do there.

 

HI
im getting a error in ESYS 3.40 when i used psdzdata that i got from ista-p 3.54.1 ilevel F010-14-11-502
error below.

i tried ESYS 3.30 and got no errors but havent used it with car yet ive only used 3.40 and it works good with my car so was hoping to stay using it and its easier to read on laptop

is ESYS 3.40 just to new for older psdzdata ??

 

Yes, it is.

 

Hi
im after getting another error message when i connected ESYS 3.30 up with car.
is this error becuse of corrupt psdzdata or do i need even a older version of ESYS.
attached screengrab

 

Update you E-Sys and PSdZData.

E-Sys Launcher PRO 2.8.2_Build_162b BFU Edition was released May 2019, which was a repackage of E-Sys Launcher PRO 2.8.1 initially released in Aug 2017 with an .est Token that expired on "2022-06-13", so now unuseable. While there were newer E-Sys Launcher PRO 3.7.0 and E-SysX applications previously available, neither application is currently available from their respective Developer's any longer, besides which both now also have very outdated CAFD Mapping. As such, the best option for support of all F/I/G Series cars with current up-to-date mapping is the new BimmerUtility application.

E-Sys Package:

E-Sys - Installation Instructions - v.18.pdf:

138.1 KB file on MEGA

mega.nz

E-Sys_Setup-3.40.2_64bit.exe:

95.77 MB file on MEGA

mega.nz

PSdZData:

v.4.46.31_PSdZData_Lite.rar

File on MEGA

mega.nz

- OR -

v.4.46.31_PSdZData_Full (MEGA):

File on MEGA

mega.nz

v.4.46.30_PSdZData_Full (Torrent):

File on MEGA

mega.nz

* NOTE: PSdZData Full Version is ONLY NEEDED FOR PROGRAMMING (FLASHING) ECU's and is NOT needed if only FDL or VO Coding.

BimmerUtility:

Home | BimmerUtility

www.bimmerutility.com

* NOTE: For FDL Coding, E-Sys requires a 3rd Party “Mapping” application such as BimmerUtility as it Provides CAFD Mapping. Back in Nov 2014, BMW AG made changes to PSdZData beginning with 54.2 PSdZData where they removed (trimmed) all descriptive text from CAFD and FAFP files, making FDL Coding of ECU's difficult, as the FDL Codes can no longer be easily located. The "Mapping" application dynamically maps the trimmed data back into CAFD file making FDL Coding possible. BimmerUtility is NOT needed for VO (FA) Coding nor ECU Programming (Flashing) as these can be performed with E-Sys direct.

 

Shawn
i have those already ,the TALline questions were from using ESYS 3.40.2 and latest psdzdata for my car F010-23-11-530


im also trying to flash back to factory i level F010_14_11_502
and after much searching i found the psdzdata in ISTA-P 3.54.1 but errors now,
tried 3.40, 3.34, which were coming up with errors just running them not even connected to car but 3.30 ran without errors but after coming up with that error now, (c028)

could it have been that i loaded a edited svt_ist that i created in esys3.40 into 3.30

 

I have no idea what you are doing nor why SVT would be edited. If you want to flash car back to F010_14_11_502 you need to use old E-Sys, like 3.27.1, and psdzdata full with F010_14_11_502 target. Unless you have retrofits, you should use original FA and SVT for flashing.

 

SVT edited as per post 2 here
would you have a link for E-sys 3.27.1

 

Ok, that SVT Edit is fine. It did not change ECU list, just firmware revisons.

72.51 MB file on MEGA

mega.nz

 

thank you for that

 

Ok, good luck with it.

 

Hi shawn im getting same kind of error with Esys-3.27.1 , do you have another older version maybe 3.24.3 or some stable version inbetween.
been searching for ages looking for a copy
thanks.

 

PM sent.

Maybe your psdzdata is the problem, not E-Sys.

 

OK so i went ahead and flashed same i level as is on car using latest psdzdata 4.46.31 and Esys 3.40.2
after editing all main sub and patch in SVT_ist . ,
All ECU`S`flashed ok EXCEPT NBT.

im another 1 with a STUCK NBT in blue screen, Btld i know got as far as 98% and it looks to be flashed ie black
it seems the SWFL`s are corrupt or didnt flash
and i had just read about this issue before i flashed it with HTTP and UDS protocols

Do you think i should try the ReFlash Btld in UDS and the others in HTTP or ?

how do i edit TAL to flash needed SWFLs one at a time via HTTP as i read solved this

 

OK so i went ahead and flashed same i level as is on car using latest psdzdata 4.46.31 and Esys 3.40.2
after editing all main sub and patch in SVT_ist . ,
All ECU`S`flashed ok EXCEPT NBT.

im another 1 with a STUCK NBT in blue screen, Btld i know got as far as 98% and it looks to be flashed ie black
it seems the SWFL`s are corrupt or didnt flash
and i had just read about this issue before i flashed it with HTTP and UDS protocols

Do you think i should try the ReFlash Btld in UDS and the others in HTTP or ?

how do i edit TAL to flash needed SWFLs one at a time via HTTP as i read solved this

I;d flash BTLD with UDS, and then see if the SWFL also flash with HTTP, else change them to UDS also.