RSCM has the same router and version and since his "cat /proc/mtd" command gave the same results as mine (mtd7 = fullflash), I assumed my bootloader size was also 131072 as shown below:
> i got 131072 using a hexeditor from a dump of mtd7 (read above @epsilon) (wr1043nd_v1.8 )
I don't understand why it's bricked either since as fizkz pointed out, "nothing was written back to fullflash yet. All the writing was done to files in tmp. Assuming no typos"...there weren't any!
btw in my case i wrote the boot.bin in a linux machine (my desktop) because the router didn't have enough space to handle all the operation
i got the dump and then "scp-it" from the router, used the firmware and cat command on it and then i trasfered it back to the router. that way i could bypass the free space issue
are you sure you don't have response? ping? access via ssh/telnet? have you hard-reset it? there's plenty to test before thinking on serial cables or flash chips
ps:
i did brick my router in the past and saved it, bc of that i have cables and pins attached to the port that way in the future i could connect the serial ttl usb adapter easy
Maybe this is my problem.. I cant finish cat order. Takes several minutes and when push enter then got ampn out connection
My router is tp link
I have a mac but i could virtualize linux or windows on it
For now
- telnet router
- wget firmware factory to ddwrt (why it cant be the normal upgrade firm?)
- dd boot7 as boot.bin
- stuck when cat firmware at boot.bin
Could it be because is out of space?
Could it be because it needs more time (>5 mins?)
How I would manage linux terminal for transfer files with the router?
Could I do with mac terminal?
This is still an issue on the TP-Link TL-WR1043ND v1. Flashed r34311 (12/29/17), can't upgrade via the web interface to r34578 (01/19/18).
As BrainSlayer mentioned, builds before r33375 (09/19/17) used "DD-WRT" as the string at the start of the firmware, and since that build they're all using "TP-LINK Technologies".
This is still an issue on the TP-Link TL-WR1043ND v1. Flashed r34311 (12/29/17), can't upgrade via the web interface to r34578 (01/19/1.
As BrainSlayer mentioned, builds before r33375 (09/19/17) used "DD-WRT" as the string at the start of the firmware, and since that build they're all using "TP-LINK Technologies".
Sorry, I get file "factory-to-ddwrt"+ mtdblock7 for tplink a 8192000bytes file
So i'm ready to do mtd -f write boot.bin fullflash
Two questions before
- Will I loose my personal configuration?
I'm doing a upgrade (stuck at versión greater than 34578 for upgrade to the newest.
- Could I downgrade to a previous 34578 version using the same method?
I’d like downgrade to 7-2-2017 version that works great for me
I think all was mess up but like a miracle it works
TP Link 1043ND 1.8
Telnet
* dd if=/dev/mtdblock7 of=/tmp/boot.bin bs=1 count=131072
* wget http://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2018/01-19-2018-r34578/tplink_tl-wr1043nd/factory-to-ddwrt.bin
* cat factory-to-ddwrt.bin >> boot.bin
* (DEEP BREATH) mtd -f write boot.bin fullflash
Unlocking fullflash ...
Could not unlock MTD device: fullflash
fullflash: Not supported
Writing from boot.bin to fullflash ... [w/e]
GLUP** (Not supported?)(not unlock?) I read this forum and find a user with boot loop
* reboot
Segmentation fault
Segmentation fault
-sh: /tmp/.rc_shutdown: Permission denied
-sh: /sbin/reboot: I/O error
SUPER GLUP**!!
* ls
Segmentation fault
Power off router and pray ... wait ... boot ... leds.... wlan ... led ...URL and got it with 34578 version and old config maintained
And this command is running for 5-10 seconds, router is restarted and both files are not present in /tmp folder
Do I understand that something is wrong and I should not go for the command "mtd -f write boot.bin fullflash" because it simple doesn't exist?
Question is why router is restarting at step E) ?
I think all was mess up but like a miracle it works
TP Link 1043ND 1.8
Telnet
* dd if=/dev/mtdblock7 of=/tmp/boot.bin bs=1 count=131072
* wget http://download1.dd-wrt.com/dd-wrtv2/downloads/betas/2018/01-19-2018-r34578/tplink_tl-wr1043nd/factory-to-ddwrt.bin
* cat factory-to-ddwrt.bin >> boot.bin
* (DEEP BREATH) mtd -f write boot.bin fullflash
Unlocking fullflash ...
Could not unlock MTD device: fullflash
fullflash: Not supported
Writing from boot.bin to fullflash ... [w/e]
GLUP** (Not supported?)(not unlock?) I read this forum and find a user with boot loop
* reboot
Segmentation fault
Segmentation fault
-sh: /tmp/.rc_shutdown: Permission denied
-sh: /sbin/reboot: I/O error
SUPER GLUP**!!
* ls
Segmentation fault
Power off router and pray ... wait ... boot ... leds.... wlan ... led ...URL and got it with 34578 version and old config maintained