NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Anything I should do before rolling back firmware?
Router: R7000 Nighthawk AC1900 We get dropped connections maybe at least once a day that requires turning our router off and back on. We have tried multiple things ranging from editing the DNS serv...
> When you say "reinstall", [...]
I don't know what that meant.
> [...] Or does the firmware remain the way it was at the moment I reset
> the router? [...]Yes. A (misnamed) "Factory Reset" is simply a settings reset. It
does not change the firmware version.> [...] I read somewhere that firmware version isn't affected by a
> factory reset.I've read many things in many places, but that one's true.
That said, I might expect loading new firmware not to require a
settings reset. The new firmware should be able to cope with (and/or
convert) old settings as required. However, when loading older
firmware, I'd do a settings reset and manual reconfiguration. I would
not expect old firmware to deal correctly with newer settings.But, notwithstanding my expectations, after loading _any_ different
firmware, if the gizmo behaves badly, then I'd try a settings reset and
manual reconfiguration before declaring a disaster. ("Trust no one," I
always say.)
> [...] I was considering going to 1.0.9.42Should be harmless.
One other preparatory step would be to fetch a firmware kit for your
current firmware. In the unlikely event that the old firmware cripples
your Internet access, you'd have what you'd need to restore what youhad.
> What is the current firmware version? "roll back" to what?
The current firmware is 1.0.11.100_10.2.100 and I was considering going to 1.0.9.42
The current firmware is 1.0.11.100_10.2.100 and I was considering going to 1.0.9.42
> When you say "reinstall", [...]
I don't know what that meant.
> [...] Or does the firmware remain the way it was at the moment I reset
> the router? [...]
Yes. A (misnamed) "Factory Reset" is simply a settings reset. It
does not change the firmware version.
> [...] I read somewhere that firmware version isn't affected by a
> factory reset.
I've read many things in many places, but that one's true.
That said, I might expect loading new firmware not to require a
settings reset. The new firmware should be able to cope with (and/or
convert) old settings as required. However, when loading older
firmware, I'd do a settings reset and manual reconfiguration. I would
not expect old firmware to deal correctly with newer settings.
But, notwithstanding my expectations, after loading _any_ different
firmware, if the gizmo behaves badly, then I'd try a settings reset and
manual reconfiguration before declaring a disaster. ("Trust no one," I
always say.)
> [...] I was considering going to 1.0.9.42
Should be harmless.
One other preparatory step would be to fetch a firmware kit for your
current firmware. In the unlikely event that the old firmware cripples
your Internet access, you'd have what you'd need to restore what you
had.
- > I don’t know what that meant
That question was directed to plemans when he suggested “reinstall the firmware over ethernet. Then factory reset and manually reinstall” The fact that “reinstall” was in there twice kind of threw me off, because if firmware remains the same after a reset then I don’t understand the need to reinstall it again after the reset.
And for the record the firmware was originally installed via ethernet (for plemans). It had to be since at the time the firmware it is currently running was installed I had to resuscitate the router back to life by installing firmware via ethernet through command prompt. The router was totally unresponsive a few weeks back for whatever reason, but installing firmware with command prompt booted it back up.
Thank you by the way for all the replies. They are helpful. I’m sort of the “IT guy” in this house, so when something goes wrong I typically have to find ways to fix it, often times with a little help from the internet.
Qu9ke wrote:
> I don’t know what that meant
That question was directed to plemans when he suggested “reinstall the firmware over ethernet. Then factory reset and manually reinstall” The fact that “reinstall” was in there twice kind of threw me off, because if firmware remains the same after a reset then I don’t understand the need to reinstall it again after the reset.Sorry if I wrote it poorly or didn't explain fully. I meant just try reinstalling the current firmware first, the reset and reinstall as option 1. Try that and see if it works prior to downgrading the firmware. A reset only removes settings. If there's an issue with corrupt firmware, a reinstall of the firmware is needed. Its worth trying with the current firmware first. Then if it doesn't work, the downgrade option. And you don't always have to reset afterwards but if there's issues after changing firmware, sometimes a reset and manual reinstall helps if an old/retained setting is causing the issue.
Qu9ke I'm sure it's entirely unnecessary, but when I very successfully upgraded via ethernet my firmware from v.64 to v.100, I disabled WiFi within the router settings prior to carrying out the upgrade. I just didn't want any chance of the router attempting to connect to the internet via any other means whilst I was carrying out the operation. As I say, probably zero need to do what I did, but it made me feel better. I think I carried out a reset prior to and after the upgrade. Whatever, I just followed Netgear's instructions on their downloads page. I then did all of the other 'tweaks' before turning WiFi back on and splitting my networks into standard and Guest.
By the way, neither would I ever attempt an up/downgrade via the Nighthawk App. That's just a personal thing by the way. People should however do what they feel comfortable with, as long as they follow the correct procedures.
And for the sake of repeating myself, I have had no problems whatsoever with firmware version .100. For me, it isn't 'broke' or 'borked', no WiFi drop outs on 5ghz band at all, it's worked perfectly since installation on 4th April - apart from Logging reporting DoS attacks, sorted that by disabling Logs. Netgear default NTP server dropping out of sync, sorted that by changing NTP to a local UK server.
Probably best to disable auto update feature, disable UPnP, don't use Smart Connect and change DNS servers. Your choice though!
