NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ORBI RBR50 stuck with Wireless Warning Off after upgrading to version 2.7.2.104
I have been using my ORBI RBR50 for quite a while, with no issues whatsoever. Today I get a message on my Orbi App, asking to upgrade to the latest version (v 2.7.2.104), and, as I usually do, I...
lcba813 wrote:Is there anything I can do? The product is out of support by now, but I think it is not acceptable to have a fully functional product get damaged because a routine firmware upgrade
"out of support: can mean (a) past 90 days of "complimentary" support, or (b) past the 1 year warranty, or (c) both. Which is it?
Amazing that it will operate enough to do a manual firmware update, but cannot turn on the radio.
It could be that the only remedy left is to TFTP the firmware to the unit.
https://kb.netgear.com/000059633/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP-client
https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP
There was a fascinating discussion in 2019 about disabling/enabling WiFi radios on the Orbi. (a) a telnet method and (b) a method using developer mode on the web interface. The action picks up about post #10
Maybe the "enable" trick will wake up the radios?
That's not going to work, on my /dev there are no athX devices... if no athX devices are present, none of the "higher level" programs will work.
I'm trying to figure out how to enable the kernel module and add the athX devices. That way maybe I could fix this. A little help from an insider would go a long way.
The device is past the one year warranty. Everything works fine, but the Atheros devices are unloaded due to the kernel bug.
What I'm trying to figure out now, is if there is a way to fix the failure in the firmware. I am guessing there is something that went wrong writing to the actual qualcomm device ROM or something.