You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NOTE: You should select this option if you are going to request support for new unlock
algorithm or existing one didn't worked for you.
IMPORTANT: before creating a new issue first check if there is any existing one with same model
or algorithm request, in that case you'd better add information to that particular issue (your
laptop model, BIOS version, screen photo, etc).
Please replace [VENDOR] in a title with your laptop vendor (e.g. dell, hp, acer) and [MODEL]
with model, also you can specify extra information in [algorithm info] if you can, otherwise just
remove it from a title.
Please specify following information:
General information
Vendor: Dell
Model: Latitude E7270
Firmware version: 1.21.6
Don't expect on immediate response, your issue might help someone other who would face such
issue in a feature but not necessarily you. I'd suggest you to contact your vendor support, cause
this should be much faster channel.
While I've found a workaround (changing the suffix to BF97), I figured this was worth documenting.
The text was updated successfully, but these errors were encountered:
NOTE: You should select this option if you are going to request support for new unlock
algorithm or existing one didn't worked for you.
IMPORTANT: before creating a new issue first check if there is any existing one with same model
or algorithm request, in that case you'd better add information to that particular issue (your
laptop model, BIOS version, screen photo, etc).
Please replace
[VENDOR]
in a title with your laptop vendor (e.g. dell, hp, acer) and[MODEL]
with model, also you can specify extra information in
[algorithm info]
if you can, otherwise justremove it from a title.
Please specify following information:
General information
Don't expect on immediate response, your issue might help someone other who would face such
issue in a feature but not necessarily you. I'd suggest you to contact your vendor support, cause
this should be much faster channel.
While I've found a workaround (changing the suffix to BF97), I figured this was worth documenting.
The text was updated successfully, but these errors were encountered: