I was preparing a new Mikrotik hEX router for church. so these are still fixable with proper equipment (desolder NAND chip, fix the contents using chip programmer, solder it back) but how many people can do this? Instead boards are heading to e-waste bucket even when hardware is still perfectly working.Your Mikrotik doesn’t boot. I have been fixing Mikrotik hardware for a long time, replacing caps, power regulators, doing hot air rework, chip swaps etc. Why even differentiate between boards with RS232 and TTL UART ports? It's stupid. Especially because Mikrotik could have prevented this so easily by having proper bootloader menu. Again, unless you need some of the new features or there are some needed security fixes, there is no need to run latest and greatest version.Īs for RB922, it's sad. Before updating any hardware, always wait at least a week and read entire thread about it here on forum before deciding to go ahead. There is ZERO reason to update it every release and Mikrotik is 100% guilty of causing this mess by dropping proper versioning for routerboot like it was before and forcing it to be same as ROS version number.Īlso I would completely avoid latest stable and long term releases as they are problematic at best. I can't even get to to boot to Netinstall.ĭo not update the routerboot unless you NEED it updated.
The interfaces LEDs comes on after a few seonds and then they reboot again. The first firmware upgrade went fint, but after the second reboot for the bootloader both are now stuck in a boot loop. I have experienced the exact same thing this week. Was there something in a change log or app note telling you not to upgrade directly from 6.40 to 6.49?Īny suggestions on how to un brick these three routers? As there is no serial port, and the network interface is hosed, it looks like I am stuck. I am guessing that the bootloader, and backup are corrupting. So I tried one more RB922, I used a different laptop. I rebooted the unit and it did the exact same thing. I installed just the routeros-mipsbe.npk. It was running ROS 6.40.3 and had firmware 3.41. So I pulled out a RB922 that I had and did the same thing. I tried Netinstall with another working router and the router shows up. I tried NetInstall on all the ports, nothing.
I ran wireshark to see if there was any traffic coming out of the Ethernet port, nothing. I tried using NetInstall, and it never shows up. The act light flashes and goes off like it is resetting, but it just goes into the boot loop. It would blink the act light and then flash all of the indicator lights and reboot. Then I rebooted it, and it went into a boot loop. So I went about setting it up the way I wanted. The router rebooted fine and had the OS running. The upgrade went fine, I thought, using Winbox. I wanted to use Wireguard and so I tried to upgrade it to 6.49. So I started with an RB751 which had ROS 6.40.1 on it. I needed a wireless bridge for a trade show.
0 kommentar(er)
