Hello. I just picked up one of these routers from newegg during their recent $20 sale and I found this thread and became very excited to try this out. Is there any way to tell if I have a v1 or v2 WNR2000? Netgear's site is proving to be not much help. When I tried uploading the .CHK file to my WNR2000 it told me to please provide the correct file extension (.img).
Hello. I just picked up one of these routers from newegg during their recent $20 sale and I found this thread and became very excited to try this out. Is there any way to tell if I have a v1 or v2 WNR2000? Netgear's site is proving to be not much help. When I tried uploading the .CHK file to my WNR2000 it told me to please provide the correct file extension (.img).
Any help would be greatly appreciated!
Thanks
Easiest way is to just look at the bottom as it will say just WNR2000 for a v1 and WNR2000v2 for a v2. But since it's asking for a .img firmware, I can tell you that you have a v1 as looking at Netgear's site, the v1s use a .img file whereas the v2s use a .chk file. Sorry.
Does that mean dd-wrt cannot run on WNR2000v1? Are we completely out of luck?
The v1 is Atheros based so pop over to the dd-wrt Atheros subforum and read the WNR2000v1 thread. _________________ Kernel panic: Aiee, killing interrupt handler!
WNR2000v2 doesn't run DD-WRT either. I telnet-enabled mine, logged in and promptly bricked it with a 'write some-ddwrt-image.bin linux' command. The HW reset doesn't appear to work anymore either. If throw a JTAG connector up on this mofo can I somehow recover it? Or is it hammer time?
WNR2000v2 doesn't run DD-WRT either. I telnet-enabled mine, logged in and promptly bricked it with a 'write some-ddwrt-image.bin linux' command. The HW reset doesn't appear to work anymore either. If throw a JTAG connector up on this mofo can I somehow recover it? Or is it hammer time?
Who told you to install dd-wrt that way?
Fekkin dumb way of doing it when the only dd-wrt file released for this router is intended to be used directly from the Netgear Administration/Firmware update page in their gui.. _________________ Kernel panic: Aiee, killing interrupt handler!
It wasn't accepting the CHK file I found. All in the past now.
It seems like me flashing the wrong firmware and their being an error during the web ui flash failing probably put you in the same the state in the end. Is there hope at this point? Or perhaps another way to reset the factory default? I don't have any problem sticking the JTAG pins in. Already got the case cracked open.
The jtag pinout of this router is not known.
You don't need to fiddle with jtag, you need a serial TTL converter so you can see what you are doing, see what happens during boot.
Start with reading this thread from the first post and you'll know everything you need for getting a serial connection to the router. _________________ Kernel panic: Aiee, killing interrupt handler!
Suppose the serial console showed the flash was bad and the boot failed before I can do anything; what happens then?
The nice thing with a serial interface is that you don't have to suppose, you will know and knowledge always beats guessing..
It is the number 1 rescue tool to get and it only costs $3 more than what 5 resistors does.
If your boot loader is damaged (which they rarely are when a router is bricked) then you'll have to find out if there is any jtag connection in that router and what the pinout is. _________________ Kernel panic: Aiee, killing interrupt handler!