yashsingh1/xdaforums huggingface dataset:
[Moto E4 Guides, News, & Discussion] resarfekim:
Thanks madbat.

I extracted, and installed the servicefile.xml using RSDLite.

It rebooted into the bootloader and presumably flashed the stock rom.

When it came back up, Magisk appears uninstalled. But when I go to check SafetyNet, I get "CTS Profile Match: Fail"

Is there something else I should do to pass safetynet?

Also, I got the popup to upgrade my system software, so I hit Yes on that and it's downloading now. Is that going to mess anything up?

Thanks again,

Mike
[Moto E4 Guides, News, & Discussion] madbat99:
Should be fine since you flashed stock. Safetynet might be failing because the bootloader is unlocked, or something else. Shouldn't affect Pokemon go. If you want to be sure you can do the flashfile.xml and let it wipe Data and all.
[Moto E4 Guides, News, & Discussion] resarfekim:
You are right, Pokemon runs properly now. Thanks for the help!
[Moto E4 Guides, News, & Discussion] madbat99:
No problem.
[Moto E4 Guides, News, & Discussion] resarfekim:
Found that removing magisk/root was as easy as clicking "remove" from the magisk app.
[Moto E4 Guides, News, & Discussion] madbat99:
For some, it won't boot. If they unencrypted and some other things.

If you've modified anything in the system partition directly then you've tripped dm-verity and your device won't boot.

It's not enough to just flash the stock boot image.

Dm-verity needs to be disabled in the boot image or flash the stock system image.
[Moto E4 Guides, News, & Discussion] A pet tick:
Verification problembs

im trying this but whenever i try to flash twrp to my phone it comes up with verrification errors. Is there a way around this or a verified image?

C:\adb>fastboot flash recovery twrp.img

target reported max download size of 536870912 bytes

sending 'recovery' (10302 KB)...

OKAY [ 0.326s]

writing 'recovery'...

(bootloader) Image recovery failed validation

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.340s
[Moto E4 Guides, News, & Discussion] DB126:
Well, one workaround is to simply boot the TWRP image vs installing it. There are a handful of advantages to retaining stock recovery and only boot TWRP when needed.
[Moto E4 Guides, News, & Discussion] KevMetal:
Haha , are you certain you unlocked your bootloader...fastboot can only flash *verified as in OEM signed images until you unlock it ...then you can flash most other images

If your twrp will boot as Davey says you can just flash magisk ....for root etc
[Moto E4 Guides, News, & Discussion] A pet tick:
I went in developer options and used the "OEM unlocking" switch. Is this the wrong thing? Also is there a way to retain all my data (apps, downloads, ect) while rooting?
[Moto E4 Guides, News, & Discussion] skullkid383:
Go here follow steps https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
[Moto E4 Guides, News, & Discussion] madbat99:
No, no. You just ticked a switch. You have to get an unlock code from Motorola. Follow [MENTION=8931427]skullkid383[/MENTION] link. Unlocking your bootloader will wipe your data. Then you have to format data again when you root anyways, to remove encryption, after flashing a dm verity opt encrypt zip. You have some reading to do bud. But, don't forget to have fun. Isn't that why we tinker with our devices?
[Moto E4 Guides, News, & Discussion] KevMetal:
No it's right but read the guides , in fastboot , before flashing img file you need to run the command

fastboot oem unlock

A message will appear on your phone's screen that requests confirmation and you need to confirm by pressing the volume up button .

Only after this can you flash recovery .No , this unlocking bootloader will factory reset your phone .
[Moto E4 Guides, News, & Discussion] madbat99:
That's for the mediatek version. Since this is the Qualcomm section, I figure that's the one he has. But he didn't really say so...
[Moto E4 Guides, News, & Discussion] KevMetal:
Yeah true
[Moto E4 Guides, News, & Discussion] madbat99:
You can get a different e4 and activate it on Verizon if your stuck to Verizon. The unlocked/unbranded version is very nice.

But as for clockworkmod recovery, I didn't read it anywhere. Development ended on it long ago. It won't even flash modern ROMs even if you can find a version that still works. So I imagine the only people using it have very very old devices.

