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...