Stage 1 tune detection help

Azzy said:

bmw e91lci 318d N47D20C 105kw 141hp
EDC17CP02

Click to expand...

There are a few issues with your file that need to be addressed before we can help properly.

File Analysis:

The file you uploaded (318d1037396567ORI.bin) is 1.50 MB (1,572,864 bytes), but the entire beginning of the file (at least the first 0x2000+ bytes) is filled with 0xFF. The estimated entropy is 0.00 bits/byte, which is extremely low — this strongly suggests the file is either:

• A partial read (only external flash / calibration area, with the rest padded as 0xFF)
• A corrupted or incomplete dump
• Read with a tool that didn't capture the full internal flash content

What I can extract from the strings:

• Bosch number: 1037396567
• SW/HW identifier: 0089SY0A3R5BKB131
• ECU type: EDC17C06 (note: the string says EDC17_C06, not EDC17CP02 — please double-check your ECU label)
• Variant: V3R5
• DTC init string: "(SWB init)" present — suggests some calibration data is in the file

Concerns:

1. EDC17C06 vs EDC17CP02 — the file header identifies as EDC17C06. The E91 LCI 318d N47D20C 105kW typically uses EDC17C06 or EDC17CP02 depending on production date. Can you confirm the exact part number from the ECU label (Bosch HW number)?
2. File size — a full EDC17C06 read via BDM/boot should be 2 MB (2,097,152 bytes) for the full flash, or sometimes 1.5 MB if only the external flash was read. With all 0xFF at the start, this looks like an external flash only read (e.g., via OBD with KTAG/KessV2 or similar).
3. 0.00 entropy — the preview is entirely 0xFF. The actual calibration data must be further into the file, but the tool metadata suggests it may be very sparse.

What I need from you to help with Stage 1 tune detection:

• What tool was used to read? (KTAG, KessV2, CMD, Autotuner, BDM100, etc.)
• Read mode? (OBD, Boot/Bench, BDM?)
• Full ECU label — HW number, SW number, Bosch part number from the physical sticker on the ECU
• What exactly do you want to detect? — Are you trying to check if this "ORI" file is actually original, or are you comparing it against a suspected tuned file?

If you're trying to verify whether this file is truly stock or has already been modified, I would need either:

• A second file to compare against (the suspected tuned version), or
• Confirmation of the exact SW version so I can compare known stock calibration values (IQ maps, rail pressure, torque limiters, etc.)

Please provide these details and I can help you further.

then this is the one

Azzy said:

then this is the one

Click to expand...

I need more context to help you. Your message isn't clear — "this is the one" what exactly?

Please clarify:

1. Is this the file you want to check if it's stock or already tuned?
2. Or is this the tuned file and you have another ORI to compare against?

Also, my previous questions still stand — I need this info to give you a proper analysis:

• What tool was used to read? (KTAG, KessV2, CMD, Autotuner, etc.)
• Read mode? (OBD, Boot/Bench, BDM?)
• Confirm ECU type — the file identifies as EDC17C06, not EDC17CP02 as you stated. Which one is on the ECU label?
• What exactly do you want to detect? — Are you trying to verify if this "ORI" is genuinely original, or are you looking for specific map changes?

Without a second file to compare or confirmed stock SW reference data, I can't tell you if this has been modified. If you have a second file (tuned or another backup), upload it and I can do a binary comparison.

this is the better file i think

Azzy said:

this is the better file i think

Click to expand...

I can see you uploaded edc.rar (76.55 KB), but unfortunately I cannot extract RAR archives — the server doesn't support it.

Please re-upload the file in one of these formats:

• .bin / .ori / .mоd (raw binary)
• .zip (if you need to compress it)

Also, 76.55 KB is extremely small for an EDC17C06 dump. A typical read should be:

• OBD read (maps only): ~256 KB – 512 KB
• External flash (P-flash): ~1.5 MB
• Full BDM/Boot read: ~2 MB

76 KB suggests either:

• Only a small calibration zone was exported
• The file is heavily compressed inside the RAR
• It's a partial export from tuning software (e.g., WinOLS project, not a full dump)

Please:

1. Re-upload as .zip or raw .bin
2. Confirm what tool was used to read
3. Confirm if this is supposed to be the ORI or the suspected tuned file
4. Tell me what you're trying to detect — is the goal to check if your car has already been tuned (Stage 1)?

bmw e91lci 318d N47D20C 105kw 141hp

Azzy said:

bmw e91lci 318d N47D20C 105kw 141hp

Click to expand...

Thanks for confirming the vehicle:

BMW E91 LCI 318d — N47D20C — 105kW / 141HP

That info is noted, but I still need the following to actually help you:

1. The file
Re-upload the file as .bin or .zip — I cannot open .rar files. The first file you uploaded (318d1037396567ORI.bin) was mostly 0xFF / empty data, so I need a proper dump.

2. Technical details

• ECU type — The first file identified as EDC17C06, not EDC17CP02. Can you confirm from the ECU label sticker?
• Bosch HW/SW number — from the ECU label (e.g., 0281018294, SW 8517706, etc.)
• Read tool — KTAG, KessV2, CMD, Autotuner, other?
• Read mode — OBD, Boot/Bench, or BDM?

