Posted: Tue Jul 14, 2009 3:41 Post subject: Flashing Netgear WNDR3300 via Telnet from Original Firmware?
My router will not flash anything I throw at it. The router always says firmware upgrade failed after a few seconds. I tried he same firmware (1.0.26), a newer official firmware 1.0.29, and 1.0.30 beta. I also tried several recent Eko builds, including 12307. The official firmwares were the NA versions, since I live in the USA. I flashed a semi-working version of DD-WRT without reading what is recommended in the WNDR3300 thread here first, then flashed back to the default firmware. After that, I have not been able to flash the router.
I got Telnet enabled in the original Netgear firmware thanks to this site: http://www.beatjunkie.de/Router_eng.htm and am hoping I can flash the router via telnet. I see that there are instructions for doing so if DD-WRT is already on the router here http://www.dd-wrt.com/wiki/index.php/Installation#Flashing_with_Command_Line but I did not see a file or folder named "linux" anywhere in the filesystem, after using "ls" on all the folders I did see. Can I flash this way, and if so, can I do the same thing as listed there but using a recent eko build? I don't want to brick a router that costs this much.
Why don't you just flash with tftp? Use the file recommended in the wiki...you can change to a different version later. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Why don't you just flash with tftp? Use the file recommended in the wiki...you can change to a different version later.
I first tried to flash in late April or early May, and I don't remember which ones I tried, but they were probably the most recent versions at the time. I tried again yesterday with what I mentioned previously.
I tried tftp about 15 times including several just now. This is what I did:
tftp 192.168.1.1
binary
rexmt 1
timeout 60
trace
(plug in router)
put dd-wrt.v24-12030_NEWD_mini_wndr3300.chk (already typed before plugging in router, so just press enter)
The output is this (I changed the firmware's filename to make typing it easier):
sent WRQ <file=dd-wrt.v24.chk, mode=octet>
sent WRQ <file=dd-wrt.v24.chk, mode=octet>
sent WRQ <file=dd-wrt.v24.chk, mode=octet>
sent WRQ <file=dd-wrt.v24.chk, mode=octet>
sent WRQ <file=dd-wrt.v24.chk, mode=octet>
sent WRQ <file=dd-wrt.v24.chk, mode=octet>
tftp: sendto: No route to host
I tried at several points after plugging the router in, and get either the same thing with fewer sent WRQ... lines, a "Transfer Timed Out" or "sendto: Host is down" after a sent WRQ... if I press enter earlier.
My ethernet settings are as follows:
IP: 192.168.1.99
Subnet mask: 255.255.255.0
Router: 192.168.1.1
Half-Duplex
10BaseT/UTP
MTU: 1500
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Tue Jul 14, 2009 17:40 Post subject:
EDIT] I just saw you are using OSX....sorry...I missed that earlier.
What I have found is that Vista is nothing but problematic for flashing using tftp...if you have an XP rig somewhere available..I suggest you use it to flash using the tftp utility....or get the Ubuntu linux CD and boot your computer up off the CD into linux and flash it using linux.
If you hard reset the router and use the Netgear web gui...I can't see why it won't let you upgrade the firmware from the gui....just select the 3300.chk file and it should flash directly...no tftp, telnet...or otherwise to deal with.
One more thing that you should do...once you do have telnet working...issue
"erase nvram" as a command...then power cycle the router...then try the tftp utility (not command line)...see if it will flash using that method.
[EDIT] - I am sure OSX is what is messing you up....I suggest you borrow an XP machine from a friend to do the initial flash.
redhawk _________________ The only stupid question....is the unasked one.
EDIT] I just saw you are using OSX....sorry...I missed that earlier.
What I have found is that Vista is nothing but problematic for flashing using tftp...if you have an XP rig somewhere available..I suggest you use it to flash using the tftp utility....or get the Ubuntu linux CD and boot your computer up off the CD into linux and flash it using linux.
If you hard reset the router and use the Netgear web gui...I can't see why it won't let you upgrade the firmware from the gui....just select the 3300.chk file and it should flash directly...no tftp, telnet...or otherwise to deal with.
One more thing that you should do...once you do have telnet working...issue
"erase nvram" as a command...then power cycle the router...then try the tftp utility (not command line)...see if it will flash using that method.
[EDIT] - I am sure OSX is what is messing you up....I suggest you borrow an XP machine from a friend to do the initial flash.
redhawk
I tried the DrayTek utility a few times on a Windows XP machine to no avail. The program appeared to just crash out after changing to say that it was sending and showing an empty progress bar. I set static IP, half duplex 10mbps, subnet, and gateway before trying. I'm downloading an Ubuntu LiveCD to try flashing from Linux, but I believe I tried that when I first had this issue so I don't think it will help.
Joined: 24 Feb 2009 Posts: 2026 Location: Sol System > Earth > USA > Arkansas
Posted: Tue Jul 14, 2009 22:19 Post subject:
unimania wrote:
I tried both tftp.exe and tftp2.exe a few times, neither worked. Is there a way to force the router into recovery mode?
When using tftp, have you set up an "infinite" ping in another window to compare your start time with? Your 'window' for tftp should start the second you see a ping response with ttl=100. If you do not catch it within 5 to 10 pings, you need to power cycle the router to start over. Timing is critical to get the tftp process to work right. _________________ E3000 22200M KongVPN K26
WRT600n v1.1 refirb mega 18767 BS K24 NEWD2 [not used]
WRT54G v2 16214 BS K24 [access point]
Try Dropbox for syncing files - get 2.5gb online for free by signing up.
Read! Peacock thread
*PLEASE* upgrade PAST v24SP1 or no support.
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Tue Jul 14, 2009 22:29 Post subject:
Many (read as most) of the Netgear units will not automatically go in to tftp mode unless there is corrupt kernel or nvram.
That is why using a serial cable is the best way to troubleshoot these kinds of problems...from serial terminal you can break into the CFE and force tftpd daemon to start.
With Serial hooked up...plug the router in...As soon as you give it power start with a rapid fire of CNTL-C to break into the CFE. (you have about 250mS to hit this)
Once at the CFE> prompt...you then type "tftpd" and it will start "Reading::..."
Its at this point you can then start the tftp utility to flash FW to the unit.
redhawk _________________ The only stupid question....is the unasked one.
Many (read as most) of the Netgear units will not automatically go in to tftp mode unless there is corrupt kernel or nvram.
That is why using a serial cable is the best way to troubleshoot these kinds of problems...from serial terminal you can break into the CFE and force tftpd daemon to start.
With Serial hooked up...plug the router in...As soon as you give it power start with a rapid fire of CNTL-C to break into the CFE. (you have about 250mS to hit this)
Once at the CFE> prompt...you then type "tftpd" and it will start "Reading::..."
Its at this point you can then start the tftp utility to flash FW to the unit.
redhawk
I don't have any of the equipment to attach a serial cable to my router (a serial cable, a serial->usb adapter, torx screwdriver...) so I decided to take a chance and maybe brick my router. If it didn't work, well, then I would get a serial connection set up and I would be fine anyway.
I enabled telnet again as it must be for every boot. Once connected, I ran "erase linux" and "reboot" and got the flashing green power LED indicating the bootloader! So I tftp'ed eko's 12030 for the wndr3300 and after several minutes it rebooted into DD-WRT. I connected over wireless and the router appears to be working, though it is not connected to the internet yet.
The router was working fine up to this point, I just wanted the extra features and familar interface of DD-WRT on this router.
Edit: I don't remember why I used 12030, but I flashed 12476 on it just now using the web interface. It is broadcasting on 2.4Ghz and 5Ghz now.
Joined: 04 Jan 2007 Posts: 11564 Location: Wherever the wind blows- North America
Posted: Sun Jul 19, 2009 17:23 Post subject:
unimania wrote:
I enabled telnet again as it must be for every boot. Once connected, I ran "erase linux" and "reboot" and got the flashing green power LED indicating the bootloader! So I tftp'ed eko's 12030 for the wndr3300 and after several minutes it rebooted into DD-WRT. I connected over wireless and the router appears to be working, though it is not connected to the internet yet.
I'll be honest...I never even thought of trying it by this method....I like this...very simple...and apparently very effective to clear the kernel.
thanx for sharing what worked for you.
redhawk _________________ The only stupid question....is the unasked one.
Clever.....I bet THAT makes Red's notes. Added to the wiki? _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Alright peeps, I ran into the same problem as unimania. I have the netgear original firmware 1.0.30NA and it wouldn't let me upgrade the firmware no matter what I did.
I would always get the error firmware upgrade failed.
I had to use telnetenable 192.168.1.1 (mac address, no colons) Gearguy Geardog
It took a few tries and reboots to get this to work but it finally did. (the username Gearguy is case sensitive and so is the password) I was able to log onto the router using telnet 192.168.1.1
the screen that comes up says something on the lines of busybox then a prompt #
then the easiest way to fix the firmware problem is to type
erase linux
YOU MUST WAIT UNTIL THE # (PROMPT) COMES BACK AFTER THE ERASE LINUX COMMAND THEN UNPLUG AND PLUG BACK IN.
The power light then starts to flash as it is waiting for tftp and the firmware file. (You must use the dd-wrt.chk file, you cannot use the bin file)
send in your new firmware file via tftp and then wait until the power light stops flashing (it will flash slowly then reset)
after it initally resets go ahead and unplug and plug back in.
hope that helps, it did for me.
a strange anomaly my mac addresses were blanked out (00:FF:FF:FF:FF:FF) and I had to manually repair them.
