Could we get clarification if devices that were never downgraded to AirOS 5.5 will work if moved to 3.16.2.0?
With 3.16.1 and earlier we had to do the 5.6 to 5.5 downgrade, so those should always be safe.
For the nightly builds this downgrade was not needed (and maybe 17RC1 too?). One could go out of the box, directly to a nightly build. However, attempting to go to 3.16.2RC1 a few weeks ago would near brick that never-downgraded node, requiring TFTP recovery.
A number of forum members reported bricks during the 3.16.2RC1 phase. I replicated it twice unforunately. It's not an unusual situation since the XW version of the nanostation needed 17RC1 and/or a nightly when it first came out, so there are a number of these cases out there. Some may not remember the initial install path they did a year ago.
Thanks,
Ian
You are here
3.16.2.0 upgrading
Wed, 09/05/2018 - 15:02
#1
3.16.2.0 upgrading
Wed, 09/05/2018 - 16:48
#2
AE6XE
Yes, 3.16.2.0 still requires
Yes, 3.16.2.0 still requires the mesh node to be downgraded to AirOs 5.5.x version. Specifically, the bootloader needs downgraded to the version in AirOs 5.5.x. The difference from 3.16.1.1 is the device will no longer be soft bricked. It just won't boot with the incompatible bootloader.
Thu, 09/06/2018 - 13:17
#3
Will the next full release
Will the next full release contain the magic of the nightly builds that "just works"?
Thu, 09/06/2018 - 13:48
#4
K5DLQ
Yes. The nightly and next
Yes. The nightly and next full release will have the Ubiquiti bootloader upgrade woes solved. (3.16.2.0 was primarily a security update. it does not add any new device support).
Theme by Danetsoft and Danang Probo Sayekti inspired by Maksimer