1. Begin with WNR2000v2-V1.2.0.8_36.0.60NA.chk (from Netgear) running on the device. (If you're bricked, nmrpflash will save the day*. Many "bricked" states of this router are recoverable this way.)
  2. Proceed as the wiki dictates, by initially flashing trailed mini Broadcom K26 build 15962 onto the device via Netgear's web interface. (If it seems to have worked, but you can't log in: reset the device via the red button.)
  3. Complete the process by flashing (per the wiki's subsequent recommendation) non-trailed mini Broadcom K26 build of your choice (38937 seems to be a crowd favorite ca. fall 2019) onto the device, from within DD-WRT. NOTE that I was only able to get this working via telnet:
    cd /tmp ; wget ftp://ftp.dd-wrt.com/betas/2019/02-23-2019-r38937/broadcom_K26/dd-wrt.v24-38937_NEWD-2_K2.6_mini.bin && write dd-wrt.v24-38937_NEWD-2_K2.6_mini.bin linux && nvram erase && nvram commit && reboot

    (attempts to use the web-interface GUI, web-interface CLI, and/or TFTP all bricked every time.)

  4. immediately upon booting: activate "Administration" > "Factory Defaults"; it was my experience that if you do not, it may brick after a minute or two, and you'll have to start over from nmrpflash.

*ETA: Red Hat Linux users may have to execute the following before using nmrpflash:

sudo ln -sv libpcap.so.1 /usr/lib64/libpcap.so.0.8

Leave a Reply

Your email address will not be published. Required fields are marked *

Warning: This site uses Akismet to filter spam. Until or unless I can find a suitable replacement anti-spam solution, this means that (per their indemnification document) all commenters' IP addresses will be sent to Automattic, Inc., who may choose to share such with 3rd parties.
If this is unacceptable to you, I highly recommend using an anonymous proxy or public Wi-Fi connection when commenting.