Mikrotik Chateau LTE12

RouterOS General
1

Hi everyone,

we would love to get some help on this. We’ve bought Mikrotik Chateau LTE12 in the company and someone set it up with LTE backup and it worked perfectly for 14 days already. And then it just decided to go crazy. We’ve already switched the power adapter and so on.

I’ve tried to factory reset it 6 times already, but the computer gets a weird default DHCP IP (usually it’s 192.168.88.1, it even says in “get started” that it should be like this), but I get 169.254.253.37 for instance, no gateway (seems like some Windows default IP).

Neither netInstall nor Winbox detected the modem, no ping response from 192.168.88.1 (with static IP settings).

Has anyone had similar issues or something? Not even the SIM card gets detected properly, the signal bar is not showing with dots as it was before. Does it mean it’s really dead or is it perhaps set in some weird mode by a customer accidentally?

Thank you all very much

2

The fact your PC gets an ip in the 196.254.x.y range, indicates to me that device is not acting as DHCP server which it would if it were set to factory config.
Which I believe means it is not factory reset but reset without config.
Can you try again ?
Power on and immediately press reset (might take 2 persons to get it right).
Hold this button during boot time until the LED light starts flashing, then release the button to reset the RouterOS configuration (should take about 5 seconds).

You might be able to use winbox/MAC to get in ?
You may have to set a manual IP on your network port to get winbox working.

3

Hi, it is for sure factory reseted, as we’re working with Mikrotics for a long time. You let go of reset button while main light is flashing. It does.

After a bit more research, it seems to be a bootloop after update (even tho we don’t remember updating the Mikrotik). http://forum.mikrotik.com/t/chateau-5g-boot-loop-netinstall-not-working/151624/4

And the same, we’re having the problem that Mikrotik is not showing up in Winbox or netinstall, neither versions that were menitoned in the post up… We don’t know whats up with this mikrotik, this kind of bugs in OSes shouldn’t happen :confused:

4

So it appears to be stuck in netinstall mode ?
Then perhaps someone did hold on to reset for too long …

Already tried the backup boot loader (press reset BEFORE power on and keep it held until device appears in netinstall window).
Some users have reported success when using first netinstall using (ouch …) 6.49.10 version but I’m not sure that’s a good idea here.
Maybe try 7.12 latest beta ? You can always downgrade afterwards.

Personal opinion: I prefer Linux for netinstall. Much better success rate (for me).

5

After few hours of tossing it around, I have managed to save it. I’ve used RouterOS netInstall v7.12beta7, configured another Mikrotik to default (192.168.88.1), attached my PC to 192.168.88.2, netBooting to 192.168.88.3, held reset button for about 20 seconds, till it poped up in netInstalled and flashed 7.12beta7-arm image. Thank god. Mikrotik, please release more stable OSes next time.