|
Title: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: turboat on May 29, 2014, 09:45:05 AM UPDATE:
Eeepromtool is now hosted on github. The most recent release will always be located in: https://github.com/turboat/eepromtool/releases/ Source code is in: https://github.com/turboat/eepromtool Pull requests are welcome :) Eepromtool is a command line tool, either run using 'python eepromtool_04.py' or 'eepromtool_04.exe'. If it just flashes up and disappears, this is because it is a command line tool. If you dont know what a command line tool is, you probably shouldnt be trying to edit your ECU. Displaying Information To simply display the info in a bin called INFILE, use: eepromtool_04.exe INFILE For example with an ecu eeprom: Code: eepromtool_04.exe ecu.bin With a cluster eeprom: Code: eepromtool_04.exe cluster.bin Immo On/Off To set immo status, you must specify input file, output file and desired immo status. Checksums will be corrected automatically unless you specify --nofixcs. For example: Code: eepromtool_04.exe --in ecu.bin --immo off --out ecu_off.bin Title: Re: 95040Tool - Please test Post by: turboat on May 29, 2014, 09:49:55 AM To change immo or VIN:
$ ./95040tool.exe --in Immo\ bin\ with\ SKC\ 05557.bin --immo off --out immoff.bin Setting Immobiliser: Off - Immobiliser Off - Setting backup pages - Correcting checksums Writing eeprom bin to: immoff.bin - Write Successful $ ./95040tool.exe --in immoff.bin --vin YOURVINGOESHERE00 --out immoffvin.bin Setting VIN to YOURVINGOESHERE00 - Setting backup pages - Correcting checksums Writing eeprom bin to: immoffvin.bin - Write Successful $ ./95040tool.exe immoffvin.bin EEPROM Status: - VIN: YOURVINGOESHERE00 - SKC: 05557 - Immobiliser: Off - Checksum: OK - Size: 512bytes - Cluster Code: 69 D9 38 E6 D3 B2 - P0601 DTC: not set - Immo ID: UX6Z0D0454942 Title: Re: 95040Tool - Please test Post by: mx450 on June 12, 2014, 08:07:40 AM It worked.
Just wonder what is that backup page for. I made some test Three attachments uploaded in the post. 1. "95040_AWU_1.8T_06A906032GQ.ori.bin" the original file. It works fine for sure with 06A906032GQ software, but it would get DTC 18048 with 06A906032HH software. 2. "95040_AWU_1.8T_06A906032GQ.modified.EEPROM_checksume_error_before_fixing.bin" Then i made some test to remove and modify some part of it. (between 0x01C0 to 0x01FF) And after booting on table, with 06A906032GQ software, it still has no DTC generated. bit, with 06A906032HH software, i got DTC "18048/P1640/005696 - Internal Control Module: EEPROM Error" 3. "95040_AWU_1.8T_06A906032GQ.modified.EEPROM_checksume_error_after_fixing.bin" i used this command "95040tool.exe --in modified_file.bin --fixcs --out corrected_modified_file.bin" with 06A906032GQ software, it still has no DTC generated. with 06A906032HH software, the final file passed checksum checking, that DTC 18048 just gone!!!!!!!!!!!!!!!!!!! :) :) :) --------------------------------------------- I noticed that this tool change two bytes of 0x014E from my manual modified file to fix the correction. And i saw it says 'setting backup pages'. just wonder a. what is that backup page is? b. And i even change nothing of those byte of 0x0140 to 0x014D, why the checksum of 0x014E needs to be corrected? thanks for your good tool, plz light me up... --------------------------------------------- PS. I found that the 95040 EEPROM checksum checking routine are different between 06A906032GQ and 06A906032HH software. If i use 06A906032GQ software, the manual modified file wont get any DTC, and as you may see, there is no VIN and no Immo id of this 95040 original data. But using 06A906032HH software with same EEPROM data, i got the EEPROM error DTC, after i using this tool to make new file ( to correct checksum or backup page?), the 06A906032HH software is happy to pass the checksum checking. I don't have car to try if this EEPROM ok to bass IMMO as IMMO function is still on. The owner of the car with this EEPROM lives 300 KM away from me. I can try it few weeks later. Title: Re: 95040Tool - Please test Post by: stranger_in_distress on June 15, 2014, 08:21:10 AM I used this tool to fix the checksums on two modified ECU dumps, from 06A906032HN and 06A906032HJ. Worked like a charm.
Noticed one problem when running "--status" on the dump files from the above ECU's, IMMO IDs are missing the first charcter. For example: -instead of the "AUZ5Z..." it's showing "UZ5Z...", for the 06A906032HJ dump(Audi A3 AUM) -instead of the "SKZ7Z..." it's showing "KZ7Z...", for the 06A906032HN dump(Skoda Octavia AUQ) The first character of the immo id can be found, in the dump file, right after the the VIN end. Title: Re: 95040Tool - Please test Post by: turboat on June 20, 2014, 04:12:26 AM Thanks for the testing folks, I'll take a look at those bugs over the next couple of days, RL and boost piping got in the way :)
Title: Re: 95040Tool - Please test Post by: mikeb52 on July 06, 2014, 02:48:24 PM I tried your tool tonight after reloading drivers and getting my cable working.
After saving the bin file from my ecu and copying it into the same folder as your tool, when I ran the input file I received, EEPROM status: Vin:XXXXXXXXX SKC: 065535 Immo : on Checksum: invalid checksum Size:512bytes Cluster code 00 00 00 00 00 00 P0601 DTC: not set Immo ID: XXXXXXXXXXX Couldn't perform any other seps as I would get messages unrecognized arguments: bin\ with\ skc\ 95040.bin Not sure if my bin save is bad. Title: Re: 95040Tool - Please test Post by: turboat on July 06, 2014, 03:38:00 PM Looks like you've got an immo2 bin, I realised last week this doesn't work with those, will update in the next few days.
Title: Re: 95040Tool - Please test Post by: Nottingham on July 12, 2014, 01:02:29 AM Nice work.
In case you want to add: Bytes 1E9h & 1F9h = Flash Programming Counter (Succesfull) Bytes 1EAh & 1FAh = Flash Programming Counter (Attempts) Title: Re: 95040Tool - Please test Post by: turboat on July 12, 2014, 01:30:39 AM Cheers :) I'll add them when I'm tweaking it next. Ive also added basic parsing of cluster bins, and the ability to pair a cluster bin with an ecu eeprom bin. Not had time to test properly, when I have a quiet afternoon I'll upload a new version :)
Title: Re: 95040Tool - Please test Post by: vampirelo on August 14, 2014, 05:22:14 AM I have immo II ecu dump and tool give follows:
EEPROM Status: - VIN: XXXXXXXXXXXXXXXXX - SKC: 065535 - Immobiliser: On - Checksum: Invalid Checksum - Size: 512bytes - Cluster Code: 00 00 00 00 00 00 - P0601 DTC: not set - Immo ID: XXXXXXXXXXXXX Waiting for new version of tool. :) Title: Re: 95040Tool - Please test Post by: ddillenger on August 14, 2014, 09:23:20 AM I have immo II ecu dump and tool give follows: EEPROM Status: - VIN: XXXXXXXXXXXXXXXXX - SKC: 065535 - Immobiliser: On - Checksum: Invalid Checksum - Size: 512bytes - Cluster Code: 00 00 00 00 00 00 - P0601 DTC: not set - Immo ID: XXXXXXXXXXXXX Waiting for new version of tool. :) Why? Immo-2 has FF FF in the login location, and the vin is XXXXXXXXXXXXX. So, it's returning proper info. Title: Re: 95040Tool - Please test Post by: vampirelo on August 15, 2014, 04:46:43 AM Why? Immo-2 has FF FF in the login location, and the vin is XXXXXXXXXXXXX. I am about line:So, it's returning proper info. - Checksum: Invalid Checksum Checksum is 100% correct due to just downloaded from ECU. Original dump from Seat Ibiza Cupra R ECU is attached. Question: Can I use 95040Tool for attached dump to make immo-off? One more detail: I had reviewed dump and found that pages 1C and 1D chechsums (addresses 1CE-1CF and 1DE-1DF) are NOT ok. Seems that for this pages in immo II ECU in indicated addresses are not checksums. Title: Re: 95040Tool - Please test Post by: automan001 on September 02, 2014, 12:13:38 AM Why does it show cluster code as 6 bytes while it should have been 7 bytes?
Title: Re: 95040Tool - Please test Post by: turboat on September 02, 2014, 06:44:35 AM Pinkwear problem, I'll fix that ASAP.
Title: Re: 95040Tool - Please test Post by: turboat on September 03, 2014, 06:24:03 AM Prototype support for cluster bins and pairing cluster bin with ecu eeprom - I planned to do a load more testing and add immo2 support and bin cloning, but have no time and this seems to be coming up a lot, so here is an interim release.
New Features: - Basic parsing for cluster bins - Pair a cluster bin with an eeprom bin - print softcoding id from ecu bins - now reads/writes the complete cluster code, not just the first 6 bytes (duh :'( ) - fixed some bugs (corrected immoid and VIN printing, tweaked VIN decoding) How To Pair a cluster View ecu eeprom and cluster bin: Code: $ eepromtool.exe "Immo bin with SKC 05557.bin" Pair the cluster (vRS_cluster.bin) to the ECU eeprom (Immo bin with SKC 05557.bin) and write out (vRS_cluster_paired.bin): Code: $ eepromtool.exe --in "vRS cluster.bin" --out "vRS cluster_paired.bin" --pair "Immo bin with SKC 05557.bin" View paired cluster bin: Code: $ eepromtool.exe "vRS cluster_paired.bin" This bin can then be written back to the cluster, but you must use VCDS to set the softcoding in the cluster (set it to the same value as your old cluster, or set to the same value that it is already set to) so that the checksum on the cluster is reset. Attached are a windows executable version in a zip (which is a stupidly big because it includes the python runtime libraries) and the python source code - if you have python installed then just grab the script, if not then either get python2.7, or download the zip and unzip it. as ever, feedback is welcome :) [ed: I have removed the attached files to prevent confusion. Please keep the OP updated] Title: Re: 95040Tool - Please test Post by: Bi-turbo on September 15, 2014, 12:04:32 AM Is this run from (start - run - CMD then type in 95040tool.exe) to run the program?
Title: Re: 95040Tool - Please test Post by: turboat on September 15, 2014, 12:58:09 AM Yes, obviously you need this tool to be in the same directory as you are, not just in your downloads directory.
Title: Re: 95040Tool - Please test Post by: Bi-turbo on September 15, 2014, 01:04:36 AM Cool, thanks
Title: Re: 95040Tool - Please test Post by: dave926 on October 21, 2014, 09:07:39 AM I am having a horrible time trying to figure out how to use this tool with CMD
Title: Re: 95040Tool - Please test Post by: turboat on October 21, 2014, 09:32:02 AM Off the top of my head:
>eepromtool.exe <eeprom dump file> will display a load of info about the eeprom, then use >eepromtool.exe --in <eeprom dump file> --immo off --out immooff.bin to turn immo off, etc. What issues are you having? Title: Re: 95040Tool - Please test Post by: dave926 on October 21, 2014, 01:29:29 PM It's me that's the issue.
I lack CMD skills. Title: Re: 95040Tool - Please test Post by: nyet on October 21, 2014, 06:07:35 PM It's me that's the issue. I lack CMD skills. What is the problem? Be specific. Title: Re: 95040Tool - Please test Post by: byzan a4 on October 22, 2014, 12:45:55 PM i was trying to do some pairing or at least checking, but i'm getting an error that eepromtool is not recognised as an internal or external command,operable program or batch file.
Is it me? older version worked ok but complained my cluster bin was missing bits or something Title: Re: 95040Tool - Please test Post by: nyet on October 22, 2014, 12:57:51 PM Guys: If you have problems, please copy/paste the text (using right-click->mark) not a screenshot of the cmd.exe window.
Also, make sure the program you are trying to run is either in a directory in the PATH environment variable, or the current directory of your cmd.exe session. If you don't understand what either of those are: http://www.makeuseof.com/tag/a-beginners-guide-to-the-windows-command-line/ Title: Re: 95040Tool - Please test Post by: turboat on October 22, 2014, 01:09:25 PM You did download and unzip the tool, right?
Title: Re: Post by: byzan a4 on October 22, 2014, 01:17:14 PM Okay will try. I did unzip it into a folder in root of c. Then added the dash bin and eprom from the ecu into it and opened command prompt up in that folder
Title: Re: 95040Tool - Please test Post by: byzan a4 on October 22, 2014, 03:22:50 PM C:\>cd eep
C:\EEP>eepromtool --in tqsfl.bin 95040 Eeeprom Tool - 0.3 - No warranty implied or given, manually verify all cha nges before saving eeprom to ECU, this tool could cause permenent damage to ECU and prevent vehicle running Read in 2048bytes Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using -- force) WARNING: Cluster Code Block 1 and 2 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: Cluster Code Block 1 and 3 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: Cluster Code Block 2 and 3 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: cannot decode VIN, try setting VIN to fix WARNING: cannot decode ImmmoID EEPROM Status: - VIN: - SKC: 02511 - Cluster Code: 14 00 00 00 00 00 00 - Immo ID: Thats what i get reading the attached Title: Re: 95040Tool - Please test Post by: turboat on October 22, 2014, 04:39:58 PM Thanks, I'll take a look tomorrow. What year car is it? Did it process your ecu eeprom correctly?
Title: Re: Post by: byzan a4 on October 23, 2014, 12:41:46 AM Ecu eprom was perfect thank you. Car is a 2000 audi a4
Title: Re: 95040Tool - Please test Post by: TijnCU on October 23, 2014, 03:20:08 AM I am unable to launch the program in win XP. It worked well in win 8 though :o
Title: Re: 95040Tool - Please test Post by: turboat on October 23, 2014, 04:12:40 AM Ok, I think we can safely say that this doesnt work for S4 clusters! So far I've only tested it with mk4 platform clusters, but that s4 dump is totally different. I'll update it if I get time, but the varience between different eeproms is going to take a while to deal with.
Title: Re: Post by: byzan a4 on October 23, 2014, 02:26:33 PM Ah ok. No worries. Bloody cars. I just want to stop the damn light flashing
Title: Re: 95040Tool - Please test Post by: turboat on October 23, 2014, 03:02:49 PM I take it you've tried adapting the cluster and ecu with Vcds?
Title: Re: Post by: byzan a4 on October 24, 2014, 03:09:52 AM Yeah. I've changed to me. 7.5 and updated to later cluster all in one hit. So I don't have the old skc or anything as new dash is reported as immobiliser 3 in epromthingy despite it set on immo2
Title: Re: 95040Tool - Please test Post by: tpzd3fq on November 11, 2014, 12:50:02 AM Awfully sorry for mine supidity : I mistake author of this great tool---you as ArgDub :(
download these two deffrent software several months and really tested quite a few times pardon me for my blindness :) Title: Re: 95040Tool - Please test Post by: Allabout on November 18, 2014, 03:13:55 AM Was playing with the IMMO off on my ECU bin file.
Now I'm only working from examples provided within this thread and the -h suffix command. This is the error I received. C:\ME7\eepromtool>eepromtool.exe --in IMMO_on.bin --immo off --out immooff.bin - -status --fixcs 95040 Eeeprom Tool - 0.3 - No warranty implied or given, manually verify all cha nges before saving eeprom to ECU, this tool could cause permenent damage to ECU and prevent vehicle running Read in 1048576bytes WARNING: cannot decode VIN, try setting VIN to fix WARNING: cannot decode ImmmoID EEPROM Status: - VIN: - SKC: 062534 - Immobiliser: Error, set Immo - Checksum: Invalid Checksum Size: 1024kb - is this a flash bin not an eeprom bin? Exiting Traceback (most recent call last): File "eepromtool.py", line 730, in <module> File "eepromtool.py", line 675, in main File "eepromtool.py", line 230, in printStatus File "eepromtool.py", line 247, in getLength NameError: global name 'exit' is not defined C:\ME7\eepromtool> I have checked both the ECU and cluter bin files. There is no VIN set anywhere?? Only displays as XXXXXXXXXXXX I now also understand why I was struggling to decode the ECU bin for the SKC. As that is the number I kept coming up with. The cluster bin reveals completely different skc. So any suggestions or recommendations? I tried using the 95040tool first with no success at all. Here is the results of the 95040 tool. C:\ME7\95040tool>95040tool.exe --in immo.bin --out immooff.bin --immo IMMO --fi xcs 95040 Eeeprom Tool - 0.1 - No warranty implied or given, manually verify all cha nges before saving eeprom to ECU, this tool could cause permenent damage to ECU and prevent vehicle running WARNING: cannot decode VIN, try setting VIN to fix WARNING: cannot decode ImmmoID - Setting backup pages - Correcting checksums Warning: Error correcting checksum, checksums in output file may be invalid Writing eeprom bin to: immooff.bin - Write Successful C:\ME7\95040tool>ME7Check.exe immooff.bin ============================================================================== ME7Check v1.12 (c) mki, 06/2004-05/2012 Checking file immooff.bin (size=1048576) Reading Version Strings... -> Bootrom Version = F0.61 (UNKNOWN)!! ** NOT OK ** -> EPK = 42/1/ME7.̵5/6001.01//X22.Ú/Dstt2t/260599¸þ -> Contents of ECUID data table: -> ECUID data table not found ** NOT OK ** -> file not recognized as ME7, stopping analysis C:\ME7\95040tool> Title: Re: 95040Tool - Please test Post by: turboat on November 18, 2014, 04:07:54 AM Theres a few things wrong here, first up you are confusing eeprom and flash in the ECU, eeprom is where the immo settings, adaptation, SKC, etc are stored. Flash is where your maps are stored - and you use me7check for the flash, not the eeprom, hence that would report the errors.
Secondly,eepromtool reported the file size as '1048576bytes', which makes me think that you are looking at a 1MB flash bin, not a 512B eeprom bin. Did you read this bin using nefmoto? If so, go and read the bin from your ECU using argdubs tool :) Title: Re: 95040Tool - Please test Post by: Allabout on November 18, 2014, 01:01:27 PM Theres a few things wrong here, first up you are confusing eeprom and flash in the ECU, eeprom is where the immo settings, adaptation, SKC, etc are stored. Flash is where your maps are stored - and you use me7check for the flash, not the eeprom, hence that would report the errors. Secondly,eepromtool reported the file size as '1048576bytes', which makes me think that you are looking at a 1MB flash bin, not a 512B eeprom bin. Did you read this bin using nefmoto? If so, go and read the bin from your ECU using argdubs tool :) yes it was a nefmoto bin read. ok well that makes sense, thanks which tool of argdubs are you refering to? this one perhaps - http://nefariousmotorsports.com/forum/index.php?topic=1168.0title= ? Title: Re: 95040Tool - Please test Post by: turboat on November 18, 2014, 01:54:41 PM Yeh that one, commonly refered to as 'argdubs tool'
Title: Re: 95040Tool - Please test Post by: spawn2death on December 21, 2014, 05:30:07 AM Hi. I read eeproom with me7_95040 in boot mode (version 1.31 in not boot mode does not work).
C:\Temp\eepromtool>eepromtool --in eeprom_2.bin 95040 Eeeprom Tool - 0.3 - No warranty implied or given, manually verify all cha nges before saving eeprom to ECU, this tool could cause permenent damage to ECU and prevent vehicle running Read in 512bytes EEPROM Status: - VIN: XXXXXXXXXXXXXXXXX - SKC: 065535 - Immobiliser: On - Checksum: Invalid Checksum - Size: 512bytes - Cluster Code: 00 00 00 00 00 00 00 - P0601 DTC: not set - Immo ID: XXXXXXXXXXXXXX - Softcoding ID: 5712 ECU 4b0907551f I want replace my magnetti marelli panel with vdo and off immobilizer. I fear do it this with eepromtool. Invalid checksum and xxxxxxxxx vin. Title: Re: 95040Tool - Please test Post by: spawn2death on December 21, 2014, 11:22:27 AM I cross my fingers and off immo with eepromtool and write it. All is fine :) Thank you for this great tool.
Title: Re: 95040Tool - Please test Post by: aRd on December 24, 2014, 06:18:40 AM Hi turboat
as discussed, attached is an ecu and cluster file. Title: Re: 95040Tool - Please test Post by: aRd on December 24, 2014, 06:22:42 AM hi
attached is copy of the cluster and ecu I would like the data out of the cluster to be copied into the ECU Thank you Title: Re: 95040Tool - Please test Post by: aRd on December 24, 2014, 06:23:38 AM ECU file
Title: Re: 95040Tool - Please test Post by: tabster on December 26, 2014, 03:49:55 PM hi attached is copy of the cluster and ecu I would like the data out of the cluster to be copied into the ECU Thank you Ray, check your email and you will find updated ECU eeprom, with cluster immo data inside :) Title: Re: Post by: byzan a4 on January 02, 2015, 04:10:05 AM Can this be done on all combinations of cluster and ecu?
Title: Re: 95040Tool - Please test Post by: turboat on January 02, 2015, 06:38:27 AM 'All' is too strong, 'many combinations' yes.
Title: Re: 95040Tool - Please test Post by: seany260 on March 19, 2015, 03:23:45 PM Hello, im trying to play about with the tool, to get an end result off immo off, but cant even open the file in question. where do i go wrong. file attached.
C:\>eepromtool\eepromtool.exe --in 518ak 95040 Eeeprom Tool - 0.3 - No warranty implied or given, manually verify all cha nges before saving eeprom to ECU, this tool could cause permenent damage to ECU and prevent vehicle running ERROR: Could not open input file - 518ak Title: Re: 95040Tool - Please test Post by: turboat on March 19, 2015, 04:37:47 PM Try adding .bin to the end of '518ak'
Title: Re: 95040Tool - Please test Post by: seany260 on March 19, 2015, 05:02:42 PM I got it, had the eeprom file in the folder for the eepromtool instead of the c: root.
thanks for this again makes life easy. Title: Re: 95040Tool - Please test Post by: seany260 on March 20, 2015, 03:47:00 AM so im at a stop again, trying to actually 'immo off' and this is what im getting. excuse me for the slow learning! thank you.
C:\>eepromtool\eepromtool.exe --in 518ak.bin --immo off --out 518ak_off.bin 95040 Eeeprom Tool - 0.3 - No warranty implied or given, manually verify all cha nges before saving eeprom to ECU, this tool could cause permenent damage to ECU and prevent vehicle running Read in 512bytes Setting Immobiliser: Off - Immobiliser Off - Setting backup pages - Correcting checksums Error: Could not open output file, exiting Traceback (most recent call last): File "eepromtool.py", line 730, in <module> File "eepromtool.py", line 721, in main File "eepromtool.py", line 218, in writebin NameError: global name 'exit' is not defined I know im not suppose to post screen shots but this my help understand what im doing wrong.. Title: Re: 95040Tool - Please test Post by: turboat on March 20, 2015, 06:32:22 AM Do you ahve all the files that came with eepromtool, or just the .exe?
Title: Re: 95040Tool - Please test Post by: seany260 on March 20, 2015, 06:35:45 AM Yes they are all in the eepromtool folder.
Title: Re: 95040Tool - Please test Post by: ddillenger on March 20, 2015, 09:50:20 AM Do we have any clue as to the checksums in the cluster eeprom?
Title: Re: 95040Tool - Please test Post by: seany260 on March 20, 2015, 11:49:13 AM Do we have any clue as to the checksums in the cluster eeprom? Was that for me?? Title: Re: 95040Tool - Please test Post by: turboat on March 20, 2015, 11:57:42 AM Do we have any clue as to the checksums in the cluster eeprom? No, when I've changed clusters before I've always recoded them using VCDS to set the checksum. I dont think that works on 2.7t clusters thou, only 1.8t clusters. Title: Re: 95040Tool - Please test Post by: ddillenger on March 20, 2015, 02:33:11 PM No, when I've changed clusters before I've always recoded them using VCDS to set the checksum. I dont think that works on 2.7t clusters thou, only 1.8t clusters. Yes, it doesn't work on the 2.7t clusters :( Title: Re: 95040Tool - Please test Post by: seany260 on March 20, 2015, 02:38:24 PM Yes they are all in the eepromtool folder. So do you know what is the reason for my error? Title: Re: 95040Tool - Please test Post by: turboat on March 20, 2015, 03:44:26 PM So do you know what is the reason for my error? I would suggest downloading the tool again, deleting your current copy and trying again. No idea what causes that error. Title: Re: 95040Tool - Please test Post by: ddillenger on March 20, 2015, 05:42:06 PM Screenshots are perfectly acceptable. I don't know where you got otherwise, the only instance I can think of is nyet talking about people taking a picture of the computer screen with a cellphone and posting that, which is not good.
Title: Re: 95040Tool - Please test Post by: turboat on March 21, 2015, 12:26:26 AM I think nyet objects to people posting screenshots of the console, when the text can just be pasted. I'm kinda with him there, it saves space and scales better for a cell screen, but not enough to get worked up about - wayyyy to much broken in my crappy code for me to complain about how people report bugs :D
Title: Re: 95040Tool - Please test Post by: seany260 on March 21, 2015, 02:05:39 PM all sorted now immoff :D.
did not realise that it cant be run from he 'c:' moved to 'c:\users' and works well. thanks again Title: Re: 95040Tool - Please test Post by: marrakech on June 19, 2015, 01:49:52 AM Thanks for the tool!
Title: Re: 95040Tool - Please test Post by: tjwasiak on July 06, 2015, 04:11:39 AM Do we have any clue as to the checksums in the cluster eeprom? It depends on the cluster but for VDO IMMO3 Mk4/Passat/Octavia/SuperB clusters it seems that only parts of the EEPROM are covered by checksum. To be exact it is part which is responsible for speed and mileage - so K-value, speedometer scale, speed signal source (dedicated VSS sender/CAN) and mileage. I have changed many other bytes and did not have to take care about any checksum even on newer clusters.Title: Re: 95040Tool - Please test Post by: turboat on July 06, 2015, 12:23:16 PM Very interesting, do you have any info or links on the locations of the different tables in the mk4 cluster?
Title: Re: 95040Tool - Please test Post by: tjwasiak on July 06, 2015, 12:56:40 PM There is a topic (http://nefariousmotorsports.com/forum/index.php?topic=7964.0title=) here on Nefmoto regarding that. If you need any further informations just ask there - I will do my best to help you.
Title: Re: 95040Tool - Please test Post by: turboat on July 06, 2015, 01:11:30 PM Thanks, think I'd seen that before but only skimmed it. I'll take a proper look sometime soon
Title: Re: 95040Tool - Please test Post by: eliotroyano on August 19, 2015, 07:44:18 AM Friends a question I was reading that this tool can pair cluster dump with ecu dump, but it can do it in opposite way, I mean pair a ecu with cluster dump? Car is a 2002 VW Passat 1.8T AWT with manual transmission. If this software can not do it, anyone can help me to pair ECU serial dump with Cluster dump info? Attached are dumps.
Title: Re: 95040Tool - Please test Post by: vampirelo on August 19, 2015, 08:41:12 AM Friends a question I was reading that this tool can pair cluster dump with ecu dump, but it can do it in opposite way, I mean pair a ecu with cluster dump? Car is a 2002 VW Passat 1.8T AWT with manual transmission. If this software can not do it, anyone can help me to pair ECU serial dump with Cluster dump info? Attached are dumps. Why you don't do adaptation through 50 channel of Engine ECU?I can correct manually 95040.bin to match with Instrument Cluster, but you will need to set ECU to boot mode for writing. Title: Re: 95040Tool - Please test Post by: eliotroyano on August 19, 2015, 08:45:54 AM Why you don't do adaptation through 50 channel of Engine ECU? I try it but ECU does not allow it. I receive "KEY ERROR" message. I can correct manually 95040.bin to match with Instrument Cluster, but you will need to set ECU to boot mode for writing. I really appreciate that. Also will not be a problem to reprogram 95040 by setting ECU in boot mode. Title: Re: 95040Tool - Please test Post by: byzan a4 on August 19, 2015, 12:19:15 PM Why you don't do adaptation through 50 channel of Engine ECU? I can correct manually 95040.bin to match with Instrument Cluster, but you will need to set ECU to boot mode for writing. Any chance you could do that with my cluster and ecu bins? I cannot visualise what needs changing and i have an awkward cluster / ecu combo that won't match properly Title: Re: 95040Tool - Please test Post by: vampirelo on August 19, 2015, 02:36:17 PM I try it but ECU does not allow it. I receive "KEY ERROR" message. Attached matched 95040.bin and dump of Instrument Cluster with switched on Arrows.I really appreciate that. Also will not be a problem to reprogram 95040 by setting ECU in boot mode. Please note that new immo ID48 megamos chips to keys may be required. I am not sure with it! Good luck! ;) Title: Re: 95040Tool - Please test Post by: vampirelo on August 19, 2015, 02:38:38 PM Any chance you could do that with my cluster and ecu bins? Could you please attach 95040.bin and Cluster dump. To make match manually are a few minutes.I cannot visualise what needs changing and i have an awkward cluster / ecu combo that won't match properly Title: Re: 95040Tool - Please test Post by: byzan a4 on August 19, 2015, 02:58:44 PM Could you please attach 95040.bin and Cluster dump. To make match manually are a few minutes. Thank you, I am using the attatched virgin file or my original ecu eprom also is attached. If you need VIN, pleas PM me. I really appreciate your help Title: Re: 95040Tool - Please test Post by: vampirelo on August 19, 2015, 03:19:44 PM Thank you, I am using the attatched virgin file or my original ecu eprom also is attached. As I see in 95040.bin you have Imoo II Engine ECU, it is not required to match Cluster to ECU like it is for Immo III.If you need VIN, pleas PM me. I really appreciate your help You need just to login to 17-Speedo, go to adaptation channel 00, apply, save and switch off ingnition for 1 minute. Title: Re: 95040Tool - Please test Post by: byzan a4 on August 19, 2015, 03:26:53 PM As I see in 95040.bin you have Imoo II Engine ECU, it is not required to match Cluster to ECU like it is for Immo III. You need just to login to 17-Speedo, go to adaptation channel 00, apply, save and switch off ingnition for 1 minute. It won't adapt, because the ecu was never meant to be with this cluster. I have been told if I manually add the info it will work fine that way Title: Re: 95040Tool - Please test Post by: turboat on August 20, 2015, 12:27:40 AM Friends a question I was reading that this tool can pair cluster dump with ecu dump, but it can do it in opposite way, I mean pair a ecu with cluster dump? Car is a 2002 VW Passat 1.8T AWT with manual transmission. If this software can not do it, anyone can help me to pair ECU serial dump with Cluster dump info? Attached are dumps. In theory yes,I'm can't remember if I ever implemented it. I will look if I get free time later Title: Re: 95040Tool - Please test Post by: vampirelo on August 20, 2015, 05:01:17 AM It won't adapt, because the ecu was never meant to be with this cluster. I have been told if I manually add the info it will work fine that way As basis used markimmoori.bin.vin added to speedo dump and 95040.bin matched to it. Could you please check and advise result. Title: Re: 95040Tool - Please test Post by: eliotroyano on August 20, 2015, 01:54:54 PM Attached matched 95040.bin and dump of Instrument Cluster with switched on Arrows. Please note that new immo ID48 megamos chips to keys may be required. I am not sure with it! Good luck! ;) Thanks a lot vampirelo, let me try it !!!!!!!!! Title: Re: 95040Tool - Please test Post by: byzan a4 on August 24, 2015, 03:31:51 AM As basis used markimmoori.bin. vin added to speedo dump and 95040.bin matched to it. Could you please check and advise result. Many thanks Sadly no good currently, i think the ecu and dash combo talk different languages over the wline as ecu still cuts it out. Thsnk you for taking the time to do it, it's really appreciated. it's helped me to see the changes if I even need to make a change again Title: Re: 95040Tool - Please test Post by: vampirelo on August 25, 2015, 10:27:49 AM Many thanks Post values from groups 022 and 023 of Speedo measures.Sadly no good currently, i think the ecu and dash combo talk different languages over the wline as ecu still cuts it out. Thsnk you for taking the time to do it, it's really appreciated. it's helped me to see the changes if I even need to make a change again Have you bought new chip ID48 megamos? Title: Re: 95040Tool - Please test Post by: byzan a4 on September 03, 2015, 09:45:37 AM I will sort it later. Not been on. Thanks, What format would you like the "logs" or a screen shot job?
Title: Re: 95040Tool - Please test Post by: vampirelo on September 13, 2015, 12:56:04 AM I will sort it later. Not been on. Thanks, What format would you like the "logs" or a screen shot job? Any format: values like 022 - 1112, 023 - 0111 will be enough.Title: Re: 95040Tool - Please test Post by: Pwndbymustang on October 21, 2015, 03:11:18 PM This tool works awesome! Thanks Turboat!
Title: Re: 95040Tool - Please test Post by: dbreeze on December 18, 2015, 02:49:26 PM So I don't know if this is a bug or not: I have a 4B0 906 018 CL ECU (ME7.5) that I'm trying to remove the immobilizer on.
It reads fine and does not error at all (both OBD and bootmode in ArgDub's tool) but when I check the created file using '--status', it says that the checksum is invalid. Any other way that I can check the 95040 bin to see if it is in fact incorrect or if it's a bug in one of the tools? Thanks! Title: Re: 95040Tool - Please test Post by: bram380 on March 02, 2016, 01:38:55 PM Thanks Turboat,
the tools working perfect Title: Re: 95040Tool - Please test Post by: febomax on August 25, 2016, 08:08:21 AM Just for debug, i tried the tool on my dump of ecu and got :
WARNING: cannot decode ImmmoID EEPROM Status: - VIN: XXXXXXXXXXXXXXXXX - SKC: 065535 - Immobiliser: On - Checksum: Invalid Checksum - Size: 512bytes - Cluster Code: 00 00 00 00 00 00 - P0601 DTC: not set - Immo ID: ECU me 7.7.5 from A3 1800 turbo Quattro of 1999. Dump file is attached. Thanks for tool ! Title: Re: 95040Tool - Please test Post by: turboat on August 25, 2016, 11:50:30 PM That's probably immo 2, have you checked with vcds?
Title: Re: 95040Tool - Please test Post by: febomax on August 26, 2016, 02:01:23 AM Yes ! is immo2 !
So what i have to do ???? Thanks ! EDIT: if i don't understand bad simply the tool cannot show that data....so maybe the dump IS good ! The IMMO off is working correctly anyway ? SO i can use it and write the bin ??? THANKS ! Title: Re: 95040Tool - Please test Post by: vampirelo on August 26, 2016, 06:12:39 AM febomax
Tool works properly, i.e. you can upload bin with applied by me7_95040 immo off. However I checked that enough for immo 2 just to correct 01 to 02 (in two lines) for immo off address and correct for the same lines checksum. Title: Re: 95040Tool - Please test Post by: febomax on August 26, 2016, 06:25:19 AM I posted in main forum but put also here...
I don't understant why file created by tool is LOT different.... Are BOTH good ? So the correct procedure to put a new instrument cluster is : - connect NEW cluster - adapt it with vagcom - put IMMO OFF eeprom in bootmode to avoid problems with keys (i must put an immo1 against immo2 and keys are not matching) ? ? ? (code led stay blinking, i know, may be i cau se black tape inside cluster to mask) Thanks ! Title: Re: 95040Tool - Please test Post by: vampirelo on August 26, 2016, 06:50:24 AM febomax,
I would recomend to use epromboot_NOIMMO_MANUAL.bin only. I've checked this manual way correction for immo 2 and it works properly! Seems to me that tool is not applicable to immo 2 ECU therefore a lot of corrections which are not need for immo 2 ECU. Title: Re: 95040Tool - Please test Post by: febomax on August 26, 2016, 07:03:38 AM Seems also to me the same, i'm not expert but don't understand why so much differences in file made by tool.
Is correct the procedure to swap the cluster i wrote up ? THANKS ! Title: Re: 95040Tool - Please test Post by: vampirelo on August 26, 2016, 07:51:22 AM If you made immo off than you don't need to adapt cluster to ECU. Engine will start with any Cluster as well as without Instrument cluster at all!
I could not get why you are looking for difficulties? ) If you changed immo 2 cluster to immo 1 cluster (so we are talking about xxx919xxx series) than would need to change immo chip in key from id48 to id13 and match it with vagcom. Title: Re: 95040Tool - Please test Post by: febomax on August 26, 2016, 08:43:38 AM That is the problem, id13 against id48.
My question is :can i buy a VIRGIN transponder id13 (10 euro), put on key and match it with vagcom or i need to PROGRAM that trasponder before ???? This is what i still does not understood... ??? THANKS for infos ! Title: Re: 95040Tool - Please test Post by: turboat on August 26, 2016, 04:03:02 PM Don't use this for immo2. This tool was written for immo3 me isn't really aware of immo2 format
Title: Re: 95040Tool - Please test Post by: vampirelo on August 29, 2016, 05:42:39 AM That is the problem, id13 against id48. You need to buy New transponder id13, put it into key and match it to your immo 1 cluster via vagcom.My question is :can i buy a VIRGIN transponder id13 (10 euro), put on key and match it with vagcom or i need to PROGRAM that trasponder before ???? This is what i still does not understood... ??? THANKS for infos ! Title: Re: 95040Tool - Please test Post by: EuroXs4 on November 28, 2016, 10:39:56 AM I gotta say this tool is pretty slick!!I have a question.Cluster data what is it exactly??and does it need to be changed??I am swapping in a replacement ecu.I edited the vin immo id and skc to match the one thats in the car.However I am curious if the cluster data needs to match as well or not??
Title: Re: 95040Tool - Please test Post by: vampirelo on December 06, 2016, 10:12:04 AM I gotta say this tool is pretty slick!!I have a question.Cluster data what is it exactly??and does it need to be changed??I am swapping in a replacement ecu.I edited the vin immo id and skc to match the one thats in the car.However I am curious if the cluster data needs to match as well or not?? If you copy VIN ID, Immo ID, Login, 7 bytes of Matching info (skc) from old ECU to New ECU than Cluster will work with New ECU absolutly identical and no need to change anythink in Cluster.Title: Re: 95040Tool - Please test Post by: tularem on May 25, 2017, 05:25:53 PM sorry to bring this thread back from the dead, but I feel like I'm too close to getting this thing taken care of not to.
input: Code: eepromtool.exe --in immoon.bin --immo off --out immooff.bin Output: Code: Read in 2048bytes attached is my .bin file. Immo II in my 01 Jetta 1.8t (AWW)(DL) is active and won't accept the immo pin. Is the dash bad? What's the deal here? thanks in advance! Title: Re: 95040Tool - Please test Post by: vampirelo on May 26, 2017, 01:17:03 AM sorry to bring this thread back from the dead, but I feel like I'm too close to getting this thing taken care of not to. You have immo 2 dash therefore need to adopt Cluster to ECU by 00 channel of Cluster Adaptation (vagcom). After that re-match yours keys through 21 channel of cluster adoptation.input: Code: eepromtool.exe --in immoon.bin --immo off --out immooff.bin Output: Code: Read in 2048bytes attached is my .bin file. Immo II in my 01 Jetta 1.8t (AWW)(DL) is active and won't accept the immo pin. Is the dash bad? What's the deal here? thanks in advance! Title: Re: 95040Tool - Please test Post by: kido resuri on May 31, 2017, 01:43:11 PM Hi, I have Fiat Punto mk2 1.2 16V, which has ME73H4 ECU.
I was able to read the the eeprom contents with the ME7 95040 programmer. If i try to use this 95040Tool, it seems to show the SKC, but I don't think that is the right one actually. It doesn't show VIN, and shows Checksum error also. Is it possible to retrieve the SKC from this type of ECU? Thank you in advance! Title: Re: 95040Tool - Please test Post by: aef on December 21, 2017, 10:01:01 AM Just found this tool. Its great.
I used it to verify my manualy calculated skc. I would suggest to keep first post up to date and code the version into filename. 0.3 is newest? Title: Re: 95040Tool - Please test Post by: nyet on December 21, 2017, 11:28:51 PM I would suggest to keep first post up to date and code the version into filename. This is why I detest forums for doing development. Title: Re: 95040Tool - Please test Post by: nyet on May 22, 2018, 09:50:36 AM turboat: please either
1) keep the OP updated with the latest version (and add version number to the file name) or 2) provide a link to a repository that always contains the most recent version (e.g. github) The version thrashing and confusion here is unacceptable. Forums were simply not designed for this sort of thing, so some effort is required on your part. Thanks. I am removing the attached files on the OP accordingly (for now) to prevent confusion. Title: Re: 95040Tool - Please test Post by: Inquirer on May 23, 2018, 11:53:00 AM turboat: please either 1) keep the OP updated with the latest version (and add version number to the file name) or 2) provide a link to a repository that always contains the most recent version (e.g. github) The version thrashing and confusion here is unacceptable. Forums were simply not designed for this sort of thing, so some effort is required on your part. Thanks. I am removing the attached files on the OP accordingly (for now) to prevent confusion. Dear Mr Nyet: It's not my intention to start a discussion. It's only I saw that the last activity from Turboat was in march 16 2017. More than one year in silence after a high frequency post activity. By any reason he can't enter again to Nefariousmotorsport, so I guess it would be difficult for him to follow your advice, meanwhile, some noobs like me, can´t download to use or at least to evaluate the software from this thread. Could be possible to reload the 95040tool.exe at least until Turboat can answer to your message?. Thanks in advance Inquirer Title: Re: 95040Tool - Please test Post by: darksidedevel on June 29, 2018, 12:35:50 AM I've been working on a script to make it easier to immo off, set vin, get SKC, etc. Its in python, so its a much nicer distro if you have python installed, just run the script. If you don't have python installed then I have attached a zip with a .exe version. Piece of art @turboat!This is an early beta, please test this well before use! All feedback is welcome :) .... Where can I get the software my IMMO in my TT goes crazy currently I am searching for the way to bypass it. Title: Re: 95040Tool - Please test Post by: adam- on July 10, 2018, 01:59:21 AM Can we update this with the last version? I have 1.4 IIRC.
Currently sitting on my Google Drive here but would like it back here. Seems a lot of people are after it. Title: Re: 95040Tool - Please test Post by: armycat on July 10, 2018, 04:12:37 PM Can we update this with the last version? I have 1.4 IIRC. Hello, can you please send me the link to download that version you have? I would appreciate it very much! :) (also if you already posted the link or something forgive me, i am new to the forum)Currently sitting on my Google Drive here but would like it back here. Seems a lot of people are after it. Title: Re: 95040Tool - Please test Post by: dal on July 22, 2018, 05:56:45 AM Please post the lastest version again :(.
Title: Re: 95040Tool - Please test Post by: RedRotors on July 23, 2018, 01:05:53 PM +1
I'm also looking for it to fix an Immo problem on an Audi. Title: Re: 95040Tool - Please test Post by: adam- on July 23, 2018, 01:47:48 PM https://drive.google.com/open?id=0B7E8PFcAIZwKLXdnTGo1VjUxSW8
You owe me beer. Title: Re: 95040Tool - Please test Post by: dal on July 24, 2018, 04:28:20 AM https://drive.google.com/open?id=0B7E8PFcAIZwKLXdnTGo1VjUxSW8 You owe me beer. This is not the lastest version. The lastest version was on this post http://nefariousmotorsports.com/forum/index.php?topic=6134.msg62200#msg62200. Title: Re: 95040Tool - Please test Post by: adam- on July 24, 2018, 04:41:21 AM Do you have the latest version?
Title: Re: 95040Tool - Please test Post by: nyet on July 24, 2018, 07:07:36 AM Sorry, I should not have removed the attachment, and this stupid forum software doesn't seem to have a way to recover it.
I hate forums for software distribution, its crazy stupid. Title: Re: 95040Tool - Please test Post by: adam- on July 24, 2018, 07:31:10 AM Too ban hammer happy.
Title: Re: 95040Tool - Please test Post by: dal on July 24, 2018, 09:59:08 AM Title: Re: 95040Tool - Please test Post by: 4nd0r0 on September 05, 2018, 03:55:18 AM Hi guys, can someone post a link with the latest 95040Tool?
I would highly appreciate it. ;D Title: Re: 95040Tool - Please test Post by: turboat on September 28, 2018, 04:50:00 AM Sorry about the silence guys, Ive been caught up in other projects and not seen the notifications for this. I’ll dig out the latest copy and upload it :)
Title: Re: 95040Tool - Please test Post by: nyet on September 28, 2018, 02:06:24 PM Welcome back! Sorry I screwed things up here, it was entirely my fault. I should have backed up the latest revision before fat fingering the OP.
Title: Re: 95040Tool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: turboat on October 03, 2018, 12:09:50 PM EEpromtool is now hosted on github. Please pull it down, test and let me know if there are any issues.
If anyone has feedback or improvements to suggest, that would be super useful. I would like to improve the handling of immo2 bins, and it would be good to document what it does/does not do. Also if anyone has information on cluster checksums, that would be good to add. Title: Re: 95040Tool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Risky on October 03, 2018, 04:21:44 PM Worked for me :) Thanks!
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: nyet on October 03, 2018, 09:43:49 PM Thank you!
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: kutscher on October 29, 2018, 09:55:19 AM Thanks, great work turbat
Can confirm that eepromtool can immo off a ME 7.1.1, Golf 5, R32, 022906032CD, with 95160 eeprom. Read in 2048bytes Setting Immobiliser: Off - Immobiliser Off - Setting backup pages - Correcting checksums - Write Successful Read in 2048bytes EEPROM Status: - Type: ECU_eeprom - Version: Immo2 - VIN: WVWZZZ1KZ6W0..... (VW 2006 - Golf and Jetta 5, 6, Wolfsburg, Germany) - SKC: 06520 - Immobiliser: Error, set Immo - Current values: 0x12 = 0x04, 0x22 = 0x04 - Checksum: Invalid Checksum - Size: 2048bytes - 512bytes expected, check this is a eeprom bin - Cluster Code: 87 9E 5D 0B EA F2 5F - P0601 DTC: not set - Immo ID: VWZ7Z0E27..... - Softcoding ID: 0132 - Tuner Tag: Not Set - Flash Programming (successful): 4 - Flash Programming (attempts): 149 Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: turboat on October 29, 2018, 04:04:21 PM Did you write it back onto the ecu and check that it's working OK? I've never tested it on a mk5 r32 and it doesn't look like it's parsed it properly based on that output. Please can you post the bin?
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: kutscher on November 04, 2018, 06:39:45 AM Yes, the car is running. Although parsing was not perfect. Bins say more than 1000 words :)
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: turboat on November 04, 2018, 12:53:40 PM OK that's great, glad it's running. I'll try and improve the parsing, thanks for the bins.
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: bamofo on November 15, 2018, 09:48:03 AM Fixed nm.
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: dal on November 26, 2018, 05:43:34 AM Hi turboat!
First thanks for this great tool. Been using a lot for some testings here. There is one thing that I didnt manage to do yet. Last year I converted my car to wideband ECU (from ME7.5.1 032S to ME7.5.5 032LP with HP flash). Been running perfect since then. The only problem is that I never managed to make the IMMO work again. Today I ran with an immo off EEPROM on ECU, but I have the wish to fix this, and put the IMMO back on. Do you know what I can do, using your tool? I dont if helps, but I attached the cluster bin and an printscreen of the VAGeepromprogrammer screen. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Turbopower on December 31, 2018, 06:48:53 AM Hello, this is my first post with several questions to the EEprom. Sorry for my bad english.
I have an A3 8L year 2003 with AUM-engine and a strange history. The car was running, no lights in the dash, cruise-control was working. Then the OE-ECU was killed by flashing a file without proving the CS. As my skills in soldering are not good, I gave the ECU to a recommended company to reset it to the old condition. They damaged the ECU physically. I bought another identical ECU 06A9066032HJ. They desoldered the EEprom and soldered it into the other used ECU. The EEprom-dump I have is from this situation. The result was, that the car started for 1 second and stopped. Then immo3 was set off and the car was running. At first the rev-counter was dead and I could see communication-probs between ECU, powertrain and dash. The can-bus and the ABS-ECU got checked and a new dash with the old EErom-dump was mounted. Now the dash works, but the communication-probs stayed, ABS-light is on and the car is only running with Immo-off. Now I tried to solve it by myself even if I didn’t work with Immo3 before. I read the EEprom from ECU by bootmode without soldering – thanks to your great tool!!! The EEprom of the dash I read too. After quite a while of research I could see, that VIN, Immo-ID, cluster-code and login-code are correct matching. Based to this here are my specific questions: 1. Quite simple: is the login-code (used in VCDS) the same as SKC? If not, where do I find the SKC in ECU and dash? 2. What is the meaning of the bytes 014H and 015H in the 95040 ECU-EEprom and does it has to match in the dash-EEprom? 3. What is happening in the page 110H? 4. What is written in the page 140H? 5. Can you see something generally wrong in the dumps of ECU or dash (1st after crash, 2nd with Immo-off, changed after running and 3rd dash)? Thanks! Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: nxm08240 on January 09, 2019, 09:54:19 AM Trying to turn immo off on this car and I get this when I read the EEPROM over OBD
Read in 512bytes EEPROM Status: - Type: ECU_eeprom - Version: Immo3 - VIN: XXXXXXXXXXXXXXXXX - SKC: 065535 - Immobiliser: Error, set Immo - Current values: 0x12 = 0x04, 0x22 = 0x04 - Checksum: OK - Size: 512bytes - Cluster Code: 00 00 00 00 00 00 00 - P0601 DTC: not set - Immo ID: XXXXXXXXXXXXXX - Softcoding ID: 16201 - Tuner Tag: - Flash Programming (successful): 0 - Flash Programming (attempts): 0 Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: nxm08240 on January 10, 2019, 09:15:33 AM I got the last ECU sorted. I have an ECU from an AMB and I keep getting this error when trying to read in bootmode. I got it to read a couple of times with cspin6.3 but it did not read correctly. Any ideas?
ME7_EEPROM v1.40 COM: 1, Baud Rate: 10400 Memory type: 95040, size: 512 Opening COM1 ... OK Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK Sending Loader + MonitorCore ... MonitorCore successfully launched Initializing registers ... FAIL. (error=0x40E01) Closing COM1 Edit: Needed 57600 baud... Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: TTRPh on January 18, 2019, 02:12:50 PM Hi! All! Newb here, and I've tried to read all the threads in the last few days but didn't come across the right answer
Problem: I have a 2000 audi tt 1.8T ATC that has a tune from a remote tuner. I have been unable to get a pin using ME7 EEPROM programmer with either v1.31 or v1.40. I wanted to duplicate the 95040.bin onto a spare ECU to run different injectors and have a spare for safety. For the spare I have the matching cluster, and I believe they are from a 2005 Audi TT quattro. The only difference in the ECUs is that original has a C and the the spare has S at the end. I have been able to pull the pin from that ECU with v1.31, by using the --screen command and copying that into a Hex Editor Neo, but unable to do the adaptation to use the key that I have. The pin allows me to log into some controllers but not into instruments and not into immobilizer. It usually times out in each attempt, and the car starts for a second and turns off. When I try using original, I get the No response from the ECU error. What seems to be a solution is to pull the 95040.bin from original ECU to write onto spare. Alternatively, write a virgin file to spare. Questions: 1. Can this EepromTool pull my original ECU SKC? 2. Does the remote tuning software interfere with the process? 3. I've been confusing the terms bootmode vs benchtop in the forum and it makes it difficult to figure out what I need for the writing process onto 95040 chip. --Do I need a benchtop set up to write in bootmode? --What way is the appropriate way to ground pin 21, ie. can that be done when the ECU is on the car, and then using bootmode on the car? --Do I need to de-solder the chip and use a USB-eeprom burner? Thanks in advance. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: B5Quattrolife on January 22, 2019, 07:27:17 AM I got the last ECU sorted. I have an ECU from an AMB and I keep getting this error when trying to read in bootmode. I got it to read a couple of times with cspin6.3 but it did not read correctly. Any ideas? ME7_EEPROM v1.40 COM: 1, Baud Rate: 10400 Memory type: 95040, size: 512 Opening COM1 ... OK Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK Sending Loader + MonitorCore ... MonitorCore successfully launched Initializing registers ... FAIL. (error=0x40E01) Closing COM1 Edit: Needed 57600 baud... im getting the same issue, mind copying your screen? Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: B5Quattrolife on January 22, 2019, 07:55:24 AM im getting the same issue, mind copying your screen? Also this is what im looking at if anyone has any insight C:\Users\Owner>C:\Users\Owner\Desktop\ME7-Bin-Def's-Tools\ME7EEPROM.exe --bootmode 95040 -r -p 1 95040.bin ME7_EEPROM v1.40 COM: 1, Baud Rate: 10400 Memory type: 95040, size: 512 Opening COM1 ... OK Starting Boot_mode ... uC ID response 0xC5: C167CR ... OK Sending Loader + MonitorCore ... MonitorCore successfully launched Initializing registers ... OK Sending EEPROM driver ... FAIL. (error=0x40801) Closing COM1 Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: rysiektr on January 30, 2019, 04:55:15 AM Thanks, great work turbat Can confirm that eepromtool can immo off a ME 7.1.1, Golf 5, R32, 022906032CD, with 95160 eeprom. Read in 2048bytes Setting Immobiliser: Off - Immobiliser Off - Setting backup pages - Correcting checksums - Write Successful Read in 2048bytes EEPROM Status: - Type: ECU_eeprom - Version: Immo2 - VIN: WVWZZZ1KZ6W0..... (VW 2006 - Golf and Jetta 5, 6, Wolfsburg, Germany) - SKC: 06520 - Immobiliser: Error, set Immo - Current values: 0x12 = 0x04, 0x22 = 0x04 - Checksum: Invalid Checksum - Size: 2048bytes - 512bytes expected, check this is a eeprom bin - Cluster Code: 87 9E 5D 0B EA F2 5F - P0601 DTC: not set - Immo ID: VWZ7Z0E27..... - Softcoding ID: 0132 - Tuner Tag: Not Set - Flash Programming (successful): 4 - Flash Programming (attempts): 149 Hi did you have any problems with read DCT's when you turn off immobiliser? Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: matt2005 on February 14, 2019, 01:52:11 PM @ turboat, I've submitted a PR on github to merge my conversion to python3.
I plan on extending the Cluster support, but it made sense to convert it first to python3. I already have a version that seems to work for my mk1 TT cluster that I wrote in 2013, however it's exclusive to the TT clusters. I'm not a developer but I know how to do some coding so I think I can help extend it. Do you have the dumps that you originally used so I can add some tests to ensure it doesn't break anything. Thanks Matt Title: Re: 95040Tool - Please test Post by: dclifford40 on March 21, 2019, 02:34:22 PM command string
I'm not sure where exactly to ask this question,, and apologize if this is in the wrong place I intend to turn off the immo 3 in a TT I got recently with a bad cluster,,,I cant read data from it, the board is fried. I have pulled my 95040.bin file and compared it to many of the -immo off files, but it seems doing it this way is easier. I am not sure of the string to do it with this tool I have the SKC for the ecm The string I used to get my file is; Desktop\me7_95040.exe --OBD -r -p 5 95040.bin The questions; Does the ECU need to be put in boot mode when I start connecting everything on my bench rig (jump pin # 24 to ground)? Guess Im looking for a sample string that is a little more clear.. not great with command appreciate any help,,,if I figure this out Ill post a guide for dummies To change immo or VIN: $ ./95040tool.exe --in Immo\ bin\ with\ SKC\ 05557.bin --immo off --out immoff.bin Setting Immobiliser: Off - Immobiliser Off - Setting backup pages - Correcting checksums Writing eeprom bin to: immoff.bin - Write Successful $ ./95040tool.exe --in immoff.bin --vin YOURVINGOESHERE00 --out immoffvin.bin Setting VIN to YOURVINGOESHERE00 - Setting backup pages - Correcting checksums Writing eeprom bin to: immoffvin.bin - Write Successful $ ./95040tool.exe immoffvin.bin EEPROM Status: - VIN: YOURVINGOESHERE00 - SKC: 05557 - Immobiliser: Off - Checksum: OK - Size: 512bytes - Cluster Code: 69 D9 38 E6 D3 B2 - P0601 DTC: not set - Immo ID: UX6Z0D0454942 Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Risky on March 22, 2019, 12:38:13 PM Yes ECU has to be put into boot mode. I assume you are trying to write to the ECU now, no? If so use me7_95040 --bootmode -wp5 95040.bin. If you didn't already know, you can just type in me7_95040.exe and it will give you all the commands.
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: DadJorts on May 10, 2019, 10:44:10 PM need a bit of guidance here, from a 24v me7.1.1 5p083c. The immo was "professionaly" deleted by a local mobile guy, decided to do it myself once i got it back and noticed the eeprom error fault. This is the initial result with the tool, i take it the experimental part of the tool is still, well, experimental? I've attached the .bin for the curious. Any pointers on where to start with for immo off?
Huge thanks to turboat for the tool! Read in 1024bytes Found 1024b bin - parsing as a R32 bin - experimental ERROR: 1024byte file detected, but the last 512bytes are not all padded with 0xFF, this file is may be a corupt dump, a cluster dump or something other than an eeprom dump, open it with a hex editor - if this is a valid eeprom please post the file and vehicle info on the thread for this tool EEPROM Status: - Type: ECU_eeprom - Version: Immo3 - VIN: 3VWVH69M83M155367 (VW Mexico 2003) - SKC: 065535 - Immobiliser: Error, set Immo - Current values: 0x12 = 0xFF, 0x22 = 0xFF - Checksum: Invalid Checksum - Size: 1024bytes - 512bytes expected, check this is a eeprom bin - Cluster Code: FF FF FF FF FF FF FF - P0601 DTC: set to FF FF - Immo ID: VWZ7Z0C6692238 - Softcoding ID: 0032 - Tuner Tag: - Flash Programming (successful): 0 - Flash Programming (attempts): 0 Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: elektronik13 on May 18, 2019, 03:10:25 AM need a bit of guidance here, from a 24v me7.1.1 5p083c. The immo was "professionaly" deleted by a local mobile guy, decided to do it myself once i got it back and noticed the eeprom error fault. This is the initial result with the tool, i take it the experimental part of the tool is still, well, experimental? I've attached the .bin for the curious. Any pointers on where to start with for immo off? here you have a file, yoursHuge thanks to turboat for the tool! Read in 1024bytes Found 1024b bin - parsing as a R32 bin - experimental ERROR: 1024byte file detected, but the last 512bytes are not all padded with 0xFF, this file is may be a corupt dump, a cluster dump or something other than an eeprom dump, open it with a hex editor - if this is a valid eeprom please post the file and vehicle info on the thread for this tool EEPROM Status: - Type: ECU_eeprom - Version: Immo3 - VIN: 3VWVH69M83M155367 (VW Mexico 2003) - SKC: 065535 - Immobiliser: Error, set Immo - Current values: 0x12 = 0xFF, 0x22 = 0xFF - Checksum: Invalid Checksum - Size: 1024bytes - 512bytes expected, check this is a eeprom bin - Cluster Code: FF FF FF FF FF FF FF - P0601 DTC: set to FF FF - Immo ID: VWZ7Z0C6692238 - Softcoding ID: 0032 - Tuner Tag: - Flash Programming (successful): 0 - Flash Programming (attempts): 0 please report Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: DadJorts on July 04, 2019, 07:02:25 PM worked like a charm! thank again man
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: stanggenius on July 09, 2019, 09:52:21 AM Need help!! Attaching Files. I'll be happy to buy anyone a beer if they can get me out of this mess!!
I need to pair my cluster and ECU, or disable the Immo on the ECU. CLuster just shows immo active and wont stay running. Keys are good, cluster says ecu not boind to it thought obd2 scan. Tring to fix with this software and when I run the software on the cluster it gives: Read in 4096bytes WARNING: cannot decode VIN, try setting VIN to fix WARNING: cannot decode ImmmoID EEPROM Status: - Type: ECU_eeprom - Version: Immo2 - VIN: - SKC: 065312 - Immobiliser: Error, set Immo - Current values: 0x12 = 0xFF, 0x22 = 0xFF - Checksum: Invalid Checksum - Size: 4096bytes - 512bytes expected, check this is a eeprom bin - Cluster Code: 48 30 38 FF FF FF FF - P0601 DTC: set to FF 32 - Immo ID: - Softcoding ID: 65328 - Tuner Tag: Not Set - Flash Programming (successful): 255 - Flash Programming (attempts): 255 ERROR: Output file must be supplied when correcting checksum, setting immo or ch anging VIN. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: nyet on July 09, 2019, 09:54:14 AM Did you supply an output filename? If not, why not?
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: stanggenius on July 09, 2019, 10:42:47 AM I did, I may have copied the wrong output. I tried a bunch of times and did get it to output by stating the VIN. I was also able to get it to do the immo delete but the pair function returned the same error about the immobilizer in my previous post. Am I missing something? I'm new at this and don't want to screw it up further. Basically my understanding is I need those two files to pair so I can write them back, or I need to do the immo delete to get to my end goal which is get my Jetta to start again. If anyone can offer any suggestions or confirm what I need to do that would be awesome!!
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: stanggenius on July 09, 2019, 11:42:18 AM Here's what I get when I try to pair the two:
C:\tools>eep --in ins.bin --out pairedins.bin --pair eepromedc17.bin Read in 4096bytes WARNING: cannot decode VIN, try setting VIN to fix WARNING: cannot decode ImmmoID Traceback (most recent call last): File "eepromtool_04.py", line 794, in <module> File "eepromtool_04.py", line 782, in main AttributeError: ecueeprom instance has no attribute 'pair' [948] Failed to execute script eepromtool_04 Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: nyet on July 09, 2019, 11:45:50 AM Looks like that file isn't supported by the tool, unfortunately.
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: stanggenius on July 09, 2019, 12:52:47 PM Ok,
Can anyone verify that this file is modded correctly? I ran it through the software with no errors, but just want to see if anyone has any clue how to be sure that it will work, or at least not brick my ECU before I flash it back? Attaching File. Also, if anyone has any more info on how to pair my original cluster and ECU back together, please PM me, or tell me where to post. Both dumps I have from cluster and ECU are in my original post. Here's the one I would like to try flashing that wouldn't fix the immo, but hopefully bypass it. And at this point, if I can get anyone who has used this siftware to maybe compare it against theres to let me know if I should be good to go to upload back to the ECU, or if its gonna screw things up worse. I just don't want to get any deeper!!! Thanks all!! Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: elektronik13 on July 21, 2019, 12:44:23 PM Ok, Can anyone verify that this file is modded correctly? I ran it through the software with no errors, but just want to see if anyone has any clue how to be sure that it will work, or at least not brick my ECU before I flash it back? Attaching File. Also, if anyone has any more info on how to pair my original cluster and ECU back together, please PM me, or tell me where to post. Both dumps I have from cluster and ECU are in my original post. Here's the one I would like to try flashing that wouldn't fix the immo, but hopefully bypass it. And at this point, if I can get anyone who has used this siftware to maybe compare it against theres to let me know if I should be good to go to upload back to the ECU, or if its gonna screw things up worse. I just don't want to get any deeper!!! Thanks all!! I think that this file is useless Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: stanggenius on July 23, 2019, 03:49:08 PM That's what I wondered.... Something seemed off when creating it. Shootout im no expert! Someone helped generate one that isn't corrupt for me in these forums and I appreciate everyone's help!!
Title: Re: 95040Tool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: !nfern0 on September 02, 2019, 10:55:00 AM EEpromtool is now hosted on github. Please pull it down, test and let me know if there are any issues. If anyone has feedback or improvements to suggest, that would be super useful. I would like to improve the handling of immo2 bins, and it would be good to document what it does/does not do. Also if anyone has information on cluster checksums, that would be good to add. Hi There! I was looking through this thread and was searching the last days for a solution, but nothing found. So I was trying to use your current release and getting following error: The version of C:\Users\owner\Desktop\Tuning\eepromtool_04.exe is not compatible with the running Windows version. Check the computer's system information, and then contact the publisher of the software. Is there any solution for this, or do I need a 32-bit installation of windows? Thx in advance! Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Alcrerion on September 05, 2019, 10:57:48 AM Attempting to just access SKC and cluster PIN info and keep running into the same response from the program, despite trying a number of different commands.
C:\Users\alcre>C:\Nefmoto\eepromtool_04.exe usage: eepromtool_04.exe [-h] --in INFILE [--out OUTFILE] [--status] [--immo IMMO] [--vin VIN] [--skc SKC] [--cc CC] [--ii II] [--pair PAIR] [--fixcs] [--nofixcs] [--cluster] [--force] eepromtool_04.exe: error: argument --in is required C:\Users\alcre>C:\Nefmoto\eepromtool_04.exe --in INFILE ERROR: Could not open input file - INFILE Any guidance would be appreciated. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: howlingmoki on September 12, 2019, 07:43:44 PM Has anyone had problems with the file from Github recently? On my Win10 box, the Windows Defender Antivirus keeps nuking the download saying that it's detected the Win32/Fuery.B!cl trojan. If this is a known issue, is there a better or different place to get it from? I found the older 95040tool on S4wiki and downloaded that which seems to work OK.
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: jas3113 on September 19, 2019, 12:11:17 PM Has anyone had problems with the file from Github recently? On my Win10 box, the Windows Defender Antivirus keeps nuking the download saying that it's detected the Win32/Fuery.B!cl trojan. If this is a known issue, is there a better or different place to get it from? I found the older 95040tool on S4wiki and downloaded that which seems to work OK. New here and just downloaded this and had the same problem as you did. You need to disable windows defender and add it as an exception. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: howlingmoki on September 29, 2019, 10:19:57 PM Gotcha. Gave it another go this evening and it Defender was reporting a different trojan than before .. weird. Added eepromtool_04.exe to the exception list and all seems fine. I haven't done much with Windows since XP was fresh and "Microsoft security" was the punchline to a joke, so I've been a little hesitant to monkey with things too much.
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: bamofo on October 01, 2019, 08:40:51 AM Attempting to just access SKC and cluster PIN info and keep running into the same response from the program, despite trying a number of different commands. C:\Users\alcre>C:\Nefmoto\eepromtool_04.exe usage: eepromtool_04.exe [-h] --in INFILE [--out OUTFILE] [--status] [--immo IMMO] [--vin VIN] [--skc SKC] [--cc CC] [--ii II] [--pair PAIR] [--fixcs] [--nofixcs] [--cluster] [--force] eepromtool_04.exe: error: argument --in is required C:\Users\alcre>C:\Nefmoto\eepromtool_04.exe --in INFILE ERROR: Could not open input file - INFILE Any guidance would be appreciated. -- in INFILE refers to the file your trying to ingest. You need to do --in bamofo.bin or w/e your filename is. Share the file we can get the answer for you eitherway. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: turboat on October 04, 2019, 03:31:51 AM New here and just downloaded this and had the same problem as you did. You need to disable windows defender and add it as an exception. Hold off on that and I will rebuild the exe. It shouldn't have a trojan in, but you can never be sure. Safest and most secure way is to install python on your system and run the python file rather than the exe. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: GolfSportWagen on October 25, 2019, 02:57:08 PM Hi turboat,
Just curious if the GitHub file has been updated yet as I too get the Defender virus message and blockage. TIA Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: nyet on October 25, 2019, 02:58:01 PM Hold off on that and I will rebuild the exe. It shouldn't have a trojan in, but you can never be sure. It doesn't. I've been getting false positives on all sorts of crap lately. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: turboat on November 01, 2019, 02:31:39 AM I've checked it with virus total and it comes up clean, I think defender has got the signature for the python to exe builder (seriously who would write malware in py??), rather than this specific file having a trojan.
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: nyet on November 01, 2019, 08:25:53 AM I've checked it with virus total and it comes up clean, I think defender has got the signature for the python to exe builder (seriously who would write malware in py??), rather than this specific file having a trojan. I've actually seen malware written in py with the exe builder, and i think you're spot on with this. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: bogdan wst on November 01, 2019, 02:30:05 PM Hello. I am new in this forum and as per the instructions received through this tool, i want to ask for your help. I own (in fact it is my wife's car) an 2003 audi A3 8L 1.6 BFQ petrol engine. It has Jaeger (Magneti Marelli i think) no DIS cluster and i want to retrofit a VDO full DIS cluster. I have the "new" instrument cluster PIN, but i can't find the correct PIN for my original cluster (MM/Jaeger). I tried to pull it with Super Vag and Vag Commander 3.6, but no luck. The pins from the original cluster are not working when i try to pair the immobiliser through the ross-tech procedure (in channel 50 when i put the old PIN in the new value field and hit test it then says DISABLED). I also am using original ross-tech interface.
I managed to read some kind of dump information from my original cluster by using Vag Commander 3.6 (attached file), but by running the dump file through this tool (EepromTool), it seems the dump is corrupted. I attach the message i get from this tool. I also tried the SKC that this tool provided for me, but i could not login to my original Jaeger/MM cluster. I want to say i do not know how to read/extract the cluster dump file wit this tool. How can i do this? Can someone help me in finding the necessary PIN code or is there any way to rebuild my dump file so it is complete/correct for my car? Thank you very much for the support. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: BlackT on November 01, 2019, 03:15:03 PM Get SKC from ECU, it schould match your original cluster pin
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: bogdan wst on November 01, 2019, 03:21:08 PM I can't get the pin code from the ecu neither with vag commander :(
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: BlackT on November 01, 2019, 03:29:09 PM I can't get the pin code from the ecu neither with vag commander :( Agrubd tool? Boot mode?Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: bogdan wst on November 01, 2019, 03:32:59 PM I can't connect to the ecu or cluster with vag eeprom programmer 1.19. It is giving the error "unknown software version".
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: BlackT on November 01, 2019, 03:45:51 PM I mean about this http://nefariousmotorsports.com/forum/index.php?topic=1168.0title=
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Flip on April 10, 2020, 06:35:09 AM Hi there,
can you advice how to find entrys in cluster dumps? Esp. since your amazing tool can "pair" engine-eep.bins depending on that. How can one do it vice versa manually; and what about cluster checksums then? Are entrys the same for most clusters? Can one use the tool "pairing" the other way round? Thank you. Flip Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: doublerwest on July 29, 2020, 07:36:26 PM UPDATE: Eeepromtool is now hosted on github. The most recent release will always be located in: https://github.com/turboat/eepromtool/releases/ Source code is in: https://github.com/turboat/eepromtool Pull requests are welcome :) Eepromtool is a command line tool, either run using 'python eepromtool_04.py' or 'eepromtool_04.exe'. If it just flashes up and disappears, this is because it is a command line tool. If you dont know what a command line tool is, you probably shouldnt be trying to edit your ECU. Displaying Information To simply display the info in a bin called INFILE, use: eepromtool_04.exe INFILE For example with an ecu eeprom: Code: eepromtool_04.exe ecu.bin With a cluster eeprom: Code: eepromtool_04.exe cluster.bin Immo On/Off To set immo status, you must specify input file, output file and desired immo status. Checksums will be corrected automatically unless you specify --nofixcs. For example: Code: eepromtool_04.exe --in ecu.bin --immo off --out ecu_off.bin you wouldnt happen to know how to change the tuner tag would you if thats even a function ..>!!!! Title: Re: 95040Tool - Please test Post by: doublerwest on July 29, 2020, 07:41:22 PM Guys: If you have problems, please copy/paste the text (using right-click->mark) not a screenshot of the cmd.exe window. Also, make sure the program you are trying to run is either in a directory in the PATH environment variable, or the current directory of your cmd.exe session. If you don't understand what either of those are: http://www.makeuseof.com/tag/a-beginners-guide-to-the-windows-command-line/ any ideas on changing the tuner tag ? is that even a feature on this program Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: nyet on August 04, 2020, 10:06:48 PM What problem are you trying to fix?
Title: Re: 95040Tool - Please test Post by: bamofo on August 05, 2020, 12:24:23 PM any ideas on changing the tuner tag ? is that even a feature on this program You can manually remove the tuner tag in the eeprom. then Checksum it with the eeprom tool or manually do CSM on it. Share your EEPROM and we can help. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: doublerwest on August 06, 2020, 05:39:31 PM trying to put this car back to factory and first flashing experience i wipped the immo off the car bricked the guages and im trying to reset the counter and change the tuner tag to my tag as it is my car and im just trying to learn as i go just wanted to make sure it was possible as i am willing to figure it out never know answers if you dont ask questions the car has allot of issues im working on me7logger currently to see why im over boosting with n75 in place almost forgot i asked this question ....
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: doublerwest on August 06, 2020, 06:00:33 PM im guessing the guages still have the immo on them is why i cant gain acess into it still working on that one..
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: porotokka on August 15, 2020, 05:32:49 AM Hello!
I'm fixing Golf MK4 2001 T1.8 cluster and ecu. Cluster fried and I managed to recover data from cluster EEPROM. I have 2 clusters (Bosch Motometer 1J0920825A BOO) now from junk yard. I have written data from fried one to spare cluster now with success. I have read ECU EEPROM with success with bench harness and ME7EEPROM in bootmode. All data are paired between cluster/ECU EEPROM bins but I'm curious about cluster bin file. Are there specific location for cluster code in it? IMMO type is II and cluster bin size is 256 bytes. I cannot read info with eepromtool, gives an error: Read in 256bytes WARNING: cannot decode VIN, try setting VIN to fix WARNING: cannot decode ImmmoID Traceback (most recent call last): File "eepromtool_04.py", line 794, in <module> File "eepromtool_04.py", line 731, in main File "eepromtool_04.py", line 70, in __init__ File "eepromtool_04.py", line 171, in parse IndexError: list index out of range [6660] Failed to execute script eepromtool_04 Do I have to have cluster code in ECU's EEPROM bin file now there is: - Cluster Code: 00 00 00 00 00 00 00 Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: bamofo on August 17, 2020, 10:53:05 AM Hello! I'm fixing Golf MK4 2001 T1.8 cluster and ecu. Cluster fried and I managed to recover data from cluster EEPROM. I have 2 clusters (Bosch Motometer 1J0920825A BOO) now from junk yard. I have written data from fried one to spare cluster now with success. I have read ECU EEPROM with success with bench harness and ME7EEPROM in bootmode. All data are paired between cluster/ECU EEPROM bins but I'm curious about cluster bin file. Are there specific location for cluster code in it? IMMO type is II and cluster bin size is 256 bytes. I cannot read info with eepromtool, gives an error: Read in 256bytes WARNING: cannot decode VIN, try setting VIN to fix WARNING: cannot decode ImmmoID Traceback (most recent call last): File "eepromtool_04.py", line 794, in <module> File "eepromtool_04.py", line 731, in main File "eepromtool_04.py", line 70, in __init__ File "eepromtool_04.py", line 171, in parse IndexError: list index out of range [6660] Failed to execute script eepromtool_04 Do I have to have cluster code in ECU's EEPROM bin file now there is: - Cluster Code: 00 00 00 00 00 00 00 Hi You need to share your EEPROM... or we cant help. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: mdccode5150 on October 19, 2020, 05:10:39 PM Worked thanks! 8)
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Dominik89 on October 24, 2020, 07:38:35 PM can anyone read this file?
i always get ERROR: could not open input file Its an audi a4 b7 dash eeprom Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Dominik89 on October 24, 2020, 07:50:25 PM here a screenshot
What am i doing wrong? Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: nyet on October 24, 2020, 10:40:16 PM That would require eeprom.bin to be in C:\Users\x
You will want to back up and learn how cmd.exe works before doing anything else. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: mdccode5150 on November 05, 2020, 11:36:56 PM Did I miss something? or this program only does 512 EEPROM Files?
This is what I get: C:\>eepromtool_04.exe ecu.bin Read in 1024bytes Found 1024b bin - parsing as a R32 bin - experimental ERROR: 1024byte file detected, but the last 512bytes are not all padded with 0xFF, this file is may be a corupt dump, a cluster dump or something other than an eeprom dump, open it with a hex editor - if this is a valid eeprom please post the file and vehicle info on the thread for this tool EEPROM Status: - Type: ECU_eeprom - Version: Immo3 - VIN: WVGBC67L74D009484 - SKC: 05166 - Immobiliser: On - Checksum: Invalid Checksum - Size: 1024bytes - 512bytes expected, check this is a eeprom bin - Cluster Code: EE 7A 20 4B 57 1C 1B - P0601 DTC: not set - Immo ID: VWZ3Z0C5075067 - Softcoding ID: 0133 - Tuner Tag: Not Set - Flash Programming (successful): 2 - Flash Programming (attempts): 2 C:\> Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: mdccode5150 on November 05, 2020, 11:38:07 PM Sorry here is the file
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: elektronik13 on November 12, 2020, 06:16:53 PM Sorry here is the file what should i do including eepromTitle: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: mdccode5150 on November 22, 2020, 11:17:50 PM I just wanted to know (at the time) if the EEPROM dump would work...But I found that it changed a lot more than the immo due to it being a 1024 size. I ended up just taking the immo, and checksum values from the generated dump and manually edited the original file.
Thanks Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: elektronik13 on November 23, 2020, 10:25:23 AM I just wanted to know (at the time) if the EEPROM dump would work...But I found that it changed a lot more than the immo due to it being a 1024 size. I ended up just taking the immo, and checksum values from the generated dump and manually edited the original file. that is, I understandThanks that you did it yourself and you don't need any help anymore Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Micaaacek on December 08, 2020, 01:33:44 PM Hello All,
can I use this program to change VIN, SKC, Cluster code and Immo ID in ECU bin file ? I have similar problem as user "stranger_in_distress". I want to use AUQ ECU with AUM engine with Immo ON. I read that stranger_in_distress solved it, but its almost 6 years ago. I succesfully changed VIN in eeprom file via this program but change of SKC, Cluster code and Immo ID is not possible :-\ Do I something wrong ? Because command line shows "Not Yet Supported for ECU Bins". C:\>e2t.exe usage: e2t.exe [-h] --in INFILE [--out OUTFILE] [--status] [--immo IMMO] [--vin VIN] [--skc SKC] [--cc CC] [--ii II] [--pair PAIR] [--fixcs] [--nofixcs] [--cluster] [--force] e2t.exe: error: argument --in is required C:\>e2t.exe --in HN.bin --vin TMBBL21U838684718 --out HN_VIN.bin Read in 512bytes Setting VIN to TMBBL21U838684718 - Setting backup pages - Correcting checksums - Write Successful C:\>e2t.exe --in HN_VIN.bin --skc 00679 --out HN_VIN_SKC.bin Read in 512bytes Not Yet Supported for ECU Bins Traceback (most recent call last): File "eepromtool_04.py", line 794, in <module> File "eepromtool_04.py", line 769, in main AttributeError: ecueeprom instance has no attribute 'setSKC' [4452] Failed to execute script eepromtool_04 Thanks. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: bamofo on December 09, 2020, 09:09:15 AM Hello All, can I use this program to change VIN, SKC, Cluster code and Immo ID in ECU bin file ? I have similar problem as user "stranger_in_distress". I want to use AUQ ECU with AUM engine with Immo ON. I read that stranger_in_distress solved it, but its almost 6 years ago. I succesfully changed VIN in eeprom file via this program but change of SKC, Cluster code and Immo ID is not possible :-\ Do I something wrong ? Because command line shows "Not Yet Supported for ECU Bins". C:\>e2t.exe usage: e2t.exe [-h] --in INFILE [--out OUTFILE] [--status] [--immo IMMO] [--vin VIN] [--skc SKC] [--cc CC] [--ii II] [--pair PAIR] [--fixcs] [--nofixcs] [--cluster] [--force] e2t.exe: error: argument --in is required C:\>e2t.exe --in HN.bin --vin TMBBL21U838684718 --out HN_VIN.bin Read in 512bytes Setting VIN to TMBBL21U838684718 - Setting backup pages - Correcting checksums - Write Successful C:\>e2t.exe --in HN_VIN.bin --skc 00679 --out HN_VIN_SKC.bin Read in 512bytes Not Yet Supported for ECU Bins Traceback (most recent call last): File "eepromtool_04.py", line 794, in <module> File "eepromtool_04.py", line 769, in main AttributeError: ecueeprom instance has no attribute 'setSKC' [4452] Failed to execute script eepromtool_04 Thanks. You can or PM me and ill update it for you! Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Micaaacek on December 09, 2020, 01:27:25 PM You can or PM me and ill update it for you! Thank you for offer, but fortunately it has been fixed. I found program "VisualME7Logger" and this cool software did what i needed to do. After that ECU works fine in car without any problem and I hope so. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: nyet on December 09, 2020, 01:28:45 PM Thank you for offer, but fortunately it has been fixed. I found program "VisualME7Logger" and this cool software did what i needed to do. After that ECU works fine in car without any problem and I hope so. ? how did that fix immo? Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Micaaacek on December 09, 2020, 02:19:10 PM ? how did that fix immo? Immo is ON and works. Here is what I did: 1) Downloaded E2prom from HJ ECU (AUM) and from HN ECU (AUQ) 2) Opened HJ E2prom in VisualME7Logger and copy VIN, SKZ, Immo PIN and Cluster code to notepad 3) Opened HN E2prom in VisualME7Logger and replace VIN, SKZ, Immo PIN and Cluster code by data from HJ (notepad) 4) Saved updated E2prom with checksum routine 5) Flashed to ECU and installed ECU to car I dont know if this is correct procedure, but it works without any DTCs and I have tried more than 20 starts of engine, I drove more than 50 km and its still OK. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: d3irb on December 09, 2020, 02:42:58 PM ? how did that fix immo? visualme7logger actually has an EEPROM tool in it, blew my mind too: https://github.com/sbloom82/VisualME7Logger/blob/master/VisualME7Logger.Output/EEPROM.cs Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Micaaacek on December 12, 2020, 02:34:00 PM During testing I found small bug. When I tried to pair Skoda's cluster and ECU bin I found that this SW only accept Immo ID with 13 characters. Skoda uses IMMO ID with 14 characters.
Can anyone confirm this ? C:\>e2.exe --in cluster.bin --out cluster_paired.bin --pair ecu.bin Read in 2048bytes Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force) Read in 512bytes Setting VIN to TMBUR41U038686255 Setting Immo ID to SKZ7Z0B1704024 Setting SKC to 00648 Cluster updated to: EEPROM Status: - Type: Cluster - VIN: TMBUR41U038686255 (Skoda 2003 - Octavia 96-03, Dresden; Vrchlabi) - SKC: 0648 - Cluster Code: EC 88 B1 E4 9A F4 CE - Immo ID: SKZ7Z0B170402 Writing 2048kb cluster eeprom bin to: cluster_paired.bin - Write Successful This tool cannot set checksum for cluster bins, so you must force the cluster to reset the checksum by using VCDS to update the cluster softcoding (setting it to the same value will force the update) C:\>e2.exe --in cluster_paired.bin Read in 2048bytes Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force) EEPROM Status: - Type: Cluster - VIN: TMBUR41U038686255 (Skoda 2003 - Octavia 96-03, Dresden; Vrchlabi) - SKC: 0648 - Cluster Code: EC 88 B1 E4 9A F4 CE - Immo ID: SKZ7Z0B170402 Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: elektronik13 on December 12, 2020, 06:40:05 PM During testing I found small bug. When I tried to pair Skoda's cluster and ECU bin I found that this SW only accept Immo ID with 13 characters. Skoda uses IMMO ID with 14 characters. I think of the VW group always uses the ID of 14 charactersCan anyone confirm this ? C:\>e2.exe --in cluster.bin --out cluster_paired.bin --pair ecu.bin Read in 2048bytes Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force) Read in 512bytes Setting VIN to TMBUR41U038686255 Setting Immo ID to SKZ7Z0B1704024 Setting SKC to 00648 Cluster updated to: EEPROM Status: - Type: Cluster - VIN: TMBUR41U038686255 (Skoda 2003 - Octavia 96-03, Dresden; Vrchlabi) - SKC: 0648 - Cluster Code: EC 88 B1 E4 9A F4 CE - Immo ID: SKZ7Z0B170402 Writing 2048kb cluster eeprom bin to: cluster_paired.bin - Write Successful This tool cannot set checksum for cluster bins, so you must force the cluster to reset the checksum by using VCDS to update the cluster softcoding (setting it to the same value will force the update) C:\>e2.exe --in cluster_paired.bin Read in 2048bytes Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force) EEPROM Status: - Type: Cluster - VIN: TMBUR41U038686255 (Skoda 2003 - Octavia 96-03, Dresden; Vrchlabi) - SKC: 0648 - Cluster Code: EC 88 B1 E4 9A F4 CE - Immo ID: SKZ7Z0B170402 Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Micaaacek on December 13, 2020, 03:22:17 AM I think of the VW group always uses the ID of 14 characters On the first page of this topic are some examples with Audi and there is only 13 characters in Immo ID. However I have tried to open updated bin of cluster in another SW and it seems that Immo ID has 14 characters. It looks like its only display bug. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: elektronik13 on December 13, 2020, 03:54:20 PM On the first page of this topic are some examples with Audi and there is only 13 characters in Immo ID. However I have tried to open updated bin of cluster in another SW and it seems that Immo ID has 14 characters. YesIt looks like its only display bug. when it comes to ECU EEPROM 95040 This program has a bug Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Nic88 on January 31, 2021, 11:21:00 PM hi,
can someone please point me in the right direction. using Argdubs tool i pulled the skc which was 65535. that never worked on vcds when i tried to program the replacement ecu to the cluster. i then read this links and downloaded the tool of github and ran that. below is the outputs. it says it disabled the immo successfully and wrote it back but it never. can someone please let me know what im doing wrong with the tools or is there a way to get the correct ecu skc. c:\users\nic\desktop\eepromtool --in file.bin --immo off --out immooff.bin Read in 512bytes Settings Immobiliser: Off Immobiliser OFF - Setting backup pages -Correcting checksums -write successful c:\users\nic\desktop\eepromtool --in immoff.bin --status Read in 512bytes EEprom Status - Type: ECU_eeprom -Version: Immo3 -Vin: XXXXXXXXXXXXX SKC 65535 Immoboliser: OFF -Checksum: OK -Size: 512Bytes -Cluster Code: 00 00 00 00 00 00 00 -P0601 DTC: nt set -Immo ID: XXXXXXXXX -Softcoding ID: 0031 _Tuner tag: _Flash Programming <successful>:0 -Flash Programming <attempts>:0 Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: macxxx on February 01, 2021, 12:22:45 AM Wrote you in the second topic - its immo2 so you dont need pin from ecu , just from cluster
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Nic88 on February 01, 2021, 01:32:20 AM yeah macxxx, i saw that afterwards. its odd though that the tool says its immo3. and on that i actually tried the Immo2 adaptation on vcds and it didnt work. il get that dumps for you and post it in the next hour
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: macxxx on February 01, 2021, 01:49:12 AM If you have immo off adaptation wont work
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Nic88 on February 01, 2021, 02:07:22 AM so i just went to do the adaptation again on the car... this time login into the instrument module first. (even though ross tech doesn't mention that step) and it worked, car is idling. so yes definitely was a immo 2 ecu. i think what confused me was that the output said the ecu was immo3 when it wasnt. thanks for pointing that out macxxx
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: macxxx on February 02, 2021, 02:32:11 PM You should never trust any software for 100% ;) For me its quicker to use hex editor and calculator that this soft
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Nic88 on March 12, 2021, 10:03:40 PM hi guys, so im back with another build that came my way in the week. long story short, its an AUQ mk4 jetta that had a fried ecu due to dodgy 02 sensor connections. i got hold of a audi AUM ecu and tried the vcds adaptation but that fails and says "system not ok". on another thread i see the guys mentioning a difference with the immobilizers that can cause this, but the last comments are in 2014 so dont really want to resurrect that . what would the best route be, just remove immo off the audi ecu or transfer the eeprom over from the fried ecu. the car still starts with the fried ecu, its just the throttle that is dead. seeing as my last issue i had was on a immo 2 ecu i didnt need to play around with the tools that much. if i do attempt the immo off, can i do it all with this tool and write it to the ecu plugged in or do i have to go the route of grounding the pin etc, ideally i dont want to mess around with the actual ecu... thanks in advance
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Nic88 on March 13, 2021, 11:20:05 AM Forget the above. After spending a few hours trying to write the eeprom with the ecu in the car and failing. I took a old harness and cut the obd and ecu plugs off and made a bench harness. Wrote the new file to the ecu now I'm sorted. Thanks to the guys that wrote the tools... May the car God's bless you
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: mourison on June 01, 2021, 03:14:15 PM Hi,
Does anyone have an EEPROM bin from a new unpaired unit? I'm trying to figure out how to make the old "new", so I'd like to compare the differences :) Thank you Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: bamofo on June 02, 2021, 01:43:39 PM Hi, Does anyone have an EEPROM bin from a new unpaired unit? I'm trying to figure out how to make the old "new", so I'd like to compare the differences :) Thank you Look up Virgin on this site and you will find a few. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Usernameno1willtake on July 21, 2021, 11:38:06 AM Looking for details how to match a 95040 virgin to an original cluster IMMO ON. i dont want anyone to do it for me i would like to know what goes where cause when i make it manually in hxd the vin doesn show up right nor does the immo id. i will link all files (original Cluster 4b092981P, Virgin_95040 and my "edited one 95040chksm" i thought to be right.)
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Usernameno1willtake on July 21, 2021, 11:41:46 AM Looking for details how to match a 95040 virgin to an original cluster IMMO ON. i dont want anyone to do it for me i would like to know what goes where cause when i make it manually in hxd the vin doesn show up right nor does the immo id. i will link all files (original Cluster 4b092981P, Virgin_95040 and my "edited one 95040chksm" i thought to be right.) this is trying to use the pair command with eepromtool_04 C:\ME7>eepromtool_04 --in cluster.bin Read in 2048bytes Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force) WARNING: Cluster Code Block 1 and 2 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: Cluster Code Block 1 and 3 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: Cluster Code Block 2 and 3 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: cannot decode VIN, try setting VIN to fix WARNING: cannot decode ImmmoID EEPROM Status: - Type: Cluster - VIN: - SKC: 02553 - Cluster Code: 45 A4 B6 64 C8 E8 03 - Immo ID: C:\ME7>eepromtool_04 --in virgin_95040.bin Read in 512bytes WARNING: cannot decode ImmmoID EEPROM Status: - Type: ECU_eeprom - Version: Immo2 - VIN: XXXXXXXXXXXXXXXXX - SKC: 065535 - Immobiliser: Off - Checksum: Invalid Checksum - Size: 512bytes - Cluster Code: 00 00 00 00 00 00 00 - P0601 DTC: not set - Immo ID: - Softcoding ID: 65535 - Tuner Tag: - Flash Programming (successful): 0 - Flash Programming (attempts): 0 C:\ME7>eepromtool_04.exe --in cluster.bin --out paired95040.bin --pair Virgin_95040.bin Read in 2048bytes Detected 2kb bin, parsing as a cluster eeprom (prevent this guessing by using --force) WARNING: Cluster Code Block 1 and 2 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: Cluster Code Block 1 and 3 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: Cluster Code Block 2 and 3 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: cannot decode VIN, try setting VIN to fix WARNING: cannot decode ImmmoID Read in 512bytes WARNING: cannot decode ImmmoID Setting VIN to XXXXXXXXXXXXXXXXX WARNING: Cluster Code Block 1 and 2 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: Cluster Code Block 1 and 3 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: Cluster Code Block 2 and 3 do not match, this may indicate an error in the file, or a format not supported by this tool WARNING: cannot decode ImmmoID ERROR: VIN number must be 14 characters ERROR: Could not set Immo ID Traceback (most recent call last): File "eepromtool_04.py", line 794, in <module> File "eepromtool_04.py", line 782, in main File "eepromtool_04.py", line 631, in pair File "eepromtool_04.py", line 620, in setImmoID NameError: global name 'exit' is not defined [8568] Failed to execute script eepromtool_04 Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: stuydub on July 21, 2021, 01:26:52 PM if your immo 2 u dont need pins or anything just use vcds and adapt ecu in adaption channel 0
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: doublerwest on July 21, 2021, 02:05:47 PM so i just went to do the adaptation again on the car... this time login into the instrument module first. (even though ross tech doesn't mention that step) and it worked, car is idling. so yes definitely was a immo 2 ecu. i think what confused me was that the output said the ecu was immo3 when it wasnt. thanks for pointing that out macxxx If this tool says immo3 then its prolly immo 3 file.. immo 3 files will work on an immo 2 box figured that out the hard way ...I set my guage cluster to immo3 settings tinkering with it vcds obdeleven couldnt fiqure out what to change back to correct it late nights will do that to you and had to port in a immo 3 file to get it to stop throwing a data bus code of some sort pain in the arse...Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Usernameno1willtake on July 21, 2021, 04:32:44 PM if your immo 2 u dont need pins or anything just use vcds and adapt ecu in adaption channel 0 i guess im a bit confused then, so using the 95040 skc logging into the ecu with the virgin 95040 (dont have original) then adapt it to the cluster? nothing more? Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: 6iller on September 11, 2021, 01:32:59 AM Thanks, great work turbat Can confirm that eepromtool can immo off a ME 7.1.1, Golf 5, R32, 022906032CD, with 95160 eeprom. Read in 2048bytes Setting Immobiliser: Off - Immobiliser Off - Setting backup pages - Correcting checksums - Write Successful Read in 2048bytes EEPROM Status: - Type: ECU_eeprom - Version: Immo2 - VIN: WVWZZZ1KZ6W0..... (VW 2006 - Golf and Jetta 5, 6, Wolfsburg, Germany) - SKC: 06520 - Immobiliser: Error, set Immo - Current values: 0x12 = 0x04, 0x22 = 0x04 - Checksum: Invalid Checksum - Size: 2048bytes - 512bytes expected, check this is a eeprom bin - Cluster Code: 87 9E 5D 0B EA F2 5F - P0601 DTC: not set - Immo ID: VWZ7Z0E27..... - Softcoding ID: 0132 - Tuner Tag: Not Set - Flash Programming (successful): 4 - Flash Programming (attempts): 149 Hey guys. I have an ECU 022906032KF (HW 04) with 95160 eeprom in a Golf 5 R32 and want just to read an SKC. Could you please explain me in steps how it should be done? Command INFILE would be enough? To specify the input file I created a blank txt and renamed it into infile.bin. But it doesn't work so. Do I have to dismantle the ECU and enter into the boot mode? Or it's possible to do it on the car via OBD? Actually I wanted to try me7_95040 after I successfully tested it on ME 7.5 from my 1.8T. But as I found out the memory and structure of R32 G5 ECU is other so I didn't risk it... Besides that I don't know how to enter to bootmode on it. Thanks Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: bamofo on September 13, 2021, 08:40:22 AM Hey guys. I have an ECU 022906032KF (HW 04) with 95160 eeprom in a Golf 5 R32 and want just to read an SKC. Could you please explain me in steps how it should be done? Command INFILE would be enough? To specify the input file I created a blank txt and renamed it into infile.bin. But it doesn't work so. Do I have to dismantle the ECU and enter into the boot mode? Or it's possible to do it on the car via OBD? Actually I wanted to try me7_95040 after I successfully tested it on ME 7.5 from my 1.8T. But as I found out the memory and structure of R32 G5 ECU is other so I didn't risk it... Besides that I don't know how to enter to bootmode on it. Thanks Not supported correctly with that tool. 95160 i do by hand. There are differences. If you need help PM me. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Nosfogger on June 23, 2022, 05:48:42 PM UPDATE: Eeepromtool is now hosted on github. The most recent release will always be located in: https://github.com/turboat/eepromtool/releases/ Source code is in: https://github.com/turboat/eepromtool Pull requests are welcome :) Eepromtool is a command line tool, either run using 'python eepromtool_04.py' or 'eepromtool_04.exe'. If it just flashes up and disappears, this is because it is a command line tool. If you dont know what a command line tool is, you probably shouldnt be trying to edit your ECU. Displaying Information To simply display the info in a bin called INFILE, use: eepromtool_04.exe INFILE For example with an ecu eeprom: Code: eepromtool_04.exe ecu.bin With a cluster eeprom: Code: eepromtool_04.exe cluster.bin Immo On/Off To set immo status, you must specify input file, output file and desired immo status. Checksums will be corrected automatically unless you specify --nofixcs. For example: Code: eepromtool_04.exe --in ecu.bin --immo off --out ecu_off.bin So I ran this on my 2002 audi allroad 2.7t. To turn off the immo. It ran fine. I then ran the verification. Everything looks fine says immo off and it worked great. Installed the ecu back Into the car. Light on cluster still flashing and car still just starts and dies right away. Any thoughts on what I'm. Missing? Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: arved on September 27, 2022, 05:48:36 AM How can i download the exe file?
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: dal on September 27, 2022, 06:34:17 AM Click on the github repo /releases link (first link). Locate file name 'eepromtool_04.exe' and click on it.
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: goliat17 on January 23, 2023, 10:05:11 AM UPDATE: Eeepromtool is now hosted on github. The most recent release will always be located in: https://github.com/turboat/eepromtool/releases/ Source code is in: https://github.com/turboat/eepromtool Pull requests are welcome :) Eepromtool is a command line tool, either run using 'python eepromtool_04.py' or 'eepromtool_04.exe'. If it just flashes up and disappears, this is because it is a command line tool. If you dont know what a command line tool is, you probably shouldnt be trying to edit your ECU. Displaying Information To simply display the info in a bin called INFILE, use: eepromtool_04.exe INFILE For example with an ecu eeprom: Code: eepromtool_04.exe ecu.bin With a cluster eeprom: Code: eepromtool_04.exe cluster.bin Immo On/Off To set immo status, you must specify input file, output file and desired immo status. Checksums will be corrected automatically unless you specify --nofixcs. For example: Code: eepromtool_04.exe --in ecu.bin --immo off --out ecu_off.bin Hello eepromtool_04 champions!!! I'm French, so apologies in advance for the deepl translation!!! I need help to solve a problem of modifying several mapping bin files after using eepromtool_04 in command line on a single bin file! At first sight my files are still ok, but they are apparently filled with values like fffffffffff or aaaaaaaaa, yyyyyyyyy in front of and behind the bin file when I open it with a hex editor! I'm currently working on an eeprom 25320A to fix an immo off problem with julie emulator ! any help will be welcome ! thanks in advance Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: EuroXs4 on June 25, 2023, 05:36:02 PM Hey guys so I suspect I may have a corrupt dump in my 95P08 eeprom cause I keep getting p1681 fault code after key cycle and I have tried the work around and so on on this me7.1.1 vw phaeton ecu with immo. Can I write any 95P08 eeprom? and then try adapting again?
Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: ClusterModz on August 22, 2023, 10:10:00 AM anything new for the rb4 clusters? looking to adapt a new cluster to original ecu. i have both eeproms ready and a post ive made with no input yet.
http://nefariousmotorsports.com/forum/index.php?topic=22071.0title= Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: EuroXs4 on August 25, 2023, 12:05:23 PM anything new for the rb4 clusters? looking to adapt a new cluster to original ecu. i have both eeproms ready and a post ive made with no input yet. http://nefariousmotorsports.com/forum/index.php?topic=22071.0title= New meaning brand new cluster or NEW(used donor)? Each has its own crypto mask and checksum. Title: Re: EepromTool - decodes/modifies eeprom bins to immo off, set vin, get SKC, etc Post by: Roggy on October 26, 2023, 09:37:58 AM Hi, worked great so far. But i got a situation going on, is there a way i could write directly to the cluster the modified eeprom.bin using the command line? cause eeprom programmer , vag k can etc doesn't connect to the new cluster and cant do it that way, the original cluster does get recognized but with the "new" one i simply get the "ecu not found" and stuff.
Thanks in advance. |