Forum RSS Feed Follow @ Twitter Follow On Facebook

Thread Rating:
  • 1 Vote(s) - 1 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[-]
Welcome
You have to register before you can post on our site.

Username:


Password:





[-]
Latest Threads
[REQUEST] Lenovo G700 (7ACNxxWW) Whiteli...
Last Post: dukeeee
Today 09:42 AM
» Replies: 163
» Views: 103263
Dell 5285, bios 1.23.0 downgrade unlock
Last Post: drukman
Today 06:18 AM
» Replies: 0
» Views: 55
Rampage V Extreme Bios
Last Post: Stipularbirch
Yesterday 11:20 PM
» Replies: 1
» Views: 1245
[Request] HP 3300 Pro MT Bios Unlock/Mod
Last Post: manu69xyz
Yesterday 07:12 PM
» Replies: 36
» Views: 36034
[Request] Unlock the BIOS HP ProDesk 40...
Last Post: manu69xyz
Yesterday 06:57 PM
» Replies: 12
» Views: 13107
LG Gram BIOS modding
Last Post: Aqualung
Yesterday 11:20 AM
» Replies: 1
» Views: 152
[REQUEST] Huawei Matebook 14 Core Ultra ...
Last Post: Ikrom_1
Yesterday 10:52 AM
» Replies: 0
» Views: 153
[REQUEST] Lenovo B50-70 (9DCNxxWW) BIOS ...
Last Post: billibons
Yesterday 09:52 AM
» Replies: 75
» Views: 54537
Latest Sony VAIO SVS13A17GBB (SVS131 ser...
Last Post: mirroreduser
01-17-2026 03:54 PM
» Replies: 0
» Views: 161
[REQUEST] Sony Vaio VPC-EE (R0210Z5) Adv...
Last Post: qwertyu123
01-17-2026 11:44 AM
» Replies: 58
» Views: 37462
Foxconn P4M8907SA-RS2H Intel Core 2 Duo ...
Last Post: acquamaster
01-16-2026 04:20 PM
» Replies: 2
» Views: 240
[REQUEST] Lenovo G400S (7BCNxxWW) Whitel...
Last Post: RyzerLenovoG400S
01-16-2026 02:30 PM
» Replies: 219
» Views: 136351
Asus F80Q
Last Post: megvadulthangya
01-16-2026 02:30 PM
» Replies: 3
» Views: 6417
[REQUEST] MSI MS-16F2 Barebone BIOS Unlo...
Last Post: den384
01-16-2026 10:51 AM
» Replies: 4
» Views: 6665
[REQUEST] Lenovo G50-70 (9ACNxxWW) White...
Last Post: ploukop
01-16-2026 03:41 AM
» Replies: 250
» Views: 143054
[REQUEST] Lenovo Ideapad Z710 (7FCNxxWW)...
Last Post: SomePCUser
01-16-2026 01:47 AM
» Replies: 229
» Views: 184836
[REQUEST] Acer Nitro 5 AN517-54 BIOS Unl...
Last Post: alexandrmd
01-15-2026 10:56 AM
» Replies: 31
» Views: 13950
[REQUEST] Acer Aspire E1-531(G) BIOS Unl...
Last Post: 0rkan
01-14-2026 08:43 PM
» Replies: 103
» Views: 73490
ASUS TUF FX504GD BIOS Unlock Request
Last Post: steelray124
01-14-2026 02:15 PM
» Replies: 31
» Views: 14872
[REQUEST] Lenovo N580 whitelist removal
Last Post: Dudu2002
01-14-2026 04:09 AM
» Replies: 55
» Views: 32250

[REQUEST] HP Folio 13-1000 Series Whitelist Removal
#61
Did another test to try to understand what's going on:

1- Hashed the BIOS dump I took in my previous post (step 3).
2- Erased the BIOS.
3- Flashed the BIOS dump I took in my previous post (step 3).
4- Took another dump from the BIOS and save it to a different file.
5- Hashed the dump from step 4 and compared to the hash of step 1. They match so I know that the content of the BIOS is exactly the same.
6- Booted the laptop. Screen is on, but I only see a blinking cursor on the top left corner of the screen. Waited for a while but nothing happened seems stuck.
7- Powered off the laptop and took another dump of the BIOS and saved yet to a different file.
8- Hashed this new dump and compared it to the hashes from the dumps of step 1 and 5. To my surprise this new hash doesn't match with the other two.

Do you know why is it possible that on the first boot after flashing with the programmer the BIOS content change?
I didn't expect that to be honest.
find
quote
#62
(05-17-2021, 04:35 AM)fc7 Wrote: Do you know why is it possible that on the first boot after flashing with the programmer the BIOS content change?
This is a common thing that does not cause the cursor to appear in the corner of the screen. The content of the dump changes in variable areas and is subject to many factors, for example, after switching on, the timer starts counting. This is also saved in the dump, but the BIOS area remains unchanged.
find
quote
#63
(05-17-2021, 07:18 AM)Maxinator500 Wrote:
(05-17-2021, 04:35 AM)fc7 Wrote: Do you know why is it possible that on the first boot after flashing with the programmer the BIOS content change?
This is a common thing that does not cause the cursor to appear in the corner of the screen. The content of the dump changes in variable areas and is subject to many factors, for example, after switching on, the timer starts counting. This is also saved in the dump, but the BIOS area remains unchanged.

Thanks for the clarification.
Then I'm totally clueless on why taking a dump from a working stock BIOS, and flashing it again later on is not working and it's showing this behavior.
On the other hand flashing the BIOS update file always work.....
find
quote
#64
I just posted on another forum (https://www.win-raid.com/t8887f16-Can-t-...#msg144145) the problem I found when restoring a BIOS dump using the programmer (blinking cursor on the top left corner of the screen) and see if anyone can explain it.

On the other hand I wanted to ask you, which tool are you using to modify this BIOS, UEFITool, H2OEZE, Andy's Phoenix Tool something else?

In my case, for example when extracting module 91472655-50E0-4D81-9AF6-239E6F431B8C with UEFITool or H2OEZE I get a 1 byte difference in the extracted file, while I was expecting them to be exactly the same.

Sorry for asking too many questions I'm just trying to learn.

Thanks.
find
quote
#65
(05-18-2021, 12:46 PM)fc7 Wrote: On the other hand I wanted to ask you, which tool are you using to modify this BIOS, UEFITool, H2OEZE, Andy's Phoenix Tool something else?
To modify this bios, I used PhoenixTool because the replacement of modules can be done in bulk. UEFITool is also suitable, because you need the checksumm of each changed module to be recalculated and this tool does this automatically, but it does not know how to decrypt bios. H20EZE is not very convenient as it does not provide access to all modules.
find
quote
#66
Finally I found why the first backup (the one I took while flashing the first modded BIOS using InsydeFlash) wasn't working and after restoring it with the programmer all I got was a blinking cursor in the top left corner of the screen.

The problem was that the BIOS backup ME region was completely empty.
What I did to fix it was to use UEFITool 0.28 to extract the ME region from the BIOS file that was working (the one extracted from HP BIOS update package) and use it to replace the empty BIOS ME region in the backup.
Saved the new BIOS file and flashed it to the chip with the programmer and now everything seems to be back as it was before starting to play with it.

Maxinator500 thanks a lot for all your help and patience, I've learning a lot.
find
quote
#67
(05-24-2021, 03:34 PM)fc7 Wrote: The problem was that the BIOS backup ME region was completely empty.
Yes.
(05-14-2021, 09:19 PM)Maxinator500 Wrote: I can only confirm that creating a backup using InsydeFlash makes the ME region clean in the output file of the BIOS image.
But did you find the reason for what happening after you flashing backup made with the CH314A?
find
quote
#68
No, I didn't investigated that one but I checked and it has the ME information so no idea.
I'm also wondering if InsydeFlash is missing anything else from the backup besides the ME region, but so far it seems not.

Anyway, my next goal is to try to remove the whitelist without breaking USB boot (or anything else).

As an alternative I found a module that seems to contain the list of all allowed wifi cards: CD28DACA-BDBE-481A-90AC-625C79CF234C "H19BIOSLock"
So if I don't succeed removing the whitelist completely what I would try to do is to replace the IDs of a whitelisted card, with the IDs of my replacement card. In the end I didn't want to mess to much with the BIOS of this laptop, all I want is to be able to install the replacement wifi/bt card.
find
quote
#69
I finally solved it!

The reason why with the modded BIOS the laptop was not able to boot the OS if any USB drive was connected was this module: CD28DACA-BDBE-481A-90AC-625C79CF234C "H19BIOSLock"
It seems that this module was also patched and for some reason that patch was causing the problem. Moreover patching this module is not needed to bypass the whitelist.

Summary:

These are the only two modules that needs patching in order to bypass the whitelist and don't end up with a corrupted BIOS:

- 91472655-50E0-4D81-9AF6-239E6F431B8C "StartUpMenu": to bypass the whitelist
- 86D70125-BAA3-4296-A62F-602BEBBB9081: to be able to boot the modded BIOS

Also VERY IMPORTANT:
- To be able to flash the modded BIOS in my case at least, a programmer is needed.
- My advice is to dump the BIOS with the programmer first to have a backup and also to use that as a base image to patch the modules above and keep ME region + DMI data intact.

I hope this helps someone else in the future.
Thanks a lot Maxinator for all your help and patience!

EDIT: fixed typos
find
quote


Forum Jump:


Users browsing this thread: 3 Guest(s)