Strange HD253GJ

Don't Lose Your Data Forever!

DIY data recovery has risks. You could lose your data forever! Don't want to risk it? Talk to a professional now.

pclab

Moderator
Hi guys

I have a strange case here with this Samsung.
The log is this:
*PA VID=0000 PN=0004 Rev=0001- 785x Found
*PA VID=0000 PN=0004 Rev=0001- 785x Found
ChipRev = 63B0
U
S_0
RV En Sensor Circuit
En Shock Sensor Circuit
SO_1
SpinStartUp: mcSpinRPM = 692
RPM at Handoff: 868
Temp : 25 degC
SpinOk
mS1 00000003
SK C:133077 H:0
POK
POK
Boot Sector Error! Take a default.
Loaded FIT ( 0: 0: 1)
CalibTable Loaded. Rev:0x14
Selective MARC NX Loaded
ResoTable Loaded. Rev:0x01
Ovly loaded to 0x0001CD00
Ovly loaded to 0x1005B800
FdtTable Loaded. Rev:0x02
| 19 | RLIST | 2 | 0 | 256 | 1140 |
Reading Serial Num Pass
Up MC
TgtCyl: 2032
Hd: 0 Zn: 0 Avg.:- 135
TgtCyl: 264349
Hd: 0 Zn: 1 Avg.: 154

SVCAL(0080,0000)-->PASS
rb(e1140 20 0 836 13)
rb(e1140 20 0 836 13)
rb(e1140 20 0 836 13)
W-MC e(00001140) (20: 0: 836:0x09:0x0093)
>>Insitu: MC rd fail
| 167 | DRM | 33 | 0 | 0 | 1140 |
rb(e1140 33 0 0 159)
rb(e1140 33 0 0 159)
rb(e1140 33 0 0 159)
W-MC e(00001140) (33: 0: 0:0x0B:0x00A7)
| 55 | SMRT | 20 | 0 | 4 | 1140 |
rb(e1140 20 0 4 12)
rb(e1140 20 0 4 12)
rb(e1140 20 0 4 12)
W-MC e(00001140) (20: 0: 4:0x09:0x0037)
rb(e1140 20 0 4 12)
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 1005BDA1]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():10034A2D L0 0000EBB7]
[DEBUG HALT @MDL_RSRC_BufferAlloc():00000000 L0 00000000]

It keeps always busy. It spins OK, no bad noises.
I tried to swap PCB, but same thing, until I put the original one and I started to work.
I did a FW backup, all ok. Accessed data )I saw the folder structure, but it was giving some errors and needed to do a power off/on.After that it went to the same log.
I then tried a hotswap (followed the rules to do it), but after standby and calibration it clicks.
I found that the patient have 1 head (on DE it showed only 1 head) and on the donor (even after writing ROM into donor PCB) it keeps saying it have 2 heads.
Tried to do RAM headmap, start with changed headmap and nothing works....

Any ideas??
 

Jared

Administrator
Staff member
DigitalVeriKurtarma":pfvxfnyp said:
[post]14888[/post] To those of you who have access to the data recovery secrets section

That's not you then is it.
 

Jared

Administrator
Staff member
Re-read the part I highlighted in red. It says, THOSE WHO HAVE ACCESS TO THE SECRETS SECTION. That's not you.

Wouldn't be very well kept secrets if anyone could view it publically.
 
Top