Rocket M2 to upgrade to 3.20.3.0 fail

23 posts / 0 new

Fri, 04/03/2020 - 15:16

NH6WR

My bad but now what? Accidentally loaded 3.20..3.0-ar71xx-ubnt-bullet-m-sysupgrade.bn into an older Rocket M2 XM. I am unable to connect to the rocket now using the localnode: 8080 address with DCHP or static ip of https://192.168.1.20 with my laptop set static ip of 192.168.1.100

I have tried several times now using the reset button on the rocket with no success. Is it bricked for good?

Thanks-

Fri, 04/03/2020 - 15:48

K5DLQ

can you connect to it over RF

can you connect to it over RF via another mesh node?

Fri, 04/03/2020 - 15:55

nc8q

Installing firmware with tftp

I cannot tell which 'reset button' procedure you followed, but with incorrect firmware installed, this may not help Test if device can be found with another node on the same bandwidth. If yes, upgrade via RF with sysupgrade.bin. Else, TFTP the correct factory.bin. ;-) Chuck Appendix Failsafe Mode Failsafe Mode is a method of restoring a node to an operational state. Reset Password or DHCP: After the node fully boots press and hold the reset button for 5 seconds which will cause the unit to enable DHCP and reset the root password to 'hsmm'. Full Failsafe: After the node fully boots press and hold the reset button for 15 seconds which will cause the unit to behave as if it had just been flashed with the AREDN™ firmware. You would need to go through the node settings again just as if it was the first time installing the AREDN™ firmware on the node. Installing firmware with tftp

Fri, 04/03/2020 - 18:45

