Nanostation M2 Firmware Download

I have a ubiquiti nanostation M5 (XM version board) which was shipped to me with airOS firmware version 6.x.x installed. I am trying to use the device as a station/client to connect to an access point which requires connecting with EAP-GTC. I have asked on the airOS forums, and this type of authentication method is not supported on airOS. Therefore, I thought in order to solve the problem, I would start trying to do some hacking on openWRT in order to connect to this access point if GTC auth is not already supported by default.

This is where the nightmare began. There are many conflicting and outdated reports out there about how to flash UBNT ; the problem is in general after some version (5.6.x I believe) of airOS, only 'signed' firmware is able to be flashed. There do not seem to exist any 'signed' firmware prior to this version, and none of the methods I have found online allow you to bypass this signing restriction to load openWRT.

Download File 🔥 https://urluso.com/2y7Z7o 🔥

-reverted from 6.x.x to 5.6.x (the earliest 'signed' version available), and tried to load earlier firmware from the web interface. (gives 'untrusted' error)

-booted the nanostation in TFTP recovery mode and used tftp client to try to push either 5.5.x airOS or openWRT. ("Error code 2: Firmware check failed" after upload)

-booted normally and used ssh to copy over 5.5.x version, and tried to start update using ssh following this guide ( -ubnt-nanostation-m2-loco-xm-ubnt-downgrade-code2-msgfirmware-check-failed/) (get "Firmware update file check failed!" in the ssh session)

-found that the binary in /sbin/fwupdate was actually a shell script, and the check was a separate process/program. copied /sbin/fwupdate to /tmp/fwupdate and edited the sh script to not perform the check. (device said it updated and rebooted, but it was just back at 5.6.x again after this)

I believe I am getting out of my league here ; does anyone know in the community if anyone has successfully found some way to load / get back to older firmware on these devices, or am I stuck with something useless for my purposes?

Hi all,

I'm trying to upgrade new tiny firmware 22.03.5 on Nanostation Loco M2 (XM version) but it accept only nanostation XM firmware (and not Loco as it should be) so our Loco stop working because they don't see address.

Hi mk24, thanks for your answer. I already tried to replace the firmware with the openWRT factory days ago, and it worked with no problem; the problem is when I try to install the upgrade. Then I 'd like to know why the device accept the Nanostation XM firmware and not the Loco one's

There is a serious shortage of RAM in this model thus I suggest TFTP installs instead of using sysupgrade as the latter requires storing the whole new firmware in the RAM disk while OpenWrt is running. You can backup your configuration to restore after TFTP flashing.

Thanks a lot mk24. I know I need no upgrade after installing last firmware version. As I told you I already made installation via TFTP with factory file with no problem, but I have a lot of Nanostation Loco all around Campus and restore a configuration backup (for all) after a factory flash is not an exiciting idea.

Thanks for the info. Unfortunately when I ordered it, there was nothing stating what the firmware version was, so I had only the model number to go on. I have found that ticket and seem to be making progress on it.

Thanks and 73s

Chris

Anyone have an idea how we can be sure we we'll get XM versions when we order? Is there a vendor we can order from that would know the firmware version? I ordered through Amazon and there was no way to know?

Bob, W7REJ

Easy, eh? How would I have known to do this? Where would I have found this detail? That bit of info is not mentioned on the Supported Platform Matrix. Does this mean that the nightly build will install as an AREDN flash over the UBNT XW firmware? What happens if the flask bricks the hardware? Isn't the nightly build experimental? Is it really that easy. Is this true for the NS Loco as well?

Bob, W7REJ

Hi Bob,

Well, easy to "fix"... not as easy find the info without some bookmarks (we are working on that)

[LINKS REMOVED]

With these nightly builds: (no AirOS downgrade required)

You can load the AREDN nanostation xw "factory" firmware directly over AirOs 6.0.4 and below via the AirOS GUI.

You can load the AREDN nanostation xw "factory" firmware directly over any version of AirOS via the TFTP procedure.

If the flash does work properly for some reason, a TFTP load will usually work to recover it. (99% of the time)

However, with nightly builds be prepared to do TFTP and possibly use a serial console (attached to the circuit board) to do a serial recovery. (rare)

FYI: The nightly builds DO NOT WORK for the Bullet and PowerBeam 620 devices yet, IF YOU SKIP THE AIROS DOWNGRADE STEP. We are working on the fixes for those now. If you have a Bullet and PB620 AND want to use nighly, you must downgrade AirOS to 5.x FIRST (as you have been).

