Bricked EAP225-Wall Trying to Flash Back to Original Firmware

[andyboeh]

Nope, they need to be crossed (usually; there are adapter with wrong labeling). It's always specified from the point of view of the device, so TxD of the router is the router's transmit while TxD on the computer is the computer's transmit - and connecting them won't work, you want transmit to receive. If you get it wrong, you'll get no output, but you can't break anything (if it's really just RxD/TxD swapped).

[yeahbuddy]

Edit: I was able to get PuTTY working and I'm able to type in commands. I'm not sure where to go from here. I'm following this. According to that guide I need specific values depending on the device but I'm not sure what those would be. Any ideas on this? This is the hardware spec sheet for my device

Edit2: I'm gonna be off my pc for a little bit, I made some progress though. I think I was able to get the TFTP Sever working but now the console shows the AP is looking for a file called "0101A8C0.img".

Here is the output of printenv command if it helps.

bootargs=console=ttyS0,115200 root=31:02 rootfstype=jffs2 init=/sbin/init mtdpar                                                       ts=ath-nor0:256k(u-boot),64k(u-boot-env),14528k(rootfs),1408k(uImage),64k(mib0),                                                       64k(ART)
bootcmd=bootelf 0x9f040000
bootdelay=2
baudrate=115200
ethaddr=0x00:0xaa:0xbb:0xcc:0xdd:0xee
ipaddr=192.168.1.1
dir=
lu=tftp 0x80060000 ${dir}u-boot.bin&&erase 0x9f000000 +$filesize&&cp.b $fileaddr                                                        0x9f000000 $filesize
lf=tftp 0x80060000 ${dir}board956x${bc}-jffs2&&erase 0x9f050000 +0xE30000&&cp.b                                                        $fileaddr 0x9f050000 $filesize
lk=tftp 0x80060000 ${dir}vmlinux${bc}.lzma.uImage&&erase 0x9fe80000 +$filesize&&                                                       cp.b $fileaddr 0x9fe80000 $filesize
stdin=serial
stdout=serial
stderr=serial
serverip=192.168.1.234
ethact=eth0

[yeahbuddy]

I made this reply separate because I think I'm close to the solution. I was able to put the firmware image onto the device but when I try to boot using bootm it gives me a "Bad Magic Number" error. I get this using the OpenWRT firmware file and the official TP-Link firmware file.

Edit: I was able to flash the EAP225 v3 initramfs from this page successfully. Thank you everyone for the help

Outline of the steps I took for flashing incase anyone else has a similar issue:

I followed this to flash to the device.

They use the example "erase 0xbf020000 +0x7c0000" in order to show the command, in order to find the values for whatever device your using type in "printenv bootcmd" and the output from that would replace "0xbf020000" in the example command.

The output from the tftpboot command will tell you the info for the filesize, for me it was

Bytes transferred = 4937188 (4b55e4 hex)

The (4b55e4 hex) is the important part

And then "printenv bootcmd" would output something like

bootcmd=bootelf 0x9f040000

So the command in my case was "erase 0x9f040000 +0x4b55e4" and then use those values for the other commands in the guide

Running "tftpboot" with no extra parameters should also give you the load address which in the guide is "0x81000000". For me it was the exact same address but it may be different for you.