Debrick TP-Link TL-WR841N by serial port or JTAG - need help

Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware
Goto page 1, 2  Next
Author Message
erreterr
DD-WRT Novice


Joined: 15 Oct 2010
Posts: 41

PostPosted: Wed May 04, 2011 16:58    Post subject: Debrick TP-Link TL-WR841N by serial port or JTAG - need help Reply with quote
Hi
I managed to brick a TL-wr841N by accidentally trying to revert to TP-link firmware as the dd-wrt was not working good with version 7.2 and I wrote the TL-WR741 webrevert file. Now I need to find the serial pinout for JTAG repair but I cannot find the right picture for this model as it is completely different from TL-WR841ND versions. Can somebody help me from the attached photo to find the pinout for this one?
Thanks in advance


Sponsor
fyi2000
DD-WRT Guru


Joined: 04 Apr 2010
Posts: 642

PostPosted: Wed May 04, 2011 17:13    Post subject: Reply with quote
DD-WRT Forum :: View topic - WR841N(D) V7 USB 2.0 Mod

Not sure if v7.1 same as v7.2.
maurirp
DD-WRT Novice


Joined: 25 Apr 2011
Posts: 1

PostPosted: Tue May 24, 2011 0:13    Post subject: WRT841N V7.2 Reply with quote
You have to short VCC and TX with a 10k resistor, this is TTL serial, you can't connect it directly to rs232

See on the attached image for port position
m_elias
DD-WRT Novice


Joined: 05 Jul 2006
Posts: 47

PostPosted: Mon Aug 08, 2011 19:46    Post subject: Reply with quote
I have been trying to unbrick my WR81ND using the serial pinout shown on this thread and the u-boot commands shown here http://www.dd-wrt.com/phpBB2/viewtopic.php?t=83238&postdays=0&postorder=asc&start=0

I have the firmware file wr841nv7_en_3_12_5_up(100929).bin downloaded from TP-Link.

Anyone have experience with this? Please explain to the me steps to restore any working firmware, I'd prefer the stock firmware.

Thanks.
m_elias
DD-WRT Novice


Joined: 05 Jul 2006
Posts: 47

PostPosted: Mon Aug 08, 2011 20:27    Post subject: Reply with quote
I found some more info here http://www.dd-wrt.com/phpBB2/viewtopic.php?p=626571 on page 16. The U-boot commands for a WR841N(D) are as follows:

