Hi all.
on Friday 12 nov 2021 , TWO routers Groove 52HPn were updated long term firmware and after that they are cyclically rebooted.
The reset button does not solve the problem.
Attempts to switch to the firmware download mode over the netinstall also have no result.
Presumably the new firmware was version 6.48.5.
At the end of the supposed boot cycle, a barely audible click of the system speaker is heard.
Video of attempts to download and reset the device can be viewed at the link https://youtu.be/xeHibH4PJQU
What can be the solution to this problem ?
ps.
I have been systematically working with RouterOS and Mikrotik hardware for about 12 years with a large fleet of equipment of the same name.
I have experience downloading firmware using the netinstall.
ROS 6.48.5 is known to be problematic on several device models (there are many reports in relevant thread in announcements part of this forum). Netinstall is needed to unbrick device. After unbricking, devices seem to run fine with very same version of ROS.
netinstall does not work for me, router refuses to enter etherboot mode.
As soon as interface tries to up, there is a barely audible click and a reboot occurs.
On all my many routers, updates have always occurred without problems.
This case makes me think about the likelihood of dig a grave for my networks after these updates.
Majority of failed netinstalls is due to inexperience and wrong setup. Please, try it first with a known working router. If router works fine, netinstall should work as well - that is your test benchmark. If it does not work, adjust your setup. Once you make it working with a good router, simply switch routers and try the same with a bad router - likely it will work straight away.
My first netinstall experience for example also failed. In my case it was because I did not disable all other interfaces (bt/wifi/virtual etc) in the control panel. Once I left only one interface enabled, netinstall worked straight away. This step is not described in the official manual and may be common reason of a failure.
Solution has been found. Simple solution.
One router unbricked.
managed to upload firmware using typical procedure netinstall.
I used a switch (or hub) to connect between Groove and a PC.
If you connect router directly to the PC, the PC interface does not have time to see router, which is already going to reboot.
I think this will be relevant for win users. Haven’t tested this on a linux.
Thanks to everyone who responded.
ps . remains to unbrick second router ))
I had to climb 8 meters mast for both routers
pps . second router alive also
