Dell Latitude E5550 FW status recovery error & unable to reboot

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • a_tiny_ant
    New Member
    • Dec 2021
    • 6
    • Netherlands

    #1

    Dell Latitude E5550 FW status recovery error & unable to reboot

    Hi everyone

    Since a month or so my laptop, a refurbished Dell Latitude E5550, has been unable to exit sleep mode or properly reboot. Upon waking from sleep mode it shuts down and reboots and upon attempting a reboot it just hangs at a black screen forever. The laptop was working fine for several years up until a month ago.

    Initially I thought it was OS related, since it's running Arch Linux, wouldn't be the first time an update broke something but it also happens on Windows, Ubuntu live images and even a complete restored image from a year ago where it definitely worked fine.

    Upon booting the message "FW Status recovery error" is visible and in the boot menu I'm unable to enter the MEBx extension menu. It just reboots then and afterwards the MEBx extension menu disappears from the boot menu.
    Apparently the FW error is caused by a corrupted Intel Management Engine according to some threads found on Google.

    In the BIOS there's no way to disable MEBx, it's only possible to disable hotkeys or menu entries from here. I've never used any of these functions and they're better off disabled, but they never caused any issues either up until now.

    The CMOS battery is not the issue, I've replaced that already but it wasn't even necessary according to the batteries' voltage.

    Now the most annoying side effect, flashing a new BIOS which could fix the issue does not work because it requires a reboot, which at this moment the laptop is unable to do.
    Perhaps it's possible that a MOSFET on the mainboard, that controls power states, is somehow fried? Is there any proper way to figure that out according to the schematics?

    Is it possible to reflash the BIOS and/or MEBx part from either Linux or Windows that doesn't require a reboot?

    Thanks!
    Last edited by a_tiny_ant; 12-10-2021, 04:13 PM.
  • SMDFlea
    Super Moderator
    • Jan 2018
    • 20446
    • UK

    #2
    Re: Dell Latitude E5550 FW status recovery error & unable to reboot

    Originally posted by a_tiny_ant
    Is it possible to reflash the BIOS and/or MEBx part from either Linux or Windows that doesn't require a reboot?

    Thanks!
    Its the ME firmware thats corrupt.You can try flashing the bios from windows, it will/should update the ME firmware https://dl.dell.com/FOLDER06331241M/1/E5550A24.exe .

    Be warned though,the update could go wrong,and then you`ll need to flash another bios with an SPI programmer.
    All donations to badcaps are welcome, click on this link to donate. Thanks to all supporters

    Comment

    • a_tiny_ant
      New Member
      • Dec 2021
      • 6
      • Netherlands

      #3
      Re: Dell Latitude E5550 FW status recovery error & unable to reboot

      Originally posted by SMDFlea
      Its the ME firmware thats corrupt.You can try flashing the bios from windows, it will/should update the ME firmware https://dl.dell.com/FOLDER06331241M/1/E5550A24.exe .

      Be warned though,the update could go wrong,and then you`ll need to flash another bios with an SPI programmer.
      Thanks but that is the one thing that didn't work. That executable forces a reboot which then gets permanently stuck. Also running it from the boot menu, or even FreeDOS, they all require a reboot before the bios is flashed.

      I've also tried extracting the BIOS bin files using Dell_PFS_Extract and that produces 10 different bin files. I assume the BIOS needs to be flashed with one BIN file if using an SPI programmer right? It looks like it will have to be done this way.
      Last edited by a_tiny_ant; 12-11-2021, 02:07 AM.

      Comment

      • SMDFlea
        Super Moderator
        • Jan 2018
        • 20446
        • UK

        #4
        Re: Dell Latitude E5550 FW status recovery error & unable to reboot

        Originally posted by a_tiny_ant
        Thanks but that is the one thing that didn't work. That executable forces a reboot which then gets permanently stuck. Also running it from the boot menu, or even FreeDOS, they all require a reboot before the bios is flashed.

        I've also tried extracting the BIOS bin files using Dell_PFS_Extract and that produces 10 different bin files. I assume the BIOS needs to be flashed with one BIN file if using an SPI programmer right? It looks like it will have to be done this way.
        The extracted files are only ME FW and a bios update.If you make a backup post it in the Bios requests section and someone will repair it

        https://www.badcaps.net/forum/forumdisplay.php?f=40
        All donations to badcaps are welcome, click on this link to donate. Thanks to all supporters

        Comment

        • a_tiny_ant
          New Member
          • Dec 2021
          • 6
          • Netherlands

          #5
          Re: Dell Latitude E5550 FW status recovery error & unable to reboot

          Right. I have extracted the BIN files from the executable, not my actual BIOS yet.
          I haven't identified the correct chip yet from the boardview/schematics yet.

          Is there an easy way to tell which one it is? There are two 8 legged Winbond chips that are connected to the CMOS battery, however one of them is for 32bit and the other for 64?

          Comment

          • SMDFlea
            Super Moderator
            • Jan 2018
            • 20446
            • UK

            #6
            Re: Dell Latitude E5550 FW status recovery error & unable to reboot

            Originally posted by a_tiny_ant
            Right. I have extracted the BIN files from the executable, not my actual BIOS yet.
            I haven't identified the correct chip yet from the boardview/schematics yet.

            Is there an easy way to tell which one it is? There are two 8 legged Winbond chips that are connected to the CMOS battery, however one of them is for 32bit and the other for 64?
            Both of them,the bios is split across both chips. Make a backup first, then flash both of the bios at post #23 https://www.badcaps.net/forum/showth...t=65154&page=2
            All donations to badcaps are welcome, click on this link to donate. Thanks to all supporters

            Comment

            Related Topics

            Collapse

            • spice_disc
              Vizio TV M50-C1 reboot cycle and static on screen
              by spice_disc
              I'm currently trying to diagnose and fix my Vizio TV (Model M50-C1). I've tried a number of different basic solutions, but I'm trying to determine if my issue is currently a failing panel, T-Con board, or main board (or something else entirely) and whether or not it is worth my time to fix it. Details of the issue and what I've tried are below as well as why I think it is either a bad panel, T-Con board, or main board.

              The Issue: The TV will be on and working fine but after the TV is on for ~5-10 minutes the screen will freeze (with sound continuing) until the TV reboots itself. While...
              09-08-2024, 02:37 PM
            • volinakis
              Chromebook recovery failed - how to fix it
              by volinakis
              So I had a Asus C433T Chromebook enrolled and after I modified bios I had to reinstall Chromium. I made a USB recovery stick with Chromebook Recovery Utility but I got "an unexpected error has occurred ..." message. I did try with another USB stick, etc. etc. -all steps found on internet about this issue and nothing worked.
              Finally I found a site where they suggested to try with an older image and ... it worked!
              What I did:
              - when “Chrome OS is missing or damaged” message appeared I pressed Tab key and found: read only firmware id: Google_Rammus. xxxxx.xxx.x....
              09-18-2023, 03:26 PM
            • reformatt
              Mac BootROM manual update
              by reformatt
              So following on from this thread, I've been meaning to work out a way to update these boards manually without either having to pull the PROM or doing a reinstall of MAC OS. If I'm just fixing a board, I should be able to just update like you do on a PC laptop right? Well this is an Apple product......

              Firmware is well hidden in the installer. But once you've found it, you can just dump it on a memory stick or a spare SSD with Big Sur installed. Many thanks to StarterGo on GitHub for the pointers. I've done this for Macbook Air 820-3437 and 820-00165 boards, but other non T2 machines...
              03-22-2023, 11:12 PM
            • myth77
              macbook pro a2141 can not make recovery
              by myth77
              So, i dont know almost anything on macs..but this is my nephews so i had to try. Its 16 inch macbook pro from 2019...It all started when he left something on the keyboard when closing the mac and there it was the crack on screen. At first it was like working but later no. After that he told me that it wouldnt power on?...hear fans but nothing..tried like 100 of stuffs but nothing helped.

              So, he bring it to me...first i open it and figured he did also. there was lots of dust i cleaned everything...and started it...the broken screen showed only backlight but nothing on the screen. I...
              06-19-2022, 11:21 AM
            • ugamazing
              820-00850 & 820-01949, No WiFi *In Recovery*
              by ugamazing
              I've got two boards with the exact same issue, and it's confusing the hell out of me. In short:

              1. Both boards behave *exactly* the same; they will show WiFi networks to connect to, and will boot fully to Internet Recovery, but they each show zero available WiFi networks once booted to Internet Recovery. I also cannot switch WiFi "off", as in, the toggle will not move.

              2. Both boards will erase perfectly fine using the "erase mac" function; I can wipe them with disk utility, but if I try to install MacOS from Internet Recovery, it says to connect...
              01-25-2023, 05:39 PM
            • Loading...
            • No more items.
            Working...