I though I read the post wrong - you weren't successfull.
Nothing in the TFTP log usually means the FW is up, and the TFTP server unreachable.
192.168.1.1 is the default ip of openwrt.
I am not. Yet. Now am I trying to send the image over..
I have succeeded to send someting but not with tftp32, but putty and I've got logs in the tftd32 
Connection received from 192.168.1.20 on port 3244 [13/02 20:40:32.844]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:40:32.844]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:40:32.849]
Connection received from 192.168.1.20 on port 3785 [13/02 20:40:43.869]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:40:43.869]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:40:43.869]
Connection received from 192.168.1.20 on port 3610 [13/02 20:40:54.901]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:40:54.901]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:40:54.901]
Connection received from 192.168.1.20 on port 3609 [13/02 20:41:05.919]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:41:05.919]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:41:05.919]
Connection received from 192.168.1.20 on port 2705 [13/02 20:41:16.948]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:41:16.948]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:41:16.948]
Connection received from 192.168.1.20 on port 2423 [13/02 20:41:27.969]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:41:27.969]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:41:27.969]
Connection received from 192.168.1.20 on port 2280 [13/02 20:41:38.989]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:41:38.989]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:41:38.989]
Connection received from 192.168.1.20 on port 1571 [13/02 20:41:50.014]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:41:50.014]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:41:50.014]
Connection received from 192.168.1.20 on port 2399 [13/02 20:42:01.029]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:42:01.039]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:42:01.039]
Connection received from 192.168.1.20 on port 1297 [13/02 20:42:12.059]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:42:12.059]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:42:12.059]
Connection received from 192.168.1.20 on port 2474 [13/02 20:42:23.084]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:42:23.084]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:42:23.084]
Connection received from 192.168.1.20 on port 4079 [13/02 20:42:34.099]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:42:34.099]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:42:34.099]
Connection received from 192.168.1.20 on port 2185 [13/02 20:42:45.129]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:42:45.129]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:42:45.129]
Connection received from 192.168.1.20 on port 3623 [13/02 20:42:56.149]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:42:56.149]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:42:56.149]
Connection received from 192.168.1.20 on port 1441 [13/02 20:43:07.169]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:43:07.169]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:43:07.169]
Connection received from 192.168.1.20 on port 3027 [13/02 20:43:18.197]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:43:18.197]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:43:18.197]
Connection received from 192.168.1.20 on port 1377 [13/02 20:43:29.219]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:43:29.219]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:43:29.219]
Connection received from 192.168.1.20 on port 3602 [13/02 20:43:40.239]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:43:40.239]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:43:40.239]
Connection received from 192.168.1.20 on port 2424 [13/02 20:43:51.259]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:43:51.259]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:43:51.259]
Connection received from 192.168.1.20 on port 1152 [13/02 20:44:02.289]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:44:02.289]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:44:02.289]
Connection received from 192.168.1.20 on port 2968 [13/02 20:44:13.309]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:44:13.309]
File <1401A8C0.img> : error 2 in system call CreateFile The system cannot find the file specified. [13/02 20:44:13.309]
Connection received from 192.168.1.20 on port 3610 [13/02 20:44:24.340]
Read request for file <1401A8C0.img>. Mode octet [13/02 20:44:24.340]
OACK: <timeout=5,> [13/02 20:44:24.340]
Using local port 60193 [13/02 20:44:24.340]
<1401A8C0.img>: sent 12888 blks, 6598367 bytes in 2 s. 0 blk resent [13/02 20:44:26.649]
Connection received from 192.168.1.20 on port 3330 [13/02 21:22:00.975]
Read request for file <1401A8C0.img>. Mode octet [13/02 21:22:00.975]
OACK: <timeout=5,> [13/02 21:22:00.975]
Using local port 50535 [13/02 21:22:00.975]
<1401A8C0.img>: sent 12888 blks, 6598367 bytes in 3 s. 0 blk resent [13/02 21:22:03.746]
Connection received from 192.168.1.20 on port 2823 [13/02 21:26:36.730]
Read request for file <1401A8C0.img>. Mode octet [13/02 21:26:36.730]
OACK: <timeout=5,> [13/02 21:26:36.730]
Using local port 59531 [13/02 21:26:36.730]
Connection received from 192.168.1.20 on port 2823 [13/02 21:26:41.730]
Read request for file <1401A8C0.img>. Mode octet [13/02 21:26:41.730]
OACK: <timeout=5,> [13/02 21:26:41.730]
Using local port 59532 [13/02 21:26:41.730]
<1401A8C0.img>: sent 12888 blks, 6598367 bytes in 3 s. 0 blk resent [13/02 21:26:44.349]
TIMEOUT waiting for Ack block #0 [13/02 21:27:01.781]
and log in putty
U-Boot 1.1.4 (Oct 18 2017 - 09:53:45)
ap152 - Dragonfly 1.0
DRAM: 128 MB
Top of RAM usable for U-Boot at: 88000000
Reserving 134k for U-Boot at: 87fdc000
Reserving 192k for malloc() at: 87fac000
Reserving 44 Bytes for Board Info at: 87fabfd4
Reserving 36 Bytes for Global Data at: 87fabfb0
Reserving 128k for boot params() at: 87f8bfb0
Stack Pointer at: 87f8bf98
Now running in RAM - U-Boot at: 87fdc000
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x17
flash size 8MB, sector count = 128
Flash: 8 MB
Using default environment
In: serial
Out: serial
Err: serial
Net: ath_gmac_enet_initialize...
No valid address in Flash. Using fixed address
ath_gmac_enet_initialize: reset mask:c02200
athr_mgmt_init ::done
Dragonfly ----> S17 PHY *
athrs17_reg_init: complete
SGMII in forced mode
athr_gmac_sgmii_setup SGMII done
: cfg1 0x80000000 cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
eth0 up
eth0
Setting 0x181162c0 to 0x60c02100
Autobooting in 1 seconds
dragonfly>
dragonfly> pintenv
Unknown command 'pintenv' - try 'help'
dragonfly> printenv
Unknown command 'printenv' - try 'help'
dragonfly> printenv
bootargs=console=ttyS0,115200 root=31:03 rootfstype=squashfs init=/sbin/init board=AP152 mtdparts=spi0.0:128k(factory-uboot),128k(u-boot),1024k(uImage),6784k(rootfs),64k(mib0),64k(ART)
bootcmd=bootm 0x9f010000
bootdelay=1
baudrate=115200
ethaddr=0x00:0xaa:0xbb:0xcc:0xdd:0xee
ipaddr=192.168.1.1
serverip=192.168.1.10
dir=
lu=tftp 0x80060000 ${dir}tuboot.bin&&erase 0x9f000000 +$filesize&&cp.b $fileaddr 0x9f000000 $filesize
lf=tftp 0x80060000 ${dir}ap152${bc}-${squashfs}&&erase 0x9f110000 +0x6d0000&&cp.b $fileaddr 0x9f110000 $filesize
lk=tftp 0x80060000 ${dir}vmlinux${bc}.lzma.uImage&&erase 0x9f010000 +$filesize&&cp.b $fileaddr 0x9f010000 $filesize
stdin=serial
stdout=serial
stderr=serial
ethact=eth0
....but whe I am trying to use only tftd32 is not working. Have no idea why.
And what does the 1401A8C0.img contain?
I think that was the original one strored at 0x81000000 - I have juts typed tftpboot and it started searching for it
Yes, but what's the content?
I don't know. I there a way to see it? I don't have that file on my system/computer.
I read it as it got read /sent.
<1401A8C0.img>: sent 12888 blks
Anyway, it seems it's the file(name) it's requesting.
Aaaa I have seen that the device is looking for that file and I have took the original firmware, rename it as it was asked and no luck. Unfortunately.
Now I am trying to do tftpboot 0x81000000 firm.bin which is the original one. It is sent to the device but I can't figure out what do I have to erase... as for example here erase 0xbf020000 +0x7c0000(this is from other device).
Now I was looking on the documented partitions here [OpenWrt Wiki] TP-Link TL-WPA8630P v2 and I am puzzled
I did something but...
U-Boot 1.1.4 (Oct 18 2017 - 09:53:45)
ap152 - Dragonfly 1.0
DRAM: 128 MB
Top of RAM usable for U-Boot at: 88000000
Reserving 134k for U-Boot at: 87fdc000
Reserving 192k for malloc() at: 87fac000
Reserving 44 Bytes for Board Info at: 87fabfd4
Reserving 36 Bytes for Global Data at: 87fabfb0
Reserving 128k for boot params() at: 87f8bfb0
Stack Pointer at: 87f8bf98
Now running in RAM - U-Boot at: 87fdc000
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x17
flash size 8MB, sector count = 128
Flash: 8 MB
Using default environment
In: serial
Out: serial
Err: serial
Net: ath_gmac_enet_initialize...
No valid address in Flash. Using fixed address
ath_gmac_enet_initialize: reset mask:c02200
athr_mgmt_init ::done
Dragonfly ----> S17 PHY *
athrs17_reg_init: complete
SGMII in forced mode
athr_gmac_sgmii_setup SGMII done
: cfg1 0x80000000 cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
eth0 up
eth0
Setting 0x181162c0 to 0x60c02100
Autobooting in 1 seconds
dragonfly> tftpboot 0x81000000 firm.bin
Trying eth0
dup 1 speed 1000
Using eth0 device
TFTP from server 192.168.1.10; our IP address is 192.168.1.1
Filename 'firm.bin'.
Load address: 0x81000000
Loading: #################################################################
#################################################################
.......
#################################################################
#################################################################
######################################################
done
Bytes transferred = 6598367 (64aedf hex)
dragonfly> erase 0xbf020000 +0x7c0000
Error: end address (0xbf7dffff) not in flash!
Bad address format
dragonfly> erase 0x9f040000 +0x64B000
Erasing flash...
First 0x4 last 0x68 sector size 0x10000 104
Erased 101 sectors
dragonfly> cp.b 0x81000000 0x9f040000 0x64B000
Zero length ???
dragonfly> cp.b 0x81000000 0x9f040000 0x64B000
Unknown command 'cp.b' - try 'help'
dragonfly> cp.b 0x81000000 0x9f040000 0x64B000
Unknown command 'cp.b' - try 'help'
dragonfly> cp.b 0x81000000 0x9f040000 0x64B000
Copy to Flash... write addr: 9f040000
done
dragonfly> bootm 0x9f040000
## Booting image at 9f040000 ...
---- fileTag = 9f040000
text base = ffffffff
entry point = ffffffff
hdr->ih_load = 00000000
hdr->ih_ep = 00000000
Uncompressing Kernel Image at ffffffff ... Stream with EOS marker is not supportedLZMA ERROR 1 - must RESET board to recover
▒
U-Boot 1.1.4 (Oct 18 2017 - 09:53:28)
ap152 - Dragonfly 1.0
DRAM: 128 MB
Top of RAM usable for U-Boot at: 88000000
Reserving 403k for U-Boot at: 87f98000
Reserving 192k for malloc() at: 87f68000
Reserving 44 Bytes for Board Info at: 87f67fd4
Reserving 36 Bytes for Global Data at: 87f67fb0
Reserving 128k for boot params() at: 87f47fb0
Stack Pointer at: 87f47f98
Now running in RAM - U-Boot at: 87f98000
Flash Manuf Id 0xef, DeviceId0 0x40, DeviceId1 0x17
flash size 8MB, sector count = 128
Flash: 8 MB
Using default environment
In: serial
Out: serial
Err: serial
Net: ath_gmac_enet_initialize...
No valid address in Flash. Using fixed address
ath_gmac_enet_initialize: reset mask:c02200
athr_mgmt_init ::done
Dragonfly ----> S17 PHY *
athrs17_reg_init: complete
SGMII in forced mode
athr_gmac_sgmii_setup SGMII done
: cfg1 0x80000000 cfg2 0x7114
eth0: 00:03:7f:09:0b:ad
eth0 up
eth0
Setting 0x181162c0 to 0x60c02100
Autobooting in 1 seconds
Trying eth0
eth0 link down
FAIL
Trying eth0
dup 1 speed 1000
HTTP server is starting at IP: 192.168.0.254
HTTP server is ready!
on cmd...
Ping statistics for 192.168.1.20:
Packets: Sent = 1410, Received = 12, Lost = 1398 (99% loss),
Control-C
^C
C:\Users\GxGL>ping 192.168.0.254 -t
Pinging 192.168.0.254 with 32 bytes of data:
Reply from 192.168.0.254: bytes=32 time<1ms TTL=128
Reply from 192.168.0.254: bytes=32 time<1ms TTL=128
....
Reply from 192.168.0.254: bytes=32 time=6ms TTL=128
on putty...
Request for: /
Request for: /favicon.ico
## Error: request file name not suport!
After clicking upgrade...
Expecting 6598609 bytes in body request message
Found boundary value: "------WebKitFormBoundaryCuj7ejmYHjlpR7jX"
Data will be downloaded at 0x80060000 in RAM
Upgrade type: firmware
Upload file size: 6598367 bytes
Loading: #######################################
#######################################
#######################################
.......
#######################################
#####
[NM_Debug](firmwareValidCheck) 01303: md5 error.
[NM_Debug](divideUpLoadFile) 01328: firmwareValid error
[NM_Debug](nm_lib_readPtnTable) 00691: NM_PTN_TABLE_BASE = 0x620000
[NM_Debug](nm_lib_readPtnFromNvram) 00519: partition_used_len = -407813932, requried len = 8192
[NM_Debug](nm_lib_readPtnTable) 00699: Reading Partition Table from NVRAM ... OK
[NM_Error](nm_lib_parsePtnIndexFile) 00590: invalid partition-index-file para id.
[NM_Error](nm_lib_readPtnTable) 00704: Parsing Partition Table ... FAILED
[NM_Error](nm_tpFirmwareCheck) 01101: Init failed.
## Error: HTTP upgrade file check failed!
Trying eth0
HTTP server is starting at IP: 192.168.0.254
HTTP server is ready!
Err I have entered wrong size of flash accordingly after the firmware file size so now it errors.
Need to redo the steps with 8M storage as required lenght will be 0x800000..
but wrong again it worked with 0x7a1200 and still wrong!
Somehow in my head is a mess which partition is which and the size as well.
That being said ...I didn't find 9f040000 in the partition docs but my bootloader is starting it so it must be the flash, and the size of the flash should be 8Mb (8192).
Please correct me if I am wrong. I am sure I am, but can't see were and what I did wrong
The last command that I have tried is
tftpboot 0x81000000 firm.bin && erase 0x9f040000 +7c0000 && cp.b 0x81000000 0x9f040000 0x7c0000 && bootm 0x9f040000
or one by one
tftpboot 0x81000000 firm.bin
erase 0x9f040000 +7c0000
cp.b 0x81000000 0x9f040000 0x7c0000
bootm 0x9f040000
Maybe the nvram should be erased aswell but tried erase nvram and didn't worked.
Ah brilliant. If you are able to get the recovery http server, you should be able to upload the stock TP-Link firmware (.bin file from TP-Link firmware .zip), and that should get the device back working.
The http server might also be startable using the command "httpd" according to the u-boot sources in the TP-Link GPL code. You can try "setenv ipaddr 192.168.1.20" to set the IP.
I would avoid any u-boot flash erase guesswork if possible unless your 100% sure. Others tried it and wiped their bootloader, forcing them to SPI flash instead.
E.g.
Hi @jwmullally,
Besides that I have reached the point where I can upload the original image to the device through http, that fails on me at 40% and in the console displays
[NM_Debug] messages...
...as in the last log of my previous post.
I have tried to tftpboot with original firmware and also with openwrt factory one, then tried the web, and failed. I have tried both of them on both of them, first on the stock tried to upload the stock by the web and the the owrt factory and same after sent the owrt factory. Didn't worked as previous.
I don't know yet what I am doing wrong.
I think I see it 
...that should be the +filesize.
According to this post
Bytes transferred = 8126464 (7c0000 hex)
dragonfly> erase 0x9f010000 +7c0000
Erasing flash...
...so the file size should be the hex of the uploaded(transferred) file.
I will try it with this.
...and no! Failed again, same message. 
I think "I've fix it!" - hopefully not for ever, but...
No uboot or any other kind of life signals on serial and also the LEDs are gone.
So, I think I'm not alone about this problem with the web failsafe.
Uploading the stock image doesn't change anything and I can't upload the openwrt image, as the system says the image is invalid.
I bricked mine in this operation 
Now when its plugged into power a red lite flashes for a fraction of a second and that's it.
I think now the only solution is to write the firmware directly to the chip.
Luckily I have a CH341A USB programmer with a SOC8 cable and I am able to connect the chip to it, but the software doesn't recognize it and there is no where in the list of chips in the software. I have only BV, CV and FV variants of this chip.
...and
mine is Winbond 25Q64JVSIQ aka 25Q64JV.
Maybe using this tutorial, or other (I am still looking for a good one) that can apply to my situation.
Hmm. It looks that I'm gonna need a full dump of the chip from someone
How is the procedure to obtain one? Is there someone who has it, or who can get one for me, or for all the users here that might be in need?
Still don't believe I have reached this point of failing 
I had to use flashrom v1.2 for this (using Raspberry Pi). flashrom v1.1 didn't recognize the chip.
# flashrom -p linux_spi:dev=/dev/spidev0.0 -r WPA8630_v2_stock.rom
flashrom v1.2 on Linux 4.19.97-v7+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org
Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Using default 2000kHz clock. Use 'spispeed' parameter to override.
Found GigaDevice flash chip "GD25Q64(B)" (8192 kB, SPI) on linux_spi.
Reading flash... done.
I'll send you a copy of my ROM (Model TL-WPA8630P(EU) Ver: 2.0)
1 Like
Hello @jwmullally,
indeed. My setup of RPi didn't get the chip. I will upgrade flashrom to v1.2.
I will give this a try.
Thank you
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.