I am lucky in the afternoon on Dec 14,2020 to unbrick R6250.
I found a software nmrpflash on https://github.com/jclehner/nmrpflash in the early morning, also checked https://openwrt.org/docs/guide-user/installation/recovery_methods/nmrpflash.
From these info, nothing related for R6250, is it true ?
My trouble status in detail on R6250 is that after power-on, it locked and only left light keep amber never blicking no more. if ping, can find 6 times ping success only.
No matter how I set tftpd server on linux or tftp/tftp2 upload in Windows, and negative way (tftpd@192.168.1.2 for vmlinuz auto fetch), they all failed. I readed lots of content on DDWRT, but very few about R6250.
Anyway, I need a risk until the final way via USB2TTL & terminal.
Set NIC IP 192.168.1.2/24 and make sure 1G with Full-duplex.
(Because I have only maxium 5 seconds to keep on live)
Cable connected on LAN1 port to my PC Windows.
The stock firmware I chosed is R6250-V1.0.1.84_1.0.78.chk because it is smallest (9,513KB).
Under administrator command execute:
E:\nmrpflash-0.9>nmrpflash.exe -i net8 -f R6250-V1.0.1.84_1.0.78.chk
Waiting for phyiscal connection.
Error: Ethernet cable is unplugged.
Again !
E:\nmrpflash-0.9>nmrpflash.exe -i net8 -f R6250-V1.0.1.84_1.0.78.chk
Waiting for phyiscal connection.
Advertising NMRP server on net8 ... |
Received configuration request from 6c:b0:ce:9b:99:1d.
Sending configuration: 10.164.183.252/24.
Timeout while waiting for TFTP_UL_REQ.
No way but try again ! power-off R6250 and keep press reset button to power-on.
E:\nmrpflash-0.9>nmrpflash.exe -i net8 -f R6250-V1.0.1.84_1.0.78.chk
Waiting for phyiscal connection.
Advertising NMRP server on net8 ... -
Received configuration request from 6c:b0:ce:9b:99:1d.
Sending configuration: 10.164.183.252/24.
Timeout while waiting for TFTP_UL_REQ.
Release reset button and again
E:\nmrpflash-0.9>nmrpflash.exe -i net8 -f R6250-V1.0.1.84_1.0.78.chk
Advertising NMRP server on net8 ... /
Received TFTP_UL_REQ while waiting for CONF_REQ!
Received upload request without filename.
Uploading R6250-V1.0.1.84_1.0.78.chk ... OK
Waiting for remote to respond.
Received keep-alive request (9).
Remote finished. Closing connection.
Reboot your device now.
I cannot believe but it is true, because I really watched the left light changed from amber to green and final blicking-amber. I worried about reboot immediately so wait 6 minuets enough.
During the whole operation, I keep an extra normal windows to keep ping 192.168.1.1 -t.
No good news, same 6 times success ping only at the beginning.
Power-off then power-on R6250 again, and it is
E:\nmrpflash-0.9>ping 192.168.1.1 -t
Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.2: Destination host unreachable.
Reply from 192.168.1.2: Destination host unreachable.
Reply from 192.168.1.1: bytes=32 time=3918ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Reply from 192.168.1.1: bytes=32 time=2ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Reply from 192.168.1.1: bytes=32 time=1ms TTL=100
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Request timed out.
General failure.
General failure.
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Reply from 192.168.1.1: bytes=32 time<1ms TTL=64
Ping statistics for 192.168.1.1:
Packets: Sent = 95, Received = 86, Lost = 9 (9% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 3918ms, Average = 46ms
So it should be worked normal, open http://192.168.1.1 and works!
What I used is 0.9.15-rc3-win32, and need to be installed npcap.
I hope to share my expreience for anybody.
Because there is nothing about openwrt return stock firmware, even on youtube.
Maybe https://openwrt.org/docs/guide-user/installation/recovery_methods/nmrpflash should added R6250 now ?
Bonne nuit!
