[Moto E3 Guides, News, & Discussion] Infinite resurrection:
Awesome post brother! I only wish I had simply read this post before messing up so much with my phone. Actually, I was messing with some magisk module (edxposed) whick bricked my device and got me stuck at a bootloop and with no recovery partition at all. (It erased my TWRP). So I used the sp flash tool and formatted the whole flash (at that time, I hadn't read this post of yours). Then I flashed my entire firmware back via the sp flash tool. So I thought that now my problem was fixed. But when I switched on my phone I saw my phone's IMEI Number gone! And the sim not working and showing invalid IMEI message. So I tried to find a fix on the internet and I found 2 solutions. First was using an app which requires the phone to support some mtk engineering mode. I followed the instructions and realised that maybe our phone Moto E3 Power doesn't support this mode. So I switched to the second solution, which required root access. So then I set off for rooting my newly unbricked phone. But I again did some mistakes:

1.) Allowed usb debugging and OEM unlocking in my phone's developer options in settings.

2.) I installed minimal ADB v1.4.3 on a windows 10 computer. Checked my phone's connection with the PC via ADB command adb devices. It worked showing some error initially (daemon not started.... Starting daemon...) and then showing some hex code signifying my device's successful connection with the PC.

3.) Used ADB command adb reboot bootloader to boot into fastboot mode. It worked too.

3.) Used fastboot command fastboot devices to check if my device is still being recognised as connected to the pc. Here came an error (the command didn't return any hex code like the adb command adb devices did. So I googled a solution which involves updating the "Android ADB interface" to "Android Bootloader interface" in the "Android device" submenu of the "Device Manager" window of the "control panel" of the pc, by updating its drivers using the "latest windows usb drivers" 8mb file which could be found very easily on the internet (searching solution for fastboot device drivers update on Google). {*Note: If you hadn't installed beforehand, any adb and fastboot drivers at all, then you will see "Other devices" submenu instead of the "Android device" submenu in the device manager window.

Also, you compulsively need to be in fastboot mode with your device attached to pc, in order to see this "other devices" submenu.} So now the fastboot devices command started working by showing the hex code like adb devices command did.

4.) Used fastboot oem unlock command to unlock the phone's bootloader. Pressed the volume up button of my phone as instructed by the warning message on my phone's screen. Unlock flow started in the minimal adb window in my pc. Finished successfully within 9-13 seconds. Another mistake now, after unlocking the bootloader, I forgot to format userdata.. Actually I didn't know about the fastboot format userdata command. I thought the fastboot -w reboot is the only way to format userdata (which wasn't working for me). Unaware of the fact that now I was going to experience a bootloop during rebooting my phone, I continued with the further steps.

5.) Used fastboot flash recovery recovery.img command to flash the unofficial twrp img which I had already placed in the minimal adb folder and renamed to recovery.img I used unofficial twrp v3.1.1 (by moderator) [which was working perfectly earlier on my phone] {link at bottom}. Successfully finished this step too. [You can use either of the two twrp: Dr. Faramroze (link provided by op) or moderator (link provided by me). Both are working fine]

6.) Used the fastboot reboot command (although it never works for me). It shows finished in the minimal adb cmd screen but the phone doesn't reboot. So I manually unplugged the device. Removed and reinserted the battery.

7.) Now rebooted to recovery screen and found the unofficial twrp successfully installed. [ Warning: After the 6th step, don't reboot your phone normally. Instead, boot into the fastboot window [hold power + vol. up] and select the boot into recovery option. This is required only for the first boot up process or else if you do a normal boot during the first boot, the stock recovery replaces our recently flashed custom recovery..

8.) Upon entering the twrp recovery during the first boot, I installed the magisk v19.3 zip I had in my external SD card. It's not necessary to root your phone right now, you may even do it later by simply rebooting from within the twrp, and later on entering recovery after your phone is all set and working and when you're free from other hassles. But I went for rooting during the first boot. And encountered an error something like: "Cannot mount data(0mb)" at the second last line. So, I could not root my phone. So I decided to root it later on and currently just have it switched on. So, I went for the reboot option in twrp.

9.) My phone started rebooting and got stuck at the boot screen with the tag Device unlocked at the lower left corner (indicating unlocked bootloader). But this was something familiar to me, I had already dealt with this error the previous time I rooted my phone. The solution was very simple. I just had to flash a no verity-otp-encrypt.zip file {included along with the twrp link} using the twrp recovery and then my device would boot properly, as it did the last time.

10.) I flashed the no verity-otp-encrypt.zip file from the twrp and got so many red line errors during the flash. (This didn't happen the last time). Every error had the same words, "cannot mount data (0mb)". So I went back to try rebooting again.

11.) Started rebooting again. This time the device didn't get stuck at boot screen, rather it went into a bootloop, rebooting again and again. Now maybe the no verity-otp-encrypt.zip file did its job and my device got free from the stuck at boot screen problem but simultaneously got caught by the bootloop error probably created due to not formatting the userdata after unlocking the bootloader. Or maybe the "cannot mount data (0mb) just ruined up my phone. Whatever the cause be, I just went for reflashing the entire firmware via the sp flash tool and temporarily forgetting all the bootloader unlocking, custom recovery, rooting, etc and live with an invalid IMEI phone without a working sim, until I find a solution on the internet.

12.) And then, I ended up here on this thread leaving my experience, and learning my mistakes from the OP's post. Very soon I will depart for the cyber cafe to try again without any mistakes this time.

At last thanks for this awesome thread.

And yes here's the link for the unofficial twrp 3.1.1 (by moderator) & the no verity-otp-encrypt.zip file:

https://drive.google.com/folderview?id=1-CHJtDUyPH1CJHebhKsUJz8SzKJAcDbv

---------- Post added at 12:56 PM ---------- Previous post was at 12:41 PM ----------

Search Google for "Moto E3 power firmware flash file" and you will come across websites providing the flash file. The file would have a name like "Motorola_Moto_E3_Power_XT1706_MT6735M_S135_161108_6.0.1.zip". The "S135" over here is the firmware version and will vary upon the version uploaded by the site. The latest version as of today is S152_190315. I somehow managed to download a S151 file and I forgot where I downloaded it from. But you can still go for older firmware versions, and then when you're done with all the flashing and rooting and all that and your phone starts up without any error, you can go for OTA updates from within the settings>about phone>system update.