New to Mikrotik

Hi so I was going to buy the Mikrotik 5gG Chateau D53G model from a guy selling it for someone else. I want to to use this with a 5G SIM as the current router ain’t giving better speeds than my phone. The router appeared to switch off after like a minute. He held the reset button a few times. But it appears that after I put in my SIM it didn’t turn off but the the WiFi light didn’t turn on but signal light was on.

I didn’t know if it was faulty so left it. But am I correct in assuming that we should have connected the router to a laptop/pc with ethernet then enter the config page to enable WiFi?

Any help is appreciated.

As you say, it is an assumption.
Obviously how a device will behave depends on its configuration.
In the case of a brand-new, still in the box, device, its behaviour should be known/repeatable, in theory when doing a reset the default configuration should be the same as new, but in practice for an used device it could boot (or not boot) with any service or interface enabled or disabled, so yes, when looking at an used device the first thing should be to connect to its management interface (also to make sure that user/password is valid) and see how it is set.
That particular model has also been reported as having issues in some cases with default configuration (after reset):
http://forum.mikrotik.com/t/chateau-rbd53g-5hacd2hnd-config-problems/151625/1
and there could have been issues with the upgraded (or not upgraded) OS with the different wifi drivers/packages, see (same model of device):
http://forum.mikrotik.com/t/d53g-5hacd2hnd-update-7-13-no-wifi/171958/1

It’s a used router. What’s the correct way to reset to factory settings?

There is a procedure (lights/flickering/timing/etc. may vary a little bit with models) detailed here:
https://help.mikrotik.com/docs/display/ROS/Reset+Button

