Nevermind, I already bricked it but Im pretty sure it can be debricked since it gives me 1-3 ttl=100 responses, but after that the network adapter says "no device connected" and it's lost. I also made a topic but got no responses yet.
Quote:
Hi,
seems like I bricked my netgear wndr3400v2 router. I tried multiple firmwares like dd-wrt/tomato etc. dd-wrt was the best, but my main goal was to have working qos and port forwarding/DMZ. With the build that was around those 2 features didnt work. So some time ago I flashed another version that bricked it. (I unbricked it once though).
The problem this time is, that I can get only 1-2 (occassionally 3) ping responses ttl=100 before timeouts happen and the ethernet adapter loses connection and says "no device connected". Last time I tftp'd it to unbrick it I had steady pings.
Whether I use windows tftp client or putty/tftp2 nothing works. My timing is with high certainty not the fault, tried it like 70 times. Problem seems to be the ethernet adapter that "gives up" too early and says there's no device connected.
Any advice? Any hope? JTAG and serial cable methods are not an option. Can I somehow tweak the ethernet adapter settings in windows so that it holds the connection longer (1-3 pings more would be sufficient I guess)?
If there's absolutely no hope without JTAG and stuff though, let me know. Im just a gamer starving for QoS (cause my main router does not have it customizable) and if I have to I'll buy a cheap dd-wrt-compatible router.
Thank you very much for your help in advance! I read some things in here and the community seems to be awesome!
So if anyone had the same issue and solved it, would be cool if you let me know!
Joined: 04 Sep 2007 Posts: 13 Location: New Jersey USA
Posted: Thu Mar 23, 2017 7:40 Post subject:
I just found a version 1 sitting on a shelf in my basement that I forgot about. I shelved it after it kept dropping connections 2-3 times a day and had to be reset.
Let the flashing begin.
I picked up a wndr3400v2. I updated to the newest stock firmware and then flashed the 2014 Hearbleed fix build linked to in this thread. So far client bridge mode is working well. I am wondering if there will ever be newer builds for this router?
Posted: Sun Aug 13, 2017 16:25 Post subject: Procedure to flash the WNDR3400v2
numanair wrote:
I picked up a wndr3400v2. I updated to the newest stock firmware and then flashed the 2014 Hearbleed fix build linked to in this thread. So far client bridge mode is working well. I am wondering if there will ever be newer builds for this router?
What's the procedure to flash this WNDR3400v2 file?
I did not see any instructions on the DL page... _________________ (WRT54G V6.00 "neutered" with
DD-WRT v24-sp2 (12/24/10) micro - build 15962)
(WRT54GS V2 DD-WRT v24-sp2 (12/18/09) mega - build 13491M VINT Eko Bridge/Repeater)
(WNDR3400v2 dd-wrt.v24-K26_WNDR3400V2_17-Apr-2014)
(dd-wrt.v24-41586_NEWD-2_K3.x_mega-WNDR4500V1 AND dd-wrt.v24-41892_NEWD-2_K3.x_mega-WNDR4500V2)
Posted: Tue Sep 18, 2018 21:24 Post subject: Bricking and Unbricking a WNDR3400v2 using MyOpenRouter FW
This old thread regarding a DD-WRT on a WNDR3400v2 seems the best place to share my last couple of sleepless nights trying to recover my router, not because I need it, because I don't give up easily.
Bricking my WNDR3400v2
----------------------
Using dd-wrt.v24-K26_WNDR3400V2_17-Apr-2014.chk from Brandon C @ MyOpenRouter, I had enabled JFFS2 support to take OpenVPN Certs and Keys off NVRAM (not because I need it, but to unify the setup with my old Linksys WRT610N where it is needed). It looks weird because when I enabled says like 640Kb, all free, after a couple of reboots says 384Kb mostly occupied (without moving the Certs/Keys yet) so there was something suspicious about it.
So a couple of days of settings and reboots, after taken VPN Certs and Keys to the JFFS2 mounted device, during some OpenVPN variables modification (OpenVPN was already working), didn't reboot anymore.
Yes, not a firmware update, just during settings update...
After trying a full reset and a 30-30-30 reset and the green status led still blinking, realized that was worse than I imagine before.
My diagnosis is that something between the process to copy Certs and Keys and the Resets, a process overwrite part of the flash messing with the Linux Kernel, Board_Data and NVRAM partitions.
Unbricking a dead WNDR3400v2
----------------------------
Didn't give up just because after correctly setting my PC to 192.168.1.2/24 I could ping with TTL=100 the freaking router!
Code:
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=100
Reply from 192.168.1.1: bytes=32 time<1ms TTL=100
Reply from 192.168.1.1: bytes=32 time<1ms TTL=100
Reply from 192.168.1.1: bytes=32 time<1ms TTL=100
First open the router box and manage to connect a Putty Terminal to the Serial Port (J41) using some kind of USB to TTL like a FDTI 232RL device (would have save me a night if I knew that the connection must be at 115200/8/None/1/None).
I realized here that the problem was with some of the NVRAM variables or Board_Data partitions because the serial terminal booted with a checksum error on the CFE boot up.
Code:
CFE for WNDR3400v2 version: v1.0.15
Build Date: Tue Jul 5 21:54:28 CST 2011
Init Arena
Init Devs.
Boot partition size = 262144 (0x40000)
Found a 8MB ST compatible serial flash
Et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.60.127.17
CPU type 0x19749: 530MHz
Tot mem: 65536 KBytes
Device eth0: hwaddr 00-FF-FF-FF-FF-FF, ipaddr 192.168.1.1, mask 255.255.255.0
Gateway not set, nameserver not set
Checksum length overflow!
Loader:raw Filesys:raw Dev:flash0.os File: Options:(null)
Loading: . 0 bytes read
Failed.
Could not load flash0.os:: Error
Device eth0 has been deactivated.
Device eth0: hwaddr 00-FF-FF-FF-FF-FF, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Start TFTP server
Reading ::
So, summarizing to get CFE> prompt, hit Ctrl-C every 1/10 of a second (just jocking, too lazy to count) during booting until prompt appear.
Then in CFE set this NVRAM variable
Code:
CFE> nvram set bypass_board_id=1
*** command status = 0
Then started TFTP server using
Code:
CFE> tftpd
Start TFTP server
Reading ::
Sent the most updated Stock Firmware using some TFTP client from Windows (i.e. tftp2.exe) thru Ethernet Port (to Server=192.168.1.1, Pwd=password, and File=WNDR3400v2-V1.0.0.54_1.0.82.chk)
Pressed Enter as required, and after 5 to 10 minutes:
CFE for WNDR3400v2 version: v1.0.15
Build Date: Mon Sep 5 13:35:48 CST 2011
Init Arena
Init Devs.
Boot partition size = 262144(0x40000)
Found a 8MB ST compatible serial flash
et0: Broadcom BCM47XX 10/100/1000 Mbps Ethernet Controller 5.60.127.17
CPU type 0x19749: 530MHz
Tot mem: 65536 KBytes
Device eth0: hwaddr 00-FF-FF-FF-FF-FF, ipaddr 192.168.1.1, mask 255.255.255.0
gateway not set, nameserver not set
Linux version 2.6.22 (builder@production) (gcc version 4.2.3) #1 Wed Jan 11 14:32:27 CST 2017
CPU revision is: 00019749
Found a 8MB ST compatible serial flash
wombo_reset set to gpio 25
Determined physical RAM map:
memory: 03fff000 @ 00000000 (usable)
Built 1 zonelists. Total pages: 16256
Kernel command line: root=/dev/mtdblock2 console=ttyS0,115200 init=/sbin/preinit
...
...
mount: mounting none on /proc/bus/usb failed: Device or resource busy
IOCTL_AG_REGION_SET: English
Start DHCP client daemon
info, udhcp client (v0.9.8) started
vlan2: No such process
route: ioctl 0x890c failed: No such process
killall: dhcp6c: no process killed
killall: IPv6-relay: no process killed
killall: pppdv6: no process killed
killall: rtsol: no process killed
killall: dhcp6s: no process killed
killall: radvd: no process killed
ifconfig: invalid number ''
ifconfig: invalid number ''
route: ioctl 0x890c failed: No such process
killall: dhcp6s: no process killed
killall: radvd: no process killed
Chanspec set to 0x1d2e
Hit enter to continue...killall: wps_ap: no process killed
killall: syslogd: no process killed
Invalid instance identifier br0
info, Entering released state
device vlan2 is not a slave of br0
info, Received SIGTERM
Hit enter to continue...Hit enter to continue...
BusyBox v1.7.2 (2017-01-11 14:33:05 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
#
# handle_genie: don't know how to process url
localize lang non-us first-brs English
localize lang non-us first-brs English
Doing nvram commit by pid 2147 !
wan_lan_reset_sig:137
Doing nvram commit by pid 2147 !
#
And my WNDR3400v2 was fully back!... Ready to flash my new DD-WRT, OpenWRT or Tomato flavor and start all over again.
And yes, probably this won't be happening to some of the new DD-WRT v3.0-releases, but for these old boys the only one who took the time to compile the firmware was Brandon C more than four years ago...
but Im pretty sure it can be debricked since it gives me 1-3 ttl=100 responses, but after that the network adapter says "no device connected" and it's lost. I also made a topic but got no responses yet.