3. What are you trying to do?

• Check if your current file is stock or already tuned?
• Compare two files (ORI vs suspected tune)?
• Something else?

Without a readable file and these details, I cannot perform any analysis. Please re-upload as .zip or raw .bin and provide the info above.

Azzy said:

bmw e91lci 318d N47D20C 105kw 141hp

Click to expand...

Here you go, racer. Make sure your head doesn’t fly off. Your firmware dumps are a mess — who knows what you’re using to read them.

Bin said:

Here you go, racer. Make sure your head doesn’t fly off. Your firmware dumps are a mess — who knows what you’re using to read them.

Click to expand...

Now we're getting somewhere! Thanks for the WinOLS project.

File Analysis

From the filename and WinOLS screenshot, this is clear:

Vehicle: BMW 3-Series 2009 318d 6AT
ECU: EDC17C06 (confirmed — not CP02)
Bosch SW: 396567
File type: WinOLS project with ORI + mоd

Modifications listed in the filename:

• Stage 2 — performance tune (IQ, rail pressure, boost, torque limiters)
• DPF off — diesel particulate filter removed/disabled
• EGR off — exhaust gas recirculation disabled
• TQM — torque monitoring / torque limiter modifications
• VMAX — speed limiter removed

What the WinOLS screenshot shows

The top window is the ORI (original) — entirely 0xFF in the header area, which matches your first upload. This confirms the original was read via OBD (slave tool like KessV2/KTAG), where the boot/header area is padded with 0xFF.

The bottom window is the mоd (tuned file) — you can clearly see data at offsets 0x000000–0x000090+ with significant changes (highlighted in red/yellow). The differences panel on the right shows >20,000 differences, which is consistent with a Stage 2 + DPF/EGR/TQM/VMAX modification.

Your question — Stage 1 tune detection

But wait — your thread title says "Stage 1 tune detection help", yet this file is labeled Stage 2 + DPF + EGR off. So what exactly do you need?

1. Are you trying to detect if your car currently has a Stage 1 tune and this Stage 2 file is something you want to flash?
2. Or do you want to verify the ORI inside this project is truly stock before flashing the mоd?
3. Or do you want to downgrade from Stage 2 back to stock and need to verify the ORI is clean?

The ORI in this project starts with 0xFF padding (OBD read), so it cannot be verified against Bosch/BMW factory checksums in the boot area — but the calibration zone can still be compared against known stock values for SW 396567.

Let me know what your actual goal is and I'll dig into the maps.

Bin said:

Here you go, racer. Make sure your head doesn’t fly off. Your firmware dumps are a mess — who knows what you’re using to read them.

Click to expand...

im so so so gratefull man, thanks a lot!!!!!!!!!!!!!!!!!!!!! im gonna test it right now, im using kess v2 to read

Bin said:

Here you go, racer. Make sure your head doesn’t fly off. Your firmware dumps are a mess — who knows what you’re using to read them.

Click to expand...

just tested it, bro, i got sideways just in the first corner, its insane,very good, just a question, in the ccc it shows 3 green OK checks, but on the bort computer it shows check engine, but after sometime it fixed itself, thanks a lot, i would want to learn to do that myself, but its hard to understand
thanks a lot again!
Racers will rise again

Azzy said:

just tested it, bro, i got sideways just in the first corner, its insane,very good, just a question, in the ccc it shows 3 green OK checks, but on the bort computer it shows check engine, but after sometime it fixed itself, thanks a lot, i would want to learn to do that myself, but its hard to understand
thanks a lot again!
Racers will rise again

Click to expand...

I didn’t develop this mоd from scratch specifically for you — I simply used a ready-made file from a well-known tuning company. Before that, I checked the file you attached in your message, and then manually verified the mоd file myself to make sure it would fit your setup perfectly.

It only took me about five minutes, so don’t worry — everything is completely fine.

As for developing a tune entirely from scratch, hardly anyone does that anymore. Building a mоd from zero takes a huge amount of time and endless map corrections. The better approach is to have a solid database of ready-made tunes. A customer comes in, you read the original file, and if there isn’t already a tune for that exact software number in your database, you take the closest matching one and transfer the calibration section in something like WinOLS — assuming the addresses match. Then you calculate the checksum and you’re good to go.

Bin said:

I didn’t develop this mоd from scratch specifically for you — I simply used a ready-made file from a well-known tuning company. Before that, I checked the file you attached in your message, and then manually verified the mоd file myself to make sure it would fit your setup perfectly.

It only took me about five minutes, so don’t worry — everything is completely fine.

As for developing a tune entirely from scratch, hardly anyone does that anymore. Building a mоd from zero takes a huge amount of time and endless map corrections. The better approach is to have a solid database of ready-made tunes. A customer comes in, you read the original file, and if there isn’t already a tune for that exact software number in your database, you take the closest matching one and transfer the calibration section in something like WinOLS — assuming the addresses match. Then you calculate the checksum and you’re good to go.

Click to expand...

well it seems quite simple lol, can i ask for a stage 1 dpf off? because i drove today to school and i think my clutch started slipping