2. Revert to default config of dd-wrt
set the password on http interface
3. Set static IP (192.168.1.10 mask 255.255.255.0 gw 192.168.1.1) on wired PC
4. Open 3 different command prompt with:
First for ping response check (not real necessary)
with a "ping 192.168.1.1 -t"
Second for telnet session
log in root and make an "erase linux" or "mtd erase linux" ( i made both for sure )
you should see a message similar to:
Unlocking linux ...
Erasing linux ...
Waiting prompt return
Put the chk file on path of the cmd (default c:\users\user)
Prepare the tftp on third command prompt with :
"tftp -i PUT WNDR4000-V126.96.36.199_8.0.71.chk"
send a "reboot" on the telnet session and wait the first ping response for send the tftp command.
Wait 5-10 min & the router is ok
(Made a reset on the wndr4000 for restore the default netgear password "admin/password")
This worked great for me too, Thank You!!
FYI for others, I found it slightly easier to use the tftp utility recommended on another DD_WRT page I read 1st.
I turned off the router loaded up the tftp utility with the .chk file (no password)I turned on the router and hit the upgrade button, and it worked great. I also had to reset the router after flashing, before I was able to access the router web page.
you have to go back to stock following this ^^ _________________ wrt160n v1 BS k2.4
wrt610n v1 BS k2.6
Posted: Mon Apr 09, 2012 17:17 Post subject: Use 18777 big version on WNDR4000 for NTFS
I have determined after trying out the different mega builds from 18024 through 18777 that the ntfs usb drive won't mount. I then flashed the firmware with the 18777 big version and I can again mount the ntfs formatted usb drive and access it from the network.
Core USB Support
USB Printer Support
USB Storage Support
Automatic Drive Mount
Run-on-mount Script Name
Disk Mount Point
Block device, size 1.819 TiB (2000398934016 bytes)
DOS/MBR partition map
Partition 1: 1.819 TiB (2000396289024 bytes, 3907024002 sectors from 63)
Type 0x07 (HPFS/NTFS)
Windows NTLDR boot loader
NTFS file system
Volume size 1.819 TiB (2000396288512 bytes, 3907024001 sectors)
Status: Not mounted
Status: Mounted on /mnt
Because of my upgrade issue from 18024, I had to flash to stock using TFTP then to 18777. Later on I tried to flash from 18777 to another build (18946 by Eko) and AGAIN the upgrade doesn't go through. Same thing: upgrade 360sec timer goes away after a couple of seconds, router reboots and nothing changes.
Is this a 18xxx DD-wrt problem or a router problem? It will be a real hassle to upgrade in the future if this problem doesn't get fixed.
All I have successfully loaded 18777 on my new WNDR4000. I followed the procedure posted by Clevar. I was able to go from stock to mini to big 18777 without any major issues. I have loaded versions for ~5 other device models in the past however I always like to see what worked for others and if it looks like good documentation I will give it a shot.
FYI - For those looking for the applicable release read on...The database entry for this router does not list specific release. Not sure why, but I am sure the admins have their reasons. If you attempt to look-up this router in the database the file link provided just dumps you to the top level for the 2011 BrainSlayer releases and that can be confusing, especially if you aren't on this site very much.
Under each of the release folders are folders for each platform specific release. For the WNDR4000 you are looking for broadcom_K26. It is here you will find the files you need. In short you will need the .chk file for the WNDR4000 and then an nv64k.bin that includes the feature set you want to run. Please see Clevar's doc for specifics.
The only issue I have noted with this device and version is I did notice some odd behavior with the web management authentication. If you restart the router and keep your current browser open if does not prompt for new creds but any attempts to make changes fail. If this behavior existed before I never noticed it.
I've set this up successfully on my other dd-wrt router (linksys e3000 build 14853).
I've noticed two issues: 1. WEP 64bit/10hex doesn't seem to work when setting up Wlan. I realize that WEP is the weakest choice of encryption, but I'm using for an isolated guest network and so my son's Nintendo DS can connect (only uses WEP). When I switch to WPA or WPA2 it works fine. This is not a deal breaker.
2. Once I try to bridge the connection I can no longer connect to it. The connection just times out
To elaborate a bit. The router assigns an ip address to my cellphone (test device), and it's the newly created subnet: 192.168.2.1 and it shows that the device is connected on the new virtual wireless lan I just created, but for some reason I can't seem to get the internet.
Update: I went ahead and flashed to 17990 and it appears both problems are there too: WEP Encryption not working (at least for wlans) and when bridging the virtual lan I loose internet.
Please EKO or anyone can you please comment on this? Is this something you are working to fix or is anyone else experiencing this issue?