@fairestmeat - Changed checksum is expected, as long as your edited BIOS opened in app after (close app, then open new instance and your new mod vBIOS), as long as it's Green/OK then it's OK
UEFITool does not correct that checksum, the Maxwell app should. I meant when you reinsert vBIOS body into BIOS it will correct the checksum on that GUID in the BIOS itself, if there is one in the header. We're discussing two possible checksums here

What GUID is the vBIOS you are editing, there is several vBIOS there so I'm not sure. Ohh, doesn't matter, I checked a few of them, and each GUID has it's own checksum.
So yes, once you replace with UEFITool (be sure it's same way you extracted), the UEFITool will correct the checksum on rebuild and new file will have different checksum for that GUID than the original.
You can see these checksums if you use UEFITool NE Alpha (version 51-x), ohh, sorry, I see you can also see this in the regular versions too (such as 25), it's in the info on right side when you select a GUID at it's base/root

Be careful here, without flash programmer if vBIOS is a brick then you wont have any display output to recover BIOS! If I were you, I would wait until I have flash programmer in hand so you can recover if necessary.

@Lost_N_BIOS

So, I've just installed intel xtu, and after a reboot I have a black screen

I didn't change anything in BIOS yet, now the computer turns on, the fan spins a bit, stops and nothing happen...

How can I try a blind flash, or some other recovery method?

@fairestmeat - Installing software shouldn't cause anything like this, you sure you didn't change anything in BIOS yet? Remove HDD and see if that helps, if not, remove one stick of memory and try again and see if you can load BIOS or not.

You'd have to google Acer BIOS recovery and see if you can find some recovery methods, I think there is a USB recover method but I'm not familiar with any of that. Programmer is the way to go, with backup made before you flash anything (even stock BIOS)
Blind flash would only work, if two things.
1. You changed some graphics setting (or thing ie vBIOS edit you mentioned) that caused you to have no display output, but board would otherwise be running and fine (so blind flash would work here, maybe not in vBIOS edit situation, depending on edit/rebuild).
2. You know which exact keys to press to get to BIOS flash are (In BIOS, or DOS etc) and wrote all that down, prepared in advance.

You said #1 doesn't apply, so BIOS is likely bricked, if removing the HDD doesn't get it booting again (since you mentioned software caused this, that's why I said remove the drive, usually though software isn't going to affect BIOS, but maybe it made some changes to BIOS settings?)

YOu need flash programmer probably, it's cheap if you purchase from China and have shipped slow (less than $7 total), price goes up from there if you buy more locally or have someone ship faster etc.
Let me know if you need linked examples. You need CH341A + SOIC8 test clip with cable.

Final thought.... Why would you install or want to use XTU, when you now have full unlocked BIOS?

Zitat von fairestmeat im Beitrag #17

---

@Lost_N_BIOS

So, I've just installed intel xtu, and after a reboot I have a black screen

I didn't change anything in BIOS yet, now the computer turns on, the fan spins a bit, stops and nothing happen...

How can I try a blind flash, or some other recovery method?

---

@Lost_N _BIOS
Well, i downloaded xtu so I didnt have to go to bios everytime to ajust something xD taking the hdd off and memory didnt work :/

O found somethings about puting the bios on a USB, and start the computer pressing fn + ESC, by doing that the Power light keeps flashing, and the fan runs hard for a while, but nothing happens... I Saw some other things about using wincrisis/crisdisk etc but nothing solide.
I Guess programmer is the way to go, i would appreciate some exemples

@fairestmeat @LOST_N_BIOS


The BIOS chip is usually locked on that machine as well. If you cannot reset BIOS through key-press combo, as @LOST_N_BIOS already mentioned, programmer would be the only option.

@GooballDiesel - He "was" already using unlocked Mod BIOS, but then Intel software caused some issue


@fairestmeat - Make sure USB is 2.0 stick, formatted to FAT32, smaller USB = better (128MB-2GB), and BIOS file usually has to be a certain name too (and on root of USB)
Also, you can't use the BIOS I modified for you for that, you have to use the stock extracted fd (make copy with .bin extension too)

Here is examples of what you need programmer wise, as mentioned, you can buy from other sellers, other stores etc, often shipped faster for more $$ (and you can get both in bundle/kits too)
https://www.ebay.com/itm/142885544668
https://www.ebay.com/itm/382486015977

Zitat von fairestmeat im Beitrag #20

---

@Lost_N _BIOS
Well, i downloaded xtu so I didnt have to go to bios everytime to ajust something xD taking the hdd off and memory didnt work :/

O found somethings about puting the bios on a USB, and start the computer pressing fn + ESC, by doing that the Power light keeps flashing, and the fan runs hard for a while, but nothing happens... I Saw some other things about using wincrisis/crisdisk etc but nothing solide.
I Guess programmer is the way to go, i would appreciate some exemples

---

@GooballDiesel - This is Acer, and you probably know more than me about Acer or Insyde BIOS (I hate it )

@GooballDiesel @Lost_N_BIOS

Thanks guys, I'll take a look on programmer, mean while, is there a method to know what shoud the image name be for the usb recovery?

------------------------

Alt + f10 didn't do anything, same black screen and fan starting

Zitat von fairestmeat im Beitrag #25

---

@GooballDiesel @Lost_N_BIOS

Thanks guys, I'll take a look on programmer, mean while, is there a method to know what shoud the image name be for the usb recovery?

---

Open BIOS with UEFITOOL.

Find "recovery" like following photo:




right click on "compressed section" choose "extract body"

open extracted file with hex editor, then search for ".rom"

Zitat von fairestmeat im Beitrag #25

---

@GooballDiesel @Lost_N_BIOS

Thanks guys, I'll take a look on programmer, mean while, is there a method to know what shoud the image name be for the usb recovery?

---

@fairestmeat - Hopefully you can get with info above, thanks @GooballDiesel

If not, DO NOT erase or write anything once you get programmer, only read, verify and then save and send to me then WAIT!!
This way you are sure we get valid dump before you erase or write anything. This way we also find correct software version that writes to your chip, otherwise dumps could be fail and writes would also fail.
Once you get in there, tell me your BIOS chip ID (read off the chip), so if necessary I can tell you what software version works best or what ID you should use if other than exact etc.

Zitat von Lost_N_BIOS im Beitrag #27

---

@fairestmeat - Hopefully you can get with info above, thanks @GooballDiesel

If not, DO NOT erase or write anything once you get programmer, only read, verify and then save and send to me then WAIT!!
This way you are sure we get valid dump before you erase or write anything. This way we also find correct software version that writes to your chip, otherwise dumps could be fail and writes would also fail.
Once you get in there, tell me your BIOS chip ID (read off the chip), so if necessary I can tell you what software version works best or what ID you should use if other than exact etc.

---

@GooballDiesel

Thnaks alot guys, I'll try as soon as I can.
When do the fn+esc the Power light start flashing, this means that the recovery parte of bios is working?

Zitat von fairestmeat im Beitrag #29

---

@GooballDiesel

Thnaks alot guys, I'll try as soon as I can.
When do the fn+esc the Power light start flashing, this means that the recovery parte of bios is working?

---