[REQUEST] Acer Aspire E5-553(G) BIOS Unlock

[starvest]

Hello, my laptop is Acer E5-553G-F79R, i want to activate amd-v to run android emu in android studio, this my vars.txt https://drive.google.com/file/d/1lTS4ujs...sp=sharing

I would really grateful if you can help me to unlock amd-v

[suhaspr]

Hello Sir,

        I have an acer aspire E5-553g-T9VU Amd A10-9600p Laptop. 
        Currently, I am on bios version 1.05 ( Insyde version ).
        Bios Insyde Acer E5-553G link --> 

        https://global-download.acer.com/GDFiles...R&SC=AAP_4

         From extensive searching on this forum, I came to know i need to download H2OVE Tool. I have downloaded it and 
         generated vars.txt from it which is present in attachment below.

         I will be forever grateful to you if you can help me enable virtualization in my firmware. 


Regards,
Suhas P R

Hi!
Done. Check your PM.

Hello feluchi,

                 Thanks for responding. This is a very good website regarding bios information. 
                 However, I did this myself in meantime and i have AMD-V Enabled now!!  
                 Now, I am even running ubuntu 16.04.3 in the vmware 14.0 superb..

    Just want to mention how I did this to help out fellow users. I searched bios mods forum and
     got this link --> https://www.bios-mods.com/forum/Thread-R...ion?page=2

Here, a user named [b]PieterBKK has mentioned the correct steps for enabling AMD-V on acer AMD Laptops. Bless him![/b]

[b]Regards,[/b]
[b]suhas p r[/b]

[JoeCaloric]

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.

[ravenart]

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

[rapstar]

Hello.

Bios Version as copied from msinfo32

BIOS Version/Date Insyde Corp. V1.06, 5/18/2016


I need to access the advanced options in my bios to unlock amd-v for my Asus Aspire 553g-f55f.
It has a fx-9800p processor and M445dx (dual graphics) so a dedicated crossfire with a integrated graphics setup.
Here is my Vars vile. https://drive.google.com/file/d/173L0PpL...sp=sharing


I noticed my particular laptop model is not in the bios repository.

I was going to try this Video Tutorial for a different acer https://youtu.be/fzuuE0tz6bY,

Which seems pretty simple, but it's a different laptop and I didn't want to risk changing a hex value and bricking cuz they controlled different things or something.

Also, a vars mod wont change my available memory will it? I have 16gb. I believe on a single slotl.

[rapstar]

sorry bout that double posting. I read up a bit on the work you do here. I added my vars file to the original post. Your work is really helpful. Thanx.https://drive.google.com/open?id=16gpGRb...33LoY--vz1

Looking at the picture, I can see my vars file has the 000000E0 line, under setup. Does that mean that I change that 2nd the last "00" to "01" and save it with the H2OUVE tool?



Or is my bios different and requires something else.

[rapstar]

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.

[JoeCaloric]

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?

[rapstar]

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

[sunpuk745]

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