OpenWrt Forum Archive

Topic: TP-Link TL-WR941ND v5.0

The content of this topic has been archived between 31 Mar 2018 and 27 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

neoke007 wrote:

I installed this firmware to my device (941ND ver 5.0). I found the problem:
- Failsafe not working: Lan interface not working (light's lan or wan not turn on), so I can not connect to device via Ethernet port (lan or wan).

Do anyone else have same problem ?

Unfortunately, yes. I successfully bricked my 5.0 version router using that firmware. U-Boot starts the kernel, but it crashes with kernel panic. See last couple of lines in attached log. I've got a serial cable, but was yet unable to interrupt the boot loop.

Regards
Ektus.

U-Boot 1.1.4 (Jun  8 2013 - 15:28:02)

U-boot AP123


DRAM:  32 MB
Flash Manuf Id 0x1c, DeviceId0 0x30, DeviceId1 0x16
flash size 4MB, sector count = 64
Flash:  4 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag934x_enet_initialize...
No valid address in Flash. Using fixed address
No valid address in Flash. Using fixed address
 wasp  reset mask:c03300
WASP ----> S27 PHY
file: ag934x.c,line: 189==: set LAN&WAN SWAP. --debug by HouXB
GMAC: cfg1 0x80000000 cfg2 0x7114
eth0: ba:be:fa:ce:08:41
s27 reg init
athrs27_phy_setup ATHR_PHY_CONTROL 4 :0x1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 4 :0x10
eth0 up
WASP ----> S27 PHY
file: ag934x.c,line: 189==: set LAN&WAN SWAP. --debug by HouXB
GMAC: cfg1 0xf cfg2 0x7214
eth1: ba:be:fa:ce:08:41
s27 reg init lan
ATHRS27: resetting s27
ATHRS27: s27 reset done
athrs27_phy_setup ATHR_PHY_CONTROL 0 :0x1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 0 :0x10
athrs27_phy_setup ATHR_PHY_CONTROL 1 :0x1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 1 :0x10
athrs27_phy_setup ATHR_PHY_CONTROL 2 :0x1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 2 :0x10
athrs27_phy_setup ATHR_PHY_CONTROL 3 :0x1000
athrs27_phy_setup ATHR_PHY_SPEC_STAUS 3 :0x10
eth1 up
eth0, eth1
Autobooting in 1 seconds
## Booting image at 9f020000 ...
   Uncompressing Kernel Image ... OK

Starting kernel ...

[    0.000000] bootconsole [early0] enabled
[    0.000000] CPU revision is: 0001974c (MIPS 74Kc)
[    0.000000] cpu srif ddr srif cpu 535 ddr 400 ahb 200
AR9341
detect mem size
Uart Init
Booting WASP !!! -:) ...
[    0.000000] sys id = 121 Atheros AR9341 rev 1.1 (0x0121)
[    0.000000] Determined physical RAM map:
[    0.000000]  memory: 02000000 @ 00000000 (usable)
[    0.000000] Zone ranges:
[    0.000000]   Normal   [mem 0x00000000-0x01ffffff]
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x00000000-0x01ffffff]
[    0.000000] Primary instruction cache 64kB, 4-way, VIPT, I-cache aliases, linesize 32 bytes.
[    0.000000] Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
[    0.000000] Linux version 3.9.4 (root@dd-wrt) (gcc version 4.8.1 (OpenWrt/Linaro GCC 4.8-2013.04 r36550) ) #328 Mon May 27 08:33:25 CEST 2013
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 8128
[    0.000000] Kernel command line: console=ttyS0,115200 root=1f02 rootfstype=squashfs noinitrd init=/sbin/init
[    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] __ex_table already sorted, skipping sort
[    0.000000] Writing ErrCtl register=00000000
[    0.000000] Readback ErrCtl register=00000000
[    0.000000] Memory: 29004k/32768k available (2190k kernel code, 3764k reserved, 419k data, 204k init, 0k highmem)
[    0.000000] NR_IRQS:80
[    0.000000] Calibrating delay loop... 266.64 BogoMIPS (lpj=1333248)
[    0.080000] pid_max: default: 32768 minimum: 301
[    0.080000] Mount-cache hash table entries: 512
[    0.090000] NET: Registered protocol family 16
[    0.490000] 25MHZ ref freq
[    0.510000] bio: create slab <bio-0> at 0
[    0.520000] Switching to clocksource MIPS
[    0.520000] NET: Registered protocol family 2
[    0.530000] TCP established hash table entries: 512 (order: 0, 4096 bytes)
[    0.530000] TCP bind hash table entries: 512 (order: -1, 2048 bytes)
[    0.540000] TCP: Hash tables configured (established 512 bind 512)
[    0.540000] TCP: reno registered
[    0.540000] UDP hash table entries: 256 (order: 0, 4096 bytes)
[    0.550000] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[    0.560000] NET: Registered protocol family 1
[    0.560000] gpio_proc: module loaded and /proc/gpio/ created
[    0.570000] wl0gpio_proc: module loaded and /proc/wl0gpio/ created
[    0.580000] squashfs: version 3.0 (2006/03/15) Phillip Lougher
[    0.580000] msgmni has been set to 56
[    0.590000] io scheduler noop registered (default)
[    0.590000] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[    0.620000] serial8250.0: ttyS0 at MMIO 0x18020000 (irq = 11) is a 16550A
[    0.620000] console [ttyS0] enabled, bootconsole disabled
[    0.620000] console [ttyS0] enabled, bootconsole disabled
[    0.640000] guessed flashsize = 4M
[    0.640000] scanning for root partition
[    0.640000] tplink uboot detected
[    0.650000] guessed bootloader size = 20000
[    0.660000]
[    0.660000] found squashfs at 110000
[    0.660000] Creating 8 MTD partitions on "ar7240-nor0":
[    0.670000] 0x000000000000-0x000000020000 : "RedBoot"
[    0.670000] 0x000000020000-0x0000003e0000 : "linux"
[    0.680000] 0x000000110000-0x0000003d0000 : "rootfs"
[    0.690000] mtd: partition "rootfs" set to be root filesystem
[    0.690000] 0x0000003d0000-0x0000003e0000 : "ddwrt"
[    0.700000] 0x0000003e0000-0x0000003f0000 : "nvram"
[    0.700000] 0x0000003f0000-0x000000400000 : "board_config"
[    0.710000] 0x000000000000-0x000000400000 : "fullflash"
[    0.720000] 0x000000000000-0x000000020000 : "fullboot"
[    0.730000] libphy: Fixed MDIO Bus: probed
[    0.730000] tun: Universal TUN/TAP device driver, 1.6
[    0.740000] tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
[    0.740000] PPP generic driver version 2.4.2
[    0.750000] PPP BSD Compression module registered
[    0.750000] PPP Deflate Compression module registered
[    0.760000] PPP MPPE Compression module registered
[    0.760000] NET: Registered protocol family 24
[    0.780000] u32 classifier
[    0.790000]     Performance counters on
[    0.790000]     input device check on
[    0.790000]     Actions configured
[    0.800000] Netfilter messages via NETLINK v0.30.
[    0.800000] nf_conntrack version 0.5.0 (453 buckets, 1812 max)
[    0.810000] nf_conntrack_rtsp v0.6.21 loading
[    0.810000] nf_nat_rtsp v0.6.21 loading
[    0.820000] ip_tables: (C) 2000-2006 Netfilter Core Team
[    0.820000] TCP: westwood registered
[    0.830000] TCP: hybla registered
[    0.830000] TCP: vegas registered
[    0.830000] NET: Registered protocol family 17
[    0.840000] Bridge firewalling registered
[    0.840000] 8021q: 802.1Q VLAN Support v1.8
[    0.850000] searching for nvram
[    0.850000] nvram size = 0
[    0.880000] Broken NVRAM found, recovering it (Magic 55AA030E)
[    0.890000] Atheros AR71xx hardware watchdog driver version 0.1.0
[    0.890000] ar71xx-wdt: timeout=15 secs (max=171) ref freq=25000000
[    0.920000] SQUASHFS error: Unknown inode type 15 in squashfs_iget!
[    0.920000] List of all partitions:
[    0.930000] 1f00             128 mtdblock0  (driver?)
[    0.930000] 1f01            3840 mtdblock1  (driver?)
[    0.940000] 1f02            2816 mtdblock2  (driver?)
[    0.940000] 1f03              64 mtdblock3  (driver?)
[    0.950000] 1f04              64 mtdblock4  (driver?)
[    0.950000] 1f05              64 mtdblock5  (driver?)
[    0.960000] 1f06            4096 mtdblock6  (driver?)
[    0.960000] 1f07             128 mtdblock7  (driver?)
[    0.970000] No filesystem could mount root, tried:  squashfs
[    0.970000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
[    0.970000] Rebooting in 1 seconds..

[    0.690000] mtd:
partition "rootfs" set to be
root filesystem
[    0.690000]
0x0000003d0000-0x0000003e0000 :
"ddwrt"

I hardly think that you flashed the firmware posted here..

nebbia88 wrote:

[    0.690000] mtd:
partition "rootfs" set to be
root filesystem
[    0.690000]
0x0000003d0000-0x0000003e0000 :
"ddwrt"

I hardly think that you flashed the firmware posted here..

ahem... sorry. Has been a while back (was waiting for delivery of the serial cable), so it's possible I took another file. Yes, wr941NDv5_factory-to-ddwrt.bin looks like it. Sorry for the inconvenience, will switch to the other forum...


Regards
Ektus.

Ektus wrote:

Sorry for the inconvenience, will switch to the other forum....

I didn't meant that...

about stoppig uboot, are you sure you typed "tpl" really fast, just when you see "Autoboot...."?? type it many times.. no enter key required!

nebbia88 wrote:
Ektus wrote:

Sorry for the inconvenience, will switch to the other forum....

I didn't meant that...

about stoppig uboot, are you sure you typed "tpl" really fast, just when you see "Autoboot...."?? type it many times.. no enter key required!

Ah okay. Tried it again, and have got a prompt "wasp>" in hyperterminal. So something is working. Will continue tomorrow, it's almost midnight here...


Thank you for your help!
Ektus.

Ektus wrote:

Ah okay. Tried it again, and have got a prompt "wasp>" in hyperterminal. So something is working. Will continue tomorrow, it's almost midnight here...

Success! Flashed openwrt and got the web interface (luci) running.


Thank you!

wasp> tftp 0x80000000 tl-wr941nd_v5.0.bin
Using eth1 device
TFTP from server 192.168.1.100; our IP address is 192.168.1.111
Filename 'tl-wr941nd_v5.0.bin'.
Load address: 0x80000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         #################################################################
         ######################################################
done
Bytes transferred = 3932160 (3c0000 hex)
wasp> erase.b 0x9f020000 +0x3c0000

First 0x2 last 0x3d sector size 0x10000
  61
Erased 60 sectors
wasp> cp.b 0x80000000 0x9f020000 0x3c0000
Copy to Flash... write addr: 9f020000
done
wasp> reset

U-Boot 1.1.4 (Jun  8 2013 - 15:28:02)

U-boot AP123


DRAM:  32 MB
Flash Manuf Id 0x1c, DeviceId0 0x30, DeviceId1 0x16
flash size 4MB, sector count = 64
Flash:  4 MB
Using default environment

In:    serial
Out:   serial
Err:   serial
Net:   ag934x_enet_initialize...
sbiomed wrote:
thotypous wrote:

I have just put a TL-WR941ND v5.0 router on production with OpenWrt. You can use the same firmware file as TL-WR841N v8, but you need to modify the header in order for the TP-Link web-interface to recognize it as a valid firmware for WR941ND v5.0 hardware.

For the impatient, I have put my modified firmware online: tl-wr941nd_v5.0.bin. MD5 is: db062f1699c760775c5046cc303cba91. It worked perfectly with my router (I did not need to open it at all), but no warranties it will not brick your router, though.

If you want to modify the firmware yourself, do as follows:

  1. Download openwrt-ar71xx-generic-tl-wr841n-v8-squashfs-factory.bin

  2. Open it in a hex editor. Look at offset 0x40. There should be the following bytes: 08 41 00 08. Modify to: 09 41 00 05

  3. Get mktplinkfw.c, md5.c and md5.h. Compile the tool: gcc -Os mktplinkfw.c md5.c -o mktplinkfw.

  4. Run: ./mktplinkfw -i *-factory.bin

  5. Look for the expected MD5Sum1: expected : e5 67 34 4d 04 99 20 60 f5 76 c6 04 15 81 ab f8

  6. Open the hex editor again, go to offset 0x4c, and copy the MD5 above (it should span from offset 0x4c to offset 0x5b).

  7. Go and upload the resulting file to firmware upgrade (in TP-Link web-interface). Good luck.

Many thanks to LOM from DD-WRT and to cable007 for reporting this approach worked with DD-WRT.




I can confirm the firmware works on TL-wr941ND v 5.0000. With the following defects:-
1)PPPOE connection drops at regular interval.
2)Coverage is significantly dropped in comparision to TP-LINK firmware.
So, can't use the most of router. Hence
I reverted back to the original firmware. sad
I hope the firmware appears soon.


I have all the sames problems.
is impossible to use

i back to original firmware

Hi there! Are there some news about this topic? Like some users, I put the firmware posted in this thread and it worked, but the power of coverage is very bad compared with the original firmware, so I reverted back.

Have you any idea about the time that will take to correct this issues and get a stable release for this device?

Thank you.

any news about?

neoke007 wrote:

I installed this firmware to my device (941ND ver 5.0). I found the problem:
- Failsafe not working: Lan interface not working (light's lan or wan not turn on), so I can not connect to device via Ethernet port (lan or wan).

Do anyone else have same problem ?

Hi neoke007, Sorry for the delay. The device is installed in another city and I only had the chance to access it physically during this weekend.

I have tested the failsafe mode and it worked OK. Please make sure you are pressing the correct button. Press the button in the rear of the device, near the on/off switch (I think it is labeled "QSS/reset"). Please note that the button in the front of the device (which is labeled "wireless on/off") cannot be used to start the failsafe mode.

So, press the rear button as soon as the SYS light blinks for the first time. It will start blinking faster. Then you can access the router by plugging an Ethernet cable to the WAN port (not to one of the switch ports!). The router will be accessible at 192.168.1.1, as usual.

For the people complaining about signal range / coverage issues, unfortunately I can't do anything about that because I can't reproduce those problems. Although I only have physical access to it around once a month, my device is working flawlessly since my first report, and is covering 3 floors of a construction. The users of my device are pretty satisfied with the signal.

(Last edited by thotypous on 28 Oct 2013, 22:09)

I have a tp-link wr940n V2

"Firmware Version: 3.14.5 Build 130709 Rel.36000n
Hardware Version: WR940N v2/WR941ND v5 00000000".

Can i use this firmware http://downloads.openwrt.org/attitude_a … actory.bin for my device?

Firmwares (on official site) for TL-WR841ND v8 (130506) and TL-WR941ND_V5 (130709) are different. Although, WR941ND_V5  and WR940N v2 are the same (130709).


Thanks!

(Last edited by Iltd on 11 Nov 2013, 23:17)

madmax wrote:

PunBB bbcode test

Hi, what are the models of the chip LNA &PA, can't see it clearly.

Anyone knows?

(Last edited by eeff11 on 14 Dec 2013, 12:44)

Iltd wrote:

I have a tp-link wr940n V2

"Firmware Version: 3.14.5 Build 130709 Rel.36000n
Hardware Version: WR940N v2/WR941ND v5 00000000".

Can i use this firmware http://downloads.openwrt.org/attitude_a … actory.bin for my device?

Firmwares (on official site) for TL-WR841ND v8 (130506) and TL-WR941ND_V5 (130709) are different. Although, WR941ND_V5  and WR940N v2 are the same (130709).


Thanks!

I have same router as yours.
Use modded firmware by thotypous  tl-wr941nd_v5.0.bin this works. Before updating don't forget to factory reset router. 
Note! Do not update by wifi use lan connection.

Hi!

I have the same router as shown in the pictures (it says HW ver 5.1 on the device and the box however) and flashes successfully with the here linked modded firmware and also after that with regular firmware for 841n v8 via sys upgrade.
I have to say that the WAN dropping connection (serial console gets spammed with eth0 up / eth0 down messages every second or so at the worst times with trunk snapshot for 841nd v8 and not so often with the modded FW on this thread) stuff is true, but WLAN coverage is pretty good for me smile
Also, I'm now trying to tweak the PPPoE daemon as I have a feeling that it might be the culprit... (did some tests with various devices on the WAN port)
But the whole connection drop thing is very very annoying...
I would love to see a specially designed firmware flavor for this router, since its really needed and this HW version seems to be the one thats being shipped right now as i have ordered the router a few days ago via Amazon Germany...
I realize there are A LOT of different router and you can't cover them all, but also the TP-LINK routers seem to be very popular with OpenWRT users, which is also why I bought this exact router again. (Had HW ver 3.6 before, was awesome but I failed at flashing due to negligence and the serial port is f***d beyond repair -.-)

I would try to compile my own firmware flavor from trunk, but I can't quite work that out as of today, but I'll keep trying! (Now that I have a router with a serial console that works...) If I succeed, I shall post the FW here for all the unlucky HW ver 5 users!

Until then, please fix ! Thank you !

(Last edited by Profecy on 21 Dec 2013, 21:50)

thotypous wrote:

I have just put a TL-WR941ND v5.0 router on production with OpenWrt. You can use the same firmware file as TL-WR841N v8, but you need to modify the header in order for the TP-Link web-interface to recognize it as a valid firmware for WR941ND v5.0 hardware.

For the impatient, I have put my modified firmware online: tl-wr941nd_v5.0.bin. MD5 is: db062f1699c760775c5046cc303cba91. It worked perfectly with my router (I did not need to open it at all), but no warranties it will not brick your router, though.

If you want to modify the firmware yourself, do as follows:

  1. Download openwrt-ar71xx-generic-tl-wr841n-v8-squashfs-factory.bin

  2. Open it in a hex editor. Look at offset 0x40. There should be the following bytes: 08 41 00 08. Modify to: 09 41 00 05

  3. Get mktplinkfw.c, md5.c and md5.h. Compile the tool: gcc -Os mktplinkfw.c md5.c -o mktplinkfw.

  4. Run: ./mktplinkfw -i *-factory.bin

  5. Look for the expected MD5Sum1: expected : e5 67 34 4d 04 99 20 60 f5 76 c6 04 15 81 ab f8

  6. Open the hex editor again, go to offset 0x4c, and copy the MD5 above (it should span from offset 0x4c to offset 0x5b).

  7. Go and upload the resulting file to firmware upgrade (in TP-Link web-interface). Good luck.

Many thanks to LOM from DD-WRT and to cable007 for reporting this approach worked with DD-WRT.

Hi Thotypous,

I have installed successfully your posted openwrt firmware on my router TPLink WR941NDv5. Everything is working great with LuCI UI. I am totally a newbie here so I do not know how to set up my TPLink router as a repeater. My main router is Cisco WAG120n. Please help me solve this.

Thanks million times =]]

