Topic: tp link 4300 wont start

The content of this topic has been archived on 22 Mar 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Page 1 of 1

Post #1

dr.muradd

9 Dec 2014, 00:15

hello

i used to use openwrt on my router but im last week i decide to change to ddwrt and i didnt get any problem but after week of use ddwrt i dont like it and i think its not worth to use so i decide to go back to openwrt

i tried to flash the wrt-to-stock firmware in order to flash openwrt but the process didnt complete its always give upgrade error i tried to use tftp but same thing happen to me and after a lot of search in google and forum someone says that u can use winscp and telent by putty so that what i did . i toke the bin file and upload it to the tmp then by telenet command i write it , after thats the router restart and wont start . just power led is on nothing ealse .. so i spend 4 hours in ddwrt and openwrt wiki and forum to find solution but no success , i tried tftp recovery by hold wps .. i tried stock firmware nd open nd dd non of them work the download success but when restart its back to power led only .. also tried 30/30/30 reset method also noot working ,, also tried to send the frimware by tftp clint to 192.168.0.86 and my computer ip 192.168.0.66 also nothing happen error no response

i have no experience with jtag and im out of solutions

Post #2

dr.muradd

9 Dec 2014, 02:32

see this log .. i know what request the router . but is there anything wired like the DHCP thing ?

03:27:47.302422 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300
03:27:49.997267 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300
03:27:54.547905 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300
03:27:54.962619 IP 192.168.1.1.520 > 192.168.1.255.520: RIPv2, Response, length: 44
03:28:02.483585 IP 192.168.0.86.1586 > 192.168.0.66.69:  44 RRQ "wdr4300v1_tp_recovery.bin" octet timeout 5 
03:28:03.192844 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300
03:28:07.483482 IP 192.168.0.86.1586 > 192.168.0.66.69:  44 RRQ "wdr4300v1_tp_recovery.bin" octet timeout 5
03:28:11.263957 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300
03:28:12.341346 IP 192.168.1.35.51429 > 224.0.0.253.3544: UDP, length 40
03:28:12.483473 IP 192.168.0.86.1586 > 192.168.0.66.69:  44 RRQ "wdr4300v1_tp_recovery.bin" octet timeout 5
03:28:17.483466 IP 192.168.0.86.1586 > 192.168.0.66.69:  44 RRQ "wdr4300v1_tp_recovery.bin" octet timeout 5 
03:28:20.091810 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300
03:28:22.483449 IP 192.168.0.86.1586 > 192.168.0.66.69:  44 RRQ "wdr4300v1_tp_recovery.bin" octet timeout 5 
03:28:24.842912 IP 192.168.1.1.520 > 192.168.1.255.520: RIPv2, Response, length: 44
03:28:25.424146 IP 192.168.0.66.57779 > 192.168.0.86.69:  34 WRQ "wdr4300v1_tp_recovery.bin" octet 
03:28:26.425375 IP 192.168.0.66.57779 > 192.168.0.86.69:  34 WRQ "wdr4300v1_tp_recovery.bin" octet
03:28:27.426613 IP 192.168.0.66.57779 > 192.168.0.86.69:  34 WRQ "wdr4300v1_tp_recovery.bin" octet
03:28:27.483443 IP 192.168.0.86.1586 > 192.168.0.66.69:  44 RRQ "wdr4300v1_tp_recovery.bin" octet timeout 5
03:28:28.374422 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300
03:28:28.427854 IP 192.168.0.66.57779 > 192.168.0.86.69:  34 WRQ "wdr4300v1_tp_recovery.bin" octet 
03:28:29.429061 IP 192.168.0.66.57779 > 192.168.0.86.69:  34 WRQ "wdr4300v1_tp_recovery.bin" octet 
03:28:30.430298 IP 192.168.0.66.57779 > 192.168.0.86.69:  34 WRQ "wdr4300v1_tp_recovery.bin" octet 
03:28:32.483437 IP 192.168.0.86.1586 > 192.168.0.66.69:  44 RRQ "wdr4300v1_tp_recovery.bin" octet timeout 5
03:28:36.386833 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300
03:28:36.958934 IP 192.168.1.28.5353 > 224.0.0.251.5353: 0 PTR (QU)? _googlecast._tcp.local. (40)
03:28:36.974766 IP 192.168.1.28.5353 > 224.0.0.251.5353: 0 PTR (QU)? _googlecast._tcp.local. (40)
03:28:37.046283 IP 192.168.1.28.59543 > 239.255.255.250.1900: UDP, length 129
03:28:37.483427 IP 192.168.0.86.1586 > 192.168.0.66.69:  44 RRQ "wdr4300v1_tp_recovery.bin" octet timeout 5
03:28:37.542190 IP 192.168.1.28.59543 > 239.255.255.250.1900: UDP, length 129
03:28:37.975493 IP 192.168.1.28.5353 > 224.0.0.251.5353: 0 PTR (QM)? _googlecast._tcp.local. (40)
03:28:42.483421 IP 192.168.0.86.1586 > 192.168.0.66.69:  44 RRQ "wdr4300v1_tp_recovery.bin" octet timeout 5
03:28:45.381236 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300
03:28:47.483409 IP 192.168.0.86.1586 > 192.168.0.66.69:  44 RRQ "wdr4300v1_tp_recovery.bin" octet timeout 5
03:28:52.483400 IP 192.168.0.86.1586 > 192.168.0.66.69:  44 RRQ "wdr4300v1_tp_recovery.bin" octet timeout 5
03:28:52.874003 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300
03:28:54.723137 IP 192.168.1.1.520 > 192.168.1.255.520: RIPv2, Response, length: 44
03:28:59.854589 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300
03:29:08.613258 IP 0.0.0.0.68 > 255.255.255.255.67: BOOTP/DHCP, Request from 98:fe:94:e3:d0:46, length 300

