Upcoming Maintenance Alert:

The UBNT Community will be upgraded at 5pm MDT on April 25th. During this time the community forums will be set to read-only status.

Learn more

×
Reply
Emerging Member
Posts: 48
Registered: ‎03-09-2014
Kudos: 14

Re: HOWTO: Unbrick your UniFi AP

Dont put it in the trash.. Sent it to me for my grave yard development :-)

Have you tried the tftp method to restore the partitions ?
New Member
Posts: 19
Registered: ‎08-27-2013

Re: HOWTO: Unbrick your UniFi AP

When you try command PRINTENV is there SERVERIP value ?

New Member
Posts: 2
Registered: ‎12-28-2014

Re: HOWTO: Unbrick your UniFi AP

Hoping someone can help me revive an old UAP-LR.  It is not responsive to ping/ssh on 192.168.1.20.  I was able to get it to accept a new firmware over tftp once, but no change in behavior.

 

When I boot the unit I get the following terminal output, it never moves past "Booting...":

U-Boot unifi-v1.5.2.206-g44e4c8bc (Aug 29 2014 - 18:01:57)

DRAM:  64 MB
Flash:  8 MB
PCIe WLAN Module found (tries: 1).
Net:   eth0, eth1
Board: Copyright Ubiquiti Networks Inc. 2014
Hit any key to stop autoboot:  0
Board: Ubiquiti Networks AR7241 board (e512-20.0101.002e)
UBNT application initialized
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.32.33
   Created:      2017-09-16   5:35:32 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    921589 Bytes = 900 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

Booting...

And this is the output I get when I boot the unit into tftp mode by holding down the reset button:

U-Boot unifi-v1.5.2.206-g44e4c8bc (Aug 29 2014 - 18:01:57)

DRAM:  64 MB
Flash:  8 MB
PCIe WLAN Module found (tries: 1).
Net:   eth0, eth1
Board: Copyright Ubiquiti Networks Inc. 2014
Hit any key to stop autoboot:  0
Board: Ubiquiti Networks AR7241 board (e512-20.0101.002e)
UBNT application initialized
reset button pressed: clearing cfg partition!

First 0x7b last 0x7e sector size 0x10000
.... done
reset button pressed: clearing u-boot-env partition!

First 0x4 last 0x4 sector size 0x10000
. done
u-boot-env is invalid, overiding with default.

First 0x4 last 0x4 sector size 0x10000
. done
write addr: 9f040000
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |

Any insight is appreciated.

New Member
Posts: 2
Registered: ‎01-19-2014

Re: HOWTO: Unbrick your UniFi AP

I have the same problem as a few people in this thread - via the TTL connection there doesn't appear to be anything corrupted, but the AP is not reachable via the ethernet interface.

 

The Unifi Discovery tool does show the AP (UAP-LR) with the default IP of 192.168.1.20, however there is no way to reach it (never responds to ping), even in TFTP recovery mode.

 

I tried to figure out what is happening. I ran a packet capture and it looks like the device is transmitting data (it transmits both the discovery broadcasts and DHCP requests): 

 

dhcp, warning       default offering lease 10.1.17.105 for 44:D9:E7:2E:7D:AC without success

But it doesn't receive anything at all.

 

So (as mentioned previously) it does indeed appear that the Ethernet port is damaged, even though the PHY does not report any errors when booting. 

 

If anyone managed to pinpoint the problem exactly I would appreciate it, however as it is a hardware problem, I don't think it's worth pursuing it much further.

New Member
Posts: 2
Registered: ‎12-28-2014

Re: HOWTO: Unbrick your UniFi AP

I ended up coming to a similar conclusion.  The only thing that still bothers me is that I was able to sucessfully tftp the firmware to the unit several times so on some level connectivity was still possible.

Emerging Member
Posts: 48
Registered: ‎03-09-2014
Kudos: 14

Re: HOWTO: Unbrick your UniFi AP


mezz64 wrote:

I ended up coming to a similar conclusion.  The only thing that still bothers me is that I was able to sucessfully tftp the firmware to the unit several times so on some level connectivity was still possible.


I would agree that you have connectivity, if you can tftp the firmware in then the ethernet hardware must be working.

 

Have you tried actually doing a full factory reset ?, you may just have a corrupted config which when the device is in recovery mode is not active as the recovery process is.

 

When the device boots it will load your config and at that point it might the problem presents its self.

Reply