yashsingh1/xdaforums huggingface dataset:
[Moto E4 Guides, News, & Discussion] Jason M.:
That's why I did this:

https://xdaforums.com/moto-e4/moto-.../rom-lineageos-14-1-moto-e4-qualcomm-t3868291

With everyone losing data and not having other things working. But, saying the Dev is slow at best is a little disrespectful. He has told everyone his father was sick and dealing with that. He also supports a lot of devices that otherwise might be forgotten by now, and has done a lot of work for Motorola devices over the years. Fortunately, I haven't had any hardware failures on my perry or owens yet and myself and others are working on Oreo and eventually Pie for both devices.
[Moto E4 Guides, News, & Discussion] squid2:
I still want to support this device and my other official devices (currently stuck in LOS 14.1). I do like the Moto E4. The issue is that I’ve just been busy with other things, or have felt lazy/tired when I do have spare time.

My day job is consulting which involves a lot of travel, and I also have work related software side projects. I also have a bunch of other hobbies and side projects, ranging from helping friends with electronics hardware design and firmware, to photography, to watch collecting and repair, to collecting and working on cars. I also have commitments helping elderly relatives and performing property maintenance related work.

Working on Android devices is another hobby of mine that I do for personal satisfaction. Between the various devices I support, I have several tens of thousands of users, so I try to at least keep things in a stable state for those that I support officially.

I’ll try to find time to work on Android things this month, but I won’t make any promises right now.
[Moto E4 Guides, News, & Discussion] Jason M.:
Motorola is notorious for doing this. It's nothing new. Before the E4 and E4 Plus a lot of phones only got maybe one OS update and a few security patches. I do see your complaint about no OS update but at least they keep rolling out security patches. That's the chance tou take when you buy a phone. Motorola doesn't release the device trees either. They only have to release the kernel source. Developers who choose to support and build custom roms for a device make them and that's how the E4 Plus has lineage trees. I don't think the E5 or E5 Plus even have device trees yet other than maybe enough to build TWRP.
[Moto E4 Guides, News, & Discussion] skullkid383:
Even the g6 don't have trees yet
[Moto E4 Guides, News, & Discussion] Jason M.:
Yeah, I thought about that after my last post here. Motorola abandoned these devices as far as OS updates because Google switched everything to treble. The E4 and E4 Plus don't have vendor partitions and they're not going to use the oem partition where all the bloatware is for the vendor partition which is needed for treble. But that's what we're gonna do for custom oreo and pie roms.
[Moto E4 Guides, News, & Discussion] Jason M.:
Thanks. I think I'm done with it though because I hate blind building. Unless I get another E4 for testing I think I'm done with the device. I just got an E5 Plus and I'm giving my wife my E4 Plus and my E4 to my daughter. I just don't have enough reliable E4 testers
[Moto E4 Guides, News, & Discussion] madbat99:
[MENTION=4291964]Jason M[/MENTION] I got an e4 (SPerry) with the the grey ring of touch death if interested. No touch response on left (1/4 inch) and right (maybe closer to 1/2 inch) if it helps. Rendering it unusable for my daily use. I use my phone at work for group text (a/c and furnace techs all receive dispatch through our phones)

