Forum RSS Feed Follow @ Twitter Follow @ Twitter

Thread Rating:
  • 5 Vote(s) - 4.2 Average
  • 1
  • 2
  • 3
  • 4
  • 5
[Request] Acer Aspire E5-553-1786
(11-09-2017, 06:10 PM)FerchogtX Wrote: Weird question, in fact, I did compare the files, and I found there is also a change in the 00000140 range, according to McCkarke's help:

Original:

Code:
00000140: 00 00 01 00 00 01 00 00 00 00 00 00 00 01 00 02

Changed:
Code:
00000140: 00 00 01 00 00 01 00 00 00 00 00 00 00 00 00 02

There is a 01 changed into a 00... can you confirm if this is needed to enable Virtualization or not? Or at least, what does this value do?

Thanks in advance.

Cya!

I just tried this using both the original change and additionally changing the extra bit above.  In both cases the change was easy enough to make, and after the initial change Task Manager does indeed report virtualization has been enabled.  However, I 'm wondering if that is just changing a flag and not actually changing anything in the machine itself, because VirtualBox is still reporting that I do not have VT-x/AMD-V available on the system.
find
quote
(05-07-2017, 10:15 AM)mclarke2355 Wrote: Hi,
the flashing of the modded BIOS might not work because the recovery checks the signature of the BIOS file.

However, you might be able to enable AMD-V using this method (needs to be adapted): http://www.geektech.co.nz/how-to-unlock-...enovo-y700
This method requires Windows as a system as the necessary tool is only available for Windows.

