[Moto Z2 Force  Questions & Answers] KOAO:
Actually, shockingly, yes. I was. And it works. I did **** up the first few tries through trial and error, but currently I am using the Sprint Z2 Force on Verizon, running Verizon firmware with everything running. Glitches and all the same from a Z2 Force that would come with Verizon. Hell, you even get their bloat! Truly the Verizon Experience with the addition of Root and an Unlocked bootloader.

Doing this, I'd assume you have sim unlocked it and unlocked the Bootloader of your Z2 Force . Also note that this wipes EVERYTHING, SO BACK UP.

Also note that considering I was stunned when it worked, it's possible I missed a step while writing this up so again, have a window of time to be free. And a backup phone of possible.

The way I did it, is first prepping to have a few hours of your time because it could take a while. Set up like 2 or so hours where no one is going to call you on your phone since you'll need your Sim in the Z2 in case anything goes wrong.

Then, you need to download the latest Verizon Z2 Force Firmware. You don't have to technically do this, but updating is going to be a pain since you aren't going to be allowed to take OTA's (more on that later.) So just get the one with the January Security Patch as that is the most recent one

Here is the Verizon Firmware. Just sort by date to the most recent one for this year, there is only one lol.

https://mirrors.lolinet.com/firmware/moto/nash/official/VZW/

Next is download the flashall utility. You aren't going to use the flashall.bat, but adb is in there. Extract the Verizon firmware into that flash all folder. From there, assuming you have adb debugging and all, boot into the bootloader.

Once you have everything prepped, follow this guide here. The first one, with wipe

https://xdaforums.com/z2-play/how-to/fastboot-rom-flash-update-stock-rom-t3838213

But, if you don't want to open another tab, here are the instructions. There is an important thing to note. The Verizon Firmware has it's OEM in 2 chunks, as opposed to the single .img file the others do. In this case you would run the fastboot oem, drag oem chunk 0 into cmd and run it, then run fastboot oem again and do the same for oem chunk 1 from the folder you are performing everything from. I also think we are missing sparsechunks 6-10, so just follow the steps for what files you have and ignore the ones you don't. We also have system sparse chunk b's, two files, to flash as well. We seem to have a few files others don't.

Run these commands one by one.

fastboot getvar max-sparse-size

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot flash dsp adspso.bin

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system_b system_b.img_sparsechunk.0

fastboot flash system_b system_b.img_sparsechunk.1

fastboot flash oem oem.img_sparsechunk.0

fastboot flash oem oem.img_sparsechunk.1

fastboot erase cache

fastboot erase carrier

fastboot erase ddr

fastboot erase userdata

fastboot oem fb_mode_clear

fastboot reboot

Do not forget to run fastboot oem fb_mode_clear, otherwise you will boot into fastboot at every reboot.

After that, everything should be working. It worked for me I'll try to help if anything goes wrong but I hope that doesn't happen.

That said, an important note about updates and OTA's. Our Z2 Force is not a real Verizon Z2 Force. Something internally, most likely the fact it's not certified and is the same reason it doesn't show up in Verizon's site as an offical Z2 Force, is the reason we cannot take OTA's. If an Update were to come out for our phone, we would need to download the latest firmware. Once someone can get the latest OTA from Verizon for us, we then have to use the same ADB method to update our devices.

The steps for updating without deleting data are in the link to the thread above, but here are the commands for doing so without wiping data. Again, reminder that our flash oem is in two chunks, And we don't have sparsechunks 6-10.

fastboot getvar max-sparse-size

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot flash dsp adspso.bin

fastboot flash logo logo.bin

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash system system.img_sparsechunk.5

fastboot flash system_b system_b.img_sparsechunk.0

fastboot flash system_b system_b.img_sparsechunk.1

fastboot flash oem oem.img_sparsechunk.0

fastboot flash oem oem.img_sparsechunk.1

fastboot erase cache

fastboot erase carrier

fastboot oem fb_mode_clear

fastboot reboot

Again, do not forget to run fastboot oem fb_mode_clear. I cannot stress this enough because I nearly said "**** this ****" because of this simple command that I forgot to copy in. This is what puts our phone into it's state to flash firmware. So disable it once you are done.

I would assume that this would also work for flashing the Sprint to a true unlocked version. I was tempted to test it, since the unlocked retail versions get updates first and are already on the latest March Security patch. But, I was stopped because I could not find the retail firmware anywhere. The link for the retail in this thread 404'd, so this is the next best thing.

I did encounter an anomaly once everything was said and done. The phone app wasn't showing up once I had all my apps set up. I had to find it, clear the cache, and for good measure disabled and re-enabled it and it never disappeared/stopped responding again. I did end up using Magisk to install the Google Dialer framework and am using that with no issues. Aside the issue that I can't download it from the playstore, so I had to download it from a reputable site.

Note that I never had sprint service on it, so anything related to that or battery life on the sprint rom is something I have no clue about. But, I seem to get very good battery life on it.

I posted some screen shots below.