All,
I have been using Gargoyle on UBNT devices, specifically the Bullet M2 and PicoStation M2. I have loaded the Gargoyle 1.6.2 firmware onto the devices through the AirOS webpage. For AirOS versions 5.5.8 and 5.5.10 the process has been flawless. However, UBNT has just come out with a firmware update, version 5.6.2. When I loaded Gargoyle 1.6.2 onto the newest firmware version from UBNT the device behaved strangely. On the firstboot page all the timezones were displayed by variable name, and not by the value of the variable. Also, none of my changes would save on any webpage.
I thought I would try to re-load the gargoyle firmware from within the gargoyle webgui. However, the buttons would not work on that webpage. I used Chrome developer tools and saw there was an error on the page, but I forgot to get a SS of it.
Since I couldn't load any firmware from Gargoyle I thought I would try to re-load the AirOS firmware using the TFTP recovery method. The TFTP transfer was successful, but now the device is stuck in an endless reboot loop. I have placed the device back in the TFTP recovery mode and tried to load older AirOS firmware versions as well as OpenWRT images but it fails every time with the message "Error on Server: Firmware check failed."
Has anyone else experienced this same issue or have any ideas for me to try? Currently this device is bricked!!!
UBNT Bullet M2 Firmware Update
Moderator: Moderators
Re: UBNT Bullet M2 Firmware Update
having similar issues myself. AirOS ?? to gargoyle_1.7.2-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin
everything seems fine as a base install.
Soon as I configure it to IP range name and ssid etc.. 50% fail to be stable and cycle boot.
I was doing 1.6.0 and upgrading to 1.6.2 then to 1.71 which seem to be ok?
everything seems fine as a base install.
Soon as I configure it to IP range name and ssid etc.. 50% fail to be stable and cycle boot.
I was doing 1.6.0 and upgrading to 1.6.2 then to 1.71 which seem to be ok?
Re: UBNT Bullet M2 Firmware Update
I'm guessing this issue has to do with the new version of U-Boot being loaded with the 5.6.2 firmware version.
For firmware versions 5.5.8 and 5.5.10 the U-Boot is: U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)
Here is the mtdparts command result for 5.5.8 and 5.5.10
Now for the 5.6.2 firmware version the U-Boot version is: U-Boot 1.1.4.2-s956 (Jun 10 2015 - 10:54:50)
Here is the mtdparts command result for 5.6.2
The changes are in rootfs, cfg, and EEPROM. I'm guessing this is the cause of all my problems. Does anyone have any comments on how to get gargoyle / openwrt loaded successfully on this device?
For firmware versions 5.5.8 and 5.5.10 the U-Boot is: U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)
Here is the mtdparts command result for 5.5.8 and 5.5.10
Code: Select all
U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)
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
Here is the mtdparts command result for 5.6.2
Code: Select all
U-Boot 1.1.4.2-s956 (Jun 10 2015 - 10:54:50)
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 0x005a0000 0x00150000 0
4: cfg 0x00040000 0x006f0000 0
5: EEPROM 0x00010000 0x00730000 0
active partition: nor0,0 - (u-boot) 0x00040000 @ 0x00000000
Re: UBNT Bullet M2 Firmware Update
SOLUTION: DO NOT UPLOAD OPENWRT TO FIRMWARE VERSION 5.6.2. INSTEAD, FIRST LOAD AN OLDER VERSION OF FIRMWARE, ex: 5.5.10, AND THEN UPLOAD OPENWRT.
Re: UBNT Bullet M2 Firmware Update
this is the same solution I once used for another brand of router