Pages: 1 ... 3 4 [5] 6 7 ... 9
Author Topic: ME7Sum: Open Source Checker/Corrector for ME7  (Read 179519 times)
AARDQ
Sr. Member
****

Karma: +11/-0
Offline Offline

Posts: 338


« Reply #60 on: November 09, 2014, 12:58:51 PM »

Sometimes i get this failure! I 've integrated me7sum and me7check in tuner pro's custom tools. What i'm doing wrong?

No spaces in path names allowed, e.g. Tunerpro Files won't work.  The prog thinks 'Files' is the name of the bin, and, of course, it isn't.
Logged
SB_GLI
Hero Member
*****

Karma: +115/-10
Offline Offline

Posts: 1022


« Reply #61 on: November 10, 2014, 02:48:34 PM »

Spaces should work fine as long as you put quotes around the file names.  Although it is wise advice, especially when dealing with open source / free software that uses file IO, to make sure your folders don't have spaces in them.
Logged
slappynuts
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 49


« Reply #62 on: May 14, 2015, 06:52:27 PM »

I am having issues trying to run a bigger MAF on this ecu B0906018P. ME7 sum says it corrected everything and it is good, but ME7check says it fails.
« Last Edit: May 15, 2015, 10:28:41 AM by slappynuts » Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12232


WWW
« Reply #63 on: May 14, 2015, 07:00:50 PM »

Please don't make me download those files, cut and paste the output you are seeing.
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
slappynuts
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 49


« Reply #64 on: May 15, 2015, 03:39:13 PM »

Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>cd..

C:\Windows>cd..

C:\>me7\me7sum me7\bigmafstockatwgood.bin me7\bigmafstockatwgood_fix.bin
ME7Tool (v1.0.3) [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 'me7\bigmafstockatwgood.bin'

Step #1: Reading ROM info ..
 Searching for EPK signature...OK
 Searching for ECUID table...OK
 EPK         : '42/1/ME7.5/3/4012.00//F22id/Dst06g/250899/'
 Part Number : '4B0906018P  '
 Engine ID   : '1.8L R4/5VT     '
 SW Version  : '0006'
 HW Number   : '0261206537'
 SW Number   : '1037352750'

Step #2: Reading ROMSYS ..
 Startup section: word[0x008000]+word[0x00FFFE]
 @008038 Add=0x007CD1 CalcAdd=0x007CD1  ADD OK
 Program pages: 8k page first+last in 0x0000-0xFFFF and 0x20000-0x7FFFF
 @00803c Add=0x3972A5 CalcAdd=0x3972A5  ADD OK
 All param page: word[0x010000]+word[0x01FFFE]
 @01b560 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: Finding CRC table(s) ..
 Searching for CRC table(s)...OK
 CRC table(s) OK

Step #5: Reading Main Data Checksums ..
 Searching for main data CRC pre block...missing
 Searching for main data CRC/csum blocks...missing
 Falling back to default 512k CRC blocks...OK
 Searching for main data CRC offsets...OK
 Searching for main data checksum offsets...missing
 Main CRCs:
 1) 0x010000-0x013FFF @70000 CRC: AB605C52 CalcCRC: E2FDA8ED    ** FIXED **
 2) 0x014300-0x017F67 @70006 CRC: 534DE7C2 CalcCRC: 534DE7C2    CRC OK
 3) 0x018191-0x01FBFF @7000c CRC: A323DCA6 CalcCRC: A323DCA6    CRC OK

Step #6: Reading Main Program Checksums ..
 Searching for main program checksum..OK
 ROM Checksum Block Offset Table @1dfec [16 bytes]:
 1) 0x000000-0x00FBFF CalcChk: 47EF557E
    0x00FC00-0x01FFFF CalcChk: 2CEDD2F0 CalcCRC: 668F1A38 SKIPPED
 2) 0x020000-0x07FFFF
    <7ffe0>  Chk: D81EDC5F CalcChk: D81F6097 ** FIXED **

