Zitat von Lost_N_BIOS im Beitrag #150

---

It\'s OK, you got it! If they are both 00 already, then it\'s already disabled.

---

Yes, sorry, I should have mentioned if already 00 then = disabled.
I just checked the latest FPT dump you sent me, and I see 0xA2 and 0xA3 BOTH = 01 in NVRAM setup area, so I think maybe you are not in correct setup (And or, it's due to secure boot enabled too)
Be sure you are in the largest "Setup" with GUID - EC87D643-EBA4-4BB5-A1E5-3F3E36B20DA9

Zitat von Lost_N_BIOS im Beitrag #152

---

Yes, sorry, I should have mentioned if already 00 then = disabled.

---

Yes, there is always two setups, once is tiny (sparse content)
Sounds like you are in correct one then, must be due to secure boot enabled. Disable that, then do as mentioned (That must be done, even for the last FPT stuff I mentioned on page #10 too)

The Secure Boot is always disabled. I will try again now.

You said it's enabled at #145, that's why I keep mentioning it. But, now that I looked back you were explaining why it's disabled, only mentioned "with enable" etc. Sorry for my confusion
If it is disabled, then not sure why you are seeing those set to 00, it's not that way in the BIOS you dumped and sent to me.
If you still see 00 for both, try 0x05 and then see if FPT lets you do #2. If not, then do what I mentioned with FPT at the end of page #10 and see if you get success on #2 of that way or not.

In the meantime, as long as I check the variables and secure boot - here is the result of steps 1 and 2 (dumped the BIOS region with a new name *biosregst1.bin* and flashbacked it).

Add this to your post #150 (End of page 10) stuff too!
1. FPTw.exe -a 0x10000 -l 0x20000 -d NVRAM.bin
2. FPTw.exe -a 0x10000 -l 0x20000 -f NVRAM.bin

Ohh! Haha, so it's disabled and now FPT step #2 passes! You must have disabled it via grub even though it was saying "out of range"!!
Sorry I did not think to have you recheck that with grub! If you type just the offset, without 0x00 after it, then it shows you current value (in grub/setup_var I mean), I should have had you check, but usually out of range means it's failing and nothing is going to change.

So, all set now!!
Send me biosregst1.bin, and when I get back in later today, or tonight, I will do the mod BIOS for you again!

@Lost_N_BIOS
So, if I got that right: out of range error occured because the locks were disabled already ?
No, I was thinking to verify that, and then I googled: check bios locks status, check grub setup_var locks, check bios locks, verify smi lock etc. - all I found are your posts on this forum with the commands setup_var - nothing about how to check that

Btw, PDR Region does not exist - what does it mean ?

DOWNLOAD for free: biosregst1.bin

No, out of range usually means setup_var can't edit whatever you tried. Nothing to do with anything already being set to any value in NVRAM (This what you are editing with RU or setup_var, the "Setup" storage area for setup values)
Various things cause this, not sure what did in this case. But, it was untrue anyway, since it changed it, so you should not have seen that error

Yeah, to check an offsets current value with setup_var you do like below
setup_var 0xA2 xx << To change to xx value
setup_var 0xA2 << To just check value, you don't need to do above first (ie no need to attempt a change), I only added there for complete example. When you type just this, it will then readout the current value for the given variable/offset

PDR region does not exist means it looked and it's not in the BIOS, it's not part of this BIOS at all anyway, you can ignore.
GbE region error is same, if/when you ever see it, simply means it's not in the BIOS (boards with Intel Gigabit LAN have it, those that do not may or may not have it, but FPT will often mention if you flash certain things in certain ways.
^^ Your BIOS DOES have this But, we are not trying to dump or flash the whole BIOS, or GbE, so you should not see message about it

So clear, so easy to understand ;)
Thanks a ton!

@EthanWalker - You're welcome!

Here, mod is done - Redux mod, same change log, minus M2 mod + Microcode refresh (+ keep all)
- EFI RST 14.8.2.2397
- oRom RST 14.8.2.2397 TRIM Mod
- NVME Mod
- All microcodes removed in main volume except updated 40661 ALL Microcodes remain this time, both volumes updated to latest for ALL


Flash back in via >> FPTw.exe -bios -f EthanWalkerNewFinal.bin
http://s000.tinyupload.com/index.php?fil...223553839177892

@Lost_N_BIOS
When I graduated from high school or when I was accepted to work in a super company -> I wasn't so excited as I am now.

I will flash it tonight because this morning and all day I will need this laptop.
But tonight, I'll flash it right away - I hope I don't damage anything... because then I'll have to come back with a message from the intercom, once I don't have another spare laptop.

Haha, what super company do you work with? It's great to hear you're so excited!
Do you need to know about installing to NVME, or have you already done that before or read up on it etc?

Don't worry, all should be fine!
But, I know what you mean, so no rush here from me

Zitat von Lost_N_BIOS im Beitrag #164

---

Haha, what super company do you work with?

---

Zitat von Lost_N_BIOS im Beitrag #164

---

Do you need to know about installing to NVME, or have you already done that before or read up on it etc?

---