NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RBR50 firmware upgrade. now unit stuck with green solid power light and nothing else.
after attempting firmware upgrade from the web page, my rbr50 is now unresponsive. power light glows green and thats it. i have tried the 30.30.30 reset and it does not change anything. unable to ...
2.7.2.104 is what i'm trying to put back on it after upgrade by web interface failed with 2.7.3
on windows 10, tried both tftp64 per one message as well as built in tftp client on windows 10 pro.
pressing reset for 30 secs does not change the light from solid green to anything else.
triack wrote:2.7.2.104 is what i'm trying to put back on it after upgrade by web interface failed with 2.7.3
on windows 10, tried both tftp64 per one message as well as built in tftp client on windows 10 pro.
pressing reset for 30 secs does not change the light from solid green to anything else.
My understanding is that there is a brief window of time during startup when the hardware looks for a tftp connection before beginning the regular boot up process. Rather than using the paperclip, power the Orbi off, (say a brief prayer or mantra), power it back on and try tftp.
I once took 4 or 5 tries to get tftp to work.
Using tftp is quite a chore, what with having to change the computer to a static IP address and cable it directly to the Orbi, but it has worked several times for me.
no good, unable to get tftp to even show an attempted connection from the orbi
> on windows 10, tried both tftp64 per one message as well as built in
> tftp client on windows 10 pro.I'd stick with the command-line TFTP client program. Better error
messages, if nothing else.> no good, unable to get tftp to even show an attempted connection from
> the orbiA vague description of what does _not_ happen is less useful than a
clear description of what _does_ happen."unable" is not a useful problem description. It does not say what
you did. It does not say what happened when you did it. As usual,
showing actual actions (commands) with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.The TFTP recovery scheme is a multi-step procedure which offers
multiple opportunities for user input, hence user error. By itself,
saying that you "tried" it doesn't say much. See "As usual, [...]",
above. Especially when using a command-line program, copy+paste is your
friend.
> [...] a brief window of time [...]
"unable" also doesn't say _when_ you did anything.unable... yah.....
trying to get orbi into tftp mode....
hold reset for 30. release, hold reset and power on, still holding reset for 30 sec, release reset.
power light stays green during intire process.
at this point, even attempting to use the put command in eather TFTP client, results in no connect to orbi.
so what would you sugest to try next. since holding reset for 30 secs and power up orbi does not put it into a state to accept an tftp connection.
Last resort could be this:
https://www.snbforums.com/threads/custom-firmware-build-for-orbi-rbk50-rbk53-rbr50-rbs50-v-9-2-5-1-18sf-hw-v-9-2-5-1-18-1sf-hw.64414/page-3#post-590839
https://community.netgear.com/t5/Orbi/Is-my-13-month-old-RBR50-bricked/td-p/2009904/jump-to/first-unread-messagehttps://community.netgear.com/t5/Orbi/ORBI-RBK50-RBS50-Tips-Tricks-Hidden-Secrets-etc/m-p/1745266#M60729
https://community.netgear.com/t5/Orbi/Orbi-Router-Auto-Firmware-Update-Switch/td-p/1743269/jump-to/first-unread-message
If your system is under warranty, you might make contact with NG support...
triack wrote:no good, unable to get tftp to even show an attempted connection from the orbi
not under warranty... bummer