Or another dev who is interested in it. It still flashes ok and all.
[Moto E4 Guides, News, & Discussion] Jason M.:
Thanks for the offer but I don't really want to give my address to a complete stranger.
[Moto E4 Guides, News, & Discussion] KevMetal:
well you could just choose a drop off / collection point ....:confused:
[Moto E4 Guides, News, & Discussion] Jason M.:
Yeah, I guess your right there
[Moto E4 Guides, News, & Discussion] DB126:
Appreciate your work for those who enjoy custom roms and trying to adapt branded hardware to different carriers. XT1768 (unlocked stock) remains my daily driver as I like the form factor, battery life and rock solid reliability. That said, the liabilities of this aging platform are becoming increasingly apparent. At some point you have to let go of yesterday's technology, especially given the approachable price point of stronger alternatives.
[Moto E4 Guides, News, & Discussion] Jason M.:
Thanks, but I'd rather not accept it and end up having further hardware failure which is probably likely.
[Moto E4 Guides, News, & Discussion] madbat99:
Cool. Your probably right. Tossed in the drawer with old phones going back to froyo (2.2) lol
[Moto E4 Guides, News, & Discussion] Jason M.:
Lol, I've got a few back to gingerbread like a zte warp and a couple samsung transform ultra's.
[Moto E4 Guides, News, & Discussion] Jason M.:
You should just invest your $ in a new phone
[Moto E4 Guides, News, & Discussion] madbat99:
I think he means he's done with this device.
[Moto E4 Guides, News, & Discussion] Jason M.:
That was saved as a draft in the xda app from before we spoke the other day. It was sent by accident
[Moto E4 Guides, News, & Discussion] KyleBryant:
You don't have to, set up a PO box or have it as pick up at carrier only
[Moto E4 Guides, News, & Discussion] Jason M.:
Please show me a link to device trees for the E4 Plus on github that were put there by Motorola
[Moto E4 Guides, News, & Discussion] Jason M.:
No. Not Motorola. That's the first person to make owens trees. There's been much more progress since from [MENTION=4136656]SeanStar[/MENTION] and myself
[Moto E4 Guides, News, & Discussion] madbat99:
Motorola has? Where?
[Moto E4 Guides, News, & Discussion] Jason M.:
The Moto G, Razr and a few others like 10 yrs ago, lol

Edit: but only to build stock

Motorola's GitHub:

https://github.com/MotorolaMobilityLLC

No Moto E4 Plus sources

The only other sources I have ever seen anywhere for Motorola that aren't only the kernel source which they have to release, are here:

https://sourceforge.net/motorola/wiki/Projects/

Anything else is from custom rom developers not affiliated with Motorola.
[Moto E4 Guides, News, & Discussion] madbat99:
Thats pretty much what I meant. Lol. Had to 1 up me, and be all informative... Lol

I meant for e4 plus. If they had released trees for that and I missed it...
[Moto E4 Guides, News, & Discussion] Jason M.:
Wasn't trying to 1 up you, lol. If they did release sources for it other than the kernel and I missed it, I'd love to see it.
[Moto E4 Guides, News, & Discussion] madbat99:
I was just kiddin dude. Merry Christmas from New Orleans!!

You did it the right way and quoted sources. Made me feel lazy. Lol
[Moto E4 Guides, News, & Discussion] Jason M.:
Thanks. Same to you!
[Moto E4 Guides, News, & Discussion] acspdx:
I just got a Moto E4 (XT1768 Qualcomm version). I unlocked the bootloader and have run all the system updates/security patches, but I haven't rooted it yet. I also haven't activated it because I'm waiting for the SIM card to arrive in the mail. Can I go ahead and do the next steps (TWRP, no-verity, Magisk, root) while I'm waiting, or would it be safer to get it up and running on the mobile network first?

Android version: 7.1.1

Android security patch level: November 1, 2018

Baseband version: M8917_18.08.04.17.03R PERRY_NA_CUST

Kernel version: 3.18.31-perf-g4727d26, hudsoncm@ilclbld34 #1, Thu Oct 25 09:21:31 CDT 2018

Build number: NPQS26.69-64-12
[Moto E4 Guides, News, & Discussion] DB126:
To be absolutely safe I would have activated it before unlocking if the device is still under seller warranty. What if it does not activate/work? Seller is less likely to offer assistance if the device/rom has been modded. Same thought process applies to the sequence of steps you are now proposing.

