Try everything exactly as mentioned in post #27, then give me both logs

Hi! After renaming the 8MBCut file to BIOS.fd, I get the following error: "It only supports to flash secure BIOS on current platform. The image to be updated is not a secure BIOS." I noticed that, after running the program, a text file called FlsHook.txt appears, so I guess this might be the log file you are looking for. I didn't find anything in the Temp folder though.
Edit: Oops, sorry, I know discovered a text file called H2OFFT, and I guess this is what your're looking for.

Did you get a log from the BIOS.fd flash attempt or not? Log file will be named H2OFFT.log, and will either appear in that folder you run from, or the temp folder I mentioned (May be in randomly named folder in temp, search for H2OFFT.log, or dump temp before you do it, then look in what is there after)
As for the error you mention above, when do you see that, before reboot or after reboot on that black update screen?

What is in the flshook.txt, upload for me or copy here in a spoiler tag.

* Edit, please show me an image of this error, I need exact wording so image will be best, thanks

I uploaded the two log files in the post above. This is the content of the flshook.txt file:

[08/19 09:33:36] OnEnableHook()
[08/19 09:33:36] Save Power Button Configurations
[08/19 09:33:36] LidAcIndex: 1
[08/19 09:33:36] LidDcIndex: 1
[08/19 09:33:36] PwrButtonAcIndex: 1
[08/19 09:33:36] PwrButtonDcIndex: 1
[08/19 09:33:36] SleepButtonAcIndex: 1
[08/19 09:33:36] SleepButtonDcIndex: 1
[08/19 09:33:37] OnDisableHook()
[08/19 09:33:37] OnStopAp()
[08/19 12:20:11] OnDisableHook()
[08/19 12:20:11] OnDisableHook() - skip
[08/19 12:20:11] OnStopAp()
[08/19 13:18:39] OnDisableHook()
[08/19 13:18:39] OnDisableHook() - skip
[08/19 13:18:39] OnStopAp()
 
 

As for the second error, it occurs before restarting, and the application closes. With the first case (the original BIOS.fd file you sent me), I get the error after restarting.
Edit: I attached the photo with the second error

Thanks. See my edit above. FlsHook.exe and that log looks like it's for the power scheme enable/disable, to unlock something and allow that EC Update, nothing we're dealing with
Sadly, I'm not finding error, invalid, or even "Secure BIOS" in the usual files I would edit for this error, so either it's using file within the onboard BIOS for this, or they've removed the textual descriptions for the error in the iscflash.sys files, I'll keep looking
I'll look in H20FFT itself instead, since that is a pre-reboot error, maybe it's stopping it instead of the .sys file that usually does. Anyway, I will keep looking and let you know, thanks for the image.

I see error #4 in log2, which file did you try to flash then? This is version compare check, if it finds same version then it stops, I disabled this, but maybe I missed an instance, or as mentioned it may use the ini from the onboard BIOS
Once I know which file I will double check it. I also see this may be EC Part check version fail, but I doubt it's that.

The other log file has 4 attempts in it, so I need these to be redone one at a time, log removed and renamed between each, so I have a clean log of a single instance for each BIOS file, and a single flash attempt only, from the package and method I outlined in post #27

Zitat

---

I see error #4 in log2, which file did you try to flash then? This is version compare check, if it finds same version then it stops, I disabled this, but maybe I missed an instance, or as mentioned it may use the ini from the onboard BIOS

---

The log2 text file is the renamed 8MBCut.fd file. The other one is the original BIOS.fd file you sent me in the same archive. In 5 minutes I'll sent you the new log files.
Edit: uploaded new log files

Thank, one of those original logs you sent had many log entries, so I couldn't be sure what was what. I think I missed something in the settings.
Here, try this, and if it fails, then I will enable the settings option interface for you and you can then show me what all options the tool allows you to configure aside from what I am changing in platform.ini

Please try replacing platform.ini (two are included in this file). First, replace edited one in there now with this new one, then after first test rename platform2.ini to platform.ini for second test, replace first one with second after first test
Delete all logs before these tests, after test one, save log and delete, so second test log will be new and only contain those results.
For this test, use the 8MBCut BIOS, renamed to BIOS.fd
http://s000.tinyupload.com/index.php?fil...585877360568650


* Edit - Secondary test, stock files only here, except I edited platform.ini to enable ME FW reflashing only and disabled BIOS flash + logging enabled. And I cut to 8MB BIOS, since there is a in-BIOS ini file that would be used otherwise, and if I edit that in place it would be signed BIOS that would have broken signature
I am not sure how this ME flashing option works on Insyde BIOS, but ME REflash is our goal, hopefully it's using this ini file and not one in onboard BIOS
After testing this, especially if you see some ME Updating process or "BIOS Flashing" please check ME via MEInfoWin -verbose and show me image of entire report or text of report in spoiler tags
http://s000.tinyupload.com/index.php?fil...400494971885729

Hello! Here are the results!

Zitat

---

Please try replacing platform.ini (two are included in this file). First, replace edited one in there now with this new one, then after first test rename platform2.ini to platform.ini for second test, replace first one with second after first test
Delete all logs before these tests, after test one, save log and delete, so second test log will be new and only contain those results.
For this test, use the 8MBCut BIOS, renamed to BIOS.fd

---

