NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Havok970
Apr 18, 2021Tutor
Solid orange power LED after firmware update
Greetings,
My son initiated a FW update and after reboot it came up with a solid orange power LED. Cannot even get a link LED on the uplink port using a known good cable.
Troubleshooting:
Never get l2 to known good port on known good router (unlike this POS) on known good cable from uplink on Netgear (aka POS)
I have tried every "factory reset" possibility. If I power it up with the reset button pressed, it changes to flashing white yet NEVER gets l2 with my Mikrotik on known good cable in known good port plugged into the uplink. When I reboot it, it comes back to solid orange power LED. It was on a static and I did remove the lease on my Mikrotik JIC, but still can't even get l2.
After reading countless similar issues, including the fact that they removed TFTP instructions and then put them back up, I have to wonder if they are disabling the uplink port now to prevent people from using the TFTP fix. I can get l2 on the other ports, but no mac shows up, so likely turns into a hub, but no excuse why port LED's on the POS don't work (or why there are not actual LED's on the uplink port, either)
This issue is COMPLETELY AVOIDABLE. The power WAS NOT INTERRUPTED DURING FW UPDATE, which makes me consider the possibility this is PLANNED OBSOLESCENCE, especially combined with the reasoning above.
Flash memory is ridiculously CHEAP now, so there is zero excuse for not having dual FW memory and checksum verification. It wouldn't surprise me if this hardware is capable and they just didn't do it.
I do see "hidden SSID" intermittently broadcast from the device on WiFi analyzer, but cannot connect or even see it from the Nighthawk or Genie apps. By all evidence, Netgear bricked the device on purpose irrecoverably through lack of due diligence at the very least.
9 Replies
Sort By
> [...] Cannot even get a link LED on the uplink port using a known good
> cable. [...]What does Netgear call this "the uplink port"? If you mean the
WAN/Internet port, then the "Internet" LED does not behave the same as
the LAN Ethernet port-status LEDs (and so it does not indicate a simple
physical link).Visit http://netgear.com/support , put in your model number, and look
for Documentation. Get the User Manual (at least). Read. Look for the
LED descriptions and "Troubleshoot".
> After reading countless similar issues, [...]The non-psychics in your audience might not know what you've been
reading.> [...] I have to wonder if they are disabling the uplink port now to
> prevent people from using the TFTP fix. [...]Huh? The TFTP recovery scheme uses a LAN Ethernet port, not the
WAN/Internet Ethernet port.- Havok970Tutor
I'm somehow unsurprised an alleged "guru" doesn't know "Uplink port" is standard network terminology, or that the uplink port is usually the default management port, and was more invested in insulting my submission than solving the problem. I maintain this problem is 100% avoidable and thus I have REASON for snark. Thanks for nothing, "guru"
- Havok970Tutor
I further went down the rabbit hole, unfortunately.
Luckily I looked through the procedure or I would have been even more upset at this issue that was directly caused by Netgear's lack of due diligence in making a firmware update process that doesn't commonly brick the hardware.
I read through the manual. According to it, solid orange is booting and blinking white means corrupt firmware. It sent me to this site with no other instruction, as if support would magically fix it.
I looked over the tftp procedure, something I've worked with on enterprise networking equipment. It is completely inadequate because my son's router never gets to blinking power as detailed on step 6:
6. Watch the Power LED. It will start with an orange color and then start flashing.
If that is something that only happens when a device is programmed with an IP and connected to a LAN port, this is not documented. Instead of re-IPing my computer for no reason, I would like some assurance that this is indeed the case, preferrably by Netgear support.