I get the following error when I try to recover F3 translator...

[osity]

Customer's budget doesnt allow for heads swap.

Procedure stopped after about 4 days and gave the following output:

"Fork" searching: 383904746 - 976773167
Verify sectors ext error Device error detected "UNC"
PRd: Err Rd Ph Sect D4B9:2:58A(1)! Tech state 0x72, 0x03110081
Surface scanning error (UNC) : PRd: Err Rd Ph Sect D4B9:2:58A(1)! Tech state 0x72, 0x03110081
LBA : 383904786
"Fork" searching: 383904787 - 976773167
Verify sectors ext error Device error detected "UNC"
Translation "fork" direction detection ambiguity!
Correct it manually!
LBA : 384086272

I restarted drive and it still wont access end parts.
Not sure what do next with this.

[300ddr]

The manual rebuild procedure isn't too hard once you understand it. It can be days-weeks faster than waiting for the auto-rebuild. But, if the sectors are intentionally zeros in the area where the reading stops, auto-rebuild may be the only way. We have one of these going right now and it's been 4 days so far. For some reason on this drive it takes like 10 minutes for every translator regeneration to finish (even though heads all work and read quickly). And you do need Terminal connected.

[300ddr]

Another thing: confirm in DE that the "used sectors" on the MFT include LBA past where it's stopped reading. If they only have a small amount of data, you may be able to recover 100% without fixing translator.

[osity]

I have ordered a PCB for this as I was told by TS that a PCB may be related. Should be here in a couple days.
It's interesting that terminal is needed for this ......

[300ddr]

I was told by TS that a PCB may be related

That would be quite a surprise. Please report back once you find out.

[GuideRecovery]

exactly in case of weak or bad heads, you won't be able to recovery it automatically.