![]() I have not fully tested changing the BIOS logo through hex editing (AFU Change Logo worked for me), but I have successfully removed the BIOS logo by deleting the Logo.bmp, MyOemLogo1, MyOemLogo2 modules, repatching, and flashing the BIOS. This is a useful thread on how to change the GIF image through hex patching manually. ![]() This is how the “ AFU/AMI Change Logo Utility” works, it detects the header to find the modules with a “logo” tag and repacks modules with modified images passed into the program. The BIOS code will only show the image on POST if the header (in hex) of the Logo.bmp, MyOemLogo1, MyOemLogo2… etc. The process of changing the BIOS logo is similar to removing it. To change it, first dump your BIOS using Intel FPT on DOS or through Windows (DOS is more stable because there is less risk of corrupting the BIOS flash, which could require another SPI flash). I have posted on another thread describing the process in detail for removing it. The UEFI BIOS logo is the one that shows up during POST and while Windows boots. I recommend using UEFITool 0.21.5 (other versions won’t let you repack modules) to look into and modify BIOS modules: DXE drivers/menu configurations/CPU microcode update/etc., a small part of the BIOS that changes how the BIOS ROM works on the system. On Clevo P650RE3 models, you can also DUMP the ME and FD regions using -ME and -FD command-line flags respectively. NOTE: DO NOT attempt to flash using fptw -f without -BIOS, you will be flashing ALL firmware files accessible through FPT! Remember to make backups regularly and note what you are flashing. Here’s a short crash course on Intel FPT (how to flash a modified BIOS when you have an Intel motherboard/CPU):įptw -f -BIOS → lets you flash your BIOS regionįptw -d -BIOS → lets you dump your BIOS region You can check out the BIOS from the clevo mirror posted here and using amibcp, hxd, and uefitool ![]() The prema mod for a similar model (P650SG) doesn’t have that structure/format either. Where it says “suppress if true…” I changed it to false by changing the 46 to a 47, but still no chipset options after flashing. I’m having trouble here: …072122.png?dl=0 I found no hex strings like that (Setup, Advanced, Chipset, Security, Exit: 01 01 00 01 01) in the IFR file… I tried this tutorial: …io…nus-MSR-unlock! However chipset options are still locked down though, even after trying to change the hex codes to false. AMI-specific features like NCBs, ROM_AREA structure and other things like that can't be implemented by me because of the NDA I have.My Sager NP8657-S (Clevo P650RE3) laptop arrived yesterday and I was successfully able to unlock the advanced options! I flashed using Intel FPT and I got an original backup of the BIOS and modded the advanced and chipset menus in AMIBCP.If someone wants to write an unpacker for such crappy files - I will be glad to use it. The program is meant to work with BIOS images, not some vendor-specific BIOS update files, that is why some of that update file either cant be opened at all or return errors on reconstruction.It's on my high priority features list, so I hope it will be corrected soon. Some images may not work after modification because of no FIT table support implemented yet.Some images has non-standard calculation of base address of TE images, so the program can rebase them incorrectly after modifications.Don't rush it, because reconstruction process can also generate some usefull messages, which will be lost if you open the reconstructed file immediatelly. If anything goes wrong on the reconstruction, an error will pop up, otherwise the program will prompt if you need to open the reconstructed file. After you've finished the modifications, you need to initiate image reconstruction using Save image file command from the File menu.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |