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
New Member
Posts: 12
Registered: ‎12-11-2013

Re: HOWTO: Unbrick your UniFi AP

Data Size: 918303 Bytes = 896.8 kB Load Address: 80002000 Entry Point: 80002000 Verifying Checksum at 0x9f050040 ...OK Uncompressing Kernel Image ... ERROR: LzmaDecode.c, 543 Decoding error = 1 LZMA ERROR 1 - must RESET board to recover Resetting...

New Member
Posts: 12
Registered: ‎12-11-2013

Re: HOWTO: Unbrick your UniFi AP

Data Size: 918303 Bytes = 896.8 kB
Load Address: 80002000
Entry Point: 80002000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... ERROR: LzmaDecode.c, 543

Decoding error = 1
LZMA ERROR 1 - must RESET board to recover

Resetting...

New Member
Posts: 12
Registered: ‎12-11-2013

Re: HOWTO: Unbrick your UniFi AP

After upgrade UAP LR keeps on Rebboting please see the log file attached 

 

Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... ERROR: LzmaDecode.c, 543

Decoding error = 1
LZMA ERROR 1 - must RESET board to recover

Resetting...

U-Boot unifi-v1.3.3.124-ge1a2c421 (Sep 27 2013 - 13:13:30)

Board: Ubiquiti Networks AR7241 board (e512-6.0101.002e)
DRAM: 64 MB
Flash: 8 MB
*** Warning - bad CRC, using default environment

*** saving default environment ...
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Net: eth0, eth1
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS Ubiquiti Linux-2.6.15-5.2
Created: 2012-02-24 16:55:55 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 730087 Bytes = 713 kB
Load Address: 80002000
Entry Point: 80002000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

Booting...

 

 

 

New Member
Posts: 21
Registered: ‎08-16-2013
Kudos: 14

Re: HOWTO: Unbrick your UniFi AP

At this point I'm not sure I can help more. It sounds like a deeper problem, maybe faulty flash, faulty hardware in general, don't know.... anyway, pretty sure a hands-on approach is kind of needed to debug more. Sorry, I'll rest here.

Maybe try and test using other versions of Unifi firmware (earlier then 2.4.6, or even some 3.x beta ones). See if you get lucky reviving it.

 

Cheers.

New Member
Posts: 16
Registered: ‎05-14-2012
Kudos: 3

Re: HOWTO: Unbrick your UniFi AP

[ Edited ]

Thanks so much -- vali_cheche -- for this accurately detailed steps. I used to follow the tftp way but missed some of the steps mentioned on this so I thought the AP is totally broken.

 

So far I have ressurected 5 APs with this method! Thank you, you're a life saver! Man Happy

New Member
Posts: 25
Registered: ‎11-18-2013
Kudos: 2

Re: HOWTO: Unbrick your UniFi AP

 I Have sucessful un bricked my 5 nos of uap lr  via soft TFTP method

its working in production

 

 

Thanks u guys

 

New Member
Posts: 1
Registered: ‎01-23-2014

Re: HOWTO: Unbrick your UniFi AP

I have a problem with UAP-AC-PRO. It doesn't start tftp server at boot.

Using TTL conection i receive below messages:

 

Decompressing...done


CFE version 6.37.14.7201 (r452093) based on BBP 1.0.37 for BCM947XX (32bit,SP,LE)
Build Date: Tue May 6 14:38:17 PDT 2014 (build-unifi@ubnt-builder1)
Copyright (C) 2000-2008 Broadcom Corporation.

Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
bcm_robo_enable_switch: EEE is disabled
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 6.37.14.7201 (r452093)
CPU type 0x19749: 600MHz
Tot mem: 131072 KBytes

CFE mem: 0x81F00000 - 0x81FA2680 (665216)
Data: 0x81F38100 - 0x81F3B3D0 (13008)
BSS: 0x81F3B3D0 - 0x81F3C680 (4784)
Heap: 0x81F3C680 - 0x81FA0680 (409600)
Stack: 0x81FA0680 - 0x81FA2680 (8192)
Text: 0x81F00000 - 0x81F38100 (229632)

