Hello,

I have a "tl-wr941nd v5" router with a "LuCI" interface (OpenWrt | OpenWrt Attitude Adjustment 12.09 | Load: 0.11 0.15 0.06).

I need to return it back to its original firmware, but when I attempt to load it, I get this message:

"The uploaded image file does not contain a supported format. Make sure that you choose the generic image format for your platform."

I have tried the following firmwares:
- wr941nv3_en_3_13_9_up(120201).bin
- wr941ndv5_en_3_13_31_up_boot(130105).bin
- wr941ndv5_en_3_14_5_up_boot(130709).bin
- wr941ndv5_webrevert.bin

In addition, I tried resetting it to factory settings by using the button located on the back, but it did not work, as it did not restart.

If anyone can assist, I would greatly appreciate it.

Thank you

Check the wiki for more information, http://wiki.openwrt.org/toh/tp-link/tl- … l.firmware

thanks

I've done what http://wiki.openwrt.org/toh/tp-link/tl- … l.firmware says (using firmware wr941ndv5_en_3_14_5_up_boot(130709).bin ), but now only the power light turns on. have I turned it into brick?

report precisely every operation and command you did.

did you save a log/screenshot of the terminal window?

(Last edited by nebbia88 on 11 Dec 2013, 07:00)

I didn't capture screenshots and I don't have the logs

I execute the following commands:

cd /tmp/
dd if=wr941ndv5_en_3_14_5_up_boot(130709).bin of=tplink_boot.bin skip=257 bs=512
mtd -r write tplink_boot.bin firmware

Then it started to write and reboot.

In addition, I tried resetting it to factory settings by using the button located on the back, but it did not work, as it did not restart.

you should have found a genuine tp-link firmware file with out the _boot in the filename and verified it doesn't need to be stripped and just wrote it out to the firmware partition. Then from there if you wanted a newer bootloader then let tp-link upgrade it for you with the factory firmware. If your newest firmware isn't a _boot and you wanted the bootloader upgrade then find an older factory firmware before the bootloader.

Another idea is ERASE the region that the firmware is going into being mindful not to erase your art partition. Erasing the whole firmware mtd partition is everything but the art and the bootloader usually. Why? The config partition is also used by tp-link and it should be zero-ed out before the factory firmware first boots.

For future people about to make this cock up
~ $ dd if=routerbackup.bin bs=4 count=1 skip=37 2>/dev/null | hexdump -v -n 4 -e '1/1 "%02x"'
00000000
(a 4mb entire eeprom backup)
~ $ dd if=kernel.img bs=4 count=1 skip=37 2>/dev/null | hexdump -v -n 4 -e '1/1 "%02x"'
00000000
( a tp-link factory firmware kernel image )

Bugger that was mean't to be non-zero for the first one. I thought we had a new way of checking if firmware file was stripped or not. It should return someting different if the file name from tp-link has a _boot in it.