Samsung HD204UI firmware udpate help
I recently got a 2tb Samsung HD204UI and I could really use help making a bootable cd or usb thumb drive in order to run the firmware update. I've spent a few hours trying various things and I'm just not getting it at all. The samsung website provides me with a zip file (http://www.samsung.com/global/business/hdd/faqView.do?b2b_bbs_msg_id=386) that contains an .exe file and instructs me to create a bootable cd or usb drive in order to run it. I've tried tinkering with nero/ultrasio/magiciso and I Just can't seem to get it. From all the reading i've done, i'm assuming i have to take the .exe file then somehow make that into a bootable iso file - i've made it into a regular iso file but not bootable - and then create a bootable usb drive with it. But i really can't get past the first step - if that is even the route to go. What do i need to do? What programs do I need? Any help would be appreciated or even a link with pictures of a step by step guide. Thanks in Advance.
There is no need to create a CD ISO.
Create the bootable USB flash drive, then unZIP the contents of the ZIP file to the root directory of your USB drive.
Reboot from the USB drive and type "FAEG" at the DOS prompt.
BTW, the BIOS must be temporarily reconfigured for legacy IDE mode, not SATA mode.
I'm having an issue. I managed to get into the SFLASH menu via bootable CD but I don't see it flashing the firmware.
Searching shows that most people just typed in the "F4EG" and the program installed it. All I get is a menu. Do I have to type a specific command? A scan shows the hard drive is port 2. Thanks.
I have tried both F4EG and F4EG.exe. The response I get in command prompt is "Bad command or filename" if I don't include the "X:\" .
They brought back a few pages of results but here is the first page of each:
Some details that may be useful:
Windows 7 Ultimate 64-bit
Burned onto a CD-RW and threw the F4EG.exe in the root directory after. I notice you refer to it as "FAEG" Is there a different file?
Thanks for the feedback. I wasn't sure whether X: was the drive letter of a RAM drive. For example, Seagate's CD based firmware updaters create a RAM drive and then extract the firmware files to this RAM drive. I was wondering whether F4EG.EXE (not FAEG -- sorry) operated the same way.
I notice that Samsung's instructions say to "connect Target HDD to Primary / Master". Instead you say that your drive is connected to port 2. Is this SATA port 2 or IDE port 2?
Have you configured your SATA controller for "compatibility" mode in your BIOS setup? This will make your drive look like a PATA drive, not SATA. Samsung's updater is looking for a PATA drive.
FWIW, here is a Dell update for older Samsung models:
It uses an earlier version of SFLASH. The command line to update the firmware is ...
sflash24 /run:1107.est /auto
In your case I would try ...
I'd disconnect all other drives just to be safe.
I left the other HDD plugged in this time. I have my data backed up in case.
Yes, I tried that too. F4EG just brings up that main menu like before.
It finally worked! Thank you, fzabkar!
After several attempts of trying this, I was able to re-flash successfully. I made sure:
-All USB flash drives were disconnected
-No other HDDs were connected except the Samsung
-The Samsung drive was plugged into 'SATA1' on the mobo
-The SATA configuration was set to 'Compatible' in the BIOS
This time the FREEDOS boot menu was actually a little different for me while getting to command prompt than what I was given during the unsuccessful attempts. I knew something was up when I didn't get the usual 'X:\FREEDOS' in command prompt either; all that was there was a 'X:\'. I just typed 'F4EG' and hit Enter and watched it successfully do it's thing. Here is a screen shot:
This thread saved me tons of time. As noted by @Wiznaz (Mike) I will confirm that by:
1) SATA configuration set to 'Compatible' in the BIOS on my Asus P7H55-M motherboard
2) Samsung drive was only one attached to system and it used SATA connector #1
3) Only USB device was my FREEDOS boot drive created via Rufus (http://rufus.akeo.ie)
4) My only stumbling block was attempting to adjust my boot priorities in order to get the USB drive to boot; ultimately never worked and the answer was to hit F8 after POST messages and I was given the choice to use by USB drive as boot device.