Zen xt12 rescue mode not working - help needed

[tcp]

zEN pro xt12 failed during firmware upgrade. I tried the firmware restoration utility : https://www.asus.com/support/FAQ/1030652/


I changed the ip address in TPC TCP/IP V4 to 192.168.1.100 and other ip s such 192.168.1.1, 192.168.50.1 with subnet to 255.255.255.0 and used the upgrade utility with the firmware image but I keep getting message searching for ip address and then connecting to wireless device. The router is in rescure mode with white led on the top flashing

Have it bricked it. Can someone help anything I do try to recover.

 

[ColinTaylor]

Disable your PC's Wi-Fi adapter.

Run a continuous ping from your PC to the router to confirm the Ethernet cable connection. So on Windows that would be:

ping -t 192.168.1.1

 

[tcp]

it is pinging successfully. "packet sent 4 recieve 4. Loss 0"

 

[ColinTaylor]

What is the TTL being returned by the ping?

 

[tcp]

What is the TTL being returned by the ping?

128

 

[tcp]

ping

 

[ColinTaylor]

Try opening a browser and going to http://192.168.1.1

Do you see a recovery menu?

 

[tcp]

no no recovery menu. and doent connect to above ip in browser

 

[tcp]

first theis recovery tool searches for ip address and then wireless ip address and then says router not in recovery mode. bUt it is in recovery mode. a white lite constantly flashing

 

[Tech9]

Leave the continuous ping running, try WPS hard reset, Rescue Mode after and when you see a ping response try the default LAN IP again. What is suggested above is getting to mini CFE Web server. Some browsers restrict http access, try different one. Leave the recovery tool alone for now.

 

[tcp]

tried the above. Default ip adrress of 192.168.50.1 or 192.168.1.1 provide page not dispalayed , no connection ( on opera, ie explorer, chrome and firefox). Pinging with no probs

 

[L&LD]

Be sure you're using 'incognito' mode (or equivalent, for the browser you're using).

Reboot your computer. Clear the cache of each browser before you try connecting. Be sure you close the windows fully, and are not just minimizing them.

Hope you are not really using ie explorer. If you are, try Edge, instead.

 

[Tech9]

zEN pro xt12 failed during firmware upgrade

By the way, was it auto firmware update?

 

[tcp]

Possibly . As auto firmware update was on.


When the router starts it displays mostly green lights good few times and one or two times white red and keeps having green lights. It does not coonect via lan connection to another router or to the PC. No lan port when on. Butlan port blinking in rescue mode occurs and ping goes through.

I tried sevral times the above. Nothing else is openeing up in the browsers ( in incognito mode). Does it look like irreperable?.

 

[Tech9]

Does it look like irreperable?

What you need to do is described above. If it doesn't work no matter what you have tried - RMA is your only option. Must be covered by warranty.

 

[tcp]

192.168.50.1 would be the routers IP so try using 192.168.50.2 with default gateway 192.168.50.1

View attachment 54367

Still cannot open the webpage with router default address. I can ping 192.168.50.2. But not 192.168.50.1


Neither the recovery tool is able to search the IP address

Are there any other recovery tools that I could give a try

 

[ColinTaylor]

Default on XT12 is 192.168.50.1

View attachment 54371

That is the default LAN address when the router is working normally. I don't know about the XT12 but with other Asus routers that have 192.168.50.1 as the default LAN address their recovery IP is still the old 192.168.1.1 address. This seems to be borne out by the OP being able to ping 192.168.1.1 but not 192.168.50.1.

 

[KevTech]

This seems to be borne out by the OP being able to ping 192.168.1.1 but not 192.168.50.1.

But what was he setting to get this response?
I wonder as he was also getting a response at 192.168.50.2

I can ping 192.168.50.2

 

[ColinTaylor]

But what was he setting to get this response?

When getting a response from 192.168.1.1 I assume he was using 192.168.1.100 which he mentioned first or 192.168.1.10 which is stated in the FAQ he was following.

I wonder as he was also getting a response at 192.168.50.2

In that case you had asked him to set his PC to be 192.168.50.2 so he was pinging himself. But still no response from 192.168.50.1.

 

[majika]

I've not read full post just parts so here as just some handy little cmd lines to help locate a missing device IP if all else fails

Passive, probing
> arp -a
see what IP's is broadcasting on your iface net..
next run
> netstat -a
> netstat -aof | findstr :8443 <== or whatever you may have changed the GUI default access port number to..
Search by default port number maybe of help to spot what IP your router maybe sitting on.

Destructive
> ipconfig /flushdns
$ ipconfig /release & /renew

It could be a previous cached session page in browser so go back to your last know IP reload that page up again then "ctrl + F5" to clear out any cached page or go incognito as above.. Try for http://<ip>:80 | http:<ip>:8443 | https://<ip>:8443

Also ipv6 https://[ffee:abcd:ffee::1]:8443 <== If you have ipv6 enabled this maybe a way back in but you need to look for the ipv6 addy for that device 1st.

also can search by local domain i forget what they are now.. like https://asusrouter.com:8443 is one I think...

HTH's