NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
New - Orbi RBR50 Router Firmware Version V2.7.2.104 Released
Security Fixes: Fixes security issues This firmware addresses security vulnerabilities. For more information about security vulnerabilities, visit https://www.netgear.com/about/security. Downloa...
- I became aware of the latest firmware while browsing this forum. Neither the app nor the web interface indicated an available update. I downloaded the files via my computer and performed a manual update via the web interface -- one satellite first, then the other, then on to the router. (RBK50) In the past, I have had updates pushed out (only once); notices both on the web and app of firmware updates available; and updates that I found were released via this forum which I've manually installed (the latter seems to be the most frequent way I have updated firmware). Through all ways, I have never had the slightest issue with downloading and installing updated firmware.
HTBruceM wrote:So next I tried the TFTP update method on one of the Sats. Isolated on a dedicated PC ethernet connection with manual IP. TFTP would not work, no blocks were transmitted. The sat would configure itself to IP address 250. I could PING it from the PC. But I could not open it's web pages, and I could not upload the FW file via TFTP. Tried resetting the sat numerous times and no dice.
My experience with TFTP has been erratic. There seems to be a brief period after the device is powered on when it will respond to TFTP and when I missed that time slot, TFTP would not work. I would try more times.
"TFTP active window"... Yeah that makes some sense to me. I will continue to work in this solution.
The sats never get far enough to even enable the WiFi radios, and they won't update (or finish updating/booting) on the wired backhaul connection either.
TFTP seems to be my only path to unbrick these sats at this point.
This is serious stuff: if the firmware update process leaves devices in "bricked" state.
How did you update the firmware? App? web interface?
Advice: create a new thread with descriptive subject. Better than adding to a long thread which is marked "solved"
alokeprasad wrote:This is serious stuff: if the firmware update process leaves devices in "bricked" state.
How did you update the firmware? App? web interface?
Advice: create a new thread with descriptive subject. Better than adding to a long thread which is marked "solved"
The last time I did a firmware update I did it from the PC login - web interface
https://kb.netgear.com/000059634/How-to-upload-firmware-to-a-NETGEAR-router-using-Windows-TFTP
Need to press the reset button for 30 seconds then release, then it send to PUT the command and upload the FW.try nmrpflash?
Try that when tftp doesn't work
HTBruceM wrote:"TFTP active window"... Yeah that makes some sense to me. I will continue to work in this solution.
The sats never get far enough to even enable the WiFi radios, and they won't update (or finish updating/booting) on the wired backhaul connection either.
TFTP seems to be my only path to unbrick these sats at this point.
Thanks for that hint.
My first mistake was not doing the hard factory reset ahead of the TFTP load. The instructions given were somewhat generic and not specific to the Orbi. The instructions just said to power off/on and then hit the PUT button on the TFTP app when the power LED blinks orage. Well that never happens on the Orbi. It blinks RED.
My 2nd mistake was not waiting for the power LED to start blinking red while pushing the reset with the paper clip. Unless it blinks red, it is not going thru the proper factory reset sequence.
My 3rd mistake was not using 192.168.1.1. Since this sat kept coming up to 250, I assumed that was the address they used for the TFTP after reset. Wrong. It is 192.168.1.1. I had been testing/pinging address 250 because the sat was coming up to that address in its "hung up" state; assuming it would also do that upon the factory reset.
Sadly after it did appear to load up the 2.7.2.104 FW, it came back to the same place. Forever pulsing the white LED ring.
My next step is to re-load the previous FW into the SAT using the TFTP process again. Maybe it's not bricked after all.
