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

[HP_ENVY_User_32]

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.

I purchased a Pomona brand clip which seems to work much better. I am no longer experiencing the issue where the BIOS flash file differs from the readback. The only problem is that now I dont have a working version of the bios since all the flashes/reads were corrupted by the faulty clip.

The only file downloadable from lenovo is this:
https://support.lenovo.com/us/en/downloa...-edge-e545

Unfortunately this is a .fl1 file which seems to be compressed. Is there a way to get the correct rom from that fl1 file that you know of?

[Maxinator500]

The only problem is that now I dont have a working version of the bios since all the flashes/reads were corrupted by the faulty clip.

Lenovo E545 BIOS dump.
Source.

[HP_ENVY_User_32]

The only problem is that now I dont have a working version of the bios since all the flashes/reads were corrupted by the faulty clip.

Lenovo E545 BIOS dump.
Source.

Thanks for that bios dump. With that, I was able to successfully flash the un-patched bios & the machine booted perfectly.

I next used your automod script on the working bios, and again was able to flash successfully!

Upon entering the bios, the only new parameters I am seeing is the ability to view the SMbios log, which just details the booting history of the device. See here for what I am seeing: https://imgur.com/a/u94n0xM

Was this the intended result of the patch? When browsing the Hii modules of the bios it appears that there are many more advanced options than just the ability to view the SMbios log.

[Maxinator500]

Was this the intended result of the patch?

No. Although the AMD menu unlock patch didn't work, I know a guaranteed way. I will prepare another archive soon.

[Maxinator500]

Done.

Automatic patching script

With this, you will be able to access hidden menus via the Main tab of BIOS.

[HP_ENVY_User_32]

Done.

Automatic patching script

With this, you will be able to access hidden menus via the Main tab of BIOS.

I just flashed this and am not getting any display. The fans start and stay on at normal levels as if it has successfully booted into the os, however I only see a black screen.

Did any of the patches that were just applied modify the vbios in any way? Or perhaps the LCD controller?

As a side note, the first patcher you sent disabled my trackpad and trackpoint when flashed, though the rest of the PC worked fine.

Additionally, each time I flash I have verified that the data on the EEPROM is the same as the bin file that was flashed, so that is no longer the issue here.

When you are making these patches, are you basing them off the original rom I sent you? If so, I would stop doing so as that ROM was corrupted by the poor clip of my CH341A. When comparing that rom I originally sent to the working dump you sent, there are many differences which I assume could cause issues if you are basing your mod off my original corrupted dump. I would base any mods off the bios dump you recently sent as that’s the only one that had worked when flashed back.

[Maxinator500]

Did any of the patches that were just applied modify the vbios in any way? Or perhaps the LCD controller?

No.

As a side note, the first patcher you sent disabled my trackpad and trackpoint when flashed, though the rest of the PC worked fine.

That's odd.

When you are making these patches, are you basing them off the original rom I sent you?

Now I understand why. Of course they were of different versions and their modules are also slightly different: there is a 20 byte displacement in module of "Main" tab. I've updated the script so now it is intended for the latest BIOS version (1.18).
Listen, since I know which BIOS dump works for you, you can continue by using its modified variant and flash it directly without paying attention to the script I made. The finished BIOS mod for you: HP_ENVY_User_32.zip.

[HP_ENVY_User_32]

Did any of the patches that were just applied modify the vbios in any way? Or perhaps the LCD controller?

No.

As a side note, the first patcher you sent disabled my trackpad and trackpoint when flashed, though the rest of the PC worked fine.

That's odd.

When you are making these patches, are you basing them off the original rom I sent you?

Now I understand why. Of course they were of different versions and their modules are also slightly different: there is a 20 byte displacement in module of "Main" tab. I've updated the script so now it is intended for the latest BIOS version (1.18).
Listen, since I know which BIOS dump works for you, you can continue by using its modified variant and flash it directly without paying attention to the script I made. The finished BIOS mod for you: HP_ENVY_User_32.zip.

I just flashed the file attached and got a black screen again. I noticed in the BIOS that there was a version mismatch between the BIOS firmware and the EC firmware, so I flashed back the working BIOS in an attempt to run Lenovos BIOS update software which also updates EC firmware, however upon flashing back the original BIOS the keyboard and trackpad do not work anymore.

The keyboard actually does work inside the BiOS menus, however it does not work in the OS. I have reinstalled the OS and tried every driver I can find online, but nothing will get the keyboard or trackpad to work inside windows. Any idea what’s going on here?

In summary:
None of the patched BIOSes will allow the computer to boot with any display.
None of the non-patched BIOSes (even the ones directly from Lenovo) allow the keyboard or trackpad to function inside the OS, however the keyboard does work in the BIOS.

Is this something you have ever experienced? If so are you aware of any solution to this? For a while, both devices appeared in the device manager in windows, however neither was functional and soon after they disappeared from the device manger.

[Maxinator500]

Is this something you have ever experienced?

I only experienced keyboard issues when I forcibly installed the wrong driver. But it looks like your problem is of a different nature, for which I do not have a solution.
Have you checked if keyboard works on a freshly installed system or in Windows Live USB?

[HP_ENVY_User_32]

Is this something you have ever experienced?

I only experienced keyboard issues when I forcibly installed the wrong driver. But it looks like your problem is of a different nature, for which I do not have a solution.
Have you checked if keyboard works on a freshly installed system or in Windows Live USB?

I have reinstalled the OS, and it still does not work. They also did not work inside the installer USB and I had to use external peripherals.