unbrick tp-link 1043 rev.1 with gargoyle (openwrt)
1) recovery mode launch
- turn off the router
- change pc ip on 192.168.1.2
- turn on the router and check SYS led: as soon as it blinks first time - press and hold RESET
- SYS should blink frequently, if so - release reset
2) flashing
- download gargoyle sysupgrade firmware (example gargoyle_1.8.1-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin)
- ssh to router (192.168.1.1) and write
mount_root
/etc/init.d/dropbear start
passwd
- download winscp
- "Session" tab
host name = 192.168.1.1
port number = 22
user name = root
password = *password* from passwd
- copy sysupgrade.bin into the /tmp
- return to ssh now and write:
cd /tmp
mtd -e firmware -r write gargoyle_1.8.1-ar71xx-generic-tl-wr1043nd-v1-squashfs-sysupgrade.bin firmware
- do not restart or turn off the router! the router should reboot itself!
I'd like to be able to help you further. But I can only point you towards information that will allow you to help yourself.
It would be useful to know if both error reports are from the same model.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
448 wrote:unbrick tp-link 1043 rev.1 with gargoyle (openwrt)
1) recovery mode launch
- turn off the router
- change pc ip on 192.168.1.2
- turn on the router and check SYS led: as soon as it blinks first time - press and hold RESET
- SYS should blink frequently, if so - release reset
yeah,... as mentioned before: cannot do that when the darn sys-led is not lighting up
@lantis: yup, tried to preserve settings, dunno about the second brick.. but he has a 1043nd as well.
Mine is v1.
And from what version did you preserve settings?
That could be an issue.
My other suggestion wiuld be to turn it on and leave it overnight. I've seen a few tp link routers bring themselves back to life. That's a long shot though.
https://lantisproject.com/downloads/gargoylebuilds for the latest releases
Please be respectful when posting. I do this in my free time on a volunteer basis.
opkg install kmod-brcm-wl
ERROR: Dependency kernel (= 3.18.23-1-e64d63d489e72db2672ccd5f283d3169) of package kmod-brcm-wl is installed,
but has incompatible version 3.18.29-1-4bdaa2a592ba64d14ad62e705c8065e1 and is marked as 'hold'