Hello! My Belkin RT 3200 router with stock fw is apparently bricked, because it does not allow me to access the interface, it never connects, where I live (Venezuela) there are many failures with the electrical supply, and the router turns off and on many times per this reason.
I have already tried to reset with the reset button, in the same way it does not let me access the interface, I also noticed that the router does not provide an IPv4 address to my computer connected by Ethernet, what can I do?
You have to ask local belkin service. No OpenWRT involved.
Obviously if OEM software is irrecoverably damaged you cannot install OpenWRT like here https://openwrt.org/toh/linksys/e8450
Probably borrow UPS when you try.
It appears you are using firmware that is not from the official OpenWrt project.
When using forks/offshoots/vendor-specific builds that are "based on OpenWrt", there may be many differences compared to the official versions (hosted by OpenWrt.org). Some of these customizations may fundamentally change the way that OpenWrt works. You might need help from people with specific/specialized knowledge about the firmware you are using, so it is possible that advice you get here may not be useful.
Ask for help from the maintainer(s) or user community of the specific firmware that you are using.
Provide the source code for the firmware so that users on this forum can understand how your firmware works (OpenWrt forum users are volunteers, so somebody might look at the code if they have time and are interested in your issue).
If you believe that this specific issue is common to generic/official OpenWrt and/or the maintainers of your build have indicated as such, please feel free to clarify.
So far no OpenWRT was involved, so damage done cannot be predicted/assessed. Some vendors stuff "telemetry" in flash sooner pr later leading to flash wear or half-programmed blocks. Before any attempt at OpenWRT - OEM firmware has to be brought in good shape
OpenWRT was not involved, but this is a likely case of what the OpenWRT devs predicted to happen with this device under this user's situation. The stock firmware design had some significant flaws that would result in the device failing to boot beyond BL3.1 under certain conditions, and the end results match the situation described here. The good news is that yes indeed, this device can be recovered from nearly any software flaw. However, the process for doing so from a stock firmware is a bit more complicated.
The primary OpenWRT forum topic for this device contains the "hard recovery" instructions necessary to recover the RT3200/e8450 to a stable OpenWRT 23.05.x firmware from a flash corruption issue that prevents boot. However, it does require access to a USB to 3.3v serial adapter (often referred to as USB TTL), the mtk_uartboot tool, and the instructions may need to be altered slightly depending on whether or not the router's 'factory' partition was also corrupted.
Sadly, recovering to stock firmware is extremely complicated in comparison. It would also likely require access to clean, valid copies of data that were not backed up (stock firmware doesn't have an option to do so) and were not made readily available by the vendor.
Thank you for all the help, I tell you that I managed to make the router connect under WiFi mesh with another router just like the one I have at home, thanks to this I am using the router with the problem as a secondary mesh node, I still cannot access it. the brick router interface.