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
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:
650 G5,830 G6, 840 G6, 850 G6 18F4048-1919FFF-25FB8
435 G8, 445 G8, 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:
650 G5,830 G6, 840 G6, 850 G6. 18F4048-1919FFF-25FB8.mps
435 G8, 445 G8, 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.
.
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
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:
650 G5,830 G6, 840 G6, 850 G6 18F4048-1919FFF-25FB8
435 G8, 445 G8, 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:
650 G5,830 G6, 840 G6, 850 G6. 18F4048-1919FFF-25FB8.mps
435 G8, 445 G8, 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.
.
Comment