[REQUEST] Medion Akoya E1318T BIOS Unlock

[Maxinator500]

the value is still 00, what ever I try with he H2OUVE utility it stays this way.

You might probably be using UVE only in GUI mode. Don't you? Try -gv and -sv commands of console mode.

[mikrostart]

the value is still 00, what ever I try with he H2OUVE utility it stays this way.

You might probably be using UVE only in GUI mode. Don't you? Try -gv and -sv commands of console mode.

Yes, I'm using the GUI version. 
Must admit that it is a bit hard with the console. 
I got this: 
Variable Editor Feature:
  -gv <File>                  : Supported!
  -sv <File>                  : Supported!
  -re -vn <VarName> -vg <GUID> : Supported!



EDIT: 
Managed to enter the command:

.\H2OUVE-W-CONSOLEx64.exe -gv vars.txt

I'm attaching the file. 
Is it enough to edit the setup moduleonly with notepad? 
  vars.txt (Size: 51.18 KB / Downloads: 1)

[Maxinator500]

Is it enough to edit the setup moduleonly with notepad?

Edit setup F2 variable in the file, with notepad. And try to set new variables via -sv command.

[mikrostart]

Is it enough to edit the setup moduleonly with notepad?

Edit setup F2 variable in the file, with notepad. And try to set new variables via -sv command.

Ok, made the -sv command: 

Code:

H2OUVE.exe -sv vars.txt
Now Parsing File From vars.txt.
Succeed to read vars.txt file.
Variable Index[001]: Set failed!
Variable Index[002]: Set failed!
Variable Index[003]: Set failed!
Variable Index[004]: Set failed!
Variable Index[005]: Set failed!
Variable Index[006]: Set failed!
Variable Index[007]: Set failed!
Variable Index[008]: Set successfully!
Variable Index[009]: Set successfully!
Variable Index[00a]: Set successfully!
Variable Index[00b]: Set successfully!
Variable Index[00c]: Set successfully!
Variable Index[00d]: Set successfully!
Variable Index[00e]: Set successfully!
Variable Index[00f]: Set successfully!
Variable Index[010]: Set successfully!
Variable Index[011]: Set successfully!
Variable Index[012]: Set successfully!
Variable Index[013]: Set successfully!
Variable Index[014]: Set successfully!
Variable Index[015]: Set failed!
Variable Index[016]: Set failed!
Variable Index[017]: Set failed!
Variable Index[018]: Set failed!
Variable Index[019]: Set successfully!
Variable Index[01a]: Set successfully!
Variable Index[01b]: Set successfully!
Variable Index[01c]: Set failed!
Variable Index[01d]: Set successfully!
Variable Index[01e]: Set successfully!
Variable Index[01f]: Set successfully!
Variable Index[020]: Set successfully!
Variable Index[021]: Set failed!
Variable Index[022]: Set failed!
Variable Index[023]: Set failed!
Variable Index[024]: Set failed!
Variable Index[025]: Set failed!
Variable Index[026]: Set successfully!
Variable Index[027]: Set successfully!
Variable Index[028]: Set successfully!
Variable Index[029]: Set successfully!
Variable Index[02a]: Set successfully!
Variable Index[02b]: Set successfully!
Variable Index[02c]: Set successfully!
Variable Index[02d]: Set failed!
Variable Index[02e]: Set failed!
Variable Index[02f]: Set failed!
Variable Index[030]: Set successfully!
Variable Index[031]: Set successfully!
Variable Index[032]: Set failed!
Variable Index[033]: Set failed!
Variable Index[034]: Set successfully!
Variable Index[035]: Set successfully!
Variable Index[036]: Set successfully!
Variable Index[037]: Set successfully!
Variable Index[038]: Set successfully!

But again the SVM is not enabled. Based on the above I think that the f0 row is written? 
I'm wondering if the representation in H2OUVE and hexdump are idential?!

Here we have from H2OUVE: 

Code:

"Setup"

      GUID: A04A27F4-DF00-4D42-B552-39511302113D

      Attributes: 0x7

      DataSize: 0x279

      Data:


            000000F0: 00 00 01 00 00 00 00 00 00 01 00 00 00 01 00 00

But is this the same 0xf2 like in hexdump: 

Code:

root #hexdump -C Setup-a04a27f4-df00-4d42-b552-39511302113d
000000f0 01 00 00 00 00 00 01 00 00 00 00 00 00 01 00 00 |................|

Note where the new value 01 emerges in hexdump - it is on the 7th position from left to right, not in the place of 3rd like it is on H2OUVE?

[Maxinator500]

So, if the new value 01 emerges to the 7th position in hexdump, let's calculate the var. number we need to change with UVE.
This will be F2 - F6 - F2 = EE.
So, the line will be like...

Code:

000000E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00

Consider zeroes as values to be untouched.

Do load defaults and try again with the new variable.

[mikrostart]

So, if the new value 01 emerges to the 7th position in hexdump, let's calculate the var. number we need to change with UVE.
This will be F2 - F6 - F2 = EE.
So, the line will be like...

Code:

000000E0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 00

Consider zeroes as values to be untouched.

Do load defaults and try again with the new variable.

Ok, now the f2 alue is finally 01, but the svm is still disbaled. 

Anyway thanks a lot for the efforts! 

Well, I'm out of luck, no more ideas. 

In this thread, it states for f4 to enable svm, and some hiden menus of the other offsets: 

https://forums.mydigitallife.net/threads...-to.45118/

Code:

000000f0  00 01 01 00 01 00 00 00  00 00 00 00 00 00 00 01  |................|

Much in the same way, the hidden pages (Advanced and Power) and a few extra options can be enabled by modifing the efi variables at position 0x21b and 0x21c. Just set them to "0x01" and reboot. ....|

Code:

00000210  00 00 00 00 01 00 00 00  00 00 00 01 01 00 00 00  |................|

[Maxinator500]

Well, I'm out of luck, no more ideas.

There's one more idea I have.
Is your device exactly Medion E1318T? I don't understand why we have to iterate over F2, F4 or else when it is possible to get to know the true variable easily. But I need information about the device's model name.

[mikrostart]

Is your device exactly Medion E1318T

   

[Maxinator500]

Ok, thank you.
After extracting the contents of the H90T_S.bin file you attached, I can confirm that 0xEE is indeed right variable for SVM Support enablement. So, there must be something else, but I'm out of ideas either.

[mikrostart]

Ok, thank you.
After extracting the contents of the H90T_S.bin file you attached, I can confirm that 0xEE is indeed right variable for SVM Support enablement. So, there must be something else, but I'm out of ideas either.

I managed to connect with the author of the Gentoo tutorial, here is some kind of an idea:

there is a separate setting for the IOMMU which I haven't
been able to discover. Is this needed to work with SVM or it needs either one of the two /OIMMU or SVM/ to be enabled somehow, and make possible to use VMs?