NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R8000 Firmware v1.4.1.30_1.2.26 won't restore config from previous firmware
Hi guys
I've just upgraded to the latest version of the firmware for my R8000. There was lots of messing about (Netgear servers must have been busy or something) but after the firmware was applied, it looked like it had done a factory reset.
So I went back to a backup of the config that I had taken just before the upgrade and tried to restore that.
I didn't get any errors, but the restore finishes & seems to have no effect - the original settings are not imported.
The issue is that I have around 60 fixed ip addresses setup which is going to be a nightmare to reinsert manually.
Please don't tell me that the old backup of the config when running the old firmware (only a few versions older) is not compatible.
Hope you can help
Trevor
So my accepted solution (NG want me to provide one), is to no longer use NG for saving lots of config as they can trash my data whenever they want and expect me to type it in again - not doing that!
Instead I'm using a Raspberry PI as a DHCP server and disabling this feature on the NG router.
That way I can properly back up the settings.
18 Replies
That firmware version is not for the R8000, but either an R8000P or R7900P.
Usually if one does hit a problem, a RESET and manual entry of the settings is advisable. It really depends on what was changed?
Is it possible you got a corrupted d/l?
rowets wrote:
There was lots of messing about (Netgear servers must have been busy or something) but after the firmware was applied, it looked like it had done a factory reset.
It is normal for the router to re-boot as it is internally installing the firmware. I'll assume you did the install via a browser Genie? Don't understand the part above about the NG servers... normally it is a fast d/l and then the router starts updating. Not sure what you meant by 'messing about' but it is possible you had gotten a bad d/l. I'd try getting it again via SUPPORT and try again. I'd advise against using a backup if you did indeed lose all settings.
Yes, it was a problem selecting the correct model from the web pages, I have a R8000P (sorry about that), I'm in the UK and it wouldn't let me select the exact model from the web page
When trying to connect to N/G it just sat there for ages trying to download the firmware, but it got there in the end
I don't think it's a corrupted download as the router is working perfectly.
The reboot I understand, I've that many times in the past on firmware upgrades
But after this firmware upgrade, it went into a complete reset of the router, eg, new network names, new passwords, and all the fixed ip addresses that I'd set up and all the other settings that I can't remember.
Is it expected behaviour that this firmware will completely reset the the router and the config files created on previous firmwares will not work
rowets wrote:
But after this firmware upgrade, it went into a complete reset of the router, eg, new network names, new passwords, and all the fixed ip addresses that I'd set up and all the other settings that I can't remember.
Is it expected behaviour that this firmware will completely reset the the router and the config files created on previous firmwares will not work
Sorry, I can't comment on this specific router, but I've owned my NG routers and others as well and I've never seen this?
I'd guess it might be possible due to the problems getting the file down, could have been a timing issue even, I do not know?
I guess since you are at 'square one' with the router you might want to go back a level, set a few settings, like SSID names and then upgrade again and see if they hold? If they do, it might have been something odd happened? Not knowing what actually changed code wise in the firmware it would be hard to tell if it could/would wipeout settings or not?
Since it is working, you might want to turn off AUTO-UPDATE if the firmware supports it. Of course, sometime in the future, a security fix might be made you'd want to update at that time.
