NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R6300v2 -- Bad Firmware on Netgear site R6300v2-V1.0.4.12_10.0.77.chk
Guys
BEWARE that The latest October 2017 firmware for R6300v2 is bad. I had manully download 'R6300v2-V1.0.4.12_10.0.81.chk' and the router stopping issuing IPs and turned into a brick. Now I can't even log into admin after resetting to default (because it can't issue IPs anymore).
The built-in "Router Update" option does not find the above version. It only finds R6300v2-V1.0.4.12_10.0.77.chk. I tried to overwrite afterwards (i,e, downgrade from R6300v2-V1.0.4.12_10.0.81) but the damage was aready done. My router is out of warranty so I have no way out other than buying a new device.
Please don't download R6300v2-V1.0.4.12_10.0.81.chk stay with R6300v2-V1.0.4.12_10.0.77.chk.
Do you mean that even after a factory reset you cannot access the device?
If so, you may not have reached the end of the road.
First try this:
- Press reset for 30 seconds
- Keep pressing reset while removing power
- Keep pressing reset for another 30 seconds while apply power
If that fails, move on to this:
How to upload firmware to a NETGEAR router using TFTP | Answer | NETGEAR Support
2 Replies
Do you mean that even after a factory reset you cannot access the device?
If so, you may not have reached the end of the road.
First try this:
- Press reset for 30 seconds
- Keep pressing reset while removing power
- Keep pressing reset for another 30 seconds while apply power
If that fails, move on to this:
How to upload firmware to a NETGEAR router using TFTP | Answer | NETGEAR Support
Thank you Micahel. Initially I did the reset as described, but it didn't help. In fact's that's when I lost total control of the device probably becuase it won't even issue an IP after the reset and using admin and default password it came with.
I went to Costco an bought a new router. Couple of days later I was playing with the above device and it worked this time.
Thank you again for your post though.