Wish I had better news for you. But root is impossible on that one. Sorry dude.
[Moto E4 Guides, News, & Discussion] DB126:
Blame? Hardly. It's called a business model. Root is not an entitlement.
[Moto E4 Guides, News, & Discussion] KevMetal:
Well to be certain you need to check what you buy . However, I disagree with your statement. Once I buy a product I become the owner and the only true reason to own something as opposed to hiring something is the right or opportunity to do as you please with your new property. It's true that through the ages government and big brother has tried to make a few extra bucks with taxes & tarrifs and or legal restrictions ( for everyones safety) but it has never changed the true inherent premise of what ownership means to people . Some years ago all the carriers were locking their phones to certain networks and now that is mostly illegal around the world and most phones are free to use on all networks. Eventually a similar case will appear in court one day arguing an owner's root rights . So in my opinion root is more than a right it's the basis for the foundation of ownership and inherently implied with the purchase of the device. Therefore the owner is entitled to root access .Whether one agrees with concept of ownership is a story for another ....and after that if we ever really truly own things or do we just prevent other people from fully enjoying or benefitting from something under our control . Kind of like the phone and the manufacturer and the carrier..... isn't it true without root a entity with power has put restrictions on you ....so back to the beginning ( did he truly own the device or was he tricked into trying to own something he didn't have the power to control and therefore lost some of the benefit of his money ) That is not business . That is taking advantage of the consumer . Even if they disclose there won't be root it's like telling an alcoholic to be careful of drinking too much beer on the label ..................
[Moto E4 Guides, News, & Discussion] DB126:
Well crafted but really not in the same ballpark as simple carrier unlocking. Most consumer devices are effectively 'root locked' with no indication the emerging IoT economy will go a different direction. The business friendly SaaS derivative for consumer gizmos (think voice assistants and everything they communicate with) will demand consistent, "secure" endpoints which lawmakers will easily buy into. Especially if such controls reach into items such as autos and shared resources (eg: power grid) which seems likely.

Far more probable is a consumer bill of rights around simple repairs which seems to be gaining traction in several countries.

But your challenge was around the concept of 'entitlement' and the presumption of unfettered access/control based on physical possession which at present has no legal standing. Nor is it likely in the foreseeable future in the absence of a clear set of definitions around "ownership" in the consumer electronics landscape.
[Moto E4 Guides, News, & Discussion] KevMetal:
Good point and I see what you are saying and my only response would be that the law and interpretation of it becomes very subjective on the bleeding edge and will never truly nor fully govern human behavior. Keeping that in mind I simply won't change my own concept of what ownership and my implied rights related to it means to me ....and I definitely don't advocate supporting any player in the android / handset game who thinks security is the same as no root access or not releasing sources .The simple truth is the type of security and insurance being sold to us is wholly unnecessary unless you are a high profile politician with secrets or embezzled millions to hide in which case the level of expertise available to penetrate or bypass rises in tandem. Not having root is like having an alarm system in your house controlled for you by the security company you hired ......very dangerous unless your brother owns the security company.
[Moto E4 Guides, News, & Discussion] DB126:
Yep - although I'm not sure I would trust my brother either. :)

While personal beliefs are fine and dandy reality is in the absence of a sustained groundswell from consumers the focus will remain elsewhere which means business get to set the rules. A peek at what is trending on social media offers a view into the future that does not look favorably on any inner layer of the onion that requires more than 30 seconds of sustained thought or result in an uncommanded blood flow redirection. As for entitlements, we're going to agree to disagree on this one for the reasons outlined in previous posts which seems rooted (no pun intended) on the definition of physical "ownership" and the rights that go along with it.
[Moto E4 Guides, News, & Discussion] KevMetal:
Hahahaha , yes , it depends on your brother I guess . Well okay I accept your offer to agree on disagreeing . Your opinion also hinges heavily on your presumption that the subjective law system can be manipulated in only one direction but not another or will remain static on some as yet undefined questions.
[Moto E4 Guides, News, & Discussion] Genji-2d:
i want to share this as it is very crucial for some of us, twrp flashes fine. but /data is in a weird format if not mistaken named as (enmc) format data does not work cause /data cannot be mounted or formated. tryed flashing no-verify. zip does not fully flash. changed /data to ext4, i get access to /data and can format data cool. so i do the following. after changing the /data to enmc to ext4, i go and format data reboot to twrp flash no verify.zip then magisk everything goes fine. until the reboot where it boots back to twrp everytime. thats using the recovery in OP i used another which was 3.1.1.0. when i boot into it would tell me that data was decryted and what not but in the 3.2.1.0 its like on everyother twrp no extra dialog but Rom wont boot. i will provide screenshot when possible

---------- Post added at 11:53 PM ---------- Previous post was at 11:28 PM ----------

tried another version of twrp and its does what i mention i will provide link of where it is found keep in mind the twrp in this thread it super faulty for my xt1775 owens. https://xdaforums.com/devdb/project/?id=23041#downloads this twrp is 3.1.1.0 and has this extra dialog stating that dev/block/by-name/etc & and /data was sucessfully decrypted. only needed to flash no verify.zip just in case and now i can flash rom and what not.
[Moto E4 Guides, News, & Discussion] madbat99:
First, this twrp is not faulty. You have made some major errors, and no. Data is not a weird format. It is f2fs.

You flashed the wrong twrp for your device.

Formatting to ext4 is not recommended. Format data works just fine. You have to type the word yes. And of course you need an opt encrypt zip to remove the force encrypt flag from the boot image.

The reason you ended up in a twrp loop is this (aside from flashing the wrong twrp for your device)

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, or format data, 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:

dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc bs=1M

Then you will be able to boot to system normally. Needless speculation doesn't help you or anyone else. You were supposed to flash the dmverity no opt-encrypt.zip before you formatted data. Flash it, then reboot recovery, then format data. Then enter the command above in twrp terminal.

IMPORTANT:

This thread is not for Owens. That is the plus model. This is for Perry. The regular Qualcomm E4. If you flashed the Twrp from this thread on an Owens device, you have more problems than I am prepared to address. You need to go to your device's forum and start over. And stop posting "crucial" info that is completely incorrect because you haven't read properly and identified your device before flashing random files.
[Moto E4 Guides, News, & Discussion] ubigdumy:
What would be the best way to take an update from Motorola or at least turn off updates so it stops popping up with the annoying update screen. I didn't know if I unrooted and took the security update if I could just reroot with this method.
[Moto E4 Guides, News, & Discussion] madbat99:
I've seen some who have taken the latest update say to root again they had to use magisk manager to patch the boot.img to root.
[Moto E4 Guides, News, & Discussion] user-261:
Kingroot apk download
[Moto E4 Guides, News, & Discussion] madbat99:
Or just hot your phone with a hammer and post all your personal info on foreign servers
[Moto E4 Guides, News, & Discussion] davejames500:
I just got a few of these phones and looking to root them. I installed all the latest updates. I've read some posts about patching boot.img with magisk manager for the latest security update. How would I do the patching?
[Moto E4 Guides, News, & Discussion] skullkid383:
I'm assuming ur already unlocked bootloader if so flashing magisk should work but I'll return one of mine to stock and try and see if it does
[Moto E4 Guides, News, & Discussion] davejames500:
I tired it. My phone is rooted now.

I flashed no verify then magisk. no other steps needed
[Moto E4 Guides, News, & Discussion] c0080900v:
Anyone anyone around here ROOTED Sprint XT1766 with this guide?
[Moto E4 Guides, News, & Discussion] madbat99:
Everyone.
[Moto E4 Guides, News, & Discussion] RebelLion_:
Anybody working on a kernel for this device? I'm researching 0sm0sis' Android Image Kitchen so I can try and compile one myself with some tweaks, if I even can lol
[Moto E4 Guides, News, & Discussion] guitardoc64:
Good luck! I'm sure that you will be able to find people to test it out for you.
[Moto E4 Guides, News, & Discussion] phonecapone:
I'm assuming this isn't signed? I get an error about not being signed or corrupt image when flashing. When i reboot to recovery or system i get a prompt "bad key" where normally you would see the bootloader unlocked screen. I can boot TWRP fine however.

XT1765 / MetroPCS

EDIT: NM, I flashed again and this time removed the battery and replaced it instead of rebooting. It took. Now to flash a decent logo over the N/A.
[Moto E4 Guides, News, & Discussion] motoe4xt1676verizon:
Damm you verizon
[Moto E4 Guides, News, & Discussion] DB126:
Been that way for 5+ years. Never buy a carrier branded phone...especially one from Verizon.
[Moto E4 Guides, News, & Discussion] shinacalypse:
Hi Everyone

Sorry to jump in like this on the thread, but is there Oreo for Moto E4 (XT1762)?

If yes, are there any valid steps I can follow to root and install?

Thanks a lot in advance!
[Moto E4 Guides, News, & Discussion] madbat99:
Not for the Qualcomm version.
[Moto E4 Guides, News, & Discussion] shinacalypse:
How can I tell the difference?
[Moto E4 Guides, News, & Discussion] madbat99:
Xt1762 is the mediatek version. That one is woods. Qualcomm is Perry. So check the ROMs in the woods section.

Probably need to start with Twrp recovery.

https://xdaforums.com/moto-e4/development/twrp-teamwin-recovery-moto-e4woods-t3815749/post77059053
[Moto E4 Guides, News, & Discussion] cloudblue:
Hello fine devs. I moved from the moto e surnia to the moto e4 perry yesterday. After perusing this thread, I think I would like to keep the stock rom and simply Root, with stock recovery so as to be able to run xposed framework. I have unlocked the bootloader on this xt1766 (qc425). Am i correct in thinking all I need to do is flash no verify.zip and magisk to make this happen? Or fastboot twrp add magisk?? Is there someone who can point me to correct steps to do this? with links to the same? Thanks in advance.....a moderate noob.
[Moto E4 Guides, News, & Discussion] DB126:
Yep. See OP for guidance. If you wish to retain stock recovery skip steps 2.1 and 2.2. Instead, boot TWRP when needed using the command 'fastboot boot <twrp.img>', where 'twrp.img' is the name of the file downloaded in step '0.v'.
[Moto E4 Guides, News, & Discussion] madbat99:
If you want to keep stock recovery, just fastboot boot recovery twrp.img instead of flash. While in twrp, format data (to remove encryption) and flash dm no verity opt encrypt zip, and magisk.zip. should be all good then. You can install Xposed through magisk, it's in the download section of magisk manager. When you tap Xposed in magisk manager there is a link to the Xposed APK you need (have to use that one to recognize systemless Xposed). You won't pass safetynet with Xposed. But since it's a magisk module, you can turn it off and reboot to pass, and re enable it when you're done doing whatever you need safetynet for.

Edit: ninja'd by [MENTION=5488402]Davey126[/MENTION] lol.
[Moto E4 Guides, News, & Discussion] DB126:
FWIW - I could care less about safetynet. To keep things simple I install (flash) Xposed via conventional method. Works fine and avoids doinking around with fussy Magisk modules.
[Moto E4 Guides, News, & Discussion] cloudblue:
[MENTION=5488402]Davey126[/MENTION] & [MENTION=5752019]madbat99[/MENTION], Thanks for the info....I may have temporarily screwed the pooch though.. I'm getting error:255 "failed to mount data" "unable to format to remove encryption" (device or resource busy). Wonder if it was because my SD card was formatted as shared internal when I started the process???..... Restoring back up now...
[Moto E4 Guides, News, & Discussion] DB126:
Glad you are part of the 5% club that actually take backups. As for SD card config...well...seems like a bad idea (being generous). Same for encryption if enabled. On a related matter take note of F2FS issue with data partition if you plan to use Magisk modules. Easily mitigated; suggest you NOT reformat to ext4 or use a custom kernel. Go for Magisk F2FS Loopback Bug Workaround module instead. Works a treat.
[Moto E4 Guides, News, & Discussion] madbat99:
Yeah, you'll want to keep sd card as external. Glad you made a backup. You'll need the zip files on your sd card since you're formatting data. So keep it as external storage.
[Moto E4 Guides, News, & Discussion] cloudblue:
Yep yep. Thanks. BTW, I don't need the safety net either, can I just flash the Magisk file and be done with it?
[Moto E4 Guides, News, & Discussion] DB126:
Recommend applying the previously mentioned f2fs fix; never know when that will come to bite you - likely long after the details of this discussion are lost to grey matter abyss.
[Moto E4 Guides, News, & Discussion] madbat99:
Gotta format data.
[Moto E4 Guides, News, & Discussion] Fear of Oneself:
Is Squid2's custom TWRP the only version that works on Perry? It doesn't appear that this is a supported device on twrp.me/devices

thanks!
[Moto E4 Guides, News, & Discussion] madbat99:
Yep. No official twrp yet. I think that's going to change soon though. Squid2 is talking official lineage as well as treble. And more. He updated his twrp to the latest, and added 64bit support for the future
[Moto E4 Guides, News, & Discussion] Fear of Oneself:
Interesting, I just flashed his latest one about an hour ago on a Ting Mobile, qualcomm E4 (perry.) Ended up with a soft brick immediately. I can no longer boot up, just left with "bad key" at the top of the display.

I can still get into the bootloader though, which leads me to believe that this is fixable from my past HTC experience. But I can't send files to the device when it mounts via MTP, fantastic
[Moto E4 Guides, News, & Discussion] madbat99:
Did you wait when you saw bad key? It's normal after unlocking the bootloader. Just wait. It's going to say that every time. Until you format data and flash dm no verity and magisk to remove encryption.

Every Moto device says that after you unlock the bootloader. After you format data and flash no verity it will change to n/a

You did not have a soft brick. You just didn't wait 2 minutes. Hopefully you haven't do e something worse to try to fix it, cuz it ain't broke
[Moto E4 Guides, News, & Discussion] Fear of Oneself:
I left it sitting at "bad key" while I washed the dishes which took about a half hour.
[Moto E4 Guides, News, & Discussion] ₥ike_grips:
It's the web sight. It took me 6 or so attempts to get the unlock_key. Just keep clicking it'll hopefully eventually go threw.

---------- Post added at 04:38 AM ---------- Previous post was at 04:30 AM ----------

Yep yep yep. (Well I read half the guide and it worked for me) if you get errors ignore most of them, like flashing recovery returned errors but worked fine.
[Moto E4 Guides, News, & Discussion] Ortem1UP:
Hey all. So I've successfully rooted my E4 from "Metro By T-Mobile" ??

This is my first Motorola/Android OS phone ever. Last Moto was the Krzr.

But the procedure I followed was a bit different. I unlocked bootloader, couldn't flash TWRP, kept getting rebooted back to bootloader, but booting into TWRP wasn't a problem. Although, I couldn't for the life of me format the data. Kept stating that it wasn't mounted. And when I tried mounting data. It wouldn't let me. I couldn't select it from the options. System, cache, MicroSD were selectable but not data. So I just proceeded to flash No Verity and Magisk Beta and rebooted the System. But all it would do was boot back into bootloader. So I created a bat file and ran it via fastboot to go back to stock and redid all the steps but this time I unplugged the phone from my lappie( yeah, that was the problem). Still couldn't flash TWRP nor could I format data. Also, It didn't boot into the "keep read only" option as it did the first time. But it was already selected. So I just flashed the files and rebooted system and it was a success. Still no TWRP tho. Any idea why? Also, should I be worried that I couldn't format data or that it wasn't mountable?
[Moto E4 Guides, News, & Discussion] madbat99:
You can try putting the TWRP image on your SD card then booting to TWRP as you did before. Select install then select install image and install the TWRP image file you have on your SD card to the recovery partition. That may get it flashed permanently for you.
[Moto E4 Guides, News, & Discussion] Ortem1UP:
Thanks for the quick reply. I actually was reading somewhere on these forums that flashing the twrp image with flashify will also work. So I attempted it just a few minutes ago and viola. I now have twrp installed. Thanks though. I still appreciate your reply. It seriously helps a lot to just search and read through all the threads. There's always an answer somewhere on here. Now to install the f2fs fix and proceed with installing some Magisk Modules.

Thanks again yo.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Sorry I haven't been back to reply to everyone I've moved on to the E5 plus and gsi testing.
[Moto E4 Guides, News, & Discussion] Jason M.:
How is the E5 Plus? Been thinking about grabbing one
[Moto E4 Guides, News, & Discussion] madbat99:
My e4 is gone too. Lost touch response on left and right edges. I picked up a G6 play.
[Moto E4 Guides, News, & Discussion] Jason M.:
I bought a G6 play like 4 months ago, didn't like it much and it kept randomly rebooting so I returned it
[Moto E4 Guides, News, & Discussion] madbat99:
Flashify was going to be my next suggestion. Glad you got it.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Absolutely fantastic, I'm actually running a 9.0 gsi on it right now. I highly recommend this phone.
[Moto E4 Guides, News, & Discussion] skullkid383:
I posted Hannah twrp on xda for moto E5+ if u need it and I second this highly recommend