[Samsung Galaxy J7 Prime / J7 On NXT (Exynos7870)] Mightx:
Finally found a solution, albeit with a caveat. For those who can't boot properly on ares reborn included in the rom, try flashing ares 7 treble (not universal and not oneui) and it should work without freezing or bootloop. The only problem is that a message saying "there is an internal problem with your device" will show up on boot but easily ignorable and the gains on kernel control and oc outweigh the slight inconvenience of having to click away a warning message on boot...

Edit 1: It also works with Ares Refreshed v1.1. Preferably use this instead of og ares 7 treble since that one had so many experimental features that are unstable such as 1794MHz cpu oc, 1146MHz gpu oc, and even charging oc.

Edit 2: I found out that any frequency above 1586MHz on the CPU (little or big core regardless) such as 1690MHz would be unstable and freeze and random reboot the phone. Workaround is to flash the kernel and flash magisk then change the cpu settings in hktweaks.

Edit 3: That's weird since 1690MHz on Pie on Helios 3.1 is completely stable. I've tried raising big and little core voltages by +25mV for the meantime to see if it will fix the instability issues. Must also be why some exact model phones may have less degraded silicon that's why they can boot without freezing on these oc'ed kernels.

Edit 4: Nope raising core voltages doesn't help that much. After 30 mins, even if only the big cluster is allowed to boost to 1690 MHz, the phone still reboots. For now just stick to the max frequency on all cores of 1586MHz. Also, stick to the stock preset of HMP as less or more aggressive settings tend to make it unstable again.

Edit 5: Also, even though this rom shows as non-treble in ofox recovery, you need to flash a treble specific kernel to not freeze on the lockscreen. Seems like it should be treble but when flashing universally packed kernel zips, it picks to flash a non-treble one instead so that causes the freeze on lockscreen and auto-reboot.

Edit 6: Flashing ares reborn after flashing the og ares 7 should now work. It will also remove the message warning on boot. Beware though that all instability points mentioned above still remain unresolved on ares reborn.

Edit 7: Also try another cpu governor such as blu-active or ondemand as interactive may become unstable sometimes. And try wiping the dalvik cache after flashing the kernel to possibly avoid phone freezing and/or app crashes as most probably coming from another kernel with mostly stock frequencies like Simple Kernel would be the one wherein the apps are optimized for and they may cause system crashes when you flash an oc kernel like Ares.

Edit 8: I got the cpu oc (1690 little 1690 big cpu) working on ares reborn. Just wipe dalvik cache after flashing it and oc settings should work mostly fine without crashing the system or apps. Also never try overclocking the gpu beyond 1001MHz since 1146 whatever you do will cause freezing and random reboots. Just set max to 1001MHz and put it into interactive not static or booster. Also, 1794 on the big cluster would crash the phone due to thermals. Any way to disable thermal limits for the cpu?

Edit 9: Is it just me or based on my observations the Metallic Blue/Black G610Y models don't handle OC and kernel booting well while the White/Gold G610Y devices are completely fine in terms of kernels and booting but sometimes they can get the zero brightness bug?

Edit 10: Tried to replicate the whole procedure and just in case it was a one-off scenario and oddly enough it didn't work anymore. I just get the same freeze after 5 seconds when booted up on ALL kernels EXCEPT Simple so back again to square one without any workarounds. Oof can't we get a new kernel that plays well with ALL devices?

Edit 11: Don't try my methodology as it has a low chance to work at all and a high chance to bootloop the phone since it's sort of a hit or miss thing going on with Device A, which I talked about in a thread I recently made (be sure to check it out!)

Edit 12: Check my thread on weird observations for G610X for more findings and workarounds!