There are so many posts to this thread, my eyes were getting blurry trying to track information down. So, as a last resort, I'm posting in hopes of getting some assistance. My laptop is an HP dv6-6145dx with AMD A8 processor, running BIOS F20. I have Phoenix Tool v2.14 installed. I ran it on the BIN file taken from my Insyde BIOS download file (extracted using WinRAR) and discovered the white list is there and a crappy list of cards supported. I understand about the 3 key identifier for the card (vendor, product, subsys) and how the hex code is transposed (e.g. 18 14 becomes 14 18). So I have no problem with knowing how to identify a card entry and how to obtain the hardware identifier from device manager properties. What puzzles me is this rather easy statement of "just search and find the codes". The ROM files are binary, so my eyes glaze over with the dreaded thought of dragging each individual ROM file into a hex editor and searching. Is there any way to narrow down which file likely contains the white list codes? Also, am I right that when you edit it, the Phoenix Tool will detect the change and automatically apply it when "Dynamic" mode is selected?
Serg008, Backup didn't work with Flas**t. Says IHESI 10h Fail, Internal error ef function not supported.
Serg, Do you think it makes a difference if the backup I sent you to remove the white list was created while Secure Boot was still enabled? I or course have it disabled when trying to flash the new BIOS but am pretty sure it was enabled when I made the original backup that I placed on File Send for you. Also I went back to the first step. Some times I find starting fresh either works or reveals something I may have missed. I am running the FPT backup utility with Secure Boot OFF. This is now in the error log. Error 26: The host CPU does not have read access to the target flash area. To enable read access for this operation you must modify the descriptor settings to give host access to this region.
Thanks for clarifying the issue. It has a feature to protect it from writing an old bios over a new one, Back Bios, something like that. I tried with it enabled and disabled with no positive impact. I'll not be soldering anything I can assure you. Frustrating that some of these G580's have this kind of write protection and some apparently don't. Not sure if there is anything to be learned from looking at the BIOS Universal Bios Tool backup as compared to the FPT tool. The Flas**t thing seemed to be for an IndyeBIOS and mine isn't. If there is anything I can try let me know. Thanks again however, Jim In doing some searching looks like this is not a new problem/issue. A few threads indicate if a new bios is released after installing it the write protection bit might get reset.
Hi Serg, I was wondering how to do the bios mod for Lenovo Z580. I would like to back up the bios, but I get different md5 checksums with two different tools. Can you send me the process of moving the whitelist. Thanks in advance!
Serg, is it possible to edit the white list for an HP Insyde BIOS that is RSA signed? I have learned the procedure for extracting the BIOS data using the Phoenix Tool and how to recreate the files for normal BIOS recovery. The additional step would be to edit the ROM file containing the white list and then let the Phoenix Tool rebuild the BIOS files. If the modification is only to adjust the existing hex values, meaning to exchange the references from one wifi card to another, will this work? The steps I followed to produce a BIOS that will be properly flashed when rebooting with Win + 'B' keys held involves selecting the correct SLIC file in the process (in my case it is the SLIC_MPC 2.1, as indicated by the RW report). However, Yen's instructions on the 1st post state to select in the advanced options "NO SLIC", and says "Please note we don't use the tool to SLIC a bios, but to decompose the modules / rebuild the bios." So I'm not quite sure what that means and the implications. Should the SLIC file not be selected in the process? Or does it just mean that the BIOS files will be reassembled differently?
OK, thanks for your response. Do you know anyone who might, and if so can you point me to them? I'd greatly appreciate it.