Flashing & Recovering Phoenix BIOS: Which Phlash? Which DOS?

Discussion in 'BIOS Mods' started by drool, Feb 27, 2010.

  1. drool

    drool MDL Novice

    Jan 26, 2010
    #1 drool, Feb 27, 2010
    Last edited: Feb 28, 2010
    Is there a preferred version of DOS & phlash16 to be used when flashing a modded BIOS or recovering from a bad flash?

    I've been lurking around here and now have successfully flashed a modded BIOS on an older motherboard. This was more of a test than anything else. I would have tossed the motherboard had I bricked it.

    Now I want to go for higher stakes and install a modded BIOS for my Toshiba Satellite A205-5804 that was created by Busykid508 as described here.

    It's my belief I should try to use the manufacturer's tools whenever possible. I am able to dig some out of the most current BIOS download.. To do this I used 7-zip. The 9.10 beta version to be precise.

    Doing this, I can get a phlash16.exe file along with DOS files that I presume to be MS-DOS but could be a freeware clone. The DOS files can be used by the HP USB Disk StorageTool for creating a bootable USB memory stick necessary for BIOS flashing outside of Windows.

    But the articles that I've read here mention MiniDOS and other versions of phlash16. Are there reasons for using these instead or are these simply listed for everybody's convenience?

    I'm mainly concerned about recovering from any bad flash that I may do.

    Anyway, for those who may be interested, I'll now explain how to extract phlash16 and DOS files from Toshiba's BIOS download, sa200f3v250.exe

    (Actually, you can do essentially the same thing with Busykid508's modded BIOS download.)

    First off, when you install 7-zip, you'll have the option of integrating it into Windows Explorer which is how I always use it. You now can right-click on whichever file you want to extract from choosing the 7-zip option and its daughter dialog box or whatever this Windows feature is supposed to be called. (Trying to make this as easy as possible for the newbies but I suspect that this all old-hat for most everyone here.)

    Anyway, after you've downloaded sa200f3v250.exe, you can extract everything into a folder "sa200f3v250" using the right-click method I've just described. Go into this folder with Windows Explorer.

    Inside this folder there is a file "[0]" which you will now do the same thing and extract everything inside there to yet another new folder, "[0]~". As before, go into this folder.

    Inside "[0]~", there is a file "2258d250.exe" which appears to be a WinImage Self Extractor file. Once again, right-click on this and extract everything into still yet another new folder, "2258d250". As before, go inside.

    Now you will find a single file, "2258d250.ima". Yes, once again, right-click on that and extract the contents into one more new folder, also called "2258d250". Go inside.

    Now you've finally gotten to all of the files that you may want: "msdos.sys", "io.sys" & "command.com", which are needed by the HP USB Disk StorageTool to make a bootable USB memory stick, "phlash16.exe", the Phoenix flash utility, and "autoexec.bat", which is actually a executable text file that will show you the proper command-line options for running "phlash16.exe".

    Speaking of options, does anyone know what "/mode=3" means and why this necessary? What will choosing each of the different mode numbers do for you?
  2. drool

    drool MDL Novice

    Jan 26, 2010
    I stand corrected.

    The last part of my previous post does correctly describe how to extract MS-DOS files from a Toshiba BIOS download but these appear to be OLD MS-DOS files. From 1994.

    I should have realized something was not quite right when my USB stick could be formatted only to the original FAT file system format but not to FAT32.

    My recollection is that there is a 512MB drive size limit for FAT. The HP USB Disk Storage Tool successfully formatted my 1GB USB memory stick, albeit to ~512MB, but my laptop couldn't boot off of it.

    Oh well, nobody thought this thread was worth responding to anyway.
  3. danjr

    danjr MDL Novice

    Nov 23, 2010
    Which Phlash? Which DOS?

    I am actually curious about this same thing. I followed the same steps to try to recover an HP Dv9000, albeit using a self-extracting zip for the bios, and using another DOS version I had found while trying to recover a deleted partition table (ugh).
    Although, the version of DOS I used had no HIMEM running (at least as far as I could tell, no config.sys or autoexec.bat), when I ran phlash16, it errored out saying could not run alongside memory managers, like HIMEM... Trying to find a solution to this problem, but seems I will keep searching.

    In other words, "bump".
  4. tqhoang

    tqhoang MDL BIOS Modder

    Apr 29, 2008
    Are you sure there is no himem.sys running? By default Windows hides operating system files like config.sys. You'll have to adjust your folder viewing properties to display them & also display any hidden files too.
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. Japheth

    Japheth MDL Novice

    Jan 11, 2011
    flash your bios from vista/7 installation disc instead

    You don't have to try flashing your bios with phlash16.exe from dos, which is quite hard coz of himem.sys or any mem manager that is booted together with win98boot etc.

    here is what i did when i needed to flash my toshiba a200-24a with new bios ver.:

    1. download winflash.exe and the bios *.rom file (usually it comes together in a single setup.exe file and copy it to usb flash drive (UFD) e.g. sandisk 2gb.
    2. boot from vista/7 installation CD or either WinPE/RE CD.
    3. when you get to "Install Now" window press SHIFT+F10 keys. and a command prompt will appear. (black window - commandline)
    4. look for you usb flash drive letter. e.g. c: or d: or e: etc..
    5. run setup.exe or winflash bios.rom (according to the manual)

    now the flashing process will start!
    when finished Reboot.
  6. sebus

    sebus MDL Guru

    Jul 23, 2008
    Dangerous!, install disk is not full Win32 system, so it might or might NOT work as designed

    But it is you that take the risk after all...

  7. pipeld

    pipeld MDL Novice

    Mar 17, 2015
    thanks a lot it helped me solving issues