First, you will need the tool: https://drive.google.com/file/d/0B4NHIBM...RtQXM/view
Extract the archive and go to the folder with the extracted files.
Then, you need to open an administrative command prompt in that folder (google it if you don't know how).
Execute the command from step 1 of the linked guide in that command prompt (H2OUVE.exe -gv vars.txt).
After that, you'll have the file "vars.txt" in that folder.
You need to upload this file, so that I can make the change.

For reference, here's the EFI-table with available settings for this notebook: https://drive.google.com/open?id=0B4NHIB...WI4LW14bE0
And here's the setting that needs to be changed:
0x1C40B             Setting: SVM support, Variable: 0xEE {05 91 54 02 55 02 54 00 34 12 EE 00 00 10 00 01 00}
0x1C41C                 Option: Disabled, Value: 0x0 (default) {09 07 27 00 10 00 00}
0x1C423                 Option: Enabled, Value: 0x1 {09 07 28 00 00 00 01}

Here mine vars.txt
Please enable my V-AMD. Thanks before.

Ven
find
quote
(11-25-2017, 11:51 PM)JoeCaloric Wrote:
(11-09-2017, 06:10 PM)FerchogtX Wrote: Weird question, in fact, I did compare the files, and I found there is also a change in the 00000140 range, according to McCkarke's help:

Original:

Code:
00000140: 00 00 01 00 00 01 00 00 00 00 00 00 00 01 00 02

Changed:
Code:
00000140: 00 00 01 00 00 01 00 00 00 00 00 00 00 00 00 02

There is a 01 changed into a 00... can you confirm if this is needed to enable Virtualization or not? Or at least, what does this value do?

Thanks in advance.

Cya!

I just tried this using both the original change and additionally changing the extra bit above.  In both cases the change was easy enough to make, and after the initial change Task Manager does indeed report virtualization has been enabled.  However, I 'm wondering if that is just changing a flag and not actually changing anything in the machine itself, because VirtualBox is still reporting that I do not have VT-x/AMD-V available on the system.

Did changing the 00000140 line fix y our virtual box problem, when the initial change to 000000E0 didn't?

Anyway. I just tried without changing the 00000140 line and my virtual box is working and my memory is still at 16 gigs. The restart took forever, gave me an error message from Windows about restarting after 15 minutes. Then hung on the manufacturer splash screen for 10 more minutes, so I just restarted manually by pressing down the power button, and everything is working fine.

So all I had to do was change the 000000E0 under the Setup Group, line and use the H2OVUE tool and this guide above to change the 2nd to last "00" to "01" and vwala. I'm good. Hope that helps somebody. Thanks for the guide.
find
quote
(12-05-2017, 05:44 PM)rapstar Wrote:
(11-25-2017, 11:51 PM)JoeCaloric Wrote:
(11-09-2017, 06:10 PM)FerchogtX Wrote: Weird question, in fact, I did compare the files, and I found there is also a change in the 00000140 range, according to McCkarke's help:

Original:

Code:
00000140: 00 00 01 00 00 01 00 00 00 00 00 00 00 01 00 02

Changed:
Code:
00000140: 00 00 01 00 00 01 00 00 00 00 00 00 00 00 00 02

There is a 01 changed into a 00... can you confirm if this is needed to enable Virtualization or not? Or at least, what does this value do?

Thanks in advance.

Cya!

I just tried this using both the original change and additionally changing the extra bit above.  In both cases the change was easy enough to make, and after the initial change Task Manager does indeed report virtualization has been enabled.  However, I 'm wondering if that is just changing a flag and not actually changing anything in the machine itself, because VirtualBox is still reporting that I do not have VT-x/AMD-V available on the system.

Did changing the 00000140 line fix y our virtual box problem, when the initial change to 000000E0 didn't?

Anyway. I just tried without changing the 00000140 line and my virtual box is working and my memory is still at 16 gigs. The restart took forever, gave me an error message from Windows about restarting after 15 minutes. Then hung on the manufacturer splash screen for 10 more minutes, so I just restarted manually by pressing down the power button, and everything is working fine.

So all I had to do was change the 000000E0 under the Setup Group, line and use the H2OVUE tool and this guide above to change the 2nd to last "00" to "01" and vwala. I'm good. Hope that helps somebody. Thanks for the guide.

No.  Changing the 00000140 line did nothing.  Changing the 000000E0 line causes Windows to report that virtualization is on (whereas before it said it was off). But virtual box is not working on that machine.  It works on other machines I have.  So I don't know.  Maybe the motherboard really doesn't support it, so turning it on in the CPU doesn't do anything?
find
quote
(12-05-2017, 07:42 PM)JoeCaloric Wrote:
(12-05-2017, 05:44 PM)rapstar Wrote:
(11-25-2017, 11:51 PM)JoeCaloric Wrote:
(11-09-2017, 06:10 PM)FerchogtX Wrote: Weird question, in fact, I did compare the files, and I found there is also a change in the 00000140 range, according to McCkarke's help:

Original:

Code:
00000140: 00 00 01 00 00 01 00 00 00 00 00 00 00 01 00 02

Changed:
Code:
00000140: 00 00 01 00 00 01 00 00 00 00 00 00 00 00 00 02

There is a 01 changed into a 00... can you confirm if this is needed to enable Virtualization or not? Or at least, what does this value do?

Thanks in advance.

Cya!

I just tried this using both the original change and additionally changing the extra bit above.  In both cases the change was easy enough to make, and after the initial change Task Manager does indeed report virtualization has been enabled.  However, I 'm wondering if that is just changing a flag and not actually changing anything in the machine itself, because VirtualBox is still reporting that I do not have VT-x/AMD-V available on the system.

Did changing the 00000140 line fix y our virtual box problem, when the initial change to 000000E0 didn't?

Anyway. I just tried without changing the 00000140 line and my virtual box is working and my memory is still at 16 gigs. The restart took forever, gave me an error message from Windows about restarting after 15 minutes. Then hung on the manufacturer splash screen for 10 more minutes, so I just restarted manually by pressing down the power button, and everything is working fine.

So all I had to do was change the 000000E0 under the Setup Group, line and use the H2OVUE tool and this guide above to change the 2nd to last "00" to "01" and vwala. I'm good. Hope that helps somebody. Thanks for the guide.

No.  Changing the 00000140 line did nothing.  Changing the 000000E0 line causes Windows to report that virtualization is on (whereas before it said it was off). But virtual box is not working on that machine.  It works on other machines I have.  So I don't know.  Maybe the motherboard really doesn't support it, so turning it on in the CPU doesn't do anything?

Try deleting all your vitual sessions uninstall and reinstall VMware. that's what I did before I modded the bios.

Any help for me on unlocking the whole bios hidden menu? I'm just being greedy now lol, sike Fk Acer
find
quote
(05-07-2017, 10:15 AM)mclarke2355 Wrote: Hi,
the flashing of the modded BIOS might not work because the recovery checks the signature of the BIOS file.

However, you might be able to enable AMD-V using this method (needs to be adapted): http://www.geektech.co.nz/how-to-unlock-...enovo-y700
This method requires Windows as a system as the necessary tool is only available for Windows.

First, you will need the tool: https://drive.google.com/file/d/0B4NHIBM...RtQXM/view
Extract the archive and go to the folder with the extracted files.
Then, you need to open an administrative command prompt in that folder (google it if you don't know how).
Execute the command from step 1 of the linked guide in that command prompt (H2OUVE.exe -gv vars.txt).
After that, you'll have the file "vars.txt" in that folder.
You need to upload this file, so that I can make the change.

For reference, here's the EFI-table with available settings for this notebook: https://drive.google.com/open?id=0B4NHIB...WI4LW14bE0
And here's the setting that needs to be changed:
0x1C40B             Setting: SVM support, Variable: 0xEE {05 91 54 02 55 02 54 00 34 12 EE 00 00 10 00 01 00}
0x1C41C                 Option: Disabled, Value: 0x0 (default) {09 07 27 00 10 00 00}
0x1C423                 Option: Enabled, Value: 0x1 {09 07 28 00 00 00 01}

help me please


Attached Files
.txt   vars.txt (Size: 86.91 KB / Downloads: 0)
find
quote
Hello friends,

I am completely new to both this forum and BIOS modifications, please excuse my naivety Shy

I wish to enable AMD-V on ACER ASPIRE E-15 E5-553G-T9VU which is disabled by the vendor. There is no option to enable AMD-V on this machine's BIOS. 

I need AMD-V for university projects. 

Can anyone please guide me in this issue. I read the posts in this thread but they are of -1786 and my machine is -T9VU, are both of these same?
I think i'll need the steps from scratch.  Tongue 

Looking forward to hear from you.

Many thanks.

Regards.
find
quote
Hi friends,

Sorry to sound desperate but I need Amd-V very urgently.

Please help me for - purchased in India - E-15 E5-553G-T9VU.[/size]

Smile Smile Smile
find
quote
Hi anyone,
really need help to turn on AMD-V for my ACER E5-553G-114Q
BIOS Version Insyde Corp V.1.19

it is safe process?can someone help me please?
Thanks you so much Smile

Please this is my Vars
find
quote
Wink 
Hello  Big Grin , i'm new and here's my vars.txt

My Acer's series is E5-553G-F79R
BIOS version : Insyde Corp. V1.09, 03/08/2016


can u help me ? Thanks.

oditouchiha's vars.txt

find
quote


Forum Jump:


Users browsing this thread: 1 Guest(s)
Expand chat
Expand chat
Expand chat

To join us in the community live chat, please register or log-in