I have a 5g nano xm that had been working with the 3.19.x.x software. When I tried updating to 3.20.3.1 using UI the lights on the node all flashed and then only the green power light on the left side remained on. I tried to tftp it and it does not respond at all. I cannot make it do anything.
You are here
bricked m5 nanostation
Sun, 01/03/2021 - 15:37
#1
bricked m5 nanostation
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer
The left green light is all that comes on. It is on steady, not blinking.
It appeared that the node was updating and that screen was showing and after a few minutes the screen went blank and said it could not connect. I opened a new screen and typed localnode:8080 and nothing happened. I noted only one green light on the left side, which did not seem right and that is when I powered off and tried to tftp.
I should have described the event in better detail. I have had the screen go blank after an update before and it usually meant it has loaded.
In any event, where do I go from here?
Thanks for your thoughts.
Itried 192.168.1.20 with no response. I didn't try the 1.1 address
Also connect the computer and node through a simple Ethernet switch (dumb switch) so that the switch can maintain the computer’s network link while the node is being rebooted. That may help in the TFTP mode.
Denis
I have been using a switch as xw's seem to need that.
I can get it into tftp mode but the address is not a ubiquiti address. I think it must have an aredn address since that's what it was opersting on before bricking. When I push reset, the far right green light flashes at a quick rate for 10seconds or so and then there's a flicker from the center lights and then all go out except for the left green light. It goes into tftp mode but don't know where to go from there.
Your node should respond to 192.168.1.20 and I see you have been here for a few years but I have to ask is your PC in static mode?
Denis
It is in static mode.
Let me refresh. I have a nanostation that is xm and has had aredn software on it for several years. I was updating using UI when ithe computer screen went blank and the node lights blinked off. After a minute the left green light came on solid. I have tried the reset button and the right light flashes and then goes back to the lleftt green light on solid. I have set static at 192.168.1.40 and tried 192.168.1.20 and 192.168.1.1 but it is not recognized. I have put it into tftp mode and tried installing the software but command prompt does not recognize the request.
It was suggested I didn't wait long enough on the initial update. This is possible.
I set protocal to dhcp and tried localnode:8080 it gives no result.
If it is not fixable I will trashcan it but was wondering if there is a fix first.
I think everyone for their input.
I assume you mean copy from the command prompt. Not sure how to do that
Highlight the command or commands you want to copy and press [CTRL-C]
Open a message here and press [CTRL-V]
Ok. I was doing a sysupgrade but have pushed the reset button. Do you want me to try the factory os sysupgrade software?
Should read or not os
os>tftp -i 192.168.1.20 put downloads\aredn-3.20.3.1-ath79-ubnt_nanostation-m-factory.bin
Could you ping 192.168.1.20 before you attempted the tftp?
Also a suggestion. Rename the file to something simple - like factory.bin and put it into the folder that you are operating from. Saves typing and dramatically reduces the likelyhood of fat fingering the filename. Typing ...put factor.bin is a lot easier than ...put downloads\aredn-3.20.3.1-ath79-ubnt_nanostation-m-factory.bin
If all else fails don't trash it you can use the serial recovery method using the original OS. I have done it but it's a bit complicated.
Here is a link to KD4RSX:
Unbricking a Node by KD4RSX | Amateur Radio Emergency Data Network (arednmesh.org)
Denis KD1HA
Curious how did you make out?
I ended up loading the older 3.19.3.0 factory software and it is now working. I have not retried updating to 3.20.3.1 as yet.
Retried to load 3.20.3.1 using UI and it wouldn't load so it can stay with the older software.