Ohh sorry, I meant about FPT can't write back BIOS region due to odd error caused by AFU.
Yes, I meant reflashing of stock BIOS from Asus. So, this Winflash tool, is that the same one I mentioned, when choosing Win8.1 >> windows BIOS update Utility?
Is that what tells you "No, can't update BIOS" due to too old etc? << Once you confirm this is the tool or now, I will edit it per your edited in info, to see if we can bypass that error

Good to see ME FW version is showing up, at least it's not badly corrupted, but still could have some issue that's causing the delay at startup. We would not know for sure without redoing via clean/update ME FW
If reflash of BIOS region is not too important to you now, and you only want to resolve the delay at startup, this may only be ME FW related which we can try to fix first and see if solves the issue or not (or you can also first test clean install of windows onto your NVME, to rule out some windows files causing a delay)
I see you mentioned M.2 + NVME insert, that may also be causing an issue, normally we'd only insert one or the other, not sure why you had me do both?

Do you want me to take your latest dump, unlock FD (so we can easier mess with ME FW later if needed, via FPT), clean and update ME FW, and then you program that back as-is without touching BIOS region for now.
So you can then test and see if delay resolved, or if not, test clean windows install, to see if delay resolved.
Then if not, first thing would be to remove M.2 mod, only NVME mod is needed here, then if issue remains further ME FW test may be required (someone elses region first as quick test), then stock BIOS region only as quick test etc.
Lots can be done here, in many ways, to see what's going on, but what we do all depends on how much you want to mess with programmer (least as possible is best), and what your main goals to fix are.

Right, sorry - I just checked on the Asus website, it is called Windows BIOS update utility - only after installing the utility, it appears as WinFlash tool.
So, yes - I couldn't update with Windows BIOS update utility, it says that the latest version of BIOS update (213) from the ASUS website is older than the current version.

I don't remember why I requested M.2 + NVMe, but if it is possible, you can add NVMe only - since I will use an NVMe drive from now.

Zitat

---

Fernando said: The word "M2 mod" is misleading. What the related authors obviously meant is the insertion of a specific EFI module named "SAMSUNG_M2_DXE", which is required to boot off an M.2 or PCIe connected SSD, which uses the AHCI protocol. It has nothing to with an attached NVMe SSD.

---

Well, the delay on the boot, to be honest - doesn't bother me at all (because it doesn't affect the performance - at least from what I've noticed).
*The delay only occurs when I connect the POWER cable. I mean, I connect the Power cable and the laptop starts automatically (without pressing the Power button) + a delay.
** But If I shutdown the laptop now (without disconnecting the Power cable) and then press the Power button - it will start as usual, without delays... - but if I shutdown + disconnect it from power source, then re-connect again, it will start with a delay.

Well yes, it would be great to mess less with programmer because I disassembled this laptop too many times, and as I can see, the LCD cable is going to die soon because I removed/connected it to many times, and it is sensible as hell.
I'm really not sure what to choose from the options above - all of them seem to be legit, since we don't have a 100% way to solve the issue with ME FW.
Anw, as I said - the delay doesn't bother me, the laptop works great.

OK, I will edit the tool and see if you can then get past this error. Please show me a screenshot of the exact error.
Once we get to BIOS region edits, I will remove the M.2 insert. System should not auto-start either, so I think something is wrong with the ME FW maybe, or EC FW, not sure, but I know it shouldn't do that.
Does your BIOS Clock keep correct time when power is removed, for say 1 hour? If you programmed in any BIOS from me, it's likely that FD is already unlocked, so we may be able to test/address ME FW issues via FPT, unless you also get the same odd error with FPT when trying ME region as you do with BIOS region.

Please dump FD for me and lets see what's there >> FPTw.exe -desc -d fd.bin

So, if we ignore everything, ie delay is OK to you, what does that leave us to do?

@Lost_N_BIOS

Zitat von Lost_N_BIOS im Beitrag #123

---

Please show me a screenshot of the exact error.

---

Zitat von Lost_N_BIOS im Beitrag #123

---

Does your BIOS Clock keep correct time when power is removed, for say 1 hour?

---

Zitat von Lost_N_BIOS im Beitrag #123

---

Please dump FD for me and lets see what\'s there

---

Yes, thanks, exactly that image is what I wanted to see If I can't edit the exe to make it bypass this, we can edit the stock BIOS date to fix this issue!
I will check the exe now and edit this with file for you to replace if/when I can find and bypass. * Edit, before I can do this, which exact package did you download and install? From which OS did you choose at top, Win10, Win8.1

Ahh, so the delay is this! Fail Safe is being used due to BIOS resetting, along with memory re-training again each time you remove power.
CMOS is being reset each time you remove power due to either dead CMOS battery or bad CMOS package connection.
Check the battery with multi-meter, if it's not 3.0-3.3V replace it CR2032 is what you need, and the cheap x3-5-10 packs on ebay work perfectly for a long time

