OpenWrt Forum Archive

Topic: TpLink MR3420 firmware is bricked, not able to access it thro Ethernet

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

Hi

I loaded the openwrt firmware on my router but when I tried to move back to the original Tp link firmware then my router firmware bricked now I am not able to access it, due to this my warranty is also void.

Please suggest me how can I resolve this problem and get back to original firmware or at least make it run on any firmware.

dont worry  smile

please repeat this steps ;

https://forum.openwrt.org/viewtopic.php?id=57242

maybe your router needs different file name "mr3020v1_tp_recovery.bin"

please read wireshark messages ...

for me line 44  ...



PunBB bbcode test

(Last edited by micro77 on 31 May 2015, 13:07)

Hi Micro 77,

My problem is little different. My Router is bricked and I am not able to access it via Ethernet port so TFTP is not able to access my Router root directory.
Here is one video for your reference -
https://www.youtube.com/watch?v=UuDAmZzbl7o

Could you please suggest the solution for it?

your router seems constantly repeats "rebooting ".

and i think ;  it has maybe different hardware  fault.

Hi

I was able to get some message on TFTP window.

Start time                            Client Address            File                                         Mode         Size    Transferred    Blocksize   
6/5/2015 8:36:30 PM    192.168.0.86:1823    mr3420v2_tp_recovery.bin    octet    ?    0                      0

Timeout    Status                                 Description
0              Requested file not found.         Failed to download file from server. Requested file not found.

Do you have any idea now ? I have the client address.

When I try to Access the router Via tftpgui or any other tftp, I am getting following message.

192.168.0.86 requested mr3420v2_tp_recovery.bin file not found.

What does it mean ?

is your firewall open ?

maybe you should disable it.

Firewall was already disabled. Even I tried different tftp, I got the same message.

The discussion might have continued from here.