Recent content by SNBForums User

Quite frankly, my RT-AX86U had been working so well for so long on 3004_388.8_0 that I really became mostly unconcerned (as in complacent) with updates. That said, noticed I was behind a few revisions, so I went ahead and performed yet another in a long history of dirty updates, the result of...

Dirty upgrade over 3004.388.7_0 with zero issues encountered after the fact (as is usual).

Merely as another data point, having fairly recently replaced my very-long-in-the-tooth previous Asus router with an RT-AX86U, and after installing 3004.388.7, my also-very-ancient OBi100 VoIP device is still quite happily humming along with these settings, none of which I changed from the default:

Sorry for your difficulties, but this has the quintessential "TLDR:" written all over it...

FWIW, I fairly recently replaced my own long-in-the-tooth RT-AC68U (which was many years ago converted from a TM-AC1900) with an RT-AX86U, and after doing my own due diligence decided that the risk/reward ratio was skewed way too far to the risk side. As a result, I bit the bullet, took a deep...

A successful dirty update on my new-to-me RT-AX86U after many years of the same on my long-in-the-tooth, but now-retired, RT-AC68U (converted from a router whose name shall never be spoken ;)). As with each-and-very of the previous dirty updates on the RT-AC68U, this one on my RT-AX86U completed...

And yet another successful Merlin firmware installation in a long history of "dirty" upgrades on my RT-AC68U (a device whose previous name shall never again be spoken), with perfect success. As a matter of course, I generally wait a few weeks before installing full-incremental releases of Merlin...

Yet another in a multi-year string of successful unwashed upgrades on what is now known as an "RT-AC1900" (aka, a device whose previous name shall never be uttered in this forum, lest you forever suffer banishment) with no ill affects whatsoever. Once again, it's good and I'm happy, or it's...

Living on the edge, I just completed yet another, and for the umpteenth time (it's been at least dozens of times), a "dirty" Merlin firmware upgrade from 386.3_2 to 386.4_0 on my now-really-ancient AC68U (Formerly known in this forum as "The Device Whose Name Shall be Banished Forever and Shall...

And yet another completely successful dirty upgrade on my favorite-of-all time router, formerly and officially known as "the-router-that-may-not-be-discussed in this forum" For those of you who get it, this is a very solid firmware track, as have been the others.

Yep, same hardware, same issue. You did some very good detective work.

Have actually lost count of how many dirty upgrades I've completed on my RT-AC68U since moving to Merlin's firmware, but can add another to the list after moving from 384.19 to 386.1 without any issue whatsoever.

I have occasionally (about every 18 months or so) run into this issue with my ancient and well-used RT-AC68U, which is essentially the same router as yours. When it happens, I SSH into the router and run "for line in `nvram show | grep =$ `; do var=${line%*=}; nvram unset $var; done; nvram...

One more data point of another in a very long history of "dirty" upgrades on my RT-AC68U and one more success, which adds to my many multiple dozens of said "dirty" upgrades over the span of multiple years of Merlin FW installations without a single need for a factory reset---ever. The RT-AC68U...

Yeah, definitely not sticky, but since I only rarely need to reboot between firmware upgrades, stickiness is not really an issue for me. Thanks.