So.. my experience came from a K53BE laptop, and I really didn't feel compelled writing anything about such dreadfulness, but comments here seem wrong enough that I think some clarification is needed. There shouldn't be any important difference from your case, given the systems have more or less the same age (~2012) and technology (AMI Aptio4).
So, first of all: I believe the most important thing is checking if LEDs are still left working.
If they correctly respond to power on/off and AC plugging, chances are the most basic functionality is still there. HDD access light should also blink every now and then. Otherwise if nothing comes alive (short of a shy fan, if any)... I'd really start looking for an SPI programmer.
Alternatively, if you happen to have an usb key with a built-in "activity lighting", you could try to see if when connected on boot it blinks.
Regardless of leds though, we are gonna need a FAT32 one (size shouldn't matter, mine was 64GB) with the official bios image inside. There's plenty of mystery around the name you should give to such file, I for one had: amiboot, K43BE (the "genitor" of my laptop family, after which my bios image was actually named on asus website) and VRL50 (the motherboard part number, acronym also found in bios image itself). All of them both in a .bin and .rom fashion.
Then, I'm going to list scrupulously what I did afterwards, but I have no pretense or knowledge of this having been strictly necessary:
Remove the hard disk(s)
Unplug the pc from charge (battery should be left connected)
Wait ~5 minutes
Insert the usb key in a 2.0, non-header, port
Press RightControl and Homeā± on the keyboard
Power on, while keeping pressed down these buttons
Reconnect AC power, while keeping pressed down the buttons
After some amount of time that shouldn't exceed the minute, display should first flicker, then finally power on (and just when this occurs you should let go buttons).
Eventually asus firmware should take care of the remainder part of the recovery procedure.
EDIT: crash recovery may also require different special keys such as Alt+F2, or F11. While other times, for as much the dead display, it could even be you can still boot normally from disks. YMMV.
EDIT2: the same procedure is still confirmed to work on much newer Aptio V asus latops (also showing that probably I may have been a bit overzealous in my instructions)
The Crucial MX 500GB m.2 is only SATA. This is at least what the specs say:
Link to description.
M.2 is a Form Factor. NVMe is the Controller or Interface. Most m.2 SSD's are NVMe, but yours I think is not!
Can you boot the OS from the SATA or doesn't this work either?
Best Answer
I managed to figure it out. I had to make the USB bootable drive in UEFI mode. Tried with Rufus and the Windows 10 tool from the Microsoft website and they both worked.