GT-AX6000 won't update to 3.0.0.6_102.4

[OldManBrodie]

For a few weeks now, I've been trying to update my GT-AX6000 to the newest firmware version. Every single time, it fails. Whether I do automatic via amtm, automatic through the WebUI, or manual through the WebUI, it fails and reboots back to 3.0.0.4.

After reading up a bit on possible causes, I decided maybe I should try to reset to defaults and try again. I tried resetting via the WebUI and the hard reset method (hold WPS button while powering on). Same outcome.

Ok, maybe I'll flash the stock firmware? Same thing: the update fails and it reboots back to 3.0.0.4.

At this point, I'm ready to burn it all down and start fresh, so I put the router into rescue mode (hold reset while powering up, then go to the basic web interface and upload the firmware). I tried several times. Once with the stock 3.0.0.6 firmware, once with the 3.0.0.6 merlin firmware, and just for funsies, once with the 3.0.0.4 merlin firmware. Each time, I waited about 15 minutes for the router to reboot. When it didn't reboot on its own, I power cycled it. When it rebooted, I couldn't access it. My PC even said that the cable wasn't plugged in. I googled around and found a post on here saying "BE PATIENT, it can take up to an hour for the flash to finish and reboot." So once again I put it into rescue mode, uploaded the 3.0.0.6 firmware, and waited. And waited. And waited some more. I'm currently at over 3 hours since the screen refreshed and said "Update in progress." I've been pinging away at the router, and it hasn't missed a single ping. The ROG LED is fast flashing, and the power LED is blinking super slow (like 5 seconds on, 5 seconds off). To all appearances, it's still working on flashing the firmware. But 3 hours seems excessive. At what point do I give up?

What have I missed, screwed up, not tried, etc? People say it's super hard to brick these routers, and while it seems like I can reliably get into rescue mode, I can get no further. Is this router toast?

 

[jksmurf]

There’s been a few folks who struggled with getting devices into rescue mode for various reasons, often after a long period of frustration it is missing one step, that might be worth a try.

See here for some feedback on this, including a dumb one from me; and this post regarding static address on the PC.

You didn’t mention putting the PC you’re trying from onto a static IP address? Unplug and replug the cable, not using the power switch?

I’m guessing your continuous ping follows some of these pointers, pinging the router (although I think the router’s ‘recovery IP’
may now be 192.168.50.1 and not 192.168.1.1).

btw are you sure you’re pressing the WPS button when you hard-reset it, the lettering on some of the identical buttons can be pretty hard to read.

 

[FourthandShort]

For a few weeks now, I've been trying to update my GT-AX6000 to the newest firmware version. Every single time, it fails. Whether I do automatic via amtm, automatic through the WebUI, or manual through the WebUI, it fails and reboots back to 3.0.0.4.

After reading up a bit on possible causes, I decided maybe I should try to reset to defaults and try again. I tried resetting via the WebUI and the hard reset method (hold WPS button while powering on). Same outcome.

Ok, maybe I'll flash the stock firmware? Same thing: the update fails and it reboots back to 3.0.0.4.

At this point, I'm ready to burn it all down and start fresh, so I put the router into rescue mode (hold reset while powering up, then go to the basic web interface and upload the firmware). I tried several times. Once with the stock 3.0.0.6 firmware, once with the 3.0.0.6 merlin firmware, and just for funsies, once with the 3.0.0.4 merlin firmware. Each time, I waited about 15 minutes for the router to reboot. When it didn't reboot on its own, I power cycled it. When it rebooted, I couldn't access it. My PC even said that the cable wasn't plugged in. I googled around and found a post on here saying "BE PATIENT, it can take up to an hour for the flash to finish and reboot." So once again I put it into rescue mode, uploaded the 3.0.0.6 firmware, and waited. And waited. And waited some more. I'm currently at over 3 hours since the screen refreshed and said "Update in progress." I've been pinging away at the router, and it hasn't missed a single ping. The ROG LED is fast flashing, and the power LED is blinking super slow (like 5 seconds on, 5 seconds off). To all appearances, it's still working on flashing the firmware. But 3 hours seems excessive. At what point do I give up?

What have I missed, screwed up, not tried, etc? People say it's super hard to brick these routers, and while it seems like I can reliably get into rescue mode, I can get no further. Is this router toast?

I had the exact same problem and ultimately they replaced the router due to the issue.

One symptom I remember was my Jffs partition was locking (if I recall correctly) and it was having issues unlocking that.

 

[OldManBrodie]

See here for some feedback on this, including a dumb one from me; and this post regarding static address on the PC.

You didn’t mention putting the PC you’re trying from onto a static IP address? Unplug and replug the cable, not using the power switch?

Yeah, I'm using 192.168.1.10 as my static IP for my PC, with a subnet of 255.255.255.0, and no gateway. I can get to the rescue restore mini-web page, so I assume that it's properly entering rescue mode, and that I can connect to it.

Interestingly, I can't TFTP the FW file to the AX6000. It just times out. I tried that as a last-ditch effort, because it was the only way I was able to get an update to "take" on an RT-AX56U a while ago.

I haven't tried the firmware recovery application, as I'm running Linux, not Windows.

I’m guessing your continuous ping follows some of these pointers, pinging the router

Yup, though I missed the part about the TTL. That's interesting, because the TTL was 64 for me, even when I was in rescue mode. I'm not sure if that matters.

(although I think the router’s ‘recovery IP’may now be 192.168.50.1 and not 192.168.1.1).

Rescue is 192.168.1.1, for what I can tell on newer routers. 192.168.50.1 is the default IP after a factory reset.

btw are you sure you’re pressing the WPS button when you hard-reset it, the lettering on some of the identical buttons can be pretty hard to read.

No, I was holding the reset button in back while plugging it in. I think the WPS button is used when you want to factory reset, not go into rescue mode.

I had the exact same problem and ultimately they replaced the router due to the issue.

Huh, well I think mine is 2.5 years old, so I somehow doubt they're going to replace it for me, but I can certainly ask....

One symptom I remember was my Jffs partition was locking (if I recall correctly) and it was having issues unlocking that.

I wonder how I can check that. I can't SSH in, or get to any kind of WebUI besides the rescue page.