| v11.x | 2015 | v10 image or trunk | - | Forum thread [[https://​forum.openwrt.org/​viewtopic.php?​id=61309|here]]. Only the flash chip seems to be different compared to v10.x. Supported in [[http://​git.openwrt.org/?​p=openwrt.git;​a=commit;​h=d71d620ac7d5a496bc7be16f9f1046d9c6133d14|trunk]] as from 2016-04-01. You can use 15.05 images for v10 with sysupgrade -F, overriding the hardware check. Compared to v10.0, the antennas have a different shape (a lot like the antennas shipped with Archer C7), and the WAN LED is now duocolour, green and orange. For v15.05.1, an image built from SVN r49389 works out of the box.|

+

| v11.x | 2015 | v10 image or trunk oder LEDE 17.01.2 ​ ​| ​ - | Forum thread [[https://​forum.openwrt.org/​viewtopic.php?​id=61309|here]]. Only the flash chip seems to be different compared to v10.x. Supported in [[http://​git.openwrt.org/?​p=openwrt.git;​a=commit;​h=d71d620ac7d5a496bc7be16f9f1046d9c6133d14|trunk]] as from 2016-04-01. You can use 15.05 images for v10 with sysupgrade -F, overriding the hardware check. Compared to v10.0, the antennas have a different shape (a lot like the antennas shipped with Archer C7), and the WAN LED is now duocolour, green and orange. For v15.05.1, an image built from SVN r49389 works out of the box.|

Beware that this installation method needs a [[doc:​hardware:​port.serial|TTL level serial console]] usb to TTL like DKU-5 data cable or RS232-TTL level shifter like this: {{:media:​max3232.gif?​500}}\\ and [[:​doc:​howto:​generic.flashing.tftp|a working TFTP server]] and should not be attempted unless you have experience with this sort of thing or are eager to learn.

+

Beware that this installation method needs a [[doc:​hardware:​port.serial|TTL level serial console]] usb to TTL like DKU-5 data cable or RS232-TTL level shifter like this: {{media:​doc:​hardware:​serial:​max3232.gif?​500}}\\ and [[:​doc:​howto:​generic.flashing.tftp|a working TFTP server]] and should not be attempted unless you have experience with this sort of thing or are eager to learn.

This is taken more or less verbatim from https://​forum.openwrt.org/​viewtopic.php?​id=24203,​ thanks to dl3daz.

This is taken more or less verbatim from https://​forum.openwrt.org/​viewtopic.php?​id=24203,​ thanks to dl3daz.

Line 191:

Line 198:

4. Done.

4. Done.

-

==== TFTP recovery via bootloader for v8,​v9,​v10,​v11 ====

+

==== TFTP recovery via bootloader for v8,​v9,​v10,​v11,v12 ====

As most other current TP-Link routers this device can be flashed and debricked without serial access. Basically, the procedure is as follows:

As most other current TP-Link routers this device can be flashed and debricked without serial access. Basically, the procedure is as follows:

- Set your PC to use the static IP address ''​192.168.0.66''​ (the router will have ''​192.168.0.86''​)

- Set your PC to use the static IP address ''​192.168.0.66''​ (the router will have ''​192.168.0.86''​)

-

- Put an OpenWrt factory image named: for v8 **mr3420v2_tp_recovery.bin**;​ for v9 **wr841nv9_tp_recovery.bin**;​ for v10 **wr841nv10_tp_recovery.bin**;​ for v11 **wr841nv11_tp_recovery.bin** in the root directory of an TFTP server and start it

+

- Put an OpenWrt factory image named: for v8 **mr3420v2_tp_recovery.bin** ​or **wr841nv8_tp_recovery.bin** (for v8.4); for v9 **wr841nv9_tp_recovery.bin**;​ for v10 **wr841nv10_tp_recovery.bin**;​ for v11 and v12 **wr841nv11_tp_recovery.bin** in the root directory of an TFTP server and start it. For v12 you still need a v12 firmware. Just the filename has to be named as a v11 device!

- Power on the router while pressing the reset button until the lock LED is lighting up

- Power on the router while pressing the reset button until the lock LED is lighting up

- Wait for the router to reboot

- Wait for the router to reboot

+

+

:​!:​**WARNING!** **For hardware version 13, it is very likely that u-boot will be erased while using this method, as most mediatek SOC models tend to!** Therefore, do **NOT** flash sysupgrade image using TFTP! Instead, follow the instructions described here: [[toh:​tp-link:​archer-c50#​tftp_recovery_de-bricking]] for the factory image, for OpenWrt image, you must append the bootloader using dd. If the bootloader gets overwritten,​ the only way out is to use a SPI flash programmer to reflash it.

For details, see [[toh:​tp-link:​tl-wdr4900#​reset_button_method_no_serial_cable_needed]]

For details, see [[toh:​tp-link:​tl-wdr4900#​reset_button_method_no_serial_cable_needed]]

Line 207:

Line 219:

{{page>​meta:​infobox:​dangerous&​noheader&​nofooter&​noeditbtn}}

{{page>​meta:​infobox:​dangerous&​noheader&​nofooter&​noeditbtn}}

-

With the TL-WR842ND router, there is a catch: the stock firmware is obtained from the OEM: [[http://​www.tplink.com/​en/​support/​download/?​model=TL-WR841N| versions 1,​5,​7,​8,​9]](verions ​v1 and v1.5 have same latest fw) and [[http://​www.tplink.com/​en/​support/​download/?​model=TL-WR841ND&​version=V3|link for v3]]

+

With the TL-WR842ND router, there is a catch: the stock firmware is obtained from the OEM: [[http://​www.tplink.com/​en/​support/​download/?​model=TL-WR841N| versions 1,​5,​7,​8,​9]](versions ​v1 and v1.5 have same latest fw) and [[http://​www.tplink.com/​en/​support/​download/?​model=TL-WR841ND&​version=V3|link for v3]]

* in case the file name of this firmware file does not contain the word **//"​boot"//​** in it, you can simply revert back to original firmware

* in case the file name of this firmware file does not contain the word **//"​boot"//​** in it, you can simply revert back to original firmware

Line 223:

Line 235:

</​code>​

</​code>​

-

You should transfer the firmeware ​image to the /tmp folder and revert back to original firmware (if availlable ​you can flash the firmware via the webinterface as well):

+

You should transfer the firmware ​image to the /tmp folder and revert back to original firmware (if available ​you can flash the firmware via the webinterface as well):

Via the safer method using sysupgrade:

Via the safer method using sysupgrade:

Line 235:

Line 247:

</​code>​

</​code>​

-

It is also possible to revert to the stock firmware using the method with tftp described in "TFTP install"​. (you still need the firmware images without the boot part).

+

It is also possible to revert to the stock firmware using the method with tftp described in "TFTP install"​. (you still need the firmware images without the boot part, unless you're using v13, in which case refer to the instructions for TFTP flashing above).

OEM TP-Link firmware for the TL-WR841ND with the **//boot part removed//** or the original firmware if there wasn't a boot part to revert to the original OEM firmware:

OEM TP-Link firmware for the TL-WR841ND with the **//boot part removed//** or the original firmware if there wasn't a boot part to revert to the original OEM firmware:

* Kill the broken ​OWRT firmware<​code>​mtd -r erase rootfs_data</​code>​enter<​code>​firstboot</​code>​enter<​code>​reboot -f</​code>​After rebooting log in again just to check if the router is accessable. If you cant start again at the beginning.

+

* Kill the broken ​OWrt firmware<​code>​mtd -r erase rootfs_data</​code>​enter<​code>​firstboot</​code>​enter<​code>​reboot -f</​code>​After rebooting log in again just to check if the router is accessable. If you cant start again at the beginning.

Now change the network settings on the PC back to "​Aquire IP adress automatically"​ and connect the router with the internet. Do a manual reboot by simply turning it off and back on again. The PC should now get an ip adress by DHCP. If this is the case you successfully resetted the router. If not repeat from the beginning or [[https://​forum.openwrt.org/​viewtopic.php?​id=33906|do this]] if you like.

Now change the network settings on the PC back to "​Aquire IP adress automatically"​ and connect the router with the internet. Do a manual reboot by simply turning it off and back on again. The PC should now get an ip adress by DHCP. If this is the case you successfully resetted the router. If not repeat from the beginning or [[https://​forum.openwrt.org/​viewtopic.php?​id=33906|do this]] if you like.

-

Basically the router now works like after the initial flash to OWRT. Now you have to [[:​doc:​howto:​basic.config|configure the internet connection]] and probably you want to install [[:​doc:​howto:​luci.essentials|LUCI]]. After that open your browser, connect to 192.168.1.1 and log in with the data you entered via telnet.

+

Basically the router now works like after the initial flash to OWrt. Now you have to [[:​doc:​howto:​basic.config|configure the internet connection]] and probably you want to install [[:​doc:​howto:​luci.essentials|LUCI]]. After that open your browser, connect to 192.168.1.1 and log in with the data you entered via telnet.

:!: Note: 30 dBm tx power can't be set if your wireless country is any that allow higher channel than channel 11 (i.e. Viet Nam). If you encounter this situation, I suggest you should change your country to //00 - World//

:!: Note: 30 dBm tx power can't be set if your wireless country is any that allow higher channel than channel 11 (i.e. Viet Nam). If you encounter this situation, I suggest you should change your country to //00 - World//

4. Make a backup of your original ART: <​code>​dd if=/​dev/​mtd4 of=/​tmp/​orig_art.bin</​code>​

4. Make a backup of your original ART: <​code>​dd if=/​dev/​mtd4 of=/​tmp/​orig_art.bin</​code>​

Line 294:

Line 307:

8. Your router will reboot. After that, you will be able to set 30 dBm tx power.

8. Your router will reboot. After that, you will be able to set 30 dBm tx power.

-

-

-

-

Line 451:

Line 460:

</​code>​

</​code>​

</​tabbox>​

</​tabbox>​

+

== Final actions ==

== Final actions ==

Just be sure that the files are saved. To edit the files on windows, either use vi on the openwrt, check for a tutorial online, the basic commands are not difficult; or use winscp with a SCP connection and edit the files with an editor on windows. Then reboot the system and check for the wifi connection.

Just be sure that the files are saved. To edit the files on windows, either use vi on the openwrt, check for a tutorial online, the basic commands are not difficult; or use winscp with a SCP connection and edit the files with an editor on windows. Then reboot the system and check for the wifi connection.

Line 537:

Line 547:

(esc :wq)

(esc :wq)

</​code>​

</​code>​

+

===== Serial console =====

===== Serial console =====

Line 544:

Line 555:

==== Yet another user notes ====

==== Yet another user notes ====

+

* For TP-Link WR841ND V7.0 the 10k the pullup resistor is not required, connect all four pins (tested with 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter, make sure to set its voltage to 3V not 5V)

* For TP-LINK WR841ND V7.2 power conector (+5V) is ignored, just connect RX - TX - GND and router power cord, work fine...

* For TP-LINK WR841ND V7.2 power conector (+5V) is ignored, just connect RX - TX - GND and router power cord, work fine...

* My TP-LINK WR841ND V7.2 has a VCC of +3.3V and like the TL-MR3420 [[:​toh:​tp-link:​tl-mr3420#​serial]] needed to connect a 10k pullup resistor between the TX and the 3.3V pin to get reliable serial:

* My TP-LINK WR841ND V7.2 has a VCC of +3.3V and like the TL-MR3420 [[:​toh:​tp-link:​tl-mr3420#​serial]] needed to connect a 10k pullup resistor between the TX and the 3.3V pin to get reliable serial:

//NOTE: ART partition can be extracted from original flash (EON 2M) at last 64K area, address as 0x1F0000. ART data need to be appended to new flash manually, otherwise an ar934x_wmac error occurs without wifi function.//