Solved GT-AX6000 Rescue

[VonIII]

Just upgraded from an ASUS RT-AC3200 to a GT-AX6000. The GT-AX6000 came with firmware 3.0.0.4.388_23285.

For the hell of it I tried importing my RT-AC3200 config into the GT-AX6000... and it worked! Most everything configured, looked incredible!

But alas, it was too easy, as soon as I upgraded to firmware version 3.0.0.6.102_21514 it went into a frustrating boot loop. I factory reset it several times to no avail. I even clean loaded 3.0.0.4, imported my old config, re-exported, then tried to import that into 3.0.0.6, but still the boot loop. Something in there the router doesn't like, can't blame it I guess trying to load such an old config. And at the same time it's a bit worrying that some odd bit of config can persist like that, you think there would be some validation or config schema to filter it out.

In the end just loaded 3.0.0.6 and i'm going to re-configure from scratch. Probably better in the long run.

And I wanted to post a few nuggets of info here which I was having a hard time finding in one place:

TO FACTORY RESET ASUS GT-AX6000

1. Hold down the WPS button, then power on the router
2. The WPS button is on the BOTTOM FRONT of the router. Probably the last place someone techie will look lol (I'm always focused on the back ports myself)
3. Wait until flashes several times, then power the router off and back on again

TO RESCUE / UN-BRICK AN ASUS GT-AX6000 THAT APPEARS TO BE BRICKED OR IN BOOT LOOP / ENTER RESCUE MODE

Follow instructions below to put the router into "rescue mode" and connect to the mini web interface to upload a new firmware to the device. You'll need a computer or laptop with an ethernet port and a regular ethernet cable.

1. Power off the router
2. Wire a computer with an ethernet port directly to one of the LAN ports
3. Set the ip address manually on the connected computer:
   1. Network and internet settings
   2. Change adapter options
   3. Right-click on Ethernet Connection, get properties
   4. Double click on "Internet Protocol Version 4"
   5. Select "use the following IP Address"
      1. IP address: 192.168.1.10
      2. Subnet Mask: 255.255.255.0
      3. Click Ok, Click OK
4. Hold down the router reset button
5. Power on the router
6. Wait until the LED starts blinking and the power LED blinks slowly (router is in rescue mode)
7. Now you should be able to ping the router at 192.168.1.1
8. Open browser to http://192.168.1.1
9. Click Upload and select the raw firmware file (not the zip) downloaded from ASUS Support for your router
10. Click “Update Software”
11. Browser will show as busy (wheel spinning)
12. Then browser will timeout saying “site can’t be reached” or some such
13. Power cycle the router
14. Switch interface back to DHCP
    1. Follow steps in 3, but instead of "use the following IP Address", select "Obtain an IP address automatically"
    2. Click Ok, Click Ok
15. Open browser, after recovery it’s usually http://192.168.50.1
16. If you have problems connecting after the firmware update:
    1. Type Windows-R
    2. enter "cmd" (without quotes)
    3. hit ok
    4. type "ipconfig" (without quotes)
    5. when everything is working you should have an IP address, and the default gateway will be your router
17. If you have problems connecting when the router is in rescue mode:
    1. Type Windows-R
    2. enter "cmd" (without quotes)
    3. hit ok
    4. type "ipconfig" (without quotes)
    5. when everything is working you should have an IP address of 192.168.1.10
    6. type "ping 192.168.1.1" (without quotes)
    7. you should get a reply
    8. if you have no reply, then power off the router and hold the reset button to get back to rescue mode
    9. make sure the cable between the router and your computer is plugged into a LAN port and you see link lights

God speed, good luck.
-Von

 

[Tech9]

Importing different router settings is not recommended. Reset and Rescue Mode procedures are clearly described in Asus related documents online.

 

[VANT]

I didn't expect that someone would try to import settings from one router model to another one based on a completely different code base. As you can see, I was wrong.

 

[VonIII]

In my defense, I did say I tried it "For the hell of it" - definitely not something I would recommend to the unwashed masses.

 

[VonIII]

Reset and Rescue Mode procedures are clearly described in Asus related documents online.

@Tech9 , for others visiting this thread, can you provide a link and / or documentation referring to what you mention as "Reset and Rescue Mode procedures ... in Asus related documents online." Specifically for GT-AX6000 please.

 

[L&LD]

[Wireless Router] When Standard Reset Isn’t Working: Hard Factory Reset - Models list | Official Support | ASUS USA

Merlin on ASUS ax86U Question

I have an ASUS AX86U and contemplating the installation of Merlin firmware. The DDNS settings on the AX86U are limited to select dns providers. If I install Merlin, will I have more flexability (choices) with the DDNS Settings? Thanks in advance!

www.snbforums.com

 

[VonIII]

Just to be clear - the "ASUS Wireless Router Firmware Restoration Utility" doesn't work with the ROG Rapture GT-AX6000. You have to use the mini web interface as I explain above.

If you can find a video or document that covers that, please link to it. ty!

 

[ualdrivr]

Just upgraded from an ASUS RT-AC3200 to a GT-AX6000. The GT-AX6000 came with firmware 3.0.0.4.388_23285.

For the hell of it I tried importing my RT-AC3200 config into the GT-AX6000... and it worked! Most everything configured, looked incredible!

But alas, it was too easy, as soon as I upgraded to firmware version 3.0.0.6.102_21514 it went into a frustrating boot loop. I factory reset it several times to no avail. I even clean loaded 3.0.0.4, imported my old config, re-exported, then tried to import that into 3.0.0.6, but still the boot loop. Something in there the router doesn't like, can't blame it I guess trying to load such an old config. And at the same time it's a bit worrying that some odd bit of config can persist like that, you think there would be some validation or config schema to filter it out.

In the end just loaded 3.0.0.6 and i'm going to re-configure from scratch. Probably better in the long run.

And I wanted to post a few nuggets of info here which I was having a hard time finding in one place:

TO FACTORY RESET ASUS GT-AX6000

1. Hold down the WPS button, then power on the router
2. The WPS button is on the BOTTOM FRONT of the router. Probably the last place someone techie will look lol (I'm always focused on the back ports myself)
3. Wait until flashes several times, then power the router off and back on again

TO RESCUE / UN-BRICK AN ASUS GT-AX6000 THAT APPEARS TO BE BRICKED OR IN BOOT LOOP / ENTER RESCUE MODE

Follow instructions below to put the router into "rescue mode" and connect to the mini web interface to upload a new firmware to the device. You'll need a computer or laptop with an ethernet port and a regular ethernet cable.

1. Power off the router
2. Wire a computer with an ethernet port directly to one of the LAN ports
3. Set the ip address manually on the connected computer:
   1. Network and internet settings
   2. Change adapter options
   3. Right-click on Ethernet Connection, get properties
   4. Double click on "Internet Protocol Version 4"
   5. Select "use the following IP Address"
      1. IP address: 192.168.1.10
      2. Subnet Mask: 255.255.255.0
      3. Click Ok, Click OK
4. Hold down the router reset button
5. Power on the router
6. Wait until the LED starts blinking and the power LED blinks slowly (router is in rescue mode)
7. Now you should be able to ping the router at 192.168.1.1
8. Open browser to http://192.168.1.1
9. Click Upload and select the raw firmware file (not the zip) downloaded from ASUS Support for your router
10. Click “Update Software”
11. Browser will show as busy (wheel spinning)
12. Then browser will timeout saying “site can’t be reached” or some such
13. Power cycle the router
14. Switch interface back to DHCP
    1. Follow steps in 3, but instead of "use the following IP Address", select "Obtain an IP address automatically"
    2. Click Ok, Click Ok
15. Open browser, after recovery it’s usually http://192.168.50.1
16. If you have problems connecting after the firmware update:
    1. Type Windows-R
    2. enter "cmd" (without quotes)
    3. hit ok
    4. type "ipconfig" (without quotes)
    5. when everything is working you should have an IP address, and the default gateway will be your router
17. If you have problems connecting when the router is in rescue mode:
    1. Type Windows-R
    2. enter "cmd" (without quotes)
    3. hit ok
    4. type "ipconfig" (without quotes)
    5. when everything is working you should have an IP address of 192.168.1.10
    6. type "ping 192.168.1.1" (without quotes)
    7. you should get a reply
    8. if you have no reply, then power off the router and hold the reset button to get back to rescue mode
    9. make sure the cable between the router and your computer is plugged into a LAN port and you see link lights

God speed, good luck.
-Von

I did all of the above that you mentioned before I read your post, on my GT-AX6000. It worked for awhile. I had it wire backhaul meshed with an RT-AX86U. The other day I wanted to reboot the system manually. I shut the main router first (GT-AX6000) and then the RT-AX86U. I turned the GT-AX6000 back on and it was bricked once again. It just refused to boot. I was on with support for ever and they wanted me to send the router in for repair and at my expense of course, since the router is out of warranty! I did not do it then, when it first happened, because it had come back to life after I did the rescue mode reset and the WPS hard reset.

If you ask me it was the firmware update that did it and ASUS doesn't want to address the issue. When I updated from 102_34797 to 102_34810 that's when the router went bonkers....! After all the hard resets and rescue resets, like I said, the router worked for awhile and it was set with the 102_34797 firmware, then it crapped out again when I tried to just reboot it. Pretty upset about it. Expensive piece of equipment and got badly bricked like that??? C'mon...!

Good think the RT-AX86U worked, but I had to reset that one to factory settings, because it was setup as a Mesh Node. I had to redo the whole network again with the AX86U, which BTW is a solid router.

After that, I said eff it..., it's only money...right? So I bought the Beast of a router the ASUS ROG GT-BE98 Pro. The router is massive and it's quad band. The two 6Ghz channels are pretty much useless for now. They have very short range, just like the 5GHz channel used to be when it first came out. They are fast, but you have to be very close to the router to appreciate them. I wire backhauled the AX86U to it again and the Network works pretty well.

The only issue I see is that the majority of the 2.4GHz devises in my house pair a lot easier with the AX86U than with the 2.4GHz channel of the GT-BE98 Pro. I am trying to figure it out why this is happening. I guess they are not used to the new router???? I forced bound a few of them that were closer to the BE98 to the router and they disconnected from the Network for a bit and then they came back on again and stayed with the new Beast of a router for now. We shall see. My settings are the same they were when I had the GT-AX6000/RT-AX86U Mesh system in place.