To change device-mode setting you need to power off or press reset after issuing that first command.
Not simply reboot.
Did you ?
The device-mode can be changed by the user, but remote access to the device is not enough to change it. After changing the device-mode, you need to confirm it, by pressing a button on the device itself, or perform a "cold reboot" - that is, unplug the power. When the change is confirmed, regardless of confirmation mode, the device will be rebooted !
The topic seems quite suspicious.
Is it possible that you can't read what appears in the terminal after the commands?
Was "failure: not allowed by device-mode" read and not everything else?
And then "having the dreaded [..] error"...
"dreaded"??? So it's so well-known that we already know the reason...
To me, the post just looks like something AI invented to add spam.
All I can say is that no, I am not AI and I did not engineer this situation for any nefarious purpose.
If you want to know the background, I am setting up a VLAN tunnel to get a WAN connection into my router in a Unifi network. My Unifi switch is for some reason cutting the speed of the connection by 50%, which is why I installed the Mikrotik. On the way to this forum post, I’ve spent several days troubleshooting and trying to get this working. I bricked my Mikrotik switch and had reflash using the recovery mode utility.
So to answer your question, no. I am not AI. I did not use a LLM to generate this post, and yes, I am very grateful that I was able to receive the answer I was looking for (that I hasn’t powered off the device to get the change to take).
Our local Script Cat Wizard did exaggerate a bit , but what surprises me as well is that you have to issue this command from terminal.
It DOES throw you a prompt on screen what to do next after changing that device-mode setting.
Power-off or push reset or press mode button within x seconds.
(mode button only possible for device that have it)
Guys (and Gals, let's stay bias free ),
I am new here, but doing IT tasks since 1983 .... when you go deep in the rabbit hole and at 3 in the morning the router blaring you reboot me and press the button might go unnoticed. I bricked a Cisco 2511 in 1994 because I missed a prompt ...
So here no harm done and with the benefit of the doubt somebody's issue has been solved.
Cheers