Device eth0: hwaddr DC-9F-DB-B4-0C-A1, ipaddr 192.168.1.20, mask 255.255.255.0
gateway not set, nameserver not set
Invalid boot block on disk
Invalid boot block on disk
flash0.0: Device not found
Invalid boot block on disk
flash1.trx CRC check failed!
Invalid boot block on disk
flash1.trx2 CRC check failed!
Both images bad!!!

 

 

Is it possible to unbrick it?

Member
Posts: 223
Registered: ‎05-14-2014
Kudos: 15

Re: HOWTO: Unbrick your UniFi AP

So I followed the process and got a message the said transfer complete???

 

Then it blinks and goes white again.... what is that all about?

 

AP LR - I am trying to update it to 3.2.10 because I have no idea what firmware was on it when it died.

 

TIA

New Member
Posts: 22
Registered: ‎03-13-2013
Kudos: 2
Solutions: 1

Re: HOWTO: Unbrick your UniFi AP

Hi all,

i'm trying to unbrick a UAP.

I connected from TTL i run urescue command and the

UAP say:

U-Boot unifi-v1.2.1.71-g529c499d (Dec 21 2012 - 12:50:21) 

Board: Ubiquiti Networks AR7241 board (e502-16.0101.002e)
DRAM: 64 MB
Flash: 8 MB
Net: eth0, eth1
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS Ubiquiti Linux-2.6.15-5.2
Created: 2012-12-21 21:40:43 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 729741 Bytes = 712.6 kB
Load Address: 80002000
Entry Point: 80002000
Verifying Checksum at 0x9f050040 ...Bad Data CRC
ar7240>urescue
Setting default ip 192.168.1.20
Starting TFTP server....
Using eth0 (192.168.1.20) address: 0x81000000
waiting for connection: checksum bad:
/

 

i run tftp client command to put firmware.bin (2.4.6)

UAP say:

Receiving file from 192.168.1.254:
Received 5719597 bytes
Firmware Version: BZ.ar7240.v2.4.6.2178.131008.1132

 

The UAP not reboot and the TTL prompt not respond...

If I force reboot the UAP return in prompt command mode

ar7240>

 

This UAP had firmware version 2.3.9 (i don't have this) where can i download this firmware??

I tryed to donwload from: http://goo.gl/jSvbMm but the link are broken.

 

Help help!!

 

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

Re: HOWTO: Unbrick your UniFi AP

Have a go at this process I came up with described here ;  recovery method

 

You will need the individual parts of the partitions, if you dont have them, give me a shout and I can let you have them, let me know which version you are trying to write. I dont have all of them just yet, but I'm getting a small collection and might just have the one you want.

 

Cheers,

Steve..

New Member
Posts: 1
Registered: ‎05-27-2015

Re: HOWTO: Unbrick your UniFi AP

gentlemen,

I have a similar problem. I install via Putty an open-wrt firmware suddenly the writing process "'roots' to / dev / mtd3 (rootfs) ..." [21%] stopped at 21%. Since then the ap stopped Run.

I can not ping to 192.168.1.20.

Open the equipment and connected the USB cable and ttl through the putty accessed the ap, I canceled the autoboot and tried using the command urescue though nothing happened and I did not succeed in reestablishing the functioning of ap.

What can I do?



 

 

#############################

 

TANKS

 

IMG-20150521-WA0003.jpg
Emerging Member
Posts: 48
Registered: ‎03-09-2014
Kudos: 14

Re: HOWTO: Unbrick your UniFi AP


AzaelDourado wrote:

gentlemen,

I have a similar problem. I install via Putty an open-wrt firmware suddenly the writing process "'roots' to / dev / mtd3 (rootfs) ..." [21%] stopped at 21%. Since then the ap stopped Run.

I can not ping to 192.168.1.20.

Open the equipment and connected the USB cable and ttl through the putty accessed the ap, I canceled the autoboot and tried using the command urescue though nothing happened and I did not succeed in reestablishing the functioning of ap.

What can i do



when you put the AP into urescue mode, it is listening for an image to be transfered to it from another tftp server, have you tried to transer the original ubnt mfirmware image to the AP ?

 

New Member
Posts: 22
Registered: ‎03-13-2013
Kudos: 2
Solutions: 1

Re: HOWTO: Unbrick your UniFi AP

Thi is the output of mtdparts:

 

ar7240> mtdparts
device nor0 <ar7240-nor0>, # parts = 6
#: name size offset mask_flags
0: u-boot 0x00040000 0x00000000 0
1: u-boot-env 0x00010000 0x00040000 0
2: kernel 0x00100000 0x00050000 0
3: rootfs 0x00660000 0x00150000 0
4: cfg 0x00040000 0x007b0000 0
5: EEPROM 0x00010000 0x007f0000 0
active partition: nor0,0 - (u-boot) 0x00040000 @ 0x00000000
defaults:
mtdids : nor0=ar7240-nor0
mtdparts: mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),1024k(kernel),6528k(rootfs),256k(cfg),64k(EEPROM)

 

 