setenv serverip [your tftp server's ip addr]

setenv ipaddr [ip on same subnet as server]

tftpboot 0x81000000 [filename.bin, must match filename on tftp server, used bin file from tp-link web download]

erase 0x9f020000 +0x3c0000

cp.b 0x81000000 0x9f020000 0x3c0000

bootm 0x9f020000
hawkeye1103
DD-WRT Novice


Joined: 19 Feb 2013
Posts: 1

PostPosted: Tue Feb 19, 2013 23:24    Post subject: Reply with quote
Hey,

I have tried the method explained in the post above on a WR841N v8 but failed at repairing it

After I flashed the firmware via serial and rebooted the router. I got the following leds lit up: power, Wan, LAN 1,2,3, the rest are off.

Can't get any kind of connection wan or anything else.
Serial is not showing any activity also.
V-ctor
DD-WRT Novice


Joined: 01 May 2013
Posts: 2

PostPosted: Wed May 01, 2013 12:33    Post subject: Reply with quote
Have anybody debricked WR841N v8 via serial ?
V-ctor
DD-WRT Novice


Joined: 01 May 2013
Posts: 2

PostPosted: Thu May 02, 2013 6:53    Post subject: Reply with quote
hawkeye1103 wrote:
Hey,

setenv serverip [your tftp server's ip addr]

setenv ipaddr [ip on same subnet as server]

tftpboot 0x81000000 [filename.bin, must match filename on tftp server, used bin file from tp-link web download]

erase 0x9f020000 +0x3c0000

cp.b 0x81000000 0x9f020000 0x3c0000

bootm 0x9f020000


It helped me!!! Uraaa!!! I debricked my wr841n v8.0 with this wr841nv8_ru_3_14_19_up(120809).bin file.
http://www.tp-linkru.com/Resources/software/TL-WR841N_V8_121009_RU.rar
It's Russian one for my russian router.
Probably you can use another bin file (for your country) but you have to choose file name without "boot".
sunkai
DD-WRT Novice


Joined: 18 Aug 2009
Posts: 19

PostPosted: Sun May 26, 2013 16:41    Post subject: Reply with quote
I have the same problem: a bricked v8.4, through loading the latest v8.x dd-wrt firmware.

I have an operational serial console interface, and can get to the "wasp>" prompt with the "tpl" interrupt, but neither the WAN nor LAN ports appear to be operational.

After connecting a port on the router directly to my computer's port, and putting both on the same subnet (192.168.1.x), there still doesn't appear to be a connection.

I'm running TFTP32 with the standard install configuration, and have selected the 192.168.1.x interface to run the server on.

Are there any settings in TFTP32 that should be changed from the defaults?

Is there any other software that can be used to validate the Ethernet link?

Any help much appreciated.
sunkai
DD-WRT Novice


Joined: 18 Aug 2009
Posts: 19

PostPosted: Mon May 27, 2013 11:52    Post subject: Reply with quote
Windows 7 classified the Ethernet connection between my computer and the router as an "Unidentified Network". This was causing the firewall to block the TFTP port (69).

Once I disable the Windows firewall, I was able to transfer the chosen firmware through LAN port 1.
sanist
DD-WRT Novice


Joined: 02 Oct 2008
Posts: 7

PostPosted: Sun Sep 08, 2013 9:31    Post subject: Reply with quote
OK, so here is my situation: I have WR841ND v8.1, which I flashed to openwrt 12.09rc1 successfully.

In my attempt to subsequently install ddwrt, I first attempted to return to TP-stock firmware and after much searching online for a non-boot firmware, i came across wr841nv8_en_3_13_17_up(120418).bin.

I flahsed it via web interface, and bricked my router. I am now connecting via serial interface, and am getting a strange behaviour: I can't seem to get to a state where I can force U-boot. Instead, the system appears to boot a corrupted image, which nevertheless gets me to a login prompt. I can't find any valid user/passwd combination (admin/admin, root/admin, root/5up, my previously functioning root/password combo).

Can anybody shed some light. I include a log of the boot sequence.

Thanks


flash_size passed from bootloader = 4•K¬ëKA끐L¦fHè¤ÔR"I褅Mº&&RJÕդüi¤¹™, YRam size passed from bootloader =33554432 «
CPU revision is: 0001974c (MIPS 74Kc)ªTŠ –
ath_sys_frequency: cpu srif ddr srif cpu 535 ddr 400 ahb 200½Ó¨Q¨5……Õ*ғ‚áÅ`…•ÑZ
Determined physical RAM map:
memory: 02000000 @ 00000000 (usable)
Zone PFN ranges:
Normal 0x00000000 -> 0x00002000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00002000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 8128
Kernel command line: console=ttyS0,115200 root=31:2 rootfstype=squashfs init=/sM
PID hash table entries: 128 (order: 7, 512 bytes)
Dentry cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 2048 (order: 1, 8192 bytes)
Primary instruction cache 64kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 32kB, 4-way, VIPT, cache aliases, linesize 32 bytes
Writing ErrCtl register=00000000
Readback ErrCtl register=00000000
Memory: 30132k/32768k available (1722k kernel code, 2636k reserved, 426k data, )
NR_IRQS:128
plat_time_init: plat time init done
Calibrating delay loop... 267.26 BogoMIPS (lpj=534528)
Mount-cache hash table entries: 512
NET: Registered protocol family 16
bio: create slab <bio-0> at 0
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
NET: Registered protocol family 2
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 1024 (order: 1, 8192 bytes)
TCP bind hash table entries: 1024 (order: 0, 4096 bytes)
TCP: Hash tables configured (established 1024 bind 1024)
TCP reno registered
NET: Registered protocol family 1
ATH GPIOC major 0
squashfs: version 4.0 (2009/01/31) Phillip Lougher
msgmni has been set to 58
io scheduler noop registered
io scheduler deadline registered (default)
Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0xb8020000 (irq = 19) is a 16550A
console [ttyS0] enabled
PPP generic driver version 2.4.2
NET: Registered protocol family 24
5 cmdlinepart partitions found on MTD device ath-nor0
Creating 5 MTD partitions on "ath-nor0":
0x000000000000-0x000000020000 : "u-boot"
0x000000020000-0x000000120000 : "kernel"
0x000000120000-0x0000003e0000 : "rootfs"
0x0000003e0000-0x0000003f0000 : "config"
0x0000003f0000-0x000000400000 : "art"
->Oops: flash id 0x1c3016 .
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
Port Status 1c000004
ath-ehci ath-ehci.0: ATH EHCI
ath-ehci ath-ehci.0: new USB bus registered, assigned bus number 1
ehci_reset Intialize USB CONTROLLER in host mode: 13
ehci_reset Port Status 1c000000
ath-ehci ath-ehci.0: irq 3, io mem 0x1b000000
ehci_reset Intialize USB CONTROLLER in host mode: 13
ehci_reset Port Status 1c000000
ath-ehci ath-ehci.0: USB 2.0 started, EHCI 1.00
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
TCP cubic registered
NET: Registered protocol family 17
802.1Q VLAN Support v1.8 Ben Greear <greearb@candelatech.com>
All bugs added by David S. Miller <davem@redhat.com>
athwdt_init: Registering WDT success
ath_otp_init: Registering OTP success
ath_clksw_init: Registering Clock Switch Interface success
VFS: Mounted root (squashfs filesystem) readonly on device 31:2.
Freeing unused kernel memory: 112k freed
init started: BusyBox v1.01 (2012.04.13-11:59+0000) multi-call binary
This Board use 2.6.31
xt_time: kernel timezone is -0000
nf_conntrack version 0.5.0 (512 buckets, 5120 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
insmod: cannot open module `/lib/modules/2.6.31/kernel/iptable_raw.ko': No suchy
insmod: cannot open module `/lib/modules/2.6.31/kernel/flashid.ko': No such fily
PPPoL2TP kernel driver, V1.0
PPTP driver version 0.8.3
insmod: cannot open module `/lib/modules/2.6.31/kernel/harmony.ko': No such fily
unlzma/peek_old_byte: position 10654951 out of range
unlzma/peek_old_byte: position 45760 out of range
SQUASHFS error: crypto_decompress_update returned -54847, data probably corrupt
SQUASHFS error: squashfs_read_data failed to read block 0x1cea02
SQUASHFS error: Unable to read data cache entry [1cea02]
SQUASHFS error: Unable to read page, block 1cea02, size 9977
SQUASHFS error: Unable to read data cache entry [1cea02]
SQUASHFS error: Unable to read page, block 1cea02, size 9977
SQUASHFS error: Unable to read data cache entry [1cea02]
SQUASHFS error: Unable to read page, block 1cea02, size 9977
SQUASHFS error: crypto_decompress_update returned -48, data probably corrupt
SQUASHFS error: squashfs_read_data failed to read block 0x1d8379
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba
SQUASHFS error: Unable to read data cache entry [1d8379]
SQUASHFS error: Unable to read page, block 1d8379, size 96ba

unlzma/peek_old_byte: position 2227536 out of range
unlzma/peek_old_byte: position 84935041 out of range
SQUASHFS error: crypto_decompress_update returned -142, data probably corrupt
SQUASHFS error: squashfs_read_data failed to read block 0x250e5
SQUASHFS error: Unable to read fragment cache entry [250e5]
SQUASHFS error: Unable to read page, block 250e5, size af92
SQUASHFS error: Unable to read fragment cache entry [250e5]
SQUASHFS error: Unable to read page, block 250e5, size af92
(none) login: root
SQUASHFS error: Unable to read fragment cache entry [250e5]
SQUASHFS error: Unable to read page, block 250e5, size af92
SQUASHFS error: Unable to read fragment cache entry [250e5]
SQUASHFS error: Unable to read page, block 250e5, size af92
Password:
Login incorrect
(none) login:
nebbia88
DD-WRT User


Joined: 08 Mar 2010
Posts: 174

PostPosted: Sun Sep 08, 2013 12:00    Post subject: Reply with quote
can't you stop uboot by typing "tpl" when you see the "Autobooting.." message just after power on?
sanist
DD-WRT Novice


Joined: 02 Oct 2008
Posts: 7

PostPosted: Mon Sep 09, 2013 7:34    Post subject: Reply with quote
thanks for the tip. My problem is fixed.

My issue was that just after reboot, I was getting few lines of garbage on the screen, followed shortly by the log above.

When I typed tpl immediately after reboot, all I could ever see was the garbage, as if the comm settings were wrong. I knew i was in some kind of an interactive mode, but i just could not read anything of what i was typing, or what was being echoed to the tty (i did try changing the comm settings, to no avail).

In the end, i typed the entire tftpboot procedure in the blind at the comm settings specified in the procedure, hoped for the best and ... success.

Thanks to all for the help and the great work in making getting this firmware and the knowledge available.
nebbia88
DD-WRT User


Joined: 08 Mar 2010
Posts: 174

PostPosted: Mon Sep 09, 2013 19:30    Post subject: Reply with quote
wow never seen such a behaviour, uboot outputs garbage on serial but kernel does not??? o.O
Inayan
DD-WRT Novice


Joined: 09 Sep 2013
Posts: 2

PostPosted: Mon Sep 09, 2013 21:26    Post subject: Reply with quote
Hi, i'm newer here. I have tha same problem, today i have upgraded my wr841nd to firmware v8 and bricked him, all leds turns on and off second by second. Can i fix this problem? How to connect serial cable?

Thank you.
Goto page 1, 2  Next Display posts from previous:    Page 1 of 2
Post new topic   Reply to topic    DD-WRT Forum Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum