TP-LINK WR1043ND v1.8 failed update to 1.14

[baniakjr]

Hi,

I've got update problem with TP-LINK WR1043ND v1.8
Router had previously installed Gargoyle (not really sure about version, probably 1.12) it was not used for about 2 years. After powering on it was working fine, but I decided to upgrade firmeware and that's were everything when sour.
I performed update through GUI, with sysupgrade image from this site, version 1.14 (gargoyle_1.14.0-ath79-generic-tplink_tl-wr1043nd-v1-squashfs-sysupgrade.bin). Router restarted and never fully came back. No wifi, no cable connection, sys Led flashing

Code: Select all

Power -> on
all -> flash
Sys -> flashing few times
all -> flash
sys -> flashing constantly slowly

After sometime I managed to power it in failsafe mode. Had to wait after second all Led flash and then press restart button.

Code: Select all

Power -> on
all -> flash
Sys -> flashing few times
all -> flash
reset -> press
sys -> flashing constantly fast

When in fail safe mode I'm able to set my ip statically to 192.168.1.* connect by Ethernet cable and then login by putty (ssh)

Code: Select all

BusyBox v1.35.0 (2023-04-27 20:28:15 UTC) built-in shell (ash)

------------------------------------------------------------------
|            _____                             _                 |
|           |  __ \                           | |                |
|           | |  \/ __ _ _ __ __ _  ___  _   _| | ___            |
|           | | __ / _` | '__/ _` |/ _ \| | | | |/ _ \           |
|           | |_\ \ (_| | | | (_| | (_) | |_| | |  __/           |
|            \____/\__,_|_|  \__, |\___/ \__, |_|\___|           |
|                             __/ |       __/ |                  |
|                            |___/       |___/                   |
|                                                                |
|----------------------------------------------------------------|
| Gargoyle version 1.14.0   | OpenWrt 22.03 branch               |
| Gargoyle revision 97d7a844| OpenWrt commit 863f769             |
| Built May 19, 2023        | Target  ath79/default              |
------------------------------------------------------------------
================= FAILSAFE MODE active ================
special commands:
* firstboot          reset settings to factory defaults
* mount_root     mount root-partition with config files

after mount_root:
* passwd                         change root's password
* /etc/config               directory with config files

for more help see:
https  ://openwrt  .org/docs/guide-user/troubleshooting/
- failsafe_and_factory_reset
- root_password_reset
=======================================================

root@(none):~#

root@(none):~# logread
Failed to connect to ubus

root@(none):/etc/config# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 6144      6144         0 100% /
tmpfs                      512         0       512   0% /dev
tmpfs                    12920        28     12892   0% /tmp

root@(none):~# mount_root
loading kmods from internal overlay
overlay filesystem has not been fully initialized yet
switching to jffs2 overlay

root@(none):/rom/root# df
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/root                 6144      6144         0 100% /rom
tmpfs                      512         0       512   0% /dev
tmpfs                    12920        28     12892   0% /tmp
/dev/mtdblock4             512       272       240  53% /overlay
overlayfs:/overlay         512       272       240  53% /

root@(none):/rom/root# firstboot
This will erase all settings and remove any installed packages. Are you sure? [N/y]
y
/dev/mtdblock4 is mounted as /overlay, only erasing files

after that nothing changes

I tried uploading new firmware with tftpd64 but to no avail.
I changed my ip to 192.168.1.66 set up tftpd64
Prepared 2 files (because I found to different info's on how should i name image, renamed from gargoyle_1.14.0-ath79-generic-tplink_tl-wr1043nd-v1-squashfs-factory.bin):
wr1043ndv1_tp_recovery.bin
wr1043nv1_tp_recovery.bin

Tried restarting router, restarting into failsafe mode and never got any response, tftpd never showed anything in logs.

Now to my actual question What to do? Is there anything i should try in failsafe mode, it seems like internal storage is fully? Should I try further with tftpd and am I missing something?

Now that I think about it, router had previously connected usb drive and there was some swap partition I think. However before upgrade it was working fine without it. I don't have the drive any more.

[Lantis]

Load an earlier version, or try a 1.15 beta build https://lantisproject.com/gargoyle_cust ... lds/ath79/

In reality, your device is now at the edge of no longer having enough storage to get newer versions.

[baniakjr]

Thanks for quick answer. I would gladly downgrade to 1.13 o 1.12 or even try beta 1.15 but at the moment don't really know how.

I'm only able to boot it in failsafe mode and haven't got any luck with tftpd.

Is there a way to do it through ssh and command line?

Or is any one able to help me with tftpd. I followed some tutorials on that, but all of them showed it as almost automatic process and there were some differences like filename, how and when to reset router and so on.

What i already tried is:

• set ip to: 192.168.1.66 (then i'm able to connect through ssh)
• renamed bin files and pointed tftpd to them (tried 2 different names)
• while tftpd was running restarted router (switching power on/off). Tried also with failsafe mode by pressing restart button after second all led flash.

and nothing really happens. All instruction I've seen mentions wps button, which my router don't have, there qss one and reset button on back.

[Lantis]

If you are able to get it into a fail safe mode and ssh in, then you should be able to use SCP to move a sysupgrade file into /tmp and run the sysupgrade from there.

For tftp, your ip should be 192.168.0.66, not .1.66
Try that and hopefully more success

[baniakjr]

Thanks, I feel silly now I was so fixated on fact that it's not booting properly that I didn't realize I can run sysupgrade from failsafe mode.

Tried with 1.14 but had same result, after that I downgraded to 1.12 and it works properly now. Thanks!