I've just updated to 36104 and it works ok on TL-WR1043ND v.1.8. I do not recommend to join boot.bin and factory-to-ddwrt.bin on the router, it is safer to download boot.bin on PC, join it with factory-to-ddwrt.bin there, and upload resulting fullflash.bin back to the router. Once I've run out of RAM on router when trying to join these files directly on router.
Router Name: DD-WRT
Router Model: TP-Link TL-WR1043ND
Firmware Version: DD-WRT v3.0-r36104 std (06/10/18)
Kernel Version: Linux 3.10.108-d2 #57802 Sun Jun 10 04:02:03 CEST 2018 mips
Joined: 14 Oct 2016 Posts: 78 Location: United States
Posted: Sun Sep 30, 2018 2:20 Post subject:
Hmm... I'm currently on DD-WRT build 33607... which was released back in October 2017. If I were to update to the last working build... say 36006 or 36079... I would have to update it via another way instead of the web-update?
Probably not much but always want to keep my devices up to date.
A feasible update may arrive soon, at this locale: https://www.gargoyle-router.com/phpbb/viewtopic.php?f=14&t=11743
I tested it with my unstable archer, which was then stabilized and could browse the web at a quicker pace. The openwrt wifi was weaker than DD-WRT, but you can find the noscan option and fit larger 9dbi antennas, if needed. Anyway, there was the update news.
You have to get your original boot.bin (2 * 64kB) - but you need to download it only once and store in a safe place
1. Start SSHd on your router (Services -> Secure Shell -> SSHd -> Enable -> Save -> Reboot Router)
2. Connect to router via SSH Client, eg. PuTTY, default IP is 192.168.1.1 port 22
3. Log in (login and password like for www panel)
4. Verify partition layout: cat /proc/mtd
5. In the output find line ending with "fullflash"
6. if it looks like this: mtd7: 00800000 00010000 "fullflash"
... save boot.bin using following command: dd if=/dev/mtdblock7 of=/tmp/boot.bin bs=1 count=131072
7. Connect the router with WinSCP, if you have saved a session profile prior to connecting with PuTTY you may use this, use SCP protocol
8. You start at /tmp/root, so go one level up (..) to /tmp
9. Copy boot.bin to local file system, then you may delete it from router (it will disappear after reboot anyways)
When you have your boot.bin on your computer:
copy /b boot.bin+factory-to-ddwrt.bin fullflash.bin
mtd -f write fullflash.bin fullflash
I find this solution more reliable... serial port is 3.3V TTL, running at 115200bps. Header P1 pinout is:
1 - TxD (to Rx in converter)
2 - RxD (to Tx in converter)
3 - GND (to GND in converter)
4 - +5V (leave unconnected)
Pin 1 is marked (having the ports towards you it is the rightmost pin of the serial header, opposite the header marking P1).
On the PC you have to set a static IPv4 192.168.0.5/255.255.255.0 and start a TFTP server. On the server you have to have a firmware file, factory-to-ddwrt.bin (not a webupgrade one!!!).
This part is tricky, copy a text 'tpl' (without quotes to the clipboard, open a connection in a serial console (eg. PuTTY), turn on router and immediately start pasting the 'tpl' string (cliking right mouse button does the paste, not usual ctrl+v). You should get the 'ar7100>' prompt. Then you do:
After first command, please verify the offset (+7b0000). If it is different - STOP THERE!!!
Via the console you don't need to flash BOOT area. However if you want to, you can. To do a full flash (which is not full actually) you may use the fullflash.bin prepared as like for telnet/ssh upgrade.
After first command, please verify the offset (+7d0000). If it is different - STOP THERE!!!
Never ever erase/flash anything above the 0xbf7e0000 boundary!!!
Last - for the external programmer... well you have to to have a good image of the whole 8MB Flash, preferably save the 0x7e0000 - 0x7fffff area from the original flash, and append it to the fullflash.bin (prepared as before). I was using the TL-866A with the appropriate adapter.
for my v.1.0, and according to OPEN-WRT, to flash stripped firmware (=without boot), such as "factory-to-ddwrt.bin" it should be: 7c0000 and not 7b0000, but I suppose it depends on the size of the firmware image? (but ok, one can verify whether it matches after the write, that's how I learned that a non-stripped image does not fit 7c0000, so for non-stripped = fullflash it should be 7d0000)
For v1.x hardware:
tftpboot 0x81000000 firmware.bin
erase 0xbf020000 +7c0000 # 7c0000: size of the firmware (be aware that you may have a different size thus bricking your router)
cp.b 0x81000000 0xbf020000 0x7c0000