NefMoto

Noob Zone => Noob Questions => Topic started by: vwnut8392 on September 13, 2016, 07:17:58 PM



Title: cant correct checksum? bad RSA?
Post by: vwnut8392 on September 13, 2016, 07:17:58 PM
i pulled this file from a car that magically stopped running and it had a checksum error fault code so i check the checksum ME7check and it says the RSA cant be corrected. anyone know of a why to make it correct? it came from an automatc 2004 jetta 1.8T. File in question is attached.


Title: Re: cant correct checksum? bad RSA?
Post by: nyet on September 13, 2016, 08:15:08 PM
Did you bother trying ME7Sum? If not, why not?

Does the file have AL/NLS?


Title: Re: cant correct checksum? bad RSA?
Post by: vwaudiguy on September 13, 2016, 08:59:19 PM
Does the file have AL/NLS?

Nothing but a lot of prok zero'd


Title: Re: cant correct checksum? bad RSA?
Post by: vwnut8392 on September 15, 2016, 12:00:29 AM
yes i did try ME7sum and no it doesnt have any of the add on's because it came from an automatic car.


Title: Re: cant correct checksum? bad RSA?
Post by: nyet on September 15, 2016, 12:10:44 AM
yes i did try ME7sum

And? Where is the output? Please don't beg for somebody ELSE to do checksums for you without letting somebody teach you to do it yourself.


Title: Re: cant correct checksum? bad RSA?
Post by: vwnut8392 on September 15, 2016, 12:34:08 PM
And? Where is the output? Please don't beg for somebody ELSE to do checksums for you without letting somebody teach you to do it yourself.

Here's the output from ME7sum.

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 '06A906032NL.bin'

Step #1: Reading ROM info ..
 Searching for EPK signature...OK
 Searching for ECUID table...OK
 EPK         : '42/1/ME7.5/120/4013.00//24D/Dst03o/110303/'
 Part Number : '06A906032NL '
 Engine ID   : '1.8L R4/5VT     '
 SW Version  : '0003'
 HW Number   : '0261208164'
 SW Number   : '1037368002'

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

Step #3: Reading RSA signatures ..
 Searching for RSA offset #0...OK
 Searching for RSA offset #1...OK
         Signature: @9d19a-9d21a
           Modulus: @16a7c-16afc
          Exponent: @16afc = 3
 Searching for MD5 ranges...OK
 MD5 Block Offset Table @16a58 [32 bytes]:
 1) 0x00010002-0x00013FFE
 2) 0x00014252-0x00017F4E
 3) 0x00018192-0x0001FBDC
 4) 0x00026A00-0x0002FFFC
 EncrMD5: 2a 09 d6 c7 a7 e4 7d 71 a9 f3 43 07 15 2a 80 97
 CalcMD5: c7 04 37 c6 37 73 ef af 86 ed 79 58 7d 7a cc 55
 ** 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: 001292A6
 2) 0x014252-0x017F4E CalcCSM: 002B83F0
 3) 0x018192-0x01FBDC CalcCSM: 004B801B
 4) 0x026A00-0x02FFFC CalcCSM: 00BAFB42
 @9d9e0 CSM: 00BAFB42 CalcCSM: 00BAFB42  Main data checksum OK

Step #6: Reading Main Program Checksums ..
 Searching for main program checksum..OK
 ROM Checksum Block Offset Table @1fbb4 [16 bytes]:
 1) 0x000000-0x00FBFF CalcChk: 48D03EC9
    0x00FC00-0x01FFFF CalcChk: 24D586D2 CalcCRC: 80EA809F SKIPPED
 2) 0x020000-0x0FFFFF
    <fffe0>  Chk: 0795984C CalcChk: 0795984C 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 06A906032NL.bin

*** WARNING! 1/1 uncorrected error(s) in 06A906032NL.bin! ***



Title: Re: cant correct checksum? bad RSA?
Post by: vwnut8392 on September 15, 2016, 12:36:02 PM
and the output from ME7check.
==============================================================================
ME7check v1.12 (c) mki, 06/2004-05/2012
Checking file 06A906032NL.bin (size=1048576)
Reading Version Strings...
-> Bootrom Version = 05.12
-> EPK = 42/1/ME7.5/120/4013.00//24D/Dst03o/110303/
-> Contents of ECUID data table:
   - '0261208164'         (SSECUHN)
   - '1037368002'         (SSECUSN)
   - '06A906032NL '       (VAG part number)
   - '0003'               (VAG sw number)
   - '1.8L R4/5VT     '   (engine id)
-> Contents of ECUID data table:
   - 'HW_MAN004'


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


Title: Re: cant correct checksum? bad RSA?
Post by: nyet on September 15, 2016, 01:16:50 PM
So tell ME7Sum to output a corrected file.


Title: Re: cant correct checksum? bad RSA?
Post by: nyet on September 15, 2016, 01:18:12 PM
From

http://nefariousmotorsports.com/forum/index.php?topic=3347
To output corrected checksums you must specify an output file:

  me7sum image.bin out.bin


Title: Re: cant correct checksum? bad RSA?
Post by: vwnut8392 on September 16, 2016, 01:54:18 PM
i feel like an idiot, i didnt realize i had to add the output file name to it. thank you nynet. problem solved!