Unable to re-integrate the modified ".ff" module

Discussion in 'BIOS Mods' started by kizwan, Feb 9, 2011.

  1. kizwan

    kizwan MDL Member

    Mar 6, 2010
    189
    31
    10
    #1 kizwan, Feb 9, 2011
    Last edited by a moderator: Apr 20, 2017
    Hi andy & Yen,

    I need your help again. :p This time the modified ".ff" module failed to reintegrate. The Phoenix SLIC Mod tool complain the module is 118386 bytes too big. I only change 10 bytes though. I really appreciated if you can take a look & advice me about it.

    A little background why I need to modify the ".ff" module. The modified module is for unlocking Enhanced Intel SpeedStep Technology (EIST). It involved MSR register 0x1a0 bit 20. Bit 20 is "EIST Locked" bit; 0 - unlocked, 1 - locked. When EIST is unlocked, we can enable dual-IDA mode on supported hardware. When EIST is unlocked, the EIST can be enabled/disabled in Windows (important prerequisite for enabling dual-IDA). Little background about dual-IDA can be found over here & here.

    The changes I made in the ".ff" module is (two places - I show one of 'em):-
    Original:-
    Code:
    0000168F  B9A0010000        mov ecx,0x1a0
    00001694  48                dec eax
    00001695  0FBAE814          bts eax,0x14
    00001699  48                dec eax
    Modified to:-
    Code:
    0000168F  B9A0010000        mov ecx,0x1a0
    00001694  90                nop
    00001695  90                nop
    00001696  90                nop
    00001697  90                nop
    00001698  90                nop
    00001699  48                dec eax
    This compressed file contain original BIOS file, the modified ".ff" module & SLIC.LOG (when I attempt to re-integrate the modified module):-
    http://www.mediafire.com/?antsc8sm2m1g11y

    :biggrin:
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  2. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,671
    2,434
    60
    #2 andyp, Feb 9, 2011
    Last edited by a moderator: Apr 20, 2017
    If you used 1.75, use 1.76. I introduced a bug in 1.75 which affected module recompression if more than one type of compression (EFI, Tiano, LZMA) was used.

    Andy

     
  3. kizwan

    kizwan MDL Member

    Mar 6, 2010
    189
    31
    10
    With 1.76, it still unable to re-integrated the module. The log file contain the same error:-
    (part of it)
    Thank you andy for looking into this. :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,671
    2,434
    60
    Yeah.
    There are quite a few problems actually. The module copying code was never designed for the .ff modules as they are kind of EFI hybrids. It makes lots of assumptons that are not valid.

    I am working on it :)

    Andy
     
  5. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,671
    2,434
    60
    Right.... what i thought was a quick fix, has actually taken all afternoon..... and yet the solution was acutally quite simple. LOL.

    Try 1.77

    Andy
     
  6. kizwan

    kizwan MDL Member

    Mar 6, 2010
    189
    31
    10
    I'll try 1.77 as soon as I'm able to download it. Have little problem downloading the file. I'll try to download later. :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. kizwan

    kizwan MDL Member

    Mar 6, 2010
    189
    31
    10
    Hi andy,

    I unable to download 1.77. At first I thought the server is down but when I tried to download Award & AMI tools, I'm able to do so. This is the error message I got:-
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  8. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,671
    2,434
    60
    Should be ok now.
    Andy
     
  9. kizwan

    kizwan MDL Member

    Mar 6, 2010
    189
    31
    10
    Thanks. Just tested 1.77 & it works:-
    It said "2 bytes too big" which is acceptable since I change 10 bytes but it reintegrated successfully. :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  10. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    10,938
    10,477
    340
    Just curious how it did it. Does it move modules then or is there a gap module around?..never did that before at Phoenix new style bioses, it usually failed to reintegrate if the size is too big. I cannot have a look by myself since I'm not at home anymore....:p

    Thanks.
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,671
    2,434
    60
    Some of the modules seem to have FFh padding. In this case there are 10 FFh bytes before the next module which is QWORD aligned. I have just overwritten a couple of those.
    It is technically untested but some of these new Phoenix ones are very similar to EFI, and it's fine there.

    Andy
     
  12. kizwan

    kizwan MDL Member

    Mar 6, 2010
    189
    31
    10
    #12 kizwan, Feb 11, 2011
    Last edited: Feb 11, 2011
    (OP)
    Thank you for the explanation. This explained why I don't have problem reintegrating "F7731B4C-58A2-4DF4-8980-5645D39ECE58.ff" module even though the tool reported it "2 bytes too long". Successful reintegration on two BIOS; Acer Aspire 7730G & Aspire 7738G. However, on Lenovo IdeaPad Y450's BIOS, reintegration failed because there is no FFh bytes between "F7731B4C-58A2-4DF4-8980-5645D39ECE58.ff" module & the next module.

    I have to use Andy's Phoenix SLIC tool for rebuilding Aspire 7730G's BIOS because PBE take a longer time to open it (content of several modules not consistent every time opening it with PBE).

    I can't do anything for Lenovo IdeaPad Y450's BIOS. I can rebuild it with PBE but when I want to check the modified BIOS modules, Andy's Phoenix SLIC tool produced this error:-
    [​IMG]
    So, I guess this error means the modified BIOS is not properly build by PBE.

    So far, I got 100% successful build with Insyde BIOS for this mod (tested by me & others). The module involved is "F7731B4C-58A2-4DF4-8980-5645D39ECE58_3_606.ROM".

    Thank you Andy for your great work. You too Yen. :)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  13. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,671
    2,434
    60
    That could just as easily be a bug also.
    Could you post a link to the bios that causes this

    Andy

     
  14. kizwan

    kizwan MDL Member

    Mar 6, 2010
    189
    31
    10
    #14 kizwan, Feb 15, 2011
    Last edited: Feb 15, 2011
    (OP)
    This file contains original BIOS image, the .ff modified module & SLIC.LOG. Thank you.
    http://www.mediafire.com/?t9qb5hoymxcxfc9

    Ops! Sorry. I just realized that you're referring to the modified BIOS which caused the above error. This is the modified BIOS build with PBE which failed to decompressed using Pheonix SLIC tool:-
    http://www.mediafire.com/?w5v3j4wq07w3s4a
    (This modified BIOS is not tested. Already compared with original image & found out there are too many differences which I believe can bricked the notebook if flashed.)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  15. andyp

    andyp SLIC Tools Author

    Aug 8, 2008
    1,671
    2,434
    60
    There seems to be a zero length module. This is what was upsetting the tool. I doubt it should be there though.
    1.79 can parse properly.

    Andy