PhoenixTool should be the first choice when dealing with odd BIOS containers.
But I made a little .bat to avoid using it all the time. The 2 files should be in the same folder as Dell exe file, probably a clean one to avoid misdetects. You should also install Python and 7-zip, then correct their location in line 27 (ususally C:\Python\python.exe) and line 120 (usually "%programfiles%\7-Zip\7z.exe" or "%programfiles(x86)%\7-Zip\7z.exe").
One particular note is step 5, which is searching in %temp% for any unpacked BIOS files. Therefore it is needed to have a cleaned temp folder (at least from any .hdr/.fd/.rom/.cap/.bin) and to let the error message open for 5 seconds, otherwise the unpacked files will get deleted once message is closed. But a manual search is far better, I only implemented this as a quick solution.
I have tested with multiple types of files. With "Dell Vostro 3560 A13.exe" and "L322XA08.exe" even PhoenixTool fails.
Note that Iām note a coder and this suffice for my needs. If anyone is able to help, even with a feedback, please do so. Credits to JimboBobB from MDL for Dell_HDR.py
Edited: I have added a new .bat, which should reduce the number of error messages. If you get more than one error, than it is likely that the BIOS needs another extraction method. Just drop the exe file on the bat. The requirements have changed a bit. The .exe, Dell_HDR.py and .bat should be in the same folder with no other BIOS file (.fd, .rom, .bin etc.) around. Also it is now needed to have hexfind.exe from UBU in the same folder. Since CodeRush has put some work in providing this file and I donāt plan to release this as a standalone package, I donāt think it is fair to add it without his consensus.
It has been tested with some limited samples I had, but it is more than likely that it wonāt work for each one. That is why I posted here, for some feedback.
Note: You can find download links to a lot of actual and already extracted AHCI/RAID ROM modules from different chipset manufacturers within the start post of >this< thread.
Apologies if my questions are so rudimentaryā¦ Been reading the posts but hasnāt really addressed any of the questions I have.
How do I know which processing tool I need? It does say download all of them which I have done, and if I want to update the Intel RAID ROM module and I have a gigabyte motherboard, am I safe to assume that I use CBROM_155 with the associated bin file?
Is it trial and error?
Or should I be using UEFI BIOS Updater?
Not understanding the differences between CBROM and the UEFI BIOS Updater.
Pardon me if this is also discussed elsewhere and if it is please could you point me in the right direction?
So Iāve got to the below stage where I have updated the bios file with the AHCI/RAID ROM module (Intel_RST_RAID-ROM_v11.2.0.1527) file named 8086-2822_11201527.bin renamed to pchraidr.bin
Yes! You are right: The linlk was broken, because the website win-lite.de doesnāt exist anymore. I am sorry about the broken link, which is now corrected.
As the name "UEFI BIOS Updater" already says, the UBU tool is only usable, if you want to modify an AMI UEFI BIOS. Only rather new mainboards (from Intel 6-Series Chipset up) have such BIOS. As you already have found out, you have to use the tool CBROM, because your mainboard has a Phoenix/Award BIOS.
Yes!
You can use either of them, but I would prefer the DOS Flash Utility. Donāt forget to store somewhere the original BIOS to be able to reflash it in case of any trouble.
Good luck! Fernando
P.S:: BIOS modding is risky and should not be done in a hurry. This afternoon I will do a deeper look into the BIOS of your mainboard.
Just enter the BIOS of your system. Then you will see, if your mainboard uses a Phoenix/Award or an AMI BIOS. After having found out the BIOS type (Phoenix/Award, AMI or UEFI AMI) by entering the BIOS, you know, which of the BIOS modding tools and which one of my 3 guides you will need.
Only for me and other people, who are trying to modify an unknown BIOS, but not for the mainboard owner like you.
Meanwhile I have tested the BIOS modding you want to do. After having downloaded and extracted the latest GA-P55A-UD4 BIOS named p55aud1.f15, I opened it with the tool CBROM v1.98 and got this result:
Since all PCI ROM modules are listed below the sensitive module MINIT, there was no need to use the CBROM v1.55 for the BIOS modding procedure. Then I extracted the original Intel AHCI ROM named pchahci.bin and the Intel RAID ROM named pchraidr.bin from the BIOS to look for the versions of them. After having opened both modules with the Hex Editor HxD I found out, that the Intel AHCI ROM was v1.20E (which is already the latest) and the Intel RAID ROM was v9.5.0.1037. As next step I replaced the Intel RAID ROM v9.5.0.1037 by the v11.2.0.1527 (according to my guide). Everything worked as it should (no error message, no replacement of sensitive BIOS modules were shown). As last step I reopened the modded BIOS and got this result:
Can someone help me to extract BIOS file from EXE flasher, please? Here is the link . It should be Phoenix EFI BIOS. Itās for my Samsung laptop (Intel SB CPU + HM65 chipset). My general goal is to see how outdated are all ROMs which can be updated, and to try to flash a modified BIOS, if it not too risky and is worth it at allā¦
I tried to extract the BIOS from the EXE file by using 7-Zip, the tool Resource Hacker, CodeRushās UEFITool and Andyās PhoenixTool, but didnāt succeed.
Iāve got all the needed tools to update my aging XPS 1645. Iāve got the BIOS I want (WPH file) and Iāve got the latest microcode I want to put on it which is version 7 (BIOS has version 4).
I can find the microcode section in the BIOS and update it using Hex but after saving and trying to install it, it fails due to wrong offset. Iāve also tried to run this past Phoenixtool, in the DUMP folder I can find it in the BB.BIN file, update that section - and then run Phoenixtool again but the problem is that itās not updated (this is where Iām doing something wrong).
Lastly I tried to cheat by using the Hex method first, then running the updated BIOS through Phoenixtool - all looked fine but again, wrong offset so wonāt install.
add: CBROM wonāt do anything with this so Iām using latest Phoenixtool.
hmm, I donāt have anything like that? This is the process I am using with pictures.
1)
2)
3)
At this stage I have my DUMP output and Iāve set the options to allow myself to mod the modules as I understand it.
So now I can navigate to the DUMP directory and modify the BB.BIN file and replace the microcode with version 7. But if I simply do that and then press āGOā it wonāt update it to the new BIOS_SLIC.WPH file.
Instead, if I now press āGOā it will go through itās motions and tell me that I can now modify the entries in the DUMP folder half-way through the process. If I do that and update the BB.BIN file and then let it finish, I get a new BIOS_SLIC.WPH which has been updated with latest microcode - great news.
Pressing āGOā - 1st part:
(Iād now mod the BIN.BB file to update the microcode)
Letting it finish:
Problem: this output is still giving me checksum error when I try and install it?
Please compare the size and the checksum of both CPU Microcode modules (the original and the inserted). If the checksums should be different, you may be able to correct it by using an hex editor.
Alright thanks though I think Iām just missing something simple. For example Iāve just learned that the BB.BIN is actually a Boot Block file, now why would I have to mod this file to update microcode I donāt know but for now, thatās the only āmoduleā that is spat out and where I can find the microcode. If it was as simple as having a microcode module alone itād be simpler (I think, still possible the offset would be off).
Hello Please help me with the bios i have a HP Thin Client with this bios and i have made a mod in the thin client added a memory socket DDR2 so-dimm and tried to put in there 2x2 GB RAM i have tested it but with 2x2GB the TK dont work (it starts and shows 3,5GB but several systems didnāt start) i am 99% sure that the bios have some kind of memory limitation thats why it shows 3,5GB not 4GB
i have tested win7 64, win8.1 64bit both restarts the TK after start about 10 sec windows miniPE XP from cd launched normally (i think its 32bit) and shows 3,5GB same as the bios shows but i have run there a cpu-z and it showed me normally 4GB (2x2GB) in socket 1 2GB running normally in socket 2 2GB runs normally too, 3GB (2+1) runs normally too, but 2x2GB not i think that the bios should show normally 4GB both of the 2GB kingston modules are identikal HP T5735
i do not think that they answer 1 soldered second ram socket void the warranty 2 its to old for warranty 3 do not think that they have interest on answer people who are modding their TKs but thanks for reply
Weāve gotten quite far in upgrading these small devices, but this RAM issue, with the second added RAM socket has reached a āroad-blockā
I understand this site (yours) only deals with the RAID section of the BIOS, but if you can look at the picture (screen-capture) I made, after using the recommended BIOS reading tool you suggested, can you tell us the section of the BIOS dealing with the RAM controller?
In this case, we may be able to compare a working 2 RAM socket thinclientās BIOS section, to this older one. Thank you.
