Wdr4300 dd wrt
Dd-wrt new beta firmware upgrade-downgrade procedure
My TP-Link WDR 4300 wireless router was bricked after a software update went wrong. It was left unused for a long time, with the assumption that it had died due to a hardware failure and that it could not be revived. Finally, I was able to devote some time to it and try to recover or salvage it… Continue reading How to de-brick, unbrick, or restore your TP-Link WDR-4300 wireless router
If you’re having trouble accessing the TP Connection WDR4300 router’s LUCI OpenWRT page, try the steps below. Set the PC’s IP address to 192.168.1.2, the subnetmask to 255.255.255.0, and the gateway to 192.168.1.1. Switch the router off. Remove the WAN cable. Link your PC Ethernet cable only to the ETH0 Power socket. On your router, Wait for the router to begin… Continue to read How to Reset the TP Connection WDR4300 Router After a Bad OpenWRT LEDE Install
On the TP Connection WDR4300 router, I installed the Chaos Calmer OpenWRT firmware update. It’s important to remember that if you already have OpenWRT installed on your router, you can install the sysupgrade firmware file rather than the factory binary firmware file. When upgrading from the factory TP Connection firmware, just use factory. Using this file to install for the first time… Continue reading After upgrading OpenWRT from barrier-breaker to chaos-calmer, I’m unable to log into the LuCi web interface.
Since I’ve tried deleting the bootloader from the original firmware, but it doesn’t help. Until now, I’ve reconnected every router via TFPT, regardless of whether it had a bootloader or not.
All is very speculative here, Jupp. The TS should definitely keep a log. Alternatively, try an ssh sysupgrade of one of the other sysupgrade-openwrt-images and see what comes up as an error message.
If the correct Stock FW is incorrectly identified via TFTP, there will be an entry in the TFT Server Log (alternatively, with Wirehshark/TCPDump) indicating the intended Dateiname.
If you can’t get wireless to work by using big channel modes, it’s possible that the friendly neighbor “feature” is preventing you from doing so, and you’ll have to switch to regular modes to get wireless to work.
(If a serial console is available, it’s a good idea to do dry runs by ad-hoc RAM booting a factory prior to actual flashing.)
bin from a TFTP host server, served by WDR3600’s default 6F01A8C0.img filename via uboot “tftp” + “bootm”).
Switch on your router. As the ‘SYS’ light (asterisk symbol to the right of the power light) begins to blink, quickly press the WPS/Reset button on the router’s back-left for a few seconds (>1 sec). The ‘SYS’ light should now begin to flash rapidly.
The above instructions did not work well on a TL-WDR4300 Ver 1.6 with Barrier Breaker Bleeding Edge, r39211. The only way I could get the router into failsafe mode was to click the WPS/Reset button quickly and repeatedly until the front panel “star” LED started blinking. When that LED eventually turned on, it seemed to go straight to the “failsafe” indicator, which blinked rapidly. If the WPS LED lights up (rightmost, “yin-yang arrows”), you might have pressed the button too soon during the boot sequence.
I’m currently using DD-WRT v24-sp2 (03/25/13) std – build 21061, which is the system database’s recommended version. However, I read that in 2013, someone upgraded to build 21286. Is it safe to say that the device database is actually outdated and that a newer version is available? This appears to be the most recent router build, but I’m not sure if it’s stable. I’d like to upgrade because sshd won’t start, and upgrading is the recommended solution. There are 15 comments. 84 percent sharesavehidereport Voted up This discussion has been ended. There are no new comments or votes that can be made. Sort by the strongest.