My RB5009 cannot enter the routing system after the script automatically restarted last night. Has anyone encountered this situation?
I tried using the Reset Button, but there was no response。
My RB5009 cannot enter the routing system
You don’t have access to the router? Or is there another problem?
after the script automatically restarted last night.
Why do you run a script?
Has anyone encountered this situation?
For me, the situation is unclear…
I tried using the Reset Button, but there was no response。
How exactly did you use the reset button?
What do you mean by no respons?
Did you follow procedure:
https://help.mikrotik.com/docs/spaces/ROS/pages/24805498/Reset+Button
Yes, I followed the procedure.
https://help.mikrotik.com/docs/spaces/R … set+Button
1、i can’t access to the router，It looks like it didn’t start properly
2、I used the scheduled restart script to test the ddns script
add name=reboot on-event=\
"/system scheduler disable reboot\r\
\n/system reboot\r\
\n" policy=reboot,write start-date=2025-05-11 start-time=05:00:00
After the device is powered on, the ether2 light is always on and remains in this state.
Using the reset button, there is no change in the device.
That brings you to either netinstall the device (if the reset button is working) or RMA the device.
https://help.mikrotik.com/docs/spaces/ROS/pages/24805390/Netinstall
Are you 100% sure the reset button is properly pressed befor powering the RB?
Of course, I have used network installation before
My last device was RB750Gr3, and I just changed to RB5009 last month
But do check that the power supply is working as it should, ideally testing the device with another surely working power supply.
This is not Mikrotik specific, any device power supply may fail “completely” (no power at all or evidently too low voltage output, easy to check) but also “partially” (an internal component fails, the power supply still gives out the theoretical voltage, but it has not enough “juice” for the device to boot, when a peak of power is usually needed).
This latter mode of failure can be tricky as a voltmeter check may pass, but when you actually have the load connected, volts and amperes drop.
I don’t have another 24V power adapter so it’s hard to rule out a power issue. The unit is still under warranty so I can send it back to the dealer for repair.
I suddenly seemed to remember that I updated the firmware before using the scheduled reboot, using the following link
https://box.mikrotik.com/f/7637f95e71cc497797de/?dl=1
https://help.mikrotik.com/docs/spaces/ROS/pages/40992878/RouterBOARD
I did the same thing. And my RB5009 is bricked exactly like yours. The update of the backup boot a few days before, seemed successful. But after a reboot the next day it would not come online. Constant blue led and faint green on eth 2. Cant get contact with netinstall.
Gibbs’ Rule #39: There is no such thing as coincidence. 
It seems like a serious bug, both of you should ASAP open a ticket with support.
What I am curious about here …
Why would anyone use packages from box.mikrotik.com with a very crafted URL unless instructed to do so by support ?
That’s some dev-environment, I think. Normal URLs are download.mikrotik.com.
I mean, we normal users can never now the exact URL for a certain package outside the normal channels so this has to come from support, right ?
EDIT: Ah, I see … it’s the Help page itself this comes from. Sweet … 
Can you write which routeros you were using when you install firmware?
A special package is provided to upgrade the backup RouterBOOT (> DANGEROUS> ). Newer devices will have this new backup loader already installed at the factory. If your RouterOS is v7, your factory-firmware version is lower than 7.18.2 and your device displays the message → > The “protected routerboot” feature requires a backup-routerboot upgrade > ← when trying to enable the feature, do the following:
So you tried to enable protected routerboot and ROS showed you the error message, so you were forced to do the dangerous upgrade?
And if you really enabled protected rooterboot, it is expected to disable the reset button:
I was on 7.18.2 routeros. Did the bb upgrade but did not enable protected routerboot.
The next day i wanted to get back on 7.19rc2 and during that install process it shut down, not to start again.
Will open a support ticket.
I don’t know what is warranty status of your device but i don’t think support can help in your situation. They can avoid only further devices can be bricked.
If your device out of warranty connect over uart/serial port and see what’s going on.
Look serial in this page. https://openwrt.org/toh/mikrotik/rb5009ug_s_in
Yeah i’m out of warranty. Bought it in 2021.
Thanks for the link!
I did not enable protected rooterboot. After uploading the v7 universal package for all architectures and rebooting, the log showed that the firmware update was completed. After rebooting again, I could not enter the router.
I have already sent a ticket：SUP-188707
RB5009UG+S+IN
Here’s another victim. I hope they come up with some fix.