Root Bootloader Unlock & Back to Stock for Motorola E4 Plus "owens"

ocnbrze · Jul 4, 2019

hmmmmm it seems like you are doing everything correct according to the guide. it also could be that my linux is very bad. or its the booze affecting my brain......i don;t know. anyways, i have pm'ed the op.......so hopefully we can others to help out.

bcrichster · Jul 4, 2019

OK, I'm here! I'm the one that posted the XT1776 mmcblk0.img for Owens but it is from the Sprint update 44-12 patch..
The XT1775 mmcblk0.img security patch level, I'm unsure. If your phone was updated to a newer patch than the mmcblk0.img was written with, that'll keep you from booting too.

doodalydoo said:
I did prepare the SD card using Linux. The only deviation from the guide was when it came to "open as root", but the guide also says you can get around using it by altering the terminal command.

1st: YES, OPEN TERMINAL AS ROOT (right click next to image file, select "open as Root", then right click again, "open terminal" and go from there), this is needed for a special permissions level, critical factor, indeed.

doodalydoo said:
I used the first one because that was what my SD card matched. The code as written didn't work. It gave me an error saying no file existed, which is why I had to drag and drop to get the path to the file and replace the bold part of the code with it
(sudo dd bs=4M if=mmcblk0.img of=/dev/sdb status=progress oflag=sync)

the right clicking "in folder that has ur mmcblk0.img" idea will keep you from needing to drag&drop anything. The actual file writing will take several minutes when everything is writing correctly. Insert the card to bricked phone and plug it in hole holding PWR &vol down at same time, should boot right up into bootloader mode. If bootloader boots, remove sdcard IMMEDIATELY & BEFORE flashing stock FW or your sdcard will be rewritten with like 20 partitions instead of the files flashing to actual owens device, Lol

doodalydoo · Jul 4, 2019

bcrichster said:
OK, I'm here! I'm the one that posted the XT1776 mmcblk0.img for Owens but it is from the Sprint update 44-12 patch..
The XT1775 mmcblk0.img security patch level, I'm unsure. If your phone was updated to a newer patch than the mmcblk0.img was written with, that'll keep you from booting too.

1st: YES, OPEN TERMINAL AS ROOT (right click next to image file, select "open as Root", then right click again, "open terminal" and go from there), this is needed for a special permissions level, critical factor, indeed.

the right clicking "in folder that has ur mmcblk0.img" idea will keep you from needing to drag&drop anything. The actual file writing will take several minutes when everything is writing correctly. Insert the card to bricked phone and plug it in hole holding PWR &vol down at same time, should boot right up into bootloader mode. If bootloader boots, remove sdcard IMMEDIATELY & BEFORE flashing stock FW or your sdcard will be rewritten with like 20 partitions instead of the files flashing to actual owens device, Lol

I do not have the "open as root" option in the context menu. Which Linux should I use? I'm currently using Linux Mint Cinnamon as suggested in the guide.

bcrichster · Jul 5, 2019

doodalydoo said:
I do not have the "open as root" option in the context menu. Which Linux should I use? I'm currently using Linux Mint Cinnamon as suggested in the guide.

Try Mint4Kitchen or mint Cinnamon 19.0.. You won't make any headway until you can use that option successfully

doodalydoo · Jul 6, 2019

bcrichster said:
Try Mint4Kitchen or mint Cinnamon 19.0.. You won't make any headway until you can use that option successfully

Good news, it worked. I did this with Ubuntu, which you will have to dual boot if you are running Windows. The guide states you can use a Linux live usb, but there is not enough storage to extract the 30+ gb file on those. You could probably use a virtual machine as well, but I couldn't set one up to work for this.

Right click the folder the .img file is located at
Click open terminal here
Type sudo su and enter password
Run the command from the guide to transfer the file

