I post the original rom file, and the one after the "repair"


I think the repaired one which WDR calls NewFlash.bin is damaged.
The original maybe is good (the original rom is 2512.bin)

Someone can tell me if NewFlash.bin is really damaged as i think and why does get damaged when i clic on repair?
WDR should fix it, maybe version 3.0 is not good...

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

I understand that MOD 107 is irrelevant, and I understand that the actual problem is a head fault. I'm just indulging the OP and trying to put his own mind at rest.

_________________
A backup a day keeps DR away.

I did a remote diagnosis with A-FF Repair Station, this is the result:


WDR report that the only SA damaged modules are 6F, and 107 and both don't affect the rom repair if i understood right.
Anyway i can't fix them!!

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

ok, i end here.
Give me a information please...
If i use WDR 6.0 and disable head 1 on ram, do you think i will be able to image drive on good heads in normal speed?

If i do selfscan i will lose data?

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

I need a confirm from a PRO if head depop without ram will make loose all data or if is safe.
If depop doesn't destroy data i will try imaging the drive...

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

I can confirm if you disable one head and managed to read the data on the other 5 good heads, the data on the disabled head is still intact.
BUT if the head that is disabled is somewhat damaged in it's "flying capability" then it WILL destroy the surface (data) of that platter.
So it's a high risk for DIY.

_________________
Rescue IT Datarecovery service Sweden
Rescue IT Dataräddning Göteborg AB
http://www.rescue-it.se

Before to depop head 1, explain me what should I do to reactivate it later?
To turn on it again should i press reset translator and then recalculate translator with p-list?

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

I downloaded the resource dump linked by "fzabkar" and i took from it module 32 and i wrote into my drive, then i did fast p-list translator recalculation.
Now the drive is faster in mhdd scan and is detect faster also in bios, but i still have the stop issue after few seconds (anywhere in the drive)
I did a test also with option "logical scan" in WDR.

As you can see i get all "?" after few good sectors.
Example from LBA 0:

I get all "?" from lba 326.992

----------------------------------------------

Another example from LBA 500.000.000:

I get all "?" from lba 500.509.184

If i begin scan since lba 500.509.000, i get all "?" from lba 500.509.432


----------------------------------------------

One more example, from lba 1.000.000.000:

I get all "?" from lba 1.001.439.944

If i begin scan since lba 1.001.430.000, i get all "?" from lba 1.002.494.240


This means that they are not really bad sectors, maybe still translator issue?

I guess the module 32 is clean now, but something more should be fix, any idea?

P.S.
I decided to not do head depop.

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

I don't know why you did this, but did you match the MOD version?

_________________
A backup a day keeps DR away.

The drive has at least one bad head

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

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

I notice that in the SMART report the Current Pending Sectors attribute has a worst normalised value of 1. This suggests that at one time there were several thousand pending sectors but these have since been returned to service. Sounds like an intermittent fault to me ...

_________________
A backup a day keeps DR away.

Yes MOD version is the same

My original mod 32:


mod 32 resource dump:

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

Could it be a smart issue?
It's possible to disable smart in WDR 3.0?

This was the original smart status:


Smart status now:

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

SMART isn't the reason for your problems. SMART is merely reporting the problems.

AISI, the Raw Read Error Rate, Seek Error Rate, and Current Pending Sectors were clues that the drive had a head fault. Your defect list pointed to head 4, but subsequent testing hinted at head 1.

Your latest SMART results are typical of a new drive which has not yet recorded sufficient activity in order for the SMART data to be statistically significant. That's why you see a lot of "253" values.

_________________
A backup a day keeps DR away.

If i decide to do head depop, should i do it on head 1 or head 4?
Or both?

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

I tried to copy files and folder in dos with NTFS4DOS utility, but i don't understand why it copies only the first file in the directory.
This utility it ignores all other files in the directory when i give the copy command (it ignores also all sub-directorys).
Maybe the problem is due to the issue on drive...

Examples of commands which i tried:
1. "copy e:\foto d:foto"
2. "cd e:\foto"
"copy *.* d:\foto"

Both this commands copy only 1 file of the directory (the first one)

P.S.
With NTFS4DOS i'm able to see all files in the directory (with DIR command), but not to copy all of them!!

Do you know some other dos program which are able to copy files and folders for NTFS sourse partition?

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

That's expected, because they are the wrong commands for the result that you are requesting. You need to investigate the DOS xcopy command and its options (e.g. /s /e) in order to copy sub-directories. I haven't used NTFS4DOS - any issues with that are a different problem. You need to try the correct DOS command (i.e. xcopy) first

I tried xcopy, doesn't detect ntfs partition!
In NTFS4DOS option /s /e are not able

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

There are other DOS NTFS readers, but I don't know which ones you've already tried... As I explained, when you find one which works for you and which mounts the NTFS partition as a drive letter, you need to understand the limitations of the DOS copy command. Also I didn't see you explain why you are trying to do this from DOS.

Because cloning the drive is not an option due to the very low speed (i don't even have those expensive tools for cloning as DDI).
I need to recover only pics folder (which is about 100GB), in dos i can access to the folder directory and i can see all files are inside, but i hadn't luck on copying those until now.

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