Cannot upgrade asuswrt-merline firmware from 3004.388.9_2

[wandererm]

Offizieller Support | ASUS Deutschland

Das ASUS Support Center hilft Ihnen Treiber, Handbücher und Firmware-Versionen herunter zu laden. Hier finden Sie auch FAQs und Troubleshooting Hilfen

www.asus.com

Thanks, Colin.
I have tried this method before. The ASUS restore utility could NOT find my router even I have set the router in the rescue mode (slow blinking power light).

 

[ColinTaylor]

The ASUS restore utility could NOT find my router even I have set the router in the rescue mode (slow blinking power light).

In which case instead of using the Asus utility try pointing a web browser at http://192.168.1.1 and seeing if you get the CFE miniWeb Server interface. You can upload firmware images through that.

 

[John Fitzgerald]

Leave the power switch in the on position and unplug the power at the back of the router for 1 minute. Plug back in and try to flash ASAP.
Also, clear browser cache prior to above.

Sometimes you get a bad download, so also delete all old downloads and get a fresh download, also prior to above.

Standard is 192.168.50.1 for this unit and ASUS is keyed to that.

 

[wandererm]

In which case instead of using the Asus utility try pointing a web browser at http://192.168.1.1 and seeing if you get the CFE miniWeb Server interface. You can upload firmware images thro

In which case instead of using the Asus utility try pointing a web browser at http://192.168.1.1 and seeing if you get the CFE miniWeb Server interface. You can upload firmware images through that.

Unfortunately, it's not reachable. It seems that there was not webserver available for my router in the rescue mode.

 

[wandererm]

Leave the power switch in the on position and unplug the power at the back of the router for 1 minute. Plug back in and try to flash ASAP.
Also, clear browser cache prior to above.

Sometimes you get a bad download, so also delete all old downloads and get a fresh download, also prior to above.

Standard is 192.168.50.1 for this unit and ASUS is keyed to that.

Oh. 192.168.50.1? Ok, never tried that b4. The document was asking to set a laptop on 192.168.1.10/24. I will need to change my laptop to 192.168.50.10/24 then? I will give it a try. Thanks, John!

 

[ColinTaylor]

Oh. 192.168.50.1? Ok, never tried that b4. The document was asking to set a laptop on 192.168.1.10/24. I will need to change my laptop to 192.168.50.10/24 then? I will give it a try. Thanks, John!

Rescue mode always uses 192.168.1.1.
192.168.50.1 is the address to use when the router has booted up normally.

 

[ColinTaylor]

Unfortunately, it's not reachable. It seems that there was not webserver available for my router in the rescue mode.

There is a webserver for your router. If you can't reach it that would indicate that the router isn't in rescue mode (or your PC is not configured correctly). If you don't get the timing of the power and button presses quite right it will not go into rescue mode.

To check whether the router is reachable and in rescue mode run a constant ping (ping -t 192.168.1.1) from your PC and note the TTL value. In rescue mode the TTL will be 100.

 

[wandererm]

wwwwwwwww

There is a webserver for your router. If you can't reach it that would indicate that the router isn't in rescue mode (or your PC is not configured correctly). If you don't get the timing of the power and button presses quite right it will not go into rescue mode.

To check whether the router is reachable and in rescue mode run a constant ping from your PC and note the TTL value. In rescue mode the TTL will be 100.

Ok, so what's the legit way to verify it?
I followed the instruction, tried unplug/plug-in with the reset button pushed, wait for few seconds until the power light slowly flashing, then released the reset button. How could the router not be in the rescue mode?

 

[ColinTaylor]

To check whether the router is reachable and in rescue mode run a constant ping (ping -t 192.168.1.1) from your PC and note the TTL value. In rescue mode the TTL will be 100.

If the ping is correct but you can't get to the web server it may be your browser interfering with things. Try the browser's "safe mode" or another PC/browser.

 

[wandererm]

Thanks. I will give it a try. I did get the ping back from the router but I didn't pay attention to the TTL.
BTW, the SSH was not available either. If it's not in a rescue mode (will that be a normal boot then?), I should be able to SSH in, right?

 

[ColinTaylor]

Thanks. I will give it a try. I did get the ping back from the router but I didn't pay attention to the TTL.

If the TTL is correct but you can't reach the webserver it might be your browser. Some browsers forcibly redirect HTTP connections to HTTPS, which won't work here.

BTW, the SSH was not available either. If it's not in a rescue mode (will that be a normal boot then?), I should be able to SSH in, right?

SSH is only available if you've enabled it in the router's settings. It's not enabled by default.

 

[wandererm]

SSH is only available if you've enabled it in the router's settings. It's not enabled by default.

I know. I meant for my configurations, a normal boot should have the SSHd launched on my router. In this case, I could not get a SSH connection. That made me thinking the router was indeed in the rescue mode.

 

[ColinTaylor]

I know. I meant for my configurations, a normal boot should have the SSHd launched on my router. In this case, I could not get a SSH connection. That made me thinging the router was indeed in the rescue mode.

That sounds logical.

 

[John Fitzgerald]

If you changed your main setup from 192.168.50.1 to 192.168.1.1, change it back to 192.168.50.1 until you can get the flash to work properly.

Also try to flash to 10_2, the one between .9_2 and and .11, just to see if it goes???

 

[wandererm]

If you changed your main setup from 192.168.50.1 to 192.168.1.1, change it back to 192.168.50.1 until you can get the flash to work properly.

Sorry, I didn't follow.
My router is configured with 192.168.18.1 as the LAN IP.
Booting the router to the rescue mode would change it to the default IP 192.168.1.1 address. But for my case, the ASUS utility could not find it from a PC with 192.168.1.10/24 static IP. (As you have seen above, I could ping the router 192.168.1.1 addrss; but I could not access the web interface)
I don't think I need to change my setup to 192.168.1.x subnet.

 

[John Fitzgerald]

Sorry, I didn't follow.
My router is configured with 192.168.18.1 as the LAN IP.
Booting the router to the rescue mode would change it to the default IP 192.168.1.1 address. But for my case, the ASUS utility could not find it from a PC with 192.168.1.10/24 static IP. (As you have seen above, I could ping the router 192.168.1.1 addrss; but I could not access the web interface)
I don't think I need to change my setup to 192.168.1.x subnet.

I'm saying you altered the default setup. Change it back to stock until you can get it to flash, then go back to whatever you want long term.

Stock is 192.168.50.1

 

[wandererm]

I'm saying you altered the default setup. Change it back to stock until you can get it to flash, then go back to whatever you want long term.

Got it. But I wonder what's the purpose as the rescue mode would change the router IP to 192.168.1.1 anyway?
Oh, got that. You meant change it to the stock IP 192.168.50.1. Sorry, missing that part.

 

[wandererm]

Are you saying I can change the router IP and try to upgrade the firmware in "normal mode"? Still, why does it make a difference? Just curious.

 

[John Fitzgerald]

Are you saying I can change the router IP and try to upgrade the firmware in "normal mode"? Still, why does it make a difference? Just curious.

ASUS expects it that way.

Also try a normal flash of the most recent Stock ASUS Firmware to see if it goes, then go back to RMerlin firmware if it takes.

Keep everything stock.

 

[wandererm]

ASUS expects it that way.

Just to confirm, you meant the upgrade is done in "normal mode", right?