How do I check and confirm my exact boot size ?
I have a TP-Link 1043ND v1.x (i don't rememeber if it's 1.1/1.2/1.3/1.4)
Can anyone please post a step by step how-to ? Just the determining the boot size, everything else I got it (or at least i think so...)
Hi,
as many of you, my router (1043ND) is stuck on older fw and can't be upgraded the usual way. So, I have tried flashing directly through RS232 and TFTP and I managed to get newer version working (36006). But any newer than that and my router gets stuck on boot everytime:
[ 1.070000] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,2)
I'm not sure how to get past this... Is it possible that I have an old u-boot version or something?
These are the commands I use to flash fw:
Or should I flash a bigger range? I'm clueless at this point and would really appreciate any help.
Full log:
Code:
U-Boot 1.1.4 (Apr 28 2011 - 15:55:09)
AP83 (ar9100) U-boot 0.0.11
DRAM:
sri
32 MB
d read 0x100000ff
flash size 8MB, sector count = 128
Flash: 8 MB
sing default environment
n: serial
Out: serial
Err: serial
et: ag7100_enet_initialize...
o valid address in Flash. Using fixed address
cfg1 0xf cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
eth0 up
eth0
Autobooting in 1 seconds# Booting image at bf020000 ...
Uncompressing Kernel Image ... OK
Joined: 16 Nov 2015 Posts: 6410 Location: UK, London, just across the river..
Posted: Sun Jul 15, 2018 16:36 Post subject:
BrainSlayer wrote:
in older firmwares the string isnt tp-link but dd-wrt. i changed that string to tp-link in that firmware and this all caused the bug since my mtd partition code was looking for the wrong string to detect the bootloader size
and i can see yours is dd-wrt
just read the first page ..first!! _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Posted: Sun Jul 15, 2018 20:17 Post subject: Re: My 1043ND v1.9 is unbricked now!
rafalB wrote:
I was pretty sure I have had bricked my router. But it was interesting for me that leds were blinking differently when I powered on the router with reset button pressed. I thought that maybe router is alive waiting for firmware. Then I have found this article: https://www.trishtech.com/2015/06/unbrick-tplink-wr740n-wifi-router/
... and following it I was able to unbrick my router TFTPed original latest stock TP-Link firmware downloaded from https://www.tp-link.com/us/download/TL-WR1043ND_V1.html#Firmware renamed to wr1043nv1_tp_recovery.bin
Afterwords I have flashed latest DD-WRT r35034 released on 17.02.2018 (DD.MM.YYYY )
You sir are a GOD ! you just saved me, i was sure my 1043ND v1 was toast, but it's ALIVE !!!
I've tried to flash it to the latest DD-WRT and failed, the router went back to boot-loop so I took your advise and upgraded to r35034 and it's working great !
So - there is no chance to upgrade from r35034 once again ???
This upgrading problem still persists. I have WR1043ND v1.8 router and I am stuck at r36006. I tried all of the OP's methods and problem continues. Router flashes the firmware and it stucks in a bootloop with an error of unable to mount root fs on unknown-block (31,2). I do not believe this is a bootblock name thing. Because i flashed the router with the breed bootloader. The OP's suggestions where you preserve the boot sector then flashing it to the router is bypassed via this breed recovery method. I managed flashing r36006 but after that all the releases gave me the error of kernel panic: unable to mount root fs on unknown block (31,2). No need of mentioning that i tried upgrading from the WEB GUI and failed(It uploads the fw then reboots but no change). I also flashed webrevert image to the router. It reverted. Then factory to ddwrt image also gave me the same error. Any actual solutions?
Joined: 16 Nov 2015 Posts: 6410 Location: UK, London, just across the river..
Posted: Sat Oct 20, 2018 15:37 Post subject:
solution 1 - cut the struggle and buy a new router...
solution 2 stay on this build
solution 3 check those new builds may have been oversized
witch is very likely
solution 4 as this router has a very bad flash chip it may be dead and you are stuck to this build... change the chip with either the same or compatible one _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Joined: 16 Nov 2015 Posts: 6410 Location: UK, London, just across the river..
Posted: Mon Nov 05, 2018 8:27 Post subject:
Mtkr125 wrote:
I get connected by Rs232 But it does not show letters but symbols, which can be
this means either bad connection or router is dead...
make sure Tx is connected to Rx and that you use the proper voltage, mostly is used 3.3v and speed, bits, error settings are correct _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
The router I have is a Tp Link 941ND Ver3.6. Now I buy an RS232 TTL usb cable and now if I can see the characters correctly, but I still can not stop the automatic restart, I can not enter "TPL" from the terminal.
Posted: Mon Dec 03, 2018 15:23 Post subject: WR941ND v3
I don't know if anyone can help me with this. I've tried the procedure described on the firsts posts, but now when I turn the router on (wr941nd v3) all lights up, none blinking, and nothing else happens. I'd tried serial cable connection, but I only got a 0x000 as a response from the router, nothing else. Any advice?
Thnx in advance.
Joined: 16 Nov 2015 Posts: 6410 Location: UK, London, just across the river..
Posted: Tue Dec 04, 2018 11:42 Post subject:
this thread is regarding problems only with that build,
if you did't read all the thread and too some actions
that are not on the subject very likely to have problems now...
did you identify the boot size first, ware you sure those steps are correct and regarding your router as well???
to unbrick your router if its not dead look in youtube or ggl it if you don't have any outputs from your serial that means router is dead... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55179 WAP
TP-Link WR1043NDv2 -DD-WRT 55303 Gateway/DoT,Forced DNS,Ad-Block,Firewall,x4VLAN,VPN
TP-Link WR1043NDv2 -Gargoyle OS 1.15.x AP,DNS,QoS,Quotas
Qualcomm-Atheros
Netgear XR500 --DD-WRT 55460 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55460 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55363 Gateway/DoT,AD-Block,AP Isolation,Firewall,Forced DNS,x2VLAN,Vanilla
Broadcom
Netgear R7000 --DD-WRT 55460 Gateway/SmartDNS/DoH,AD-Block,Firewall,Forced DNS,x3VLAN,VPN
NOT USING 5Ghz ANYWHERE
------------------------------------------------------
Stubby DNS over TLS I DNSCrypt v2 by mac913
Joined: 15 Jan 2012 Posts: 12 Location: Kiev, Ukraine
Posted: Mon Dec 24, 2018 20:17 Post subject:
mich3lin wrote:
Hi,
as many of you, my router (1043ND) is stuck on older fw and can't be upgraded the usual way. So, I have tried flashing directly through RS232 and TFTP and I managed to get newer version working (36006).
Same here, except latest working build for my 1043nd v1 is 36104. I flashed several newer builds (36154, 36168, 36247, 36527, 37305, 37932, 37961, 38060) via serial and tftpd, got bootloop on all of them. If I recover to stock tplink firmware via serial+tfttpd, and then flash factory-to-ddwrt.bin newer than 36104 via webgui - same bootloop. Someone probably shoud remove those newer builds from ddwrt router database page for this particuar router. I also have asus rt-n16 upgraded from older ddwrt build to 38060 via webgui, working ok.
Hi,
as many of you, my router (1043ND) is stuck on older fw and can't be upgraded the usual way. So, I have tried flashing directly through RS232 and TFTP and I managed to get newer version working (36006).
Same here, except latest working build for my 1043nd v1 is 36104. I flashed several newer builds (36154, 36168, 36247, 36527, 37305, 37932, 37961, 38060) via serial and tftpd, got bootloop on all of them. If I recover to stock tplink firmware via serial+tfttpd, and then flash factory-to-ddwrt.bin newer than 36104 via webgui - same bootloop. Someone probably shoud remove those newer builds from ddwrt router database page for this particuar router. I also have asus rt-n16 upgraded from older ddwrt build to 38060 via webgui, working ok.
i can confirm same problem with tp-wr1043nd v1.1
anyone confirm installing a build later than 36006?