You can boot (vs flash/install) twrp and take a full backup of your system in its current state which should ALWAYS be the first step prior to rooting/modding. Be sure to keep that stock image in a safe place - preferably off-device.
[Moto E4 Guides, News, & Discussion] acspdx:
Oh well, what's done is done. I got it refurbished from eBay, so I don't think there was much of a "warranty" anyway. But I'll take your advice on the TWRP backup.
[Moto E4 Guides, News, & Discussion] Aquaferret:
Unlocked Verizon XT1767 E4 now using Freedom (Wind) in Canada

So I bought this phone on Ebay with the following FCC ID # 1HDT58WC1 Type M2993. The phone was bought unlocked from Verizon for any carrier but I notice every time I restart the phone, it gives the message "SIM card is not from Verizon Wireless". I know numerous people have said the Verizon version is bootlocked but is this true for a carrier unlocked phone? Also will Android Oreo or Pie work on this phone even though the Moto community says that is it far as it will go with this model. Any suggestions on a work-around / advice on how to upgrade this phone would be greatly appreciated.
[Moto E4 Guides, News, & Discussion] madbat99:
Verizon branded phones are bootloader locked. All of them. There is no Oreo or pie for that device and never will be. No workarounds no nothing.

Sorry to be the bearer of bad news
[Moto E4 Guides, News, & Discussion] DB126:
- yes

- no

Not eligible for bootloader unlock; no root or custom ROMs.

Edit: [MENTION=5752019]madbat99[/MENTION] beat me to it; sorry to be yet another grim reaper.
[Moto E4 Guides, News, & Discussion] ajsvakzhhwbwb:
Hey I bircked my device and I lost root with magisk in my moto e4 xt1762 idk how to root my device again without flashing TWRP I hope if anyone can help me I have magisk manager but idk how to install the zip file
[Moto E4 Guides, News, & Discussion] jonesdavid14:
I've now officially regret getting the Verizon variant of the E4. Now what?
[Moto E4 Guides, News, & Discussion] madbat99:
Nothing you can do with it involving root. But it's still a decent phone.

If you want to root a phone, don't buy a Verizon or AT&T branded device.

Buy a factory unlocked version and you can still use it on Verizon.
[Moto E4 Guides, News, & Discussion] reikred:
screen pattern unlock causes problem!

In my case, the settings.developer-options.OEM-unlocking slider button would not work. It would throw up the screen pattern unlock challenge , and after solving the challenge, the slider button was still in the disabled position. This would then repeat each time I tried.

FIX: Clear the android screen unlock pattern under settings.security. Then the OEM-unlocking slider button will work, and one can proceed with the "fastboot oem unlock YOUR_UNIQUE_KEY" operation.

Please add the above to the recipe!

(My case otherwise is an moto-e4 xt1768 and I was doing the unlocking from linux, but none of those specifics seemed relevant)
[Moto E4 Guides, News, & Discussion] googlephoneFKLenAsh:
I am currently rooted but I want to update to the latest stock image and reroot.

How to do it without wiping my data?

Do I just flash latest stock firmware with RSD and then flash twrp, then in TWRP I flash no-verify and root zip? Do I need to wipe/format in TWRP? I want to avoid wiping.
[Moto E4 Guides, News, & Discussion] madbat99:
As long as you don't boot to system after flashing the new firmware (which would encrypt your phone) , no wiping needed. When RSDlite finishes make sure you catch it before it reboots and hold the volume button so it just boots back to bootloader.

Then proceed with root procedure.

Use the servicefile in RSDlite (from firmware). Using the flashfile would wipe data.
[Moto E4 Guides, News, & Discussion] googlephoneFKLenAsh:
To avoid booting into system, can I just pull the battery when it trys to reboot after flashing firmware with RSD? Then I can mamually boot into bootloader.

This way I will be certain it won't boot into system.

---------- Post added at 07:03 AM ---------- Previous post was at 06:51 AM ----------

To avoid booting into system, can I just pull the battery when it trys to reboot after flashing firmware with RSD? Then I can mamually boot into bootloader.

