New AMI BIOS tool for performing SSV2/3 and Dynamic SLIC Modification

Discussion in 'MDL Projects and Applications' started by andyp, Jan 7, 2009.

  1. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    3 possible reasons, as others have said.

    1) Loader - ensure if EVER installed that ALL elements are removed/refreshed (ie. boot sector/MBR etc.) - I think VOAK 2.5 can do this
    2) 'Lock' in BIOS code - some BIOSes copy the OEM/Table ID from another table, from another place or write it in code ('split' OEM/Table IDs). These need finding and patching - eg. the recent phoenix SONY table ID lock success.
    3) Copied from part of BIOS that is not normally flashed - this is what aflash2 /all tries to deal with.

    If you have no loader and aflash2 doesn't work then can we have a link to the BIOS and before and after RW reports please.

    Thanks
    Andy
     
  2. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    Looking at the changelog (hint, hint :D) there have been a few changes. Basically don't use SSV - this seems to cause all the problems. I have had a few (3 I think) successes recently where the SLIC table has needed to go in the bootblock.

    Try a normal SSV2 mod. If that doesn't work post the BIOS link and a HWDirect dump of the last 1MB of memory and we can go from there.

    Andy
     
  3. nicholasf

    nicholasf MDL Novice

    Oct 15, 2008
    18
    0
    0
    Hi Andy, please take a look at post 1217 on page 122 of this thread you will find my problem with bios link and rw report. Thanks for your reply!
     
  4. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    Which method did you use to mod?
    Andy
     
  5. nicholasf

    nicholasf MDL Novice

    Oct 15, 2008
    18
    0
    0
    I try SSV3 and Dynamic. Both without success.
     
  6. armada

    armada MDL Addicted

    Dec 8, 2007
    857
    209
    30
    when it says extended boot block checksum not valid what is the proper way to fix that. can this be done through the advanced settings? please let me know how to fix this error thank you

    should i follow this as you said andyp:

    The bootblock checksum errors should be handled like this:
    1) Flash the original unmodified BIOS
    2) Assuming it works OK then the bootblock checksum is obviously not an issue so:
    3) Tick ignore checksum and module 80h errors in advanced
    4) Mod
    5) You will still get a dialog box every time an error is found, ensure that the bootblock checksum is the ONLY one you get
    6) Flash the modded BIOS from DOS.

    Andy

    what is the chance this will fail or brick the system (msi notebook)

    here is the log from ticked ignore checksum errors does this look okay??

    Version 1.43
    Manufacturer - MSI
    Original BIOS size 1048576 bytes (1024K)
    1000C Module 11 Padded size 51208
    1C828 Module 8 Padded size 2080
    1D05C Module C Padded size 8
    1D078 Module 1B Padded size 181228 (Actual size 181226 Original size 415031)
    49478 Module 20 Padded size 40424 (Actual size 40421 Original size 65536)
    53274 Module 20 Padded size 36992 (Actual size 36990 Original size 59392)
    5C308 Module 20 Padded size 25676 (Actual size 25676 Original size 45056)
    62768 Module 4 Padded size 22120 (Actual size 22117 Original size 35809)
    67DE4 Module 10 Padded size 14016 (Actual size 14016 Original size 33667)
    6B4B8 Module 21 Padded size 11356 (Actual size 11353 Original size 25754)
    6E128 Module 18 Padded size 6144 (Actual size 6141 Original size 16965)
    6F93C Module 1E Padded size 3268 (Actual size 3265 Original size 6593)
    70614 Module 19 Padded size 1436 (Actual size 1436 Original size 4868)
    70BC4 Module 6 Padded size 860 (Actual size 860 Original size 2560)
    70F34 Module 2B Padded size 840 (Actual size 839 Original size 1360)
    71290 Module E Padded size 520 (Actual size 520 Original size 12915)
    714AC Module 80 Padded size 104
    E0018 Module 55 Padded size 32064 (Unlinked)
    NVRAM at D0000 length 10000
    ROM Hole at 0 length 10000
    There are unlinked blocks in module 80h
    Bootblock at F0000 length 10000
    Extended Bootblock at E0000 length 20000
    Boot block checksum is correct
    Extended boot block checksum not valid
    Main BIOS checksum is correct
    1B module size is 415031 bytes
    AMIBIOS string found at F7AB
    SSV2 method
    SLIC module size is 374 bytes
    SLIC module checksum is 0
    OEM Activation 2.1 SLIC
    No split OEM/Table ID strings found
    Scanning for space to insert SLIC
    There is space to insert SLIC in ROM image at 80000
    RSDT table found at 49FE5
    RSDT table can be extended
    XSDT table found at 4A0E5
    XSDT table can be extended
    RSDT table OEM and Table ID patched to MSI_NBMEGABOOK
    XSDT table OEM and Table ID patched to MSI_NBMEGABOOK
    FACP table OEM and Table ID patched to MSI_NBMEGABOOK
    FACP table OEM and Table ID patched to MSI_NBMEGABOOK
    APIC table OEM ID patched to MSI_NB
    HPET table OEM ID patched to MSI_NB
    MCFG table OEM ID patched to MSI_NB
    Existing SLIC in 1B deleted
    SLIC table OEM ID patched to MSI_NB
    OEM table OEM ID patched to MSI_NB
    Module 1B written
    New 1B Module is 20 bytes too big
    Zero area 1
    Module 1B written
    New 1B Module is 48 bytes too small
    Module 1B written
    New 1B Module is 36 bytes too small
    Module 1B written
    New 1B Module is 12 bytes too small
    Module 1B written
    New 1B Module is 8 bytes too small
    Module 1B written
    New 1B Module is 8 bytes too small
    Module 1B written
    New 1B Module is 4 bytes too small
    Module 1B written
    New 1B Module is 12 bytes too small
    Module 1B written
    New 1B Module is 4 bytes too small
    Module 1B written
    New 1B Module is 4 bytes too small
    Module 1B written
    New 1B Module is 8 bytes too small
    Module 1B written
    New 1B Module is correct size
    1B copied to original BIOS
    SLIC inserted at 80000
    32 bit BIOS checksum corrected after SLIC table
    New BIOS written 1048576 bytes
    1000C Module 11 Padded size 51208
    1C828 Module 8 Padded size 2080
    1D05C Module C Padded size 8
    1D078 Module 1B Padded size 181228 (Actual size 181225 Original size 415031)
    49478 Module 20 Padded size 40424 (Actual size 40421 Original size 65536)
    53274 Module 20 Padded size 36992 (Actual size 36990 Original size 59392)
    5C308 Module 20 Padded size 25676 (Actual size 25676 Original size 45056)
    62768 Module 4 Padded size 22120 (Actual size 22117 Original size 35809)
    67DE4 Module 10 Padded size 14016 (Actual size 14016 Original size 33667)
    6B4B8 Module 21 Padded size 11356 (Actual size 11353 Original size 25754)
    6E128 Module 18 Padded size 6144 (Actual size 6141 Original size 16965)
    6F93C Module 1E Padded size 3268 (Actual size 3265 Original size 6593)
    70614 Module 19 Padded size 1436 (Actual size 1436 Original size 4868)
    70BC4 Module 6 Padded size 860 (Actual size 860 Original size 2560)
    70F34 Module 2B Padded size 840 (Actual size 839 Original size 1360)
    71290 Module E Padded size 520 (Actual size 520 Original size 12915)
    714AC Module 80 Padded size 104
    NVRAM at D0000 length 10000
    ROM Hole at 0 length 10000
    There are unlinked blocks in module 80h
    Main BIOS checksum is correct
    Bootblock at F0000 length 10000
    Extended Bootblock at E0000 length 20000
    Boot block checksum is correct
    Extended boot block checksum not valid
    1000C Module 11 Padded size 51208
    1C828 Module 8 Padded size 2080
    1D05C Module C Padded size 8
    1D078 Module 1B Padded size 181228 (Actual size 181225 Original size 415031)
    49478 Module 20 Padded size 40424 (Actual size 40421 Original size 65536)
    53274 Module 20 Padded size 36992 (Actual size 36990 Original size 59392)
    5C308 Module 20 Padded size 25676 (Actual size 25676 Original size 45056)
    62768 Module 4 Padded size 22120 (Actual size 22117 Original size 35809)
    67DE4 Module 10 Padded size 14016 (Actual size 14016 Original size 33667)
    6B4B8 Module 21 Padded size 11356 (Actual size 11353 Original size 25754)
    6E128 Module 18 Padded size 6144 (Actual size 6141 Original size 16965)
    6F93C Module 1E Padded size 3268 (Actual size 3265 Original size 6593)
    70614 Module 19 Padded size 1436 (Actual size 1436 Original size 4868)
    70BC4 Module 6 Padded size 860 (Actual size 860 Original size 2560)
    70F34 Module 2B Padded size 840 (Actual size 839 Original size 1360)
    71290 Module E Padded size 520 (Actual size 520 Original size 12915)
    714AC Module 80 Padded size 104
    E0018 Module 55 Padded size 32064 (Unlinked)
    NVRAM at D0000 length 10000
    ROM Hole at 0 length 10000
    There are unlinked blocks in module 80h
    Bootblock at F0000 length 10000
    Extended Bootblock at E0000 length 20000
    Boot block checksum is correct
    Extended boot block checksum not valid
    Main BIOS checksum is correct
    Unreferenced bytes are present
    SLIC performed successfully.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    Hi

    There appears to be some sort of lock then. I have asked the others to have a look to see if they have any ideas, otherwise I might have to create some custom BIOSes that patch code - I can see a couple of possible culprit areas - are you happy to test these?

    Andy
     
  8. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    Provided the EBB checksum 'error' is present in the original unmodded BIOS then it should be OK. The EBB is not modified at all (hence the error persists to the end). The steps you list are correct.

    Andy
     
  9. armada

    armada MDL Addicted

    Dec 8, 2007
    857
    209
    30
    is there any way to tell if the error is in the original? this is a unmodded bios direct from msi. if there is a way i can let you know. but the original is flashed and on the system now so the original works 100% and thanks again
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    Load the originial into the tool. If the error comes up then it's in the original!

    Andy
     
  11. nicholasf

    nicholasf MDL Novice

    Oct 15, 2008
    18
    0
    0
    Better not take risks, the solution of the loader is the less dangerous in this case... Anyway thanks you for your help!
     
  12. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    It certainly is safer.

    Cheers,
    Andy
     
  13. mictlan

    mictlan MDL Member

    Nov 9, 2009
    241
    123
    10
    @andyp:

    Do I need a SLP file for Windows 7 bios mod (only slic 2.1)?
     
  14. urie

    urie retired mod

    May 21, 2007
    8,999
    3,381
    300
    SLP 1.0 is for xp SLIC 2.0 for vista SLIC 2.1 for vista and windows 7.
     
  15. Andrew2

    Andrew2 MDL Novice

    Nov 8, 2009
    14
    16
    0
    Hi Andy,

    Asus P6T64 WS Revolution, BIOS V. 507 showed the "missing OEM SLP string" issue also (using amitool 1.43, SSV3 & ASUS SLIC).

    Confirmation: This worked for the P6T64... , too.

    Thanks for the tip!
     
  16. joebob69

    joebob69 MDL Novice

    Jan 11, 2010
    3
    0
    0
    I just tried this several times on my ASUS M50VM-x1, using the latest AMI (rev 212) BIOS file from the ASUS support site (which I just flashed), ASUS SLIC 2.1 and ASUS SLP, and default settings (method SSV3), but when I click "Go", it starts working only to freeze the whole computer when a Windows popup asking me if I'd like to run MMTOOL.exe appears.

    After a reboot, I find the modded BIOS and BIN files, but I'm afraid to use them.

    Any ideas?
     
  17. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,673
    2,570
    60
    Run mmtool on its own once, and untick the box that says ask every time.
    Then run the tool.

    Andy
     
  18. joebob69

    joebob69 MDL Novice

    Jan 11, 2010
    3
    0
    0
    Doh. I feel stupid. That worked. :D

    Edit:

    Oh more thing if you don't mind:

    I don't have a USB drive handy to boot to AFLASH2 with (the DOS flasher ASUS provides.) Do you know if it's safe to flash with EZFlash which is included with my BIOS? (Again, I'm running an ASUS M50VM with AMI v. 212.)

    Cheers, Andy!
     
  19. bloke

    bloke MDL Junior Member

    Mar 1, 2008
    53
    0
    0
    #1239 bloke, Jan 11, 2010
    Last edited by a moderator: May 23, 2017
  20. urie

    urie retired mod

    May 21, 2007
    8,999
    3,381
    300
    @ bloke, ar you saying the asrock computer doesn't boot at the moment after bios flash ? do you know there is no bios recovery available on asrock motherboards.