Linksys EA6350 V3 uboot ttl can not used

Hardware Questions and Recommendations
1 
U-Boot 2012.07 [Barrier Breaker r48529,r48529] (Jul 21 2016 - 09:43:37)

Boot version: v0.6.0 -- IPQ4018.ILQ.1.1.6-CSU1 for the EA6350v3 board

smem ram ptable found: ver: 1 len: 3

DRAM: 256 MiB

get_board_param - mach

id : 0x8010100

NAND: spi_nand: spi_nand_flash_probe SF NAND ID 0:ef:aa:21

SF: Detected W25N01GV with page size 2 KiB, total 128 MiB

SF: Detected MX25L1605D with page size 4 KiB, total 2 MiB

ipq_spi: page_size: 0x100, sector_size: 0x1000, size: 0x200000

130 MiB

MMC:

....

board_update_dualboot_runtime_vars@1032: updating the 's_env' partition 0x4000 ...OK
main_loop@455: run_command(if test $boot_part = 1; then run bootpart1; else run bootpart2; fi, 0)

NAND read: device 1 offset 0x0, size 0x500000

5242880 bytes read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
(EA6350v3) #

But I can't type anything on the keyboard, can someone help me？

2

bad soldering (if you needed to do some) or bad USB TTL.

you could try the automatic recovery from https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=a873b292840848b67addb5be0c762d292bde33a1

3

Soldering andusb ttl is fine.
I can only use uboot because I wrongly flashed on all both partitions (I know it sounds stupid but it's true)
But now uboot is not working...

4

In the URL you gave me, it says this

Recovery (Manual):
- The steps for manual recovery are the same as the generic u-boot tftp
  client method.

But I'm unable to use uboot normally, it's a problem

5

you wrote your USB TTL was fine, and so was the soldering, if that's the case, we can't really do anything else for you ...

6

I tried to find the programmer firmware because I am using CH341A, but I haven't found it yet

7

I used a programmer to write to the chip (after saving), and now what TTL reads is like this

NAND read: device 1 offset 0x0, size 0x500000
ecc err(0x20) for page read
NAND read from offset 0 failed -74
0 bytes read: ERROR
(EA6350v3) #

I'm wondering if there's anything else that needs to be done before the firmware is flashed into the chip

8

I think I found the problem, but it's bad news.
The ttl rx on the router PCB is damaged and unknown components have fallen off.