@Lost_N_BIOS

Thank you so much for your reply! :D


Yes, my chip is W25Q128JV as well. I did what you said:

Please find the attached SCEWIN result, fd.bin, me.bin and mainDXEVol.bin. Only 5.03.111 works.

All writing backs got error 167.

@Black-Xstar - Thanks for the info, and FD/ME dump too. Looks like programmer may be required, since error 167 still on both those FPT runs
But, maybe we can do changes with SCEWin, lets see FPRR is disabled already, so only BIOS lock needs changed, and then if 167 error remains this is due to a FPRR lock in BIOS module and not in BIOS/NVRAM settings (so programmer would need to remove it, if we can find/remove)
Here is edited NVRAM.txt for version 5.03.1111 (This was only one that worked), put this in that folder and then run the command below from Admin CMD Prompt
http://s000.tinyupload.com/index.php?fil...947925063733130

SCEWIN /i /s nvrammod.txt

Then reboot, and try FPT spoiler #1-2 again, using new biosreg name, just in case it passes #2 this time

@Michaelsunzy - Did you brick your system, or are you booting again etc? I was a bit confused with your previous post as to what was going on, what you did etc.
If you can boot now, great! Please wait, we'll see about SCEWin, if this can get past 167 error or not. If not, programmer will be required for edits, and on 167/FPRR I may or may not be able to remove via BIOS edit, I'll have to see if I can find the lock in modules.
Since you already have programmer. Please send me dump from working system, unedited. This means if you are booting OK now, reflash stock BIOS using stock method, so BIOS is clean without any edits.
Then load optimized, save and reboot back to BIOS, then disable secure boot, TPM, and remove any BIOS password. Then shut down, dump the BIOS using colibri and send to me.
I will then see if I can find and remove the lock causing 167, if not, I will just do the menu edit/unlock for you manually so we can see if AMIBCP is breaking something, or if there is some auto-BIOS-Recovery going on here or something. << If that, not sure we can get around, unless you can find chip containing what it's using as backup to restore from.

@Lost_N_BIOS

I tried import back modified NVRAM.txt file, then I reboot computer. When I see Acer logo, the computer automatically reboot again. The behaviour is the same as I change NVRAM value in the RU. The FPT still reports error 167 when I use it in the Windows.
I guess this BIOS has some kind of protection? If the important value in NVRAM get changed, it will automatically restore it in next reboot.

Is there anyway to around it? Like, change the value related to the onboard graphics directly without unlock BIOS.

I am still waiting for my flash programmer.

@Black-Xstar - Sounds like some auto-recovery, not protection, otherwise it would not be able to reset the value to original.
Check the board on both sides once you programmer arrives, then dump all SOIC8 chips you see, give me their ID's too, in case I need to tell you to use certain software/version to dump

You can try changing only the graphics option you want to change, using RU method, then reboot and see if it's changed back.
It's located at >> Onboard Graphics Controller, VarStoreInfo (VarOffset/VarName): 0x12D, VarStore: 0x16 << = SaSetup @ GUID - 72C5E28C-7783-43A1-8767-FAD73FCCAFA4
00 = Disabled
01 = Enabled

Or, you can also try making the change in SCEWin and see if same too. To edit this, open your original NVRAM.txt dump, find that setting and move the asterisk as it mentions, then flash it back.

// Setup Question = Onboard Graphics Controller
// Token =CE0 // Do NOT change this line
// Offset =12D
// Width =01
// BIOS Default =[00]Disabled
// Options =*[00]Disabled // Move "*" to the desired Option
// [01]Enabled

Change to
// Setup Question = Onboard Graphics Controller
// Token =CE0 // Do NOT change this line
// Offset =12D
// Width =01
// BIOS Default =[00]Disabled
// Options =[00]Disabled // Move "*" to the desired Option
// *[01]Enabled

Then after reboot, dump again and check to see if it's back to original. If it is, then we may either have to use programmer to make changes, or have to find the backup it's using to recover and make the changes there first

@Lost_N_BIOS

I already tried that, both RU and SCEWin, to modify 0x12D @ SaSetup.
It doesn't work. System automatically restore it at next reboot.

So my last hope will be the programmer! Is it possible that programmer will not work in my case?

Thanks.

@Black-Xstar - Sorry to hear it! If you cannot find the backup chip on the board, then yes, programmer may not matter. Show me image of both sides of the board
Are you sure you do not have secure boot enabled, or a BIOS password set? If not, then yes, there must be some kind of auto recovery going on here, and for that there would need to be a secondary chip with a backup BIOS on it.
!! Try this !! Remove the hard drive, and test making those changes again and see if they stick or not. This is to check to be sure there is not a hidden BIOS image stored on the hard drive.
If the settings then remain without hard drive, but get reset after you put the drive back, then we know the backup is there, then we can find and remove!

@Lost_N_BIOS Some mother pics:

@Black-Xstar - Please put all those in a max compressed zip, I'm on limited internet, thanks
Also, please boot to RU and show me all the variable GUID's you can see, looking to see if you see "SystemAccess"
I don't see it dumped in your BIOS dump NVRAM, but it should be there, possibly due to your current user access level it's hidden from the OS access, and this may be why we're at a stand still here for now.
With programmer, we can do it all directly, and change this too. But, hopefully you can see this in RU. If you can, go into it, and show me what you see at 0xD32, if 01, change to 00 and then reboot and see if that sticks. If it did, then retry the other variable changes and see if they then stick too.

@Lost_N_BIOS

I am sorry, I am not longer having this PC due to unexpected factors.
I am moving to Lenovo tiny series now, I hope I can have a perfect hackintosh.

The programmer is still on the way, I will keep it for the Lenovo.

I remember I saw 0xD32 = 0x01 and changed to 0x00, but again the system restored it after reboot

Thank again for all your help!

@Black-Xstar - Please explain, what happened???

@Lost_N_BIOS I realize I need save money. So I returned Acer and AMD graphics card. Then, I bought a cheap Lenovo (no graphics card) instead.

@Black-Xstar - Ohh, OK, I hear that! Well, start a thread for the Lenovo, if there is not already one here for your model. We may be able to flash in unlocked BIOS for that without programmer and all these hassles.
IF I can unlock it's BIOS, some Insyde BIOS kick my butt

I found this thread looking up to enable the igpu with this Acer.

My hackintosh is running fine but I would like to enable it to get DRM and everything else working.

I'm a noob in the bios editing world but i will do my best. What do you need from me @Lost_N_BIOS ? :)

@Benlehot - Do you have flash programmer like CH341A + SOIC8 test clip with cable? If not, order a set now, let me know if you need linked examples.

@Lost_N_BIOS no but I will buy one. Is this what we need ? https://www.amazon.ca/KeeYees-SOIC8-EEPR...00262589&sr=8-8

Edit: I tried to use RU.efi. I booted in the editor but I was not able to find the value to change. Here's what I did

ALT + C to select UEFI Variables
Select SASetup
Tried to find the value 0x12d but I couldn't find it.

What did I do wrong?

I'm not using the original Hard drive in the computer so I wanted to give it a test since you said it could be some sort of recovery on the hard drive.

Thank you!