You are here

Home » Forums » General discussion

How to Restore to stock ubiquiti firmware on Bullet m2?

18 posts / 0 new
Log in or register to post comments
Last post
Fri, 11/06/2015 - 23:46
#1
K6AMD
How to Restore to stock ubiquiti firmware on Bullet m2?

Hello everyone

I cant seem to find any information regarding this and dont want to risk bricking my bullet. Does anyone know how to restore to stock firmware?

Do I just simply download the firmware and flash it from the Aredn web ui ?

 

Thank you very much for all your help

Top
Fri, 11/06/2015 - 23:51
K5DLQ
K5DLQ's picture
Use the TFTP technique.
Use the TFTP technique.
Top
Sat, 11/07/2015 - 09:42
WU2S
WU2S's picture
TFTP Procedure

The full description of the TFTP procedure can be found from the AREDN home page main menu by selecting Software --> Installation.

Top
Sat, 11/07/2015 - 14:25
K6AMD
Thank you very much K5DLQ and

Thank you very much K5DLQ and WU2S.

I did the tftp procedure and it worked out great. I was a bit scared because I had previously bricked one of my bullets that had air os 5.6 on it. I bricked it after flashing aredn firmware.  This was before the warning was put up about airos 5.6. I am trying to be as cautious as possible.

 

Thank you once again

Top
Sat, 11/07/2015 - 14:34
(Reply to #4)
K5DLQ
K5DLQ's picture
glad you got it worked out!

glad you got it worked out!

 

73

Top
Tue, 03/22/2016 - 10:29
K0SPN
Dredging up an old topic, but
Dredging up an old topic, but is there a technical reason that the uploader in the Admin GUI won't work?

Not that this is exceedingly difficult, it would just be nice to more easily go back and forth for testing/site survey since I don't have extra units available.
Top
Tue, 03/22/2016 - 11:52
(Reply to #6)
KG6JEI
At the moment it is because
At the moment it is because the GUI doesn't understand the additional headers that exist inside of a factory-type file which is what is pushed by Ubiquiti. This is one part where we rely on OpenWRT code as the base and it has not been implemented there because each device type can have a different header, there is to my knowledge no reasonable way (we are limited on space and cpu so big database = bad) to catalog and detect all the headers into the upgrade scripts to be stripped off before installation. It's easy for a vendor that only works with a single hardware line (Ubiquiti) to embed this in as each group of devices usually has its own software tree, we on the other hand are working with multiple device lines and vendors. While we currently only have support for Ubiquiti and TPLink device at the moment even between these two vendors the headers are different.
Top
Wed, 03/23/2016 - 23:44
(Reply to #7)
K0SPN
Makes sense.
Makes sense.

As I said, an annoyance really, nothing difficult.

Cheers.
 
Top
Thu, 03/24/2016 - 06:34
kj4pvx
kj4pvx's picture
I have a "how to" video
I have a "how to" video hosted on my server node, if you need it for reference.

http://hambox.local.mesh/howtovideos/

it's on kj4pvx-server



Hank
KJ4PVX
Top
Wed, 04/06/2016 - 16:52
WX4LTG
I've got a Bullet M2 here
I've got a Bullet M2 here that won't respond to ping. You can drop it into TFTP recovery mode, ping it on 192.168.1.20, and push firmware to it, but after it reboots then there's absolutely no access any more - no ping, no SSH, nothing. But you can still drop it back into TFTP mode and do it again.

It's very strange. Any ideas?
Top
Wed, 04/06/2016 - 17:18
(Reply to #10)
K5DLQ
K5DLQ's picture
go into TFTP recovery mode...
  1. go into TFTP recovery mode...
  2. verify ping on 192.168.1.20
  3. tftp (in binary mode) the "factory" AREDN firmware.
  4. after it loads and reboots, UNPLUG your network (LAN) cable from your PC.
  5. wait 5-10 secs
  6. plug in your network cable
  7. after the node boots up, ping localnode
Top
Wed, 04/06/2016 - 17:45
(Reply to #11)
WX4LTG
I've done that. Several times
I've done that. Several times. I finally tried reinstalling the Ubiquiti firmware, and it does exactly the same thing. Everything seems to be fine right up to the reboot, and then it stops pinging.
 
Top
Wed, 04/06/2016 - 18:00
(Reply to #12)
KG6JEI
I saw someone else report
I saw someone else report NAND chip failures some time ago that sounds similar. It would take being plugged into th serial port to truely debug it.

http://www.aredn.org/content/ubiquity-error-saving-setup#comment-151

Another item is make sure you didn't flash 5.6 firmware into the device either before installing AREDN or after as you may have hit issues around the new bootloader (would also need serial access to see)
Top
Wed, 04/06/2016 - 18:15
(Reply to #13)
WX4LTG
It's not mine, or I'd crack
It's not mine, or I'd crack it and connect the TTL.
Top
Mon, 04/25/2016 - 10:28
(Reply to #14)
WX4LTG
I forced a urescue -f -e,
I forced a urescue -f -e, pushed the 5.5 TFTP, did it again without the -f -e, pushed 5.5 again over TFTP, and saw a few additional boot-time errors. So I pushed one more 5.5 TFTP, and the Bullet seems to be working again now. Keeping an eye on it, wondering if a reboot may kill it again.
Top
Wed, 04/06/2016 - 18:23
K5DLQ
K5DLQ's picture
fyi, the Bullet is easy to
fyi, the Bullet is easy to open.  no "cracking" required.  ;-)

unscrew the silver ring under the N-connector and slide the board out
Top
Wed, 04/13/2016 - 12:36
(Reply to #16)
WX4LTG
I was making a bad pun on the
I was making a bad pun on the sound the Bullet makes the first time you turn that ring to unscrew it. ;)
Top
Wed, 04/13/2016 - 22:10
(Reply to #17)
K5DLQ
K5DLQ's picture
haha... gotcha
haha... gotcha
Top

Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer