It would have been cooler if you didn't have the ROM dump and you had to regent it from SA !

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

At least you didn't damaged modules/tracks at the SA level.
Did you figure out what part of the code was wrong to erite to ROM instead of platter module/track ?

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

now I know that a bad mod 47...doesn't let the heads finding the SA start and gives 4341 error with 5x2 clicks. but how come that with the old pcb I can access the donor's SA, and not its own SA?

the symptoms are almost identical.

the non-royl firmware like mine...doesn't have those copies of rom modules in SA..not that I know. so..how to regen?


I fixed that 2hours ago. I used exactly that code to fix the rom I still haven t tested the "write entire rom" function...because the programmer didn't arrived yet. The function is ready, but it have to wait. The mods can be fixed...the rom not.

Cool !
And now we know the meaning of another error code, as well as how the drive behaves with damaged adaptives on Rom.
Too bad i wasn't able to test my tools on your drive ! Lol !

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

or not.

how does a hdd dies if to many errors are detected? maybe it's killing its own firmware mod 47 preventing to detect SA. but this doesn't explain why the old pcb works on the new hdd. I couldn't explain how my mod 47 was modified even during that bogus tests. I'm trying to find some information about that 47 rom mod. it holds the zone 0, adaptives...aka SA adaptives. there are n zones for a disk.

I understand that basically contains:
- a constant TPI - track per inch - which it's a constant in SA, or harcoded inside firmware since it's zero in my mod;
- for each head Data DAC Offset; a delta for the head to jump from the servo sector to the track sector;
- MR Offset ... the distance between read - write heads on ox axis?
- Preamp DAC Offset the the distance between read - write heads on oy axis?

since this are unique to each HEAD..how come that we can do HAS? I mean, ok,,you flash the old fimware, but the rest of the mod 47 it's on the patient SA..and holds info for the rest of the disk zones N-1 also..who assigns those values? perhaps a factory test builds them?

Maybe you can learn more by investigating the self scan logs and the self scan scripts inside the drive ?

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

some errors I have on donor's Head 1 wen trying to read SA on track -1 and other + tracks:
VSC error code decoded: 0x5181 -->> DISK_DAM_ERROR
VSC error code decoded: 0x51A2 -->> DISK_ECU_UNSAFE_ERROR
VSC error code decoded: 0x53E4 -->> DISK_SERVO_ACTUATOR_AI_FATAL_ERROR

plus bad noise

Try not to kill the drive.
You can allways depop the bad head and re-use the drive or sell it on ebay.
Better yet, selfscan it !

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

as I said..it came with a big hole in the air filter..and show ugly marks from a fall down. it's a miracle that it's still spinning.

I tried the depop stuff with 3.0. but the nasty sounds were still present. undone the depop and now shows other model.

Did you copy the modules/tracks first ?
At any rate you should be able to get it to show the correct model with 3.0 !
Strange thing is the strange sound even when depoping.
You should have asked your money back from the ebay guy !

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

yes, it was the first thing i dit before started the game with it. a full bk sa+mods
went down on xp again to play with the depop. what else should i do after depoping a bad head? it shows the same size. how do i find/set the correct size for the new situation?

Super Format the drive or use the self scna should do it, with the depoped head.
Depop, run selfscan and see what happens.

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

If you have a backup of all the modules and ROM you should be able top depop the head without any issue.
3.0 On "Heads Map" remove the checkmark from "Head 1" go to "head to depop" enter "1" select "Clear Translator" press GO .

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

The you have to do the super format with p-list

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

bricked the donor's PCB

tried to do like u said...but I got some err msgs complaining about wrong lba...because the size wasn't changed. tried to lower the lba to 120gb...but there were 3lba: lba0 2 3...on the passport dir. at a moment it worked with the format..and th operation lasted for 1h. tried again to adjust the lba size (max size) and those lba1 lba o etc anyway..while doing that I got at a moment strange clicks and sounds and stopped reading the SA. tested with the old bcb and the SA was read fine. Putting back its pcb I did 2-3 flashes until I remembered that I must unplug the power. then it worked again but recognized as wdc rom. tried to upload the old sa mods. went fine but again recognized as wdc rom. then reflash...and bang..the pcb was bricked

now I'll have to wait for the rom programmer.

Ups .....
What do you mean by PCB was briked ?
If you plug PCB only to 3.0 and power PCB only and wait 30 sec. doesn't it report readyness ? If so you might be able to re-flash using 3.0.
Did you tried that ?

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

How many times did you reflash the ROM and using what ?
When you briked the drive were you using 3.0 or your app ?

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.

flashed with 3.0 ... 3 or 4 times. didn't know exactly which version of rom..because the way that app creates the backup directories. I had the old bios in the "WDC ROM..." dir..and when the donor transformed into WDC ROM (after lba changes)..the directory was automatically assigned by the app as for the old hdd. I don't remember on first flashes-es If I flashed the image from another dir. but it worked few times. I'm sure that the last bios was from the old pcb.

the pcb won't spin the motor. and it's not detected by any tool. the registers doesn't respond to any commands.



this means that the device at the end of the controller it's dead

Did you figure out how to use the terminal method ?
Might be a good time to try while you are waiting for the External ROM programmer to arrive

_________________
1Q9xrDTzTddUXeJAFRn37aqh1Yr6buDCdw - (Bitcoin Donations)
paypal.me/Spildit - (PayPal Donations)
The HDD Oracle - Platform for OPEN research on Data Recovery.