TL-WR2543ND losing config after reboot on LEDE 17.01.4

Installing and Using OpenWrt
1

I'm trying to install LEDE on my WR2543ND and everything looks ok, except that I lose all my configuration after rebooting or turning off/on my router.

This is my result when running df -h:

Filesystem                     Size       Used Available Use% Mounted on
/dev/root                       2.3M        2.3M             0  100% /rom
tmpfs                           29.6M    528.0K     29.1M      2% /tmp
tmpfs                           29.6M      56.0K     29.6M      0% /tmp/root
overlayfs:/tmp/root      29.6M      56.0K     29.6M      0% /
tmpfs                         512.0K             0    512.0K      0% /dev
/dev/mtdblock3             4.4M       4.4M             0  100% /rom/overlay
2

Looks like your rootfs is only in ram...
Did you flash a image with initram in the name?

For persistence you should flash sysupgrade image with sysupgrade tool or luci or a factory image with webgui of tplink firmware or tftp recovery from uboot.

3

I trying to flash the factory image from here.
I tried a older OpenWRT version too but my LuCi was too slow when using this other image

I flashed via TP-Link webgui on both cases (I reflashed original firmware before try 17.1).

4

Tried to flash 17.1 sysupgrade image after 15 factory and now i got this:

root@LEDE:~# df -h
Filesystem Size Used Available Use% Mounted on
/dev/root 2.3M 2.3M 0 100% /rom
tmpfs 29.6M 536.0K 29.1M 2% /tmp
tmpfs 29.6M 48.0K 29.6M 0% /tmp/root
tmpfs 512.0K 0 512.0K 0% /dev
/dev/mtdblock3 4.4M 1.3M 3.1M 29% /overlay
overlayfs:/overlay 4.4M 1.3M 3.1M 29% /

Still losing configuration after reboot.

5

You now have a 4.4 MB large overlay(fs backed by jffs2) on /dev/mtd3, that appears to be fine. Please invoke "firstboot" (which resets/ deletes your configuration again) and reboot one more time, give your router ~5 minutes after the reboot to actually finish its business (generating ssh/ ssl keys, formatting the jffs2 partition) before trying to log in or to configure it, I see no reason why it wouldn't work with a persistent configuration then (if not, please look into "dmesg" and "logread" for clues).