NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RBW 30 Firmware 2.5.0.4 and 2.6.1.6 files are corrupt
Before and after unzipping firmware downloads for RBW30 versions 2.5.0.4 and 2.6.1.6, the firmware file is labeled as "Recovered File Fragments" instead of "Disk Image File" that I get when I downlo...
In file explorer I changed the extension of the unzipped firmware download file from .chk to .img
then I had to connect to each RBW30 unit individually using their respective IP addresses. From there I could work through the menus to get to manual firmware update and use the renamed .img file. The file loaded and updated.
> In file explorer I changed the extension of the unzipped firmware
> download file from .chk to .img
I'd expect that not to be helpful, and to cause more trouble than it
might save. Some devices won't accept a file with the wrong file type
(".XXX").
> [...] and use the renamed .img file. The file loaded and updated.
And did that method _not_ work with a file with its original name?
Based on your comment that there was nothing wrong with the file but perhaps the arbitrary file ext name and your implication that Netgear and Windows might not be on the same page when unzipping and naming the file, I figured changing the file ext name might work.
As for connecting to each individual satellite, no I did not try that with the .chk file because the ORBI manual update page told me that the file type was wrong when I tried to upload the .chk file. I don't remember the message after I changed the ext to .img, but it wasn't wrong file type. Whatever the message, it occured to me to try to connect to each satellite one at a time and do the upload that way.
Some other notes: my RBW30 were not factory paired to the RBR50. The three RBW30s had been part of another system and I had to reset them in order to pair them to the RBR50.
I previously had trouble updating this and another RBR50 which came with firmware versions in the 1.x.x.x range which would not auto update to the current 2.7.1.60.. I eventually manged to update to 2.7.1.60 by updating first to the lowest 2.x.x.x, then 2.2.1.212, then 2.7.1.60. I stumbled on this solution after reading the release notes on random 2.x..x.x updates. It would be nice if the release notes on all updates included some of these secrets. If Netgear thinks that no one would want to update 1.x.x.x firmware to the latest version, they should think again. My RBR50s came right out of their shrink wrapped boxes Some date stamps on the packaging showed one unit dated from 2017 and the other from early 2020.