Posted: Thu Sep 22, 2022 10:54 Post subject: tl-wr1043n v5.0 via openwrt luci to dd-wrt
Hello,
I flashed the latest beta "factory-to-ddwrt.bin" for the above named tp-link router via Luci on my router.
After restart, I can not connect to it via lan cable. I don't even get a proper IP, only a 169...
Have I done something wrong? Do I need to debrick it now via serial console?
Regards, Dieter
Moderator note 10.20.23: Historical information added here for continuity - kp69
The only success I have seen is with force upgrade box checked and nothing else checked (do not keep settings).
But this was also with a different model router (Marvell), and I do not know the status or behavior on your router.
Good news your router has TFTP recovery.
"Rename OpenWrt or original firmware to WR1043v5_tp_recovery.bin Set static IP of your PC to *192.168.0.66/24*
Router will obtain IP 192.168.0.86 for a few seconds while loading, when reset button pressed at power On."
"Connect the device (one of the LAN ports) to a host computer via an ethernet cable
Change the host computer IP address (manual or static) to 192.168.0.66
Install a tftp server. This is host computer OS specific.
On Mac OS X, you can start the built-in tftp server with $ sudo launchctl load -w /System/Library/LaunchDaemons/tftp.plist
Download a desired firmware (openwrt *factory.bin or the original firmware wr1043nv1_*_boot*.bin) and rename the *.bin file to wr1043nv1_tp_recovery.bin in the tftpboot directory (if you use Tftpd check log viewer for read request from your router, to make sure your rename is correct. It's good to mention here that if you use tftpd64 on Windows 11 it's possible that the log viewer may be empty. The log viewer was empty in my case under Windows 11, so probably the tftpd64 author should update his program). The v4 file needs to be named wr1043ndv4_tp_recovery.bin.
On Mac OS X, copy the renamed file to /private/tftpboot/
Use a pin or paper clip to press down the reset button (in the hole besides the power adapter hole) and connect the power, while holding down the reset button for a few seconds
The LEDs should flash indicating firmware upload in progress.
The device will automatically boot to use the new firmware after flashing."
Check use anticipation window of 1024 bytes to speed up transfer in TFTP settings.
May also want to check the box Bind TFTP to this address 192.168.0.66 also YMMV.
This is because the dropdown option for Server Interfaces resets at every attempt.
Joined: 08 May 2018 Posts: 14209 Location: Texas, USA
Posted: Thu Sep 22, 2022 15:44 Post subject:
You can't flash the TL-WR1043N v5 from stock firmware or OpenWRT by any method, whatsoever. You also cannot TFTP flash DD-WRT to this router. I still have not revisited a possible way via serial / u-boot yet because I didn't jumper the one serial lead and have to hold it to the PCB which makes things tedious.
I don't even recall what the command was that I was hinted towards a few months ago, but believe me, I have tried *every* known way to flash this router with no success yet. Recovery to stock or OpenWRT firmware via TFTP does work per the instructions @blkt posted above. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
thank you very much for your support! I knew, that flashing from stock won't work from the forum, therefore I thought I try it this way. There are several post online, how to flash directly from openwrt to dd-wrt. Did not know, that they are all nonsense.
In the end, I have to acknowledge that there is no feasible way, even though there is a beta.
Strange but ok.
Joined: 08 May 2018 Posts: 14209 Location: Texas, USA
Posted: Thu Sep 22, 2022 16:27 Post subject:
zappel wrote:
Hello,
thank you very much for your support! I knew, that flashing from stock won't work from the forum, therefore I thought I try it this way. There are several post online, how to flash directly from openwrt to dd-wrt. Did not know, that they are all nonsense.
In the end, I have to acknowledge that there is no feasible way, even though there is a beta.
Strange but ok.
Regards, Dieter
I bricked mine trying every method from this forum and the internet that you mention, if I remember correctly. My notes are elsewhere at the moment, and I'd rather refer to them for details than "speak in err". I've had several discussions with BrainSlayer, one more recently that I still need to follow-up on. Noted "renewed interest" by the community in flashing this router, check. I'm surprised these are still available...
Not new information that hasn't already been discussed or submitted, but thank you for looking. BrainSlayer said to flash this, you have to use "firmware recovery", and I am guessing via u-boot serial. I don't think there is a web interface recovery method similar to Asus. Last commit to the tp-link safeloader code in DD-WRT was 20 months ago and I have tried more recent versions to no avail.
Joined: 16 Nov 2015 Posts: 6435 Location: UK, London, just across the river..
Posted: Thu Sep 22, 2022 16:28 Post subject:
yep v5 is dodge there was only one build that was working with it ages ago,
and than therefore none of the builds ware ok...i tried to sort it for a friend and
it was a nightmare..he ended using OpenWRT instead but unit died for some reason..
no idea was it software or hardware related anyway..
https://svn.dd-wrt.com/ticket/6300 more on the issue..KP-69 stuff... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 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 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55779 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 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: 08 May 2018 Posts: 14209 Location: Texas, USA
Posted: Thu Sep 22, 2022 16:38 Post subject:
Alozaros wrote:
yep v5 is dodge there was only one build that was working with it ages ago,
and than therefore none of the builds ware ok...i tried to sort it for a friend and
it was a nightmare..he ended using OpenWRT instead but unit died for some reason..
no idea was it software or hardware related anyway..
I've tried every file from the initial public beta forward. If you're going to say there was a good build, link it, please. Otherwise, it's "hearsay" and "misinformation", because I never came across this information searching this forum with a fine-toothed comb. And most of what I looked at in that ticket was bogus after the fact.
@blkt: there is a post that may still be in the moderator's forum that I moved there with some information that is still on my old laptop that is currently taking a break. It was from a commit on OpenWRT that I stumbled across, but never followed up on. _________________ "Life is but a fleeting moment, a vapor that vanishes quickly; All is vanity"
Contribute To DD-WRT Pogo - A minimal level of ability is expected and needed... DD-WRT Releases 2023 (PolitePol)
DD-WRT Releases 2023 (RSS Everything)
----------------------
Linux User #377467 counter.li.org / linuxcounter.net
Joined: 16 Nov 2015 Posts: 6435 Location: UK, London, just across the river..
Posted: Thu Sep 22, 2022 16:56 Post subject:
i tried to find some clues and i couldn't find my communication with my friend but, it was somewhere begging slash summer of 2018, must have been some of the first builds for it...
if i recall correctly, but im not entirely sure (as it could be somewhere else) there was also a thread in DDWRT with a bloke complaining with the same issue, first flash was ok..
but no flashible builds after...
no idea what would be the very first stock firmware if this adds to the case...
i also did try few builds and it was bootlooping than tried back to stock TFTP, it worked than tried OpenWRT and it was the one that stayed as nothing was flashible after...same case as i can recall...
dodge router is v5 although it seemed with a touch of a better specs...
no idea y BS posted a builds and keeps posting for this unit, as those are not working at all...
p.s. i could be a also wrong, as it could be the v4 that was, not v5 or something like... lots of water since than and my alz is kicking this days ...
The important bit is, if BS will look at it and sort the issues, as im interested of this unit as this sales atm...
so far my 1043v2 is rock solid (thanks 2 BS)... _________________ Atheros
TP-Link WR740Nv1 ---DD-WRT 55630 WAP
TP-Link WR1043NDv2 -DD-WRT 55723 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 55779 Gateway/DoH,Forced DNS,AP Isolation,4VLAN,Ad-Block,Firewall,Vanilla
Netgear R7800 --DD-WRT 55779 Gateway/DoT,AD-Block,Forced DNS,AP&Net Isolation,x3VLAN,Firewall,Vanilla
Netgear R9000 --DD-WRT 55779 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
sorry, that I started a new one.
I had the impression, that the old ones were mainly dealing with the issue, that the firmware won't flash, and I thought by mistake, a had a work around using OpenWRT.
Why did I want to try DD-WRT in the first place? Well, I have an issue with this router for my radio streaming devices. Some Logitech Squeezeboxes and a Lenovo Google device. While streaming radio, and only then, the connection gets stalled every now and then. I could track it down to the router. With another tp-link router, different type, using OpenWRT, this does not occure.
Everything else seems to work with my WR1043N.
I thought, I could give DD-WRT a try to fix it.