Samsung F1 firmware

[fzabkar]

Hi ! I didn't check the resources but for drives prior to Trinity (classic samsung) overlay module is OVERLAY and not MOVLY001.

I examined balgator's FIT module but it only has references to MOVLY001, BOVLY001 and MOVLY009. There is no OVERLAY module. :?

Looking forward to the terminal log ...

[helpless]

I think that it will be hard to fix without a proper firmware tool that works with Samsung.

SHT will do the job but costs $200 USD.

Sorry, i don't see any cheaper alternative unless somehow you can find out a way to match ROM with overlay by flashing something to the drive with the vendor tools,

But then again, this would be very easy to fix with something like full version of SHT.

A tool alone will not fix it, he/she will need to download the right microcode to the the hdd.
I doubt if there is any info on the original rom/fw version in the drive. If the update hasn't changed anything on the platters, you have to buy/find at least the correct main code compatible with your fw.

[fzabkar]

My analysis at Tom's Hardware confirms that only the ROM is affected by the update.

FWIW, I found this in the MASS module:

Code:

Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F

00000000  41 4D 53 53 20 20 20 20 A8 00 01 00 00 00 00 00  AMSS    ¨.......
00000010  31 36 39 37 31 33 53 49 31 39 35 38 35 34 00 00  169713SI195854..
00000020  00 00 00 00 02 00 52 54 4E 49 54 49 20 59 00 20  ......RTNITI Y.
00000030  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000040  00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
00000050  41 31 32 43 79 38 42 72 64 2E 31 31 00 00 00 00  A12Cy8Brd.11....

Once again it points to "1AC28yrB.d11", Trinity.

[Spildit]

I think that it will be hard to fix without a proper firmware tool that works with Samsung.

SHT will do the job but costs $200 USD.

Sorry, i don't see any cheaper alternative unless somehow you can find out a way to match ROM with overlay by flashing something to the drive with the vendor tools,

But then again, this would be very easy to fix with something like full version of SHT.

A tool alone will not fix it, he/she will need to download the right microcode to the the hdd.
I doubt if there is any info on the original rom/fw version in the drive. If the update hasn't changed anything on the platters, you have to buy/find at least the correct main code compatible with your fw.

Option 1 - Get SHT + another drive with same F/W version on the label that your drive have. Read ROM from donor, write to patient. Done. As long as F/W version on both labels are the same + update only changed ROM, writting native correct ROM to the drive will fix it.

Option 2 - Get SHT + another compatible drive of the same full model. Even if F/W version doesn't match do hot swap and write Overlay from donor to patient. Write donor ROM to patient ROM/PCB. Done.

[fzabkar]

Option 1 - The OP has stated that there is no firmware version on the drive's label.

Option 2 - I have checked the drive's resources. I cannot find an overlay file that isn't empty. So how does this model work?

[Spildit]

SHT DEMO might not work as expected on newer Trinity drives. Might be buggy as well.

Can the OP post a photo of the label of the drive ? There should be a mention to the firmware version like F/W or something like that on the label.

[helpless]

Option 1. What is the point in copying ROM from donor to patient PCB (opposed to simple pcb swap)? And have you ever tried to write saved Samsung ROM to PCB and has it worked? I have never tried it, just want to know if it really works.

The OP will have to buy some PCBs and try them, maybe he/she will be lucky.

Can the OP post a photo of the label of the drive ? There should be a mention to the firmware version like F/W or something like that on the label.

Samsung very rarely prints the fw on the label.

[Spildit]

Option 1. What is the point in copying ROM from donor to patient PCB (opposed to simple pcb swap)? And have you ever tried to write saved Samsung ROM to PCB and has it worked? I have never tried it, just want to know if it really works.

If you have 1 working drive + 1 non working drive with same ROM version and damaged drive have wrong ROM then if you copy correct ROM and write it to damaged drive then you will end up with 2 working drives without swaping PCB. Advantage is to save $$$ in buying PCBs or entire drive to swap PCB and end up with 1 damaged PCB.

Yes, it does work as long as you can write to ROM. Tested this with Trinity with FIPS module. On several drives i was able to write the ROM back to the PCB by TTL and SHT full version (latest version).