[Moto G4 Plus Guides, News, & Discussion] echo92:
Good to hear you got your device working again.

Yep, the commands I gave you do not lock the bootloader - you need the fastboot OEM locking commands as I mentioned, which are in the script/command list in the first opening post of this thread. The two OEM lock begin commands will erase your device, so move backups off your device.

Before you flash to re-lock your bootloader, you should boot your device with the stock firmware and enable OEM unlocking as I describe here: https://xdaforums.com/showpost.php?p=74971791&postcount=497 That way, you should be able to re-lock your bootloader and if anything happens, you'll be able to unlock your bootloader and get your device booting. It's entirely up to you if after re-locking your bootloader you choose to disable OEM unlocking for increased security, but be aware if you do disable that toggle and you have device issues, there's not much we can do about it with a locked bootloader, and you'll have no way to unlock it as the toggle is off. Furthermore, you have no warranty.

I would recommend using all the commands, starting from fastboot OEM lock begin. Though you may be certain your device is clean and fully stock, a locked bootloader is very stringent and will check that each of the key partitions match the signatures it expects - any unknown signatures and it may well block your device from booting. By full flashing the same firmware onto your device, you minimise the risks of a failed boot. If that occurs, you can try re-locking with the NPJS25.93-14-13 firmware (Dec 2017) or if you had OEM unlocking enabled earlier, then you can unlock your bootloader and flash another ROM.

Re-locking your bootloader should hide the bootloader warning, bear in mind Motorola has a record of warranty being voided against your IMEI and thus a locked bootloader may still mean you have to pay for repairs if you have to take your device to a service centre. Again, it depends on the service centre and the nature of the repair, as well as any local warranty/consumer laws.

As I mentioned in the post above, I do not know if the NPJS25.93-14-10/NPJS25.93-14-13 builds are meant for retla regions, regardless of if they flash okay. If they are deployed in retla too, then you should expect to get OTA updates, and as your device should be on the same patch level, they should be safe to use - the risk comes from having mismatched bootloaders and systems, which with a locked bootloader is not likely (incidentally, OTAs don't appear to care about bootloader locked status).

If NPJS25.93-14-10/NPJS25.93-14-13 are builds not deployed on the retla software channel, then you may have to manually update, as the Motorola servers would not recognise those builds for your particular software channel and so your device would continue to report it's on the latest build. With the lack of information for retla builds, I don't know what the latest build for that region is. I can only hope that if you find yourself in this situation, that the upcoming Oreo build will merge software channels to the same build (as what happened with Nougat with NPJ25.93-14) and thus put you back onto the OTA update path.