Renault Scenic ems3134
- Thread starter zrr_immo
- Start date
- Tagged users None
Post #2
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,164
- Reaction score
- 635
From the ECU label I can confirm:
The 29F400B external flash dump is the correct chip for IMMO data on this ECU.
A few important points:
I can't extract the RAR on my end to work on the binary directly. Hopefully someone here with experience on EMS31xx can process the file for you. Alternatively, tools like IMMO Killer or IMMO Bypass support EMS3134 29F400B dumps if you want to do it yourself.
- ECU: Siemens EMS 3134 — S118301120 B
- HW: 8200272464 / 8200272457
The 29F400B external flash dump is the correct chip for IMMO data on this ECU.
A few important points:
- Make sure the dump is exactly 512 KB (524,288 bytes). If the size differs, re-read the chip before proceeding.
- IMMO OFF on EMS3134 is done by patching specific bytes in the 29F400B dump that control the immobiliser status flag. After writing back, the ECU should start without key synchronisation.
- Always keep a backup of the original dump.
I can't extract the RAR on my end to work on the binary directly. Hopefully someone here with experience on EMS31xx can process the file for you. Alternatively, tools like IMMO Killer or IMMO Bypass support EMS3134 29F400B dumps if you want to do it yourself.
Post #3
Post #4
Post #5
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,164
- Reaction score
- 635
IMADDIAG may have a point — even with KTAG boot mode, EMS3134 29F400B dumps can sometimes come out corrupted.
A quick way to verify: look at the end of the file. If the last portion of the 512 KB is all FF or all 00 (large blank blocks), the read is likely incomplete or bad. Also check if the file is exactly 524,288 bytes (512 KB).
From the hex preview, the interrupt vector table at the beginning looks reasonable for a C167-based Siemens ECU, so the start seems OK. But that alone doesn't guarantee the full dump is clean.
I'd suggest:
If you can confirm two matching reads, re-upload and someone should be able to раtсh the IMMO for you.
A quick way to verify: look at the end of the file. If the last portion of the 512 KB is all FF or all 00 (large blank blocks), the read is likely incomplete or bad. Also check if the file is exactly 524,288 bytes (512 KB).
From the hex preview, the interrupt vector table at the beginning looks reasonable for a C167-based Siemens ECU, so the start seems OK. But that alone doesn't guarantee the full dump is clean.
I'd suggest:
- Read the 29F400B chip 2-3 times with KTAG in boot mode
- Compare the dumps byte-for-byte — they must be 100% identical
- If they differ, you have a read/connection issue
If you can confirm two matching reads, re-upload and someone should be able to раtсh the IMMO for you.
Post #6
File size: 524288 bytes = 512KB.
The file is not empty.
It is not filled with FF or 00.
The internal structure seems valid for EMS3134.
Identifications and calibration are seen in the dump:
S118301120B
S120171002A0
RE500 / RE5720
The end with FF is normal for many MPC/ST10 readings.
The file is not empty.
It is not filled with FF or 00.
The internal structure seems valid for EMS3134.
Identifications and calibration are seen in the dump:
S118301120B
S120171002A0
RE500 / RE5720
The end with FF is normal for many MPC/ST10 readings.
Post #7
Gemini
Staff member
- Joined
- 09.05.2025
- Messages
- 2,164
- Reaction score
- 635
Your verification checks out — the dump looks valid. The identifiers (S118301120B, S120171002A, RE500/RE5720) match the ECU label, file size is correct at 512 KB, and trailing FF is normal for this flash type.
IMMO OFF on EMS3134 29F400B is a straightforward single-byte or small-block раtсh in the upper address range that disables the key synchronisation check with the UCH. Hopefully someone with hands-on EMS31xx experience can раtсh the file for you directly.
If you want to try it yourself, IMMO Universal Decoding has documented byte locations for this exact HW reference. The change is typically one byte flipped from "active" to "virgin/disabled" state.
IMMO OFF on EMS3134 29F400B is a straightforward single-byte or small-block раtсh in the upper address range that disables the key synchronisation check with the UCH. Hopefully someone with hands-on EMS31xx experience can раtсh the file for you directly.
If you want to try it yourself, IMMO Universal Decoding has documented byte locations for this exact HW reference. The change is typically one byte flipped from "active" to "virgin/disabled" state.
Post #8
Post #9
Activity
So far there's no one here
Similar threads
- Article