Depending on the date the device was manufactured once the device is reset the credentials will be either:
older devices:
user:admin
password:
newer devices:
user:admin
password:<written in teeny-tiny characters on a sticker on the device (and on a sticker on the instructions, if available>

The configuration may be largely blank (for “professional devices”) or a “default one” (for consumer and soho devices), but what happens is that a script is run, so (again it may depend on the model) this base script may have been modified, in this sense a reset to factory may not be a real reset to factory, it is a reset to default configuration, but this default may have been changed.

Maybe an excess of caution, but with used devices, you really never know what may be inside them.

There is another procedure that allows to start from fresh (keeping or not keeping the configuration) called netinstall:
https://help.mikrotik.com/docs/display/ROS/Netinstall
that is often advised as there is the possibility that for whatever reasons there are some “hidden” settings or “corruption” in the filesystem or to clear as much space as possible, as seen in the mentioned thread.

Have the router connected via ethernet and SIM card inserted with 4 bars. Ethernet is blinking, I’m trying to log in with 192.168.88.1 but it doesn’t load the page. Any ideas what I’m doing wrong?

Ok logged in with Mac address, manually updated routeros to latest version. Used this video to enable WiFi. But the light is still not enabled.

https://m.youtube.com/watch?v=KpVNpA7TX10

Follow the instructions here:
http://forum.mikrotik.com/t/forum-rules/173010/1
and post your configuration.

Thanks, will do after work. So about 6 hours from now.

Btw after reboot realises the wireless option disappeared and only showed WiFi and there was no radio and master was in red. I went back to what it was on 7.1.5.

Then I found out you have to install QCOM package. So might try updating again.

The disadvantage of upgrading manually is that you could miss an additional package.
You can add it later any time, just add package.

When upgrading automatically, this won’t happen.

When I tried to update automatically, it gave some DNS error. So I just drag and dropped the update.

# 1970-01-02 00:11:43 by RouterOS 7.15.3
# software id = 
#
# model = D53G-5HacD2HnD
# serial number = 
/interface bridge
add admin-mac= auto-mac=no comment=defconf name=bridge
/interface wireless
# managed by CAPsMAN
set [ find default-name=wlan1 ] band=2ghz-b/g/n channel-width=20/40mhz-XX \
    country="united kingdom" distance=indoors frequency=auto installation=\
    indoor mode=ap-bridge ssid=MikroTik-C4BE8B wireless-protocol=802.11
# managed by CAPsMAN
set [ find default-name=wlan2 ] band=5ghz-a/n/ac channel-width=\
    20/40/80mhz-XXXX country="united kingdom" distance=indoors frequency=auto \
    installation=indoor mode=ap-bridge ssid=MikroTik-C4BE8B \
    wireless-protocol=802.11
/interface lte
# A newer version of modem firmware is available!
set [ find default-name=lte1 ] allow-roaming=no band="" nr-band="" sms-read=\
    no
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wireless security-profiles
set [ find default=yes ] supplicant-identity=MikroTik
/ip pool
add name=default-dhcp ranges=192.168.88.10-192.168.88.254
/queue type
add fq-codel-ecn=no kind=fq-codel name=fq-codel-ethernet-default
/queue interface
set ether1 queue=fq-codel-ethernet-default
set ether2 queue=fq-codel-ethernet-default
set ether3 queue=fq-codel-ethernet-default
set ether4 queue=fq-codel-ethernet-default
set ether5 queue=fq-codel-ethernet-default
/disk settings
set auto-media-interface=bridge auto-media-sharing=yes auto-smb-sharing=yes
/interface bridge port
add bridge=bridge comment=defconf interface=ether1
add bridge=bridge comment=defconf interface=ether2
add bridge=bridge comment=defconf interface=ether3
add bridge=bridge comment=defconf interface=ether4
add bridge=bridge comment=defconf interface=ether5
add bridge=bridge comment=defconf interface=wlan1
add bridge=bridge comment=defconf interface=wlan2
/ip neighbor discovery-settings
set discover-interface-list=LAN
/interface list member
add comment=defconf interface=lte1 list=WAN
add interface=ether1 list=WAN
add interface=ether2 list=LAN
add interface=ether3 list=LAN
add interface=ether4 list=LAN
add interface=ether5 list=LAN
add interface=wlan2 list=LAN
add interface=wlan1 list=LAN
/interface wireless cap
# 
set bridge=bridge enabled=yes interfaces=wlan2,wlan1
/ip address
add address=192.168.88.1/24 comment=defconf interface=ether2 network=\
    192.168.88.0
/ip dhcp-server
add address-pool=default-dhcp interface=bridge name=defconf
/ip dhcp-server network
add address=192.168.88.0/24 comment=defconf dns-server=192.168.88.1 gateway=\
    192.168.88.1
/ip dns
set allow-remote-requests=yes
/ip dns static
add address=192.168.88.1 comment=defconf name=router.lan
/ip firewall filter
add action=accept chain=input comment=\
    "defconf: accept established,related,untracked" connection-state=\
    established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=\
    invalid
add action=accept chain=input comment="defconf: accept ICMP" protocol=icmp
add action=accept chain=input comment=\
    "defconf: accept to local loopback (for CAPsMAN)" dst-address=127.0.0.1
add action=drop chain=input comment="defconf: drop all not coming from LAN" \
    in-interface-list=!LAN
add action=accept chain=forward comment="defconf: accept in ipsec policy" \
    ipsec-policy=in,ipsec
add action=accept chain=forward comment="defconf: accept out ipsec policy" \
    ipsec-policy=out,ipsec
add action=fasttrack-connection chain=forward comment="defconf: fasttrack" \
    connection-state=established,related hw-offload=yes
add action=accept chain=forward comment=\
    "defconf: accept established,related, untracked" connection-state=\
    established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" \
    connection-state=invalid
add action=drop chain=forward comment=\
    "defconf: drop all from WAN not DSTNATed" connection-nat-state=!dstnat \
    connection-state=new in-interface-list=WAN
/ip firewall nat
add action=masquerade chain=srcnat comment="defconf: masquerade" \
    ipsec-policy=out,none out-interface-list=WAN
/ipv6 firewall address-list
add address=::/128 comment="defconf: unspecified address" list=bad_ipv6
add address=::1/128 comment="defconf: lo" list=bad_ipv6
add address=fec0::/10 comment="defconf: site-local" list=bad_ipv6
add address=::ffff:0.0.0.0/96 comment="defconf: ipv4-mapped" list=bad_ipv6
add address=::/96 comment="defconf: ipv4 compat" list=bad_ipv6
add address=100::/64 comment="defconf: discard only " list=bad_ipv6
add address=2001:db8::/32 comment="defconf: documentation" list=bad_ipv6
add address=2001:10::/28 comment="defconf: ORCHID" list=bad_ipv6
add address=3ffe::/16 comment="defconf: 6bone" list=bad_ipv6
/ipv6 firewall filter
add action=accept chain=input comment=\
    "defconf: accept established,related,untracked" connection-state=\
    established,related,untracked
add action=drop chain=input comment="defconf: drop invalid" connection-state=\
    invalid
add action=accept chain=input comment="defconf: accept ICMPv6" protocol=\
    icmpv6
add action=accept chain=input comment="defconf: accept UDP traceroute" \
    dst-port=33434-33534 protocol=udp
add action=accept chain=input comment=\
    "defconf: accept DHCPv6-Client prefix delegation." dst-port=546 protocol=\
    udp src-address=fe80::/10
add action=accept chain=input comment="defconf: accept IKE" dst-port=500,4500 \
    protocol=udp
add action=accept chain=input comment="defconf: accept ipsec AH" protocol=\
    ipsec-ah
add action=accept chain=input comment="defconf: accept ipsec ESP" protocol=\
    ipsec-esp
add action=accept chain=input comment=\
    "defconf: accept all that matches ipsec policy" ipsec-policy=in,ipsec
add action=drop chain=input comment=\
    "defconf: drop everything else not coming from LAN" in-interface-list=\
    !LAN
add action=accept chain=forward comment=\
    "defconf: accept established,related,untracked" connection-state=\
    established,related,untracked
add action=drop chain=forward comment="defconf: drop invalid" \
    connection-state=invalid
add action=drop chain=forward comment=\
    "defconf: drop packets with bad src ipv6" src-address-list=bad_ipv6
add action=drop chain=forward comment=\
    "defconf: drop packets with bad dst ipv6" dst-address-list=bad_ipv6
add action=drop chain=forward comment="defconf: rfc4890 drop hop-limit=1" \
    hop-limit=equal:1 protocol=icmpv6
add action=accept chain=forward comment="defconf: accept ICMPv6" protocol=\
    icmpv6
add action=accept chain=forward comment="defconf: accept HIP" protocol=139
add action=accept chain=forward comment="defconf: accept IKE" dst-port=\
    500,4500 protocol=udp
add action=accept chain=forward comment="defconf: accept ipsec AH" protocol=\
    ipsec-ah
add action=accept chain=forward comment="defconf: accept ipsec ESP" protocol=\
    ipsec-esp
add action=accept chain=forward comment=\
    "defconf: accept all that matches ipsec policy" ipsec-policy=in,ipsec
add action=drop chain=forward comment=\
    "defconf: drop everything else not coming from LAN" in-interface-list=\
    !LAN
/system note
set show-at-login=no
/system routerboard mode-button
set enabled=yes on-event=dark-mode
/system script
add comment=defconf dont-require-permissions=no name=dark-mode owner=*sys \
    policy=ftp,reboot,read,write,policy,test,password,sniff,sensitive,romon \
    source="\r\
    \n   :if ([system leds settings get all-leds-off] = \"never\") do={\r\
    \n     /system leds settings set all-leds-off=immediate \r\
    \n   } else={\r\
    \n     /system leds settings set all-leds-off=never \r\
    \n   }\r\
    \n "
/tool mac-server
set allowed-interface-list=LAN
/tool mac-server mac-winbox
set allowed-interface-list=LAN

But now, with the appropriate qcom package installed, the wifi is running, right?

No. Well I installed RouterOS with netinstall but it doesn’t install QCOM, says failed.

This is strange.
A package like qcom should be installabile in any moment (i.e. also after the installation of the main routeros package).
Maybe you can try a new netinstall, making available both the routeros and qcom package.

I done that and when I go to package, system, package, QCOM is greyd out. I enable it and it says scheduled for enable.

Wait a minute, the d53g is this one:
https://mikrotik.com/product/chateau_5g
it is an AC device, it should use the wifi-qcom**-ac** package, not the wifi-qcom, which is for AX devices.
It is confusing, but read carefully:

https://help.mikrotik.com/docs/display/ROS/Packages

Well some good news and bad news. Flashed QCOM AC instead of just QCOM and the WiFi started working.

But the randomly reboots. Well if playing a long YouTube video or doing a speed test. This is with WiFi and WiFi disabled. Like when it’s under load? Wth heck is that all about!?

There may be some settings that need to be changed/tuned, but it shouldn’t reboot by itself.
The configuration you posted indicates:

# managed by CAPsMAN

that wifi settings are managed by capsman, but us this the case? (i.e. do you really have anothe Mikrotik device that is controlling this one?)

Post a new export of your current configuration.

So far no more reboots. It appears a third party underpowered adapter was provided
https://postimg.cc/TyY8pZ94

This doesn’t happen with a Zyxcel 12v 4a adapter.

Yep.
Your device specs:
DC jack input Voltage 12-28 V
Max power consumption 23 W
Max power consumption without attachments 17 W
would require no less than 17/12=1.42A@12V or 17/24=0.71A@24V
or - better - 23/12=1.92A@12V or 23/24=0.96A@24V
Still, if Mikrotik sells with it a power supply with 1.2A@24V, they may have their reasons.
This one should be the original one:
https://mikrotik.com/product/saw30_240_1200gr2a