[REQUEST] Help finding problem after bios corruption

Hi,
First off all thankyou for your patience

Here is the history
last month i get my hands to one of these laptops Asus Vivobook pro N580G

Firts day i make the mistake of update bios from a GPT USB stick getting a blank screen

I buyed a CH314 and a bios dump from vinafix and programed the bios according to the beginners guide

the laptop came back to life but with issues no Function keys, waiting time between power states around 40 seconds an no serial number or Windows licence

later that week used corrupted bios dump to extract licence serial number and MAC address and a fully working bios from a friend that buyed the same laptop in same store,
using HxD replaced serial number, windows licence and MAC address on Friends Bios dump but after flashing i still have the issue off long wait times between Power states( power, restart and suspension) and random freezes

here its a TXT with the link to the Dumps

Dumps.txt (84 Bytes)

@gmnckw - What is BIOS Chip ID? And what software/version are you using to write to the chip with?

Sounds like corrupted ME FW issue, which should be fixed when you write mod BIOS from friends system, unless you broke BIOS editing it, or software/version you are using isn’t best to write to your chip with.

After checking dump (friend mod) this is corrupted dump. Is this dumped from chip, after you wrote, or only friends BIOS modified and you didn’t write it yet?
If this is not dumped, only you modified friends BIOS, this is bad mod. If this is dumped off chip, after you modified it and programmed it in, then it’s just a bad dump

Are you dumping with same version software you dumped and wrote before? Let’s get this sorted out before I do anything, give me your chip ID
What is Dump Bad? Is this dump from BEFORE you wrote anything to chip with programmer, or AFTER you wrote with programmer using vinafix BIOS?

Also, please confirm, which is your exact model >> N580GD or N580VD?

Hi @Lost_N_Bios
the chip is a 25b127DSIG
the Friend mod is a friend modified dump so yes i suppose is a bad mod
i used ASProgrammer using the GD25Q128C preset i still have access to my friend´s laptop in case i need to take another dump bad dump its the Dump of the original chip after bad update before writing anithing with the programmer
and yes its a N580GD

Use ASPrgrammer and GD25Q128C is suggested, sounds like that’s what you used Friend mod is corrupted in such a way it looks like a bad dump from programmer, not a bad BIOS edit (Friend BIOS before you mod is OK). What did you edit it with and how etc?
I will make you new BIOS, thanks for confirming model.

Please send me PM of your MAC ID, serial, and UUID etc, so I can find in BIOS and properly transfer out in all areas.
I see you changed serial, but not sure what your MAC or his MAC Is, and I want all this in text file so I can keep in folder and easily note when needed as I edit.

Thank you Lost_N_Bios for your help and comprension

I moded using HxD and replacing the text so i suppose that was my mistake i really appreciate your help i just sended PM with the info

@gmnckw - Here, first we test with your original NVRAM in place, if it works fine, then nothing more to do after first test Doing it this way because it’s easier to not rebuild your NVRAM if we don’t have to, it may be OK and just ME FW was messed up bad enough to make it not work, if not then it was the NVRAM.
If that fails, I will make you BIOS with stock (empty NVRAM - Actually, this is also included now), and you run system once, boot to BIOS, load optimal defaults, save and exit, boot to windows then shut down and dump again and send back to me so I can then put your details back into NVRAM area

So, first program in dump-BAD-FDMEOGNV, if that fails to boot, then program in dump-BAD-FDMEStockNV and do what I mentioned above
https://ufile.io/48setgi8

I used your friends BIOS to update it’s ME FW, then put back into your BIOS, so if his ME FW was messed up (ie slow startup like you mention) then that may carry over.
If this happens, but everything else OK, then let me know and I will fix using stock BIOS ME FW and update it instead (And we’ll fix ME FW for friends BIOS and send him fixed BIOS too)

@Lost_N_BIOS Thanks a lot, first didnt work but second just works great no delay betwen power states (only isuue is that at powerup it tries to power twice before boot ) i also uploaded the dump as you mentioned to Drive link

You’re welcome! Nice to hear the original power issues are now fixed! Sorry to hear there is a new one though Does it always do this now? If yes, please shut down, remove power cable, and main battery, press and hold power on button for 15 seconds, then let sit for 1+ minute with no power.
Then connect main battery and power cable back, boot to BIOS, load optimal defaults, save and apply, reboot back to BIOS to make any changes you want. Then save and boot to windows. Shut down, wait a minute, then start it again, does it still double boot now?

I don’t know what you mean, about uploading file to “drive link”? Maybe you forgot to add link?

@Lost_N_BIOS did what you told me the double boot bloblem is still tere another issue is that coming back from a suspended state keeps blank screen and need to force restart (i thinks is OS problem) the drive link is the folder link that was in #1 post, thank you for your help

Ohh, sorry, I forgot you had a link in that text, I think maybe you can post links now? Did this BIOS always double boot, or do you not know and had not used this BIOS version before?
If you had not used this version before, please try flashing back to previous version you were using now, so we can see if that’s a normal BIOS issue with this BIOS version or not.

@Lost_N_BIOS i returned to

at first start restarted 2 times by itself and the third boot keep at blank screen shuted down and nex boot was succesful everything is working now i made several test and no problem at all, so i like to say you are awesome and really apreciatte your help

@gmnckw - So maybe some random glitch thing, or NVRAM was rebuilding maybe, not sure? So all is OK now?
OK, I will edit dump again now and put your details back into NVRAM, then you program back in and can put system back together. Then probably again will need a few reboots to sort itself out
Actually! I checked, and NVRAM rebuilt itself and copied in the correct details to correct places from the other areas that I already put your details into. So you’re good to go now