Posted: Sun Aug 26, 2018 18:02 Post subject: 2018-08: which LAST working version x WR1043ND v1.8 ?
who can tell me which is the LAST, right and perfecly working DD-WRT Version for my TP-LINK TL-WR1043ND v1.8 (S/N:10B674******) ??
and HOW correctly installing it???
I have bricked my WR1043 twice using the file from:
and flashing via original TPlink firmware!!
I have succesfully UNbricked it reinstalling via SERIAL interface and USB/TTL the
"OPENWRT_15.05.1-ar71xx-generic-tl-wr1043nd-v1-squashfs-factory.bin" file and the router now WORKS!
Theoretically, the list would be:
33006, 35681, 35831, 36006, 36079
To clear the bricky error:
Load the webrevert file and load the TP-Link Firmware from March 2014
Load 33006 factory-to-ddwrt.bin and wait 5 minutes
Once at 33006, test hardware for stability.
Other versions mentioned have merit in some way, but may or may not suit your application. Newer versions of firmware have more errors on older hardware that the devs aren't using personally. TPlink factory firmware's update page probably is safer than dd-wrt firmware update page.
Last edited by danielwritesback on Fri Sep 07, 2018 23:08; edited 4 times in total
My first question is do you have a tutorial/how to for updating via telnet or serial?
My second question, which is the more important, do you also have a tutorial or how to of programming the flash-chip with an external programmer for the 1043?Which Programmer did you use?
Could you maybe write an how to? I`m very interested to learn this.
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.
35681 and stuck? You can roll back to stable build 33006, reset, revert to factory firmware, reset and then these are likely to work: 35831, 36006, 36079. This looks very similar to the good list for other Atheros as well.
Last edited by danielwritesback on Mon Sep 03, 2018 7:58; edited 1 time in total
In my case (WR1043ND v1.1),
the final version which can be normally upgraded & downgraded with DD-WRT Web UI, is "09-11-2017-r33345",
since "09-19-2017-r33375" to "06-10-2018-r36104", I can only upgrade it with the TFTP trick & factory-to-ddwrt.bin FW file.
Since "06-16-2018-r36154", the only thing I have after flashing is a boot-loop WRT1043ND v1.
For now, my WR1043ND v1.1 stucks at "06-10-2018-r36104".
BTW, I only use TFTP/Web UI to de-brick WR1043ND, you may try it first, if the bootloader of 1043ND not completely corrupted yet.
(but I guess if the bootloader is really corrupted, even with the TTL cable, it mightn't rescue the completely dead 1043ND)