Upon flashing the initial image of OpenWrt onto this router the Web UI was fully functional, I then proceeded to flash the full version (24x) after which the following occurred:
Web UI is not accessible even after manually setting IP , Subnet , DNS items.
Router does not offer an IP address for itself to the PC or mac.
The ASUS firmware restoration tool can now successfully flash OpenWrt firmware only if it is .bin but fails to flash ASUS stock firmware , I have tested an alternative whereby I modified the ASUS stock firmware file headers, magic, and a few tiny bits and pieces whereby it then successfully managed to flash the stock firmware but the IP issues and lack of Web UI access continued.
I re flashed it with OpenWrt and left it off as I cannot get it to work in a manner that yields connectivity for the system it is intended to offer internet to.
NOTES: The router LED lights and functionality/ies are intact , eg. if powered off and then on while holding the reset button in , it does enter the restoration or recovery mode perfectly, if I do the same while holding the WPS button rapid power LED flash occurs and reset like reboot afterwards. If I plug into it the ethernet cable into WAN port it lights up, same for LAN cable to PC or mac , however WiFi remains off , I even tested this method: I am now using an eero 7 router temporarily until this one is either fixed or my new replacement RT-AX52 arrives this week , basically ethernet cable from eero 7 to WAN port in RT-AX52 and then checking on the eero mobile app on my Android phone it showed it as an OpenWrt device, Manufacturer ASUSTek COMPUTER INC. Security: Unknown and with a valid MAC address, even an eero router assigned IP address, but unfortunately I could not SSH into it no matter what IP I tried or set manually to in order to achieve that if failed on me.
I'm hopeful someone will know and be able to provide me here with clear plain English easy to understand step by step instructions on a process to achieving a working functional state without me prying it open or the option I more recently prior to posting this gave much consideration to which was throwing it out the window. lol That logic aside, Help!
Do not do the above if you used remittor's TRX images. You must flash his ubi cleaner before flashing OEM.
To me it seems like you flashed correctly, unit boots completely, and you likely have your modem/gateway and this router in the same 192.168.1.0/24 subnet.
Failsasfe/recovery requires lan1/port1 to function.
Thanks for that quick response, I might try the TFTP method.
Actually interested in the method just suggested now to me by user: cookiemonster , suggesting to try remittor's 'ubi cleaner' before flashing OEM. Sounds like something that could actually work out.
Hey thank you, I'm actually going to try this 'ubi cleaner' , I will look it up, but just in case, do you have the url link to it by any chance, regardless thanks heaps for the recommendation. I will let you all know how that works out for me when done.
Your unit is not bootlooping, so something is working. Disconnect everything from router except pc connected to lan1/port1 and try to reach failsafe/recovery.
Hey thanks for the reply, I will definitely try it, I have just one question though...
ASUS firmware restoration tool or TFTP ? and if TFTP what should the IP manually be set to , and what should the routers IP manually be set to, ideally and if possible to just give me a short simple 1. in terminal type tftp .... as I am a bit of a developer but it's the more simple/complex depends on who sees what as what that get me
Asus tool removes some bits of a TRX before sending. You can try using tftp in Rescue Mode above: (https://openwrt.org/docs/guide-user/troubleshooting/tftpserver) I can confirm tftp works that way and it seems to flash exactly just like windows tool; however, I have never recovered a unit via this method.
With both methods, you should only use TRX in that mode.