Tool to Insert/Replace SLIC in Phoenix / Insyde / Dell / EFI BIOSes

Discussion in 'MDL Projects and Applications' started by andyp, Nov 26, 2009.

  1. haiduongbros

    haiduongbros MDL Addicted

    Apr 13, 2009
    504
    163
    30
  2. WIND0WS 7

    WIND0WS 7 MDL Member

    Sep 28, 2009
    145
    0
    10
    Please guys, I really need your help, I don't know what I need to do.
     
  3. WIND0WS 7

    WIND0WS 7 MDL Member

    Sep 28, 2009
    145
    0
    10
    kizwan would you mind sharing how you found the CPU microcodes in the roms please?
     
  4. WIND0WS 7

    WIND0WS 7 MDL Member

    Sep 28, 2009
    145
    0
    10
    I found a CPU microcode in the .hdr file but how come the tool won't allow me to hack it or the temphdr?
     
  5. .NetRolller 3D

    .NetRolller 3D MDL Novice

    Jul 16, 2009
    32
    2
    0
    Any chance of adding MXM structure detection to the next version?
    The MXM structure can be recognized by the ASCII string "MXM_" (not null-terminated), which is followed by 2 bytes (the first one is the MXM version, second one is the MXM revision; both should be below 0xA), then the size of the structure (excluding the 8-byte header) as a 16-bit integer, and finally the data in the structure. The entire structure (including header) should have a checksum of 0x0 (but it is a good idea to recognize MXM structures with a checksum error - the Acer Aspire 5920G is known to have such an MXM structure). If you need more information on how to identify an MXM structure, ask here.
     
  6. Apokrif

    Apokrif MDL Addicted

    Dec 7, 2008
    542
    35
    30
    Ok… I’d expect, CPU microcode update is not persistent… I.e. it needs to be updated on every CPU reset (or power off, obviously) Wrong/malicious microcode update update will be able to brick CPU otherwise…

    I can write short instructions:
    Andy tool has a switch (don’t remember, need Andy help) to unpack BIOS and stop.
    You can replace any module and let tool continue (you don’t even need to modify anything with tool - Andy - please correct if I’m mistaken)
    It’ll repack BIOS again with the module you just replaced.
    If you don’t replace anything - you’ll get same exactly BIOS (you can do fc /b to prove)

    Take a look into the DUMP folder - you should be able recognize CPU microcode one.
    If you unpack ANY later BIOS – it’ll have never version, most likely.

    Guys,
    Please correct me if I’m wrong somewhere - I hope we can put together this little tutorial easily.
     
  7. kizwan

    kizwan MDL Member

    Mar 6, 2010
    189
    31
    10
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. Apokrif

    Apokrif MDL Addicted

    Dec 7, 2008
    542
    35
    30
    Need a little help:
    CPU-Z shows:
    Processor 1ID = 0
    Number of cores4 (max 4)
    Number of threads4 (max 4)
    NameIntel Core 2 Quad Q6600
    CodenameKentsfield
    SpecificationIntel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz
    Package (platform ID)Socket 775 LGA (0x4)
    CPUID6.F.B
    Extended CPUID6.F
    Core SteppingG0
    Technology65 nm

    What is my CPUID for microcode update?
    000006FB/FB060000
    or
    000006F0/F0060000

    I see couple FB060000 in HDR, but there is nothing like date before them (Date of the update creation in binary format: mmddyyyy
    (e.g. 07/18/98 is 07181998H).)
    And there is no single module with 000006FB...
    Could you zip and post Phoenix microcode update, please?
     
  9. kizwan

    kizwan MDL Member

    Mar 6, 2010
    189
    31
    10
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. WIND0WS 7

    WIND0WS 7 MDL Member

    Sep 28, 2009
    145
    0
    10
    As I said there's only .ROM files in the DUMP folder and I can't recognize the CPU microcode in a ROM, only in the HDR & temphdr which aren't in the DUMP folder and can't be manually edited and inserted with the tool. Do I need to open the ROM's in a HEX editor?
     
  11. WIND0WS 7

    WIND0WS 7 MDL Member

    Sep 28, 2009
    145
    0
    10
    If I replace the existing cpu*.bin code (7168-48=7120 bytes since first 48 characters don't exist in the .hdr) with a standard (2048 bytes) cpu*.bin code and gzip the new .hdr file, name it bios.gz, boot it up with FreeDOS and run "d4700a10.exe -readgzfile" would it attempt the flash but possibly give a CRC mismatch error which can be corrected I believe?
     
  12. Apokrif

    Apokrif MDL Addicted

    Dec 7, 2008
    542
    35
    30
    Exactly - 2 CRCs need to to be updated.
     
  13. Apokrif

    Apokrif MDL Addicted

    Dec 7, 2008
    542
    35
    30
    No. kizwan poset a link to Intel site + microdecode.rar.
    Should be something like this:
    0001067a
    0001067a
    000106a4
    000106e5
    0001067a
    000106e4
    00020652
    000206a7
    000006f7
    000006fa
    00000f48
    00010661
    00020655