Firmware or file LDR hard drive wd usb 3.0

jenny

New member
I hard drive USB 3.0 WD20NMVW, I've converted to sata connectors.
Help me Firmware Or File LDR, I restore the data.
Thank you
wwd2tb.jpg
rom.JPG
 

jol

Member
I'm not familiar with MRT, but can MRT use a LDR made by PC3K ?
I remember reading somewhere (hddguru, I think) that only last ver. of MRT can deal it, (do you have the last ver. ?) Or maybe it's referring to ST LDR's (don't know (remember))
 
jol":2rt2tyae said:
I'm not familiar with MRT, but can MRT use a LDR made by PC3K ?
I remember reading somewhere (hddguru, I think) that only last ver. of MRT can deal it, (do you have the last ver. ?) Or maybe it's referring to ST LDR's (don't know (remember))

Well,
A Western Digital LDR Is Nothing but a Overlay "Pending" Code Structure of Firmware That Should Be Loaded To Memory to Make HDD Function .In WDC 5C,13,11 Etc Modules Are Called LDR.As LDR is Not a Buch Of Files Together Its Impossibly They Are Not Supported By Other Tool If One Tool Has Extracted Them Unlike Seagate LDR File Composed of Multiple Sys Files Etc
 

Jared

Administrator
Staff member
pclab":2dg9t30o said:
Sometimes on MRT it's it failled, but it actually gets loaded.
Check again.

Same thing happens on PC-3000 if the drive is taking too long to respond. Try loading again and see if it says "LDR already loaded" (or something like that). Or just re-check ID and see if it now shows the kernel ID. It should be compatible, I know I've used a lot of MRT LDRs with PC-3000 so I can't see why it wouldn't work the other way.

If you're hearing any SA accessing activity lasting more than a few seconds after power on, it could be that you'll need to block SA access in ROM by changing the SA region location in ROM. That way it'll fail to read the directory module, come ready, and allow LDR upload. Afterward you should then have SA access (assuming heads are good).
 
Top