SLIC Masked?: How does that Work?

Discussion in 'BIOS Mods' started by Nestor, Jul 3, 2013.

  1. Nestor

    Nestor MDL Junior Member

    Jan 3, 2009
    57
    5
    0
    Latest BIOS updates for the most of the Fujitsu(-Siemens) laptops first manufactured in 2008 or 2009 have both SLIC 2.0 and 2.1 in them, specifically 4 SLIC's FUJ 2.0, FSC 2.0, FUJ 2.1 and FSC 2.1 (FUJ for Fujitsu; FSC, Fujitsu-Siemens Corp).

    When dumping the BIOS region from the RAM after flashing a Fujitsu PC with one of them (original, not modded) using FlashAid, the RWEverything shows only one SLIC (2.0) read however though a backup of BIOS indicates all four SLIC's have been written.

    How...?

    This question is NOT for getting my pc modded with SLIC 2.1, simply just a question, because I have got my 2 pc's bricked already (and I have never seen a feedback of successful mod of a Fujitsu laptop with FlashAid ever!)
     
  2. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,238
    11,054
    340
    When we developed the Phoenix tool (programmer Andy) we had encountered such BIOSES from Fujitsu-Siemens. Either no SLIC got mapped or the SLIC 2.0 or the SLIC2.1. The BIOS itself had been the same. It's controlled by a special area of the BIOS where the OEM's can set a 'flag' to either tattoo it as SLIC2.0 or SLIC 2.1 or 'free OS'.
    This area is untouched by ordinary BIOS updates.
    It are similar SLP tools to those who have been leaked : http://forums.mydigitallife.net/threads/9055-SLP-Marker-File-Update-Utility

    So the BIOS asks (reads) for such permanent 'flags' and maps either marker 2.0 or marker 2.1 to the pubkey or two completely different SLIC's. If I can remember it right there were different behaviors of such Fujitzu BIOSES. SLICS were fragmented and spread over the BIOS modules (header / pubkey / marker).

    In short: BIOS reads flags (written bytes by a SLP 'tattoo' tool in a non-flashable area) and behaves: no entry-->no SLIC mapped to physical memory, different flags set---> either SLIC2.0 or SLIC 2.1


    The OEM's can license different notebooks by using the same BIOS (update). To mod them properly one needs to have the rw everything report and the BIOS. The best approach had been to introduce a new SLIC anyway and to 'disable' the current (if mapped at all) by renaming SLIC to SLAC.

    AFAIK I had been able to make successful mods, though. And andy's tool can also when properly setup. If you need more details I need to search the forums, but I guess most 'trouble' with those BIOSES had been posted via PM from me to andy and vice versa.....it's been a long time...:)
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  3. Nestor

    Nestor MDL Junior Member

    Jan 3, 2009
    57
    5
    0
    #3 Nestor, Jul 3, 2013
    Last edited: Jul 3, 2013
    (OP)
    Thanks for your detailed explanations.

    BTW coming over to the "2 bricked pc's" stuff, now I wish I had flashed (at least one of) them with WinPlash (on Windows) or a Phoenix dos flasher
    because the BIOS rom files were 1.00 or 2.00 mb large exactly and modded by the simple "replacing" method.
    If ALL bytes were rewritten there should have been no reason for not booting.

    Riding on your talking about Andy, is he now engaged in anything else?
    I played with an Epson bios and found a bug on his AwardTool (reported on the request thread).
    There's been no update yet for the tool since I was said that bug should not have to be PMed to him directly because he should see that...
     
  4. Yen

    Yen Admin
    Staff Member

    May 6, 2007
    11,238
    11,054
    340
    He is rarely online here, I guess he is busy (AFAIK he is a doctor in a hospital)....the project (tools development) hasn't been officially canceled yet........I guess when he has the time to come to here again he'll have a look at it....

    And yes, problems occurred mostly due to a improper flash process. Winphlash was unreliable on Vista first, and the DOS version phlash17 had been very reliable...the later versions of winphlash were reliable even on 64 bit OS...but the phrase always prefer to flash from DOS (or built in flash) has still some validity...(BIOS). With UEFI many things have changed, though....
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...