Now I can put the firmware (2.4.6.2178) as this:

 

ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \
Receiving file from 192.168.1.13:51367
Received 5683852 bytes
Firmware Version: BZ.ar7240.v2.4.6.2178.131008.1132
Setting U-Boot environment variables
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
        erasing range 0x9F050000..0x9F10FFFF: ............ done
Erased 12 sectors
        writing to address 0x9f050000, length 0x000c0000 ...
write addr: 9f050000
Copying partition 'rootfs' to flash memory:
        erasing range 0x9F150000..0x9F5CFFFF: .......................................................................e
Erased 72 sectors
        writing to address 0x9f150000, length 0x00480000 ...
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot unifi-v1.2.1.71-g529c499d (Dec 21 2012 - 12:50:21)

Board: Ubiquiti Networks AR7241 board (e502-16.0101.002e)
DRAM:  64 MB
Flash:  8 MB
Net:   eth0, eth1
Hit any key to stop autoboot:  0 
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.15-5.2
   Created:      2013-10-08  18:37:43 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    729748 Bytes = 712.6 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

Booting...


U-Boot unifi-v1.2.1.71-g529c499d (Dec 21 2012 - 12:50:21)

Board: Ubiquiti Networks AR7241 board (e502-16.0101.002e)
DRAM:  64 MB
Flash:  8 MB
Net:   eth0, eth1
Hit any key to stop autoboot:  0 
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.15-5.2
   Created:      2013-10-08  18:37:43 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    729748 Bytes = 712.6 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

Booting...

but the system enter in a infinite loop...

HELPME!!!!

hahhahh!!!

 

 

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

Re: HOWTO: Unbrick your UniFi AP


morpheus77 wrote:

Thi is the output of mtdparts:

 

ar7240> mtdparts
device nor0 <ar7240-nor0>, # parts = 6
#: name size offset mask_flags
0: u-boot 0x00040000 0x00000000 0
1: u-boot-env 0x00010000 0x00040000 0
2: kernel 0x00100000 0x00050000 0
3: rootfs 0x00660000 0x00150000 0
4: cfg 0x00040000 0x007b0000 0
5: EEPROM 0x00010000 0x007f0000 0
active partition: nor0,0 - (u-boot) 0x00040000 @ 0x00000000
defaults:
mtdids : nor0=ar7240-nor0
mtdparts: mtdparts=ar7240-nor0:256k(u-boot),64k(u-boot-env),1024k(kernel),6528k(rootfs),256k(cfg),64k(EEPROM)

 

 

Now I can put the firmware (2.4.6.2178) as this:

 

ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \
Receiving file from 192.168.1.13:51367
Received 5683852 bytes
Firmware Version: BZ.ar7240.v2.4.6.2178.131008.1132
Setting U-Boot environment variables
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
        erasing range 0x9F050000..0x9F10FFFF: ............ done
Erased 12 sectors
        writing to address 0x9f050000, length 0x000c0000 ...
write addr: 9f050000
Copying partition 'rootfs' to flash memory:
        erasing range 0x9F150000..0x9F5CFFFF: .......................................................................e
Erased 72 sectors
        writing to address 0x9f150000, length 0x00480000 ...
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot unifi-v1.2.1.71-g529c499d (Dec 21 2012 - 12:50:21)

Board: Ubiquiti Networks AR7241 board (e502-16.0101.002e)
DRAM:  64 MB
Flash:  8 MB
Net:   eth0, eth1
Hit any key to stop autoboot:  0 
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.15-5.2
   Created:      2013-10-08  18:37:43 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    729748 Bytes = 712.6 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

Booting...


U-Boot unifi-v1.2.1.71-g529c499d (Dec 21 2012 - 12:50:21)

Board: Ubiquiti Networks AR7241 board (e502-16.0101.002e)
DRAM:  64 MB
Flash:  8 MB
Net:   eth0, eth1
Hit any key to stop autoboot:  0 
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.15-5.2
   Created:      2013-10-08  18:37:43 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    729748 Bytes = 712.6 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

Booting...

but the system enter in a infinite loop...

HELPME!!!!

hahhahh!!!

 

 


Its either that the config is corrupt and you need to reset that by hilding down the reset button until it breifly flashes green. Or and I've been in this loop as well and had another problem with CRC errors on boot and needed to work this out to manuall reflash the partitions back to get it working..

 

I appreciate this is an old thread, but I couldnt find any help to the problem either so I decided to spend the time working out a solution when the urescue command doesnt flash properly and recover the unify.

Below is the output of my TTL Serial console connected to the Unify (SWX-UAP)

** BE CAREFUL You can make the situation worse than it already is by miss typing the commands, getting a memory address wrong etc.. ** BE CAREFUL ** (Worth saying twice) And remember your results may vary to mine. I have sucuessfully recovered eleven unify's that would not recover via the urescue process using the below. Each and every one is now updated to 2.4.6.2178 and is working perfectly.

U-Boot unifi-v1.2.1.71-g529c499d (Dec 21 2012 - 12:50:21)

Board: Ubiquiti Networks AR7241 board (e502-6.0101.002e)
DRAM:  64 MB
Flash:  8 MB
*** Warning - bad CRC, using default environment

***           saving default environment ...
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Net:   eth0, eth1
Hit any key to stop autoboot:  0
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.15-5.2
   Created:      2012-02-24  16:55:55 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    730087 Bytes = 713 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...Bad Data CRC

ar7240> mtdparts default
ar7240> saveenv
Saving Environment to Flash...
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
ar7240> tftp 83000000 2.4.6.2178/mtdblock2
Using eth0 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.20
Filename '2.4.6.2178/mtdblock2'.
Load address: 0x83000000
Loading: #################################################################
         #################################################################
         #################################################################
         ##########
done
Bytes transferred = 1048576 (100000 hex)
ar7240> protect off all
Un-Protect Flash Bank # 1
ar7240> erase 0x9f050000 +0x100000
................ done
Erased 16 sectors
ar7240> cp.b 0x83000000 0x9f050000 0x100000
Copy to Flash... write addr: 9f050000
done
ar7240> cmp.b 0x83000000 0x9f050000 0x100000
Total of 1048576 bytes were the same
ar7240> tftp 83000000 2.4.6.2178/mtdblock3
Using eth0 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.20
Filename '2.4.6.2178/mtdblock3'.
Load address: 0x83000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######
done
Bytes transferred = 6684672 (660000 hex)
ar7240> erase 0x9f150000 +0x660000
...................................................................................................... done
Erased 102 sectors
ar7240> cp.b 0x83000000 0x9f150000 0x660000
Copy to Flash... write addr: 9f150000
done
ar7240> cmp.b 0x83000000 0x9f150000 0x660000
Total of 6684672 bytes were the same
ar7240>
ar7240> reset

Resetting...

U-Boot unifi-v1.2.1.71-g529c499d (Dec 21 2012 - 12:50:21)

Board: Ubiquiti Networks AR7241 board (e502-6.0101.002e)
DRAM:  64 MB
Flash:  8 MB
*** Warning - bad CRC, using default environment

***           saving default environment ...
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Net:   eth0, eth1
Hit any key to stop autoboot:  0
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.15-5.2
   Created:      2013-10-08  18:37:43 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    729748 Bytes = 712.6 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

Booting...

And from then on its accessable again from the regular Unify web interface.


I've invested time in reading about U-Boot and what commands were available and knowing linux and networking already, together with programming knowledge this is how I have bought it all together to transfer the parts of the image nessasary and write then directly,

What you will also need is the seperate parts of the NAND flash that make up the whole filing system, I only used the kernel and rootfs parts though. You will also need a working tftp server for the unify to pull the partitions from, but you'll probably have this already since you've tried the urescrue and found it not wor work.

To get the working partitions you'll need another working unify that you can ssh into and then extract from and copy to your tftp server ready to be transfered. I did try and work out a way to extract them from the firmware.bin file but gave up and went for the shorter route.

 

 

New Member
Posts: 3
Registered: ‎05-11-2015
Kudos: 1

Re: HOWTO: Unbrick your UniFi AP

[ Edited ]

stevebird,

I have a UniFi AP LR receiving:

U-Boot unifi-v1.3.4.150-g9c1b7607 (May 13 2014 - 14:36:18)

Board: Ubiquiti Networks AR7241 board (e512-6.0101.002e)
DRAM:  64 MB
Flash:  8 MB
Net:   eth0, eth1
Hit any key to stop autoboot:  0
## Booting image at 9f050000 ...
   Image Name:   MIPS Ubiquiti Linux-2.6.15-5.2
   Created:      2013-10-08  18:37:43 UTC
   Image Type:   MIPS Linux Kernel Image (lzma compressed)
   Data Size:    729748 Bytes = 712.6 kB
   Load Address: 80002000
   Entry Point:  80002000
   Verifying Checksum at 0x9f050040 ...Bad Data CRC
ar7240>

This is after flashing the latest firmware or 2.4.6.

This is unfortunately my only UniFi AP so I cannot retreive working partitions from a working unit to flash. Can you provide the partitions needed?  My email is bsmithx84 and I use gmail.  Thanks for your help so far.

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

Re: HOWTO: Unbrick your UniFi AP

I've got verious firmware versions on my server -

 

Help your self at ftp dot avtsuk dot com

 

username and password should be obvious :-)

 

If anyone else finds these useful please drop me a message to say you've used them.

 

I'm still trying to develop a method to recover totally dead AP's by re-writing back the U-Boot partition via Jtag.

 

I'm killing more AP's than I am fixing at the moment trying different Jtaging methods, if anyone has an AP that they can donate to the cause it would be appreciated.

 

 

New Member
Posts: 22
Registered: ‎03-13-2013
Kudos: 2
Solutions: 1

Re: HOWTO: Unbrick your UniFi AP

Hi stevebird,

you use this: 

ar7240> tftp 83000000 2.4.6.2178/mtdblock2Using eth0 device
TFTP from server 192.168.1.254; our IP address is 192.168.1.20
Filename '2.4.6.2178/mtdblock2'.
Load address: 0x83000000

 

what is 83000000??? 

Not is the exadecmal notation of 192.168.1.254.

What does it stand for??

 

Thanks a lot!

 

 

 

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

Re: HOWTO: Unbrick your UniFi AP

HI.

 

 

0x83000000 is the memory address where the file is going to read into.

 

Its high enough to avoid over writing current memory that is in use and then allows you to read back from that address and write it to the nand. 

 

Cheers.Steve

 

New Member
Posts: 2
Registered: ‎06-17-2015

Re: HOWTO: Unbrick your UniFi AP

Hello,

 

I have a site with 3 UAP-PRO. last week when I wanted to add a 4th AP, one of the 3 inplace went wrong.

 

I followed instructions to TFTP the firmware into the faulty UAP-PRO, which seems to work. I tried several firmware, I always get the same result: AP reboots, I get a white LED flashing, then strobing. 

 

When I try to SSH in with ubnt / ubnt, the SSH connection closes immediatly.

 

I have this device for 2 years, and I'm based in Taiwan. Is it still elligible for an RMA?

 

Can anyone let me know what I could try next?

 

Thanks in advance and best regards!

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

Re: HOWTO: Unbrick your UniFi AP


 

I followed instructions to TFTP the firmware into the faulty UAP-PRO, which seems to work. I tried several firmware, I always get the same result: AP reboots, I get a white LED flashing, then strobing. 

 

When I try to SSH in with ubnt / ubnt, the SSH connection closes immediatly.


Sounds very much like the update failed, SSH will not be available unless the AP boots to a running state.

 


I have this device for 2 years, and I'm based in Taiwan. Is it still elligible for an RMA?
 

Not very likely. We've been in the same position with our clients. We are encouraged to upgrade to solve problems in a defective/buggy or unreliable firmware and then if it fails and the AP fails to boot then we are not supported.

 


 

Can anyone let me know what I could try next?


Open up the unit and connect a TTL serial lead to the diagnosis port on the AP and see if you get any output, it might give a clue as to why its not booting.

 

Havetried  tried all the regular recovery methods, using TFTP, button presses etc ?

Reply