Sorry to hear the last BIOS I sent didn't work either . Good you found 2.11 dump, and good it works on your system too! Great you updated to 2.18 already too. Now, send me dump from programmer off your system with 2.18, then I can see about putting back in your correct info.
Once connected, as in, once you can read it properly with any software, leave it connected and don't move anything around. Then you can dump, no need to keep reclamping once you are connected and detectable.
Ahh, I see you got it finally. So FPT dump of complete and working 2.18 BIOS from your system? If yes, great, I will check it and then we can just FPT flash.
If BIOS lock or SMI/SMM lock enabled, you'll have to use grub/setup_var or H20UVE or program once more with those locks removed, so you can fully write anytime with FPT (FD locks aren't the only possible locks).
Or, did you already test complete FPT Dump (FPTw.exe -d FileName.bin) and then flash it back (FPTw.exe -f FileName.bin) And it flashed back? If not, please test that now and if you get error, stop, show me the error, and do not reboot yet

* Edit - how did you "update" to 2.18 from 2.11? I've not checked the 2.11 dump yet, but the last 2.18 FPT dump you posted is missing an NVRAM volume (EVSA), so looks like built on top of incorrectly flashed 2.11 or 2.18 (FPT or programmer flashed stock BIOS instead of actual dump)
At least it's working for you though * Edit, yes, this is the problem, the original 2.11 dump you started on is not a properly dumped BIOS. This was incorrect flashed (however) to stock 2.11, then dumped. So, now you are here

So, what is your goal from here on out, provided I do not need to further unlock BIOS settings mentioned above?

For your bios, I tried two programming to be sure but without success, so I looked for alternative bios it was not obvious but my system is based on the same basis as other references that use the same bios, which is not obvious to know at Acer unlike HP.


The FD lock is not the only one, indeed I confirm that there is another lock:
FPTw.exe -f FileName.bin
returns the following warning and error:

PDR Region does not exist
GBE Region does not exist

Error 28 : protected range registers are currently set by bios, preventing flash access. Please contact the target system vendor for an option to disable protected range registers.

Do you know what the "PDR" is ?



2.11 to 2.18 :

In the beginning, the system was delivered with an original BIOS 2.xx and then updated to 2.18 with the normal procedure.

