As per documentation and user guide i switched dir-2640 to recovery mode by pressing reset+power light starts blinking orange.
Changed to static address 192.168.0.2 with 24 mask
Fired up firefox on ubuntu and opened 192.168.0.1.
Chose right openwrt factory bin file which i renamed to dink-factory.bin and hit upload button.
After some time it says connection timed out.
Tried same procedure with private window.
Tried with curl 8.5.0 with attributes v i and F firmware=@dlink-factory.bin it showed that it uploaded.
Waited 5 mins for it to reboot it didnt. Did power on/off changed static address to 192.168.1.2 mask 24.
Tried pinging and opening 192.168.1.1 with browser nothing.
Lights on the router are blue now.
Stock firmware isnt in place the only way i can get anything in browser is via dlink recovery mode.
In the link you just provided which i followed before opening a new thread was written if all methods (with different browsers) failed try curl method which i did.
They simply timed out i would call it fail.
Right after hitting upload button in recovery page there is no feedback of whats happening and after some time page refreshes to connection timed out.
Quotes in curl are needed only if the string contains spaces or special characters not to cause expansion/globbing. In my case as i renamed the firmware to dlink-factory.bin there is no need for quotes.
Regardless i will try that now and will come with update if that works.
yeah, I'm not sure if it's required, but worth trying.
I think the key thing right now is for the recover page to come up again in general. If that doesn't come up, serial may be required to figure out what is going on.
Will it accept the vendor's factory firmware? Not that it is required, but this could be a useful test to make sure the process is not resulting in a corrupted file upload.
I wonder if something might be wrong with the 23.05 factory images.
How about 21.02 (the first supported release)... see if it will work with that version's factory image. If it does, you can then use that as a springboard to get to 23.05 via sysupgrade.
I wasn't suggesting that the file itself was corrupted (although it is always a good thing that you verified it)... I was thinking that it could have been a corruption during the upload to the router itself.
I left it on didnt touch anything now after trying 21.02.0 second time. It has whole night reboot by itself. In the morning will check and will post here. Thanks for support anyways.
Yes im doing restart by myself but never waited 10mins. May be 5 max.
