The pins to solder to de motherboard are sold in an electronics store?, the man in the videos I think he used a paper clip of the size of the hole, is that possible?
My suggestion was to try and find someone who was experienced to do the soldering for you...you could start asking in electronics stores, or places that build computers.
The poster of the video did cut pieces of a paper clip for the pins.
ty jwoods, I think that part is OK, I´ve disabled the antivirus and the firewall, and set the ip of the computer to 192.168.0.66 and I think thats not the problem because when the router connects and ask por the file, it appears a little window with a progress bar with something like "transfering file" and it goes till 1the end.
A couple of messages above I´ve copied the log file without the recovery file so the router couldnt find it:
"Connection received from 192.168.0.86 on port 4008 [10/05 10:43:18.001]
Read request for file <ArcherC7v2_tp_recovery.bin>. Mode octet [10/05 10:43:18.001]
File <ArcherC7v2_tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [10/05 10:43:18.001]
Connection received from 192.168.0.86 on port 4008 [10/05 10:43:21.005]
Read request for file <ArcherC7v2_tp_recovery.bin>. Mode octet [10/05 10:43:21.005]
File <ArcherC7v2_tp_recovery.bin> : error 2 in system call CreateFile The system cannot find the file specified. [10/05 10:43:21.005] "
forget this part of the log file because it was just to know if I should rename the file to ArcherC7v2_tp_recovery.bin or to ArcherC7v3_tp_recovery.bin
ty
Unless there is a typo, the IP address in the messages doesn't match what you said you set it to.
What messages do you get when you do specify the recovery file?
As far as I know my PC acts as a tftpd server with IP 192.168.0.66 , and the router acts as a Client with IP 192.168.0.86 (that ip is set automatically on the router, the one I have to change is my PC´s IP)
Server ip : 192.168.0.66 (or 192.168.1.66 deppend on the version)
Client ip : 192.168.0.86
I think the file is requested from the client 192.168.0.86 to the server 192.168.0.66
Quote:
Where did you get/rename ArcherC7v2_tp_recovery.bin from?
I don´t understant the question. I take the file for example factory-to-ddwrt.bin (or the files B@R gave me three posrts above) from the betas repository and rename in my computer to ArcherC7v2_tp_recovery.bin, then I put that file in the same directory that is TFTPD32 installed, and also with the program you can select the folder if it is a different one.
I think the file is requested from the client 192.168.0.86 to the server 192.168.0.66
Quote:
Where did you get/rename ArcherC7v2_tp_recovery.bin from?
I don´t understant the question. I take the file for example factory-to-ddwrt.bin (or the files B@R gave me three posrts above) from the betas repository and rename in my computer to ArcherC7v2_tp_recovery.bin, then I put that file in the same directory that is TFTPD32 installed, and also with the program you can select the folder if it is a different one.
Your network connection should be set up like the video beginning at the 8:33 mark.
You should not be using any DD-WRT files as your recovery file.
You should download the latest stock firmware from TP-Link depending on your location, and rename that as the recovery file.
Your network connection should be set up like the video beginning at the 8:33 mark.
You should not be using any DD-WRT files as your recovery file.
You should download the latest stock firmware from TP-Link depending on your location, and rename that as the recovery file.
Yes the stock firmware was the first firmware I used, the I tried with others, but no luck with anyone.
And the IPs were set exactly as the video, as you say in min 8,33
I think there is a problem that needs serial port connection
Just to make sure there is not a permissions issue with the location of the recovery file, or the recovery file itself, I would try downloading a fresh copy of the stock firmware from TP-Link, rename it, and put it in the Tftpd root directory (which is the default in Current Directory).
As mentioned before, the stock firmware should be the most current version, for your location...
Finally I´ve got an USB-Serial adapter, and succeded getting a serial conection with the router C7.
but even following the steps in the video I couldnt bring the router back to life, but maybe at least i´m a little closer ;o)
I´ve stablished a serial conection between the router and the PC (putty).
used tpl to stop the bootloop
and then as the video says, I used the tftpboot command to see the ip of the tftp server, the name of the file requested, and the adresses of memory when it starts booting.
I set everything to use tftp, dowloaded from TP-Link the latest original firmware file (called ArcherC7v2_en_3_14_3_up_boot(150427).bin)
and renamed it to 6F01A8C0.img
the used the command tftpboot and the file started uploading to the router with lots of ########## symbols.
It ended with the value fa0200 (hex) which its supposed to be the end of the file as far as I know
Then I used:
erase 0x9f020000 +fa0200
(it started erased the memory and counted from 1 to 250 or so)
and then:
cp.b 0x81000000 0x9f020000 0xfa0200
and started copying the file.
everything without errors, but then I type reset and the router is starts rebooting again (
with this log in the serial conection throught puty:
Code:
## Booting image at 9f020000 ...
Uncompressing Kernel Image ... Too big uncompressed streamLZMA ERROR 1 - must RESET board to recover
U-Boot 1.1.4 (Apr 24 2015 - 13:53:04)
ap135 - Scorpion 1.0DRAM:
sri
Scorpion 1.0
ath_ddr_initial_config(178): (32bit) ddr2 init
tap = 0x00000003
Tap (low, high) = (0x4, 0x1d)
Tap values = (0x10, 0x10, 0x10, 0x10)
128 MB
Flash Manuf Id 0x1, DeviceId0 0x20, DeviceId1 0x18
flash size 16MB, sector count = 256
Flash: 16 MB
Using default environment
*** Warning *** : PCIe WLAN Module not found !!!
In: serial
Out: serial
Err: serial
Net: ath_gmac_enet_initialize...
athrs_sgmii_res_cal: cal value = 0xa
No valid address in Flash. Using fixed address
No valid address in Flash. Using fixed address
ath_gmac_enet_initialize: reset mask:c02200
Scorpion ----> S17 PHY *
Vlan config...
TEST: FINAL REG VAL after TX Calibration - 0x46000000
TEST: FINAL XMII VAL after RX Calibration - 0x56000000
TEST: FINAL ETH_CFG VAL after RX Calibration - 0x00028001
athrs17_reg_init: complete
: cfg1 0x80000000 cfg2 0x7335
eth0: ba:be:fa:ce:08:41
eth0 up
athrs17_reg_init_wan done
SGMII in forced mode
athr_gmac_sgmii_setup SGMII done
: cfg1 0x800c0000 cfg2 0x7214
eth1: ba:be:fa:ce:08:41
eth1 up
eth0, eth1
Setting 0x18116290 to 0x60c1214f
Autobooting in 1 seconds
## Booting image at 9f020000 ...
Uncompressing Kernel Image ... Too big uncompressed streamLZMA ERROR 1 - must RESET board to recover
U-Boot 1.1.4 (Apr 24 2015 - 13:53:04)
ap135 - Scorpion 1.0DRAM:
sri
Scorpion 1.0
ath_ddr_initial_config(178): (32bit) ddr2 init
tap = 0x00000003
Tap (low, high) = (0x4, 0x1c)
Tap values = (0x10, 0x10, 0x10, 0x10)
128 MB
Flash Manuf Id 0x1, DeviceId0 0x20, DeviceId1 0x18
flash size 16MB, sector count = 256
Flash: 16 MB
Using default environment
*** Warning *** : PCIe WLAN Module not found !!!
In: serial
Out: serial
Err: serial
Net: ath_gmac_enet_initialize...
athrs_sgmii_res_cal: cal value = 0xa
No valid address in Flash. Using fixed address
No valid address in Flash. Using fixed address
ath_gmac_enet_initialize: reset mask:c02200
Scorpion ----> S17 PHY *
Vlan config...
TEST: FINAL REG VAL after TX Calibration - 0x46000000
TEST: FINAL XMII VAL after RX Calibration - 0x56000000
TEST: FINAL ETH_CFG VAL after RX Calibration - 0x00028001
athrs17_reg_init: complete
: cfg1 0x80000000 cfg2 0x7335
eth0: ba:be:fa:ce:08:41
eth0 up
athrs17_reg_init_wan done
SGMII in forced mode
athr_gmac_sgmii_setup SGMII done
: cfg1 0x800c0000 cfg2 0x7214
eth1: ba:be:fa:ce:08:41
eth1 up
eth0, eth1
Setting 0x18116290 to 0x60c1214f
Autobooting in 1 seconds
And everything seems the same as before, only bootloops.
I don´t know what I did wrong, maybe I used a wrong firmware file? (factory to ddwrt for example), or maybe that were not the correct memory adresses...
Anyone can help me a little, after succeded with the serial soldering part I feel that I desserve a better endind haha.
Following this, I attempt to load my firmware file
Code:
Environment size: 686/65532 bytes
ap135> tftp 0x81000000 factory-to-ddwrt.bin
eth1 link down
eth0 link down
Using eth1 device
TFTP from server 192.168.0.66; our IP address is 192.168.0.86
Filename 'factory-to-ddwrt.bin'.
Load address: 0x81000000
Loading: T T
Retry count exceeded; starting again
eth0 link down
eth1 link down
Tx Timed out
Tx Timed out
I assume you are using TFTPD64 in your PC, and changed it´s ip to 192.168.0.66 (try also 192.168.1.66)
Disable the antivirus and the firewall in the PC, it made it impossible to connect for me.
I think it´s not necessary to write:
setenv serverip 192.168.0.66;setenvipaddr 192.168.086 (this is a typo isn´t it?)
(the IP of the PC is what you set before and i think the router IP is set automatically to 192.168.0.86 when doing TFTPBOOT)
anyway the ips and the process of tftp seems ok, but the comunication between the pc and the router doesnt work, thats why I think the logviewer of the tftp64 is very useful.
I should try just tfptboot to see the log file of tftp64 if the router is connecting properly and requesting the file to the server. You can copy that log file here so people can help you too.
I'm having a similar issue and could use some help.
My C7 isn't looping, but it's getting stuck in step two of this sequence:
Pfvrflsim wrote:
1) all lamps
2) 1,2 and 4rd (power, star and bigger wifi lamp)
3) All except 3rd.
And starts over.
The recovery sequence through tftpd32 works great. The C7 will transfer the frimware from my laptop without issue, but the LEDs will stay one the 1st, 2nd, and 4th, and it won't reboot. I can't ping 192.168.0.1
Any ideas? I'm thinking I'll have to pick up a serial cable & USB to serial adapter.
Thanks for the suggestion. I'm running into the same issues. Here's the log from tftpd32:
tftpd32 log viewer wrote:
Connection received from 192.168.0.86 on port 2482 [29/12 09:09:12.746]
Read request for file <ArcherC7v2_tp_recovery.bin>. Mode octet [29/12 09:09:12.747]
OACK: <timeout=3,> [29/12 09:09:12.747]
Using local port 57111 [29/12 09:09:12.747]
<ArcherC7v2_tp_recovery.bin>: sent 31745 blks, 16252956 bytes in 17 s. 0 blk resent [29/12 09:09:29.981]
All firmware seems to have transferred over to the router via tftpd32 fine. The router doesn't seem to make much activity after the transfer. It seems to reboot since the ethernet port on my laptop loses and regains connection, however the LEDs on the front of the router don't change during the process or afterwards. The 1st (Power), 2nd (System) and 4th (Wireless 5 GHz) LEDs remain lit up.
My router was for Israel (IL version).
After restoration the router with pointed firmware I did flashing of EU version. Don't use last versions from TP-Link site, because you will get the locked router for your specific region.
And wait more after flashing via tftp, may be for 5-10 min to be sure.
Posted: Tue Jan 15, 2019 16:57 Post subject: Any news?
knighted wrote:
All firmware seems to have transferred over to the router via tftpd32 fine. The router doesn't seem to make much activity after the transfer. It seems to reboot since the ethernet port on my laptop loses and regains connection, however the LEDs on the front of the router don't change during the process or afterwards. The 1st (Power), 2nd (System) and 4th (Wireless 5 GHz) LEDs remain lit up.
Hi, I'm facing now the same issues ... did you find any solution ?
For me as well the files get transfered, but after that nothing happens (event after 15 mins waiting).
(
... did you find any solution ?