please tell me how you did it
i tried to connect via uart, but I could connect via uart.
only wrong characters appear
I have found a way to install OpenWrt on the ER605 v2 without using a serial console. 
You can see the GitHub repo I have made.
6 Likes
To gain SSH on newer firmwares, SSH to the router as before, and then run two commands in the CLI shell: first, run enable, then run debug. The CLI shell will ask you for a password. The password is the same root password used to SSH into the router.
2 Likes
Hi, after flashing the firmware in recovery mode,
When I try to connect with ssh it times out and I can't continue.
No lights other than the power LED.
Could you lend me your strength to overcome this situation?
Which firmware did you flash?
It was the oldest one that can be downloaded on the TP link site, so I believe it is "ER605(UN)_V2_2.0.1 Build 20220223"
Now that I think about it, maybe I should have matched the version written in model.json...
If I have time, I will open ER605 and try uart.
having issue:
cd recovery_image; qemu-mipsel -L ../download/mipsel-linux-muslsf-native ../download/er605v2_gpl/staging_dir/host/bin/dkmgt_firmware_make -b -m model.json; rm ER605v2_flash.bin; mv ER605v2_up.bin er605v2_openwrt_recovery.bin; mv er605v2_openwrt_recovery.bin ../
/bin/sh: 1: qemu-mipsel: not found
rm: cannot remove 'ER605v2_*_flash.bin': No such file or directory
mv: cannot stat 'ER605v2_*_up.bin': No such file or directory
mv: cannot stat 'er605v2_openwrt_recovery.bin': No such file or directory
make: *** [Makefile:10: er605v2_openwrt_recovery.bin] Error 1
The required QEMU user mode emulation binary is not installed (qemu-mipsel). You need to install it. For Ubuntu, run apt install qemu-user.
thx, got the recovery .bin.
proceedd up to step 8, rbut no ssh access
router ports not working, only port 5 working and without ssh access.
uart access available, any help much appreciated
ER605 login: root
Password:
BusyBox v1.22.1 (2022-02-23 18:52:50 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -| || | | || || |
|_____|| |||||___||| |____|
|| W I R E L E S S F R E E D O M
BARRIER BREAKER (Barrier Breaker, unknown)
- 1/2 oz Galliano Pour all ingredients into
- 4 oz cold Coffee an irish coffee mug filled
- 1 1/2 oz Dark Rum with crushed ice. Stir.
- 2 tsp. Creme de Cacao
root@ER605:~#
root@ER605:~# cd /etc
root@ER605:/etc#
root@ER605:/etc# ls
.[1;36mTZ.[0m .[1;34miproute2.[0m .[1;34mrc.d.[0m
.[1;32mbanner.[0m .[1;32mipsec.conf.[0m .[1;32mrc.local.[0m
.[1;34mboard.d.[0m .[1;34mipsec.d.[0m .[1;36mresolv.conf.[0m
.[1;34mcfgsync.d.[0m .[1;32mipsec.secrets.[0m .[1;32mservices.[0m
.[1;34mchat.[0m .[0;0mlocaltime.[0m .[1;32mshadow.[0m
.[1;34mcloud_proc.[0m .[1;34mmodem.[0m .[1;32mshadow-.[0m
.[1;34mconfig.[0m .[1;34mmodeswitch_data.[0m .[1;32mshells.[0m
.[1;34mcrontabs.[0m .[1;34mmodules-boot.d.[0m .[1;34msnmp.[0m
.[1;34mdefault.[0m .[1;34mmodules.d.[0m .[1;34mssl.[0m
.[1;32mdevice_info.[0m .[1;36mmtab.[0m .[1;32mstrongswan.conf.[0m
.[1;32mdhcp6s.conf.[0m .[1;34mnetlink.d.[0m .[1;34mstrongswan.d.[0m
.[1;32mdhcp6sctlkey.[0m .[1;34mnginx.[0m .[1;32msys_monitor.conf.[0m
.[1;32mdiag.sh.[0m .[1;32mnsswitch.conf.[0m .[1;32msysctl.conf.[0m
.[1;32mdnsmasq.conf.[0m .[1;34mopenvpn.[0m .[1;32msysupgrade.conf.[0m
.[1;34mdropbear.[0m .[1;32mopenwrt_release.[0m .[1;34mtddpd.[0m
.[1;34measy-rsa.[0m .[1;32mopenwrt_version.[0m .[1;34mtmngtd.d.[0m
.[0;0methers.[0m .[1;32mopkg.conf.[0m .[1;34mtmngtd.rules.[0m
.[1;32mfirewall.user.[0m .[1;32mpasswd.[0m .[1;34mtmngtd.tmo.[0m
.[1;36mfstab.[0m .[1;32mpasswd-.[0m .[1;34muci-defaults.[0m
.[1;34mgcom.[0m .[1;34mportal_mgmt.[0m .[0;0muhttpd.crt.[0m
.[1;32mgroup.[0m .[1;34mppp.[0m .[0;0muhttpd.key.[0m
.[1;32mhosts.[0m .[1;32mpptpd.conf.[0m .[1;32musb-mode.json.[0m
.[1;32mhotplug-preinit.json.[0m .[1;32mpreinit.[0m .[1;34musb_modeswitch.d.[0m
.[1;34mhotplug.d.[0m .[1;32mprofile.[0m .[1;32mwifidog-msg.html.[0m
.[1;32mhotplug.json.[0m .[1;34mprofile.d.[0m .[1;32mwifidog.conf.[0m
.[0;0mimproxy.conf.[0m .[1;32mprotocols.[0m .[1;34mwireless.[0m
.[0;0mimproxyvnet.conf.[0m .[1;34mradiusclient-ng.[0m .[1;34mxl2tpd.[0m
.[1;34minit.d.[0m .[1;34mrc.button.[0m
.[1;32minittab.[0m .[1;32mrc.common.[0m
root@ER605:/etc#
root@ER605:/etc#
me only having a hot Meseta pure arabica for now 
no crushed Ice
@chill1Penguin which stock firmware version is recommended in our ER605v2 to make your patch work?
It looks like you still booted into the TP-Link firmware. Perhaps your build of the recovery image did not successfully fully compile?
Can you send me your recovery image build log? Also, since you have UART access, can you also send me a full boot log? You can DM me.
I have successfully tried with the latest firmware (2.1.2 Build 20230210).
Thanks for the reply @chill1Penguin I'll try it in a few days.
Latest firmware is 2.2.0
er605 2.2.0
please explain me how for these 2 logs
I tried uart, but I couldn't even see the boot log.
But strangely, I was able to boot normally only when I connected the pin to FT232RL.
I flashed the built image again and it came back to the same state.
er605 gpl
https://static.tp-link.com/resources/gpl/er605_gpl.tar.gz
can we build a recovery using this for the v1?
The ER605 emits data over the UART port as soon as the device powers on. If you can't see anything coming from the device, I suspect that something is wrong with your connections, soldering, and/or baud rate settings.
Possibly. I don't have a v1 to try, though.