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
The process that you need to follow has already been outlined above in detail.
You have no other option but to get to the CFE subsystem, and start the tftpd server, and send the firmware image.
You still have not answered a number of questions so I'm not sure what is actually going on and you haven't provided a trace of the output from PuTTY when it is connected to the router serial port and the router is powered on.
You really need to be able to reliably connect to the serial connector of the router and see what is being output by the router (this is not PuTTY, it is console output of the router).
This is the only way to wok out what is going on and you should see "something" even if it is just an error message.
Forget about the ctrl+c for a moment, connect the USB-TTL cable to the serial port of the router and capture the output from power on then post that.
Right now that's all that's needed to try and work out what's going on.
If you don't see any output then I have to think the serial communication is not working for some reason, check the PuTTY settings etc.
Yes, you could have corrupted the CFE, which is also game over, I don't know how to recover that.
While it's possible the CFE has been corrupted it's unlikley.
PuTTY is frequently used for this by Windows users, there's no reason to think it can't do what's required here.
I don't use Windows, if I can possibly avoid it, so I don't know about alternative terminal emulation software.
Ian
Hi.
I tried to get the information to you.
I send you my pictures on the monitoring display. hopefully you see some thing good.
Peter11742
