Thank you, both, so much for your advice. I guess the fifth time was the charm, and I'm updated to 384.13. Have a great weekend!
I've got the same problem... Any tips?
(btw, this is my first post. The issues seem related and the post is recent so I'm asking here. But I will gladly post a new thread if that's what I should do.)
I'm also stuck and unable to upgrade. I'm on 384.06 with my RT-AC68u. I was hoping to go to .13, and it failed (same "issue" as you ... 100 %, then "done," then the page refreshes to the admin console showing it's stuck at old version). I thought that I might be trying to do too many versions to go in one jump. So I've tried version .08 (and .09), trying to stay within 3 versions like the FAQ recommends. I've also download the files multiple times and tried different browsers. I've yet to try the upgrade from another computer, but I'll give that a shot.
I don't have any USB items connected to the router. The router itself has been flawless (it's hardwired via ethernet to a fiber "modem")... I was just hoping to play with mesh. I've rebooted prior to updated. I've unplugged it and left it off for 30-secs to 5 min. None of that make a difference.
What else....I've seen a similar "stop upgrade" message ("rc_service: httpd 282:notify_rc stop_upgrade_ate 1 0"), but it's not always there. Interestingly, right after I attempt the upgrade, my logs are blank and it shows no clients connected. I have to reboot the router to get logs and client count, though then logs only show the months ago, plus the last log since I tried to update. For example, here's the first logged I actually looked at and remembered to today. I think it was around my 3rd attempt. The only previous item shown in the log is back in May. I have no idea where the logs went (or if that's a problem). Here's that log:
[many previous may, april, march, etc snipped]
May 4 22:05:30 ntp: start NTP update
Sep 12 12:00:42 rc_service: ntp 453:notify_rc restart_diskmon
Sep 12 12:00:42 disk_monitor: Finish
Sep 12 12:00:45 disk_monitor: be idle
Sep 12 12:00:45 kernel: *** ERROR: [tdts_shell_ioctl_sig_op_load:95] tdts_core_rule_parsing_trf_load() fail!
Sep 12 12:00:46 rc_service: zcip 578:notify_rc start_firewall
Sep 12 12:00:47 zcip_client: configured 169.254.247.160
Sep 12 12:00:49 nat: apply nat rules (/tmp/nat_rules_ppp0_vlan201)
Sep 12 12:01:04 kernel: SHN Release Version: 2.0.1 3529123_patch
Sep 12 12:01:04 kernel: UDB Core Version: 0.2.14 r3529123
Sep 12 12:01:04 kernel: sizeof forward pkt param = 192
Sep 12 12:01:09 rc_service: ip-up 435:notify_rc start_firewall
Sep 12 12:01:10 kernel: HTB: quantum of class 10001 is big. Consider r2q change.
Sep 12 12:01:10 nat: apply nat rules (/tmp/nat_rules_ppp0_vlan201)
Sep 12 12:01:10 kernel: HTB: quantum of class 20001 is big. Consider r2q change.
Sep 12 12:01:10 kernel: HTB: quantum of class 10009 is big. Consider r2q change.
Sep 12 12:01:10 kernel: HTB: quantum of class 20009 is big. Consider r2q change.
Sep 12 12:01:11 crond[280]: time disparity of 713635 minutes detected
Sep 12 12:02:15 rc_service: httpd 282:notify_rc stop_upgrade_ate 1 0
Sep 12 12:02:15 kernel: klogd: exiting
Any thoughts? I should probably just factory reset, but I've got about a zillion (OK, a dozen) devices configured with parental controls and access times. I really don't want to have to redo them from scratch if I can avoid that.
Cheers!