1er164-302 Seagate drive made in Tk frm 2016 with empty rom.

[SWM]

RAP, SAP files are read from 0x03-System disc volume.
And file 32A is read from 0x0A-Serial Flash Volume.

[Ytrezq]

From the ROM that the CA reads, read the files from the patient:
F3 T>r1,3
receive a file to a PC using the Y-modem protocol
F3 T>r3F,3
receive a file to a PC using the Y-modem protocol
F3 T>r208,3
receive a file to a PC using the Y-modem protocol

Character case is IMPORTANT! Everything is done carefully!
If the terminal is not locked...

https://www.intohard.com/forum.php?mod=viewthread&tid=271110

0x0001 RAP (Read/write Adaptive Parameters) super file
0x003F SAP(Servo Adaptive Parameters) file
0x0208 CAP(Controller Adaptive Parameters) file

Is this an SA copy of the ROM, or is it the actual ROM?

******************************************************************************************
Diag File IDs
******************************************************************************************
0x032A Entire contents of serial flash

I don t know what you mean. As I said I don t have the serial connector, and I m not even sure the com port would reply to anything given the state of the rom.

[pepe]

SWM,
those files are not present on 1ER, nor 1CH and neither on 9YN.
Nor does any F3 drive load RAP, CAP and SAP from the surface. Period. (c) blackst
Don't talk BS please.

Drive can't access SA without native SAP, so it is essential to have its orig version in ROM.

pepe

[SWM]

For those who read the topic diagonally:

Nevertheless, check the native ROM for reading. Possibly a 1.8V chip.
If the native ROM is lost, read the system files RAP, SAP, CAP from SA and put them into the donor's ROM.
These are test modules, but can give access to the user zone.
If you pray...
ps Don't forget to save the donor ROM image before changing...

I never said that the disk uses these modules in normal work.
At the pharaoh, I put a RAP from the module in the ROM. Access to user-area was, albeit bad.
My last post was a response for Frank. 32A reads from flash.

This is for Pepe, an excerpt from the first post of the topic:

I found an hard disk with an almost identical serial number (first 5 chars match along logo placement). Drive does intialialize and seems to pass reading the System Area with the other pcb (no click of death) but all sectors read as corrupt (at least the 150 first Mb).

[pepe]

If the native ROM is lost, read the system files RAP, SAP, CAP from SA and put them into the donor's ROM.

This you can't do simply because SAP is required to access the SA. Catch-22.
I went through this and it required pretty nice amount of research and had to understand quite some SAP parameters and their use, after which i was able to get access to SA.

Of course, drive doesn't click with donor rom in most cases, if heads are compatible, and drive sounds to be calibrating but you won't get it pick up anything from the SA, simply because it is unable to find it. The OP has no tools and expertise to tell what's happening when he tries to read the patient with the donor pcb, but i can tell it is still in bootfw mode and aborting all reading commands. If he could attach a serial adapter we could see something like this:

Code:

Boot 0x40M
Spin Up
RECOV Servo Op=0100 Resp=0005
TCC-0028[0x000042F9][0x000042F9]ZZZZMMMMMMMMMMMMMMMZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZZMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMMddddddWWWMMMMMM
RECOV Servo Op=0155 Resp=0005S
RECOV Servo Op=0055 Resp=0005xxxxZWZWZWZWZWZWZWZW


To summarize: It won't ever be successful to read the adaptives from the SA because of the catch22 and the fact that there is no such sysfiles on 1ER (and other) Grenadas.

pepe

[Ytrezq]

If the native ROM is lost, read the system files RAP, SAP, CAP from SA and put them into the donor's ROM.

This you can't do simply because SAP is required to access the SA. Catch-22.
I went through this and it required pretty nice amount of research and had to understand quite some SAP parameters and their use, after which i was able to get access to SA.

Of course, drive doesn't click with donor rom in most cases, if heads are compatible, and drive sounds to be calibrating but you won't get it pick up anything from the SA, simply because it is unable to find it. The OP has no tools and expertise to tell what's happening when he tries to read the patient with the donor pcb, but i can tell it is still in bootfw mode and aborting all reading commands. If he could attach a serial adapter we could see something like this:

Disagree. On start I can hear the head to read the SA, then park/disangage a few second after if left idle (drive just plugged without a computer connected). This is no different from when the drive was still working (I remember doing it when I bought it several years ago). It isn t trying to read any sectors repeatedly. Doesn t means what is read is true in reality.
I ll post the audio in 8 days when I can do it again as well as the picture of donors and original.

Last edited by Ytrezq on September 1st, 2023, 19:28, edited 2 times in total.

[fzabkar]

Post a terminal report. That may give us something tangible to work with.

[Ytrezq]

I do have a native db9 plug. If you know where to get a connector for less than 5€ in 8 days, then I can do it.
Students don t earn a lot and I need to keep 8 to 10K€ for the data recovery. Though as I said, I think anyway a terminal report won t be possible with the original rom.

If someone sends 1 here, I agree to mail it back.

[pepe]

we are after the report made with patient hda + donor pcb (rom) of course, as that's where our oppinions do not meet.

you don't need to keep much for data recovery, nobody will do this at the moment i think.
Don't attempt wiring the db9 connector to this pcb, voltage levels are VERY different (usually -12V-12V vs 0-1.8 ).


pepe

[Ytrezq]

we are after the report made with patient hda + donor pcb (rom) of course, as that's where our oppinions do not meet.

you don't need to keep much for data recovery, nobody will do this at the moment i think.


pepe

Until I find a ediscovery service that can recover the rom from the rom? I don t want to solder so need the connector.

[SWM]

Something like this:
https://www.icstation.com/converter-uar ... 15988.html

[pepe]

I don t want to solder so need the connector.

i just said that because you were talking about the db9.
the one SWM linked does the job.

pepe

[Ytrezq]

Something like this:
https://www.icstation.com/converter-uar ... 15988.html

I don t have a problem with serial but I need the 4pin plug. https://forum.hddguru.com/viewtopic.php?f=13&t=10141

[Ytrezq]

That 1 would take too long to arrive https://fr.aliexpress.com/item/33056755 ... pt=glo2fra

[pepe]

buy 2mm pitch socket header at local electronics shop
like this one:
https://eu.mouser.com/ProductDetail/Har ... LLIQ%3D%3D
or this one:
https://www.ebay.co.uk/itm/5Pcs-2mm-Pit ... 0842981468

pepe

[Ytrezq]

buy 2mm pitch socket header at local electronics shop
like this one:
https://eu.mouser.com/ProductDetail/Har ... LLIQ%3D%3D
or this one:
https://www.ebay.co.uk/itm/5Pcs-2mm-Pit ... 0842981468

pepe

That won t allow to plug to db9 port or Usb.

[pepe]

the thing SWM linked and the things i linked allow you to hook it up to an usb port. I feel like we can't help more, sorry.

pepe

[Ytrezq]

Ok I got the equipment from China. But I got a strange bad surprise.

Initially, I had https://ytrezq.sdfeu.org/audio/Recording_25.m4a
But now I have https://ytrezq.sdfeu.org/audio/Recording_26.m4a.

I ve no idea what could had caused this. I never opened the drive and took extra care to prevent shocks. The donor drive which was next to the damaged drive still works when reassembled.

[Ytrezq]

Post a terminal report. That may give us something tangible to work with.

Even if I don t do it myself because it has to be done by a lab, what to do to go back to the situation where a terminal report is useful?

[fzabkar]

A terminal report will tell us something about the ROM. You don't need to install the PCB on the drive to do this.