This way I will be certain it won't boot into system.
[Moto E4 Guides, News, & Discussion] madbat99:
Yes you can. I only said that because when I use RSDlite it usually tries to boot to system automatically after the flash is complete. So I usually just hold volume down when it does, so it reboots to bootloader.
[Moto E4 Guides, News, & Discussion] nookin:
I did not install Magisk Manager until now. Now it is saying the version is incompatible. Any ideas which version is compatible and where can I download its apk safely?
[Moto E4 Guides, News, & Discussion] madbat99:
Incompatible with what? If you flashed magisk in recovery it should have installed the manager.

The manager alone won't root you. Unless you have the stock boot.img downloaded and use magisk manager to patch it.

Now try explaining what you're actually doing.

Get magisk and the apk from the official source.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/post68966755
[Moto E4 Guides, News, & Discussion] KevMetal:
he has updated to a version of the manager apk that isn't compatible with the version of magisk zip he originally flashed...now he can't use root nor download magisk zip to update from inside the manager apk nor downgrade and he probably deleted old copies / zips ....

solution ...download latest magisk install .zip from magisk thread .. ..flash zip in recovery

fiy :also in some versions of magisk you have to install apk manually because it wasn't installed when flashing zip...just saying
[Moto E4 Guides, News, & Discussion] nookin:
Can I install an older Magisk Manager apk instead? The error I got mentioned something about v18.0.
[Moto E4 Guides, News, & Discussion] shah.azeem:
mpcs xt1765

after update latest stock some think wrong

imei 0.

try downgrade gpt.bin failed

try twrp for root error 1

any help

(bootloader) version: 0.5

(bootloader) version-bootloader: moto-msm8917-BA.34

(bootloader) product: perry

(bootloader) board: perry

(bootloader) secure: yes

(bootloader) hwrev: P3B

(bootloader) radio: 2

(bootloader) storage-type: emmc

(bootloader) emmc: 16GB SAMSUNG QE63MB RV=08 PV=03 FV=0000000000000003

(bootloader) ram: 2GB SAMSUNG LP3 DIE=8Gb M5=01 M6=06 M7=00 M8=1F

(bootloader) cpu: MSM8917

(bootloader) serialno: ZY224NHCX4

(bootloader) cid: 0x0016

(bootloader) channelid: 0x8e

(bootloader) uid: C3AD71ED00000000000000000000

(bootloader) securestate: flashing_unlocked

(bootloader) iswarrantyvoid: yes

(bootloader) max-download-size: 536870912

(bootloader) reason: Volume down key pressed

(bootloader) imei: 35567408711xxxx

(bootloader) meid:

(bootloader) date: 11-24-2017

(bootloader) sku: XT1765

(bootloader) battid:

(bootloader) iccid:

(bootloader) cust_md5:

(bootloader) max-sparse-size: 268435456

(bootloader) current-time:

(bootloader) ro.build.fingerprint[0]: motorola/perry_metropcs_c/perry:7.

(bootloader) ro.build.fingerprint[1]: 1.1/NCQS26.69-64-15/19:user/releas

(bootloader) ro.build.fingerprint[2]: e-keys

(bootloader) poweroffalarm: 1

(bootloader) ro.build.version.full[0]: Blur_Version.26.311.19.perry_metr

(bootloader) ro.build.version.full[1]: opcs_c.MetroPCS.en.US

(bootloader) ro.build.version.qcom: LA.UM.5.6.r1-03800-89xx.0

(bootloader) version-baseband[0]: M8917TMO_18.08.04.18.04I PERRY_NA_UMTS

(bootloader) version-baseband[1]: _CUST

(bootloader) kernel.version[0]: Linux version 3.18.31-perf-g9bfa00d (hud

(bootloader) kernel.version[1]: soncm@ilclbld55) (gcc version 4.8 (GCC)

(bootloader) kernel.version[2]: ) #1 SMP PREEMPT Thu Jan 31 08:16:08 CST

