All times are UTC - 5 hours [ DST ]




Post new topic Reply to topic  [ 13 posts ] 
Author Message
 Post subject: LDR needed for st3320820A
PostPosted: November 13th, 2018, 6:33 
Offline

Joined: September 14th, 2018, 13:41
Posts: 293
Location: italy
LDR needed for st3320820A firmware 3.AAD
Thanks


Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 13th, 2018, 15:18 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
Your tool should be able to generate a loader from these resources:
http://files.hddguru.com/download/PC-3000%20Support/Firmware/Seagate/Galaxy/ST3320820A_S-6D_3.AAD_.089_.0GB.rar

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 14th, 2018, 15:49 
Offline

Joined: December 5th, 2011, 5:38
Posts: 1626
Location: Italy
MRT hasn't any function for generating LDR file from U5 drives fw resources.
Building it directly from hdd doesn't work (fake ldr).

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


Last edited by michael chiklis on November 14th, 2018, 15:53, edited 1 time in total.

Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 14th, 2018, 15:53 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
I can try to make a loader by hand, if the OP would like to give it a go.

Can you show us a "fake loader"?

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 15th, 2018, 20:53 
Offline

Joined: December 5th, 2011, 5:38
Posts: 1626
Location: Italy
fzabkar wrote:
I can try to make a loader by hand, if the OP would like to give it a go.

Can you show us a "fake loader"?


https://mega.nz/#F!O01DkBRI!MxP2J6ZNqXD ... Q!mk1gjI7I

Download ST3160215A-3.AAD-9RABW60Y.rar from that folder, you will find two LDRs, one from mrt and another from pc3000, u can compare them.
I've saved also tracks inside ST3160215A-3.AAD-9RABW60Y.rar

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


Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 15th, 2018, 21:13 
Offline

Joined: December 5th, 2011, 5:38
Posts: 1626
Location: Italy
Spildit wrote:
Can't you simply load by SDLD the required "tracks" from a PC-3000 dump using MRT ?

Like for example using SeDiv you do SDLD to the drives the relevant portion of firmware code on tracks ...


Not possible, it's possible only to load LDR (only from pc3000 database because those one created with mrt won't work) and buffer.
Attachment:
Load LDR in MRT U5.jpg
Load LDR in MRT U5.jpg [ 65.21 KiB | Viewed 10429 times ]
Attachment:
Write buffer MRT U5.jpg
Write buffer MRT U5.jpg [ 207.24 KiB | Viewed 10429 times ]

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


Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 16th, 2018, 8:11 
Offline

Joined: December 5th, 2011, 5:38
Posts: 1626
Location: Italy
Sorry, i thought mega folder could be shared publicly, but now i see it's not like that.
Ok, i attached here the fw resource
Attachment:
ST3160215A-3.AAD-9RABW60Y.rar [2.17 MiB]
Downloaded 348 times

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


Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 16th, 2018, 16:51 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
PC3K loaders are compressed whereas MRT's are not. It seems very odd that MRT can recognise and decompress a PC3K loader, yet cannot make use of its own.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 16th, 2018, 23:00 
Offline

Joined: August 7th, 2015, 5:48
Posts: 44
Location: New York, USA
fzabkar wrote:
PC3K loaders are compressed whereas MRT's are not. It seems very odd that MRT can recognise and decompress a PC3K loader, yet cannot make use of its own.

As i know, loaders backup by PC3K/MRT in data base are compressed, but when back up as file, both are uncompressed. MRT can recognise and decompress PC3K loader, however not the other way around.

I do not know why it can't be used here regarding a u5 drive, I do not have any in hand at moment otherwise i can try and give you more information by testing both PC3K&MRT. Personally experience this can be used so far if it is a f3 drive.


Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 17th, 2018, 15:34 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
IIUC, a "classic" loader (LDR) consists of an "Mrt" header followed by several firmware components, each of which is preceded by a header of the form ...

    ID (byte) eg 10 (ROM), 11 (App code), 12 (Cert), etc
    size
    PCHS (cyl / head / sector)

This would suggest that the data recovery software interprets the LDR file, extracts the individual firmware components, and then uploads them to the drive, one by one.

OTOH, an F3 loader (LOD) appears to be uploaded to the drive as a complete LOD file, and it is the drive's firmware which then extracts each component rather than the tool.

Could it be that PC3K's classic LDR is decompressed and executed by the drive?? Or could it be that MRT expects all LDR files to be compressed, in which case its own uncompressed version would be detected as a fake?

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 17th, 2018, 19:19 
Offline
User avatar

Joined: September 8th, 2009, 18:21
Posts: 15461
Location: Australia
Spildit wrote:
F3 loaders are like "overlay" that you send to the drive, for example like Module 11 on WD. Overlay on F3 arch can be send by ATA download microcode standard command.

I was in fact wondering whether there exists a Seagate format for a classic loader which can be sent by the ATA Download Microcode command (92h). I did attempt to parse the payload in an official Seagate Galaxy firmware update. It appears to have a special format that is totally different to Mrt's loader. However, it is not clear whether Seagate's update utility strips the firmware components from the LDR file and uploads them separately via a VSC, or whether the drive itself handles everything.

_________________
A backup a day keeps DR away.


Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 19th, 2018, 17:15 
Offline

Joined: December 6th, 2012, 8:49
Posts: 290
Location: espaƱa
MRT has virtually no support for seagate with ST 10 architecture.

It has the module, but few possibilities (similar to the samsung module).


Top
 Profile  
 
 Post subject: Re: LDR needed for st3320820A
PostPosted: November 19th, 2018, 21:00 
Offline

Joined: August 7th, 2015, 5:48
Posts: 44
Location: New York, USA
Spildit wrote:
fzabkar wrote:
Could it be that PC3K's classic LDR is decompressed and executed by the drive??


I'm sure this is not the case.

F3 loaders are like "overlay" that you send to the drive, for example like Module 11 on WD. Overlay on F3 arch can be send by ATA download microcode standard command. Some tools do have loaders "encrypted" for them. SeDiv do use this method. This is to prevent files for SeDiv to be used with other tools. SeDiv decrypts the files and send them to the drive.

On ST-10 / classic the drive have no way to decompress the loader in PC3K format (or MRT). Also you are not sending by ATA, you are SDLD (Seagate Protocol) by terminal the "components" so the tool itself have to decode the loader file and send individual components to the drive. You can also chose what components to send. You might want for example send only ATA + APP and don't send CERT, etc ... The drive doesn't understand "loader" and you are not sending it by ATA. Those loaders do have to be "decoded" by the firmware tool and when you use the SDLD protocol by terminal you need to send the code directly.

This is of course a MRT bug. It can decode the PC3K loader but can't decode it's own loader.



That make sense. :)


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 13 posts ] 

All times are UTC - 5 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 58 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group