For this test, I still get this pesky message: "It only supports to flash secure BIOS on current platform. The image to be updated is not a secure BIOS." I am not entirely sure, but maybe there is a problem with the fact that I've changed the extension from .bin to .fd, as the 8MBCut isn't a .fd file.

Zitat

---

* Edit - Secondary test, stock files only here, except I edited platform.ini to enable ME FW reflashing only and disabled BIOS flash + logging enabled. And I cut to 8MB BIOS, since there is a in-BIOS ini file that would be used otherwise, and if I edit that in place it would be signed BIOS that would have broken signature
I am not sure how this ME flashing option works on Insyde BIOS, but ME REflash is our goal, hopefully it's using this ini file and not one in onboard BIOS
After testing this, especially if you see some ME Updating process or "BIOS Flashing" please check ME via MEInfoWin -verbose and show me image of entire report or text of report in spoiler tags

---

Regarding this test, I get an interesting result: the fans start to kick in but, eventually, I hit this error: "Warning: Current ME Region does not have R/W rights".
For both tests, I've attached the log files. Thank you for help!

It's nothing to do with the BIOS extension, don't worry, fd/bin/rom all same. This is due to I cut out the security capsule info and the internal ini, since we are tying to flash in a mod BIOS eventually to then allow ME re-write
I think by default, it's pulling the ini info from the onboard BIOS, not using the changes I'm putting in, however, we'll go back to this later after below test, because there is one or two more settings I can change in regards to this, before we would confirm it's not using the platform.ini we're giving it.

Good, interesting result on the last test there, maybe for this method, we can use original uncut BIOS.... But, I think we need to get FD unlocked first for that, this is what it's saying NO about.
Please try same again on the ME last package, replace first with the platform.ini not in a folder, then try and see what error you get. Then if same, or similar error, replace that platform.ini with the on in the FD folder, then flash, if it's successful that means we unlocked FD (Flash Descriptor, this is what locks a lot of things down)
If the FD flash goes over successfully, go back and try the BIOS/ME and platform.ini I originally packaged together as mentioned at post #37
http://s000.tinyupload.com/index.php?fil...148004665173841

Hello! Sadly, after replacing the platform.ini file in the ME package with the ones you last sent me, I get a new error: "Warning: Current DESC does not have R/W rights". I have attached both a screenshot and a log file that resulted from the H2OFFT utility. Thanks for help!

Does that apply to both ini files I sent you at post #39? If yes, then it's not using those INI's, and is reading one in onboard BIOS and it's FD.

You will need flash programmer + SOIC8 test clip w/ cable, or send this system back for RMA. Whichever sounds best to you.
Or, you can do Pinmod (E1 short) linked previously

hello @Lost_N_BIOS,i have the same laptop，i want to unlock the advanced menu in bios.
here is the bios dump by flash programmer:
https://mega.nz/#!KhU2gITJ!Xc9VAZ2XdtsH9...KE08TocEpUiq6qM

i also tried to modify by myself, but the laptop would not to boot by using mine modifed bios.
the bios that modified by myself:
https://mega.nz/#!3pE2EYjJ!OLDCoF0cAeQqc...UMOBOBAE_oUeJ_w

Could you help me.

thanks in advance.

Hello @Lost_N_BIOS! Thanks for your answer. It seems like we got to an end with my Me Region recover project. I will contact Lenovo next week and, depending on what they say, I might send my laptop in for a RMA. If they refuse to fix it for free, or offer to change my motherboard at extra charge, I will notice you in order to try to attempt to fix the problem by using a flash programmer. Thank you a lot for involvment and for help, and sorry I wasted your time trying to help me fix the problem!

@marianFCBT - Sorry we could not fix easily, without a programmer, sometimes it's just not possible, and I'm not the greatest at messing with Insyde BIOS stuff (so could be I just didn't figure it out too) If you get programmer we can fix it all.
Don't let them tell you that you need a new system or a new motherboard, all you need is BIOS reprogrammed fully and properly. It's not a waste of my time, sorry we couldn't get it, but it's OK, if you get a programmer we can fix!

@zhbchwin - please repackage those into a single archive and upload to some other free host, Mega has been failing to work for me for over a month now, only blank pages
Never mind, I guess they heard my complaints finally, at least for now, after 10 minutes of trying they finally loaded! Fail, both stall at 95% and wont resume = Mega is rubbish
Finally, half hour later, I got both files

* Edit - please run MEInfoWin.exe -verbose
Show me end of report, we're looking for Measured and Verified Boot, are either enabled on the left/FPF side? If yes, BIOS cannot be unlocked, due to Intel BootGuard active and protecting the volume that needs modified.
That may be why your mod failed, but I'm not sure. I also didn't check what all you edited or how etc because I saw this first so need to check this before looking at anything else, the buck stops here first.
However, I did check the module you are supposed to be editing (Setup PE32 Body), and your mod BIOS and stock BIOS match, so you didn't edit correct module. What did you edit, and how, with what tools etc?

@Lost_N_BIOS hi, sorry for the late reply. because the laptop can not boot. So I contacted lenovo, and they fixed it by changing a new motherboard.
And here is the report of the new motherboard.

I actually did something wrong, because I did not know how to edit the bios. I just modified one byte according to the diff of someboy posted orginal bios and mod bios.

Btw,I want to unlock the bios's advance menu, aiming to modify some thunderbot configurations. unfortunately the setup_var2/setup_var_3 seams to have no efforts.