Black screen after bios upgrade / incorrect OPAL password due to special characters

[sedut-pank]

I have been using sedutil on my computer for over a year. I use 1 password for SID and ADMIN1.
After updating the BIOS asrock z370 pro 4, my computer got a black screen instead of the password request.
When booting with SSD connected, even logo bios is not displayed.
If you disconnect the SSD, the computer boots normally.
It is no longer possible to roll back the BIOS version.
I plugged SSD into my laptop - password is requested and successfully decrypted.

Samsung EMT02B6Q

I am using RESCUE or cmd on my laptop to disable Locking and the PBA:

sedutil-cli --disableLockingRange 0 STARS%%$$ /dev/sda
or
sedutil-cli --disableLockingRange 0 'STARS%%$$' /dev/sda

But I get the answer:
method status code NOT_AUTHORIZED
Session start failed rc = 1
EndSession Failed

I enter 100% correct password. Maybe it's because I'm using special characters.
What do I do now?

Screenshot of the output --query /dev/sda
https://i.imgur.com/iWmiddx.jpeg

Similar password problem
Drive-Trust-Alliance#208
Drive-Trust-Alliance#96

Similar problem with bios
Drive-Trust-Alliance#384
Drive-Trust-Alliance#404

[sedut-pank]

Cheers! I was able to solve the problem.

I was using the version RESCUE64-1.15-5ad84d8.img from the github repository - it had errors.

I downloaded the RESCUE64 1.20 version, the commands worked on it and I successfully booted into the system.
https://github.com/Drive-Trust-Alliance/sedutil/wiki/Executable-Distributions

downloaded UEFI64-1.20.0
sedutil-cli --loadPBAimage 'pass' /path/to/UEFI64.img /dev/sda
The files were overwritten.
Then re-enable the lock and PBA
sedutil-cli --enableLockingRange 0 /dev/sda
sedutil-cli --setMBREnable on /dev/sda
reboot
Same again, After the motherboard logo there is no PBA password prompt, just a black screen.
In the BIOS setup, secure boot and fast boot are disabled. Legacy support is enabled everywhere.

What can I do?