FIRM0 section2 hash mismatch?

Discussion in '3DS - Flashcards & Custom Firmwares' started by Sumsquat, Jun 23, 2016.

  1. Sumsquat
    OP

    Sumsquat Advanced Member

    Newcomer
    66
    19
    Jan 15, 2016
    Gambia, The
    Hi there!
    So, I made a SysNAND dump(just in case I mess something up) with Decrypt9.
    Then I wanted to validate the dump(also with Decrypt9) and it showed me this:
    FIRM0 section2 hash mismatch
    FIRM0 is corrupt (non critical)
    Validate NAND dump: succeeded!

    I dumped the Nand again and got the same result.
    What's the problem? What will happen if I restore this dump?
    No problems with emuNAND dumps.

    Specifications of my device:
    O3DS, updated SysNand 11.0, most recent A9LH commits by AuroraWright

    I hope anyone can help me with this.

    Greetings!
     
  2. bobfacemoo

    bobfacemoo GBAtemp Fan

    Member
    350
    62
    Feb 21, 2016
    This is normal to see if you have A9LH installed
     
    Sumsquat likes this.
  3. Sumsquat
    OP

    Sumsquat Advanced Member

    Newcomer
    66
    19
    Jan 15, 2016
    Gambia, The
    Okay, nice! Thank you so much for your quick answer!
     
  4. bobfacemoo

    bobfacemoo GBAtemp Fan

    Member
    350
    62
    Feb 21, 2016
    It is perfectly fine to restore it, A9LH is stored on FIRM so it's natural that it would give a mismatch against what it should be. The reason you don't get it with EmuNAND is because A9LH is not installed on EmuNAND FIRM
     
    Sumsquat likes this.