So presumably any WR802n firmware (stock, DD-WRT, etc..) can be loaded via this method so long as the filename is wr802nv1_tp_recovery.bin. Correct?
Yes, you must have an tftp-server listening on 192.168.0.66 (the ip of the router does not matter).
The name of the file you can see than in the log of the tftp-server
Quote:
Connection received from 192.168.0.86 on port 3580 [31/01 03:18:34.417]
Read request for file <wr802nv1_tp_recovery.bin>. Mode octet [31/01 03:18:34.417]
File <wr802nv1_tp_recovery.bin> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [31/01 03:18:34.417]
Connection received from 192.168.0.86 on port 3580 [31/01 03:18:37.615]
Read request for file <wr802nv1_tp_recovery.bin>. Mode octet [31/01 03:18:37.615]
File <wr802nv1_tp_recovery.bin> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [31/01 03:18:37.615]
Connection received from 192.168.0.86 on port 3580 [31/01 03:18:40.813]
Read request for file <wr802nv1_tp_recovery.bin>. Mode octet [31/01 03:18:40.813]
File <wr802nv1_tp_recovery.bin> : error 2 in system call CreateFile Das System kann die angegebene Datei nicht finden. [31/01 03:18:40.813]
Got it working here as well. It reports itself as the wr841nd v9 (see attached).
A couple things I noticed in doing the update: 1) I used tftpd (http://tftpd32.jounin.net/) and the transfer never reported that it got to 100% even though it completed - it stopped around 70-80%, and 2) the light on the router doesn't work like stock, making it look like the router is off when it is really on. Combined those two things made me think the flash didn't work. It wasn't until I checked my wifi and saw the dd-wrt SSID broadcasting that I realized the flash was successful.
Posted: Mon Feb 01, 2016 6:16 Post subject: Thinks for your advise but it didn't word in Chinese version
CTXSi wrote:
Got it working here as well. It reports itself as the wr841nd v9 (see attached).
A couple things I noticed in doing the update: 1) I used tftpd (http://tftpd32.jounin.net/) and the transfer never reported that it got to 100% even though it completed - it stopped around 70-80%, and 2) the light on the router doesn't work like stock, making it look like the router is off when it is really on. Combined those two things made me think the flash didn't work. It wasn't until I checked my wifi and saw the dd-wrt SSID broadcasting that I realized the flash was successful.
Now to play around and see what it can do...
The ip of my router is 192.168.1.253 and I tried 192.168.1.66 but in vain. May be the filename and TFTP ip isn't correct in my version.I was going to upgrade my tp-wr802n from Chinese version to US version but failed
The ip of my router is 192.168.1.253 and I tried 192.168.1.66 but in vain. May be the filename and TFTP ip isn't correct in my version.I was going to upgrade my tp-wr802n from Chinese version to US version but failed
You need to set your PC IP to 192.168.0.66 (note the zero instead of the 1).When the router boots up (and you hold reset for 3 seconds) the router checks that IP address for a file named wr802nv1_tp_recovery.bin. The video sisu13 posted is long, but does a good job showing the process. My experience is with the US version, I don't know for sure about the Chinese version. But if you check the tftpd log it will tell you what the filename needs to be (see hesst's post for an example of the log).
Note that when you load DD-WRT on this router you first need to connect to it via wifi to configure. The single port is assigned to the WAN by default. You can change that after connecting via wifi.
I tried the tftp process renaming the dd-wrt version to wr802nv1_tp_recovery.bin. It tftp loads fine, but I receive the 18005 error each time- any version I try.
So, path of least resistance, use KrypteX's file and roll up to the latest dd-wrt beta
Ok I feel like an idiot. Not my first rodeo but can't get on this bull for some reason.
1. I've set my nic
192.168.0.66
255.255.255.0
192.168.0.1
2. Firewall is off on Mac
3. Used TCPDump -i (nic interface #) to monitor traffic
4. My Tftp server is active and i can see it deliver the payload in the TCPDump
22:41:49.292145 IP 192.168.0.86.x25-svc-port > 192.168.0.66.tftp: 43 RRQ "wr802nv1_tp_recovery.bin" octet timeout 2
22:41:49.302118 IP 192.168.0.66.54666 > 192.168.0.86.x25-svc-port: UDP, length 12
22:41:49.302211 IP 192.168.0.86.x25-svc-port > 192.168.0.66.54666: UDP, length 4
22:41:49.302284 IP 192.168.0.66.54666 > 192.168.0.86.x25-svc-port: UDP, length 516
22:41:49.302444 IP 192.168.0.86.x25-svc-port > 192.168.0.66.54666: UDP, length 4
22:41:49.302511 IP 192.168.0.66.54666 > 192.168.0.86.x25-svc-port: UDP, length 516
22:41:49.302662 IP 192.168.0.86.x25-svc-port > 192.168.0.66.54666: UDP, length 4
...
5. However, No matter what dd-wrt file i try to deliver even renaming to wr802nv1_tp_recovery.bin does not work for tl-wr802n v1
6. I'm on a mac and the tftp server does not seem to log the delivery event/attempt in any way i can tell
7. I do not see any additional logs about the attempt on the router. its like nothing has happened.
I tried several builds from the ftp link and none worked through the web interface or tftp. I could be using the wrong one for my device maybe? let me know what you guys think. thanks
I tried several builds from the ftp link and none worked through the web interface or tftp. I could be using the wrong one for my device maybe? let me know what you guys think. thanks
