Luckdeh

updated

4 years ago

Closed

L

Luckdeh

1 Rookie

•

1 Message

3

45605

October 15th, 2022 08:00

Latitude 3420, stuck on firmware update

I restarted my dell latitude 3420 to update my firmware and it is stuck at: flash progress 0% saving manifest. I don't know what to do. It has been stuck for a while now.

  • IMOperations

    1 Rookie

    •

    7 Posts

    22745

    8

    Posted October 17th, 2022 04:00

    Unplug the power and let the battery drain to force shutdown - it takes around 2 hours for a fully charged battery to drop below 50% for it to shut down.

    Once shut down, plug the power back in and let it charge for about 10-20mins for the battery to reach over 50% then boot the machine back up. It will then initiate the BIOS recovery.

    If you can't wait for 2 hours, you'll have to unscrew the back plate to disconnect the battery.

  • DELL-Cares

    Moderator

    •

    27843 Posts

    •

    745 Points

    23026

    1

    Posted October 15th, 2022 08:00

    Hello, I see you are looking for technical assistance. If you need our help, you can start a private message with us and we will be happy to assist you.


    #IWork4Dell

    For all non-technical issues that require your private data, we must communicate via a private Direct Message
    Dell Partner GEM Program, Out of Warranty Support options, No free goodwill repair, Get a copy of your Dell invoice

  • IMOperations

    1 Rookie

    •

    7 Posts

    22757

    1

    Posted October 17th, 2022 01:00

    This has literally just happened to my Latitude 3420 this morning.

  • jandrewsgrci

    1 Message

    22678

    3

    Posted October 17th, 2022 02:00

    This has now started to effect our fleet of 3420's. Have Dell removed the offending update as well as released guidance on how to fix this? Otherwise it feels like Dell is going to be receiving a lot of calls regarding bricked laptops.

  • flthn

    2 Posts

    22657

    1

    Posted October 17th, 2022 03:00

    Has anybody got any information or comments from support? 

  • IMOperations

    1 Rookie

    •

    7 Posts

    22675

    2

    Posted October 17th, 2022 03:00

    I think the only to resolve this is to remove the power and just let the battery drain, forcing a shutdown.

  • SoDan

    3 Posts

    22597

    1

    Posted October 17th, 2022 04:00

    I contacted with online support. I've already tested three laptops with windows 10. Just let the battery drain. Turn on, BIOS auto-recovery will show. After a few minutes, it was possible to log in. Better to hold off updating this bios.

  • GuiLou

    2 Posts

    22604

    0

    Posted October 17th, 2022 04:00

    Same problem here !

    Just Unplug the power and waiting to drain... Hope this solves the problem...

  • GuiLou

    2 Posts

    22460

    0

    Posted October 17th, 2022 07:00

    I confirm the solution reported back, also worked with me!

    thanks

  • Phylum

    32 Posts

    4751

    0

    Posted October 17th, 2022 16:00

    Found other posts for the same issue

    Latitude 3420, stuck on firmware update (https://www.dell.com/community/Latitude/Latitude-3420-stuck... 

    Alert to Dell latitude 3520 about BIOS update (https://www.dell.com/community/Windows-General/Alert-... 

    Dell latitude 3420 Bios update (v.1.22.0, 1.22.0) cause very serious issue (https://www.dell.com/community/Latitude/Dell-latitude-3420-Bios-update-v-1-22-0-1-22-0-cause-very/td-p/8286246) 

    Hey @DELL-Cares and @IMOperations 

    I know of 8 customers who ran into this issue today and calls are still coming in for this problem.  We have a fleet of over 2000 Dell Latitude 3420's, and these are just the ones I know about.

    Customers are reporting that they get stuck in this state for hours.

    Phylum_0-1666048459612.png

     

    In some cases after letting the battery die, they get stuck in a perpetual Auto-Recovery reboot loop.

    Phylum_1-1666048511223.png

    Naturally I have a host of questions

    1. Is this a known issue with Latitude 3420's?
    2. Is this a known issue with this particular update?
    3. Is this a known issue when BIOS updates are applied when certain conditions are met?
    4. Once the issue is resolved (e.g.: by flashing the BIOS from a USB stick via F12), is there anything we can look at on these problem machines to determine the root cause of the failure?
    5. What can we do to avoid this in the future?

    Many thanks