Tp-Link wr-940n v3 bricked

Report problems and success stories with Gargoyle on various hardware platforms.

Moderator: Moderators

jiade8
Posts: 18
Joined: Fri Oct 18, 2013 1:24 pm

Tp-Link wr-940n v3 bricked

Post by jiade8 »

My router is WR940N v3.

I found that: "The TP-Link WR940N is identical to the TL-WR941ND except that the antennas are not detachable and the hardware version is different.

WR940N v1 is a WR941ND v4
WR940N v2 is a WR941ND v5
WR940N v3 is a WR941ND v6"

So, I upgraded Tp-Link wr 940n v3 by using:
gargoyle_1.7.2-wr941nd-v6-squashfs-factory
gargoyle_1.8.0-wr941nd-v6-squashfs-factory
gargoyle_1.8.1-wr941nd-v6-squashfs-factory
gargoyle_1.9.0-wr941nd-v6-squashfs-factory

However, my router was bricked with trying all above Gargoyle Firmware.

Anyone please, I need help!
Thank you!

Lantis
Moderator
Posts: 6753
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Tp-Link wr-940n v3 bricked

Post by Lantis »

Do you own the Chinese version of the router?
If not, it is incompatible.

You'll be able to recover it by flashing the oem firmware using TFTP
See this thread:
https://forum.openwrt.org/viewtopic.php?pid=293475
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

jiade8
Posts: 18
Joined: Fri Oct 18, 2013 1:24 pm

Re: Tp-Link wr-940n v3 bricked

Post by jiade8 »

I see, international version of my router is incompatible.
Thanks Lantis.

jiade8
Posts: 18
Joined: Fri Oct 18, 2013 1:24 pm

Re: Tp-Link wr-940n v3 bricked

Post by jiade8 »

How can I know if a Tp-Link 940n v3 router is Chinese version or International version?

Lantis
Moderator
Posts: 6753
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Tp-Link wr-940n v3 bricked

Post by Lantis »

Does it have an FCC ID written on it or the box somewhere?
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

jiade8
Posts: 18
Joined: Fri Oct 18, 2013 1:24 pm

Re: Tp-Link wr-940n v3 bricked

Post by jiade8 »

Yes, it does. 940N v3 has FCC ID, ís TE7WR941NXV6.

Lantis
Moderator
Posts: 6753
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Tp-Link wr-940n v3 bricked

Post by Lantis »

Yep that's the regular version.

