Data recovery and disk repair questions and discussions related to old-fashioned SATA, SAS, SCSI, IDE, MFM hard drives - any type of storage device that has moving parts
July 17th, 2015, 4:09
Hi, maybe someone could help me disable PUIS on Samsung HDD? i have two of them now broken by win10

one is HD204UI, i have successfuly connected terminal to it, but it will not spin up, after i give spinupp comands. so thinking of disabling PUIS manualy via ROM.
other has same situation but is HD103SJ + in adition if i try to spin it up using terminal or anythign else MOSFET that controls -5V gets burtn, but i do not see any other damages to preamp or drivers, so am at a bit of lost.

many thank for any thoughts
- Attachments
-
- 2TB_ijungtas.rar
- 2TB hdd rom
- (185.99 KiB) Downloaded 813 times
-
- 1TB_ijungtas.rar
- 1TB hdd rom
- (162.92 KiB) Downloaded 731 times
July 17th, 2015, 5:09
sorry

solved
July 17th, 2015, 5:54
I've arrived at my own solution in the meantime. I cut the ROM out of the official F4EG update and discovered that it differs from yours in a few areas. Your ROM's checksum was also in error AFAICT.
How did you solve your problem?
July 17th, 2015, 19:10
Please tell me how you solved it. I've been dealing with this since last december when Windows 10 bricked my drive.
Please post your solution. Thank you.
July 22nd, 2015, 4:33
I don't have the capability as a new user. Can someone please send a PM to andrius to ask if he can come back and explain his solution?
EDIT: Hm, nevermind, I guess this second post unlocked the ability to send PMs.
February 28th, 2016, 17:11
See
http://www.hddoracle.com/viewtopic.php? ... 8192#p8192The PUIS flag (0xAA) is stored in the FIPS section at offset 0x3021. The checksum word at 0x37FE is also adjusted.
- Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00003000 46 49 50 53 9B 00 00 00 32 2E 30 30 30 20 20 20 FIPS›...2.000
00003010 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
00003020 FF AA FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿªÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
........
000037E0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿÿ
000037F0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF D8 EC ÿÿÿÿÿÿÿÿÿÿÿÿÿÿØì
I suspect that the actual problem may be this area:
- Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00041FF0 FF FF FF FF FF FF FF FF FF FF FF 00 01 00 C2 F1
The original ROM code looks like this:
- Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00041FF0 FF FF FF FF FF FF FF FF FF FF FF FF FF FF C2 F1
February 28th, 2016, 17:21
Hey fzabkar, thanks for sharing this.
I still have both drives stored away. But last I checked I even struggled to get anything from them with a TTL adapter. You suggested that I might have stressed the pins. If I got the drive to communicate via TTL, is this a fix I could do myself?
Powered by phpBB © phpBB Group.