I’ve managed to brick the HEX POE. It is self induced with a reset without backup or default configuration checked in reset configuration. I’ve tried all methods of reset but it won’t boot past a solid blue power light. The ethX lights are very dim. It is a “modern” board without any jumpers or “iron” jumper for the “screwdriver”. Any ideas? Thanks
If you only used reset in software, download Winbox an connect per mac
Thanks. I can not connect to it at all - no direct Winbox or Netinstall. It powers up but does not boot to bring the ETHx ports up. Thus, I can’t connect to it.
The reset on my hex was tricky. I had to push the reset PIN down first, then plug in the power and wait for the yellow light TO BLINK then let go of the pin reset.
So it may be just how you are doing the reset. Not sure how the poe model differs?
Thank you. POE HEX has the side reset button. HEX has the push pin on the back. I never get the yellow light. It just powers up blue power light and hangs with nothing to follow. The older boards had A) jumper or B) brass contact to connect across to reset bios. Think of resetting a motherboard bios with a screwdriver across the pins. This HEX has neither that I can see.
From Quick Guide:
Buttons and jumpers
Reset button
The RouterBOOT reset button has the following functions. Press the button and apply the power, then:
• Release the button when a green LED starts flashing, to reset RouterOS configuration to defaults.
• Release the button when the LED turns solid green to clear all configuration and bridge all interfaces.
• Release the button after LED is no longer lit (~20 seconds) to cause a device to look for Netinstall servers
(required for reinstalling RouterOS over the network).
Regardless of the above option used, the system will load the backup RouterBOOT loader if the button is pressed
before power is applied to the device. Useful for RouterBOOT debugging and recovery.
https://i.mt.lv/cdn/rb_files/1569921393RBhEX%20Poe.pdf
Try to load the backup RouterBOOT according to the above information.
Jumper or brass contact have same functionality as reset button.
“dim lights” usually mean voltage problems, in that case you will not get any link on LAN ports, so there is no way to fix this using software.
There are UART pads on the PCB, you can connect 3.3V UART to USB adapter (or logic analyzer or scope) and see if you get anything on TX pin (there is no BIOS you can enter, but often you get at least some boot messages if the board is alive).
But “dim leds” is are usually indicating some hardware damage, like voltage regulators not running or dead chip that shorts the VCC to ground.
Check voltages on all big caps, inspect all SMDs or PCB traces for any damage (use magnifier or microscope).
If the CPU is getting very hot, it’s dead. If you see any voltage over 3.3V around the CPU, board is dead thanks to failed voltage regulator.
It helps if you have another board that works and can compare voltages side by side…
Thanks all for the responses. I’m going to declare a voltage regulator issue and not take the time to prove it out. Hex PoE RB750Gr3 gave it’s life in a test environment. But, this does cause concern as we are a free WiFi marketing startup and have two of these in production at our 1st two clients. They are both the non POE version RB750Gr3. The topic of this chain is HEX PoE RB960PGS. Our provider’s solution for existing non-Mikrotik AP infrastructure is Mikrotik routers. Based on what others have told us, Microtik is rock solid. Any router using the provider has to have OS native hotspot ability for a captive portal. Thus, that rules out Edge for instance.
We are not CLI gurus 
We like the free IP-Cloud/CHR feature compared to other manufacturer products, but are concerned we have not been able to IP-Cloud to them behind a NAT.
I have another post on that: http://forum.mikrotik.com/t/ip-cloud-dynamic-ip-wan-behind-nat/140416/1