no .. i never looked at that tool before building this one .... just my friend gave me the rough idea and the files needed .. as i was in confusion about several optimization concepts .. ! anyways ... many of my friends have tested this and then i posted it .. here ..!
Willpower 2 learn As some how under the other post, I bricked my R3000 Laptop.. Or So I thought. After getting angry destroying my mouse, and 100$ later (hadda buy a new burner cuz I spilled so ****) and a usb floppy to resore. ANYWAYS With help I learned how to restore this particular model (WILL MAKE TUT LATER) I want to know if someone can revise the Phoneix guide? I messed up on the part of hex editing and something about pasting 4 spaces after ect.. then someone correct it and said its like this.... nah Bah Bah then your wrong its this.. that kind of thing.. So its too confusing.. I really want to learn how to do these on my own.. It seems award and ami have auto builders, but phoenix is difficult. maybe some pics and a step by step tut would be great as I dont think anyone can understand the phoenix tut and it is the hardest one to do.. I mod xbox's and ps2 so I am firmiliar with Jtaging, flashing, and also rocovering dead bio's made a 29 wire mod fer this.. but to get vista working with a flash... I WANNA LEARN a to z
@simbalage22 The bigiest problem with Phoenix bioses is PBE. At some bioses I'm forced to decomres them several times just to make shure that it is decomresed properly...(the same goes for the build process). When modding Phoenix bioses, make a temp directory in which you can copy all the decompresed files from the PBE's temp directory. Decompress several times to see if there is deference in the size of BIOSCODE modules. Make shure that before you begin modding to replace all BIOSCODE modules in the PBE's temp directiry with the BIOSCODE modules that had the largest size while decompresing the bios several times. Once you see a defernce in size, copy the BIOSCODE to the temp directory you've created, does making a colection of BIOSCODE modules with the largest decompressed size. Take note that this was the case with your bios and is the most probable couse why you coprupted your bios. Although I cant say for shure untill you upload the mod that you made.
You can only decompress ROM and WPH files using PBE.(PBE = Phoenix BIOS Editor) The dell's .exe file is usualy undecompresable using standard tools, like winrar. At some cases Universal Extractor might help. BTW, I'm not shure of this, but I think that dell's .exe files for bios updating, only update the areas of the bios that needs to be udated. So the dell's exe file doesn't contain the whole bios. In some cases extracting the bios from the RAM might help.
TRIED IT how exactly.. I removed < > and put C:\file in its place under run.. It went thought but i dont see any output file. I want to use this gx240 as a toy to learn how to encode these bios's
Another quick question. I have Hp OEM disc. Can you use a compaq slic on other brands like dell for patching?
Phoenix Bios Modding.. Someone Clairfy I will Post the original TUT In Bold and my questions in plain text. Phoenix: -Open bios.wph or bios.rom with Phoenix BIOS Editor The bios will be decompressed, all parts are in Phoenix BIOS Editor\TEMP folder now. You can open them with winhex to edit. Got this part -Search for "SLIC" to find a already present SLIC tabe. If found DO NOT modify try to activate first. If it doesn't activate check Everest. No SLIC present at Everest, modify bios where are we searching. Folders, In the Flash program What? Where? how? -Copy file with slic table into Phoenix BIOS Editor\TEMP and rename it to the next higher ACPIn.ROM. (n ist the next higher acpi number). What File? The hp, asus, ect bin files? So the bin file should look something like ACPI2.ROM Correct? -Open rom.scr with notepad and add a line "ACPI ACPIn.ROM -X", save it. So I would add the line with or without " " How should this line be added? -Search for "RSDT" and if present "XSDT" string. Overwrite string next to "RSDT" and "XSDT" with your OEM table and OEM table ID you want. They are usually found at BIOSCOD1.ROM file. Save changes. This is the part I was totally lost On That caused me to brick my laptop. -To enable save button (now is gray) change something random in Phoenix BIOS Editor and restore its original value -Save bios and check log for errors Got this part To Those that wanted to know how I crashed my laptop this is how.. I wasnt sure adding lines in the BIOSCOD1.ROM file. Any help Would answering these questions Would be great. basically need to know how to do the Phoenix Bios's So I can help people with ALL the bio's. reginakampher you were asking how I crashed that R3000. This is why. I am not completly understanding this TUT.. maybe you too could help Thanx In Advanced
When you look in the temp folder after decompression, you will find files that are named ACIPx.rom. "x" being a variable number. Open these files one by one in winhex and search for the string "SLIC". Yes, that's correct. Add it without the quotes. You would add the line here like this. I'm adding the line ACPI ACPI5.rom -x Code: BANKS -N:1 -S:1024 COMPRESS LZINT BOOTBLOCK BB.ROM -S:32 ACPI ACPI0.AML ACPI ACPI1.ROM ACPI ACPI2.BIN ACPI ACPI3.ROM -X ACPI ACPI4.ROM ACPI ACPI5.ROM -X <---New line added here BIOSCODE BIOSCOD0.ROM BIOSCODE BIOSCOD1.ROM BIOSCODE BIOSCOD2.ROM BIOSCODE BIOSCOD3.ROM BIOSCODE BIOSCOD4.ROM BIOSCODE BIOSCOD5.ROM BIOSCODE BIOSCOD6.ROM DECOMPCODE DECOMPC0.ROM DISPLAY DISPLAY0.ROM LOGO LOGO0.BIN LOGO LOGO1.BIN LOGO LOGO2.BIN LOGO LOGO3.BIN LOGO LOGO4.BIN MISER MISER0.ROM MODULE MOD_4800.ROM -C:H0 MODULE MOD_4B00.ROM -C:K0 MODULE MOD_5100.ROM -C:Q0 OPROM OPROM0.ROM OPROM OPROM1.ROM OPROM OPROM2.ROM -X OPROM OPROM3.ROM -X OPROM OPROM4.ROM -X OPROM OPROM5.ROM -X ROMEXEC ROMEXEC0.ROM ROMEXEC ROMEXEC1.ROM -Z SETUP SETUP0.ROM STRINGS STRINGS0.ROM TEMPLATE TEMPLAT0.ROM UPDATE UPDATE0.ROM USER USER0.ROM -X HOLE -A:0xFFF00000 -SB:131072HOLE0.ROM HOLE -A:0xFFF90000 -SB:4096HOLE1.ROM HOLE -A:0xFFFA0000 -SB:1024HOLE2.ROM Here is a sample winhex display of BIOSCOD1.ROM after searching for the RSDT string. Code: Offset 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 00050640 67 66 81 4F 14 01 00 00 00 66 33 C0 E8 06 08 67 gf.O.....f3Àè..g 00050656 66 89 47 08 E8 9B 01 66 5A 07 C3 A9 FF 0F 74 06 f‰G.è›.fZ.éÿ.t. 00050672 66 05 00 10 00 00 66 C1 E8 0C 8B C8 C3 52 53 44 f.....fÁè.‹ÈÃRSD 00050688 54 00 00 00 00 01 00 54 4F 53 43 50 4C 54 4F 53 T......TOSCPLTOS 00050704 43 50 4C 30 30 00 00 00 00 20 4C 54 50 00 00 00 CPL00.... LTP... 00050720 00 06 66 53 F8 E8 5A 01 72 03 E8 36 0E 66 5B 07 ..fSøèZ.r.è6.f[. 00050736 C3 66 56 66 57 1E 06 F8 E8 47 01 72 03 E8 CF 0E ÃfVfW..øèG.r.èÏ. 00050752 07 1F 66 5F 66 5E C3 06 53 67 66 3E 8B 7D 04 ..f_f^Ã.Sgf>‹}. I highlighted the RSDT string in blue and the area that needs to be edited with red. You would do the same if XSDT string was found. OEM ID and OEM ID table will always be 14 bytes. It's always best to edit this in hexdecimal than in text. Any questions just ask.
As for this part... As I am making a Complete Tut thanx to you, as well as learning.. The Tut says "Search for "RSDT" and if present "XSDT" string. Overwrite string next to "RSDT" and "XSDT" with your OEM table and OEM table ID you want. They are usually found at BIOSCOD1.ROM file. Save changes." meaning Search for both terms "RSDT & XSDT. Correct. now What is an OEM Table and table Id, and how does this Fit into the hex? because THIS THIS step right here is where i know I jacked up.. Here is a sample winhex display of BIOSCOD1.ROM after searching for the RSDT string. Code: Offset 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 00050640 67 66 81 4F 14 01 00 00 00 66 33 C0 E8 06 08 67 gf.O.....f3Àè..g 00050656 66 89 47 08 E8 9B 01 66 5A 07 C3 A9 FF 0F 74 06 f‰G.è›.fZ.éÿ.t. 00050672 66 05 00 10 00 00 66 C1 E8 0C 8B C8 C3 52 53 44 f.....fÁè.‹ÈÃRSD 00050688 54 00 00 00 00 01 00 54 4F 53 43 50 4C 54 4F 53 T......TOSCPLTOS 00050704 43 50 4C 30 30 00 00 00 00 20 4C 54 50 00 00 00 CPL00.... LTP... 00050720 00 06 66 53 F8 E8 5A 01 72 03 E8 36 0E 66 5B 07 ..fSøèZ.r.è6.f[. 00050736 C3 66 56 66 57 1E 06 F8 E8 47 01 72 03 E8 CF 0E ÃfVfW..øèG.r.èÏ. 00050752 07 1F 66 5F 66 5E C3 06 53 67 66 3E 8B 7D 04 ..f_f^Ã.Sgf>‹}. I highlighted the RSDT string in blue and the area that needs to be edited with red. You would do the same if XSDT string was found. OEM ID and OEM ID table will always be 14 bytes. It's always best to edit this in hexdecimal than in text. Any questions just ask.[/QUOTE]