A 2002 Mercedes-Benz S500 (W220) with All Keys Lost was successfully programmed using Xhorse Multi-Prog together with the VVDI Key Tool Plus (via Xhorse Cloud). Multiple other IR methods failed (VVDI Key Tool Plus standalone, Autel IM608, and CGDI MB via IR), but the combined bench/workflow using K-Line EEPROM read + cloud decode produced a working key.
Vehicle & System Details:
Make / Model: Mercedes-Benz S500 (W220) — 2002
Condition: All Keys Lost
EIS/EZS Type: W215 / W220 (K-Line)
Chipset: Motorola (4J74Y)
Tools used (successful flow): Xhorse Multi-Prog + VVDI Key Tool Plus
Tools attempted (IR — failed): VVDI Key Tool Plus (IR), Autel IM608 (IR), CGDI MB (IR)
Problem Overview:
This W220 S500 had no working keys and IR learning attempts with several major tools were unsuccessful. For many W220/W215 EIS units, IR learning can fail due to EIS condition, security counters, or model-specific protection. A bench/EEPROM method was chosen to reliably recover the required immobilizer data.
Why this method worked?
IR learning failed — typical when the EIS has protection or the IR learning protocol is not supported or fails due to EIS state.
EEPROM read + decode gets direct access to the immobilizer data on the module rather than relying on IR protocols, which is more reliable for “All Keys Lost” scenarios on older Mercedes EIS types (W215/W220 K-Line).
Xhorse Multi-Prog handles robust EEPROM reads; VVDI Key Tool Plus has a cloud decode + key writing pipeline that simplifies creating a working key from the dump.
For this 2002 Mercedes S500 (W220) with All Keys Lost, the bench method — reading EEPROM1 with VVDI Multi-Prog, transferring to Xhore VVDI Key Tool Plus via Xhorse Cloud, decoding, preparing, and writing the key file — produced a successful result when IR methods failed. This workflow is a reliable alternative for similar W215/W220 K-Line EIS units where IR learning is not possible.
Skype: xhorsevvdi.com
Whatsapp: https://wa.me/8613983756354
Whatsapp: 
Skype: