Skip to content

Instantly share code, notes, and snippets.

@weshouman
Created March 17, 2024 12:03
Show Gist options
  • Save weshouman/f121ed7de0b5aa0bc3be71e5c57ee0c2 to your computer and use it in GitHub Desktop.
Save weshouman/f121ed7de0b5aa0bc3be71e5c57ee0c2 to your computer and use it in GitHub Desktop.
Recovering WD SA510 Firmware 5215100

Recovering WD SA510 Firmware 52015100

Issue

WD SA510 defaults to having firmware version 52015100 which self-destructs itself, preventing further access to the drive and preventing updating it.

Failing Attempts

Following attempts were tried and failed

  • Reading the data under Linux (some partitions showed some dir others did not)
  • Rescuing the data using ddrescue (all kinds of errors and bad sectors showed up)
  • Reading the data under Windows (the drive was not identifiable)
  • Official upgrade through WD Dashboard utility (The tool breaks when tries to communicate with the SSD)

Diagnoses

The firmware needs to be upgraded, but the official methodology to update was not working because the firmware is failing.
I also noticed that the smartctl utility on the device worked when I left the drive for some time and tried to open it later. Suggesting that may be the freezer trick (keeping the drive in freezer for some time, in my case ~5 min) would give us some time.

Working Attempt

Following this guide of Trying to update the firmware using the Linux based Embedded Toolkit by Western Digital, here are the steps for the upgrade:

Preparation

Firmware Upgrade

  • Frozen the drive for 5 min

  • Booted from the USB stick

  • Click select device and choose the broken SSD CAUTION to be taken for this step

    • In my case, I had the device disconnected, and in the first scan I was able to locate the previously connected drive that I don't want to wipe
    • Then I externally connected the drive I want to upgrade the firmware using an enclosure
    • Then I chose to rescan
    • Then the newly appearing drive was clearly the one I want to wipe
  • Enter the firmware file name in our case it's 52046100.fluf

  • Then start the upgrade, if it completed succussfully you would be able to capture the data from the device. In my case I kept it connected, booted from a Linux machine with the enclosure connected then I was able to copy all the data before trying to do any operation

Appendix

The firmware link was known by following those steps

@gadgetman1966
Copy link

gadgetman1966 commented Dec 19, 2024

Cannot get the USB to boot, says no operating system found.

@pipefunk
Copy link

The download is no longer available, could someone upload it please?

@jagodalewandowska
Copy link

I forgot to update if anyone is interested - I contacted WD/Sandisk support and received a new drive after they received the faulty one. It was also free of charge, they paid for the UPS label as well. Worth a go.

Unfortunately @pipefunk I don't have it anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment