02-07-2017, 10:02 PM
(This post was last modified: 12-19-2018, 04:30 AM by DeathBringer.)
Hi, I am looking to modify the ACER VN7-791G-762X VBIOS and detail the steps taken in a clear consistent manner. Sadly I have not successfully modified a VN7 VBIOS yet but I strongly believe we can done it with strong contributions of our community.
Tools I am using, one of the most recent version of fpt and FTK, Phonenixtool266, MaxwellBiosEditor and the flash file (isflash.fd) from BIOS 1.13 for the ACER VN7-791G from the official Acer website.
I have packed them for convenience here: http://www.filedropper.com/tools_2
- Open Tools/phonixtool266/PhoenixTool.exe (run as admin)
- Select the bios(click the 2 dots button in the Original BIOS field)
- Select Tools/isflash_original.fd -> Open
- Status will change to "WORKING..." once done a DUMP file will be created in Tools/
- There are two 102KB ROM files that Maxwell Editor can open, one with a creation date of 06.05.14 (908708D4-1836-4396-A06D-526006C66361_1816.ROM) and 908708D4-1836-4396-A06D-526006C66362_1822 with a creation date 11.27.14 - I can only assume the latest one is better.
- After editing the BIOS setting you can select "Save BIOS" you can see this ROM file has been edited as the date modified will be current when looking in windows explorer.
- At this point you can go back to the Phoenix tool and click "Go" this will "repack" and create a new .fd file in the same folder the Original BIOS .fd file was loaded. NOTE: The only way I was able to repack was by going to advanced and ticking "No SLIC" as there is no ACER SLIC BIN file provided.
- Put your computer to sleep and wake it back up (this remove the write protection)
- At this point open a command prompt as administrator navigate to WHEREVER YOU STORED TOOLS ON YOUR PC\Tools\FTK10\Windows\
- type fptw -f nameofthenewfdfile.fd -bios, you will be told the sizes don't match. this is the case even when trying to flah with the original bios.
- If you get a protected error, put your computer to sleep and wake up then try the command prompt commands again.
- All that needs to be done now is restarting the PC