How to Use New Phoenix Bios Mod Tool to Modify Phoenix/Dell/Insyde/EFI Bios Files

You need to login to view this posts content.

 

dell bios without slic for ex-gx620 using pheonix mod

tell me the process of moding optiplex gx620 /d610 using pheonix tool 1.21

 

hello,
i wanted to patch my Vaio VGN-N38Z but i can't find its downloadable bios on Sony's website, and it doesnt seems to be any updates for it..
will this tool work on bios backup files made with WinPhlash ?
thanks

 

Reporting successful flash. Used Andy's latest tool on my Dell D610 with the R/W report, worked liked a charm.

Thanks to Andy for updating the tool to do full Dell mods!!!

 

i do the same way for gx620 but xp keep on crashing the system

 

You need to login to view this posts content.

 

You need to login to view this posts content.

 

This may be a bit off topic, but I need to replace the SiI 3114 module in a Phoenix Bios on an Arima HDAMAI motherboard, Bios 1.11. SiI code 5.0.49 (currently in BIOS) with 5.0.4.3 (fixes a bug where the controller won't recognize a Sata II drive). Obtained Phoenix_Tool_1.2.4 from a link somewhere on this forum, and it looks like this tool distribution may be able to do this, but I'm not sure the method I came up with is safe or not, since the focus for this tool is changing the SLIC (not needed for this system as it runs linux.)

Will this work?

1. Start PhoenixTool.exe and open the 1.11 BIOS, this creates a DUMP directory containing the broken out BIOS contents, including OPROM3.ROM and ROM.SCR. The former is the SiI code (determined with linux "strings") and the latter is needed by prepare/catenate.

2. Close Phoenix_Tool without doing anything else.

3. Open a Command shell, navigate to the DUMP directory then do:
del OPROM3.ROM
copy ..\5043.bin OPROM3.ROM
..\Phoenix_Tool_1.24\prepare ROM.SCR
..\Phoenix_Tool_1.24\catenate ROM.SCR

Doing that generated only a single error (where a compressed file was larger than uncompressed) and the resulting ROM file was the expected amount larger than the original.
EDIT: Correction, the new one is 524288 bytes and the original is 526214. The smaller size is generated even if no changes whatsoever are made, just expand with Phoenix_tool, run prepare and catenate. Expand the resulting (slightly smaller) BIOS.ROM again with Phoenix_tool, md5deep on original versus "should be like the original", and find that ROMEXEC0.ROM (only) has changed, although both are 27375. The change is the same 3 bytes as mentioned 2 posts forward, but this time at offset 6083. The space difference must be coming out of a hole or something.

Used phnxdeco to take both the original and the new one apart, then ran md5 on all the parts and found all modules had the same checksum EXCEPT:

OPROM3.rom (this was expected as it was replaced)
ROMEXEC0.rom (?)
BIOSCOD0.rom (?)

Does this look OK or is there more that needs to be done? I tried to attach the log file but for some reason or other attachments weren't uploading. phnxdeco showed that most of the pieces were in the same order, but STRINGS, UPDATE, and SETUP had moved around.


Thanks.

 

Hi,
I have new laptop vostro V13 and desktop Vostro 430 with SLIC 2.1 and windows7 home32. How to activate windows 7 ultimate x64 ? Do I need to mod their BIOS or could I only replace certificate and serial number (provide with modtool ?)
Thanks

 

You need to login to view this posts content.

 

Apparently the latter...

Code:

  phlash16 NEW_BIOS.ROM /C /Mode=3 /CS /EXIT /BU /PN /V

stops at the "Verify interface" section in the menu with the message:

Code:

   Platform Signature not found in the interface

For a positive control, tried to flash it with the manufacturer's 1.11 BIOS (same as currently on the machine, so dropped /BU) like:

Code:

  phlash16 HDAMAI.111 /C /Mode=3 /CS /EXIT  /PN /V

and it ran normally, flashing the BIOS and the system works as it did before.

Suggestions?

Thanks.

 

I used the tool as instructed and was able to modify the bios for HP pavilion DV5. Now I have FD bios files that are modified. Is it possible change the FD files back to EXE files for flashing in windows. It is recomended that INSYDE bios be flashed in windows using EXE file. any help would be nice.

 

You need to login to view this posts content.

 

WHO KNOWS WELL DELL BIOS AND ANDY"s TOOL??????

Can anybody answer the following:

1) Original Dell Bios are .exe
2) If original Bios DOES NOT have SLIC tables then the tool will not inject it ?
3) Only if you do an RW report then the tool picks SSV2 and does inject the SLIC

Why I say all above?
Did get the Dell BIOS from Dell site and at the time was not aware of RW report.
Even Andy's tool version 1.24 went Dynamic and gave a success at the end creating a new _SLIC .exe and I flashed it successfully, then there was NO SLIC in that "modded" bios at all.

I am bloody lost !

 

You need to login to view this posts content.

 

I have the same question! I own a optiplex gx280 and this machine also doesn't have a slic table. It is not clear for me if you need a RW report or not and which method is needed (dynamic or SSV2).

 

Hi, and it seems nobody bothers to answer..................great help !

My understanding is that in case of DELL if you have no RW report the tool automatically goes to Dynamic BUT if there was no original SLIC in the DELL bios, eventhough the tool will say:"Sucess" NO SLIC WILL BE INSTALLED. Quite amazing...........................
If you have the RW report then the tool goes automatically to SSV2 and then the SLIC will be there.
Now another thing. ASSUME that your optiplex280 BIOS is XXXXX.exe (all are .exe from Dell, I believe and based on Phoenix) being the ORIGINAL you start with; then the modded version will be renamed xxxxx_SLIC.exe. CAREFULL HERE. Why, because if you execute that from Windows it will pick up the xxxx.exe (do not ask me why but with a HP it did that to me).
So best way is to RENAME the xxxxx_SLIC.exe away (in another folder) from the same folder where the original may be and then do a flash in DOS mode.
If you have no flopy drive then either a DOS USB or a DOS CD ROM start up must be done with the renamed xxxx_SLIC.exe included. So when you boot from DOS you can execute then that file and flash the BIOS and then hopefully you will have the SLIC into the machine.

Good luck

 

With no SLIC you need the SSv2 mod. Dynamic is simply changing 2.0 SLIC to 2.1..

RWE report is the safest way as it will allow the tool to parse the IDs correctly and change them accordingly.

Always change the bios to the original name before flashing. however you have to do it is up to you. do not try to flash with the _slic addition.

 

As usual is a GREAT PLEASURE to say thanks and hello to 911Medic. It has been a while..........................thanks !

I suspected since I achieved nothing and momentarily ended with KMS and WIN 7 Enterprise in that machine so now I will do it properly.
Did a HP Pavillion as you suggested in your above comments but what killed me this time, being the first for Dell is that unlike HP the .exe are not winrar extractable to become .wph.

Ok, maybe one day I will be BIOSSOMEIDEA.................................

Cheers from Oceania