First of all thanks to all involved in creating this firmware and supporting it.
Ok today I got my new asus rt-nt16 router, without even trying to use in stock I started the process of flashing the shibby 104 build (I think his latest) I used the AIO USB build. filename tomato-K26USB-1.28.RT-MIPSR2-104-AIO.trx.
First attempt I thought I bricked router, after waiting 8 mins or so I power cycled it, wireless would never come up, pings returned a routing error and wasnt good situation. When attempting to go into recovery mode, it would only stay in recovery mode with no lan cable connected, whenever one was connected it exieted recovery mode so I thought all was hopeless.
I then read somewhere holding WPS down to create a rapid flashing light on boot was useful to get recovery mode working again, this worked for me and recovery mode was fixed. I reflashed asus firmware and that worked so device not bricked good.
I then tried again the same firmware file this time leaving it for much longer 15 minutes, eventually it started pinging, and the interface worked.
Spent 10 minutes or so configuring, wireless security, isp settings etc. All seemed fine didnt notice any issues. But did not do a nvram wipe first(I think was supposed to?).
Shutdown the router using its built in shutdown command and unplugged it, moved it next to my modem, plugged in all lan and wan cables.
Then noticed on my android wifi analyzer which was still running the wireless signal was gone, pinging from my pc was yielding again failures (like the previous failed flash) and thought how is this happening when was all fine before moving it. I power cycled it, no go and waited, then about 5 minutes later the wireless comes to life, it starts pinging and everything works.
So the question is this normal for such a slow boot process, or is this indicative something is wrong, is there a boot debugging feature? maybe wiping nvram? or different older firmware is more stable?
Thanks in advance.