@Lost_N_BIOS unfortunately, it did not work, neither in windows nor after S3. shutdown still after 30min. So i just ordered the programmer and clip and come back to you once the stuff arrived. im pretty sure im going to need you help with that programming stuff :-/
Thanks for your support so far! same to @Sylar76
Bummer! 
Sorry we couldn’t get it this way! Yes, come back when programmer arrives. If you feel jumpy, you can always pinmod, people do it all the time. so you should be able to do it on this too I think.
not sure about this, dont feel very confident to do this by my own
but you may be right, at least i should try 
im going to search for the audio chip tomorrow, now its quite late for today.
It’s OK, wait and programmer will arrive before you forget about this… sometime 
I order from China often, so used to the long waits, I try to forget about it, then it magically arrives.
So, has it shut down yet, it’s been past 30 minutes right?
@Lost_N_BIOS i ordered via amazon prime, so it should arrive latest next week… yep it did go off after 30min
BTW: this is the mainboard zay90 la-a681p
@Chads - Good, that’s much quicker than China shipment. Since laptop did shut down at 30 minutes, I think this means mod BIOS I sent you was overdone (changed settings too many times, there is NVRAM And setup to control this, usually you do one or other, I did both)
Lets test new BIOS with only one changed or the other, I will send two. If you want to test both again, follow same procedure I initially outlined for you in post #14, flash the mod BIOS (then reboot, load optimal defaults, then boot to DOS) then try FPT DOS.
If same error, try next BIOS, if same still then we’ll have to wait on programmer Be sure to change the file name in FPT Command for these new BIOS when you flash it - http://s000.tinyupload.com/index.php?fil…610244263494849
Flash one, reboot, load optimized, then test flashing ME as mentioned in #14, if no luck, reflash next BIOS, repeat
@Lost_N_BIOS - i just flashed both bios files and tried to fpt -me -f mef.bin after each. the error still pops up each try. so no success so far.
can you just tell me what is the difference in both bios versions you sent me?
Update: managed to pinmod and flashed the me with fpt -me -f -mef.bin 
fpt -greset was also successful.
do i realy need to flash my original bios back now?
@Chads - You may have to wait on programmer then, sorry this does not work always due to security (it’s designed to not allow this). The difference is in the area of settings used/stored that I changed, as explained above.
There is two places that hold this ME Re-Flash setting, in the first BIOS I sent you for this I changed both locations (Setup + AMITSE/SetupData x2 (one fail safe + Optimal)).
In the last two BIOS I sent you, I changed it in one or the other (Setup in one, AMITSE/SetupData for the other), in case that firs one with both was cancelling each other out or something funny like that.
Normally, changing one or the other enables it, either one.
You can try on stock BIOS, to change the NVRAM variable for this instead, but it’s more tricky. Reflash stock BIOS, and then follow what I outlined for you in post #14 after the "OR"
This method is different than the others, and could also work when these fail. This changes setup, like above, but makes the change in live NVRAM instead.
Give it a shot, it’s a little involved but I’m sure you can get it, people us this method all the time to unlock “BIOS Lock” setting to flash mod BIOS
In the end outcome may be the same, but this is the method I would have done first since it’s easiest in some ways, and doesn’t involve BIOS modifications and reflashes etc.
* Edit @Chads - I didn’t see your edit until I posted this. Yes, go ahead and reflash your backup BIOS now, otherwise ME will be disabled probably.
If you want, please first dump your entire BIOS now via (From windows OK now) >> FPTw.exe -d bios.bin
Then I will unlock FD for you so you wont have to pinmod or anything after that. Do not reboot until you’ve done this, and I’ve sent you back file to reflash!
I will replace your original dump in, and unlock BIOS lock too, this way it will all be unlocked and ME will be re-enabled due to ME Re-Flash setting being put back
@Lost_N_BIOS alright, i did not reflashed my original image yet and dumped the current version. for some reason it is now 8MB large…
bios.zip (3.52 MB)
@Chads - Yes, 8MB is correct, thanks! That’s because this is complete BIOS now since you did pinmod. Don’t reboot until we’re done, or you will have to pinmod again.
Once we’re done, you wont have to pinmod ever again, nor will you need to use programmer. However, any time you reflash stock BIOS region “BIOS Lock” will get reset to enabled, but that’s easy to get around via my guide (Never mind, I just checked again, BIOS Lock is disabled by default!)
So, all will remain unlocked until anytime you reflash FD, which normally would only happen if you program in with programmer a locked/stock FD
Here is FD unlocked BIOS, with your stock dumped region put back in, so now all stock except updated ME which you already did and FD unlocked
http://s000.tinyupload.com/index.php?fil…089694827261437
Flash via >> FPTw.exe -f biosfdstock.bin
Then you can reboot, go into BIOS, load optimal and make any other changes you usually make, then all should now be fixed!
@Lost_N_BIOS thanks i will reflash with your version. the laptop is even without your modified bios now running for 50min without shutoff. thats amazing. im tended to not touch it at all 
Yes, once you reflashed ME that 30 minute issue would be fixed. It’s fine, and you should reflash the one I just sent, then you can reboot and all will be unlocked, fixed and next time no hassles needed to reflash anything
@Lost_N_BIOS well, something is wrong. after flashing the bios the laptop does not start anymore, it looks like it tries to start, the fan starts spinning and then it resets and tries again. i already removed the bios battery but nothing changed, what a pitty, it worked already…
EDIT
get it boot with enabled pinmod, any advises? im now in windows - shall i flash back to the bios i just dumped before?
@Chads - That’s not good, sorry! Please flash this one, maybe wrong UEFITool version for your BIOS? If error from FPT about file not found, rename to shorter name
http://s000.tinyupload.com/index.php?fil…156639744985621
Flash via >> FPTw.exe -f biosfdstock2.bin
If you are scared now, you can simply reflash Asus Stock BIOS via EZ Flash, but you will have to pinmod any time you have similar issues next time, or use programmer. If you flash the BIOS above you wont, all will be unlocked.
* Edit, I compared files from first one and this one, same, so UEFITool version not an issue here. Please just flash using this way to alleviate any possible issues
Use BIOS above as source file
FPTw.exe -desc -f biosfdstock2.bin
FPTw.exe -bios -f biosfdstock2.bin
Yes, sorry, I just edited in above. Please wait one second, let me get you BIOS region and FD separately, there must be some alignment issue
One sec, I’ll edit new files in here
@Chads - Here is files, flash per below commands
http://s000.tinyupload.com/index.php?fil…733164018419821
FPTw.exe -desc -f fd.bin
FPTw.exe -bios -f biosdump.bin (This is the dump you sent me originally)
If this fails, then something wrong with the FD, I will have to look at it later and figure it out.
For now if it fails, just reflash stock BIOS from Asus via EZ flash, so you get normal BIOS region back (DO NOT flash stock BIOS via FPT)
* Edit, I have to run, be back tonight! Hopefully above sorts it for you, if not do the stock flash from Asus to put back BIOS region.
still the same
and EZ flash doesnt let me reflash the original version, it tells me the build date is too old, damn :-/
can i reflash with fpt and the 8MB dumped bios?
Edit: Managed to reflash the stock image with EZ Flash (when EZ flash shows the error that the build date is too old you have to type “risky” (no joke!) and it will continue.
Now running on stock bios…
Wow, what’s going on here! EZ Flash should always let you reflash same version? Very funky! 
Where do you type “risky”, I’ve never heard of this as an option too, will have to keep in mind to tell others to try.
Maybe the stock flasher was checking ME version, and wanting to, or did, reflash that, and that’s why it was acting funny? Since you’d already flashed in a newer and updated version than what’s included in any of the Asus stock BIOS.
What ME version do you see now, still 8.1.70.1590?
I found this trick somewhere in the internet, first i thought someone is kidding, but it worked for my old EZ flash utility. When the error appears, dont acknowledge, just type risky, and then you are able continue.
where can i see my current ME Version?
MEInfoWin still cant detect it and gives same error like mentioned in Post #1
@Chads - thanks, I’ll have to keep this in mind, I wonder if it works at all EZ Flash error screens?
I checked your ME in the BIOS dump you provided already after pinmod (in post #29), and ME was updated per the FPT ME flash you did to the mef.bin file.
So it should be working provided you have ME drivers installed and are using the correct MEInfo version (From V8 package). You can see ME version on BIOS main page or with HWINFO64 on the large window, in motherboard section.
However, it will be disabled still if you have not reflashed the stock BIOS region yet, using FPT or Asus EZ Flash with stock BIOS. Maybe that only appeared to flash?