Lost_N_BIOS was logged in last time 2 months ago, unfortunately. I hope he's well.

You can't put these data in an update file these regions don't get updated, otherwise every update would delete this information since an update image comes 'blank'. So you need to update these areas either by hardware programmer or by fpt (Intel ME tools)

Problem in your old bios is probably here- flash map is missing because of corrupt NVRAM/ EVSA store (looks a little different because of bios versions)



Download ME System Tools v8 r3
Intel (Converged Security) Management Engine: Drivers, Firmware and Tools

Run fpt(w(64)) -bios -d biosreg.bin (in windows at an adminstrator command prompt)

Post the file and the output of the command (screendump of command prompt window)

Sorry I was busy working, Here's what you asked for.

Biosreg.rar contains an image dated february 21st?

Anyway:
1.) We have to find out if bios region can be written by fpt
2.) We have to decide which parts of your corrupt dump should be transfered,

1. will be done by dumping a bios region and trying to write it back with fpt.

2. can be done
- by updating your bios now to 62CN97WW (same version is more easy to compare) and trying to repair your original dump
- by updating your bios now to 62CN97WW (same version is more easy to compare) and transfering what seems machine specific from bricked dump to new dump
- by simply adding the small block from 44F000 to any version and hoping that it'll be good enough

Please empty the directory with fpt for all earlier dumped/ stored biors regions

Then run
fpt(w(64)) -bios -d biosreg.bin (in windows at an adminstrator command prompt)

directly followed by
fpt(w(64)) -bios -f biosreg.bin (in same adminstrator command prompt window, make sure that biosreg.bin is the file you dumped directly before)

Post output window.

Thanks for your response, I will be updating the bios to the latest version, sorry I didn't have much time to do it, (I was planning to do that since the beginning), which makes things easier.

BIOS Updated successfully to the latest version 62CN97WW.
Here's the output window.

Could you please post this latest dump with 62CN97WW? Thanks

Unfortunately there's a write protection for the bios region which wont let you software flash it (fpt).

Zitat von lfb6 im Beitrag #21

---

Could you please post this latest dump with 62CN97WW? Thanks

Unfortunately there's a write protection for the bios region which wont let you software flash it (fpt).

---

As written problem is probably NVRAM grown too big. This bios uses 3 EVSA stores, the other 3 EVSA stores are static. Seems that there's on block (< 4 kB) corresponding to the brown EVSA stores in padding. Your updated bios doesn't have the last EVSA store and corresponding to that only one 4kB block used in padding. Green arrow => board specific data.

This bios seems to have a wrong size for the uefi volume holding the EVSA stores. See structure on the left, 5th EVSA and Flash Map are hidden in padding (changing the volume size makes them visible again). The bios doesn't seem to care too much about that (until the NVRAM get's too large).

Your old bios (left) had an additional error in the parser: "NvramParser::parseNvramVolumeBody: one of stores inside overlaps the end of data" So it seems to me that this construction works until the 5th EVSA store in this area is created/ used and grows larger than given size. Then it seems that the bios no longer can write to NVRAM, giving you the error message.


Cure would be to replace the 5th EVSA store in this volume (and the corresponding block in padding at 452000) with the corresponding empty areas ("FF") of a stock bios, or to transfer the board specific data to a stock bios. Stock bios does have a short flash instruction in one EVSA store which possibly should be removed, but maybe it doesn't hurt either. Programming can't be done by update since NVRAM normally isn't touched.


(There are some flash tools that can delete NVRAM, Samsung had such a problem for it's 6- series UEFI bioses, could be solved by software. But if board and tool aren't compatible one might also delete necessary standard defaults for restoring and get a brick...)

In your case I simply put in the board specific data into your dump and combined the bios region with FD/ME from your original dump.

Flash it back with programmer, read back the content of the chip and compare it to the source file, has to be a 100% identical.

@lfb6 thanks for your efforts, I really appreciate it.
To be honest, I don't understand much.

Zitat

---

This bios seems to have a wrong size for the uefi volume holding the EVSA stores. See structure on the left, 5th EVSA and Flash Map are hidden in padding (changing the volume size makes them visible again). The bios doesn't seem to care too much about that (until the NVRAM get's too large).

---

You mean my current updated BIOS or my OLD Corrupted BIOS ?

Zitat

---

Flash it back with programmer

---

Gonna have to take the laptop apart and desolder the BIOS Chip again and take it to the repair shop by Monday,

Zitat

---

read back the content of the chip and compare it to the source file, has to be a 100% identical.

---

By programmer also ? or with fpt ?

In your opinion, would that fix the problem (change the SN and UUID with no real issues) ?

@WGenius Both bios seem to have this "flaw". Even for stock bios the Flash Map isn't displayed correctly in UEFIToolNE. So it's possible this error will come again after a certain amount of changes in NVRAM.

You have to flash back via programmer, fpt doesn't work without tricks since certain areas of the bios region are write protected. You can always make a backup of the bios region with fpt, but you're not able to write it (completely). Recommendatons for writing were given as if you'd have a programmer, sorry.

Changes are minimal, it's just the earlier mentioned block that's inserted. Since the bios region is taken from your working laptop (last fpt backup) and FD and ME are from your first (real) own backup there's (if programmed correctly) zero chance to brick the machine. But disassembling and flashing itself has a risk of course.



It might seem that I made it more complated than necessary, I could've simply copied this block into your dump and call it a day. But I wanted to understand what possibly caused your error and what these 2 other bocks in padding were good for just to avoid sendnig you a file that'd cause a brick.

Zitat von lfb6 im Beitrag #25

---

Both bios seem to have this "flaw". Even for stock bios the Flash Map isn\'t displayed correctly in UEFIToolNE. So it\'s possible this error will come again after a certain amount of changes in NVRAM.

---

Zitat von lfb6 im Beitrag #25

---

It might seem that I made it more complated than necessary, I could've simply copied this block into your dump and call it a day.

---

Zitat von Plastixx im Beitrag #27

---

Zitat von lfb6 im Beitrag #25

---

It might seem that I made it more complated than necessary, I could've simply copied this block into your dump and call it a day.

---

I did that for him 6 days ago.

Not sure why he doesn't just buy a programmer himself; they're dirt cheap.

---

Zitat von WGenius im Beitrag #28

---

I wouldn't mind if I had the chance, the problem is, the only model available (here in Algeria where I live) is "beeprog" which cost too much, and I don't have a credit card, plus if I want to order a cheap one like (CH341A) it would take up to 3 months to arrive, and sometimes it won't.

---

Zitat von Plastixx im Beitrag #29

---

Zitat von WGenius im Beitrag #28

---

I wouldn't mind if I had the chance, the problem is, the only model available (here in Algeria where I live) is "beeprog" which cost too much, and I don't have a credit card, plus if I want to order a cheap one like (CH341A) it would take up to 3 months to arrive, and sometimes it won't.

---

Ah, that sucks. PM me your address and I will see if I can have one shipped to you from Aliexpress. Sure it will take a long time (if it ever arrives), but better than not having one at all. Let me know if it's better to have it shipped from Turkey or China.

---