Bios needed, Dell E5550, Tag FSFB262, Zam80 La-911P Rev.1

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • re1nhold
    Member
    • Jul 2025
    • 10
    • Germany

    #1

    Bios needed, Dell E5550, Tag FSFB262, Zam80 La-911P Rev.1

    Hello Guys

    I'm currently fixing two different Dell latitudes,
    I need a E5550 BIOS - SERVICE TAG is: FSFB262

    So far I flashed about 6 BIOS from this forum already,
    none worked,
    only fan spin ~3s, LCD black, keyboard LED on/off ok,
    I tried manual extraction with scripts for ages so to speak. VM is untried yet.
    This laptop is not burnt, it seems to just have a corrupted BIOS.
    I extra baught ram. This has to work friends.

    Do you generate it this way in Windows in CMD?:
    Code:
    E5550A24.exe /writeromfile C:\bios.fd
    Please help
    PS: official BIOS version works better than older versions? I don't know.
    Attached Files
  • Answer selected by re1nhold at 07-20-2025, 08:44 AM.
    re1nhold
    Member
    • Jul 2025
    • 10
    • Germany

    correction this image above fsf262 has me and its activated, but not latest version, it has 20 modules the latest has 28 and this above has a working BIOS
    i disabled altme bit on mine, and it seems ok so far very short term.
    more would be nice but the cleaner version i use has a bug it always removes 2 to 4 essential modules

    Comment

    • re1nhold
      Member
      • Jul 2025
      • 10
      • Germany

      #2
      +3.3V_ALW tested +2.99V
      Seems a bit low?
      Too low?

      Comment

      • re1nhold
        Member
        • Jul 2025
        • 10
        • Germany

        #3
        Now +3.3V_ALW is +3.27V

        Comment

        • re1nhold
          Member
          • Jul 2025
          • 10
          • Germany

          #4
          I ME cleaned "generic" BIOS images from the forum, including "original" dump from actual chip, not even getting a fan spin, seems corrupted, but with others it spins and flashes LED.

          I keep testing rails and me_cleaned images.
          I need help BIOS for FSFB262


          On the generic it finds 28 partitions on the "original" on the chip just 20
          generic:
          python me_cleaner.py -S -O modified_20200918_215536_SVOD3+ME10.0.56.3002.bin 20200918_215536_SVOD3+ME10.0.56.3002.bin
          Full image detected
          Found FPT header at 0x5010
          Found 28 partition(s)
          Found FTPR header: FTPR partition spans from 0x160000 to 0x210000
          ME/TXE firmware version 10.0.56.3002 (generation 2)
          Public key match: Intel ME, firmware versions 9.5.x.x, 10.x.x.x
          The AltMeDisable bit is NOT SET
          Reading partitions list...
          PSVN (0x00000bc0 - 0x000000c00, 0x00000040 total bytes): removed
          FOVD (0x00000c00 - 0x000001000, 0x00000400 total bytes): removed
          MDES (0x00001000 - 0x000002000, 0x00001000 total bytes): removed
          FCRS (0x00002000 - 0x000003000, 0x00001000 total bytes): removed
          EFFS (0x00003000 - 0x0000df000, 0x000dc000 total bytes): removed
          BIAL (NVRAM partition, no data, 0x0000add3 total bytes): nothing to remove
          BIEL (NVRAM partition, no data, 0x00003522 total bytes): nothing to remove
          BIIS (NVRAM partition, no data, 0x00036000 total bytes): nothing to remove
          FTPM (NVRAM partition, no data, 0x0000b380 total bytes): nothing to remove
          NVCL (NVRAM partition, no data, 0x000069c9 total bytes): nothing to remove
          NVCM (NVRAM partition, no data, 0x0000439b total bytes): nothing to remove
          NVCP (NVRAM partition, no data, 0x0000a60a total bytes): nothing to remove
          NVHM (NVRAM partition, no data, 0x00000058 total bytes): nothing to remove
          NVJC (NVRAM partition, no data, 0x000051e4 total bytes): nothing to remove
          NVKR (NVRAM partition, no data, 0x00005c3a total bytes): nothing to remove
          NVNF (NVRAM partition, no data, 0x0000186c total bytes): nothing to remove
          NVOS (NVRAM partition, no data, 0x0003dcce total bytes): nothing to remove
          NVSH (NVRAM partition, no data, 0x000022d0 total bytes): nothing to remove
          NVSM (NVRAM partition, no data, 0x00001de8 total bytes): nothing to remove
          NVUK (NVRAM partition, no data, 0x00008bb7 total bytes): nothing to remove
          PLDM (NVRAM partition, no data, 0x000043c5 total bytes): nothing to remove
          TMNN (NVRAM partition, no data, 0x000001a6 total bytes): nothing to remove
          GLUT (0x000df000 - 0x0000e8000, 0x00009000 total bytes): removed
          LOCL (0x000e8000 - 0x0000ec000, 0x00004000 total bytes): removed
          WCOD (0x000ec000 - 0x000160000, 0x00074000 total bytes): removed
          FTPR (0x00160000 - 0x000210000, 0x000b0000 total bytes): NOT removed
          NFTP (0x00210000 - 0x00048a000, 0x0027a000 total bytes): removed
          MDMV (0x0048a000 - 0x0004ca000, 0x00040000 total bytes): removed
          Removing partition entries in FPT...
          Removing EFFS presence flag...
          Correcting checksum (0xd9)...
          Reading FTPR modules list...
          UPDATE (LZMA , 0x1ce19a - 0x1ce345 ): removed
          ROMP (Huffman, fragmented data, ~1 KiB ): NOT removed, essential
          BUP (Huffman, fragmented data, ~85 KiB ): NOT removed, essential
          KERNEL (Huffman, fragmented data, ~242 KiB ): removed
          POLICY (Huffman, fragmented data, ~99 KiB ): removed
          FTPM (LZMA , 0x1ce345 - 0x1df6f8 ): removed
          HOSTCOMM (LZMA , 0x1df6f8 - 0x1e8bfa ): removed
          FPF (LZMA , 0x1e8bfa - 0x1ea829 ): removed
          The ME minimum size should be 1572864 bytes (0x180000 bytes)
          The ME region can be reduced up to:
          00005000:00184fff me
          Setting the AltMeDisable bit in PCHSTRP10 to disable Intel ME...
          Checking the FTPR RSA signature... VALID
          Done! Good luck!



          "original" dump:
          python me_cleaner.py -S -O modified_e5550_MEINS.bin e5550_MEINS.bin
          Full image detected
          Found FPT header at 0x5010
          Found 20 partition(s)
          Found FTPR header: FTPR partition spans from 0x4f000 to 0xe6000
          ME/TXE firmware version 10.0.30.1072 (generation 2)
          Public key match: Intel ME, firmware versions 9.5.x.x, 10.x.x.x
          The AltMeDisable bit is NOT SET
          Reading partitions list...
          PSVN (0x00000bc0 - 0x000000c00, 0x00000040 total bytes): removed
          FOVD (0x00000c00 - 0x000001000, 0x00000400 total bytes): removed
          MDES (0x00001000 - 0x000002000, 0x00001000 total bytes): removed
          FCRS (0x00002000 - 0x000003000, 0x00001000 total bytes): removed
          EFFS (0x00003000 - 0x00004b000, 0x00048000 total bytes): removed
          FTPM (NVRAM partition, no data, 0x0000b380 total bytes): nothing to remove
          NVCL (NVRAM partition, no data, 0x000069c9 total bytes): nothing to remove
          NVCP (NVRAM partition, no data, 0x0000a5cc total bytes): nothing to remove
          NVHM (NVRAM partition, no data, 0x00000058 total bytes): nothing to remove
          NVJC (NVRAM partition, no data, 0x00003da0 total bytes): nothing to remove
          NVKR (NVRAM partition, no data, 0x00005c3a total bytes): nothing to remove
          NVNF (NVRAM partition, no data, 0x0000186c total bytes): nothing to remove
          NVSH (NVRAM partition, no data, 0x000022d0 total bytes): nothing to remove
          NVSM (NVRAM partition, no data, 0x00001de8 total bytes): nothing to remove
          NVUK (NVRAM partition, no data, 0x00008bb7 total bytes): nothing to remove
          TMNN (NVRAM partition, no data, 0x000001a6 total bytes): nothing to remove
          GLUT (0x0004b000 - 0x00004f000, 0x00004000 total bytes): removed
          FTPR (0x0004f000 - 0x0000e6000, 0x00097000 total bytes): NOT removed
          NFTP (0x000e6000 - 0x000143000, 0x0005d000 total bytes): removed
          MDMV (0x00143000 - 0x00017d000, 0x0003a000 total bytes): removed
          Removing partition entries in FPT...
          Removing EFFS presence flag...
          Correcting checksum (0x9f)...
          Reading FTPR modules list...
          UPDATE (LZMA , 0x0bd3d8 - 0x0bd583 ): removed
          ROMP (Huffman, fragmented data, ~1 KiB ): NOT removed, essential
          BUP (Huffman, fragmented data, ~86 KiB ): NOT removed, essential
          KERNEL (Huffman, fragmented data, ~242 KiB ): removed
          POLICY (Huffman, fragmented data, ~100 KiB ): removed
          FTPM (LZMA , 0x0bd583 - 0x0ce8fa ): removed
          HOSTCOMM (LZMA , 0x0ce8fa - 0x0d7e0c ): removed
          FPF (LZMA , 0x0d7e0c - 0x0d9a3d ): removed
          The ME minimum size should be 454656 bytes (0x6f000 bytes)
          The ME region can be reduced up to:
          00005000:00073fff me
          Setting the AltMeDisable bit in PCHSTRP10 to disable Intel ME...
          Checking the FTPR RSA signature... VALID
          Done! Good luck!

          ​

          Comment

          • SMDFlea
            Super Moderator
            • Jan 2018
            • 20695
            • UK

            #5
            Why run python me_cleaner.py it will disable the ME firmware or make it unbootable
            All donations to badcaps are welcome, click on this link to donate. Thanks to all supporters

            Comment

            • re1nhold
              Member
              • Jul 2025
              • 10
              • Germany

              #6
              kind of a rhetorical question.
              to reduce interaction with your system.
              not to make it not boot ofcourse.

              So why flash a random "sibling" BIOS from here on winbond BIOS chip?
              It'll replace your BIOS or make it unbootable, duh.

              Comment

              • re1nhold
                Member
                • Jul 2025
                • 10
                • Germany

                #7
                The E5550 don't POST to begin with. Untouched, No Power On Selftest

                Comment

                • re1nhold
                  Member
                  • Jul 2025
                  • 10
                  • Germany

                  #8
                  Got it working just now.
                  The board was fine.
                  BIOS was corrupted.
                  replaced successfully.
                  POST works.
                  SETUP F2 works too.
                  FSF262 image attached for anyone needing it.
                  ME may be missing. but I did it with this one.
                  just keep in mind it might take 1 or two minutes or so to boot.😂
                  But it boots on mine and might be enough to do an update .exe, etc. etc.
                  Jesus is LORD.
                  Attached Files

                  Comment

                  • re1nhold
                    Member
                    • Jul 2025
                    • 10
                    • Germany

                    #9
                    correction this image above fsf262 has me and its activated, but not latest version, it has 20 modules the latest has 28 and this above has a working BIOS
                    i disabled altme bit on mine, and it seems ok so far very short term.
                    more would be nice but the cleaner version i use has a bug it always removes 2 to 4 essential modules

                    Comment

                    Related Topics

                    Collapse

                    Working...