There's a patch that was supposed to go into Chaos Calmer that didn't make it which added support for your device.
You may be stuck until Designated Driver version Unfortunately :(

Once you get it unbricked, shoot me a message on http://www.gargoyle-router.com/phpbb/vi ... =13&t=7861 and i'll see what i can do for you.
Remind me that your router is a bit special :P
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

neal105
Posts: 1
Joined: Tue Apr 26, 2016 5:21 pm

Re: Tp-Link wr-940n v3 bricked

Post by neal105 »

Lantis I have the same problem...I guess i bricked my wr940N v3 which i bought just yesterday .i flashed it by 1.8.1 factory.bin using 941N file as it said it was the same.. 192.168.1.1 or tplink aint working.. i have been using your firmware on wr740N for years...i dont know how to unbrick by codes or using serial port opening up my devicces back... is there a easier way ..or should i return it for warranty and they wont understand..writing from Bangladesh...

please help if you have time brother

Lantis
Moderator
Posts: 6753
Joined: Mon Jan 05, 2015 5:33 am
Location: Australia

Re: Tp-Link wr-940n v3 bricked

Post by Lantis »

I'd say the easiest thing to do would be try to warranty the device where you bought.

You could try using the tftp recovery
Follow the instructions under tftp install on this page.
https://wiki.openwrt.org/toh/tp-link/tl-wr941nd
The image you'll want to try to put on there is the factory image. The recovery image name may be different to the instructions
http://lantisproject.com/downloads/gargoyle_ispyisail.php for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.

MrBrown
Posts: 6
Joined: Sun Apr 03, 2016 9:50 am

Re: Tp-Link wr-940n v3 bricked

Post by MrBrown »

Hello Lantis.

I did recently also brick the WR940N v3 international, after flashing the "gargoyle_1.9.1-ar71xx-generic-tl-wr941nd-v6-squashfs-factory.bin".

But- that is not a problem, since I was able to restore the original TP-Link firmware using tftpd.

In fact, I was able to flash OpenWRT, by using the factory firmware provided in this post:

https://forum.openwrt.org/viewtopic.php ... 36#p320836

So now I have the OpenWRT running on the WR940N v3 international.

Here are a couple of informations from the System Status:
Model: TP-Link TL-WR941N/ND v6
Firmware Version: OpenWrt Designated Driver r49207 / LuCI Master (git-16.108.33174-51a7f96)
Kernel Version: 4.1.20
And here is the Kernel log:

Code: Select all

[    0.000000] Linux version 4.1.20 (openwrt@5ba22af2a580) (gcc version 5.3.0 (OpenWrt GCC 5.3.0 r49207) ) #1 Thu Apr 21 04:54:36 UTC 2016
[    0.000000] MyLoader: sysp=51999c9e, boardp=63da6998, parts=69874f2f
[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU0 revision is: 00019750 (MIPS 74Kc)
[    0.000000] SoC: Qualcomm Atheros TP9343 rev 0
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 00000000 (usable)
[    0.000000] Initrd not found or empty - disabling initrd
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000000000000-0x0000000001ffffff]
[    0.000000] On node 0 totalpages: 8192
[    0.000000] free_area_init_node: node 0, pgdat 803f2020, node_mem_map 81000000
[    0.000000]   Normal zone: 64 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 8192 pages, LIFO batch:0
[    0.000000] Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
[    0.000000] pcpu-alloc: [0] 0 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line:  board=TL-WR941ND-v6  console=ttyS0,115200 rootfstype=squashfs,jffs2 noinitrd
[    0.000000] PID hash table entries: 128 (order: -3, 512 bytes)
[    0.000000] Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
[    0.000000] Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 27804K/32768K available (2915K kernel code, 144K rwdata, 708K rodata, 256K init, 200K bss, 4964K reserved, 0K cma-reserved)
[    0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[    0.000000] NR_IRQS:83
[    0.000000] Clocks: CPU:750.000MHz, DDR:400.000MHz, AHB:250.000MHz, Ref:25.000MHz
[    0.000000] clocksource MIPS: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 5096694524 ns
[    0.000007] sched_clock: 32 bits at 375MHz, resolution 2ns, wraps every 5726622718ns
[    0.008219] Calibrating delay loop... 373.55 BogoMIPS (lpj=1867776)
[    0.071096] pid_max: default: 32768 minimum: 301
[    0.076074] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.083050] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[    0.093282] clocksource jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[    0.104744] NET: Registered protocol family 16
[    0.110761] MIPS: machine is TP-LINK TL-WR941N/ND v6
[    0.568489] Switched to clocksource MIPS
[    0.573846] NET: Registered protocol family 2
[    0.579413] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[    0.586768] TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
[    0.593536] TCP: Hash tables configured (established 1024 bind 1024)
[    0.600350] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.606519] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.613484] NET: Registered protocol family 1
[    0.618148] PCI: CLS 0 bytes, default 32
[    0.619155] futex hash table entries: 256 (order: -1, 3072 bytes)
[    0.642374] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    0.648586] jffs2: version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    0.661203] io scheduler noop registered
[    0.665342] io scheduler deadline registered (default)
[    0.671074] Serial: 8250/16550 driver, 16 ports, IRQ sharing enabled
[    0.680346] console [ttyS0] disabled
[    0.704217] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11, base_baud = 1562500) is a 16550A
[    0.713324] console [ttyS0] enabled
[    0.720880] bootconsole [early0] disabled
[    0.734421] m25p80 spi0.0: found gd25q32, expected m25p80
[    0.740076] m25p80 spi0.0: gd25q32 (4096 Kbytes)
[    0.745958] 5 tp-link partitions found on MTD device spi0.0
[    0.751767] Creating 5 MTD partitions on "spi0.0":
[    0.756717] 0x000000000000-0x000000020000 : "u-boot"
[    0.762680] 0x000000020000-0x00000015c684 : "kernel"
[    0.768567] 0x00000015c684-0x0000003f0000 : "rootfs"
[    0.774397] mtd: device 2 (rootfs) set to be root filesystem
[    0.780345] 1 squashfs-split partitions found on MTD device rootfs
[    0.786736] 0x000000370000-0x0000003f0000 : "rootfs_data"
[    0.793068] 0x0000003f0000-0x000000400000 : "art"
[    0.798728] 0x000000020000-0x0000003f0000 : "firmware"
[    0.822719] libphy: ag71xx_mdio: probed
[    1.410554] ag71xx ag71xx.0: connected to PHY at ag71xx-mdio.1:04 [uid=004dd042, driver=Generic PHY]
[    1.420649] eth0: Atheros AG71xx at 0xb9000000, irq 4, mode:MII
[    2.010351] ag71xx-mdio.1: Found an AR934X built-in switch
[    2.052575] eth1: Atheros AG71xx at 0xba000000, irq 5, mode:GMII
[    2.061198] NET: Registered protocol family 10
[    2.070152] NET: Registered protocol family 17
[    2.074831] bridge: automatic filtering via arp/ip/ip6tables has been deprecated. Update your scripts to load br_netfilter if you need this.
[    2.087947] Bridge firewalling registered
[    2.092250] 8021q: 802.1Q VLAN Support v1.8
[    2.103628] VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
[    2.112853] Freeing unused kernel memory: 256K (80410000 - 80450000)
[    3.013165] init: Console is alive
[    3.016906] init: - watchdog -
[    3.828171] init: - preinit -
[    4.393653] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[    4.419434] random: procd urandom read with 7 bits of entropy available
[    6.490300] eth1: link up (1000Mbps/Full duplex)
[    6.495105] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[    7.614739] mount_root: jffs2 not ready yet, using temporary tmpfs overlay
[    7.646423] eth1: link down
[    7.660494] procd: - early -
[    7.663580] procd: - watchdog -
[    8.338186] procd: - ubus -
[    8.448479] procd: - init -
[    9.207861] ip6_tables: (C) 2000-2006 Netfilter Core Team
[    9.226284] Loading modules backported from Linux version v4.4-rc5-1913-gc8fdf68
[    9.233991] Backport generated by backports.git backports-20151218-0-g2f58d9d
[    9.244657] ip_tables: (C) 2000-2006 Netfilter Core Team
[    9.260129] nf_conntrack version 0.5.0 (438 buckets, 1752 max)
[    9.302020] xt_time: kernel timezone is -0000
[    9.365538] PPP generic driver version 2.4.2
[    9.372547] NET: Registered protocol family 24
[    9.424903] ath: EEPROM regdomain: 0x0
[    9.424923] ath: EEPROM indicates default country code should be used
[    9.424931] ath: doing EEPROM country->regdmn map search
[    9.424949] ath: country maps to regdmn code: 0x3a
[    9.424957] ath: Country alpha2 being used: US
[    9.424964] ath: Regpair used: 0x3a
[    9.436457] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[    9.440239] ieee80211 phy0: Atheros AR9561 Rev:0 mem=0xb8100000, irq=47
[   16.760327] jffs2_scan_eraseblock(): End of filesystem marker found at 0x0
[   16.788512] jffs2_build_filesystem(): unlocking the mtd device... done.
[   16.795367] jffs2_build_filesystem(): erasing all blocks after the end marker... done.
[   18.259341] jffs2: notice: (980) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
[   19.546610] device eth1 entered promiscuous mode
[   19.575355] IPv6: ADDRCONF(NETDEV_UP): br-lan: link is not ready
[   19.666392] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   21.640218] eth1: link up (1000Mbps/Full duplex)
[   21.645044] br-lan: port 1(eth1) entered forwarding state
[   21.650686] br-lan: port 1(eth1) entered forwarding state
[   21.678521] IPv6: ADDRCONF(NETDEV_CHANGE): br-lan: link becomes ready
[   23.648501] br-lan: port 1(eth1) entered forwarding state
[   76.258518] random: nonblocking pool is initialized
[  198.239680] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[  198.252946] device wlan0 entered promiscuous mode
[  198.276800] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  198.283623] br-lan: port 2(wlan0) entered forwarding state
[  198.289363] br-lan: port 2(wlan0) entered forwarding state
[  200.288490] br-lan: port 2(wlan0) entered forwarding state
On this OpenWRT wiki page right on top, there is this info:

https://wiki.openwrt.org/toh/tp-link/tl-wr941nd
(2016-03-24) Unfortunately the OpenWrt-image for v6 in Barrier Breaker & Chaos Calmer was built for the Chinese version. A working patch for adding support to the current OpenWrt-trunk can be found here. The patch didn't made it into the CC 15.05 or 15.05.1 release, see here. Trunk snapshots and custom builds of the current 15.05 branch work fine.
So basically it looks like there is a patch, for the support of the WR940N v3 international.

I was wondering- since I could flash OpenWRT on the WR940N v3 international- is there a chance that you could release a Gargoyle Firmware for this router?

Thanks in advance and have a nice day!

It would really be fantastic if we could get the WR940N v3 international to work with Gargoyle. It would probably be the new budget king by far. Costs around 30 dollars, has a low power consuption of 2-2.5 watts on average.

Only downside- it has 100 Mbit LAN, so basically the wifi speeds will be faster than LAN most of the time ;)

I use a WR1043ND v3 TP-Link mainly, I just hooked up the WR940N to a Powerline Adapter in a room that has bad signal and it works very well as a cheap solution. Yes there are powerline adapters with Wifi included, but those are garbage most of the time. The WR940N with external antennas does a great job and is a cheap solution, beeing able to run Gargoyle on it would make it even more amazing.

Post Reply