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

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,696
    15,715
    340
    Its AMI Aptio (UEFI), so you need to use this.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. 594b62c3a4

    594b62c3a4 MDL Novice

    May 18, 2014
    2
    0
    0
    Great tool actually.
    Great andyp :D

    The worst case ever happen to me was some pci device did not working properly.
    Some low end mobo doesn't like their bios modified, I think.
    A great tool for some time before coming an UEFI.
     
  3. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,696
    15,715
    340
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Jeyrosati

    Jeyrosati MDL Novice

    Jul 28, 2014
    3
    0
    0
    Thanks so much. I just figured that out. I'm a bit behind on the latest tech.
     
  5. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,696
    15,715
    340
    Yes you can. But if its a notebook bios, then it requires special techniques.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  6. pcfr33k

    pcfr33k MDL Novice

    Sep 12, 2010
    9
    0
    0
    Its a notebook PC Rog Gamer's Laptop. Can I ask a couple questions. I have three of these Laptops. I really screwed up and had some help from Coderush to fix things back. I accidentally flashed a backup from one Laptop to another. I am sure you can guess what happened. It cloned them. Giving them both the same Device Serial Number, Lan Mac Address and the worst part of it all trying to figure out how to fix this it copied the Windows 8 serial number in the Bios. Windows 8 is working fine and is activated on the Clone but I am trying to figure out how I can get the original back, maybe make them all "FFFF" with Hex editor and reactivate through Asus? The Mac address is no big deal, we just changed the last hex code. The serial number was an east fix.
     
  7. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,696
    15,715
    340
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,407
    11,326
    340
    #1970 Yen, Aug 13, 2014
    Last edited by a moderator: Apr 20, 2017
    The table is invalid either way, it's not your fault. Your way to go is right, anyway both messages available have another SHA-256. The OEMIDs are part of the message and hence part of the encryption / verification. At the table header they play no role for table verification, though:

    Code:
    Offset      0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F
    
    00000000   53 4C 49 43 76 01 00 00  01 1C 53 4D 43 49 20 20   SLICv     SMCI  
    00000010   00 00 00 00 00 00 00 00  27 06 12 20 4D 53 46 54           '   MSFT
    00000020   97 00 00 00 00 00 00 00  9C 00 00 00 06 02 00 00   —       œ       
    00000030   00 24 00 00 52 53 41 31  00 04 00 00 01 00 01 00    $  RSA1        
    00000040   AB FB CB 4F 92 7D 18 0C  51 54 9C 8C 96 1B 4F 66   «ûËO’}  QTœŒ– Of
    00000050   CA 9C 24 50 A0 CB 95 31  4C 88 89 99 5A C9 55 1C   Êœ$P*Ë•1Lˆ‰™ZÉU 
    00000060   D3 9E 70 E4 7B D7 6C FC  B3 A9 C6 7F 7F 1E 38 57   Óžpä{×lü³©Æ   8W
    00000070   A4 59 3B 2B 94 00 DA DC  6D 98 71 66 0D 69 CC 84   ¤Y;+” ÚÜm˜qf iÌ„
    00000080   3A 60 31 14 2C 17 47 E5  C4 DF 19 00 7B 56 FB 63   :`1 , GåÄß  {Vûc
    00000090   9D 5A 30 D5 F0 F8 D6 F4  98 42 4A 28 68 8C 0A E1    Z0ÕðøÖô˜BJ(hŒ á
    000000A0   AD 0D 2D 12 04 45 AD 62  54 4B CF 35 01 4C 19 00   * -  E*bTKÏ5 L  
    000000B0   E8 2D B5 42 C7 84 10 E6  98 5D 44 08 42 9E 94 DB   è-µBÇ„ æ˜]D Bž”Û
    000000C0   01 00 00 00 B6 00 00 00  00 00 02 00 53 4D 43 49             SMCI
    000000D0   20 20 00 00 00 00 00 00  00 00 57 49 4E 44 4F 57             WINDOW
    000000E0   53 20 00 00 00 00 00 00  00 00 00 00 00 00 00 00   S               
    000000F0   00 00 00 00 00 00 BD D5  17 ED 61 17 58 8E 6D CC         ½Õ ía XŽmÌ
    00000100   5C 94 6A C2 8E 1B B6 52  B1 CE 56 42 0A E4 03 46   \”jÂŽ ¶R±ÎVB ä F
    00000110   70 E2 89 AE 39 84 7B 88  FE 67 C1 10 23 CE 82 A6   p≮9„{ˆþgÁ #΂¦
    00000120   09 41 49 7B E9 81 19 82  A2 DB 88 49 E8 2A 7E E3    AI{é  ‚¢ÛˆIè*~ã
    00000130   C0 95 C9 A6 53 9C 00 11  CB E4 88 27 AC 55 FB 89   À•É¦Sœ  Ëäˆ'¬Uû‰
    00000140   C0 33 45 D6 AB B9 21 4E  E1 00 C8 77 9A 69 60 B9   À3EÖ«¹!Ná Èwši`¹
    00000150   AC 05 9F 3B 18 E0 08 8C  D9 4C F0 81 85 AC EC F9   ¬ Ÿ; à ŒÙLð …¬ìù
    00000160   F3 3A 0C 5E 02 B9 5C 1B  DC 8C 7F CB 54 5E 7D A6   ó: ^ ¹\ ÜŒ ËT^}¦
    00000170   45 8E EF 55 84 8B                                  EŽïU„‹

    The green part is the message. Its SHA-256 hash must be (result when hash decrypted, the last 128 bytes of a SLIC)
    Code:
    57 A6 25 7B 07 F1 35 B0 50 32 F7 54 61 40 61 94 DF 48 F4 D3 C0 7B BD 04 0F 8B B7 CA 8D 95 00 22 
    to become valid.

    At the table above it is (taken from the F0 module):
    Code:
    9D67F81EA24A322715647B4194E69DE7DD725BC7643E3CDAD239111C24D67E19
    Also the message from the 1B module doesn't match:
    Code:
    Offset      0  1  2  3  4  5  6  7   8  9  A  B  C  D  E  F
    
    00057770                                           00 00 02                   
    00057780   00 30 36 32 37 31 32 53  4C 49 43 31 34 30 31 57    062712SLIC1401W
    00057790   49 4E 44 4F 57 53 20 00  00 00 00 00 00 00 00 00   INDOWS          
    000577A0   00 00 00 00 00 00 00 00  00 00 00                             
    SHA-256:
    Code:
    A8AD359B5F1CCC935578F07F9C92689ABD427EB9C2362812FDC58F5587BBD8E2

    You would have to find a 46 hex. byte sequence whose SHA-256 hash is the one above (blue bytes)...and insert the sequence as message..:D

    I guess the BIOS code reads it from somewhere to get a valid message, or it is a pure dummy SLIC.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  9. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,696
    15,715
    340
    @Yen

    Thanks for the detailed explanation.
    I also think so. Thats why I asked esmurf63 to post RW report of both unmodded & modded bios. No Supermicro SLIC is discovered yet.

    :hug2:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. IMweasel

    IMweasel MDL Novice

    Nov 20, 2012
    2
    0
    0
    Hi guys, i'm fiddling a bit with AMI SLIC Mod 1.63
    I'm trying to insert an SLI certificate in the DSDT table of my Asus Crosshair IV Formula, to achieve native SLI support.
    The options i ticked are; 'DSDT only' , and under advanced->options i ticked the 'Add SLI entry'
    When i hit Go, after a little while i get a 'DSDT table not found' error.

    This also happens with the Crosshair IV Extreme bios.

    I noticed that the DSDT table is in module 10, but the program is tinkering in the 1B module?
    Something is going wrong here... is the structure of these bios'es not supported perhaps?
    Or am i doing something wrong?
     
  11. nacode

    nacode MDL Novice

    Sep 23, 2014
    5
    0
    0
    Have a ASUS Board P9X79.
    Like to modify the bios wth slic 2.1
    Load down the Version V 1.63
    Put all in a separate Folder.
    Load down from ASUS Homepage the original bios file p9x79-ASUS-4701.cap for Windows 7 64 bit.
    Open AmiTool.exe as admin.
    Open the p9x79-ASUS-4701.cap file.
    Received error message "Bios size not valid"
    What can be the Problem?
     
  12. Serg008

    Serg008 MDL BIOS/EFI Guru

    Feb 23, 2010
    19,663
    8,661
    340
    It's AMI UEFI bios, try Phoenixtool 2.58 (New module method)
     
  13. nacode

    nacode MDL Novice

    Sep 23, 2014
    5
    0
    0
    Hello Serg008, loaded down the Phoenixtool all in a separate Folder.
    Open the Phoenixtool.exe as admin.
    Open the p9x79-ASUS-4701.cap (it works)
    In Slic File i placed Slic21/ASUS.bin
    In SLP File i placed Asus.txt
    in Key File i placed Key.txt
    in RW File i plade nothing (my new pc is not ready yet)

    The program produced me the p9x79-ASUS-4701_SLIC.cap file
    Will be that ok without the RW file or is the RW file absolutely neccessary?

    Thanks Joe
     
  14. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,696
    15,715
    340
    1. Don't select any SLP file - it breaks the bios signature.
    2. No need to select any RW report.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. nacode

    nacode MDL Novice

    Sep 23, 2014
    5
    0
    0
    Ok thanks Tito will do so as you suggested.
    If my new pc is ready i will install the original win 7 Ultimate 64 bit.
    What method will be the best to activate the win 7.
    At my old pc i did it with DAZ Loader.
    Will be that ok?
     
  16. Tito

    Tito Super Mod / Adviser
    Staff Member

    Nov 30, 2009
    17,696
    15,715
    340
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  17. Casturdy

    Casturdy MDL Novice

    Aug 15, 2013
    14
    2
    0
    Could someone please re-up this tool?
    The download link in the first post is down and I was not able to find any other working links.