fparts.txt error may be due to file location and where you ran the CMD prompt from, I'd have to see screenshot of the command window and your folder with the files
FD you linked is stock locked, so seems you did not program in any BIOS from me via programmer, or for some reason the BIOS you did (if you did), I did not unlock the FD.
So, that would have to be done first if we need to do anything with ME FW, and if we do then I could just do the FD and ME directly right then and you program in it.

I used Windows BIOS Flash Utility for Windows 8.1

Additional info:
Version V3.0.1
2014/11/21 - 888.63 KBytes

----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Ok, I will check the battery when I will disassemble the laptop.
Strange that the battery could have died now. It would have been an interesting coincidence, because the startup delay - started exactly after I made changes to the BIOS.

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

No, I never programmed your BIOS with programmer - Only made a backup with FPT - then I flashed your 1st mod with AFU - then I flashbacked the 1st backup with FPT which resulted to this:

Zitat

---

I'd have to see screenshot of the command window and your folder with the files

---

Thanks, Ill grab and install that 8.1 now and see if I can bypass (if so, I will have you send me the exe from the installed program folder, in case the one generated on my end in Win10 is different)
Batteries can only recharge so many times before they stop holding a good charge, and once it drops below 3V then more and more often it will get reset. It could also be loose cable to the battery or loose solder joints if it's in a plastic mounted case type holder.
Could be some random AFU flashed BIOS issues, I wouldn't doubt it, but what you describe sounds more like what I mentioned with CMOS than anything else.

Thanks for the fparts error image, it may be due to that fparts does not have your exact BIOS chip ID in it.
Compare the DOS one with the Win32 one, are they same, or is there different chip ID's in there?

* Edit @EthanWalker - * Edit, I can't install on my end, since I don't have "Asus" Laptop!
Go here, copy the WinFlash entire folder, zip it and send to me >> C:\Program Files (x86)\ASUS\WinFlash\

Even if it is not different, I will send the installed program folder (just in case)
Download: WinFlash I Win8.1

-----------------------------------------------------------------------------------------------------------------------------------
I hope it is not mandatory to check the battery now, because I need the laptop for work + to disassemble the laptop just for the battery... ufff :D Anw, if it is important, I will do this today.
Already added a couple of CMOS in my Amazon list.

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

I checked both fparts (DOS & Win32) - both of them have my chip ID in the list (which was detected by FPT as: W25Q64BV)

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

Yeah, that's what I mentioned above, grab the installed program folder, then I will simply send back file to replace if I can find and edit to bypass that error.

No, you can check the battery whenever you have time, but what you described really can only be that, battery itself or the connection to the board from the battery

Do both fparts have the exact same info on each for ALL W25Q64 entries? Your chip may not be BV ID, FPT chip detection is not always correct, so if windows one is missing some W25Q64 info that the DOS one has, then it may be due to that (Copy the DOS one into Windows one and try again)
If same error still, then probably more issues relating to the AFU Flash/FPT problem.

Zitat von Lost_N_BIOS im Beitrag #129

---

No, you can check the battery whenever you have time, but what you described really can only be that, battery itself or the connection to the board from the battery

---

Zitat von Lost_N_BIOS im Beitrag #129

---

Do both fparts have the exact same info on each for ALL W25Q64 entries?

---

Zitat von Lost_N_BIOS im Beitrag #129

---

Your chip may not be BV ID, FPT chip detection is not always correct

---

Zitat von Lost_N_BIOS im Beitrag #129

---

Copy the DOS one into Windows one and try again

---

Test this, put stock BIOS into Winflash folder, open Admin CMD Prompt there, then run this command >> WinFlash.exe /NODATE and then when it runs select BIOS file and see if it will let you flash, ignore warning about it being older if it says anything like that.
If that does not work, I can edit exe in one place that may get it, but not 100% sure

So, both fparts have BV and FV same info, and FV is your actual chip? If yes, then it's not a fparts issue, just more AFU mess with FPT stuff

Yes, it worked.

Zitat von Lost_N_BIOS im Beitrag #131

---

So, both fparts have BV and FV same info, and FV is your actual chip?

---

Nice!! So, now BIOS region will be stock again, with your serial and all that + KB backlight still working.
Then, if you can dump via FPT in DOS we can redo the mods all again now

Delay may be gone, we'll have to see. Load optimized and reboot back to BIOS to make any other changes you want.
Once you remove power that will be lost though and fail safe will load again (if battery bad or loose etc), so you can only test if delay is gone without removing power.

Zitat von Lost_N_BIOS im Beitrag #133

---

Then, if you can dump via FPT in DOS we can redo the mods all again now

---

Zitat von Lost_N_BIOS im Beitrag #133

---

Delay may be gone, we\'ll have to see.

---

Just BIOS region is all we mod, so that's all you need to dump
FPT.exe -bios -d biosreg.bin