[Moto E5 Guides, News, & Discussion] sfl899:
This exact thing happened to me at the stage of flashing, except I proceeded further even after the errors(which persisted on half of the files like recovery, all sparse chunks),stopping at some point of the instructions.

phone still functional, but not rooted, nor flashed, or is it?

The phone constantly has to boot from AP Fastmode without any button input, it automatically loads AP FastMode. I stalked the forums and decided to try to follow motorollas instructions on legitimately unlocking after a failed attempt at this flashing from the thread, and the AP Fastboot loop started. (Specifically before the commands from this forum;and after entering their "fastboot oem unlock_data" command instructions)

Note that months ago i did install and uninstall twrp successfully from my phone, and the files for twrp still remain, yet its still uninstalled as well. please help with any commands that can reset my ap fastmode loop back to default,and either fully flash or lock my device again. I dont like this twlight to softbrick,

I did try to download Android Multi Tools from an outside article,and almost got rootkitted with a dropper,but thats kind of irrelevant.(stating this so that no one falls for those assorted guides ,recommending the rootkit infected "cmd tool") they said they were gsm and blahblaaah, trying to sound legit. Please, do not go seeking the file I just mentioned, as the "original software" originated in 2017,perhaps just as infected as it is now.

FINAL EDIT, SELF RECOVERY, HOPE THIS HELPS EVERYONE:

So for those of you having the same issue as me; realizing that at this time, Motorola did do a security patch update between this month of August, you'll know that root capabilities and possibilities have been thwarted again. whether the failures come from gpt.bin,sparse,or recovery ,out of these three failures, if your phone starts doing what mine did (essentially it was on its way towards legit brick mode), endlessly looping into AP FASTBOOTMODE,this is how you fix it.

This is a legitimate way to fix AP FASTBOOT MODE BOOT LOOP, THIS IS NO WAY fixing any current bricked phones beyond repair or beyond ADB access , or corrupted IMG partitions that extend more full than the flashing methods above here. If you realized how Cricket screwed us over, and stopped at some point doing the flash here because of the AP FASTBOOT LOOP MODE, these instructions are for you. REGARDLESS OF WHAT HAPPENS, IM NOT RESPONSIBLE FOR CURING YOUR PHONE WHATSOEVER, ABSOLVED OF ANY DAMAGE DONE PRIOR TO FOLLOWING THESE INSTRUCTIONS, IM ABSOLVED AND 100% NOT RESPONSIBLE FOR ANYTHING YOU EVEN DO ON YOUR DEVICE. this is a method for those who have the similar issue I did trying to unlock flash for root capabilities without Motorola bootloader accepting it. Here we go:

Phone MUST have USB debugging on, along with the dev option of OEM Unlock turned on. OEM unlocking option will turn off on vanilla reboot of your files and original os state, HOWEVER in this instance, you want to turn unlocker on even if it's for this one time and even if it reverts later, turn the damn option on. It has limited capabilities that I'm secretly learning of myself. Don't have time to exploit it reverse engineer, however...anyways, after oem unlocked,USB debugging on,follow these steps :

~~~~~~~~~

Directory into ADB (C:/...)

fastboot oem fb_mode_set

fastboot restart bootloader (I reset the bootloader 3x personally,but at your discretion)

fastboot erase cache

(fastboot restart bootloader [OPTIONAL,pay attention to the screen of the phone and follow along with it's patterns of boot] )

fastboot oem fb_mode_clear

Thank you to anyone who attempted at trying to help me before posting. You guys are heros.