|
Title: MK5 2.5 ECU immo defeat. Post by: LVPainterZ on September 16, 2016, 02:54:43 PM Hey Guys,
Im using a 07K906032AQ ECU for a 2.5 swap into a MK1 Audi TT I've pulled the bin file and modified the immo hex and now it states that the immo is basically the same as a new ECU in VCDS The IMMO chip is 95160 and I had to use CS pin 6.3 to get it to pull the file in argdubs tool. I have read a lot on this topic but i am still having issues with the checksums. What does it take to properly check the checksums as Turboat"s tool will not do it as the bin file is 2kb I will post the fees but i don't want it to be someone does it for me. Anyone willing to help? Title: Re: MK5 2.5 ECU immo defeat. Post by: LVPainterZ on September 16, 2016, 02:57:57 PM Here are the files
Title: Re: MK5 2.5 ECU immo defeat. Post by: dbreeze on September 16, 2016, 08:29:56 PM Follow this and you should be all set.
Title: Re: MK5 2.5 ECU immo defeat. Post by: LVPainterZ on September 17, 2016, 01:06:14 AM So either vag commander worked and modified it a couple times or I'm doing the checksums wrong.
how can i check the checksums as me7sum and me7check has an error with the file? Vag com adaptation says 0 on the immo section not 1 Any ideas? Title: Re: MK5 2.5 ECU immo defeat. Post by: dbreeze on September 17, 2016, 07:38:47 AM So either vag commander worked and modified it a couple times or I'm doing the checksums wrong. how can i check the checksums as me7sum and me7check has an error with the file? Vag com adaptation says 0 on the immo section not 1 Any ideas? me7sum and me7check are for Flash .bins only, not the Eeprom. The only checksums that would need to be fixed from a normal immo defeat would be the two pages at 0x010 and 0x020. So change 0x012 and 0x022 (should originally be 01) to 02 and subtract 1 byte from the checksum (last two bytes of 0x010 and 0x020). |