FGTech Galletto 2 V52 fail ME7.5

by **IbizaNH** » Fri Oct 17, 2014 11:44 pm

Hi guys i need some advice, i have an VW Golf GTI 1.8T to read but FGtech fails at 80% it says "Error seed Key", i'm doing the read on OBD port according to Nefmoto should do the trick, any ideas on the best way to read and write this car?

Should i try BDM or BootMode instead?

Thank's

by **sparco** » Sat Oct 18, 2014 10:01 am

On vag ME7.5 its advised to use boot mode yes.

by **IbizaNH** » Sat Oct 18, 2014 4:07 pm

Thanks, I'll do that.

by **audipete** » Fri Nov 28, 2014 2:19 pm

Hi, with Nefmoto I just use a normal vag lead works fine is the car pre 2001? I know on my old audi s4 1999, I had to lift the chip and program the 44 pin psop with my Willem Programmer. And make sure battery charger is on the car when programming through obd to keep the voltage up.

by **tunemyecu** » Wed Jul 22, 2015 12:08 am

sparco wrote:On vag ME7.5 its advised to use boot mode yes.

Hi, My v54 read 100% me7.5 ecu but does nothing after the read and I see no file

do you know whats going on?

by **ecuedit** » Wed Jul 22, 2015 12:00 pm

the most reliable method for me7.5 is to desolder the flash, and programm it in programmer.

by **tunemyecu** » Wed Jul 22, 2015 3:16 pm

wow, I would have to get a friend to do that

I thought the code is different if you read the chip directly though. I did not think it was the same

by **enemigo** » Thu Jul 23, 2015 12:40 pm

ecuedit wrote:the most reliable method for me7.5 is to desolder the flash, and programm it in programmer.

you dont need any desoldering. Boot mode is the best for these ecus.

by **ecuedit** » Thu Jul 23, 2015 11:23 pm

enemigo wrote:
ecuedit wrote:the most reliable method for me7.5 is to desolder the flash, and programm it in programmer.

you dont need any desoldering. Boot mode is the best for these ecus.

enemigo read again what i wrote. I did not wrote what is best but what is most reliable.

Post is about reliability. When you have file prepared and checksum calculated - chip programmer never fails as it does not
calculate checksum. So you write what you have, chip programmer does not change file / checksum parts, it simply writes what you have, than you are sure what is on the ECU - exactly what you did in file, no messing around with flasher checksum calculations and
automatical file changing by it.

Once when you change lots of parts of the binary (parts that not lots of people know how they work - even if they have damos or function descriptions...)

in me7.5 you notice that programmer can not handle all checksum blocks and car wont start. There are parts of the binary that are not covered with checksum calculation by almost any programmer. Most of maps that are not covered by flasher checksum modules are onedimensional and not known by some softwares that are automaticaly finding maps...like ecm and similar.

So for deep and PRO work, you can face a problem with programmer checksum calculations as it does not cover that areas.