I also found out the phone has to be recognized by the computer as a usb device for this to work, so if it does not work make sure you can find your phone in the device manager. On Windows you need to download the Qualcomm usb drivers for a bricked phone to be recognized. It will show up under COM Ports in the device manager. I'm not sure how this works in Linux.This is probably specific to my phone, but my phone would become unrecognizable by my computer occasionally and I would have to unplug the battery cable and plug it back in for it to be recognized again. So if you are unable to get your computer to recognize the phone, you may have to simply remove some screws to get to the battery. Here are the instructions to do it: https://www.ifixit.com/Guide/Motorola+Moto+E4+Plus+Back+Plate+and+Battery+Replacement/106041

bcrichster · Jul 6, 2019

doodalydoo said:
Good news, it worked. I did this with Ubuntu, which you will have to dual boot if you are running Windows. The guide states you can use a Linux live usb, but there is not enough storage to extract the 30+ gb file on those. You could probably use a virtual machine as well, but I couldn't set one up to work for this.

Right click the folder the .img file is located at

Click open terminal here

Type sudo su and enter password

Run the command from the guide to transfer the file

I also found out the phone has to be recognized by the computer as a usb device for this to work, so if it does not work make sure you can find your phone in the device manager. On Windows you need to download the Qualcomm usb drivers for a bricked phone to be recognized. It will show up under COM Ports in the device manager. I'm not sure how this works in Linux.This is probably specific to my phone, but my phone would become unrecognizable by my computer occasionally and I would have to unplug the battery cable and plug it back in for it to be recognized again. So if you are unable to get your computer to recognize the phone, you may have to simply remove some screws to get to the battery. Here are the instructions to do it: https://www.ifixit.com/Guide/Motorola+Moto+E4+Plus+Back+Plate+and+Battery+Replacement/106041

Great to hear! If you've a version with unlockable bootloader, we have many ROMs for you..

doodalydoo · Jul 7, 2019

bcrichster said:
Great to hear! If you've a version with unlockable bootloader, we have many ROMs for you..

Any idea why OTA updates don't install now that I have flashed stock? I get an error when the phone reboots into recovery to install the update. I'm not rooted and I don't have any custom recoveries installed.

bcrichster · Jul 7, 2019

doodalydoo said:
Any idea why OTA updates don't install now that I have flashed stock? I get an error when the phone reboots into recovery to install the update. I'm not rooted and I don't have any custom recoveries installed.

It's quite possible you installed FW that wasn't specific to your carrier

doodalydoo · Jul 7, 2019

bcrichster said:
It's quite possible you installed FW that wasn't specific to your carrier

The phone doesn't have cell service right now, but the phone is carrier unlocked.

bcrichster · Jul 7, 2019

doodalydoo said:
The phone doesn't have cell service right now, but the phone is carrier unlocked.

Regardless of whether it's Carrier Unlocked.. Like if you bought a Metro Phone and installed Cricket or Boost FW on it, it'll give you OTA errors. Anything is possible. I've manually installed OTA's just fine after flashing correct Carrier FirmWares

doodalydoo · Jul 7, 2019

bcrichster said:
Regardless of whether it's Carrier Unlocked.. Like if you bought a Metro Phone and installed Cricket or Boost FW on it, it'll give you OTA errors. Anything is possible. I've manually installed OTA's just fine after flashing correct Carrier FirmWares

I installed the Retail version. Isn't that the firmware for unlocked phones?

bcrichster · Jul 7, 2019

doodalydoo said:
I installed the Retail version. Isn't that the firmware for unlocked phones?

Not necessarily. The specific FW actually depends on the model # & Carrier was bought from. Like Boost/Sprint devices were xt1776, metro/T-Mo is xt1775, etc..

doodalydoo · Jul 7, 2019

bcrichster said:
Not necessarily. The specific FW actually depends on the model # & Carrier was bought from. Like Boost/Sprint devices were xt1776, metro/T-Mo is xt1775, etc..

Are you sure that's right? I have the XT1775 and it isn't attached to any carrier.

bcrichster · Jul 7, 2019

doodalydoo said:
Are you sure that's right? I have the XT1775 and it isn't attached to any carrier.

