Switch to full style
Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
Post a reply

Loader Needed for Hubble LT

August 8th, 2016, 15:07

WDC WD5000LPVX-08V0TT5
ROM version............................. : 06.2TJ
ROM F/W version......................... : 0006002T
Overlay F/W version..................... : 06.2TJ
Servo F/W version....................... : NE.11

Any help would be appreciated.

Re: Loader Needed for Hubble LT

November 30th, 2016, 13:03

I'm looking this loader too.

Re: Loader Needed for Hubble LT

November 30th, 2016, 13:25

I'm afraid I don't have that one. Closest I've got is 0006001T.

Why not just use a close ROM + LDR to get SA access and then extract the LDR from the drive itself? That's what I usually do.

Re: Loader Needed for Hubble LT

November 30th, 2016, 13:35

data-medics wrote:Why not just use a close ROM + LDR to get SA access and then extract the LDR from the drive itself? That's what I usually do.

That is indeed what I ended up doing, but it took a few ROM's to find the right one.

Re: Loader Needed for Hubble LT

November 30th, 2016, 14:02

Can you share the LDR now that you've extracted it?

Re: Loader Needed for Hubble LT

November 30th, 2016, 14:07

data-medics wrote:Can you share the LDR now that you've extracted it?

Let me take a look.

Re: Loader Needed for Hubble LT

December 1st, 2016, 4:17

here you go : 0006001T

good luck
Attachments
0006001T_LDR.rar
(443.38 KiB) Downloaded 415 times

Re: Loader Needed for Hubble LT

December 1st, 2016, 12:57

Looks like einstein9 beat me to it :-)

Re: Loader Needed for Hubble LT

December 1st, 2016, 14:18

ddrecovery wrote:Looks like einstein9 beat me to it :-)

He shared 6001T....yours was supposed to be 6002T.

Re: Loader Needed for Hubble LT

December 3rd, 2016, 6:17

mr_spokk wrote:
ddrecovery wrote:Looks like einstein9 beat me to it :-)

He shared 6001T....yours was supposed to be 6002T.


its the only close one i have :>

Re: Loader Needed for Hubble LT

December 3rd, 2016, 9:50

Why not just use a close ROM + LDR to get SA access and then extract the LDR from the drive itself? That's what I usually do.


I'm interested in this thing ... what steps need to make this operation? I have Wdmarvel and MRTpro ..

Thank you in advance.

Re: Loader Needed for Hubble LT

December 3rd, 2016, 14:04

arvika wrote:I'm looking this loader too.

I just managed to find details about this drive as my initial post was over 4 months ago. I tried 7 or 8 different ROM and Loader version and none would give SA access, which probably meant head issues. In the meantime the client decided not to go ahead with the recovery so we didn't pursue it any further. Sorry I couldn't help.

Re: Loader Needed for Hubble LT

December 3rd, 2016, 14:50

jackass25 wrote:
Why not just use a close ROM + LDR to get SA access and then extract the LDR from the drive itself? That's what I usually do.


I'm interested in this thing ... what steps need to make this operation?

Transfer the adaptives from your native ROM to a donor ROM. Use the patched donor ROM and donor loader to gain SA access, etc ...

Re: Loader Needed for Hubble LT

December 3rd, 2016, 19:12

I'll look for it on Monday. I should have it.

Re: Loader Needed for Hubble LT

December 4th, 2016, 9:57

jackass25 wrote:
Why not just use a close ROM + LDR to get SA access and then extract the LDR from the drive itself? That's what I usually do.


I'm interested in this thing ... what steps need to make this operation? I have Wdmarvel and MRTpro ..

Thank you in advance.


Pretty much as Spildit already explained. Just be sure to backup the patient ROM. Then just pick out the closest resources you have for the family. Write the ROM from those resources to the PCB, then upload the matching LDR for it. You might have to block SA access in the borrowed ROM too, just to prevent it getting stuck busy if it tries to load any overlays (usually it won't anyway). Then upload dir from the HDD's own SA into RAM and copy out all modules. In some cases this may give you some issues, especially if the dir module is stored in a different location. You can change the dir location in ROM, or you might have to just read tracks and then do a search for modules in the saved tracks. Once you get the ldr from it's own SA, you can then program back the original ROM and use the newly extracted ldr.

There's also a trick I did once or twice where I just modified the version number stored in an LDR to make the PCB think it was compatible. Worked oddly enough.

Re: Loader Needed for Hubble LT

December 5th, 2016, 12:41

Here you go: https://dl.dropboxusercontent.com/u/31728104/11.rpm



>Techno mode key
>Techno mode key......................... : Ok
>
>RAM:
>HDD Info reading........................ : Ok
>Heads number............................ : 2
>Cyl Count............................... : 256
>
>Zone allocation table................... : Ok
>SA SPT.................................. : 1437
>
>ROM:
>ROM reading............................. : Ok
>ROM Data size........................... : 256 Kb
>Flash ROM dir reading................... : Ok
>Flash ROM dir reading (Ext)............. : Ok (Active)
>Modules directory address............... : 101 624
>SA regions address...................... : by default
>SA Translator loading................... : Ok
>
>ROM Modules:
>ROM version............................. : 06.2TJ
>ROM F/W version......................... : 0006002T
>Overlay F/W version..................... : 06.2UJ
>Servo F/W version....................... : NE.11
>
>Heads configuration..................... : by map
>Heads number............................ : 2
>Heads number in use..................... : 2
>Switched off heads...................... : No
>Heads map............................... : 0,1
>
>Service area:
>Permanent overlay....................... : Loaded
>SA dir reading (ID)..................... : Ok
>SA Access............................... : Copy 0,Copy 1
>

Re: Loader Needed for Hubble LT

December 5th, 2016, 12:43

Thank you Nick!
Post a reply