SAMSUNG HDD "Conceptual Case"

[shahij]

I've received a case

In LABEL: HD502HJ - 500GB

In Shape/Size/Weight/PCB - I believe it's 750GB or 1TB HDD which was actually refurbished and resold with new label of 500GB Model.

I believe it's possible to identify if it's 750GB/1TB model actually. Later issue - I can't get the idea so far - identifying the exact model.


Problem of the HDD:
===============
As I identified, it's a PCB + ROM issue.
Unfortunately, the ROM can't be read by my external programmer MINIPRO - it produces some error "at this moment, I can't remember the error, can be updated later."

Fact is - this one is a REFURBISHED HDD.


Question:
===============
Do you have any IDEA how to DEPOP head on SAMSUNG HDD? Where to get the specific info regarding head map in ROM/Module

At this moment, my tendency is preparing a DONOR HDD with similar config for the problematic HDD.

[data-medics]

I guess my question would be: If you can't even read the ROM with your equipment, how do you expect to modify and write it back to the PCB?

If you could at least post some more info about the drive, or post the ROM code would help I suppose.

Or is this case just "Conceptual" and not a real case??? I'm confused.

[shahij]

It's a real case. I was making an IDEA in mind with a plan that the DONOR overlay will be copied to PATIENT so that the DONOR ROM can match and proceed.

With this idea, I am thinking the need to prepare a DONOR first - THATS WHAT I MEANT CONCEPTUAL

At this moment, ROM reading is not possible, I'll try to read this one with other PROGRAMMER if this one be really READ. Regarding the ROM chip - it's well supported by the Programmer I use, but the PATIENT ROM is not reading for some reason.


REGARDING THE HDD:
LABEL: HD502HJ (500GB)
PCB: BF41-00353A (Indicates 750G/1TB)

[shahij]

Here is the LOG it produces with DONOR PCB + ORIGINAL ROM

Code:

Apple Macpro RAID connect phy calibration
PLL locked!
ChipRev = 63B0
*PA VID=0000 PN=0004 Rev=0002- 785x Found
*PA VID=0000 PN=0004 Rev=0002- 785x Found
U
S_0
RV En Sensor Circuit
En Shock Sensor Circuit
SO_1
SpinStartUp: mcSpinRPM = 0

RPM at Handoff: 585
Temp : 24 degC
<MDL_SVO_SpinCheckReady_1> mfAccelRty = 1    RPM = 46
SpinStartUp: mcSpinRPM = 519
RPM at Handoff: 742
Temp : 24 degC
<MDL_SVO_SpinCheckReady_1> mfAccelRty = 2    RPM = 154
SpinStartUp: mcSpinRPM = 667
RPM at Handoff: 836
Temp : 24 degC
<MDL_SVO_SpinCheckReady_1> mfAccelRty = 3    RPM = 175
SpinStartUp: mcSpinRPM = 724
RPM at Handoff: 869
<MDL_SVO_SpinCheckReady_2> SpinAccelFail    RPM = 869
SO_2 C=0,A=3,S=1,RPM=869
RPM at Handoff: 842
Temp : 24 degC
<MDL_SVO_SpinCheckReady_1> mfAccelRty = 1    RPM = 176
RPM at Handoff: 715
Temp : 24 degC
<MDL_SVO_SpinCheckReady_1> mfAccelRty = 2    RPM = 218
SpinStartUp: mcSpinRPM = 611
RPM at Handoff: 792
Temp : 24 degC
<MDL_SVO_SpinCheckReady_1> mfAccelRty = 3    RPM = 204
SpinStartUp: mcSpinRPM = 673
RPM at Handoff: 839
<MDL_SVO_SpinCheckReady_2> SpinAccelFail    RPM = 839
SO_2 C=0,A=3,S=2,RPM=839
RPM at Handoff: 813
Temp : 24 degC
<MDL_SVO_SpinCheckReady_1> mfAccelRty = 1    RPM = 203
SpinStartUp: mcSpinRPM = 707
RPM at Handoff: 858
Temp : 24 degC
<MDL_SVO_SpinCheckReady_1> mfAccelRty = 2    RPM = 211
RPM at Handoff: 729
Temp : 24 degC
<MDL_SVO_SpinCheckReady_1> mfAccelRty = 3    RPM = 181
RPM at Handoff: 578
<MDL_SVO_SpinCheckReady_2> SpinAccelFail    RPM = 578
SO_2 C=0,A=3,S=3,RPM=578
SO_3 R Sp Err
SpinUp Fail
VOP!
PK_4   C:     0 H:0
LED 1703
LED 1703

