|
SB_GLI
|
 |
« on: December 02, 2015, 07:14:37 AM »
|
|
|
Questions on how to run a command line utility, such as ME7Check or ME7Logger, seem to come up all the time on these forums. Here's a little video on how to make it a little easier on you command line noobers. https://www.youtube.com/watch?v=A4OQwGLncq0 |
|
|
|
|
Logged
|
|
|
|
|
k0mpresd
|
|
« Reply #1 on: December 02, 2015, 09:30:12 AM »
|
|
|
step #3 in the tutorial leaves a bit to be desired as far as an explanation goes. who's exactly are being stolen? still confused.  |
|
|
|
|
Logged
|
|
|
|
|
SB_GLI
|
|
« Reply #2 on: December 02, 2015, 09:54:51 AM »
|
|
|
step #3 in the tutorial leaves a bit to be desired as far as an explanation goes. who's exactly are being stolen? still confused. my advice. give up.. there's no hope for you.  |
|
|
|
|
Logged
|
|
|
|
|
|
|
dream3R
|
|
« Reply #4 on: December 02, 2015, 07:58:02 PM »
|
|
|
Nice, never seen that. If you use Windows you should really know your way around the cmd console, it helps so much, it's something that I encourage in training.... W+R cmd return and you're there!
|
|
|
|
|
Logged
|
|
|
|
|
Dave9n3
|
|
« Reply #5 on: December 06, 2015, 05:50:00 AM »
|
|
|
I only got into all this very recently! after flashing a none checksummed file onto my car after not really knowing i should have checked it and also not knowing how, i bricked my ecu.
This should be really helpful for some fellow noobs like myself!
|
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #6 on: December 07, 2015, 07:03:20 AM »
|
|
|
I only got into all this very recently! after flashing a none checksummed file onto my car after not really knowing i should have checked it and also not knowing how, i bricked my ecu.
This should be really helpful for some fellow noobs like myself!
Exactly plus remember the tab prompt auto completes sois faster as you can type lol |
|
|
|
|
Logged
|
|
|
|
QuickS4
Full Member
Karma: +6/-6
 Offline
