|
Title: Strange 24c02 from M3.8X Post by: aef on January 02, 2016, 01:55:24 PM Hi,
i opened up a 06A906018D from a AGU to immo off this thing. Its a very old non-flashable version. Someone tuned it by resolder another chip. Now the funny thing is the eprom content looks strange and not like other M3.82, 3.83 or 5.92. I reflashed a eprom from the internet and checked channel 91 with vcds. While doing this i recognised the chip is from a Passat AEB engine. lol This will work because the engine is nearly the same but whats with the strange eprom? Were there file-to-eprom binding to copyprotect the tune back in these days? Thats what i thought when i saw it. Looks like the big tunerd did it with me7 tunes/eproms. I hope this thing will run with the file... Title: Re: Strange 24c02 from M3.8X Post by: eliotroyano on January 02, 2016, 07:07:51 PM Hi, i opened up a 06A906018D from a AGU to immo off this thing. Its a very old non-flashable version. Someone tuned it by resolder another chip. Now the funny thing is the eprom content looks strange and not like other M3.82, 3.83 or 5.92. I reflashed a eprom from the internet and checked channel 91 with vcds. While doing this i recognised the chip is from a Passat AEB engine. lol This will work because the engine is nearly the same but whats with the strange eprom? Were there file-to-eprom binding to copyprotect the tune back in these days? Thats what i thought when i saw it. Looks like the big tunerd did it with me7 tunes/eproms. I hope this thing will run with the file... I saw something like this in the past from some big tuners. About the new file you are using, 8D0907557T, I just recommend use a proper matched serial eeprom to avoid issues. Here I send you an original and off version of it. I hope it can help you. Title: Re: Strange 24c02 from M3.8X Post by: aef on January 03, 2016, 03:18:36 AM Thank you for your answer.
I used this file which matches the board/case. Will report later this week. Title: Re: Strange 24c02 from M3.8X Post by: aef on February 04, 2016, 01:07:44 PM Your file worked, thx!
|