Help with bringing USB HDD to life? [WD5000LMVW - 11CKRS0]

[Oh no, another noob asking for help :roll:

]
Anyways, Hello!

Im sure youre all here more pro˙s than I am noob, but hope you˙ll find a bit time of yours to at least try to help me.

Okay, so I got this 500GB WD USB HDD some time (years) ago. But drive then started behaving as follows:

1. Plugged in,
2. Drive spinup,
3. Reading something a bit, (no "bad" sounds, only healthy, working HDD clicking noises),
4. Spinoff,
5. Go to sleep and do not wake until power cycled.

Whole it took like 10 secs, nothing showing up of course, not even sound of new recogized PnP device.

So I thought PCB issue! Ordered one, swapped both EEPROMs aaand, nothing. I did it some time ago, so I dont remeber what happened and whatnot but it definitely wasnt working. (I think HDD didnt even spin up it was just chillin there like it wasnt suposed to do anything).

I was desperate. And dumb (okay, im still dumb). So I did what I thought was sensible idea.... OMG Im embarrased.... I mixed and matched the EEPROM Chips. (not the position like they have different footprint). It achieved one thing although I still dont know if its good or bad sign: Drive now shows up...
As... "WD My Passport 07AE USB, MBR, 0,50KB :lol:

"

So... yeah that˙s the current state, hoping someone knows what to do try next.

Here I am some time later, and with enough free time around decided to poke at it again.
BUT, fear not, because I˙m not ordinary "Save my data" noob, I˙m an UltraNoob™! Just - I have some basic understanding of Disk drives, physical as well as logical, also, I have a decent soldering skills, hot air reflow, and EEPROOM programmer, so I can even dump those EEPROOMs here if anyone of you could make some sense of it (I was looking at the sea of FF˙s for a few minutes now, and it didn˙t help me in any way yet :lol:

)

I˙m sure there will be a TON of things and terminologies I won˙t understand, but I˙ll just ask, no shame...

Thank You!

Here are the dumps of the EEPROOMS:

Attachments

EEPROOM.rar: EEPROOMs; (558.52 KiB) Downloaded 401 times

The first ROM (U12) is from a 500GB drive, the second from a 250GB.