Posts: 72
|
|
« Reply #7 on: December 13, 2015, 08:16:48 PM »
|
|
|
Drag and drop is great. I was playing with this file and changed a few things and saved it as a test file. Then proceeded to correct the checksums via me7sum and it found four errors, but didn't correct them. Am I doing something wrong or wrong in thinking ME7Sum, checks and corrects the checksum errors? where as ME7Check only checks for errors? Here's that I got back.
C:\Users\Otto>C:\me7\me7sum.exe "C:\Users\Otto\Documents\Tuning\ECU Files\S4 Stage 1 Comm
ct Bins & XDF\551M Hitachi test.bin"
ME7Tool (v1.0.1) [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\Otto\Documents\Tuning\ECU Files\S4 Stage 1 Com
ect Bins & XDF\551M Hitachi test.bin'
Step #1: Reading ROM info ..
Searching for EPK signature...OK
Searching for P/N...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]
@008038 Add=0x013225 CalcAdd=0x013225 ADD OK
Program pages: 8k page first+last in 0x0000-0xFFFF and 0x20000-0xFFFFF
@00803c Add=0xABDDC5 CalcAdd=0xABDDC5 ADD OK
All param page: word[0x010000]+word[0x01FFFE]
@01b9b0 Add=0x00971D CalcAdd=0x00971D ADD OK
Step #3: Reading RSA signatures ..
Searching for RSA offset #0...missing
Searching for RSA offset #1...missing
Step #4: Reading Main Data 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) Adr: 0x010002-0x013FFE @7a866 CRC: 214CD272 CalcCRC: D89C29DC ** NOT OK **
2) Adr: 0x014252-0x017F4E @7a86c CRC: 17B90F53 CalcCRC: EAA634D5 ** NOT OK **
3) Adr: 0x018192-0x01FBB0 @7a872 CRC: 7DE91383 CalcCRC: 7DE91383 CRC OK
Step #5: Reading Main Program Checksums ..
Searching for main program checksum..OK
ROM Checksum Block Offset Table @1e75a [16 bytes]:
1) Adr: 0x000000-0x00FBFF
0x00FC00-0x01FFFF SKIPPED CalcChk: 0x28E88FEA CalcCRC: 0xAC5B652C
2) Adr: 0x020000-0x0FFFFF
@fffe0 Chk: 0x9CC13A4C CalcChk: 0x9CC13A4C Main program checksum OK
Step #6: Reading Multipoint Checksum Blocks ..
Searching for multipoint block descriptor #1...OK
1) <14224> Adr: 0x024000-0x02658D Chk: 0x0B08F804 CalcChk: 0x0B08F804 OK
2) <14234> Adr: 0x014000-0x014243 Chk: 0x00540FE9 CalcChk: 0x00540FE9 OK
3) <14244> Adr: 0xFFFFFFFF-0xFFFFFFFF END
Multipoint #1: [2 blocks x <16> = 32 bytes]
Searching for multipoint block descriptor #2...OK
1) <1fbb2> Adr: 0x000000-0x003FFF Chk: 0x0FA0F5CF Boot: (whitelisted) OK
2) <1fbc2> Adr: 0x004000-0x007FFF Chk: 0x0F4716B3 Boot: (whitelisted) OK
3) <1fbd2> Adr: 0x000000-0x003FFF Chk: 0x0FF728A4 CalcChk: 0x0FF728A4 OK
4) <1fbe2> Adr: 0x004000-0x007FFF Chk: 0x0F68CD6E CalcChk: 0x0F68CD6E OK
7) <1fc12> Adr: 0x010000-0x013FFF Chk: 0x07211187 CalcChk: 0x0721D087 ** NOT OK **
8 ) <1fc22> Adr: 0x014000-0x017F4F Chk: 0x0E82B76F CalcChk: 0x0E82BDAF ** NOT OK **
Multipoint #2: [66 blocks x <16> = 1056 bytes]
*** Found 73 checksums in C:\Users\Otto\Documents\Tuning\ECU Files\S4 Stage 1 Community P
& XDF\551M Hitachi test.bin
*** WARNING! 4/4 uncorrected error(s) in C:\Users\Otto\Documents\Tuning\ECU Files\S4 Stag
ty Project Bins & XDF\551M Hitachi test.bin! ***
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #8 on: December 13, 2015, 09:42:36 PM »
|
|
|
Drag and drop is great.
I don't see how. It doesn't let you specify an output file if you actually want it. There is no substitute for really learning how things work. |
|
|
|
|
Logged
|
|
|
|
|
adam-
|
|
« Reply #9 on: December 14, 2015, 01:04:20 AM »
|
|
|
This. Sure, ME7Sum will run with the file that you've dropped, but how does it know where to save the new file; or what to call it? Running ME7Sum on it's own tells your its requirements.  |
|
|
|
|
Logged
|
|
|
|
jimmcgee5
Full Member
Karma: +7/-7
Offline
Posts: 201
|
|
« Reply #10 on: December 14, 2015, 07:53:39 AM »
|
|
|
Oh Man , the good old days of unzip.exe and unrar.exe  |
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #11 on: December 14, 2015, 08:02:38 AM »
|
|
|
Oh Man , the good old days of unzip.exe and unrar.exe config.sys |
|
|
|
|
Logged
|
|
|
|
|
dream3R
|
|
« Reply #12 on: December 14, 2015, 08:04:20 AM »
|
|
|
I don't see how. It doesn't let you specify an output file if you actually want it.
There is no substitute for really learning how things work.
There will be a GUI next |
|
|
|
|
Logged
|
|
|
|
QuickS4
Full Member
Karma: +6/-6
Offline
Posts: 72
|
|
« Reply #13 on: December 14, 2015, 08:07:14 AM »
|
|
|
For whatever reason I had thought me7sum would correct the corrupted file and leave it as such. Then I went back to read the how-to on me7sum and tried it that way and success. Not sure why I was under that incorrect impression that it would fix the existing file (guess we delete the bad file every time?). Thanks for helping me on that. On a side note, back when I first tried to correct the file, it had 4 errors. This time when I did the correct method, it found 6 errors and ofc corrected them. So my question is this, did scanning the first few times (assuming it was going to be fixed) by doing it the wrong way cause more errors? Or is it because it's still open in TunerPro (but hasn't had any changes since trying to correct the checksums)? Or is there a completely different reason? Awesome! Thanks for reopening my eyes. It's kinda like learning a new name, if I don't say it often, I'll forget it. Repetitive practice. There will be a GUI next Actually the GUI that's out there for ME7Check would work, wouldn't it with the changes over to make it ME7Sum? hahaha |
|
|
|
|
Logged
|
|
|
|
QuickS4
Full Member
Karma: +6/-6
Offline
Posts: 72
|
|
« Reply #14 on: December 14, 2015, 08:12:26 AM »
|
|
|
Here's the report of the correct checksum that found six errors, in case it helps to see it.
C:\Users\Otto>C:\Users\Otto\Documents\me7sum-v1.0.1\me7sum.exe "C:\Users\Otto\Documents\Tuning\ECU F
iles\S4 Stage 1 Community Project Bins & XDF\551M Hitachi test.bin" "C:\Users\Otto\Documents\Tuning\
ECU Files\S4 Stage 1 Community Project Bins & XDF\551M Hitachi test fixed.bin"
ME7Tool (v1.0.1) [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\Otto\Documents\Tuning\ECU Files\S4 Stage 1 Community Proj
ect Bins & XDF\551M Hitachi test.bin'
Step #1: Reading ROM info ..
Searching for EPK signature...OK
Searching for P/N...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]
@008038 Add=0x013225 CalcAdd=0x013225 ADD OK
Program pages: 8k page first+last in 0x0000-0xFFFF and 0x20000-0xFFFFF
@00803c Add=0xABDDC5 CalcAdd=0xABDDC5 ADD OK
All param page: word[0x010000]+word[0x01FFFE]
@01b9b0 Add=0x00971D CalcAdd=0x00971D ADD OK
Step #3: Reading RSA signatures ..
Searching for RSA offset #0...missing
Searching for RSA offset #1...missing
Step #4: Reading Main Data 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) Adr: 0x010002-0x013FFE @7a866 CRC: 214CD272 CalcCRC: D89C29DC ** FIXED **
2) Adr: 0x014252-0x017F4E @7a86c CRC: 17B90F53 CalcCRC: EAA634D5 ** FIXED **
3) Adr: 0x018192-0x01FBB0 @7a872 CRC: 7DE91383 CalcCRC: 7DE91383 CRC OK
Step #5: Reading Main Program Checksums ..
Searching for main program checksum..OK
ROM Checksum Block Offset Table @1e75a [16 bytes]:
1) Adr: 0x000000-0x00FBFF
0x00FC00-0x01FFFF SKIPPED CalcChk: 0x28E88FEA CalcCRC: 0xAC5B652C
2) Adr: 0x020000-0x0FFFFF
@fffe0 Chk: 0x9CC13A4C CalcChk: 0x9CC24175 ** FIXED **
Step #6: Reading Multipoint Checksum Blocks ..
Searching for multipoint block descriptor #1...OK
1) <14224> Adr: 0x024000-0x02658D Chk: 0x0B08F804 CalcChk: 0x0B08F804 OK
2) <14234> Adr: 0x014000-0x014243 Chk: 0x00540FE9 CalcChk: 0x00540FE9 OK
3) <14244> Adr: 0xFFFFFFFF-0xFFFFFFFF END
Multipoint #1: [2 blocks x <16> = 32 bytes]
Searching for multipoint block descriptor #2...OK
1) <1fbb2> Adr: 0x000000-0x003FFF Chk: 0x0FA0F5CF Boot: (whitelisted) OK
2) <1fbc2> Adr: 0x004000-0x007FFF Chk: 0x0F4716B3 Boot: (whitelisted) OK
3) <1fbd2> Adr: 0x000000-0x003FFF Chk: 0x0FF728A4 CalcChk: 0x0FF728A4 OK
4) <1fbe2> Adr: 0x004000-0x007FFF Chk: 0x0F68CD6E CalcChk: 0x0F68CD6E OK
Multipoint #2: [66 blocks x <16> = 1056 bytes]
*** Found 73 checksums in C:\Users\Otto\Documents\Tuning\ECU Files\S4 Stage 1 Community Project Bins
& XDF\551M Hitachi test.bin
Attempting to output corrected firmware file 'C:\Users\Otto\Documents\Tuning\ECU Files\S4 Stage 1 Co
mmunity Project Bins & XDF\551M Hitachi test fixed.bin'
├╛ Opening 'C:\Users\Otto\Documents\Tuning\ECU Files\S4 Stage 1 Community Project Bins & XDF\551M Hi
tachi test fixed.bin' file for writing
├╛ Writing to file
├╛ Validating size correct 1048576=1048576
├╛ All OK, closing file
*** DONE! 6/6 error(s) corrected in C:\Users\Otto\Documents\Tuning\ECU Files\S4 Stage 1 Community Pr
oject Bins & XDF\551M Hitachi test.bin! ***
|
|
|
|
|
Logged
|
|
|
|
|