Post #3

dr.muradd

9 Dec 2014, 20:57

guys i mange by some how to connect serial port but its gave me something wired .. what i did wrong ?

y▒ޯUۅ▒]▒▒▒k'▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒U▒;!!▒w{▒▒▒▒▒▒▒▒▒w[}e▒▒▒▒▒▒▒e{▒▒K▒۪▒▒▒{▒▒▒▒▒▒*▒3'=/▒-
5▒▒e{▒▒59!9!#▒▒▒▒▒▒▒▒s'=/▒▒▒▒▒e{▒▒UFK▒▒▒▒▒▒:▒▒▒j▒
*▒▒*▒▒▒▒▒▒▒[55▒ai▒▒▒▒▒▒▒▒m#▒▒▒▒▒5'▒▒a▒▒▒▒5'▒▒u▒▒▒5'▒▒▒▒▒▒▒▒▒j˻{
Ս▒]▒▒▒]▒▒-Ս▒▒▒▒c!▒='-7▒=77▒-#▒s'=/▒▒U-#1▒3-57▒=77▒▒▒▒▒▒▒▒۪ʪ▒▒+▒▒JZ▒▒▒▒▒▒▒+▒T_V▒▒++++▒u▒▒_oM▒▒▒▒▒˚▒▒▒▒{▒▒˚▒▒▒▒{▒▒▒+▒M▒▒▒▒▒Z۪Z▒▒Z˪Z▒{[▒▒+▒O▒i▒▒▒T▒
▒▒▒]-▒9!%'55▒▒M▒▒▒▒*▒5/▒▒▒_EQ▒
▒j▒▒k▒▒▒˪▒
▒▒*▒nnۅ▒]▒▒▒▒-%=15▒=▒▒3▒▒▒▒▒▒▒▒▒▒▒뿿▒U#9!%-#1▒i5'▒m%=15▒▒▒▒▒ai▒▒▒▒Y=▒)5'▒▒▒▒▒▒▒▒

Post #4

MBS

13 Dec 2014, 18:21

You should follow the wiki and provide information about what you did, so somebody may inform you what you did wrong.

The discussion might have continued from here.

Page 1 of 1