Airrouter HP bricked

16 posts / 0 new

Tue, 07/18/2017 - 18:09

KJ6BXL

I'm looking for the method to recover a bricked Airrouter. I managed to brick it by loading AREDN on
without checking the AIROS version. How it doesn't respond to any ethernet address. I've seen the
discussion on unbricking a Nano Station using the serial port followed by TFTP of the ARDEN code.

Will this work for the Airrouter ?

Thanks

Tue, 07/18/2017 - 20:42

K5DLQ

yes

Wed, 07/19/2017 - 12:18

KJ6BXL

Airrouter bricked

Thanks , K5DLQ

Using the reset button, i got the unit into the state to accept TFTP loading ( LED 1&3 alternating with LED 2&4 )
I'm loading XM.v5.5.11.28002.150723.1344.bin from the Ubiquiti download site. (This file worked to downgrade
another Airouter.)
The Tftp program under Windows 7 outputs the following error after ~1 minute of file transfer:

"Firmware check failed"

Does anyone have thoughts/fixes for the Tftp file transfer error?

Thanks.

Wed, 07/19/2017 - 14:06

kg7bz

For some reason I fought with

For some reason I fought with the Windows 10 tftp and kept getting this error, even though I'd done it many times before. I finally gave up and used the GUI tftp program tftp2.exe and it went fine the first time. Set your computer to static address of 192.168.1.22, select the firmware to install, enter the IP address of the node (192.168.1.20) and click UPGRADE, done...

Thu, 07/20/2017 - 17:56

KJ6BXL

Airrouter bricked

I am still getting the file checksum error on the tftp transfer.

Using the gui tftp program.
I've opened the Airrouter and attached a serial terminal emulator to the serial header.

I can see the controller boot and set the IP to 192.168.1.20 and sit waiting for the tftp transfer.

When I start the tftp program running I can see the number of bytes transferred incrementing.

The XM.v5.5.11.28002.150723.1344.bin file is 6.57 MB (6,896,662 bytes) per Window file properties.
The console shows 6896662 bytes transferred before the checksum error message.

The AREDN-3.16.1.1-ubnt-airrouter-squashfs-factory.bin file is 4.68 MB (4,915,612 bytes) per Window file properties.
The console shows 4915612 bytes transferred before the checksum error message..

Both of these files have been used via the AIROS file update gui to downgrade and then do the AREDN load on
a second Airrouter sucessfully.

Is there a difference in the expected file format used by AIROS and what is needed for tftp ?

Thanks for any help.

Thu, 07/20/2017 - 19:14

(Reply to #5) #6

AE6XE

What version of uboot is

What version of uboot is showing on the device, as seen from the serial terminal emulator at device power on?

Fri, 07/21/2017 - 15:20

KJ6BXL

Airrouter Bricked

The UBoot version is:
1.1.4.2-s956 (Jun 10 2015)

The PCB is:
XM board rev 1.1 e4b2

I have found a thread on the Ubiquiti forum describing the problem.

I have tried the dual tftp sequence:
1. Interrupt Uboot and execute "urescue -f -e"
2.tftp the XW.v5.5.10-u2.28005.150723.1358.bin file
3. Interrupt Uboot and execute "urescue "
4.tftp the XW.v5.5.10-u2.28005.150723.1358.bin file

This results in the device getting stuck on the reboot after step 4.

Fri, 07/21/2017 - 15:32

(Reply to #7) #8

AE6XE

Ether the problem is

Ether the problem is identified or you have a typo?

The board is an "XM" board, this means chipset is AR92xx. Are you are loading the "XW" firmware for chipsets AR93xx? The firmware is not cross-compatible between these chipsets.

By the way, I have an AirRouter in hand reported bricked in the same way. I'll likely be taking these recovery steps for a spin shortly.

Joe AE6XE

Fri, 07/21/2017 - 15:38

(Reply to #8) #9

AE6XE

Just in case, you did see the

Just in case, you did see the full detailed steps. This link is buried in some of these posts: http://bloodhound.aredn.org/products/AREDN/wiki/HowTo/Unbrick

I just added a note a couple days ago to these instructions from another NSM2 I was working on, and got bit on this issue. It's not stuck after step 4 when the console ends at "rebooting....". AirOS turns off the console output. This means it worked. Probably just need to make sure your laptop is on the right static IP address and browse to http://192.168.1.20.

Joe AE6XE

Fri, 07/21/2017 - 17:33

(Reply to #9) #10

K6AH

AirRouter has a different default IP

The AirRouter has a default IP address of 192.168.1.1, not 192.168.1.20 as other UBNT devices. Try this address before anything more complicated.

Andre. K6AH

Fri, 07/21/2017 - 17:35

(Reply to #10) #11

K5DLQ

Good point. I always PING

Good point. I always PING the IP address before attempting TFTP.

Fri, 07/21/2017 - 17:43

(Reply to #11) #12

K6AH

Wow!

This may actually be the first time the project manager gets an answer right on the forum. I'm holding my breath for a confirmation ;-)

Fri, 07/21/2017 - 20:46

(Reply to #12) #13

AE6XE

Andre, wahoo! I can confirm

Andre, wahoo! I can confirm, the airRouter requires the following IP addresses to access. I just unbricked one:

tftp mode: 192.168.1.20
airOS booted: 192.168.1.1

I don't own one of these devices, but it is a twist from the other devices, AirOS is accessed via 192.168.1.1.

Joe AE6XE

Wed, 08/12/2020 - 23:55

#14

K1NAR

AirRouter HP upgrade to current software

My objective was to upgrade my AirRouter HP running an old AREDN software to current version. The router was operating a client tunnel mode for months.

I was not able to connect my PC (cat5 wires) to AirRouterHP running AREDN 3.18.x.? software

( PC IP 192.168.1.20) .... From my browser ( IP 192.168.1.1) but no connection was possible. After resetting AirRouter , I was able to access AREDN software and upgrade to current version 3.20.3.1

However and after updating my node name, changing password, saving settings and rebooting, AirRouter was not accessible anymore with IP 192.168.1.1.

Reset the box several times and ending with the same outcome every single time.

(Box kept AREDN 3.20.3.1 through all resets)

Likely missing a step or is my box is bricked ?

Thu, 08/13/2020 - 20:04

(Reply to #14) #15

KD1HA

It's probably not bricked.

It's probably not bricked. You can't connect to your node on 192.168.1.1. Try http://localnode.local.mesh:8080 and look at the LAN address. That is your node's IP.
Denis KD1HA

Thu, 08/13/2020 - 22:59

(Reply to #15) #16

K1NAR

Thanks, that helped solve

Thanks, that helped solve the problem

Amateur Radio Emergency Data Network

Menu SF

You are here

Airrouter HP bricked

Amateur Radio Emergency Data Network

Search form

Menu SF

You are here

Airrouter HP bricked