[TWRP][owens] TWRP for Moto E4 Plus (Qualcomm)

Magendanz

Senior Member
Mar 25, 2008
667
580
123
Issaquah, WA
www.Vote4Chad.com
WARNING: Don't do factory reset or update from system

This version of TWRP is not reading and clearing the bootloader control block (BCB). So, if you do a factory reset via Settings->Backup & Reset->Factory Data Reset, you'll be stuck in a TWRP bootloop.

The quick workaround is to reboot to bootloader, then proceed from there to Start. However, you'll need to do this *every* time until the BCB is cleared.

To clear the BCB manually, issue this command in TWRP terminal:

Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M
Or alternatively, just issue the following command from the bootloader:

Code:
fastboot erase misc
@ReimuHakurei: I tried to fix a similar problem with a non-standard BCB offset on Rockchip devices. The BOARD_RECOVERY_BLDRMSG_OFFSET makefile variable is used to set BCB offset for command-line arguments in the /misc partition. However, the code to convert it to the precompiler directive was removed. I submitted a change to restore it in an appropriate context, but I don't believe it was ever checked in.
 
Last edited:

hofs1

Senior Member
Jan 3, 2009
90
21
8
Ok so i have 2 E4 Plus unlocked from Amazon (no ads) i ran the boot loader unlock and both unlocked...... I then did the root method following the guide for the E4 and used the recovery image in this thread.....all hell broke loose i had a bunch of error when installing Magisk even just doing a cache clear in twrp would always say " failed to mount data" etc etc. Then the phone went int a twrp loop and would not boot the os......All i would get was a tiny N/A in top left corner OR i could fastboot TWRP But do nothing else.

I tried too many times but finally gave up. I decided to try the 2nd phone which all went much smoother and this time i only flashed the noverity zip and Magisk I did NOT format data this time and all seems ok.......i booted a few times all good

EXCEPT i keep getting a tiny N/A in top left corner durring boot BUT it boots fine
I then did a twrp backup and "moved " the back up to the BAD phone and did a restore and boom its back to normal
Both units boot with the n/a in top corner.

any ideas why i get that message?????
 
V

volatile1

Guest
Ok so i have 2 E4 Plus unlocked from Amazon (no ads) i ran the boot loader unlock and both unlocked...... I then did the root method following the guide for the E4 and used the recovery image in this thread.....all hell broke loose i had a bunch of error when installing Magisk even just doing a cache clear in twrp would always say " failed to mount data" etc etc. Then the phone went int a twrp loop and would not boot the os......All i would get was a tiny N/A in top left corner OR i could fastboot TWRP But do nothing else.

I tried too many times but finally gave up. I decided to try the 2nd phone which all went much smoother and this time i only flashed the noverity zip and Magisk I did NOT format data this time and all seems ok.......i booted a few times all good

EXCEPT i keep getting a tiny N/A in top left corner durring boot BUT it boots fine
I then did a twrp backup and "moved " the back up to the BAD phone and did a restore and boom its back to normal
Both units boot with the n/a in top corner.

any ideas why i get that message?????
That n/a screen is what you get instead of the normal bootlogo after unlocking the bootloader. It's perfectly normal.

Sent from my Moto E (4) Plus using XDA Labs
 

hofs1

Senior Member
Jan 3, 2009
90
21
8
That n/a screen is what you get instead of the normal bootlogo after unlocking the bootloader. It's perfectly normal.

Sent from my Moto E (4) Plus using XDA Labs
Thats what i was hoping it was So thanks for that info!!!!!

I now after some googling see that some have made a flashable e4 bootlogo that helps hide the N/A not sure if it applies to the E4 Plus
 
V

volatile1

Guest
Thats what i was hoping it was So thanks for that info!!!!!

I now after some googling see that some have made a flashable e4 bootlogo that helps hide the N/A not sure if it applies to the E4 Plus
The tutorial for making logos and the pre-made logos in the E4 thread will work just fine for the Plus. I just flashed the BlueBot logo to be sure.

Sent from my Moto E (4) Plus using XDA Labs
 

Daltonyx

Senior Member
Jan 17, 2013
54
3
8
Aubrey
After using twrp and whatnot, I ended up not having an OS due to me effing up. lol. My bad. Now, after using the retail.zip and fastboot flashing all of it back, the SECOND it boots I get hit with com.android.phone has stopped, rendering the phone inoperable. Help? :( I just got the dang thing. I want it to work. lol
 
V

volatile1

Guest
After using twrp and whatnot, I ended up not having an OS due to me effing up. lol. My bad. Now, after using the retail.zip and fastboot flashing all of it back, the SECOND it boots I get hit with com.android.phone has stopped, rendering the phone inoperable. Help? :( I just got the dang thing. I want it to work. lol
Did you flash the full firmware or only the system? How did you flash it? It looks like your not the only one this has happened to.

Sent from my Moto E (4) Plus using XDA Labs
 

Daltonyx

Senior Member
Jan 17, 2013
54
3
8
Aubrey
Only partially I guess. I can't find an RSD that works on Win10 nor a version of the retail ROM in an xml format to do it in, then again I've had a long night and it just probably isn't making sense at this point. Any fix so far? Or can ya point me in any given direction?
 

Daltonyx

Senior Member
Jan 17, 2013
54
3
8
Aubrey
Try flashing the attached zip.
Edit: with TWRP.
I JUST GOT THE ***** TO BOOT
I ended up using the xml to batch converter, and it worked like a damn pro.
I've ripped all my damn hair out over this thing :D But hey, since I got you here, why do I have the system is read only issue going on?

---------- Post added at 08:59 AM ---------- Previous post was at 08:56 AM ----------

Basically what I'm getting at here, is xposed doesn't work, huh? :(
 
V

volatile1

Guest
I JUST GOT THE ***** TO BOOT
I ended up using the xml to batch converter, and it worked like a damn pro.
I've ripped all my damn hair out over this thing :D But hey, since I got you here, why do I have the system is read only issue going on?

---------- Post added at 08:59 AM ---------- Previous post was at 08:56 AM ----------

Basically what I'm getting at here, is xposed doesn't work, huh? :(
Did you allow TWRP to modify system when asked after first installing and booting TWRP? I haven't had the problem and Xposed works fine for me so I'm not sure what your problem is.

Sent from my Moto E (4) Plus using XDA Labs
 

Daltonyx

Senior Member
Jan 17, 2013
54
3
8
Aubrey
Yeah, I allowed modifications. I got it to be r/w not, but every time I install true Xposed, bootloop. Then, when I'm try to install magisk systemless Xposed, it says magisk not activated o.o

Very new to magisk though, no idea wtf that means, besides the obvious something isn't installed properly
 
V

volatile1

Guest
Yeah, I allowed modifications. I got it to be r/w not, but every time I install true Xposed, bootloop. Then, when I'm try to install magisk systemless Xposed, it says magisk not activated o.o

Very new to magisk though, no idea wtf that means, besides the obvious something isn't installed properly
It can take a while to boot after installing Xposed. I've had it boot in like 10 mins one time and take closer to 30 another. It's best to wipe dalvik/art cache also. I've never had a bootloop on the E4 or E4 Plus after flashing Xposed. If Xposed says Magisk is not active, try going to Magisk settings and make sure Xposed is checked off in the #Superuser section like in the screenshot. There's a brand new Magisk V14.6 just released and seems to work fine also in case you didn't get it yet.
Edit: make sure your using an untouched boot.img when you flash Magisk also to make sure you don't have problems with it.
Sent from my Moto E (4) Plus using XDA Labs
 

Attachments

osoct

New member
Dec 28, 2017
1
0
0
Hi everyone, I was hoping someone could help me out with rooting my Moto E4 Plus XT1775.

I am completely new to this kind of stuff, and I just want to make sure I have the steps down correctly before I proceed.

1. Unlock bootloader -- DONE

2. Download the latest Magisk.zip and put it on my phone.

3. Go into the bootload and flash TWRP using the recovery.img from this post with this command:
Code:
fastboot flash recovery recovery.img
4 Start TWRP with this command:
Code:
fastboot reboot recovery
5. Install the latest Magisk by hitting install and selecting the Magisk.zip in the TWRP menu.

6. Install the MagiskManager.apk to receive root.

Any help will be appreciated.

Thank you!
 

madbat99

Senior Member
Mar 1, 2014
5,539
3,285
113
Only partially I guess. I can't find an RSD that works on Win10 nor a version of the retail ROM in an xml format to do it in, then again I've had a long night and it just probably isn't making sense at this point. Any fix so far? Or can ya point me in any given direction?
Rsd lite from here worked fine for me. Even on Windows 10. Found device immediately and flashed fine. Just for future reference since I see you already got it with the convert tool.
 

glockman4519

Senior Member
Jun 5, 2013
2,582
1,509
0
Central Pa
plus.google.com
Finally unlocked my bootloader today and installed TWRP.. I wanted to see how this device fared running it bone stock and I am extremely impressed. Yes, I have faster devices with nicer displays but this phone is just enough with a freaking great big honking battery. What more could you ask for. So now let the fun begin.