HP Clean VSS2 dumps,fix Endpoint Security error

[SMDFlea]

Just a thread to post clean VSS2 files/dumps in.A clean VSS2 file can, in some cases, fix
the infamous **"Endpoint Security" error message.
Be aware that if you use a clean VSS2 you may need to fill in missing DMI info using HP BCU !

I`ve included some clean files/dumps,offsets and a few scripts to autopatch a few models.
The offsets and file sizes are part of the naming convention i`ve used for the extracted
files.

hoaca388 has made an excellent guide how to extract the VSS2 file and edit/clean it up by
filling everything after the header with FF`s
https://www.badcaps.net/forum/troubl...55#post3310855

Note: It is the Main bios that is patched, not the EC_Bios.

By default the extracted VSS2`s are named "VSS2_store_VSS2_store.vss2" .The attached VSS2 files are
renamed by: start offset - end offset - size


Models,Offsets and filesize in hex:

640 G5, 650 G5,830 G6, 840 G6, 850 G6, 1030 G4, Zbook 14u G5. 18F4048-1919FFF-25FB8

435 G8, 445 G8, 855 G7, 855 G8. 1070048-1095FFF-25FB8 (Identical file/size as models above but different offsets)

ZBook Fury G8. 192A048-1967FFF-3DFB8 (Different size and offsets.Header 1 byte different)


As far as i know the per model offsets for the VSS2 store do not change after a bios update, but its
something to watch out for.


If you can`t use a hex editor you can still patch your own main bios using the attached
TinyHexer Scripts for autopatching. See the README.txt file for instructions . If anyone else
wants to add a script the existing ones can be edited easily with a text editor,just change
the filename plus the start and end offsets and filesize in decimal.

Models and Script filenames:

640 G5, 650 G5,830 G6, 840 G6, 850 G6. 1030 G4, Zbook 14u G5. 18F4048-1919FFF-25FB8.mps

435 G8, 445 G8, 845 G8, 855 G7, 855 G8. 1070048-1095FFF-25FB8.mps

ZBook Fury G8. 192A048-1967FFF-3DFB8.mps

If any of these scrips have worked for you give


**"Endpoint Security" error message

You may get this message if:

The ME firmware is corrupt or not cleaned (using a clean VSS2 will not fix this !) , you havn`t added the DMI with HP BCU ,the VSS2 store is corrupt,
you used a different bios dump, you removed a password from the EC bios, the bios was updated, secure boot is disabled.

.

[SMDFlea]

Models,Offsets and filesize:

640 G4, 650 G4, 830 G5, 840 G5, Zbook 15U G5. 1AF6048-1B1BFFF-25FB8

Script filename:

1AF6048-1B1BFFF-25FB8.mps

.

[minhdigital]

Thanks for share

[SMDFlea]

Models,Offsets and filesize:

830 G7, 840 G7, 1030 G7. 18EA048-190FFFF-25FB8

Script filename:

18EA048-190FFFF-25FB8.mps

[SMDFlea]

Models,Offsets and filesize:

440 G8, 450 G8, 830 G8 ,840 G8, X360 1040 G8. 188A048-18C7FFF-3DFB8

Script filename:

188A048-18C7FFF-3DFB8.mps

[lokmanolgun]

Hello. How can I create the vss script file for hp 800 g2 twr or can you send it?

[SMDFlea]

Hello. How can I create the vss script file for hp 800 g2 twr or can you send it?

Models,Offsets and filesize:

800 G2 TWR. B98048-BB5FFF-1DFB8

Script filename:

B98048-BB5FFF-1DFB8.mps

[chojkangta9x]

Just a thread to post clean VSS2 files/dumps in.A clean VSS2 file can, in some cases, fix
the infamous **"Endpoint Security" error message.
Be aware that if you use a clean VSS2 you may need to fill in missing DMI info using HP BCU !

I`ve included some clean files/dumps,offsets and a few scripts to autopatch a few models.
The offsets and file sizes are part of the naming convention i`ve used for the extracted
files.

hoaca388 has made an excellent guide how to extract the VSS2 file and edit/clean it up by
filling everything after the header with FF`s
https://www.badcaps.net/forum/troubl...55#post3310855

.

Hi I need endpoint fix file for HP EliteBook x360 830 G7

[Mahesa09]

Just a thread to post clean VSS2 files/dumps in.A clean VSS2 file can, in some cases, fix
the infamous **"Endpoint Security" error message.
Be aware that if you use a clean VSS2 you may need to fill in missing DMI info using HP BCU !
.

This means you just need to patch it without having to edit again "everything after the header with FF"

[SMDFlea]

This means you just need to patch it without having to edit again "everything after the header with FF"

Yes, but only the VSS2 region (or regions on some models, more than one)

[Mahesa09]

Yes, but only the VSS2 region (or regions on some models, more than one)

ok sir thankyou, this is succes, not sucses to the patch EC

[SMDFlea]

The script only patches VSS2 in the main bios, thats what it does, one thing only, it doesn`t do anything else that it`s not made for. You should learn how to use a hex editor.

[SMDFlea]

Models,Offsets and filesize:

Zbook 17 G6. 18B4048-18D9FFF-25FB8

Script filename:

18B4048-18D9FFF-25FB8.mps

[Satinfo50]

Models,Offsets and filesize:

440 G8, 450 G8, 830 G8 ,840 G8, X360 1040 G8. 188A048-18C7FFF-3DFB8

Script filename:

188A048-18C7FFF-3DFB8.mps

I have an HP x360 1040 G8 laptop and I am having issues with my endpoint security.
I ran the script and reprogrammed the BIOS but without success
After turning on my laptop this message was shown on the screen.



Every time the laptop was turned on, the counter decreased by one.
Initially, the counter showed the number 34. After turning it on and off 34 times, the message changed to show this new message and the counter remained at the number 1.
Now Windows will not boot and the laptop will only enter the BIOS program.




Can anyone help with this problem?

I have attached my script file and my BIOS backup file for further review
The endpoint.bin file is the BIOS file after running the script and the endpoint.bin.bak file is the original BIOS version of my laptop.

[SMDFlea]

Flash the endpoint.bin bios again, then use HP Bios Config Utility to enter all DMI ,and then lock MPM.

[WickedTaras]

Hello. This script

Script filename:

188A048-18C7FFF-3DFB8.mps

is compatible with PB 445 G8?

[SMDFlea]

Hello. This script
Script filename:
188A048-18C7FFF-3DFB8.mps
is compatible with PB 445 G8?

No it isn`t. I checked and the 855 G8. 1070048-1095FFF-25FB8.mps is the one you want at post 1 ,the 445 G8 is the same .I`ll edit the post and add the model number

.

[WickedTaras]

Hello! I flashed the SPI ROM with a cleaned VSS2. But it didn't give any result. What else could be the problem?

Probook 445 G8.

[SMDFlea]

Hello! I flashed the SPI ROM with a cleaned VSS2. But it didn't give any result. What else could be the problem?

Probook 445 G8.

I have no idea what the initial symptom of the laptop was. Start a new thread in laptop troubleshooting if you think there`s a hardware problem, or if you still think there`s a bios problem post your request in a 448 G8 topic and explain exactly what the issue is

[SMDFlea]

Models:

ProOne 400 G4 20-inch Non-Touch AIO Business.
ProOne 440 G4 23.8-inch Non-Touch
Zbook 15 G5
Zbook Studio G5

Offsets and filesize: 1962048-1987FFF-25FB8

Script filename:

1962048-1987FFF-25FB8.mps

[bert-bert]

Hello,
you ask for positive feedback. I hope negative feedback is also welcome. I have an EliteBook 840 G6 and this patch kills the laptop. With two different bios images the laptop is dead with the charging LED blinking a specific white-orange pattern after applying this patch. I can confirm that the offsets are correct for my image according to UEFITool. There was no battery neither the main Li-Po nor the lithium Bios coin cell or any other component connected while testing this. Just mainboard, heatsink and RAM. I do not know if this makes a difference.
Nevertheless thank you for your work and effort!

[SMDFlea]

Hello,
you ask for positive feedback. I hope negative feedback is also welcome. I have an EliteBook 840 G6 and this patch kills the laptop. With two different bios images the laptop is dead with the charging LED blinking a specific white-orange pattern after applying this patch. I can confirm that the offsets are correct for my image according to UEFITool. There was no battery neither the main Li-Po nor the lithium Bios coin cell or any other component connected while testing this. Just mainboard, heatsink and RAM. I do not know if this makes a difference.
Nevertheless thank you for your work and effort!

All feedback is welcome, negative or otherwise. To say that it has killed the laptop though is,quite frankly .I did have a look at your bios --> https://www.badcaps.net/forum/troubl...85#post3575185 ,and your Gbe region is corrupt, it is filled with FF`s. Compare it to one of the others in the thread and you`ll see there is some code in the others.