(Reply to #3) #4

NH6WR

The Node at issue cannot be

The Node at issue cannot be seen by any other node and the only LED light is the pwr green LED that will stay lit. I have tried the long press on the reset button which causes the sixth LED light to flash off and on at which time I will release the reset button and it seems to reboot but will not allow a local node 8080 connection. I guess it is possible it has located onto a different channel?

Fri, 04/03/2020 - 22:23

(Reply to #4) #5

K6CCC

TFTP it.

Fri, 04/03/2020 - 22:33

(Reply to #5) #6

NH6WR

TFTP it ?

I am not sure what that would entail and probably do not have the tools .... Certainly someone has put the wrong firmware in before, maybe my unit just went bad in the middle of the upgrade?

Sat, 04/04/2020 - 02:20

(Reply to #6) #7

nc8q

TFTP it

https://arednmesh.readthedocs.io/en/latest/arednGettingStarted/installing_firmware.html

"Ubiquiti First Install Process Ubiquiti devices have a built-in TFTP server to which you can upload the AREDN® factory image. "

Sat, 04/04/2020 - 13:06

NH6WR

Access to the unit

By the way, thank you guys for the response. I am not sure how I can upload any software if I cannot access the unit via either by RF or plugged in LAN?

Sat, 04/04/2020 - 13:17

(Reply to #8) #9

K5DLQ

if you put it into TFTP mode

if you put it into TFTP mode (ie. power off, hold reset, power on, wait 30 secs for alternating leds 1-3, 2-4), release reset button, set pc to static ip of 192.168.1.5, ping 192.168.1.20 (if successful, proceed), tftp the factory file to 192.168.1.20 (using binary mode).

Sat, 04/04/2020 - 19:08

#10

NH6WR

TFTP mode

Thank you K5DLQ, I was able to get the light show with an alternating (1=green, 3=red,5=green) and ( 1=green, 4=orange, 6=green). however my ping test completed with the light show going was this:
Pinging 192.168.1.20 with 32 bytes of data:
Reply from 192.168.1.5: Destination host unreachable.

Sat, 04/04/2020 - 19:22

(Reply to #10) #11

K6AH

The instructions go on to say

The instructions go on to say...

Continue holding the device’s reset button for approximately 30 to 45 seconds until you see the LEDs on the node alternating in a 1-3, 2-4, 1-3, 2-4 pattern, then release the reset button.
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:

[Windows with command on a single line]
> tftp -i 192.168.1.20 put C:\temp\aredn-3.19.3.0-ubnt-nano-m-xw-factory.bin
The TFTP client should indicate that data is being transferred and eventually completes.

Watch the LEDs for about 2-3 minutes until the node has finished rebooting. The reboot is completed when the LED 4 light (farthest on the right) is lit and is steady green.
Configure your computer’s Ethernet network interface to use DHCP for obtaining an IP address from the node. You may need to unplug/reconnect the Ethernet cable from your computer to force it to get a new IP address from the node.
After the node reboots, open a web browser and enter the following URL: http://localnode.local.mesh Some computers may have DNS search paths configured that require you to use the fully qualified domain name (FQDN) to resolve localnode to the mesh node’s IP address.

Sat, 04/04/2020 - 19:22

#12

NH6WR

TFTP mode

Hey on the second attempt at getting into tftp mode I had success with the ping to 192.168.1.20
Now I need to come up with old factory firmware for the old ubiquiti rocket M2 XM I am not sure of the proper file from https://www.ui.com/download/unifi/

Sat, 04/04/2020 - 19:32

#13

NH6WR

TFTP mode and putting in the correct file

I have an older M2 Rocket, I believe it is an XM and not a XW, how can I tell? I was able to find this file name XM.v6.2.0.33033.190703.1147.bin
what would be the Command in windows 10 to put this file into the router assuming the said file is located in my download folder? Thanks-

Sat, 04/04/2020 - 21:02

#14

NH6WR

Firmware image check failed. Error code: 43

This command worked-

C:\Users\nh6wr>tftp -i 192.168.1.20 put C:\users\nh6wr\downloads\XM.v6.2.0.33033.190703.1147.bin
Transfer successful: 7595970 bytes in 19 second(s), 399787 bytes/s

I am now able to get into the ubiquiti software and when I try and and upload AREDN factory software I get this message from Ubiquiti and now I am stuck again!

Firmware image check failed. Error code: 43

Sat, 04/04/2020 - 22:55

(Reply to #14) #15

KE2N

With Ubiquiti software later

With Ubiquiti software later than ~6 you cannot load third-party software using the OEM program.
Starting from OEM, you have to use the tftp method with the AREDN software (like you just did with XMetc)..

Once you have AREDN happily running on your radio, then you can use the AREDN upload feature for future updates.

Sat, 04/04/2020 - 23:03

#16

K5DLQ

you just confirmed that you

you just confirmed that you have an XM device.
you cannot install AREDN via the AirOS GUI anymore as Andre said. (you must use TFTP)

now, download the aredn FACTORY file for your rocket-m (XM).
do the SAME TFTP process except now use the aredn file (above)

Sat, 04/04/2020 - 23:11

#17

NH6WR

Now when I go thru the tftp

Now when I go thru the tftp procedure and get to the alternating (1=green, 3=red,5=green) and ( 1=green, 4=orange, 6=green). and get a successful ping test. Uploading any factory file for the rocket M2 just hangs. there is no response after the CMD
ftp -i 192.168.1.20 put C:\users\nh6wr\downloads\aredn-3.20.3.0-ath79-ubnt_rocket-m-factory.bin

The rocket just hangs with the first green LED and the orange fourthLED and the last green LED. even after 15 minutes. So still stuck, tried it twice.

Sat, 04/04/2020 - 23:21

(Reply to #17) #18

K5DLQ

ok. that is strange.

ok. that is strange.

I had a similar experience with one my "test" bullets. I chalked it up to too many firmware loads/reloads during development. I ended up TFTP loading AirOS. Then, in the AirOS gui, loaded progressively older AirOS versions until I got back to AirOS 5.5.x. Then TFTP loaded aredn and it worked.

This sounds very similar.

Sat, 04/04/2020 - 23:35

#19

NH6WR

how do I access older OS

how do I access older OS firmware files? I bet it would go with an older version of OS and use its upload feature? Thanks. My wife is in working on a jig saw puzzle and this has turned out to be my puzzle ;-)

Sat, 04/04/2020 - 23:54

#20

NH6WR

C:\Users\nh6wr>tftp -i 192

C:\Users\nh6wr>tftp -i 192.168.1.20 put C:\users\nh6wr\downloads\aredn-3.20.3.0-ath79-ubnt_rocket-m-factory.bin
Transfer successful: 6357404 bytes in 16 second(s), 397337 bytes/s

After a couple more attempts I was able to get the tftp upload to take....maybe this time I removed the LAN cable from the laptop during the reset button and inserting the LAN cable light show procedure.

but after the the rocket going thru its uploaded firmware routine and supposed reboot, the rocket stops with just the 1st green LED on and no others.
and so far no connectivity.

Sun, 04/05/2020 - 00:29

#21

NH6WR

back to the OS software

After a successful up load of the AREDN factory software above the unit would not boot to completion with the last green LED lit and unable any connectivity to it. I went back to a working AirOS and back to being unable to upload from the gui... because of the after 6 version. Can someone help me locate older versions back to AirOS 5 ?

Image Attachments:

Sun, 04/05/2020 - 22:34

(Reply to #21) #22

K5DLQ

i did a quick google search

i did a quick google search and found this:
https://ubnt.repair/download/firmware/XM/

Mon, 04/06/2020 - 11:46

#23

NH6WR

Resolved

Thank you K5DLQ.
The rocket anomaly has been resolved after numerous failed attempts of TFTP any AREDN software tried for the Rocket XM.
What worked was using
tftp -i 192.168.1.20 put C:\users\nh6wr\downloads\XM.v5.6.15.30572.170328.1107.bin which i believe is the unsigned version of software-

and using the Gui on the administration page of AirOS to load 3.19.3 factory . The rocket would hang with trying to GUI upload of 3.20.3.0 either from the AirOS gui or the gui with AREDN administration page. I did try a second downloaded file in case the original 3.20.3.0 file downloaded was corrupted
Thanks to all who commented..

Amateur Radio Emergency Data Network

Menu SF

You are here

Rocket M2 to upgrade to 3.20.3.0 fail

Amateur Radio Emergency Data Network

Search form

Menu SF

You are here

Rocket M2 to upgrade to 3.20.3.0 fail