RMA'd Asus UX32VD mistakenly has UX32A BIOS. Need advice on flashing it back to UX32VD AMI Aptio UEFI BIOS.

Hello everyone!

Down to business. Wrong BIOS has made the UX32VD Geforce 620M chip unusable, aswell as the 32GB iSSD.
We’re looking at an AMI Aptio UEFI BIOS. Currently reading as UX32A v214: http://i.imgur.com/qQBlkAK.jpg

Exact mainboard model UX32VD REV.2.1: http://forum.notebookreview.com/threads/…upgrade.783248/ (this is the mainboard)
Flash Option 1: [Guide] Flashing modified AMI Aptio UEFI using AFU
BIOS Option 1: https://www.dropbox.com/s/i4hwx5n3fzxfxd…D%20REV.2.1.rar (8.4MB .bin file of unknown origin)
BIOS Option 2: https://www.asus.com/se/Notebooks/ASUS_Z…pDesk_Download/ (Official UX32VDAS.214 BIOS 6.3MB)

Plan:

1
 
AFUDOS UX32VDAS.214 /X /GAN /L3
 

1
2
3
 
/X Do not check ROM ID (to workaround the UX32A / UX32VD "incompatibility")
/GAN Flash all blocks regardless of any software locks
/L3 Load failsafe defaults (for good measure)
 

Doubts:
I am not sure this will work at all, because I'm not sure whether UX32VDAS.214 is a raw bin file. Need someone to tell me this is ok.
Then, alternatively using the supposedly correct 8.4MB .bin file doesn't feel right, since I have no origin on it. If someone has a good .bin please share!
Also, there's no guarantee that /GAN will actually work. If there's anyone that knows which AFUDOS versions that support it, please do tell.
Backups are a given.

Are there any other options to approach this? Or am I out of options?
Need your blessing so that I'm not making any basic mistakes!
Any help is kindly received!

Hi, I have the exact same issues. Assuming you made the other post, I also had this laptop from a previous owner and it was also sent to ASUS on a RMA. I assume they messed the BIOS versioning and I am in the same situation now.

I am writing here to ask you if you have any update on this. Did you try something, what worked what did not ? Much appreciated.

In the end I used Asus’ Winflash in force mode. Works.
From what I understand, BIOS got initially corrupted because the UX32 has a bad ground, and the keyboard backlight disrupts the flash procedure.
So avoid that, and fix the ground if you have the tools. The display ground at the hinges especially.

GL HF

Thank you very much! This is the only place where I could find the answer! Exactly the same problem as you. Sorry for the mistakes in the text.