totally sure.. I believe you actually have the T-Mo/Metro variant but if you want to force the OTA's from retail, just flash their newest posted FW from lolinet (posted in my "back to Stock " thread

doodalydoo · Sep 24, 2019

Sorry to bump an old thread, but I just finally got around to putting a sim card in the phone after unbricking it and cell service does not work. IMEI, baseband, etc are all unknown. The phone doesn't even recognize the SIM card.

covid · Jun 29, 2020

Flashing is not working for me. This is what I got.

D:\fastboot final>fastboot flash gpt gpt.bin
(bootloader) has-slot:gpt: not found
(bootloader) is-logical:gpt: not found
Sending 'gpt' (45 KB) OKAY [ 0.172s]
Writing 'gpt' (bootloader) Validating 'gpt.
default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed

D:\fastboot final>fastboot flash bootloader bootloader.img
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.334s]
Writing 'bootloader' (bootloader) Validating 'boot
loader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.544s]
Finished. Total time: 1.243s

D:\fastboot final>fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
(bootloader) is-logical:modem: not found
Sending 'modem' (73891 KB) OKAY [ 2.496s]
Writing 'modem' OKAY [ 0.659s]
Finished. Total time: 3.370s

D:\fastboot final>fastboot flash fsg fsg.mbn
(bootloader) has-slot:fsg: not found
(bootloader) is-logical:fsg: not found
Sending 'fsg' (1120 KB) OKAY [ 0.194s]
Writing 'fsg' OKAY [ 0.066s]
Finished. Total time: 0.507s

D:\fastboot final>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
Erasing 'modemst1' OKAY [ 0.024s]
Finished. Total time: 0.241s

D:\fastboot final>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
Erasing 'modemst2' OKAY [ 0.024s]
Finished. Total time: 0.237s

D:\fastboot final>fastboot flash dsp adspso.bin
(bootloader) has-slot:dsp: not found
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.693s]
Writing 'dsp' OKAY [ 0.177s]
Finished. Total time: 1.111s

D:\fastboot final>fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
(bootloader) is-logical:logo: not found
Sending 'logo' (1386 KB) OKAY [ 0.208s]
Writing 'logo' OKAY [ 0.068s]
Finished. Total time: 0.518s

D:\fastboot final>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.691s]
Writing 'boot' (bootloader) Image signed wit
h key bad key
OKAY [ 0.304s]
Finished. Total time: 1.241s

D:\fastboot final>fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.699s]
Writing 'recovery' (bootloader) Image signed wit
h key bad key
OKAY [ 0.337s]
Finished. Total time: 1.278s

D:\fastboot final>fastboot flash system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (511914 KB) OKAY [ 16.812s]
Writing 'system' OKAY [ 4.104s]
Finished. Total time: 21.150s

D:\fastboot final>fastboot flash system system.img_sparsechunk.1
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (508182 KB) OKAY [ 16.703s]
Writing 'system' OKAY [ 4.106s]
Finished. Total time: 21.040s

D:\fastboot final>fastboot flash system system.img_sparsechunk.2
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (510802 KB) OKAY [ 16.690s]
Writing 'system' OKAY [ 3.890s]
Finished. Total time: 20.809s

D:\fastboot final>fastboot flash system system.img_sparsechunk.3
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (512872 KB) OKAY [ 16.845s]
Writing 'system' OKAY [ 3.778s]
Finished. Total time: 20.855s

D:\fastboot final>fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (524286 KB) OKAY [ 17.114s]
Writing 'system' OKAY [ 4.189s]
Finished. Total time: 21.527s

D:\fastboot final>fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (524286 KB) OKAY [ 17.012s]
Writing 'system' (bootloader) Failed to valida
te sparse image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed

D:\fastboot final>fastboot flash oem oem.img_sparsechunk.0
(bootloader) has-slot :eek:

em: not found
fastboot: error: cannot load 'oem.img_sparsechunk.0': No such file or directory

D:\fastboot final>fastboot flash oem oem.img_sparsechunk.1
(bootloader) has-slot :eek:

em: not found
fastboot: error: cannot load 'oem.img_sparsechunk.1': No such file or directory

D:\fastboot final>fastboot erase cache
(bootloader) has-slot:cache: not found
Erasing 'cache' OKAY [ 0.016s]
Finished. Total time: 0.322s

D:\fastboot final>fastboot erase userdata
(bootloader) has-slot:userdata: not found
Erasing 'userdata' OKAY [ 0.088s]
Finished. Total time: 0.294s

D:\fastboot final>fastboot erase ddr
(bootloader) has-slot:ddr: not found
Erasing 'ddr' (bootloader) Permission denie
d
FAILED (remote: '')
fastboot: error: Command failed

D:\fastboot final>fastboot oem fb_mode_clear
OKAY [ 0.118s]
Finished. Total time: 0.127s

D:\fastboot final>fastboot reboot
Rebooting OKAY [ 0.005s]
Finished. Total time: 0.009s

amarc78 · Jul 3, 2020

covid said:
Flashing is not working for me. This is what I got.

D:\fastboot final>fastboot flash gpt gpt.bin
(bootloader) has-slot:gpt: not found
(bootloader) is-logical:gpt: not found
Sending 'gpt' (45 KB) OKAY [ 0.172s]
Writing 'gpt' (bootloader) Validating 'gpt.
default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote: '')
fastboot: error: Command failed

D:\fastboot final>fastboot flash bootloader bootloader.img
(bootloader) has-slot:bootloader: not found
(bootloader) is-logical:bootloader: not found
Sending 'bootloader' (5179 KB) OKAY [ 0.334s]
Writing 'bootloader' (bootloader) Validating 'boot
loader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'emmc_appsboot.mbn' to 'aboot'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'prov.mbn' to 'prov'
(bootloader) - flashing 'sbl1.mbn' to 'sbl1'
OKAY [ 0.544s]
Finished. Total time: 1.243s

D:\fastboot final>fastboot flash modem NON-HLOS.bin
(bootloader) has-slot:modem: not found
(bootloader) is-logical:modem: not found
Sending 'modem' (73891 KB) OKAY [ 2.496s]
Writing 'modem' OKAY [ 0.659s]
Finished. Total time: 3.370s

D:\fastboot final>fastboot flash fsg fsg.mbn
(bootloader) has-slot:fsg: not found
(bootloader) is-logical:fsg: not found
Sending 'fsg' (1120 KB) OKAY [ 0.194s]
Writing 'fsg' OKAY [ 0.066s]
Finished. Total time: 0.507s

D:\fastboot final>fastboot erase modemst1
(bootloader) has-slot:modemst1: not found
Erasing 'modemst1' OKAY [ 0.024s]
Finished. Total time: 0.241s

D:\fastboot final>fastboot erase modemst2
(bootloader) has-slot:modemst2: not found
Erasing 'modemst2' OKAY [ 0.024s]
Finished. Total time: 0.237s

D:\fastboot final>fastboot flash dsp adspso.bin
(bootloader) has-slot:dsp: not found
(bootloader) is-logical:dsp: not found
Sending 'dsp' (16384 KB) OKAY [ 0.693s]
Writing 'dsp' OKAY [ 0.177s]
Finished. Total time: 1.111s

D:\fastboot final>fastboot flash logo logo.bin
(bootloader) has-slot:logo: not found
(bootloader) is-logical:logo: not found
Sending 'logo' (1386 KB) OKAY [ 0.208s]
Writing 'logo' OKAY [ 0.068s]
Finished. Total time: 0.518s

D:\fastboot final>fastboot flash boot boot.img
(bootloader) has-slot:boot: not found
(bootloader) is-logical:boot: not found
Sending 'boot' (16384 KB) OKAY [ 0.691s]
Writing 'boot' (bootloader) Image signed wit
h key bad key
OKAY [ 0.304s]
Finished. Total time: 1.241s

