[Samsung Galaxy J7 Questions & Answers] Droidriven:
If anyone has anything they would like to add to what I am posting in order to be more specific or definitive of what I am attempting to discuss, please, do not hesitate to post it.

There are things encoded at the hardware level that do not get changed or flashed when flashing Samsung devices, there are hardware components that have their own independent "firmware", so to speak. These components retain their original firmware regardless of what you flash on the device's internal memory(this is very similar to the BIOS chip in your PC that stays the same regardless of what OS you install or how many times you wipe the system and reinstall the OS). If the software that we flash on the internal storage does not pass the signature/security checks encoded in these components that have independent firmware at first boot, the device becomes software-bricked or can even be hardware-bricked. In other words, there are hardware components that are checking the bootloader to verify it is the correct bootloader, if not verified, the device fails to boot at that point(this usually results in a hard-brick), if verified, the bootloader checks the software that it is about to boot, if verified by the bootloader, the device continues to boot, if not verified, the device fails to boot at that point(this usually results in a soft-brick, but can potentially hard-brick). Software-brick is potentially repairable, hardware-brick is not repairable without new hardware replacements or expensive external hardware components and software tools for PC and some rather complicated methods to perform a hard-brick recovery.

In some ways and some instances, it can be a mixture of hardware level checks, bootloader checks and kernel checks before it even gets to attempting to boot at the software level. If these checks don't all agree with each other, the device cannot function properly, sometimes, not at all.

All of this is to say that 1 of 2 things will likely happen when flashing Refine firmware on our devices.

1) our locked bootloader will possibly block the install due to the refine firmware not passing our bootloader's signature/security checks.

Or

2) the firmware might successfully flash without any errors but will potentially brick the device on first boot due to not passing the bootloader's signature/security checks.

If you feel like being a trailblazer, take the chance yourself and see if it works. The rest of us choose to not take the chance in order to prevent a "worst case" scenario.

Side note****

I would like to know how they got Modaco Superboot to unlock bootloader on a Samsung device. Modaco superboot uses fastboot commands to achieve it's purpose. Now, here's the real question, how did they get fastboot to do anything to a Samsung device when Samsung devices do not even have fastboot functionality, no fastboot mode, no bootloader mode? Samsung has it's own version of "bootloader mode" but it isn't the same thing as the "fastboot related" bootloader mode. On Samsung it's called Download Mode which is only compatible with specific tools, not fastboot.

ADB works perfectly fine on Samsung, but fastboot can't do anything with Samsung.