Posted: Fri Oct 31, 2014 12:46 Post subject: Netgear-wndr3700v4 firmware upload fail
Hi,
I'm trying to upload the dd-wrt firmware to my Netgear WNDR3700v4.
The router is at the original Netgear 1.0.1.52.
When i try to upload via the routers web front-end it sits there with the star spinning but waits for ages and then fails with the message "The CGI script took too long to produce a response".
Is there anything else i can try as i would love to get the firmware on the box as some of the functions i really need.
Try first to downgrade the router to the first firmware netgear released, in case they put some checks in later fw. _________________ I am far from a guru, I'm barely a novice.
Posted: Sun Nov 02, 2014 2:14 Post subject: Same issue
I am having the same issue. I have tried rolling back the netgear firmware to release, 1.0.1.32, and still no luck. No luck with TFTP either. I will mention that I am in north america and using the world wide firmware since there is not a NA version for the V4. Could that be the issue, and if so am I just out of luck with regards to using this firmware?
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Nov 02, 2014 7:05 Post subject: Re: Nope :-(
bob_bobski wrote:
Well i tried the TFTP method, both on my Windows 8 machine and Terminal on my MacBook.
Still no joy
I might just have to give up
explain how u did the tftp please
if u havent done it like this, try it again, exactly as so.
1. download firmware .img file, rename it to a shorter name like "ddwrt" so its "ddwrt.img"
2. copy that renamed .img file to DESKTOP
3. 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. connect a windows pc (i dont know about mac or linux & how it differs with tftp) via ethernet to any of the LAN ports, NOT the wan port
5. 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
6. open command prompt, type "cd desktop" without quotes
7. type "tftp -i 192.168.1.1 put ddwrt.img" without quotes. if tftp is not a recognized command proceed to step 7a below, otherwise skip.
7a. 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 7
8. wait, should say successful, DO NOT power off or reset the router, let it flash & fully reboot. remove the static ip
9. 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
Posted: Sun Nov 02, 2014 10:11 Post subject: Wow... So close
Thanks for the very detailed TFTP description there tatsuya46...
It's in and working... Sort of... As you can see from the first attachment, following your description it went in, i waited 20 minutes for it to finish the front LED flashing but it seamed to be looping so i turned it off, waited 10 seconds and then on again. This time it came up correctly and i was able to connect.
Unfortunately it won't connect to my broadband provider. This is BT Infinity (fibre to the cabinet). Looking at the screenshots i took of my previous router setup it uses PPPoE. I've tried this and some of the other WAN connection types but still no joy.
Any further assistance would again be greatly appreciated.
Joined: 03 Jan 2010 Posts: 7568 Location: YWG, Canada
Posted: Sun Nov 02, 2014 21:11 Post subject:
if u use pppoe ull know about it cause ull have a username & password. enable the advanced settings for pppoe & toggle them, there isnt very many, see if mppe is needed or not etc. reboot the isp modem too to be sure its seeing the mac address its expecting _________________ LATEST FIRMWARE(S)
BrainSlayer wrote:
we just do it since we do not like any restrictions enforced by stupid cocaine snorting managers
Posted: Mon Nov 10, 2014 8:27 Post subject: SOLVED: "The CGI script took too long to produce a resp
bob_bobski,
Bob,
I had the same error message ("The CGI script took too long to produce a response") when attempting the process of flashing dd-wrt onto a new WNDR4300 (which has the same Atheros AR9344@560 chip as the WNDR3700v4).
Here is what I discovered, in short:
>Apparently there was a 'mis-match' between the 'stock' Netgear firmware (v1.0.0.42) and the latest wndr4300-factory.img (from Build 25279, 11/07/14); thus causing the error.
What I did to resolve:
>Downloaded from Netgear, the latest 'stock' firmware (v1.0.0.60).
>Flashed the WNDR4300 with v1.0.0.60.
Once complete,
>Flashed the WNDR4300 with wndr4300-factory.img (from Build 25279, 11/07/14).
SOLVED
All done via browser (IE-11) GUI; no TFTP required.
{Note: the 'factory.img' is required when flashing dd-wrt onto a 'stock' WNDR4300.}
I had the same issue with my WNDR3700v4 as the OP. I found following the instructions provided by tatsuya46 worked for me. Looking at the difference between the image size for the v4 router and the v2 router, the v4 is much larger and apparently is too much for the stock firmware to load? My router came with 1.0.1.32 and I upgraded to 1.0.1.52 to see if it helped - it didn't. The TFTP trick was the only way it worked.
I also had the same result as the OP when the router came back up - it was in a restart loop. After I watched it for about 10 times, I realized it was looping (and re-checked this post to see that it happened to the OP) and powered it off and back on and then it came up okay.
Then I did the 30/30/30 reset described in the Wiki. I had a bear of a time keeping the reset button pushed in for the 90 seconds while simultaneously turning the power off, on, and then off again. The paperclip kept slipping off the hidden inside of the reset button. But apparently I got it close enough because after that, I was able to make changes in the setup.
