NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR50 spontaneously bricked itself this morning - factory reset has no effect - what are my options?
I woke up to find I had no wifi and no internet. My two satellites had solid magenta rings. The router had power but no illuminated ring. I I tried to connect directly to the router via ethernet I co...
cortex wrote:
vajim wrote:
cortex wrote:I woke up to find I had no wifi and no internet.
Any recent firmware update by chance?
Not that I performed. Does the unit auto-install new firmware? If so I wouldn't know -- and since I can't get to the configuration page I can't tell what firemware it's running.
How about the app?
Some are confused about firmware updates using the app. Unless there are major security updates you are in control.
I had a similar problem a few days before you. I logged into the web interface to check something but strangely it wouldn't display the contents of some frames - I would get a server error (I can't remember which HTTP code). That was very weird (NETGEAR: it was broken) so I rebooted the device. It then bricked itself; the power LED flashed RED which, according to the manual, means "corrupt firmware". So I did the factory reset a few times until it blinked the right colour.
I used my phone to download another firmware image and TFTP'd that to the device over an ethernet cable from my laptop. I had to set a static IP in 192.168.1.0/24, but the router responded to 192.168.1.1 and consumed the TFTP image. I then left it for a while. Nothing. I tried again. This time it came up and I could log in.
How many times did you tri the reset before the LED turn the right color?
What version of FW were you able to load?
Glad you got it working.
growly wrote:I had a similar problem a few days before you. I logged into the web interface to check something but strangely it wouldn't display the contents of some frames - I would get a server error (I can't remember which HTTP code). That was very weird (NETGEAR: it was broken) so I rebooted the device. It then bricked itself; the power LED flashed RED which, according to the manual, means "corrupt firmware". So I did the factory reset a few times until it blinked the right colour.
I used my phone to download another firmware image and TFTP'd that to the device over an ethernet cable from my laptop. I had to set a static IP in 192.168.1.0/24, but the router responded to 192.168.1.1 and consumed the TFTP image. I then left it for a while. Nothing. I tried again. This time it came up and I could log in.
This happened at 3 am so my memory isn't the best, but after 3 or 4 factory resets all resulting in the "corrupt firmware" state (blinking red), I acquired and managed to TFTP the firmware across. It then failed to boot, but the error had changed from blinking red to blinking amber. Then I did a reset another couple of times and TFTP'd the image again until it seemed to do the right thing.
/edit: My impression was that the TFTP server was up always in the blinking-red state, but in the blinking-amber state it was only up for a few seconds before boot proceeded at normal.
The firmware version I used to get it "working" was 2.7.2.102.
growly wrote:I had a similar problem a few days before you. I logged into the web interface to check something but strangely it wouldn't display the contents of some frames - I would get a server error (I can't remember which HTTP code). That was very weird (NETGEAR: it was broken) so I rebooted the device. It then bricked itself; the power LED flashed RED which, according to the manual, means "corrupt firmware". So I did the factory reset a few times until it blinked the right colour.
I used my phone to download another firmware image and TFTP'd that to the device over an ethernet cable from my laptop. I had to set a static IP in 192.168.1.0/24, but the router responded to 192.168.1.1 and consumed the TFTP image. I then left it for a while. Nothing. I tried again. This time it came up and I could log in.
Unfortunately my unit seems to be even more bricked than "corrupt firmware" since the power LED does not change color at all and does not respond to resetting.
have you tried this:
https://kb.netgear.com/31486/How-do-I-reset-my-Orbi-system-to-factory-default-settings
if you you have and it's still under warranty reach ou to one of the moderators here
vajim wrote:have you tried this:
https://kb.netgear.com/31486/How-do-I-reset-my-Orbi-system-to-factory-default-settings
Yes, it doesn't work. The power LED never blinks another color and the device does not reset in any way.
Unless your interested in trying this as a last resort effort:
You'll need to get your RBR replaced.
cortex wrote:Unfortunately my unit seems to be even more bricked than "corrupt firmware" since the power LED does not change color at all and does not respond to resetting.
FURRYe38 wrote:Unless your interested in trying this as a last resort effort:
You'll need to get your RBR replaced.
cortex wrote:Unfortunately my unit seems to be even more bricked than "corrupt firmware" since the power LED does not change color at all and does not respond to resetting.
So I actually tried this and it did not work. I bought the USB to serial adapter, dissasembled the router, connected with PuTTY but it does not grant access to U-boot. My unit musy be very non-functional (as indicated by the lack of LED color change or any other response from the unit). Thankfully my CC extended warranty protection covered me and I've learned to avoid Netgear products from now on.