Step #7: Reading Multipoint Checksum Blocks ..
 Searching for multipoint block descriptor #1...OK
 1) <14224>  0x024000-0x02658D Chk: 0AFD060F CalcChk: 0AFD060F OK
 2) <14234>  0x014000-0x014243 Chk: 005CAABC CalcChk: 005CAABC OK (i)
 3) <14244>  0xFFFFFFFF-0xFFFFFFFF  END
 Multipoint #1: [2 blocks x <16> = 32 bytes]
 Searching for multipoint block descriptor #2...OK
 1) <1fc00>  0x000000-0x003FFF Chk: 0FA0F5CF Boot: (whitelisted) OK
 2) <1fc10>  0x004000-0x007FFF Chk: 0F4716B3 Boot: (whitelisted) OK
 3) <1fc20>  0x000000-0x003FFF Chk: 0FA0F5CF CalcChk: 0FA0F5CF OK
 4) <1fc30>  0x004000-0x007FFF Chk: 0F4716B3 CalcChk: 0F4716B3 OK
 Multipoint #2: [34 blocks x <16> = 544 bytes]

*** Found 41 checksums in me7\bigmafstockatwgood.bin

Attempting to output corrected firmware file 'me7\bigmafstockatwgood_fix.bin'
├╛ Opening 'me7\bigmafstockatwgood_fix.bin' file for writing
├╛ Writing to file
├╛ Validating size correct 524288=524288
├╛ All OK, closing file

*** DONE! 5/5 error(s) in me7\bigmafstockatwgood.bin corrected in me7\bigmafstoc
katwgood_fix.bin! ***

C:\>







me7check v1.12 (c) mki, 06/2004-05/2012
Checking file C:\me7\bigmafstockatw_fix.bin (size=524288)
Reading Version Strings...
-> Bootrom Version = 05.12
-> EPK = 42/1/ME7.5/3/4012.00//F22id/Dst06g/250899/
-> Contents of ECUID data table:
   - '0261206537'         (SSECUHN)         
   - '1037352750'         (SSECUSN)         
   - '4B0906018P  '       (VAG part number)
   - '0006'               (VAG sw number)   
   - '1.8L R4/5VT     '   (engine id)       
-> Contents of ECUID data table:
   - 'HW_MAN004'                           

Romsys checksum failure(s) found
-> Found 1 error!!!   *******************************

Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12232


WWW
« Reply #65 on: May 15, 2015, 04:20:29 PM »

That doesn't look good Sad

try running the _fix file back through ME7Sum..

I will take a look time permitting. Thanks for reporting the issue..
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
slappynuts
Jr. Member
**

Karma: +0/-0
Offline Offline

Posts: 49


« Reply #66 on: May 17, 2015, 08:54:00 AM »

Oh it worked! TY sir! Kicking myself for not thinking of that.   Roll Eyes
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12232


WWW
« Reply #67 on: May 17, 2015, 11:37:16 AM »

Oh it worked! TY sir! Kicking myself for not thinking of that.   Roll Eyes

No worries, it is a known bug I haven't figured out how to fix yet Sad

Thanks for providing an image I can use to test further!
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
TLS4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 13


« Reply #68 on: June 23, 2015, 09:43:38 AM »

No worries, it is a known bug I haven't figured out how to fix yet Sad

Thanks for providing an image I can use to test further!
I get the same problem, I have to run ME7Sum twice to fix all checksums.
The bins are more or less stock 8D0907551K and Q. Just a couple of codewords changed (CW_CAR_R_0___A = 0 on first try and the a few more). If you need test files I can post one of these.

Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12232


WWW
« Reply #69 on: June 23, 2015, 10:09:45 AM »

I get the same problem, I have to run ME7Sum twice to fix all checksums.
The bins are more or less stock 8D0907551K and Q. Just a couple of codewords changed (CW_CAR_R_0___A = 0 on first try and the a few more). If you need test files I can post one of these.