With the external programmer I made a backup of 2.18 but the latter is faulty and there is no NVRAM information (UUID...), (on this subject I wonder if my external programmer is not faulty, maybe there's protection or I don't know what, but it doesn't make sense) , and I had to decide to use 1.22 because my backup is 2.18 broken, but since I found a dump 2.11 :

then :

I opened 2.11 on HxD modify the values here (FD Unlocked)
I programmed 2.11 unlocked, externally.
In Setup 2.11 switched from AHCI to IDE and from UEFI to Legacy
Started live xp and launched the command (process to 2.18) :

WinFlash32.exe /bcp /sd /cvar /v /endkey /silent /bbl /cac /cbp 30 /file %UMAROM%

(without /ver)

I restart manualy

The update screen appeared (TDK OEM updater...) it was very short, the system stopped.

at restart I am 2.18 unlocked = extraction is possible.

(formerly I tried with /force but this erases the UUID/Tracking in the 2.18)

--
The objective of benefiting from a BIOS in its flashable version and the other programmable version :

In its latest version 2.18
Including microcodes updates.
Including the latest ME Blog and clean it .

Disable ME and delete it.

Allow visibility of the hidden options in bios 2.18 (but I don't have the information to do so, even if there are few options).

UUID and tracking information has not made the system unstable since 2.11.

What other improvements could be made

I thought they may not work, was only hoping we could get lucky.

PDR = Platform Descriptor Region, this is not used in your BIOS
GbE is Intel Gigabit LAN (MAC ID stored here, when this LAN is used and this module in BIOS) - this not in any of the BIOS I've looked at for your system either, so must be using Non-Intel LAN, or Intel LAN that's only FAST LAN not Gigabit LAN

Error 28 - FPRR/PRR - Flash Protected Range Registers is a lock sometimes that can be enable/disable in BIOS settings (like BIOS lock), other times a BIOS mod is required to remove it (bypass it) in an internal BIOS Module (often PCHInitDXE or Powermanagement, but I'll have to hunt it down in this BIOS)
On this, before I do anything, just like you disabled BIOS lock, please disable SMM lock >> 0xC4
You may need to change two values (unsure which you used before for BIOS Lock, RU or grub/setup_var)? After that, try FPT flash again and see if you get same error or different.
SMM LOCK, VarStoreInfo (VarOffset/VarName): 0xC4, VarStore: 0x1, QuestionId: 0x1C8, Size: 1, Min: 0x0, Max 0x1, Step: 0x0 {05 A6 3A 02 3B 02 C8 01 01 00 C4 00 00 10 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00}
Default: DefaultId: 0x0, Value (8 bit): 0x1 {5B 0D 00 00 00 01 00 00 00 00 00 00 00}
Default: DefaultId: 0x1, Value (8 bit): 0x1 {5B 0D 01 00 00 01 00 00 00 00 00 00 00}
One Of Option: Disabled, Value (8 bit): 0x0 {09 0E 03 00 00 00 00 00 00 00 00 00 00 00}
One Of Option: Enabled, Value (8 bit): 0x1 {09 0E 02 00 00 00 01 00 00 00 00 00 00 00}

If you never did disable BIOS Lock previously, sorry I maybe got confused here. We want both BIOS Lock and SMM/SMI lock disabled in your base BIOS.
Anyway, if you never disabled BIOS lock before, let me know, and I will do both in the BIOS instead and send to you for testing

I knew you originally had 2.xx BIOS. Your original dump of 2.18 BIOS is corrupted, not valid dump, this is the only issue here. No protection, just a bad dump is all.

Disable/delete ME is not suggested, this will cause fans to run at 100% and likely other stuff to fail or work improperly as well (CPU multi, memory multi, etc)
If you want to carry on from where you are now with 2.18 - I can update microcodes and ME if you want, I will see about unlocking (I hate Insyde BIOS, so no promises and this may take some testing/fail/brick/recovery/testing/repeat to find exact unlock for the menus)
I can also try to find and bypass the PRR lock for you, this may require the hassle I mentioned above with Menu unlock too, but sometimes I can find this much easier than menu unlock.
Is your LAN MAC ID in there/working, check Ethernet cable connected and see if you get internet or not.


* Edit @Kjose - Here is large set of BIOS to test, this is to test getting around the lock at FPT flash from within windows. Program each on, then reboot to windows, and try to flash BIOS via FPT.
Let me know if error same or different for each one. You can stop testing at the first one that allows the flash, let me know which one it is.
These all built from VA410218viaFPT.BIN as base, no other changes for now except to see if we can get around error 28.

!!! I Almost forgot, some BIOS have a bug that can get around sometimes!!! Please test now, put system to sleep (S3 sleep) for one minute, then wake it up and try to FPT flash again.
If no luck, carry on with below, or if luck, you can still carry on with below if you want to get it removed from BIOS anyway.

1. SetOnly.bin *
2. PCHIOnly.bin **
3. PCHBProO.bin
4. PCHIBproB.bin ***
5. 12.bin (1+2) ****
6. 13.bin (1+3)
7. 14.bin (1+4) ****

* = I think, higher changes of success - But please test all (And in order listed) if you don't mind.
Unless you run into one that works, then stop there, no further testing needed, and shouldn't be wasted time trying more after find success
http://s000.tinyupload.com/index.php?fil...540481320486575

Thank @Lost_N_BIOS, Indeed, apart from the FD unlocking I have not yet tried to disable the BIOS lock and SMM/SMI lock but I see that BIOS offers BIOS for this purpose.

By the way, this is a BIOS named "Phoenix SecureCore Tiano", You can try unlocking the menu "VT-X virtualization" (just this menu if it is available), VT-X which is enabled by default but which should be suggested to be sure it is active or not, however it's just if you think you can make it happen, and if you think it's easily, otherwise it's not essential and if yes it's just for a few tests...

Yes I confirm the LAN MAC ID is functional.

I tried the S3 and S4 standby mode and no anomalies to report: each time well awakened.

So I programmed every BIOS in the order of the list, however none of them allowed to work around error 28 with fptw.exe -f fileName.bin

1. SetOnly.bin *
2. PCHIOnly.bin **
3. PCHBProO.bin
4. PCHIBproB.bin *****
5. 12.bin (1+2) ****
6. 13.bin (1+3)
7. 14.bin (1+4) ****

Unlocking methods have apparently changed ?

Disabled and/or deleted ME remains optional, if you agree to update the microcodes and ME this will be an opportunity for me to test faster the different software which does not seem to be good indicators on Meltdown and Spectre vulnerabilities (among others).

@Kjose - BIOS Lock + SMM/SMI Lock would need disabled to FPT flash, I didn't check during this comment if they both are enabled by default, but I see above I did check on SMM/SMI and it's enabled and needs disabled first.
I checked, BIOS Lock is disabled by default, so you should only have to disable SMM/SMI lock, but then may also need the edits done I made above in that x7 BIOS test package.

Yes, I can make settings visible for you that are hidden. I'm not sure what you mean there on your VT-d comments
Intel(R) VT for Directed I/O(VT-d) is in your BIOS (System Agent (SA) Configuration page), and may be grayed out (can't tell on my end). Setting itself is enabled by default
Intel(R) Virtualization Technology is in your BIOS as well (Processor Config page), same as above, may be grayed out I can't tell. Setting itself is enabled by default

S3 sleep was not something you needed to test. This was a test for BIOS bug that gets you around the FPT/167 or 28 error. Put system to sleep S3 only, wait one minute, then wake system up and try to FPT flash the BIOS region via your FPT backup.
Some BIOS have a bug, where you normally get 167 or 28 FPT error, putting system to sleep for one minute then wake it up and this error does not happen. Hope you get what I mean now

You are hitting error 28 possibly due to how you are using FPT. You only need to flash the BIOS region, so should only be using the following command >> FPTw.exe -bios -f filename.bin
FD is already unlocked and programmed in, so no need to write FD or ME right now, so FPTw.exe -f biosinfull.bin is not needed. Only BIOS region flash is required for mod BIOS, and you unlocked ME at the FD, so anytime you wanted to reflash the ME only that can be done via >> FPTw.exe -me -f me.bin
So, now, all tests will need redone on each BIOS. But, first try to FPT flash without doing anything, on stock BIOS, if you get error 28, then do S3 sleep check, then if no luck still, reflash all those BIOS I made and try again with proper FPT command.

If no luck still, then programmer only for now

I don't think disable ME is a good choice, especially in a laptop, but it's your system Yes, I can update the microcodes again.. once all settled.
You have a programmer, so aside from convenience to flash via FPT, this is a lot of hassle for no real reason. However, I do think once you use one of the BIOS above with SMM lock disabled (ie BIOS #1) you will be able to flash BIOS region via FPT

Regarding the unlocking of BIOS menus, I wanted to mention the activation setting of the Intel Virtualization technology, I also confirm that it is enabled, but it is not visible at all in the BIOS or even grayed out.
Knowing the status of features from the BIOS menu would be great, being able to change the status of the most important ones even better .


Thank you @Lost_N_BIOS for the clarification regarding the S3 sleep mode and error 28, because indeed my interpretation was not subtle enough , now I understood .

The last of your scheduled BIOSes was number 7. 14.bin (1+4) **** on the list
I tested S3 and then typed FPTw.exe -f 218FPT.BIN

I confirm that Error 28 no longer appears., instead I get the following error:

Error 103: There are not supported SPI flash devices installed. Please check....

I then programmed the BIOS VA410218viaFPT.BIN with the same procedure and again I omit error 103 : Is it useful for me to test all BIOS x7 pack ( 7. 14.bin (1+4) since already done ) anyway


Let's put aside the deactivation and deletion of ME for now and focus on the things that really work for the final(s) BIOS.

@Kjose - sorry for delayed reply here, I had this tab open but thought I was waiting on your reply until I refreshed again tonight

So, you tested all BIOS 1-6 and no change, then #7 you get error 103?

I don't know what you programmed via FPT when you said this >> "BIOS VA410218 viaFPT.BIN" But you shouldn't be doing any stock BIOS flashing with FPT, if that is a stock BIOS.

For error 103, sounds like the fparts.txt file does not include your actual BIOS chip ID. Please run this command and show me image of the output >> FPTw.exe -I
Then tell me what ME System Tools package and version you are using FPT from.

S3 sleep bug has nothing to do with any of the BIOS I send you, this is something you test in general once to see if your BIOS has this bug or not. If it does not, then that is all.
If your BIOS had this bug, you would resume from S3 and be able to FPT flash without any errors, on the stock BIOS even, due to a security bug. Since you've never been able to do this, all done there, your BIOS does not have this bug, forget about it now

@Lost_N_BIOS No worries about the delay and thank you again

In order to follow up :

"FPTw -I" is concluded with "FPT Operation Passed" and I use Flash Programming Tool. Version: 8.1.51.1476 from Intel ME System Tools v8 r3.

I confirm error 103 with all the BIOS 1-7 & VA412018viaFPT.bin which as a reminder and from the 2.11 FD unlocked + the update 2.18 is unloaded with fpt -d FileName.bin

I that VA412018viaFPT.bin is a good and correct basis to update IME clean/secure and microcodes for a version via external programmer, what do you say ?

@Kjose - FPTw.exe -I should show you "information" that is what the -I flag is, I wanted to see this information (ie show me an image) before I can reply further about the 103 error.

I am now lost, on everything! I do not understand what this file is >> VA412018viaFPT.bin
And NOW, it's VERY unclear your testing results from above about 1-7 BIOS I made you for testing (here, you contradict what you said above at #21, or that info is not clear)
BIOS 1-7 have a specific goal in mind, and that is the only goal (passing error 28), and we stop testing at whatever BIOS reaches our goal and then you let me know what # BIOS that was (Goal was to get past error 28 only)
Now, please clarify for me which BIOS of 1-7 FIRST did not show you error 28?

@Lost_N_BIOS That the attached image sums it all up

notes :

- 218.bin (aka VA412018viaFPT.bin) is the dump previously done with ftp -d FileName.bin and the result is the same with all BIOS from 1 to 7: after S3 there are no more errors 28, only error 103 persists .

-I am obliged to perform S3 otherwise error 28 remains regardless of the BIOS (218.bin and the series from 1 to 7).

Now, I guess this error 103 is now the cause that does not allow flash... why ? I don't know .

So, with BIOS #1, error 28 is gone? If yes, then that is only BIOS that ever needed to be tested, I mentioned this when I gave you those BIOS, stop once error 28 is gone.
S3 is not required for anything, I mentioned that as a simple thing for you to test once, to see if your BIOS has this bug, it does not, forget about this now.

Ohh, so confusing! Mainly because you are not following my directions, doing stuff I didn't mention to do, then mixing those results in with results I'm waiting to hear from BIOS tests I send you.
VERY confusing

SO.................... It does look like your BIOS has the S3 bug, not sure why you didn't tell me this when I first asked you to test it!
There is no need for you to test any 1-7 BIOS, or for me to mod and make those, your BIOS has S3 bug

Does the folder you are running FPT from contain fparts.txt? If yes, OK/Good.
Replace that fparts.txt with this one and try again using any BIOS after S3 resume after one minute - http://www.filedropper.com/fparts

@Lost_N_BIOS Now we know that this S3 bug is unavoidable

The folder in which I execute FTPw contains well fparts.txt , I replaced the file with yours and (after S3 resume after one minute) unfortunately the result returns an error 103 .

S3 bug is a good thing, what do you mean unavoidable? Without it, you'd be out of luck and have to get a flash programmer.
Please wait, let me ask plutomaniac to check that fparts.txt for you, it should be working now since I've covered all bases for your chip ID, but maybe I missed something.

Plutomaniac Can you please look at the image in post #25 for BIOS Chip ID, and then check fparts.txt I made at post #26.
I added a few entries to V8 R3 fparts.txt from V9.1 R7, to cover all similar chips, but still getting FPT error 103
Thanks

Yes, it is inevitable to go into S3 sleep mode and that is good.

However, I wonder if it is possible to flash internally without first putting S3 into standby I think so because otherwise the FPTw tool has no purpose or what you call the S3 Bug is actually not a bug but a way (official and undocumented, which could have been another one) to switch the state of write flash permission.

Well, this is all speculation on my part ...