with DONOR PCB + ROM = it produces exactly same message on DONOR HDA

[fzabkar]

FWIW, if you examine the SpinPoint F3 AMD SB850 firmware update, you will find massive differences in the ROM code for the HD103SJ and HD502HJ.

Samsung F3 and F3EG Firmware Patch/Update:
http://knowledge.seagate.com/articles/e ... Q/223631en

[shahij]

By the way, the DONOR PCB I used from HD103SJ (1TB), the PCB + Original ROM was tested on 1TB DONOR HDD.

Yes, HD502HJ - is 1 platter/2 heads

But the HDD I received, according to weight/shape/PCB - it must be a 2 Platter 3/4 heads

[fzabkar]

Is this your situation?

donor PCB + donor ROM + donor HDA -> SpinUp OK
donor PCB + patient ROM + patient HDA -> SpinUp Fail
donor PCB + patient ROM + donor HDA -> SpinUp Fail

If you return the donor ROM to the donor PCB, does the donor HDA still spin up?

What was the failure mode of the patient PCB? Any terminal log?

[shahij]

donor PCB + donor ROM + donor HDA -> SpinUp OK - YES (DONOR IS 1TB HD103SJ)
donor PCB + patient ROM + patient HDA -> SpinUp Fail - YES, SpinUp fails
donor PCB + patient ROM + donor HDA -> SpinUp Fail[/list] - YES, SpinUp fails

If you return the donor ROM to the donor PCB, does the donor HDA still spin up - Can update this one tomorrow.

What was the failure mode of the patient PCB? Any terminal log?
The Patient PCB was received DEAD.

[fzabkar]

Measure the voltages at the coils on the patient PCB. You should be able to do this even in the absence of a ROM.

http://www.users.on.net/~fzabkar/HDD/HD103SJ_regs.jpg

If the Vcore or Vio voltages are missing, then the motor controller would be a likely suspect. If the motor controller failed, then it could be that the motor has a bad winding. A bad winding could damage a donor PCB.

I would measure the resistance between each pair of motor terminals.

If one winding is bad, then there may be a way to increase the motor current to compensate, but I would try this on the donor HDD.

[HddDonorMarket]

I have same issue.
This drive for my training. Not client case.
HM641JI
Pcb BF41 00306A
PCB died. Some chips burned.

I removed bios chip and soldered to working donor PCB.
Terminal log :
Apple Macpro RAID connect phy calibrationPLL locked!ChipRev = 63B0
Drive doesn't spin.
I tried another drive with same pcb. Same , only ChipRev = value different. And doesn't spin.
Again soldered original rom to donor. Working normal. It's about patient drives ROM

I couldn't find anything with Google.

[fzabkar]

Can you show us the markings on each of your patient and donor MCUs?

http://www.hddoracle.com/viewtopic.php?f=59&t=205

[HddDonorMarket]

Left donor right patient

Different MCU label
Could be not matching PCB?

[pcimage]

I knew I’d seen that message before!

Some trawling of this forum.....

https://forum.hddguru.com/viewtopic.php ... LL#p153812

[fzabkar]

The MCUs appear to be matched (both "B0").

[ddrecovery]

I knew I’d seen that message before!

Some trawling of this forum.....

https://forum.hddguru.com/viewtopic.php ... LL#p153812

Looks like some of us cannot access this exclusive part of the forum.

[fzabkar]

I knew I’d seen that message before! :-)

Some trawling of this forum.....

https://forum.hddguru.com/viewtopic.php ... LL#p153812

Looks like some of us cannot access this exclusive part of the forum.

That's the [cryptic] message you get when you try to access any deleted post.

[ddrecovery]

Giod to know. I still think they are out to get me