NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R8500 bricked
Hi All. This is my first report. I purchased on purpose the above router on Ebay. I can not register it Serial 4DG65B7G019C5 it is used like mint. The reason i found it is the best range router an...
This is my final procedure after I fixed the second router r8500.
1) J4 connector pins : 1 2 3 4 pins are visable by looking the motherboard and they are located in the front view.
and j4 mark is located next to #1 pin. 1 gets green color, 2 gets white color, 3 gets green color, 4 is not connected.
2) open the bottom cover by removing the 6 tork screws.
Take the cover half way out so you can see the j4 plug and plug the serial cable.Turn on the router.
3) Start Putty let it run for a minite or so and start sending control c commands until you will see CFE.
4) on CFE type nvram erase you will see a 0 as an answer.
5) On CFE type tftpd you will get tftpd server ready ::
6) go on comand mode dos cmd>tfttp -i 192.168.1.1 put C:\r85.chk
r85.chk will be your old firmware located on the c:\ main directory
7) Now you will see a blue led on the #1 port flickering comminicating.
8) if what you did is correct then you will get from dos and putty file tranfered successful.
9) Now hold the reset button with a pin and turn the power off.
10) with the pin on reset turn power on and waight for 3 reboots let the pin go.
11) waight for 2 minutes you will see many led's comunicating and final the main led will be normal.
12) The router is now ready to be configuerd.
13) The network name and password is located on the white paper top right or at the bottom of the router.
I did 2 units the first one it took 1 week the second one it .5 hour.
Good luck.
peter11742
This is a better picture.
Hi.
Thanks to all that they helped.
As you see we have an issue Houston.
The pictures prove it.
I reboot the router and of cource I have no pings and an orange steady light. The router reboots every 3 minutes.
I hope there is a solution for this from the people that work before on the routers.
As you see my experiance is only one week knowing nothing for the routers.
Engineers are good because they are trained to tackle any task.
Best regards.
peter11742
There seem to be a few threads on the Internet similar to what you have. One suggestion I found is to do erase nvram or nvram erase at the CFE prompt. Then reboot.
Thanks.
I fixed my win 10 laptop so now I can work and give you details.
I do not know how to delete the nvram but I will google it.
Now I send to everyone a new picture. The CFE worked this time it reported the software was tranfered.
To the people who have trouble transfering software it will be the dos causing it you must restarted dos.
At this point we made a good effort for this router I will tell any one it is the best motherboard I see in a small unit "good job netgear".
We can improove and make it better because it is builded with an engineer that had this in his mind for futer expantions.
peter11742
So you've transfered the firmware again and you've seen a confirmation it has been written in the CFE output.
That much seems to clear now.
But you still haven't provided what I asked for.
A text file of the output of the router from the USB-TTL connection from power on until after you see an error or the output stops or the router faults and reboots.
That should show if:
1) the firmware has been saved successfully (so we know the device it is saved to is not faulty).
2) probably give some indication if it is the settings that are corrupted (which is likley).
You are welcome to Google "nvram erase" which is probably what's needed, executed at the CFE prompt.
For my part, I'm not so quick to do so becuase I have wiped out information that could not be recovered in the past.
That shouldn't be the case with Netgear devices though and it looks like you have no choice so, as has been suggested, at the CFE propmt type "nvram erase<enter>".
I'd recommend leaving the router a little while after the erase, probably 30 seconds or so, even though it's probably not needed.
Then I think you can the just type "go<enter>" at the CFE prompt and have the router boot.
Alternately (and probably preferably, and is what I would do) power off the router for a few seconds and then turn it on and observe the boot output in PuTTY to check how far it gets.
Ian
