So I just tried flashing a new WNDR4300. I started with r23503 to flash from stock to ddwrt, and then I flashed to 26653 using the webflash image from ddwrt. Now I can't get it to work. The power LED just blinks green forever. The interfaces appear to eventually come up, but I can't telnet to it. If I ping the device, it returns malformed ICMP packets (according to ping).
I tried to do a 30-30-30 in this state but it didn't seem to help. Any ideas?
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Apr 12, 2015 3:04 Post subject:
what is "malformed icmp packets".? this router takes up to 1 min 10 seconds to boot unlike wndr3700/wndr3800 make sure ur giving it time to. mine is running on 26653 fine since it updated _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
ping complained that the reply packets were not the correct length.
I'm trying it now and I can't even get an IP address anymore. I've seen in the thread this device can take a long time to boot but I've let it sit for 15 minutes with it still blinking.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Apr 12, 2015 5:50 Post subject:
1 min 20 second max to boot, compared to wndr3700/3800 thats about 46 seconds. i tried putting mine back to 23503 then upgrade to 26653 it again did it just fine.
did u try tftp 26653 (the factory.img, u dont tftp the webflash) directly from stock or 23503? if so what was the procedure u used to do it _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
I went from stock to 23503 via the web interface. DD-WRT booted successfully. I then tried to update to 26653 from the DD-WRT web interface using the webflash.
So I've managed to flash back to stock (using these instructions). I flashed 23503 from the stock interface, which once again worked. I tried 26653 again from the DD-WRT web interface and it again failed.
I'm tempted to just stick with 23503 unless there's a compelling reason to upgrade, or if there's a better way to do it than the DD-WRT web interface.
Posted: Mon Apr 13, 2015 22:34 Post subject: WNDR4300 woes!
Hello! Today I bought a WNDR4300 from OfficeMax because my Linksys E1200v2s keep dying on me. Been a long-time fan of DD-WRT and am currently suffering serious woes because I cannot seem to get it to work on this thing.
Following this thread, I first attempted to upgrade using the attached .img file. This resulted in success - or so it seemed. I now have a router with DD-WRT coming up BUT I cannot seem to upgrade to a newer version... and attempts to go back to stock firmware have failed.
According to status tab:
Hardware: Netgear WNDR4300
Build: DD-WRT v24-sp2 (02/24/13) std - build 20783
As far as I can tell, this is the WNDR4300 v1, NOT the TP-Link. (Though I am not sure how I would be able to tell if it was TP-Link.)
Attempting to use TFTP to send either the .img or .bin file fails repeatedly.
Attempting to use the Web GUI to upgrade to newer versions also fails. What happens is the 300s countdown starts but after 5 seconds I am redirected to upgrade.cgi with 'cannot display the page.' Then it appears to have completely ignored my request.
I have attempted to do a 30-30-30 reset to ensure it's not an issue with corrupted settings or so on... no dice.
Don't presently trust whatever -is- installed on here since it's not behaving normally (doesn't upgrade...) and isn't asking for my password... something done goofed.
What do?
I'd like to get this thing running the latest DD-WRT it can, and if not I want it back on stock firmware.
Hunting through the thread for instructions is like putting together a jigsaw puzzle, so sorry if this has been asked before.
The wiki's supported devices gives me one answer, the dd-wrt.com's router database lists a VERSION of 4300 that doesn't seem to even exist...
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Mon Apr 13, 2015 23:02 Post subject:
list the procedure on how ur trying to tftp it what are the steps being done. & if u had a tplink that would be WDR4300 not WNDR4300 theyre very different, under the router does it just say wndr4300 or v1.x or anything like that? _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Posted: Mon Apr 13, 2015 23:12 Post subject: WNDR4300 woes!
It's the WNDR4300. So I have the right thread, woo!
EDIT: Yes. it simply says WNDR4300. No 1.x, no v2, no nothing. just WNDR4300.
EDIT2: CPU model says Atheros AR9344 rev 1.2 (0x2122), 560 mhz. Maybe that will help narrow it down!
And I really just need install instructions.
I thought that the TFTP window is the instant it starts responding to pings (using a static IP to do the pinging...)
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Apr 14, 2015 2:01 Post subject:
so if u need instructions..that means u dont know how to tftp but yet u said u tried it & it failed, so if u tried it u had some idea what u were doing, which is why i asked what is the procedure u used to attempt it so i can point out where was wrong etc _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Posted: Tue Apr 14, 2015 4:45 Post subject: WNDR4300 woes!
I am aware of two methods for getting TFTP recovery.
what I have normally done is simply begin as soon as the router responds to a ping - just send the file and voila.
However, the recovery mode for this router is apparently a little different. The process for netgear is said to be to hold the reset button while turning the router on until the power led begins flashing orange and then green.
I've attempted -both- methods, using stock firmware and the DD-WRT .img and cannot get it to respond.
TFTP2.exe says 'upgrading flash,' reaches about 75% in the blue meter and then moves on to 'erasing flash' which never moves. It keeps retrying.
I am trying everything I possibly can to figure out what is wrong with my DD-WRT install. It appears to not be able to save any settings I try to change...
EDIT: My problem appears to have been the fact that the Netgear recovery mode times out after so long, cutting off the transfer.
I was able to get OpenWRT to load onto it and it appears to be able to use all the usual features (I can SSH into it, for instance!), so at least now I have control of my router again. Would still like to get dd-wrt going though.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Tue Apr 14, 2015 6:52 Post subject:
dont use tftp2.exe or whatever other programs for it, windows has its own tftp client in it, it works fine for netgear & dlinks only some tplinks have a different type of (crappy) tftp method.
do exactly like this, it should work, i just recovered mine yesterday from a newer private test build thats broken (& several times before)
1. download firmware .img file such as r26653, rename it to a shorter name like "ddwrt" so its "ddwrt.img"
2. copy that renamed .img file to DESKTOP
3. make sure the ethernet cable is attached from the router to pc BEFORE DOING THIS STEP, if the router is in tftp mode BEFORE plugging the ethernet it WONT WORK, turn off router & hold down reset button, while still holding down the reset button turn on router, keep holding till power led flashes GREEN
4. give the pc a STATIC ip of 192.168.1.4 & set the gateway to 192.168.1.1, the gateway MUST be set to that ip too
5. open command prompt, type "cd desktop" without quotes
6. type "tftp -i 192.168.1.1 put ddwrt.img" without quotes. if tftp is not a recognized command proceed to step 6a below, otherwise skip step 6a.
6a. go to control panel --> programs --> turn windows features on/off, click the box beside TFTP CLIENT so it is checked, let it install, repeat step 6
7. wait, should say successful, DO NOT power off or reset the router, let it flash & fully reboot. remove the static ip from the pc
8. should be at ddwrt screen now, make a username/password then go to administration --> factory defaults, click yes, then click apply settings. wait for reboot then setup to ur liking _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers