RBR50/RBS50 Firmware not automatically updating to 2.5.1.8

FINAL (we hope!) Reply edits in BLUE again.

---

CrimpOn wrote:

---

TheGardners wrote:

Thanks for the response, CrimpOn. I've responded to each point below in blue.  I will do red again!

---

CrimpOn wrote:

---

TheGardners wrote:

I have attempted to update the firmware automatically on the RBR50 and it does not apply the update.By this you mean that the Firmware Update says that no new firmware is available?  Or, do you mean that the web page listed new firmware, but clicking on the link did not result in upgrade? The page does list the update, but multiple attempts to apply it simply resulted in "pseudo-availability" where the router goes through multiple many-minutes long cycles of down/up with no change to the version when it settles back to a seemingly normal state. This is a new development.  I had not realized that Netgear was "announcing" 2.5.1.8 on the Firmware Update page.  (Of course, I can't verify that because I updated already. I could "go back" to 2.3.5.30, but even I am not that dedicated.) I rebooted the router last night because the web admin UI was acting very flaky. This time, it showed the actual link to the info on 2.5.1.8, so I chose to "Update All" (the satellites showed that they were already at the latest version). It appears to have worked this time! The admin page for the router showed "Updating Settings ||||||||| [etc.]" and then rebooted again. After the reboot, the router logged in at "orbilogin.com" (new) and showed the latest firmware version to be correct.

 

I have also attempted to manually update the firmware on my RBR50 to 2.5.1.8 via the downloaded zip file and the resulting .img file upload. It seems to attempt the installation, but will not apply the update. This is the procedure followed by everyone who has upgraded to 2.5.1.8 thus far (me included).  At what point does it "go bad"?  Is there a message? In a manner similar to the above for the auto update, it seems to be applying the manually uploaded IMG file, but when the router stabilizes after the down/up cycles, it is still running v2.5.0.38. There are never any messages implying any warnings or errors.  So, going step-by-step, "Browse" to find the .img file was successful, the update started, the "Progress Bar" went across the screen, then it asked you to log in again, but the version remained the same?  (all of those steps?  did I leave any out?)

 

In my opinion, whether it is a major firmware update or not, the router should handle this activity as part of intended functionality and not cause so much grief in the community. Absolutely agree.  The topic of firmware upgrades has dominated the community forum for at least six months.  I have lost track of the number of participants who declare, "Nothing from Netgear - Ever Again!!!" I don't think I feel quite so strongly... :) I tried Linksys Velop and Google Home mesh networks before deciding to toss some cash to the Netgear Orbi platform. We are also an Arlo home and are mostly (ha!) happy with that product, too. Despite this frustration on the RBR50, the performance of the Orbi pseudo-mesh has been vastly superior to both Linksys and Google. And the configurability is better, too. So... I'm not in the camp of "NEVER AGAIN NETGEAR". I believe that the Netgear products are decent. Nowhere near ideal, but better than most.

---

---

---

I can think of a few alternatives:

1. Perform the dreaded "Factory Reset". https://www.youtube.com/watch?v=cMw4ePACgc4 
   People hate doing this because it means they have to enter all of their "assigned" IP addresses and devices names/types again.  It could be that a "clean slate" would make the RBR50 more capable of doing the upgrade.
2. Force a firmware "flash" using TFTP: https://kb.netgear.com/000059633/How-to-upload-firmware-to-a-NETGEAR-router-using-TFTP-client This is not for the faint of heart.  And, it will result in the same thing as a Factory Reset: everything has to be configured again.
3. Wait it out.  The 2.5.0.38 firmware annoyed people because it totally trashed the "device naming" tables.  If you are not having a problem with the Orbi and are thinking, "Maybe I ought to update the firmware?".... Maybe just leave it alone?

Geez.  You come here for help and get some lunatic.

---

I'm okay with very helpful lunatics! :)

Thankfully, in this case, no factory reset was needed. WHEW!