(bootloader) kernel.version[3]: 2019

(bootloader) sbl1.git: git=MBM-NG-VBA.34-0-gfe9cf09

(bootloader) rpm.git: git=c6ac81e-dirty

(bootloader) tz.git: git=c270cb8-dirty

(bootloader) devcfg.git: git=c270cb8-dirty

(bootloader) keymaster.git: git=c270cb8-dirty

(bootloader) cmnlib.git: git=c270cb8-dirty

(bootloader) cmnlib64.git: git=c270cb8-dirty

(bootloader) prov.git: git=c270cb8-dirty

(bootloader) aboot.git: git=MBM-NG-VBA.34-0-gc2e3dec

(bootloader) qe: qe 0/0

(bootloader) frp-state: no protection (77)

(bootloader) ro.carrier: metropcs

all: listed above

finished. total time: 0.070s
[Moto E4 Guides, News, & Discussion] steevo398:
bad key erasing boot loop

So I tried to flash the stock rom via the rsdlite workaround, i.e. turning the stock rom .xtml into a .bat file as per the OP. Now I'm stuck in a bad key/erasing boot loop. I can boot into TWRP, but that's pretty much it. I can't move files to or from my phone and I'm not sure what to do. Any help would be greatly appreciated.

P.s. I used the rsdlite workaround because no matter what I do it does not recognize my phone.
[Moto E4 Guides, News, & Discussion] madbat99:
Are you flashing TWRP? Did you format data (to remove encryption) and flash dmverity and forced encryption disabler? Or magisk? if not going to boot with TW RP installed unless you remove DM verity. and you won't be able to access your internal storage from TWRP until you remove encryption.
[Moto E4 Guides, News, & Discussion] steevo398:
Thank you for replying. That was all I needed to hear. I completely forgot to format data.

All is well, thanks
[Moto E4 Guides, News, & Discussion] madbat99:
You're welcome
[Moto E4 Guides, News, & Discussion] steevo398:
Aaaaannd now Google play services keeps stopping lol. The fun never stops.
[Moto E4 Guides, News, & Discussion] reikred:
What will happen if I let Motorola do OTA upgrade my rooted (as per this thread) moto-e4 to the new NPQS26.69-64-23 (2019/08/01) firmware?? Will I lose root? Can I re-root it? Will I lose data? Oh, and I have an adopted/encrypted sdcard installed at the moment.
[Moto E4 Guides, News, & Discussion] DB126:
OTA will fail as system partition has been altered (not to mention recovery partition which probably holds TWRP).
[Moto E4 Guides, News, & Discussion] reikred:
Yes, I have TWRP (and root) in working order. So If I accidentally approve the incessant update reminders, nothing permanently bad will happen, just a possibly long wait for the update to fail, and then phone will boot again with the existing firmware?

I should probably explain my motivations/goals just to make sure there are no misunderstandings:

1. get rid of the update nagging (many times per day it seems). Nothing I have tried works to stop the nagging permanently.

2. avoiding any permanent ill effects from accidentally approving the update

3. If safe and possible, install the update without relocking bootloader, without losing any data (recall I have adopted/encrypted storage), and with root access preserved (or at least easily recoverable). From what you say, it sounds like whether I try OTA or some offline method (TWRP?) for an update, it will fail in the same way, since the failure mode is that the update will discover that the system partition has been altered.

If you can illuminate me a bit more about this it would be helpful. Maybe there exists more general writeups about these topics, but I could not find answers about E4 specifically when I searched.
[Moto E4 Guides, News, & Discussion] DB126:
Disable/freeze "Motorola Update Services" (com.motorola.ccc.ota). Problem solved.

Don't attempt to apply the pending OTA update. Good chance your device will bootloop which will be hard to correct in the absence of a system backup.

Speaking of backups, got one? If not get busy. :)
[Moto E4 Guides, News, & Discussion] reikred:
The "Motorola Update Services" app is not visible in GUI.settings.apps, so I used adb shell to disable it.