Code:: Analysing WINBOND_W25X20_SOIC.bin ... Searching for LDSCs and verifying PCMBlocks ... LDSC LDSC Att PCMBlock RAM size PCMBlk CS Start ID CS Start - End address RAM / ROM Exp/Act --------------------------------------------------------------------------- 0 5A 2B 02 100 - 22A5 12000 21A4 21A4 68DF 68DF OK 20 01 A6 0C 22A6 - 435A A0800000 20B4 20B4 19 19 OK 40 02 A5 01 435B - CDF7 0 c B3FC 8A9C 5B 5B OK 60 03 A5 01 CDF8 - D434 10FAC c 78C 63C B3 B3 OK 80 04 75 03 D435 - D655 80220 c 2EC 220 C5 C5 OK A0 05 CF 03 D656 - D84A 10148A08 c 2F0 1F4 49 49 OK C0 06 6D 01 D84B - 2538F 900CDE00 c 1F748 17B44 2D 2D OK E0 07 A9 01 25390 - 3CB78 90002630 c 20FF8 177E8 65 65 OK LDSC = PM Loader Config String (32 bytes) ID = ID byte of LDSC (byte #0) CS = Checksum byte or word Att = Attributes PCMBlk = Program Code Memory Block Exp = Expected checksum for PCMBLock Act = Actual checksum for PCMBLock c = compressed PCMBlock size = size of decompressed (in RAM) and compressed (in ROM) PCMBlock in bytes ROYL directory module 0x000B found at 0x3F090 Active directory flag = 0x01 Identifying SA regions ... Reg# Reg size Reg loc ---------------------------- 0x00 0x0002B50B 0x00000000 0x01 0x0002B50B 0x00059D00 Verifying ROYL modules ... ID Size (bytes) Address Checksum dir hdr dir hdr ----------------------------------------------------- 0001 N/A 00004000 N/A 0000F471 N/A 000A OK 0000003E 00000200 0003D3C2 00000000 OK 000B OK 00000169 00000200 0003F090 00000000 OK 020B OK 00000169 00000200 0003E090 00000000 OK 0030 OK 00000400 OK 0003D400 00000000 OK 0047 OK 00000400 OK 0003DC00 00000000 OK 000D OK 00000090 00000200 0003F000 00000000 OK 004F OK 00000400 OK 0003D800 00000000 OK ROYL directory module 0x020B found at 0x3E090 Active directory flag = 0x00 Identifying SA regions ... Reg# Reg size Reg loc ---------------------------- 0x00 0x0002B50B 0x00000000 0x01 0x0002B50B 0x00059D00 0x02 0x0002B50B 0x000B3A00 0x03 0x00000000 0x00000000 0x04 0x00000000 0x00000000 0x05 0x00000000 0x00000000 0x06 0x00000000 0x00000000 0x07 0x00000000 0x00000000 Verifying ROYL modules ... ID Size (bytes) Address Checksum dir hdr dir hdr ----------------------------------------------------- 0001 N/A 00004000 N/A 00000000 N/A 000A OK 0000003E 00000200 0003D3C2 00000000 OK 000B OK 00000169 00000200 0003F090 00000000 OK 020B OK 00000169 00000200 0003E090 00000000 OK 0030 OK 00000400 OK 0003D400 00000000 OK 0047 OK 00000400 OK 0003DC00 00000000 OK 000D OK 00000090 00000200 0003E000 00000000 OK 004F OK 00000400 OK 0003D800 00000000 OK dir - Module ID/Size as reported in directory module (0x20B or 0x0B) hdr - Module ID/Size as reported in module's header N/A - Not Applicable BAD - Module has invalid checksum. This may be due to non-existent module. ROM modules saved to Flash_00\000Bmods and Flash_00\020Bmods Active directory is 0x0B Analysing active 0x0A module ... Head map checksum (Expected / Actual) = 0x0000 / 0x0000 - OK Number of heads (physical / in use) = 2/2 Head map #1 = 0x03 / 0b00000011 Head map #2 = 0x00 / 0b00000000 DCM = | N | 1 S K J D 1 S : : : : : : : : : : : : : : : : : : : unknown : : : : : : : : top VCM : : : : : : : ACA : : : : : : bottom VCM : : : : : HSA : : : : media : : : preamp : : latch : base spindle motor Analysing active 0x0D module ... Firmware Version = 01.01A01 World Wide Name = 50014EE25CD67686 Model Number = WDC WD5000LMVW-11CKRS0 Serial Number = Analysing active 0x4F module ... ROM version = 0002004C Analysing active 0x47 module ... Preamp values ----------- 0 032E3611 1 012B140C 2 02200400 3 02200400 4 02200400 5 02200400 Microjogs ------- 0 116B 1 0FE9 2 0A0A 3 0A0A 4 0A0A 5 0A0A Head/Media DCM = KS

Code:: Analysing UNKNOWN_SOIC_A25L020_possibly_original.bin ... Searching for LDSCs and verifying PCMBlocks ... LDSC LDSC Att PCMBlock RAM size PCMBlk CS Start ID CS Start - End address RAM / ROM Exp/Act --------------------------------------------------------------------------- 0 5A 43 02 100 - 22B1 12000 21B0 21B0 FC98 FC98 OK 20 01 22 0C 22B2 - 439E A0800000 20EC 20EC 80 80 OK 40 02 26 01 439F - CE4F 0 c B410 8AB0 6B 6B OK 60 03 32 01 CE50 - D49C 10FAC c 7A0 64C 58 58 OK 80 04 DD 03 D49D - D6BD 80220 c 2EC 220 53 53 OK A0 05 37 03 D6BE - D8B2 10148A08 c 2F0 1F4 F1 F1 OK C0 06 5C 01 D8B3 - 2563B 900CDE00 c 1FA40 17D88 1B 1B OK E0 07 97 01 2563C - 3CF90 90002630 c 21258 17954 9A 9A OK LDSC = PM Loader Config String (32 bytes) ID = ID byte of LDSC (byte #0) CS = Checksum byte or word Att = Attributes PCMBlk = Program Code Memory Block Exp = Expected checksum for PCMBLock Act = Actual checksum for PCMBLock c = compressed PCMBlock size = size of decompressed (in RAM) and compressed (in ROM) PCMBlock in bytes ROYL directory module 0x000B found at 0x3F090 Active directory flag = 0x00 Identifying SA regions ... Reg# Reg size Reg loc ---------------------------- 0x00 0x0002B50B 0x00000000 0x01 0x0002B50B 0x00059D00 0x02 0x0002B50B 0x000B3A00 0x03 0x00000000 0x00000000 0x04 0x00000000 0x00000000 0x05 0x00000000 0x00000000 0x06 0x00000000 0x00000000 0x07 0x00000000 0x00000000 Verifying ROYL modules ... ID Size (bytes) Address Checksum dir hdr dir hdr ----------------------------------------------------- 0001 N/A 00004000 N/A 00000000 N/A 000A OK 0000003E 00000200 0003D3C2 00000000 OK 000B OK 00000169 00000200 0003F090 00000000 OK 020B OK 00000169 00000200 0003E090 00000000 OK 0030 OK 00000400 OK 0003D400 00000000 OK 0047 OK 00000400 OK 0003DC00 00000000 OK 000D OK 00000090 00000200 0003F000 00000000 OK 004F OK 00000400 OK 0003D800 00000000 OK ROYL directory module 0x020B found at 0x3E090 Active directory flag = 0x01 Identifying SA regions ... Reg# Reg size Reg loc ---------------------------- 0x00 0x0002B50B 0x00000000 0x01 0x0002B50B 0x0002CE80 Verifying ROYL modules ... ID Size (bytes) Address Checksum dir hdr dir hdr ----------------------------------------------------- 0001 N/A 00004000 N/A 0001AD95 N/A 000A OK 0000003E 00000200 0003D3C2 00000000 OK 000B OK 00000169 00000200 0003F090 00000000 OK 020B OK 00000169 00000200 0003E090 00000000 OK 0030 OK 00000400 OK 0003D400 00000000 OK 0047 OK 00000400 OK 0003DC00 00000000 OK 000D OK 00000090 00000200 0003E000 00000000 OK 004F OK 00000400 OK 0003D800 00000000 OK dir - Module ID/Size as reported in directory module (0x20B or 0x0B) hdr - Module ID/Size as reported in module's header N/A - Not Applicable BAD - Module has invalid checksum. This may be due to non-existent module. ROM modules saved to Flash_01\000Bmods and Flash_01\020Bmods Active directory is 0x20B Analysing active 0x0A module ... Head map checksum (Expected / Actual) = 0x0000 / 0x0000 - OK Number of heads (physical / in use) = 2/1 Head map #1 = 0x01 / 0b00000001 Head map #2 = 0x00 / 0b00000000 DCM = | N | 1 Z R K H 1 S : : : : : : : : : : : : : : : : : : : unknown : : : : : : : : top VCM : : : : : : : ACA : : : : : : bottom VCM : : : : : HSA : : : : media : : : preamp : : latch : base spindle motor Analysing active 0x0D module ... Firmware Version = 01.01A01 World Wide Name = 50014EE2076952E6 Model Number = WDC WD2500LMVW-11CKRS0 Serial Number = Analysing active 0x4F module ... ROM version = 0002005R Analysing active 0x47 module ... Preamp values ----------- 0 03323419 1 05303415 2 02200400 3 02200400 4 02200400 5 02200400 Microjogs ------- 0 1139 1 10DD 2 0A0A 3 0A0A 4 0A0A 5 0A0A Head/Media DCM = RZ

The two bridge firmwares differ in several places.

These are the headers:

WINBOND_W25X20.bin (USB VID / PID = 1058 / 10A2)

Code:: Offset(h) 00 02 04 06 08 0A 0C 0E 00000000 4551 4457 5758 3631 4139 3258 3132 3437 EQDWWX61A92X1247 00000010 2020 2020 2020 2020 0300 0009 1058 10A2 .....X.¢ ^^^^^^^^^ 00000020 180C 0000 3160 373A 0000 0000 0000 0000 ....1`7:........ 00000030 0000 0000 1201 4457 0000 0900 0300 0000 ......DW........ 00000040 0000 0000 0060 373A 0000 0000 0000 0000 .....`7:........ 00000050 0000 0000 1201 4457 EEEE EEEE EEEE EEEE ......DWîîîîîîîî 00000060 EEEE EEEE EEEE EEEE EEEE EEEE EEEE EEEE îîîîîîîîîîîîîîîî 00000070 EEEE EEEE EEEE EEEE EEEE EEEE EEEE EEEE îîîîîîîîîîîîîîîî 00000080 EEEE EEEE EEEE EEEE 2201 4457 0000 0000 îîîîîîîî".DW.... 00000090 0000 0000 0100 0000 E44F 574F FFFF FFFF ........äOWOÿÿÿÿ

AMIC_A25L020_possibly_original.bin (USB VID / PID = 1058 / 07AE)

Code:: Offset(h) 00 02 04 06 08 0A 0C 0E 00000000 4551 4457 5758 3631 4139 3258 3132 3437 EQDWWX61A92X1247 00000010 2020 2020 2020 2020 0000 000D 1058 07AE .....X.® ^^^^^^^^^ 00000020 180C 0000 3060 383A 0000 0000 0000 0000 ....0`8:........ 00000030 0000 0000 1201 4457 0000 0900 0300 0000 ......DW........ 00000040 0000 0000 0060 383A 0000 0000 0000 0000 .....`8:........ 00000050 0000 0000 1201 4457 EEEE EEEE EEEE EEEE ......DWîîîîîîîî 00000060 EEEE EEEE EEEE EEEE EEEE EEEE EEEE EEEE îîîîîîîîîîîîîîîî 00000070 EEEE EEEE EEEE EEEE EEEE EEEE EEEE EEEE îîîîîîîîîîîîîîîî 00000080 EEEE EEEE EEEE EEEE 2201 4457 0000 0000 îîîîîîîî".DW.... 00000090 0000 0000 0100 0000 E84F 5E3F FFFF FFFF ........èO^?ÿÿÿÿ

AFAICT, 10A2 is the PID for a WD Elements.

My Passport would be encrypted, Elements is not.

Okay, so both those WINBONDs seems to be the original, so I marked the possibly originals completely other way around :lol:

well, nevermind, lets just say I marked "originals" as those on the replacement PCB...

Anyways, it still doesn´t work... ...At the time I was writing this...

But, then I figured, I don´t need content of those other EEPROOMs (for passport) anyways and I had 2 boards of which I didnt know which one is working and which one is broken.

And the other 2 flash were same sizes anyways so I overwrote them with the correct memory content for my HDD, from corresponding winbond EEPROOMs.

So now I had 2 PCBs, on one apparentely original winbond EEPROOMs, on the second other two EEPROOMs with now identical memory content, didn´t know which one worked. The one with the winbond has not worked so I just tried the other one, and...

It right up showed in system, loaded partitions, and all data appear to be fully readable, I have no idea what´s going on.... But it works!

The NTFS had some filesystem errors, checkdisk handled that, and now I´m doing surface test, just in case something shows up, and then off with the data!

Only thing I haven´t figured out is why?. Why it hasn´t worked and why it works with copied EEPROOMs? I don´t know, but perhaps some of you might know...

OF course, not to forget BIG THANKS to fzabkar! I would not be here with (for) now working drive here without his help! I very much appreceiate that dump analysis!

you may want to backup that data asap.

HaQue wrote:you may want to backup that data asap.

Of course, that already done!

Help with bringing USB HDD to life? [WD5000LMVW - 11CKRS0]

Help with bringing USB HDD to life? [WD5000LMVW - 11CKRS0]

Re: Help with bringing USB HDD to life? [WD5000LMVW - 11CKRS

Re: Help with bringing USB HDD to life? [WD5000LMVW - 11CKRS

Re: Help with bringing USB HDD to life? [WD5000LMVW - 11CKRS

Re: Help with bringing USB HDD to life? [WD5000LMVW - 11CKRS

Re: Help with bringing USB HDD to life? [WD5000LMVW - 11CKRS

Re: Help with bringing USB HDD to life? [WD5000LMVW - 11CKRS