Hope you guys can help me as soon as you can =]]

Hello guys,

I want to install OpenWRT, the site says that the supported version is the Attitude Adjustment (12.09 final) for v5.0 but I do not know which to download.

Which one should I Download?
openwrt-atheros-combined.squashfs.img
openwrt-atheros-root.squashfs
openwrt-atheros-ubnt2-pico2-squashfs.bin
openwrt-atheros-ubnt2-squashfs.bin
openwrt-atheros-ubnt5-squashfs.bin

After installing this will only work 2 antennas?

(Last edited by scaloni on 16 May 2014, 03:14)

This model is ar71xx-architecture, so you will find your images here (or just use the links in the previous postings).

MBS wrote:

This model is ar71xx-architecture, so you will find your images here (or just use the links in the previous postings).

These links are not my version (TL-WR941ND Ver:5.0 // FCC ID: TE7WR941NXV5).

There is no official version of OpenWRT to my router?

That is what this thread is pointing out. So, this seems to be the usable workaround at the moment:

thotypous wrote:

I have just put a TL-WR941ND v5.0 router on production with OpenWrt. You can use the same firmware file as TL-WR841N v8, but you need to modify the header in order for the TP-Link web-interface to recognize it as a valid firmware for WR941ND v5.0 hardware.

For the impatient, I have put my modified firmware online: tl-wr941nd_v5.0.bin. MD5 is: db062f1699c760775c5046cc303cba91. It worked perfectly with my router (I did not need to open it at all), but no warranties it will not brick your router, though.

If you want to modify the firmware yourself, do as follows:

  1. Download openwrt-ar71xx-generic-tl-wr841n-v8-squashfs-factory.bin

  2. Open it in a hex editor. Look at offset 0x40. There should be the following bytes: 08 41 00 08. Modify to: 09 41 00 05

  3. Get mktplinkfw.c, md5.c and md5.h. Compile the tool: gcc -Os mktplinkfw.c md5.c -o mktplinkfw.

  4. Run: ./mktplinkfw -i *-factory.bin

  5. Look for the expected MD5Sum1: expected : e5 67 34 4d 04 99 20 60 f5 76 c6 04 15 81 ab f8

  6. Open the hex editor again, go to offset 0x4c, and copy the MD5 above (it should span from offset 0x4c to offset 0x5b).

  7. Go and upload the resulting file to firmware upgrade (in TP-Link web-interface). Good luck.

Many thanks to LOM from DD-WRT and to cable007 for reporting this approach worked with DD-WRT.

R 18 (JP1) is that value? ohms?
where do the jumper to enable tx?
thank you

wr941ND ver 5.0
I installed this firmware, because the LED-lan3-LAN4 not work?


config system
    option hostname 'OpenWrt'
    option timezone 'UTC'

config timeserver 'ntp'
    list server '0.openwrt.pool.ntp.org'
    list server '1.openwrt.pool.ntp.org'
    list server '2.openwrt.pool.ntp.org'
    list server '3.openwrt.pool.ntp.org'
    option enable_server '0'

config led 'led_wan'
    option name 'WAN'
    option sysfs 'tp-link:green:wan'
    option trigger 'netdev'
    option dev 'eth0'
    option mode 'link tx rx'

config led 'led_lan1'
    option name 'LAN1'
    option sysfs 'tp-link:green:lan1'
    option trigger 'switch0'
    option port_mask '0x04'

config led 'led_lan2'
    option name 'LAN2'
    option sysfs 'tp-link:green:lan2'
    option trigger 'switch0'
    option port_mask '0x08'

config led 'led_lan3'
    option name 'LAN3'
    option sysfs 'tp-link:green:lan3'
    option trigger 'switch0'
    option port_mask '0x10'

config led 'led_lan4'
    option name 'LAN4'
    option sysfs 'tp-link:green:lan4'
    option trigger 'switch0'
    option port_mask '0x02'

config led 'led_wlan'
    option name 'WLAN'
    option sysfs 'tp-link:green:wlan'
    option trigger 'phy0tpt'

niti.sumitsharma wrote:
Iltd wrote:

I have a tp-link wr940n V2

"Firmware Version: 3.14.5 Build 130709 Rel.36000n
Hardware Version: WR940N v2/WR941ND v5 00000000".

Can i use this firmware http://downloads.openwrt.org/attitude_a … actory.bin for my device?

Firmwares (on official site) for TL-WR841ND v8 (130506) and TL-WR941ND_V5 (130709) are different. Although, WR941ND_V5  and WR940N v2 are the same (130709).


Thanks!

I have same router as yours.
Use modded firmware by thotypous  tl-wr941nd_v5.0.bin this works. Before updating don't forget to factory reset router. 
Note! Do not update by wifi use lan connection.

Same router here, is everything working fine with tl-wr941nd_v5.0.bin? do you think it is stable enough for an office?

thanks

If someone still interested, here is images with miniupnpd and openvpn out-of-the-box: http://monster.xe-xe.org/wr941nd-v52/
It's stable Attitude Adjustment (r42171), nevermind the "russian" tag, it's just for additional LuCI language pack, english is available too.

Hi,
I have TP-Link TL-WR941ND v5.0 router. I successfully updated it with OpenWrt backfire/trunk but again i'm updating it with OpenWrt and this time Bad Update happened. I mean it stopped at 55%. Now my router is not working. when i open 192.168.1.1 or 192.168.0.1 it does not open it. I tried it with Reset button from the back side of it. Already pushed reset button for 30 sec. or more. It does not work. Now my router looks Useless.
 
  Guys!! can u plz help me??
  Thanks in Advance.

thotypous wrote:

I have just put a TL-WR941ND v5.0 router on production with OpenWrt. You can use the same firmware file as TL-WR841N v8, but you need to modify the header in order for the TP-Link web-interface to recognize it as a valid firmware for WR941ND v5.0 hardware.

For the impatient, I have put my modified firmware online: tl-wr941nd_v5.0.bin. MD5 is: db062f1699c760775c5046cc303cba91. It worked perfectly with my router (I did not need to open it at all), but no warranties it will not brick your router, though.

If you want to modify the firmware yourself, do as follows:

  1. Download openwrt-ar71xx-generic-tl-wr841n-v8-squashfs-factory.bin

  2. Open it in a hex editor. Look at offset 0x40. There should be the following bytes: 08 41 00 08. Modify to: 09 41 00 05

  3. Get mktplinkfw.c, md5.c and md5.h. Compile the tool: gcc -Os mktplinkfw.c md5.c -o mktplinkfw.

  4. Run: ./mktplinkfw -i *-factory.bin

  5. Look for the expected MD5Sum1: expected : e5 67 34 4d 04 99 20 60 f5 76 c6 04 15 81 ab f8

  6. Open the hex editor again, go to offset 0x4c, and copy the MD5 above (it should span from offset 0x4c to offset 0x5b).

  7. Go and upload the resulting file to firmware upgrade (in TP-Link web-interface). Good luck.

Many thanks to LOM from DD-WRT and to cable007 for reporting this approach worked with DD-WRT.

How do I go back to original firmware?