[Moto G4 Plus Guides, News, & Discussion] echo92:
1)Xposed normally wouldn't stop an OTA from appearing, but would interfere with an installation as the OTA would detect the presence of custom system software, causing the update to likely fail. Having Xposed on your device means SafetyNet fails - depending on what apps you use, this may or may not matter, but any apps (e.g. banking, Snapchat, Pokemon Go) that depend on Google's anti-tampering detection passing may not work unless Xposed is disabled. Magisk hide does not appear to hide Xposed.

2)Hmm, unless your device is not XT1644, I'm not sure how else the NPJS25.93-14-10 firmware would have been flashed onto the device. If it's a US device, with a US SIM in, I imagine receiving an OTA not for your software channel would be unlikely.

I had a look at the NPJ25.93-14.7 stock ROM and looks like the checksums for the GPT and bootloader are different compared to the NPJS25.93-14-10 stock ROM. Though both are the same build version B1:06 and so flashing may be straightforward, I don't know how significant the differences between both ROMs' bootloaders is and thus if flashing is completely safe (since bootloaders seem to be a common cause of bricks). Also, I'm not sure if your existing bootloader would block a flash of the NPJ25.93-14.7 bootloader or they're sufficiently similar that your bootloader would permit flashing the other firmware's bootloader.

In theory you could flash the rest of the NPJ25.93-14.7 firmware (excluding the GPT/bootloader) so you're on the US firmware with US modems. That should enable OTA updates (as the servers should detect you have a US build on retUS) however taking an OTA may be risky as your bootloader may still be the NPJS25.93-14-10 version rather than the NPJ25.93-14.7 US version if the bootloader didn't flash properly. The process you've outlined otherwise looks okay - it's just the matter of cross flashing that I'm not happy with, in terms of keeping your device safe and working, particularly with the bootloaders.

Perhaps the safest route, if you really wish to flash US retail firmware, would be to wait for the US retail NPJ25.93-14.7-3, which would then bring your bootloader and GPT and the rest of your device formally to the December 2017 US retail build (with the newer bootloader and GPT fully flashing onto your device rather than the piecemeal block patching from the OTA updates), and should then be okay for OTA updates (or you could flash TWRP, ElementalX, magisk and xposed instead). Else, you could stay on the NPJS25.93-14-10 firmware stream, updating to NPJS25.93-14-13 when you're ready and hopefully, when Oreo comes out, Motorola will unify the builds again between the different regions as they did with Nougat.

If anyone else has any ideas, feel free to chip in.

---------- Post added at 01:55 AM ---------- Previous post was at 01:50 AM ----------

If you've hard bricked and are trying to get your GPT/bootloader working, you could try flashing either the December 2017 stock ROM in the opening post or the December 2017 GPT and bootloader from here: https://drive.google.com/open?id=1IfAX7v94ooB5wS7KTJGNYfQ2kXkHxP80

---------- Post added at 02:06 AM ---------- Previous post was at 01:55 AM ----------

If you've flashed the stock ROM, then boot into the stock ROM. In Settings>About Phone, tap the build number 7 times. Go to the newly activated Settings>Developer Options and enable OEM unlocking.

Now, you should be able to re-flash with the OEM locking commands and lock your bootloader without the 'image signed with bad key' warnings for your boot/recovery. Unless you're getting a different error?

Bear in mind that re-locking your bootloader will not restore your Motorola warranty, though depending on the service centre, the type of repair and local laws, you may get your device repaired as though it was under warranty. Your experience may vary.

Also, re-locking your bootloader will wipe your device again (hence the two fastboot OEM lock begin commands). If you so wish, you could disable OEM unlocking if you are happy with your device after re-locking the bootloader. This would prevent anyone with physical access from unlocking your bootloader, including you. However, if your device then fails to boot with OEM unlocking disabled, you may have very limited options for repairs besides going to the service centre. I would suggest leaving the OEM unlocking enabled so you could unlock your bootloader and flash a custom ROM, but be aware anyone with physical access to your device could do the same.