Hi, i need LDR. anyone help?

ST9500325AS
fw: 0002BSM1

Thanks.

Still looking for this.

I don't have loader for this but i have ROM, SA mods and tracks of this:

ST9500325AS
fw: 0002BSM1
s/n: 5VExxxxx
Family: Wyatt

if you know how to build a loader from tracks i can send you fw resources of this.
Which tools do you have for hdd fw working?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

When i did backup fw resource of this drive i forgot to generate the loader, but with MRT it's possible to generate loader file from tracks.
I don't know if PC3000 generates loaders from tracks, with MRT it's possible to generate it via tracks or via terminal or via ATA.
I don't have this drive anymore because i gave back to customer, so the only way i can generate the loader for you is via tracks, hope it will work with your PC3000.

FW resource included LDR file, made with MRT, hope it will work for PC3000:

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Some pics to show you how i created LDR by track in MRT...

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

thank you Michael. i tried that Ldr but not working on PC3K.

i'm sorry for that
probably it's because MRT ldr is not compatible with pc3000, or because MRT ldr is just garbage (mrt is full of bug).

Inside rar file that i sent to you there are mods, rom and tracks generated in MRT (which are perfectly compatible with PC3000), you should ask into PC3000 forum if someone knows how to build a loader without having the drive physically but by using just firmware resource.

Or just ask directly the loader in PC3000 forum...

P.S.
Rom version of loader should match with your patient drive rom or it might not work.

Good luck!

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

Try this...

_________________
PC Image Data Recovery
http://www.pcimage.co.uk

New!! HDD-PCB.COM for all your PCB and donor HDD requirements!

ISTM that the LOD file is similar in structure to those that come with Seagate's F3 firmware updates. These appear to consist of headers plus various modules.

The layout in this particular case is as follows:


ISTM that you could manually generate a loader, if you could understand the structure of the headers.

_________________
A backup a day keeps DR away.

I think I've worked out how to construct the headers. The header contents are actually embedded within each of the 4 modules. Only minor changes are required.

The Python script at the following thread provides a little insight into the structure:

http://www.hddoracle.com/viewtopic.php? ... 219&p=5825

In fact it is a simple matter to extract a complete loader from Seagate's firmware update packages.

_________________
A backup a day keeps DR away.

Very interesting Frank
Unfortunately i can't find any firmware update for Momentus 5400.6 drives on Seagate web site

How should be used Python script?

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

The Python script doesn't generate or extract the loader per se. I only referred to it because its coding illuminated the header structure. If you need a loader for the 5400.6 drive, I can try to create one for you from the modules and tracks.

_________________
A backup a day keeps DR away.

thank you all, case solved

but i interested now, how can create loader from the modules and tracks.

hyuce, you have solved with pcimage LDR ?
It's nice reading when people have solved an issue

@fzabkar
I don't need a loader for this drive, i was just tring to help hyuce and also to understand how to build LDR manually.

Would be interesting to know how you would build it if you don't have firmware update resource as for this 5400.6 drive

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

The loader consists of 4 firmware modules, namely 1D, 1E, and two modules on track 41.

The first module is located at offset 0x200 and is preceded by a header of size 0x40 bytes.


The header begins with a magic number, "71 78 37 07".

Offset 0x1D0 contains the size of the data section, namely 0x30000.

Offset 0x1E4 is the size of the data section plus header, namely 0x30040.

Offset 0x1FE is the checksum word for the header. It is calculated in such a way that the 16-bit little-endian sum, including the checksum word, is 0x0000.

Offset 0x1CC is the module ID, namely 0x0004, which is reflected in the first word of the data section.

Offset 0x1CE is the data type, 0x4A. I believe this denotes an SA overlay.

Offsets 0x1D8 - 0x1DF are the time/date stamp. The date is 2009/10/06.

The header "template" can be found by searching for the magic number within the firmware module:


Certain changes need to be made to this template, as explained above.

Preceding each module and its 0x40 byte header is another 0x40 byte header with its own 0x180 byte data section:


This first header has a type of 0x07 (offset 0x0E).

Offset 0x10 is the size of the data section, 0x180.

Offset 0x24 is the size of the entire loader, 0x70800.

Offset 0x3E is the checksum.

Offsets 0x40 - 0x1BF constitute the data section, which is empty.

Here is the next firmware module:


The size of the data section is 0x20000, and the module ID is 0x05.

One significant difference is in the main header. Whereas the first header contained the size of the entire loader, this header reflects the size of the firmware module plus the size of the all the header information preceding it (0x20000 + 0x200 = 0x20200).

We repeat this process two more times for the remaining modules.

_________________
A backup a day keeps DR away.

Here is an example where we extract the loader from the 0021LVM1 Lenovo firmware update for 5400.6 Momentus drives. It is included in the FWSH43 package (47MB):

http://support.lenovo.com/us/en/downloads/ds003740

The relevant LOD image is 5421LV17.lod. It contains the loader plus several additional components.

In this particular case the loader can be carved out from 0x00 to 0x707FF. The header needs to be edited to reflect the size of the loader (0x70800) rather than the size of the entire update (0xF3A00).

This is the original header:


This is the modified one:

_________________
A backup a day keeps DR away.

@michael chiklis yep, case has solved with pcimage's LDR.

@fzabkar wooow, very helpful information for us. Thank you!!

Thank you Frank, i'm studing your post and soon i will try to generate some loaders as you did.

_________________
My firmware database:
https://mega.nz/folder/O01DkBRI

you might also enjoy this...

_________________
Adatmentés - Data recovery

Tools for converting between old (LDR) and new (LOD) MRT Seagate F3 loaders:
http://www.hddoracle.com/viewtopic.php?f=147&t=1772

Tool for creating Seagate F3 loader (LOD) from system files:
http://www.hddoracle.com/viewtopic.php?t=1809

_________________
A backup a day keeps DR away.