[Request] Lenovo E545 (AMD) TDP+Advanced Menu

[Maxinator500]

or do I need to flash directly with a CH341A?

This.

[HP_ENVY_User_32]

or do I need to flash directly with a CH341A?

This.

Why is it that one would need to flash it directly like that? Is it related to the following error I'm getting in WinPhlash?
'Corrupted Interface Descriptors in New BIOS file
Part Table Signature not found in the interface
Error Code -161'

I actually am getting this error regardless of which BIOS I load (modded or not modded)

[Maxinator500]

Is it related to the following error I'm getting in WinPhlash?

To the other error. It is difficult to debug flashing program if you are not the owner of such a device with UEFI Phoenix bios on board.
Please notice that WinFlash in bios update for Lenovo E545 works with .FL1 bios file. If your update steps are actually correct, then I don't know the source of the problem described.

[HP_ENVY_User_32]

Is it related to the following error I'm getting in WinPhlash?

To the other error. It is difficult to debug flashing program if you are not the owner of such a device with UEFI Phoenix bios on board.
Please notice that WinFlash in bios update for Lenovo E545 works with .FL1 bios file. If your update steps are actually correct, then I don't know the source of the problem described.

Is there anything special I need to do before flashing the new Bios with CH341A? Should I Remove the CMOS battery?

[HP_ENVY_User_32]

Is it related to the following error I'm getting in WinPhlash?

To the other error. It is difficult to debug flashing program if you are not the owner of such a device with UEFI Phoenix bios on board.
Please notice that WinFlash in bios update for Lenovo E545 works with .FL1 bios file. If your update steps are actually correct, then I don't know the source of the problem described.

When running your start.bat file, this is what I'm getting as a CMD output:
https://imgur.com/q7XMPRu
Is that what is supposed to happen? The text inside of patches.txt indicates that more lines of hex code should have been replaced than just the 2 replaced by the script.

All I did was drag the original ROM file into the folder and click start.bat, did I miss something?

Is there any way to flash this from within windows? Or is there perhaps a way to create a bootable USB? I'd really prefer not to use the CH341A if possible because if that bricks it I've never been able to recover a brick after using the CH341A.

[Maxinator500]

The text inside of patches.txt indicates that more lines of hex code should have been replaced than just the 2 replaced by the script.

No. There are literally two lines: the one for Advanced tab and the second for AMD tab. The third one is for whitelist disabling, but I set the hash sign in front of this line to disable its execution.

Is there any way to flash this from within windows?

We can get started, but it will take a lot of trying to create a patch that bypasses internal checksum integrity. Yes, checksum thing does exist, but it is intended only for the BIOS installation stage. I haven't disassembled WinFlash UEFI yet, but I've had success with patching WinFlash for EFI bios.
So you manage to install the original BIOS, or find it impossible?

[HP_ENVY_User_32]

The text inside of patches.txt indicates that more lines of hex code should have been replaced than just the 2 replaced by the script.

No. There are literally two lines: the one for Advanced tab and the second for AMD tab. The third one is for whitelist disabling, but I set the hash sign in front of this line to disable its execution.

Is there any way to flash this from within windows?

We can get started, but it will take a lot of trying to create a patch that bypasses internal checksum integrity. Yes, checksum thing does exist, but it is intended only for the BIOS installation stage. I haven't disassembled WinFlash UEFI yet, but I've had success with patching WinFlash for EFI bios.
So you manage to install the original BIOS, or find it impossible?

I managed to use the CH341A to read the BIos from the chip directly, and it seems the data on the chip is different than what I originally backed up. See attached for the two dump files.

I am concerned about these files not matching, what do you think the reason for this is?

Edit: Can I also disable the whitelist be removing the # in front of the WL string inside patches.txt?

[HP_ENVY_User_32]

The text inside of patches.txt indicates that more lines of hex code should have been replaced than just the 2 replaced by the script.

No. There are literally two lines: the one for Advanced tab and the second for AMD tab. The third one is for whitelist disabling, but I set the hash sign in front of this line to disable its execution.

Is there any way to flash this from within windows?

We can get started, but it will take a lot of trying to create a patch that bypasses internal checksum integrity. Yes, checksum thing does exist, but it is intended only for the BIOS installation stage. I haven't disassembled WinFlash UEFI yet, but I've had success with patching WinFlash for EFI bios.
So you manage to install the original BIOS, or find it impossible?

I just attempted flashing the patched version of the rom extracted from the EEPROM with the CH341A, and it bricked my laptop.

I attempted flashing back the un-patched rom that I dumped with the CH341A, still bricked.

I attempted flashing back the original rom that I dumped with the software backup, still bricked.

I am noticing that when I flash a rom to the EEPROM with my CH341A and then immediately dump that flash, the dumped rom is always different in the same places from the rom that was immediately flashed beforehand.

Do you, or anyone else know what is going on here? Why is the data changing automatically when flashing?

Edit: See attached for EEPROM datasheet

[Maxinator500]

Do you, or anyone else know what is going on here?

Maybe something wrong with your CH341A? So far, you have not been able to restore any of the bricked laptops.

I am concerned about these files not matching, what do you think the reason for this is?

Both copies of the bios were saved without errors. The reason why there are differences in them is that there are variables in the bios that can change during the device's operation cycle. For example, date and time.

Can I also disable the whitelist be removing the # in front of the WL string inside patches.txt?

Yes.

[HP_ENVY_User_32]

I don't think the CH341A is bad, but the clip that came with it certainly is not very good. I think I will invest in a better clip.

You misunderstand when I say that the files are not the same, I don't just mean a few bytes here-and-there have changed. In my case there are dozens of rows of data that had info when flashed but when re-dumped were replaced with all 'FF's

I think what's happening here is that the clip is slipping slightly during the flashing process and that is causing 'FF's to be written in cases when the clip had slipped.

What clip do you recommend for a CH341A? Looking online it seems like they are all cheap with poor reviews of their ability to stay on the chip.