Title: 4F1 907 559 A Simos 6.2 Immobilizer Defeat? Post by: dbreeze on June 07, 2016, 07:38:28 PM I've tried searching but can't find any info on whether an immobilizer defeat exists for VAG Simos 6.22. Anyone have any info to point me in the right direction? ECU Eeprom is attached
Thanks! Title: Re: 4F1 907 559 A Simos 6.2 Immobilizer Defeat? Post by: k0mpresd on June 07, 2016, 08:11:39 PM no off, only clone.
Title: Re: 4F1 907 559 A Simos 6.2 Immobilizer Defeat? Post by: dbreeze on June 07, 2016, 08:21:38 PM no off, only clone. Thanks!Title: Re: 4F1 907 559 A Simos 6.2 Immobilizer Defeat? Post by: dbreeze on June 08, 2016, 08:27:34 AM @k0mpressed: Would I be able to just swap the eeprom chips between the original ECU and a replacement one or should I do a full BDM read from the original and write it to the replacement?
Title: Re: 4F1 907 559 A Simos 6.2 Immobilizer Defeat? Post by: k0mpresd on June 08, 2016, 10:14:29 AM i always do a full bdm clone.
Title: Re: 4F1 907 559 A Simos 6.2 Immobilizer Defeat? Post by: 1HGUY on June 14, 2016, 09:18:57 PM i always do a full bdm clone. I did today 2 SIMOS 6.22 ECUs by BDM-100 The trouble was that EEPROM chip M95320W was not reading correctly, even though no indication of trouble and/or errors. I had manually dumped both chips for comparison purposes. Secondly, BDM-100 does not recognize this ECU and you're limited by only FULL read/write. Any comments, suggestions, remedies will be much appreciated.Title: Re: 4F1 907 559 A Simos 6.2 Immobilizer Defeat? Post by: IamwhoIam on June 15, 2016, 06:18:39 AM this BDM-100 I presume isn't the official EVC version?
Title: Re: 4F1 907 559 A Simos 6.2 Immobilizer Defeat? Post by: k0mpresd on June 15, 2016, 07:55:13 AM i have had no issues with even clone bdm100 on these ecus.
Title: Re: 4F1 907 559 A Simos 6.2 Immobilizer Defeat? Post by: Hollywood on February 08, 2017, 12:18:24 PM i have had no issues with even clone bdm100 on these ecus. Are you using bdm100 clone through cracked winols? or another software? I can't find 6.22 compatibility.Thanks. |