since you applied AirOs 6.0.3, that has a "signed" bootloader and will only load Ubiquiti firmware. You need to look on UBNT downloads site and find an "UNSIGNED" firmware (which will load any firmware) and load it. Then, start the AirOs downgrade.

Alternatively, you can load the AREDN nightly build on any version AirOS, as long as you load via the TFTP method.

The newer versions of AirOS UI expect signed firmware and only accepts a limited AirOS version downgrade. The tftp process does not expect signed firmware. 'tftp' the nightly build directly to this device does the trick. Use the nano-m-xw factory firmware.

Joe AE6XE

Just go to Tools > Software Upgrade in the Elevated radios GUI and upload the Ubiquiti firmware file. After it finishes the flashing process, it will come back up just like it was before being elevated.

Upon, simply loading the UBNT firmware into the Elevate UI under the software upgrade window (as you would normally upgrade the firmware on a Cambium device), I have lost access to the device. Neither discovery tool will find it, and I cannot ping the IP at all.

It sounds like something went wrong flashing it... I've had that happen with quite a few ubnt radios recently (not just going between Elevate and ubnt firmware, but more so just updating the ubnt firmware to newer versions).

When your nanostation is bricked, or if the stock firmware won't let you flash our custom firmware, you can use the In-System Programming (ISP) technique to reflash the device (see also the Flashrom wiki. You're going to need:

The problem is, that AirOS 6.0.6 needs signed firmwares and even original firmwares seem to miss a valid signature for this purpose. Hence TFTP is always failing with ubnt downgrade code=2, msg=Firmware check failed. (Of course the web interface behaves likewise.

tftp of the current firmware loaded went through just fine: C:\Users\Mark>tftp -i 192.168.1.20 put XM.v6.1.4.32113.180112.0932.bin

Transfer successful: 7567044 bytes in 22 second(s), 343956 bytes/s

Second: What device are you on, exactly? This article was written in respect to Nanostation M2 Loco (XM) only. I am sure the procedure also works with other devices as well, but only if -and only if- you have the correct firmware file. Have a look at the corresponding threads at community.ubnt.com for details on that.

If the firmware update does not complete after multiple attempts, or if the airOS GUI is completely unreachable then it might be necessary to do a TFTP recovery on the device. Follow our TFTP guide here.

These devices are programmed to download a boot image from an external source. Your computer can run a PXE server which can give the node an IP address via DHCP as well as providing the firmware image via TFTP.

The recommended method for installing AREDN firmware is to download and follow the appropriate Install Checklist below which matches your device hardware. Additional descriptions are also provided in the sections that follow.

Open a command window on your computer and execute a file transfer command to send the AREDN firmware to your device. Target the default IP address of your Ubiquiti node, such as 192.168.1.20 (or 192.168.1.1 for AirRouters). The following is one example of TFTP commands that transfer the firmware image to a node:

Before you install AREDN firmware on a Ubiquiti 802.11ac device, you must first make sure it is running a specific version of the standard Ubiquiti AirOS software. This procedure will not work if the device is running any other version. Fortunately you can upgrade or downgrade the standard Ubiquiti software.

Once the upgrade has been completed, the device will return you to the login page. Log in using the username and password you created earlier (admin / admin!23). Once again you will see the System page and if everything has been successful, the firmware version will now read either WA.V8.7.0 or XC.V8.7.0 and you can move to Step 2.

The upgrade can fail on newer hardware which requires 8.7.4 firmware. This problem has only been observed and tested on newer LiteBeam 5AC devices. For these devices, follow the same firmware downgrade procedure but use the following firmware instead:

To install the AREDN firmware you first need to create a program to do this. Ubiquiti devices expect signed firmware but AREDN is not signed, so we need to bypass the checking process. To do this type or copy/paste the following two commands:

These commands take the standard Ubiquiti program used for flashing new firmware and change a few bytes to create our own version with the signature checking code disabled. The first command can take a little while to complete but when successful will return you to the shell prompt.

You may experience an issue during installation of the sysupgrade.bin file on Mikrotik devices having RouterOS v7. If your Mikrotik device came with a Current Firmware version of v7.x you can follow the instructions on this page (OpenWRT - downgrading RouterOS) to downgrade Mikrotik RouterOS prior to flashing the AREDN firmware. You can find the earlier firmware on the Mikrotik Download Archive. Download the ARM version (routeros-arm) for devices that use the ipq40xx AREDN firmware, or download the MIPSBE version (routeros-mipsbe) for other Mikrotik devices. You need to download a v6 RouterOS version that is equal or newer than the RouterOS version shown in the Factory Firmware field on your device (as in the example image). 006ab0faaa