If you're like me you started off not knowing how to do anything. And as time went on you learn more and more. Well I see people like me and I wanna help. I also see that people need there checksum corrected and maybe don't understand how-to do it. The info on how to do it may not make sense to everyone. Like me at 1st, I didn't understand command prompts very well. So here is a quick guide one how-to correct checksum's with Nyet's ME7sum. I have also contacted MTX for a plugin but have yet to hear back from them in over a week or so.
If you make changes at all to a .bin you will from my experience will have errors. I also have noticed that if you mod a file and then correct it and then wanna go back and edit it that you edit your "NEW" corrected file as I had two .bin files get corrupted by modding a .bin and the throttle body would just start clicking along with a flashing CEL and no start. This was cause it had errors and required me to boot mode recover my ecu.DOWNLOAD LATEST RELEASE OF ME7SUM
http://nyetwurk.github.io/ME7Sum/**UPDATE** (LINK DEAD thread deleted, sorry I will post new instructions for adding ME7Sum and Check into TunerPro again)
Just tonight I figured out a way to add ME7sum and ME7Check to TunerPro. Click link below to go to that thread.
http://nefariousmotorsports.com/forum/index.php?topic=5877.0title=-----------------------------------------------------------
Here is short way (by ddillenger):Download the file (me7sum), put it in your user directory (C:\Documents and Settings\usernamehere) along with the bin (we're going to call it IN for this example).
Hit START, RUN, and type: CMD
Then, type:
me7sum IN.bin OUT.bin
You'll see the program running in cmd, and will end up with a new file with the checksums corrected in the same directory you placed the previously mentioned files (C:\Documents and Settings\usernamehere). The corrected file will be named OUT.bin (or whatever you select when typing the command)
Longer Version: ----------------
*Now below is examples. Meaning this is where I put my files, and what I type is special to where my files are located. You will have to adjust for however you set things up. DDillenger suggests not to use a root folder, so please make changes to my info if you follow his advice, I am not of aware why not to, he has more knowledge in that department.
To start off download the zip file me7sum-vx.x.x.zip from http://nyetwurk.github.io/ME7Sum/
(Please be aware that there is a know issues with correction of some checksums for some errors, in this event you will need to find someone to correct the file for you that maybe has a MTX plugin).
Now extract me7sum-vx.x.x.zip and put it into folder of your choice.
Now take your .bin file and put it in same folder to make it simple.
Now you want to click the start button and in the search box type cmd to open the command prompt window.
Now see pic below. You will need to type cd.. and then cd.. again to get to root folder.
After that you will direct cmd where to find your me7sum program.
File location is how I have it, adjust to your location if needed, follow the same format with \ to indacate folders.
Now follow info in picture below
Please note, there is a grammar issues in picture. I ment to say put a new name for your NEW corrected file so you know its fixed/corrected. Do not name it the same thing as your corrupted file as it will not output a file.
After you type the above command the program will fly throw a bunch of words, you can look back and see what was corrected if you want. But if you did everything correctly you should see a message at bottom like one picture below.
Now you have a corrected file and are ready to flash.
Now if you wanna check your file, you can run cmd and type \me7sum (space) (.bin file name) you will get error check or better know as ME7Check of your file and will give you info. Again these are examples please adjust for your file locations and names of files.
I hope this helps people who might have not understood exactly how to use Nyet's ME7sum program. Please click Applaud to the left under my user ID and pic where is says Karma if this helped you. Good luck and happy Tuning and Flash folks!
BRO. the one place to get some help on this subject and your pictures are no longer there... WTF man nhaha
this was my attempt with the info provided.
C:\Users\Matt>C:\Users\Matt\Desktop\me7sum.exe "C:\Users\Matt\Desktop\551M Bosch.bin" "C:\Users\Matt\Desktop\551M Bosch.log"
ME7Sum (v1.1.2) [Management tool for Bosch ME7.x firmwares]
Inspiration from Andy Whittaker's tools and information.
Written by 360trev and nyet [BSD License Open Source].
Attempting to open firmware file 'C:\Users\Matt\Desktop\551M Bosch.bin'
Step #1: Reading ROM info ..
Searching for EPK signature...OK
Searching for ECUID table...OK
EPK : '40/1/ME7.1/5/6005.01//22m/DstC2o/011200//'
Part Number : '8D0907551M '
Engine ID : '2.7l V6/5VT '
SW Version : '0002'
HW Number : '0261207143'
SW Number : '1037360857'
Step #2: Reading ROMSYS ..
Startup section: word[0x008000]+word[0x00FFFE]
@08038 Add=0x00013225 CalcAdd=0x00013225 ADD OK
All param page: word[0x010000]+word[0x01FFFE]
@01b9b0 Add=0x00971D CalcAdd=0x00971D ADD OK
Step #3: Finding CRC table(s) ..
Searching for CRC table(s)...OK
CRC table(s) OK
Step #4: Reading RSA signatures ..
Searching for RSA offset #0...missing
Searching for RSA offset #1...missing
Step #5: Reading Main Data CRC/Checksums ..
Searching for main data CRC pre block...missing
Searching for main data CRC/csum blocks...OK
Searching for main data CRC offsets...OK
Searching for main data checksum offsets...missing
Main CRCs:
1) 0x010002-0x013FFE @7a866 CRC: FE9538BC CalcCRC: FE9538BC CRC OK
2) 0x014252-0x017F4E @7a86c CRC: 8366887D CalcCRC: 8366887D CRC OK
3) 0x018192-0x01FBB0 @7a872 CRC: 4D9F2227 CalcCRC: 4D9F2227 CRC OK
Step #6: ROMSYS Program Pages
Program pages: 8k page first+last in 0x0000-0xFFFF and 0x20000-0xFFFFF
@00803c Add=0xABDDC5 CalcAdd=0xABDDC5 ADD OK
Step #7: Reading Main Program Checksums ..
Searching for main program checksum..OK
ROM Checksum Block Offset Table @1e75a [16 bytes]:
1) 0x000000-0x00FBFF CalcChk: 47AF0B2F
0x00FC00-0x01FFFF CalcChk: 28F21610 CalcCRC: 6CB22B89 SKIPPED
2) 0x020000-0x0FFFFF CalcChk: 9CC24110
@fffe0 Chk: 9CC24110 CalcChk: 9CC24110 OK (i)
Step #8: Reading Multipoint Checksum Blocks ..
Searching for multipoint block descriptor #1...OK
1) <14224> 0x024000-0x02658D Chk: 0B08F804 CalcChk: 0B08F804 OK
2) <14234> 0x014000-0x014243 Chk: 00540FE9 CalcChk: 00540FE9 OK (i)
3) <14244> 0xFFFFFFFF-0xFFFFFFFF END
Multipoint #1: [2 blocks x <16> = 32 bytes]
Searching for multipoint block descriptor #2...OK
1) <1fbb2> 0x000000-0x003FFF Chk: 0FA0F5CF Boot: (whitelisted) OK
2) <1fbc2> 0x004000-0x007FFF Chk: 0F4716B3 Boot: (whitelisted) OK
3) <1fbd2> 0x000000-0x003FFF Chk: 0FF728A4 CalcChk: 0FF728A4 OK
..........
64) <1ffa2> 0x0F4000-0x0F7FFF Chk: 1FFFE000 CalcChk: 1FFFE000 OK
65) <1ffb2> 0x0F8000-0x0FBFFF Chk: 1FFFE000 CalcChk: 1FFFE000 OK
66) <1ffc2> 0x0FC000-0x0FFFFF Chk: 1FFDE002 CalcChk: 1FFDE002 OK
Multipoint #2: [66 blocks x <16> = 1056 bytes]
Step #9: Looking for rechecks ..
*** Found 73 checksums in C:\Users\Matt\Desktop\551M Bosch.bin
*** No errors were found and so no "C:\Users\Matt\Desktop\551M Bosch.log" was generated.
C:\Users\Matt>