Please do, thanks!
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
TLS4
Newbie
*

Karma: +0/-0
Offline Offline

Posts: 13


« Reply #70 on: June 24, 2015, 03:15:35 PM »

Please do, thanks!

Here is a K-bin and a Q-bin and corresponding output from me7check and me7sum
Logged
redtop
Jr. Member
**

Karma: +5/-0
Offline Offline

Posts: 44


« Reply #71 on: September 16, 2015, 01:30:12 AM »

Hi!
I'm working with ME7.3.1 in Fiat/Alfa Romeo/Lancia and trying to sort out what happend with the ME7Sum development. As I understand it when reading old threads, the functionality of calculating the checksum for the Ferrari ME7.3h4 made by 360Trev was never implemented in Nyet's ME7Sum software? Still there's another ME7Sum by 360Trev on Github that is intended for the Ferrari ECU: https://github.com/360trev/ME7Sum ?

Have I got this right? And is there anyplace I can get hold of 360Trev's software compiled for Windows?
Logged
nyet
Administrator
Hero Member
*****

Karma: +604/-166
Offline Offline

Posts: 12232


WWW
« Reply #72 on: September 16, 2015, 10:01:25 AM »

Hi!
I'm working with ME7.3.1 in Fiat/Alfa Romeo/Lancia and trying to sort out what happend with the ME7Sum development. As I understand it when reading old threads, the functionality of calculating the checksum for the Ferrari ME7.3h4 made by 360Trev was never implemented in Nyet's ME7Sum software? Still there's another ME7Sum by 360Trev on Github that is intended for the Ferrari ECU: https://github.com/360trev/ME7Sum ?

Have I got this right? And is there anyplace I can get hold of 360Trev's software compiled for Windows?


That software was never completed and
1) does not compute all the checksums
2) does not automatically locate checksum locations.
Logged

ME7.1 tuning guide (READ FIRST)
ECUx Plot
ME7Sum checksum checker/corrrector for ME7.x

Please do not ask me for tunes. I'm here to help people make their own.

Do not PM me technical questions! Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience.
redtop
Jr. Member
**

Karma: +5/-0
Offline Offline

Posts: 44


« Reply #73 on: September 16, 2015, 10:54:10 PM »

That software was never completed and
1) does not compute all the checksums
2) does not automatically locate checksum locations.

Thank you for the clairification!
I guess I'll have to find another tool for checksums on the Alfa ECUs.  Cry
Logged
Awaken
Full Member
***

Karma: +3/-3
Offline Offline

Posts: 84


« Reply #74 on: November 25, 2016, 06:26:19 PM »

Hello, is MD5 hash failure same as RSA failure?

Hope this thread is still alive and hopefully I can get some info.

I have a problem with a file for a 2002 S3 BAM 8N0906018BP. I use TunerPro with the MTX plugin. I have made only one simple change to the ori file, as a proof of concept and I get this when I run ME7Check:

ME7Check v1.12 (c) mki, 06/2004-05/2012
Checking file C:\Users\Ceco\Desktop\Audi S3 225HP 8N0906018BP 0261208054 366474_modified.ori (size=1048576)
Reading Version Strings...
-> Bootrom Version = 05.12
-> EPK = 40/1/ME7.5/5/4018.20//24B/Dst02o/290702//
-> Contents of ECUID data table:
   - '0261208054'         (SSECUHN)         
   - '1037366474'         (SSECUSN)         
   - '8N0906018BP '       (VAG part number)
   - '0002'               (VAG sw number)   
   - '1.8L R4/5VT     '   (engine id)       
-> Contents of ECUID data table:
   - 'HW_MAN004'                           


RSA signature failure found
-> Found 1 error!!!   *******************************

However! When I run ME7Sum on the same file, I get what I can identify as a md5 hash error, and not the RSA:

ME7Tool (v1.0.3) [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 'asd.ori'

Step #1: Reading ROM info ..
 Searching for EPK signature...OK
 Searching for ECUID table...OK
 EPK         : '40/1/ME7.5/5/4018.20//24B/Dst02o/290702//'
 Part Number : '8N0906018BP '
 Engine ID   : '1.8L R4/5VT     '
 SW Version  : '0002'
 HW Number   : '0261208054'
 SW Number   : '1037366474'

Step #2: Reading ROMSYS ..
 Startup section: word[0x008000]+word[0x00FFFE]
 @008038 Add=0x00CD15 CalcAdd=0x00CD15  ADD OK
 Program pages: 8k page first+last in 0x0000-0xFFFF and 0x20000-0xFFFFF
 @00803c Add=0xA0B46E CalcAdd=0xA0B46E  ADD OK
 All param page: word[0x010000]+word[0x01FFFE]
 @01bf7a Add=0x00971D CalcAdd=0x00971D  ADD OK

Step #3: Reading RSA signatures ..
 Searching for RSA offset #0...OK
 Searching for RSA offset #1...OK
         Signature: @8ec6a-8ecea
           Modulus: @167c2-16842
          Exponent: @16842 = 3
 Searching for MD5 ranges...OK
 MD5 Block Offset Table @1679e [32 bytes]:
 1) 0x00010002-0x00013FFE
 2) 0x00014252-0x00017F4E
 3) 0x00018192-0x0001FBDC
 4) 0x00026A00-0x0002FFFC
 EncrMD5: b6 87 d5 35 c6 9b 50 b3 d5 c5 1d eb 9a 73 2b 58
 CalcMD5: a1 6b 4d e4 20 39 c5 92 ac c2 ba 43 a9 70 9c c2
 ** NOT OK **

Step #4: Finding CRC table(s) ..
 Searching for CRC table(s)...OK
 CRC table(s) OK

Step #5: 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...missing
 Searching for main data checksum offsets...OK
 Main Checksums:
 1) 0x010002-0x013FFE CalcCSM: 001327A6
 2) 0x014252-0x017F4E CalcCSM: 00286183
 3) 0x018192-0x01FBDC CalcCSM: 00452742
 4) 0x026A00-0x02FFFC CalcCSM: 00C338F7
 @8f4b0 CSM: 00C338F7 CalcCSM: 00C338F7  Main data checksum OK

Step #6: Reading Main Program Checksums ..
 Searching for main program checksum..OK
 ROM Checksum Block Offset Table @1fb92 [16 bytes]:
 1) 0x000000-0x00FBFF CalcChk: 48D10B05
    0x00FC00-0x01FFFF CalcChk: 2198346D CalcCRC: 2E660DB7 SKIPPED
 2) 0x020000-0x0FFFFF
    <fffe0>  Chk: 425F5982 CalcChk: 425F5982 OK (i)

Step #7: Reading Multipoint Checksum Blocks ..
 Searching for multipoint block descriptor #1...missing
 Searching for multipoint block descriptor #2...OK
 1) <1fbde>  0x000000-0x003FFF Chk: 0FA0F5CF Boot: (whitelisted) OK
 2) <1fbee>  0x004000-0x007FFF Chk: 0F4716B3 Boot: (whitelisted) OK
 3) <1fbfe>  0x000000-0x003FFF Chk: 0FA0F5CF CalcChk: 0FA0F5CF OK
 4) <1fc0e>  0x004000-0x007FFF Chk: 0F4716B3 CalcChk: 0F4716B3 OK
 Multipoint #2: [66 blocks x <16> = 1056 bytes]

*** Found 70 checksums in asd.ori

*** WARNING! 1/1 uncorrected error(s) in asd.ori! ***

I have attached the binary. Thanks in advance and sorry if I failed to find an answer to this, but I am pretty sure I read the whole forum already... Smiley
Logged
Pages: 1 ... 3 4 [5] 6 7 ... 9
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.03 seconds with 17 queries. (Pretty URLs adds 0s, 0q)