AC66U_B1 Unresponsive after upgrade to 386.4

[pctechtx]

I have an AC66U_B1 and flashed the RT-AC68U_386.4_0.zip firmware after seeing the notification in router interface for an update. After the flash finished and rebooted only that LAN and Power LED would be on and was totally unresponsive via LAN. Took me forever to get recovery mode activated so I could recover. If anyone else has the issue I did, set a static IP (192.168.1.3/24) on the machine attempting to recover the router, unplug unit, press and hold WPS button and insert power plug, when power light started flashing I tapped the reset button, after tapping the reset button I started receiving ping responses and opened http connection to 192.168.1.1 and was able to load the previous firmware RT-AC68U_386.3_2.zip. Unit is back up and running, though it shows in web interface that I am on firmware 386.4.
Before rolling back I attempted flashing .4 and after reboot it acted same way. Had to use 3_2 to recover. Router interface shows it's running .4 though.
Not sure what is going on but wanted to put this out there so maybe whatever the issue is might get resolved.

Blessings

 

[bbunge]

I have flashed Merlin 386.4 on my AC66U_B1 a couple of times with no issues. Mainly going from Asus firmware to Merlin.

You did extract the install from the .zip file before flashing?

 

[pctechtx]

You did extract the install from the .zip file before flashing?

lol, of course.
I have flashed many asus routers to merlin. I'll look into what the checksum should be on the trx file when I have more time (highly likely this will be the cause). This was just the first time encountering this issue and wanted to provide how I got her back up and running in case someone else encountered similar issue. I came close to opening the case and jtaging it for recovery.
One thing I am confused about is during recovery, the last file I flashed was the 3_2 and reset NVRAM. after reboot, it's shows .4
After I check the checksum, I will reflash and if it errors again, I'll jtag it so I can see what is going on in the boot process (if anyone could reference me to the jtag interface location on this device I'd be grateful)...