You are here

Firmware Check Failed

8 posts / 0 new
Last post
KY0TES's picture
Firmware Check Failed
Hey All,

I recently tried to update my Nanostation M2 firmware, but in the process, it seems to have failed. Upon initial power-up, the device shows both the first green led and the fourth red led illuminated and nothing happens after that.

I checked the forums to find a fix, and after hours of learning tftp and trying to load firmwares while being in the bootloader mode (the flashing red/green, amber/green) and every time I run the script, it gives me the same two errors (random each time):  Error occurred during the file transfer (Error code = 0): Timeout expired. Retries expired (or)  Error occurred during the file transfer (Error code = 2): Firmware check failed

I can ping using cmd ping, but I can't seem to write to the device.

The network settings include a static IP on, Subnet is, Default gateway is

Anyone have any other thoughts?

Thanks in advance, hope to get this resolved soon!
K6AH's picture
Please post the tftp command
Please post the tftp command you are using.
KY0TES's picture
I used: tftp -i
I used: tftp -i put firmware.bin (obviously the firmware name is different). This is also after changing the directory to where the firmware was put
K6AH's picture
I was wanting to know the
I was wanting to know the entire command with the firmware name.  People tend to want to rename the .bin files for their own convenience, or Windows appends a "(1)" when the file is downloaded a second time.  In either case the tftp will fail.
tftp firmware check

I'm getting similar results.  Using files and  I've run tftp from Windows 7 and from a Raspberry pi 3.  I've run it both in text and binary mode.  On windows I get timeouts after sending a lot of packets.  On the pi I thin it goes all the way through, the last packet is smaller than 512 bytes.  and I get firmware check failed.  Target is a Ubuiqiuty nanostation m2.

AE6XE's picture
some options to confirm and
some options to confirm and try:

1) assumption is your device is older (because you are upgrading it to a newer version of AREDN), thus it is an "XM' device (different cpu than the 'XW' newer devices).    if trying to load the wrong image, you will receive the firmware check error.  If you are are not confident which model you have, then best to try both firmware options, which could be AREDN or AirOS image tftp loads. 
2) With tftp, always use the 'factory' AREDN flavor.    Sysupgrade is the same things, but packaged together in a format know to only Openwrt live firmware.
3) After putting the device in tftp mode, always 'ping' (AirRouter is the exception and different address for ubiquiti models).   If you don't get a response, then don't proceed until it can be ping'd.
4) if your device has ever been upgraded to a newer AirOS version, and this upgrade occured from the UI of AirOS, then the bootloader will be upgraded to an incompatible version with and prior versions.  Attempting to tftp install these AREDN versions will soft-brick the device such that no version of AirOS or AREDN can be installed in the normal ways - have to pull cover and attach to serial hearder and type some special bootloader commands to reover.
5) history of the device of what you have tried tells the rest of us the likely current state.    the specific image you have attempted to load, is important know  if the correct image is used.  The specific image in combination with the history indicates what the likely outcome would be.
6) I always find it tricky to get the laptop to renew IP addresses after flipping from static to dhcp and rebooting the ubiquiti device.   You may need to uplug the cable, turn off/on the interface, or similar to ensure it is in sync.   Also ping to make sure the device is responding before moving forward.


Joe - I know this is an old
Joe - I know this is an old post but I am hoping you can help. I purchased a few Rocket M5 XM radios on EBay and I believe I have the issue you described above with the AirOS version having been upgraded. I have removed the cover and set up a serial connection. Can you share the bootloader commands I would need to get this working?

Jason KC1MLQ
WU2S's picture
Possible help

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer