• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

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

But I still get errors when flashing some files... Then when I reboot it doesn't turn on... I may have done something wrong... Can I just update it with OTA updates to get full stock or would that be a bad idea?

Have you tried the twrp zip I provided in OP? Remove sdcard before flashing tho
 
Upvote 0
No, just boot to fastboot/bootloader mode only, then remove sdcard and flash stock ROM via fastboot cmds. Once completed, reboot
Success! It now works without the SD card. Thanks for the help. The only thing now is the 'bad key' and no access to the stock recovery...lol
Honestly as long as the phone turns on and works on WiFi I'm happy... I have to wait and see if it will accept a SIM tho.
 
Upvote 0
Success! It now works without the SD card. Thanks for the help. The only thing now is the 'bad key' and no access to the stock recovery...lol
Honestly as long as the phone turns on and works on WiFi I'm happy... I have to wait and see if it will accept a SIM tho.

Right on, no problem! Simply hit the Thanks/like (heart) button and/or Best Answer of the post(s) that helped ya the most
 
Last edited:
  • Like
Reactions: insanetoker89
Upvote 0
Success!

My system was on NCRS26.58-44-3 having installed the January update from WiFi. The new files you posted were accepted and I was able to lock the bootloader!

One comment:
I followed the entire sequence in OP; no signature errors reported, but both "boot" and "recovery" got the result "(bootloader) Image signed with key bad key".
Then tried to re-lock using "fastboot oem lock". I had this exchange (I removed the recurring "not found" messages):
C:\OWENS_SPRINT_NCRS26.58-44-3>fastboot oem lock
(bootloader) WARNING: This command erases all user data.
(bootloader) Please re-run this command to continue.
OKAY [ 0.203s]
finished. total time: 0.208s
C:\OWENS_SPRINT_NCRS26.58-44-3>fastboot oem lock
(bootloader) Flash valid Android images now
(bootloader) Then re-run this command to lock
OKAY [ 0.206s]
finished. total time: 0.206s
C:OWENS_SPRINT_NCRS26.58-44-3>fastboot oem lock
(bootloader) Still require signed boot.img
OKAY [ 0.188s]
finished. total time: 0.193s
C:OWENS_SPRINT_NCRS26.58-44-3>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.658s]
writing 'boot'...
OKAY [ 0.697s]
finished. total time: 1.365s
C:\OWENS_SPRINT_NCRS26.58-44-3>fastboot oem lock
(bootloader) Still require signed system.img and/or oem.img
OKAY [ 0.197s]
finished. total time: 0.202s​
Given this broad hint from fastboot, I then re-sent the 6 chunks of system and 2 chunks of oem, just to be sure. After that I locked once more and all was well:
C:\OWENS_SPRINT_NCRS26.58-44-3>fastboot oem lock
(bootloader) Lock complete! Flash signed images after reboot if needed
OKAY [ 0.349s]
finished. total time: 0.354s
C:\OWENS_SPRINT_NCRS26.58-44-3>fastboot oem fb_mode_clear
OKAY [ 0.172s]
finished. total time: 0.177s​
Full power off and on again, the system booted without "bad key"!

I strongly suspect that the flashing of everything (possibly except boot) initially was unnecessary. The optimal sequence is most likely to start with "fastboot oem fb_mode_set" and "fastboot oem lock" (the latter twice), then flash all the pieces, then the final "fastboot oem lock" and "fastboot oem fb_mode_clear".

I still need to get the device on the network and let in install the later updates from Boost, that would confirm completely that it's back to stock and lock (I suspect there is still a way to see that it had been unlocked).


Thanks again bcrichster!

So your steps to lock the bootloader are as follows?

oem lock
oem lock
oem lock
flash boot.img
oem lock
6 chunks system
2 chunks oem
oem lock
oem fb mode clear
 
Upvote 0
So your steps to lock the bootloader are as follows?

oem lock
oem lock
oem lock
flash boot.img
oem lock
6 chunks system
2 chunks oem
oem lock
oem fb mode clear

I think I seen something like that before, fortunately the terminal will direct you. I wouldn't lock the bootloader cuz ya may be screwing the next person. 'bad key' just means bootloader is unlocked, nothing more
 
Upvote 0
MOTO E4 PLUS XT1776

I put this Together from some of my trial & errors plus some info from a few threads on XDA, Hope this helps you as much as me

Bootloader Unlock:
WARNING: UNLOCKING YOUR BOOTLOADER VOIDS YOUR WARRANTY.PROCEED AT YOUR OWN RISK.
NOTE: Unlocking the bootloader will Wipe/ factory reset your device, and will delete all personal data from your device such as apps, photos, messages, and settings.

INSTRUCTIONS:

  1. Make sure to take a backup of your entire device data.
  2. Download the Android SDK OR Download the Minimal ADB and Fastboot
  3. Install the latest Motorola USB Drivers on your desktop found here: http://www.mymotocast.com/download/MDM?platform=windows.
  4. Put your device in fastboot mode (power off, then press the power and volume down buttons simultaneously).
  5. Open Command Prompt on androidsdk/platform-tools/ (Hold Shift and right click and press open command window here)
  6. Connect your Phone to PC
  7. Type this in the CMD prompt window - fastboot devices
  8. If all's well, you'll get a short string return..
  9. Next, type this in the CMD window - fastboot oem get_unlock_data
  10. You will get a return string. Copy it. [Right Click-Mark- Mark the text by pressing the shift key-Now press Ctrl+C]
  11. Paste all the lines together in a notepad. Remove the empty spaces ONLY.
  12. Now go to the Motorola Site.: https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-b ..Sign in using your Google account or Motorola ID. Scroll down the page and paste the copied string in the field at step #6. Then click on ‘Can my device be unlocked?’, after which a "REQUEST UNLOCK KEY" button will appear at the bottom of page.
  13. To get your unlock key, select the ‘I Agree’ option. Note: You will receive an email with your Unlock Key at the email address you used to log in there.
  14. Important – Copy the 20-character key that Motorola sent you via email. Make sure your device is connected.
  15. Then in CMD type: fastboot devices (To check your device is connected)
  16. Then type: fastboot oem unlock UNIQUE_KEY

    NOTE: In above command, replace the word ‘UNIQUE_KEY’ with the unlock code that you got via email. Then hit enter and the unlocking process should begin. Wait for a while and soon you’ll see ‘Bootloader Unlocked’ warning on your Moto E.

    To relock the bootloader:

    Go to Fastboot and give the command -
  • fastboot oem lock
Motorola Tutorial -

Check recovery/ TWRP image:
In terminal, type or copy/paste:
  • fastboot boot recovery.img
Flash recovery/TWRP image:
In terminal, type or copy/paste:
  • fastboot flash recovery recovery.img

  1. Now press the volume buttons (while still in fastboot mode) until ya see RECOVERY MODE, then press pwr button and it'll boot into TWRP.
  2. Wipe only the caches and reboot right back to recovery. Yes, You need to do reboot recovery to help set it or the device will otherwise swap TWRP with the Stock Recovery and you'll have to reflash again.
  3. Adjust TWRP Settings/preferences, like enable md5sum checking. Do NOT enable "rm -rf"..trust me, Lol.
  4. Reboot Recovery last time and MAKE A BACKUP!!
OK.. When ya wipe data to remove encryption:
  • Format 1st (type YES & hit enter)
  • Immediately afterwards do a normal data swipe, you'll get red lettering and it'll protest and ask ya to reboot for data function but instead of a normal rebooting, you should..
  • Directly reboot recovery and repeat until all red lettering and warnings cease
  • Now you can install ROMs at leisure without issues
Completely back to Stock.

First get your stock firmware here, the only place to get Moto stock firmware.

WINDOWS:

Then get fastboot. Google fastboot or grab the one from here, This one still works:
https://www.androidfilehost.com/?fid=962339331459002428

Copy the extracted files to you ADB/Fastboot installaton folder (usually in like, C:windows/programfiles/x86/minimal-adb_whatever)
- or -
Go to the folder where you put everything, open up a command or powershell prompt. Hold down shift, right click, "open command window here".

You can copy/paste the entire thing and past it in your command window at one time or even type it out.... line by line.
Start by checking to see if the PC sees the device:

fastboot devices


Commands:

fastboot oem fb_mode_set
fastboot flash gpt gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 oem oem.img_sparsechunk.0
fastboot flash oem oem.img_sparsechunk.1
fastboot erase cache
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot


LINUX:
No drivers to stress or anything. Just extract the Firmware zip, open the folder and right-click inside to open a terminal and use these commands. They're the same thing as above, just the added word "sudo". You can copy/paste the entire thing and past it in your command terminal at one time or even type it out.... line by line.
Start by checking to see if the PC sees the device:

sudo fastboot devices


Commands:

sudo fastboot oem fb_mode_set
sudo fastboot flash gpt gpt.bin
sudo fastboot flash bootloader bootloader.img
sudo fastboot flash modem NON-HLOS.bin
sudo fastboot flash fsg fsg.mbn
sudo fastboot erase modemst1
sudo fastboot erase modemst2
sudo fastboot flash dsp adspso.bin
sudo fastboot flash logo logo.bin
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img_sparsechunk.0
sudo fastboot flash system system.img_sparsechunk.1
sudo fastboot flash system system.img_sparsechunk.2
sudo fastboot flash system system.img_sparsechunk.3
sudo fastboot flash system system.img_sparsechunk.4
sudo fastboot flash system system.img_sparsechunk.5
sudo fastboot flash oem oem.img_sparsechunk.0
sudo fastboot flash oem oem.img_sparsechunk.1
sudo fastboot erase cache
sudo fastboot erase userdata
sudo fastboot erase ddr
sudo fastboot oem fb_mode_clear
sudo fastboot reboot


======================================
** Sources **

If this helped or ya like my work, plz hit Thanks in the OP's (1st post). :cool:

While donating is not required to use this Guide, it's certainly appreciated.
DONATIONS:
https://www.paypal.me/bcrichster
.
.
.
.
.
.
.
.

Hey bro I'm having a slight problem, when I go into the bootloader the software status says "modified" how can I get it back to normal if possible? thanks
 
Upvote 0

Attachments

  • IMG_20181205_123402196.jpg
    IMG_20181205_123402196.jpg
    353.7 KB · Views: 389
Upvote 0
Hey bro I'm having a slight problem, when I go into the bootloader the software status says 'modified' how can I get it back to normal if possible? thanks

You'd have to go 100% back to stock and relock the bootloader.. it's not worth it because we get so much more with Root and custom ROMs. We can keep getting security updates or possible OS upgrades whereas we never know with stock. And TWRP? It's something we should always have, no matter what. I wish devices shipped with it, Lol.
 
Upvote 0
You'd have to go 100% back to stock and relock the bootloader.. it's not worth it because we get so much more with Root and custom ROMs. We can keep getting security updates or possible OS upgrades whereas we never know with stock. And TWRP? It's something we should always have, no matter what. I wish devices shipped with it, Lol.

I did go completely back to stock, still shows as modified...
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones