I have a NanoStation (M5, XW) that I have been using for testing; but now I would like to revert it back to the (UBNT) factory firmware. Most recently, I have been using AREDN 3.16.1.0b01 on this node.
I initially tried to reload the UBNT image using the Setup-Administration Menu; but that fails, providing a message saying "Firmware cannot be updated the uploaded file is not recognized". The image that I was trying to load was from the UBNT site (XW Fw v5.5.10-u2, i.e., "XW.v5.5.10-u2.28005.150723.1358.bin"); which is the same image that I had on the node prior to loading the AREDN 3.16.1.0b01 image for testing. [It is worth noting that when I acquired this node, it had a UBNT XW v5.6.3 image on it; but I reloaded it to this same (XW v5.5.10-u2) image; so that I could then load the "AREDN 3.16.1.0b01" firmware for testing. All that went smoothly back when I did it.]
I then tried to Factory-reset the NsM5, so that I could reload the UBNT BIN file using TFTP. I got the appropriate alternating LED indications; and a response to PING 192.168.1.20; but it repeatedly rejects TFTP connections (even if I use TFTP2.exe). (Yes, my PC was on the 192.168.1.x subnet during this portion of the process. I even disabled my firewalls, but that changed nothing.)
I then tried upgrading the NsM5 to AREDN's Fw3.16.1.1 (i.e., AREDN-3.16.1.1-ubnt-nano-m-xw-squashfs-sysupgrade.bin); and that succeed; but when I tried to again reload the UBNT firmware, I get the same message saying "Firmware cannot be updated the uploaded file is not recognized".
QUESTIONS:
<<< vern >>>
I initially tried to reload the UBNT image using the Setup-Administration Menu; but that fails, providing a message saying "Firmware cannot be updated the uploaded file is not recognized". The image that I was trying to load was from the UBNT site (XW Fw v5.5.10-u2, i.e., "XW.v5.5.10-u2.28005.150723.1358.bin"); which is the same image that I had on the node prior to loading the AREDN 3.16.1.0b01 image for testing. [It is worth noting that when I acquired this node, it had a UBNT XW v5.6.3 image on it; but I reloaded it to this same (XW v5.5.10-u2) image; so that I could then load the "AREDN 3.16.1.0b01" firmware for testing. All that went smoothly back when I did it.]
I then tried to Factory-reset the NsM5, so that I could reload the UBNT BIN file using TFTP. I got the appropriate alternating LED indications; and a response to PING 192.168.1.20; but it repeatedly rejects TFTP connections (even if I use TFTP2.exe). (Yes, my PC was on the 192.168.1.x subnet during this portion of the process. I even disabled my firewalls, but that changed nothing.)
I then tried upgrading the NsM5 to AREDN's Fw3.16.1.1 (i.e., AREDN-3.16.1.1-ubnt-nano-m-xw-squashfs-sysupgrade.bin); and that succeed; but when I tried to again reload the UBNT firmware, I get the same message saying "Firmware cannot be updated the uploaded file is not recognized".
QUESTIONS:
- Why can't I load the "XW.v5.5.10-u2.28005.150723.1358.bin" image using the Setup-Administration menu?
- Any idea why it would be rejecting the TFTP connections?
- Any other suggestions, short of opening it up and muddling around with the serial ports?
<<< vern >>>
It's documented to reflash AirOs from AREND .you have to use TFTP.
Rejecting TFTP connections still sounds like a firewall issue (or other network configuration issue) on your PC Otherwise you should get some sort of error from the device if it had issues (like invalid firmware). I'm doubtful the bootnloader would have issues in this regard having seen the code the boot loader is based on it's a bare basic system, there really isn't room for much to go wrong inbut, statistically all issues are related to the PC doing the flashing.
73s
I just recently bought 2 of the NanoStation Loco M2 (Ver. XW v5.6.12) and with one I upgraded to the XW.v5.6.15.30572.170328.1052.bin. Then I ran the AREDN U-Boot Test Setup Program and the result was V-Bad M-Good. So I then decided to plug in my second device and run the test with the v5.6.12 and I got the same result. So moving on, I then thought I would go ahead and upgrade to AREDN software on both units and I got "Firmware cannot be updated the uploaded file is not recognized" on both.
Did you have any luck loading the AREDN firmware? If so could you send me a quick not on how you did it.
Very much appreciate your help if you can.
Gavin
VA3XRR
(prob would be a good idea to start a new thread on this since the original thread was for a 5Ghz device)
when you SSH to the device (with AirOS), does the command prompt also show "XW"? If so, this is the first XW device on the 2Ghz band that we've encountered.
Please open a bloodhound ticket.
Attach the output of the following commands (via SSH) while running AirOS:
Thanks
Following this thread i hope this is the correct place to ask my question.
I have/had an M5 nanostation XW. DtD link was not working with my other M2 nodes so I went to upgrade to 3.6.1.1 from 3.6.1.0.
After my upgrade failure I realized I uploaded the wrong firmware. I had downloaded XM instead of XW version.?
I now have two LED lights ( the power light is Green and the 4th led is Solid Red. )
The IP address is no longer pingable even after resetting..
Is there a way I can save my M5 nanostation or is it toast ?
Thank you for any help.
Kevin