D:\fastboot final>fastboot flash recovery recovery.img
(bootloader) has-slot:recovery: not found
(bootloader) is-logical:recovery: not found
Sending 'recovery' (16484 KB) OKAY [ 0.699s]
Writing 'recovery' (bootloader) Image signed wit
h key bad key
OKAY [ 0.337s]
Finished. Total time: 1.278s

D:\fastboot final>fastboot flash system system.img_sparsechunk.0
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (511914 KB) OKAY [ 16.812s]
Writing 'system' OKAY [ 4.104s]
Finished. Total time: 21.150s

D:\fastboot final>fastboot flash system system.img_sparsechunk.1
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (508182 KB) OKAY [ 16.703s]
Writing 'system' OKAY [ 4.106s]
Finished. Total time: 21.040s

D:\fastboot final>fastboot flash system system.img_sparsechunk.2
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (510802 KB) OKAY [ 16.690s]
Writing 'system' OKAY [ 3.890s]
Finished. Total time: 20.809s

D:\fastboot final>fastboot flash system system.img_sparsechunk.3
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (512872 KB) OKAY [ 16.845s]
Writing 'system' OKAY [ 3.778s]
Finished. Total time: 20.855s

D:\fastboot final>fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (524286 KB) OKAY [ 17.114s]
Writing 'system' OKAY [ 4.189s]
Finished. Total time: 21.527s

D:\fastboot final>fastboot flash system system.img_sparsechunk.4
(bootloader) has-slot:system: not found
(bootloader) is-logical:system: not found
Sending 'system' (524286 KB) OKAY [ 17.012s]
Writing 'system' (bootloader) Failed to valida
te sparse image
(bootloader) Preflash validation failed
FAILED (remote: '')
fastboot: error: Command failed

D:\fastboot final>fastboot flash oem oem.img_sparsechunk.0
(bootloader) has-slotem: not found
fastboot: error: cannot load 'oem.img_sparsechunk.0': No such file or directory

D:\fastboot final>fastboot flash oem oem.img_sparsechunk.1
(bootloader) has-slotem: not found
fastboot: error: cannot load 'oem.img_sparsechunk.1': No such file or directory

D:\fastboot final>fastboot erase cache
(bootloader) has-slot:cache: not found
Erasing 'cache' OKAY [ 0.016s]
Finished. Total time: 0.322s

D:\fastboot final>fastboot erase userdata
(bootloader) has-slot:userdata: not found
Erasing 'userdata' OKAY [ 0.088s]
Finished. Total time: 0.294s

D:\fastboot final>fastboot erase ddr
(bootloader) has-slot:ddr: not found
Erasing 'ddr' (bootloader) Permission denie
d
FAILED (remote: '')
fastboot: error: Command failed

D:\fastboot final>fastboot oem fb_mode_clear
OKAY [ 0.118s]
Finished. Total time: 0.127s

D:\fastboot final>fastboot reboot
Rebooting OKAY [ 0.005s]
Finished. Total time: 0.009s

Looks like your flashing an older firmware than what was already on your phone. You need to make sure your not downgrading like it says for the bootloader and that your flashing the exact same, or newer firmware. And that name you made for yourself is just not right.

Root Bootloader Unlock & Back to Stock for Motorola E4 Plus "owens"

DON'T PANIC!!!!!!!!!

ROMinator

Newbie

ROMinator

Newbie

ROMinator

Newbie

ROMinator

Newbie

ROMinator

Newbie

ROMinator

Newbie

ROMinator

Newbie

Lurker

Newbie

BEST TECH IN 2023

Smartphones

Best Android Phones

Upcoming

Best iPhones

Upcoming

Tablets

Best Tablets

Upcoming

Laptops

Best Laptops

Upcoming

Televisions

Best TVs

Upcoming

Game Consoles

Best Game Consoles

Upcoming

Wearables

Best Wearables

Upcoming

Smart Home

Smart Home Tech

Upcoming

Similar threads