adb shell

perry_f:/ $ pm disable-user --user 0 com.motorola.ccc.ota

Package com.motorola.ccc.ota new state: disabled-user

perry_f:/ $ exit

Yes sir, I have Titianum backup Pro. Thanks much.
[Moto E4 Guides, News, & Discussion] DB126:
Titanium is well regarded but I still favor TWRP images. Saved my sorry tail on more than one occasion. I usually store quarterly backups on the SD card and occasionally copy one off-device for save keeping. Personal data of importance is always synced to the cloud so I don't worry about that.

Might take a peek at SD Maid for managing apps (among its many capabilities). While shell commands are nice being able to query and manage app states via GUI has its appeal.
[Moto E4 Guides, News, & Discussion] vortexmak:
I have a motorola sperry XT1766 and I followed the instructions best I could. Flashed Magisk and no verity. When I tried to wipe data , it gave an error and on reboot , the screen just says N/A and boots into TWRP.

I can't get in to the OS and it just keeps rebooting to TWRP.

What do I do next?

How do I fix this?
[Moto E4 Guides, News, & Discussion] Wajahat_Ahmed:
I need help in unlocking bootloader of my device, on official site it's says "Your device does not qualify for bootloader unlocking" is there any other way to unlock it?
[Moto E4 Guides, News, & Discussion] sd_shadow:
No, but Moto site is sometimes wrong, which CID does the device have?

List of CIDs
[Moto E4 Guides, News, & Discussion] Wajahat_Ahmed:
0x0002

:(
[Moto E4 Guides, News, & Discussion] KyleBryant:
OP Updated with link to squid2's TWRP for the Qualcomm E4.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Found a way to not have to leave system read only... Update in OP
[Moto E4 Guides, News, & Discussion] :
You should remove that link to the g5 twrp since people around here don't like to read the whole op.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Good idea
[Moto E4 Guides, News, & Discussion] KyleBryant:
OP updated with new root method to disable encryption and gain root.
[Moto E4 Guides, News, & Discussion] :
Doesn't seem to be working for me. I can't flash magisk or SuperSU without being encrypted no matter what I try. I even made a boot.img with dmverity and force encrypt disabled and still won't work.
[Moto E4 Guides, News, & Discussion] KyleBryant:
That's weird, idk why it won't work for you. Restore it to a stock boot img, and then go into twrp swipe to wipe data type yes, and reboot twrp and then flash dm verity and phhsu then reboot
[Moto E4 Guides, News, & Discussion] KyleBryant:
SuperSU is currently experiencing issues with our firmware.
[Moto E4 Guides, News, & Discussion] :
I've tried that, and numerous other things many times and it's just not working. I've been mostly trying with magisk even the new beta that just dropped. I know about SuperSU issues, the only thing I haven't tried is with phhsu. I'll try that now.

Edit: OK, so phh's superuser is the way to go for now I guess. It flashes OK, but when I rebooted magisk was asking to grant phhsu apk permissions so magisk must have been installed even though the installation failed in recovery. Weird.
[Moto E4 Guides, News, & Discussion] KyleBryant:
That is weird, but I'm glad you got it working.
[Moto E4 Guides, News, & Discussion] e4noob:
Total noob here. Thought about rooting and using xposed or something. But never got around to it.

Question: Is there a good chance somebody would publish a one click utility to root/unroot for the moto e4 (USA, RW)? How long does it take usually for the experts until they release something like that?

I remember moto x had something like that. But then with an os update we were locked out of rooting. haha. So the moto e4 is unlocked and I'm looking forward to using this one click utility.

(I'll post this question as a thread later may be hopefully get a solid answer)
[Moto E4 Guides, News, & Discussion] KyleBryant:
The chances of us actually getting a one click root are very slim because you'd still have to unlock the bootloader. I'm actually using Xposed now and it's pretty great lol.