Download Ubnt Firmware
Dorthea Seate
Just go to Tools > Software Upgrade in the Elevated radios GUI and upload the Ubiquiti firmware file. After it finishes the flashing process, it will come back up just like it was before being elevated.
Upon, simply loading the UBNT firmware into the Elevate UI under the software upgrade window (as you would normally upgrade the firmware on a Cambium device), I have lost access to the device. Neither discovery tool will find it, and I cannot ping the IP at all.
It sounds like something went wrong flashing it... I've had that happen with quite a few ubnt radios recently (not just going between Elevate and ubnt firmware, but more so just updating the ubnt firmware to newer versions).
In my particular case this question relates the UniFi AP v2 but has more general implications.
One would imagine this to be a simple question to answer with a yes or no answer but not for Ubiquiti it seems.
I have been asking this question of Ubiquiti for about a month now after having problems loading OpenWRT 15.05.1 into a number of UniFi AP v2 units. The answers from Level 1 support (via their forums) has been, "It shouldn't be blocked" (hoping for a Yes or No), "It's ok in the latest release" (it wasn't), "I'll have to check with Development" (still waiting for that), "We don't support Third Party Firmware" (wasn't asking for support) or (the most honest) "I don't know". So I pressed for an answer, they escalated it to the next level but were very vague about what that meant. Oh and it seems Level 1 support at Ubiquiti have no SLA what so ever with the team they escalate to. They also have no way to communicate with them after an escalation. So the question has gone some where in Ubiquiti to be answered at some unknown time.
My own feeling is that they are avoiding answering the question as they took the excuse of the FCC rules relating to unauthorised changes to Wireless parameters that could be part of Third Party Firmware, to do this. Of course the FCC rules only applied to 5Ghz not 2.4Ghz Wireless and, as the FCC have stated, was not intended to be used as a reason for blocking Third Party Firmware. TP-Link got caught up in this too. So they cant say they are blocking.
I also think they are actively blocking. Firmware Images for the UniFi AP v2 have a different device type in their header but this is easy to cater for by either making changes in the OpenWRT firmware builder to generate a correct header (sorry not going to go into derail on that here) or by using a binary editor to change it manually. The real issue is that the Ubiquiti Firmware images have a new RSA signature section at the end. The U-Boot loader, already on the device and included in Ubiquiti Firmware updates, checks the signature and rejects images that don't have it, making TFTP updates not work. fwupdate.real used to do upgrades via the command line, also checks and rejects images without the signature giving the "Invalid FW Part 3 MAGIC 'END.'" message.
I'm interested to hear other peoples thoughts on this please.
Hello. Did you get OpenWRT or LEDE working on the UAPv2? I need to use this third party OS to make the device act as router, firewall and multi-AP, and with these new versions I can't. This is the worst thing Ubiquiti could do to these devices...
No. It's not really a matter of getting OpenWRT or LEDE to work, it's about Ubiquiti blocking the installation of third party firmware in the first place by checking that any firmware has the correct RSA signature before its even loaded. Ubiquiti wont even discuss this. Try asking the question on their support forum and see what they say .
One thing is support the 3rd party firmware and another, completely different, is not allowing me to install it at the ubiquiti devices. Are you telling me that Ubiquiti is restricting the 3rd party firmwares installation?
i've recently came up with an idea how to flash locked/signed firmware on litebeam ac gen2. basically you start flashing same ubiquiti fw that is already on device and interrupt the process, that leaves mtd partitions unlocked and you can flash another image to these using dd. more info in this GH comment-> -493658317
Do you have any plans to elevate the latest UBNT firmware or do you think it will not be possible due to certain certification ect. ? I have attempted several different ways and even types of firmware. I've tried flashing ePMP firmware, it gets uploaded, but the lights start flashing abnormally and then reboots to recovery mode.
I've bricked a UBNT running 6.2.0 by following people's advice on the DD-WRT forum. It seems the DD-WRT firmware is able to upload better than open-wrt and epmp, but I am not able to login in to the DD-WRT elevated radio to test my theory.
I no longer struggle with MikroTik elevates, after several failures and using different methods, I've mastered it to elevate in seconds without needing to change firmware as recommended. Do you have any plans to elevate MikroTik Groove Radios?
I haven't tried this - but I thought there was a TFTP Firmware Recovery process, which could (I though) allow you to restore firmware if it was corrupted.. and I thouight that could be used to get an older firmware onto a UBNT device. Again - just guessing since I haven't done it. :)
I updated the Ubiquiti controller software today as I noticed there was a recent update. After updating the controller software, I also noticed that there was a firmware update for my UAP-AC Pro access point. I updated to the latest firmware version which is 6.6.65.
During the afternoon, the internet dropped out at least once an hour - or more specifically the wireless dropped out. When trying to upload the older firmware to my website using filezilla, I noticed the connection in filezilla kept erroring out. So I had to connect via cable to upload the older firmware in order to restore my ap to the older version.
According to this, -Access-Point-6-6-65/3df9b0c0-7e51-4843-93a2-276c2d63e10a?page=1, a lot of people are having issues with this firmware version. The next release which is still in beta testing seems to have fixed the issues. I will just wait until the next release is production ready and upgrade to that bypassing version 6.6.65. The older version works perfectly, so I see no pressing need to upgrade.
I have just updated to the very latest firmware 6.6.73. According to the release notes they have fixed the problems present in 6.6.65. I will update tomorrow if this release is safe to update for ac-uap pro access points which are only using 5.2ghz.
If you have a device that you've tried to set-inform from SSH, but it's not showing up for adoption in your UniFi controller, a common problem is that the device's firmware needs to be manually upgraded before it can be adopted.
Now from the SSH prompt, issue the upgrade command. Replace the firmware URL with the appropriate one for your device. The exact command will vary by model and firmware version. For the UAP AC Lite in our example, it is:
The device should reboot with the new firmware version which you can verify with the info command. Then you should be able to set-inform from there, or set-default then set-inform if you have any problems.
HostiFi provides hosting for both Ubiquiti and TP-Link software-defined-networking (SDN) applications, with servers for UniFi, UISP and Omada. We also offer professional networking consulting, with HostiFi Pro.
An alternative more generic method, e.g. ER-X running EdgeOS 2.0.6 shows a slightly different partition layout, would be the following which transfers compressed partition images to a different host (172.16.174.4 in this example) that has more storage.
Both image files are tar format archives, the factory file is set up such that the OEM upgrade process will accept it as a legitimate (OEM) firmware image. The factory file is typically suffixed tar, the sysupgrade image as bin.
If you have an ERX-SFP device but booted an ubnt-erx factory image (e.g. per step 1), you'll need to provide the -force argument to sysupgrade with the ubnt-erx-sfp image. Using an ERX-SFP image (based on OpenWRT 21) may sidestep this issue (untested).
The initramfs-kernel.bin file can be booted via option 1 in the boot menu available via a serial connection. Enter the IP and filename for TFTP on eth0. The TFTP server must be connected to eth0, as the bootloader does not activate the other ports. After this factory image boots, use 'sysupgrade -n' to flash the sysupgrade image. (not supported by 17.01.4)
The OEM layout on the Edgerouter X has two kernel slots that are 3MB each. Starting with Linux 6.6 commit 2967e24 the kernel images built from main branch, no longer fit into this layout. This means a special migration will be required to upgrade to 24.x once it is released.
The Ubiquiti EdgeOS distributions cannot be directly re-installed by OpenWrt. This section describes how to use a Linux PC to prepare Ubiquiti firmware into a file that can be flashed as an OpenWrt sysupgrade. The router will then be running the stock firmware instead of OpenWrt. This has been tested with version v1.10.11.5274269 on an Edgerouter-X running OpenWrt 19.07.2. To fully remove OpenWrt, it is recommended to flash stock a second time from the EdgeOS firmware so that both kernel partitions contain EdgeOS. If uploading the stock image from within EdgeOS fails, the device might be out of space.
The files of interest are vmlinux.tmp and squashfs.tmp. vmlinux is the kernel image and squashfs is the root filesystem, however this squashfs image needs to be placed within a ubifs filesystem for use.
Addendum: above procedure did not work on an Edgerouter X SFP as somehow the version information did not get set; any attempt to upgrade from the EdgeOS caused kernel panic. But found another way on the Ubnt forum, so all credits there. Have put it in the form of a script.
For EdgeRouter X the LEDs on the top panel somehow doesn't show a fast blinking pattern during device start up, nor does the typical UDP broadcast message is sent during the failsafe prompt, to enter failsafe mode one could try the following procedure:
c80f0f1006