[REQUEST] Medion Akoya E1318T BIOS Unlock

[Maxinator500]

- unlockung this option in the Bios is unknown procedure for me :) Can you point what do I need to do it? PM me if you would like not to write in this topic.

It's too difficult for me to give an explanation of how you can DIY from scratch. I'm sorry.

- for enabling  MSR 0xC0010114 [C001_0114] to 0, can I use the msr module in Linux (live CD for now is my best option) with the rdmsr command?

I think you can.

On top of it, there is a "kd.exe" debugging tool for Windows capable of wrmsr, that comes with Win10 SDK package. Which would be kind of bloatware if you install it only for the "kd.exe", so msr module in Linux is better choice.

[mikrostart]

- unlockung this option in the Bios is unknown procedure for me  Can you point what do I need to do it? PM me if you would like not to write in this topic.

It's too difficult for me to give an explanation of how you can DIY from scratch. I'm sorry.

- for enabling  MSR 0xC0010114 [C001_0114] to 0, can I use the msr module in Linux (live CD for now is my best option) with the rdmsr command?

I think you can.

On top of it, there is a "kd.exe" debugging tool for Windows capable of wrmsr, that comes with Win10 SDK package. Which would be kind of bloatware if you install it only for the "kd.exe", so msr module in Linux is better choice.

How about this: 
   

Have you tested before? 

Are you awared what values shoul I put in? I'm downloading the AMD docs, which should state this.

[Maxinator500]

Have you tested before? 

Never before.

Are you awared what values shoul I put in?

Try 0x00000008 in EAX.
Technically 0x8 is "00001000", while 0x18 is "00011000", where the 4th bit is set and it locks the VT capabilities. As far as I understood from this page.
Good luck.

[mikrostart]

Under Windows it did not worked.

Tried with Kali to manage the setup module of the bios from this tutorial :

http://wiki.gentoo.org/wiki/Medion_Akoya_E1318T 

but an invalid argument is showing, which one should be?

I've tried with a different block sizes but same occurs, in some moment there is a different error "input output error" and the module just disappears from efivars until reboot.

[Maxinator500]

but an invalid argument is showing, which one should be?

Don't know. Probably there was some change to one or more names of arguments through updates. We need to find out the actual ones.

Is this device capable of EFI boot? I'm thinking if using GRUB is an option.

[mikrostart]

but an invalid argument is showing, which one should be?

Don't know. Probably there was some change to one or more names of arguments through updates. We need to find out the actual ones.

Is this device capable of EFI boot? I'm thinking if using GRUB is an option.

I think its EFI capable, actually the kali installation is booting with grub.

I'm mounting the efivars partition as writable, also I'm using the chattr command to make the bios module immutable so to be able to modify it.

Not sure if there is some bios write protection, also not know for other method to modify this bios module.

It is a simple file, but should be modified with hex offset.

From your link I reached this tool, have you used it before?
http://ruexe.blogspot.com/2020/05/tutori...tring.html

BTW, tested with msr-tools, after rdmsr the value of the svm register is 18 in dec, every attempt to make it 8 in dec, or 0x8 in hex are failing.
The wrmsr command is accepted with no errors, but again the register remains 18 /meaning the flag for amd v is not enabled/.
even if I succeed with msr tools, I doubt the register condition will persist after reboot.
EDIT: ru.efi app was very promising, but no matter what I try the values for the setup module reverts back to default even before reboot. I used ru.efi with booting from a flash drive with efi shell, so host os limitations should be excluded. I'm thinking that may be the BIOS is write protected?

[Maxinator500]

even if I succeed with msr tools, I doubt the register condition will persist after reboot.

It's true.

From your link I reached this tool, have you used it before?
http://ruexe.blogspot.com/2020/05/tutori...tring.html

Not many times, but I used it.

And it looks like the BIOS variables are write-protected.
But that should not matter for Insyde's official config utilities.
Please, try H20UVE 100.00.16.08. It should be capable either of dumping and writing setup storage values. Use console mode to see available commands. Batch file for dumping is included in the archive downloadable.

[mikrostart]

I managed to find a GUI version of H2OUVE and it did rewrie the value in setup in offset 0xf2, but Windows task manager is still claiming the SVM is forbidden/disabled. 
Maybe I'm missing now the correct value, in the Gentoo tutorial it says at: 
000000f0 01 00 00 00 00 00 00 00 00 00 00 00 00 01 00 00  

should change to 

000000f0 01 00 01 00 00 00 00 00 00 00 00 00 00 01 00 00  

Is this the same: 

   

[Maxinator500]

Windows task manager is still claiming the SVM is forbidden/disabled.

Are you sure the offset F2 value is 01 now? If not, check it using RU.EFI.

[mikrostart]

Windows task manager is still claiming the SVM is forbidden/disabled.

Are you sure the offset F2 value is 01 now? If not, check it using RU.EFI.

No, the value is still 00, what ever I try with he H2OUVE utility it stays this way.
Now focused back to the Setup module with a Gentoo live CD, but it is not doing anything, probably wrong syntax. :

   

Found also this blog of Donovan6000 but the method is quite beyond my modding skills:

https://web.archive.org/web/201410162013...tings.html