yashsingh1/xdaforums huggingface dataset:
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] CodyF86:
About to walk out the door for work so ill reply more tonight, but will for sure check out squids twrp and repack it, if it mounts storage properly. Also I didn't mean you can flash firmware from a diff E5 on a diff E5 never do that. I mean't you can flash the stock correct firmware for your phone, boot it, take the OTA and it will work with an unlocked bootloader.

Not sure about cricket phones, but am willing to hex edit their kernels if theyare unlockable.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MotoJunkie01:
Cool [MENTION=5337314]CodyF86[/MENTION]. Thanks for confirmation on the firmware. I'm slowly adding confirmed info to my firmwares thread. Good luck on the repack. Yeah, hopefully everything will mount normally.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] HackerBoss:
Wish I could root my e5 cruise cricket.just did my hafury umax mt6580 it runs nice and smooth but my goal is this e5. Cruise .
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MotoJunkie01:
With the bootloader locked down, it's safe to say that it cannot be rooted. Anything is possible of course, but extremely unlikely
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MetalGearWolf:
That sucks
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MotoJunkie01:
I fully agree and share your disappointment. Carriers such as Verizon, TracFone, AT&T and AT&T subsidiary Cricket, are notorious for excluding their branded devices from bootloader unlocking support. Motorola/Lenovo fully supports bootloader unlocking and user-end development on its smartphones and tablets. Unfortunately, on carrier branded devices such as yours, the decision as to the bootloader status is the unfettered prerogative of the carrier.

With Motorola smartphones and tablets, if you plan on rooting, customizing, tinkering, etc., it is best to get either a factory unlocked retail model or the Sprint compatible (Boost, Virgin, TextNow, etc.) model. With those device variants, unlocking your bootloader is fully supported.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] Stefan22:
Does this also work for Motorola Moto E5 Plus (or is it in the works)?
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] allenjthomsen:
[MENTION=5337314]CodyF86[/MENTION] i was unable to get the new twrp in your first post to boot so i repacked it with the e5plus zimage and dtb and have uploaded it to my androidfilehost.

here is the link

https://www.androidfilehost.com/?w=files&flid=280931
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MetalGearWolf:
Maybe in the future some one will find a way to unlock the e5 cruise. I use to have Sprint but left because their service sucks. Cricket is way more better in my opinion.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] konradsa:
Sorry, which magisk and how did you flash it? Just picked up a t-mobile moto e5 play, trying to get root now and trying to learn from your experience. Thanks
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] egoniasty:
i used twrp from this post https://xdaforums.com/moto-e5/development/recovery-twrp-moto-e-5-play-james-t3796323 for my tmobile moto e5play i did not flashed any E5 Play DM-Verity Disabled Kernel because if you flash it you will get boot loop then i flashed magik from this link https://github.com/topjohnwu/Magisk/releases/download/v16.7/Magisk-v16.7.zip

later I installed https://github.com/topjohnwu/Magisk/releases/download/manager-v5.8.3/MagiskManager-v5.8.3.apk

and xposed and gravity box .
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] vq8acsxht:
[MENTION=5255135]egoniasty[/MENTION]

Great! Now try viperfx. Does it work, also? and does viperfx unlock the sound chip meaning quality?
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] egoniasty:
im not trying viperfx it took me few hours to get my phone working after all the trials and errors with difrfent twrp builds and magik builds to see what works and what dosent for now im just happy to have my phone working for the last few weeks.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] Druadach:
So question. What would be needed to unlock the bootloader for the Cricket Variant? I might have a connection or 2 in in Cricket if there is something from the carrier that might be useful but I don't know what I'd be looking for.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MotoJunkie01:
Even with the Cricket variant (which as you know isn't supported for bootloader unlocking) typing the command:

fastboot oem get_unlock_data

will return the long string of variables which are inputted into the official unlock webpage on Motorola's website. The issue is, once this string of data is evaluated by Motorola's unlock code generator, certain variables within the data string alert the generator that the device is Cricket branded and not supported for oem unlocking. Through the years, many methods have been attempted -- algorithms, pattern analysis, etc. -- to "fool" the code generator into returning an unlock code for an otherwise unsupported device. (This is especially so with Verizon branded devices, which are traditionally unsupported on Motorola's bootloader unlocking policy.) In theory, the possibility certainly exists -- after all, there is a unique code which will oem unlock an unsupported device. The problem is, once the unlock data generated by the fastboot execution is entered into the unlock webpage, the unique code is withheld by Motorola due to the device's particular branding. To my knowledge, a viable method to bypass or otherwise "fool" the system has never been found to date. I wish I could offer more favorable input, but I'm afraid Motorola's bootloader unlocking policy has a rather insurmountable structure.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] Druadach:
That's a really long winded way of saying no. And I wasn't asking for a way to fool motos site. Obviously that method is a bit far fetched. I was thinking more along the lines of files/info from the cricket side that would lead to a temp root in order to unlock the bootloader that way or change to S-off on the device.

---------- Post added at 01:27 AM ---------- Previous post was at 01:22 AM ----------

Or maybe a engineering img/kernel from development of this Variant.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MotoJunkie01:
It was long winded indeed. But the point I was making is that oem unlocking is never on the carrier side. In other words, not even Cricket has the code to unlock the bootloader of their own device. Here is an avenue you might want to look into, as far as alternative methods go. This thread outlines using Qualcomm's EDL (emergency download) mode to push partition images to an oem locked device to gain root. This is an example involving the Moto Droid series; however, this method has been used on a number of oem locked Moto devices. Also, it does involve intentionally hard bricking your device and requires blankflash and firehose programmers. So, this example is purely proof of concept and as info to research further. https://xdaforums.com/droid-ultra/g...x-ultra-root-pogress-100-t3071609/page61/amp/
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] Druadach:
I never said I was looking for an unlock code. I'm thinking more along the lines of temp root leading to maybe the ability to use sunshine to turn s-off on the device. Or somethinh similar.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MotoJunkie01:
I understand fully. Check my link above.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] Druadach:
I'm not sure exactly as where the link is supposed to go to as it's not a thread and just a section of the forums.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MotoJunkie01:
My XDA Labs app does not parse URLs so I have an extremely difficult time posting links from a browser. Try this: https://xdaforums.com/droid-ultra/g...x-ultra-root-pogress-100-t3071609/page61/amp/

Did it again. Try this instead.

https://xdaforums.com/droid-ultra/general/droid-mini-maxx-ultra-root-pogress-100-t3071609

The thread describes pushing partition images (.mbn format) to Motorola devices with locked bootloaders. It's merely a point of reference. This method -- albeit extremely dangerous -- has been used to gain root access (/system r/w) on a number of locked down Moto phones. To use Qualcomm's EDL, you must first purposely hard brick your device. Just saying -- use caution.

---------- Post added at 02:50 AM ---------- Previous post was at 02:37 AM ----------

[MENTION=8161383]Druadach[/MENTION] also check this link. This gains temp root (via tethered jailbreak method) for some Moto devices with locked down bootloader. This particular link outlines a method for temp rooting the Verizon Moto G4 Play (xt1609), which has a perma-locked bootloader. https://xdaforums.com/g4-play/development/root-autoinitroot-motorola-bootloader-t3639316

I hope this info provided at least some points of reference for alternatives to orthodox root methods. Since the Cricket bootloader will probably never be unlockable, hopefully there are means by which to at least gain temp root.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MotoJunkie01:
[MENTION=8161383]Druadach[/MENTION] I researched some more on the Cricket branded Moto E5 variants. Unfortunately, even using alternative and temp root methods, due to Mororola's recent partition index structure changes and Android Oreo source code in general, you're very likely to incur a hard brick by tampering with the Cricket variants. There are qFuses as well as AVB 1.0 signing on the stock kernel. These Verizon and Cricket models are locked down pretty tight.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] Druadach:
Damn.. Guess I have to learn to code linux and java now so I can figure it out.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] kc9nrb:
Variant Question.

Will this ROM work with the Cruise variant of the e5 from Cricket?
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MotoJunkie01:
What ROM? This thread is for TWRP custom recovery and root.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] 1juanzh0:
h̶e̶l̶l̶o̶,̶ ̶c̶a̶n̶ ̶s̶o̶m̶e̶o̶n̶e̶ ̶p̶l̶e̶a̶s̶e̶ ̶u̶p̶l̶o̶a̶d̶ ̶t̶h̶e̶ ̶m̶e̶t̶r̶o̶p̶c̶s̶ ̶o̶r̶ ̶t̶ ̶m̶o̶b̶i̶l̶e̶ ̶T̶W̶R̶P̶ ̶b̶a̶c̶k̶u̶p̶?̶ ̶t̶h̶a̶n̶k̶ ̶u̶
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] matada:
Nevermind
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] TheAmbition267:
I have the metropcs variant and have unlocked my bootloader and even have all the files downloaded and was able to bootloader into twrp I tried flashing the no verity but won't flash because it cannot determine what partition it needs to be flashed on can someone help please

---------- Post added at 06:39 PM ---------- Previous post was at 06:36 PM ----------

How do I flash no verity in fastboot it won't let me something about not able to determine what partition
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MotoJunkie01:
fastboot flash boot boot-e5-noverity.img

You can also flash the no-verity kernel with TWRP by selecting Install, then select Install Image in the lower right of the screen, navigate to the no-verity boot image and select, then select the boot partition when prompted by TWRP. Swipe to install.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] TheAmbition267:
So I flashed everything and stuff but now it just bootloops moto and Metropcs for way too long I don’t understand what went wrong and I flashed magical beta so now my phone is stuck any idea what I should do and also I did factory reset still nothing:(
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] weakNPCdotCom:
Im having problems with the tmobile e5 play. I unlocked the bootloader and then got a bad key message. i didnt realize that the no-verity kernel wouldnt work for the tmobile variant and flashed it without making a backup (dumb me). I then tried flashing a boot image from the thread to restore factory firmware but it just gets stuck on the motorola boot screen.

---------- Post added at 06:11 PM ---------- Previous post was at 06:03 PM ----------

Nevermind guys. I was able to rectify the problem by flashing the LineageOS rom for the e5 play. I guess i can never go back to stock now until the t-mobile stock images are released :)
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] weakNPCdotCom:
Well, unfortunately I am still having issues. Rebooting my phone often reboots it straight to the bootloader. The LineageOS rom for James has problems with the camera and flash. I believe what I need is the factory boot image. Does anybody out there on the XT1921-3 T-mobile variant have a backup of their boot image they can share?
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] BBobby:
Lineage OS has had problems with camera and flash for every phone ive ever installed it on: moto G, Oneplus One, Nextbit Robin. I wouldnt be surprised this is a global problem, as there were issues with camera since CM7

---------- Post added at 10:42 PM ---------- Previous post was at 10:40 PM ----------

So no luck in unlocking bootloader with the Cricket variant?
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] konradsa:
[/COLOR]

How is it working for you? Does mobile data work? How about mobile hotspot?
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] weakNPCdotCom:
As far as I can tell mobile data works in Lineage. I had to update the T-Mobile APN because the one they had selected was garbage. I havent tried the mobile hotspot yet. I actually am now struggling with getting GApps on it because of googles new "uncertified device" pain in the ass. I am still working on getting this thing to function enough that I can at least use it until someone gets a hold of the stock firmware.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] konradsa:
Awesome, my primary use case is to use it as a mobile hotspot on the road. Since you had some trouble, do you think you could summarize the steps to follow to get lineage installed on a factory fresh t-mobile e5? Thanks
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] konradsa:
Thanks. Will probably tackle it this weekend. Will make sure to make a backup of the stock ROM first and share it.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] Dark98:
Would either of you two be able to assist me with building twrp for the e5 play(xt1920-15)? Ive got a stock boot and vendor backup for the fstab,etc
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] weakNPCdotCom:
I decided to try a couple of things in a longshot attempt to fix the camera and other hardware by flashing the stock XT1921-5 Vendor Image to my XT1921-3. I was having some issues with audio skipping when the phone was locked, and decided to see if there was anything else I could do to get the phone more stable.

Well.. Forgot that Magisk gets flashed to Vendor :silly: so I was not too excited to see an Encrypting screen when booting back to Lineage. I tried restoring and flashing Magisk to disable verity again, but the phone still encrypts before booting back to Lineage.

I don't feel like doing this whole process over again to see if flashing Lineage, Boot, Vendor and Magisk subsequently will keep data from encrypting, so I'm just going to roll with it and see if I notice any improvements in how the device runs.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] konradsa:
So I installed the ROM on my XT1921-3. It seems to work okay, but I primarily want to use this phone as a hotspot, but the hotspot data it super slow. It barely gets up 1 Mbps, while a speedtest on the phone runs at 30 Mbps. Anybody have a clue how to fix that?

---------- Post added at 10:56 PM ---------- Previous post was at 10:54 PM ----------

I did install the ROM, thanks for your awesome instructions, saved me a lot of time. I did the full backup, let me know if you still need it and where I can host it.

Thanks
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] weakNPCdotCom:
Dude that's fantastic, thank you! I'm glad it went smoothly. If you want to pm me your email address I can add you to a folder on my G drive where you can upload it.

I have been researching different ways people have fixed hardware issues in AOSP-based roms and my plan was to do my best to get the camera and flash working. But if I have any luck with that I will try to cover all of the hardware unless it works fine. I am personally having problems with audio when the screen is locked for some reason so ill be working on it.

Unfortunately I am not sure what to suggest for the hotspot. From the logs I'm seeing on my phone it almost seems like the camera being broken is making the audio to be flaky.. which cascades into some other hardware errors. Hopefully we can get it working soon.

But yeah, send me your email and ill add you to the folder to upload. I don't have a stock -3 backup so this will help a lot. Thank you so much
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] Deadlyfire1101:
I'm looking for root and also a way to fix dm-vertify
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] tbirdguy:
im running a -3 tmobile variant with Resurrection Remix system-180818-arm-aonly-gapps.img

I had to use adb to flash the img, but once i did it that way instead of twrp then all went well.

FOR GOOGLE ID i used deviceID apk that i install via adb, run it and get device id then register for gapps

(I have found a usb kb/mouse via OTG is helpful until you get the setup done)

I got root from just pushing the fstab to the vendor part (partition wouldn't mount, but i was able to push the file and it worked in twrp) then flashing magisk...

its my daily driver right now, and camera and flash and tether all work good (tether may be slow, i haven't speed checked it)
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] weakNPCdotCom:
Sounds like a good start for those of us who didn't hose our boot image. TWRP won't be able to Mount storage if it is encrypted, so the solution is to format data to remove encryption and reboot back to recovery. Mount should happen at that point.

I'm waiting on a full twrp backup of stock so we all have an image to fall back on and use for other devs until Motorola or t mobile release the firmware.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] tbirdguy:
yea still didnt mount.. ive got a twrp backup of my tmobile after i installed twrp (and any method i tried to "revert to stock" failed so i couldn't take the OTA) but its boot, and system are untouched...

if you want copy of it let me know

https://xdaforums.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901/page2
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] weakNPCdotCom:
That would be great. PM me your email, I have a Google drive folder I will start putting resources in. I can also look into the Mount issue. Not sure what's going on with that.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] renecarrera95@gmail.com:
Root

Rscggu
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] LifeHasJustBegun:
Might of screwed up on this one pretty bad, I somehow deleted my internal storage with ADB sideload dalvik and cache wipe so I flashed a stock firmware but now I can't even open my mobile network settings and when I try to mount vendor it tells me "error:closed".
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] requiiiem:
someone has a backup 1924-5 with july patch opp27.91-113?

Its forma Hanna.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] Lord_Worm:
This method does not work on the MetroPCS variant

I had to trial and error it, but I have root with everything working, including the camera. It was messed @ first, but it's working now. PM me for details (I'm at work and don't have the time for a tut)
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] ckelley1989:
PS C:\adb> fastboot devices

ZL5226W6KH fastboot

PS C:\adb> fastboot flash boot boot-e5plus-noverity.img

target reported max download size of 535822336 bytes

sending 'boot' (16384 KB)...

OKAY [ 0.531s]

writing 'boot'...

(bootloader) Image not signed or corrupt

OKAY [ 0.250s]

finished. total time: 0.781s

PS C:\adb> fastboot flash recovery twrp-e5-repack.img

error: cannot open 'twrp-e5-repack.img'

PS C:\adb> adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor

At line:1 char:19

+ adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/v ...

+ ~

Missing argument in parameter list.

+ CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordException

+ FullyQualifiedErrorId : MissingArgument

PS C:\adb> adb push fstab.qcom /vendor/etc/fstab.qcom

error: device not found

PS C:\adb> adb push fstab.qcom /vendor/etc/fstab.qcom

error: device not found

PS C:\adb>

what am i doing wrong
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] weakNPCdotCom:
did you do the entire factory flash? step by step?
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] LifeHasJustBegun:
Yea I figured it out I screwed up while doing it and erased modemst1/2 then flashed modem. Thank you for the response though. Didn't realize how important orderly fashion was. Guess that's a smack to the face if I wanna learn to be a developer lol.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] nicknc:
Hey folks, I have the unlocked US version of this phone, which, according to the sticker under my battery is the -2 variant (same as Cricket).

My bootloader is unlocked, I got TWRP installed, data decrypted, backup backed up, disable-dm verity kernel flashed, magisk 17.1 flashed, and....bootloop.

Recovery is still working great, and I'm going to do a restore of my backup, but would love to hear what advice you might have on getting this thing booting...

---------- Post added at 09:28 PM ---------- Previous post was at 08:56 PM ----------

Well, restoring my backed up system didn't work. Restoring the backed up boot partition didn't work (but I'm not surprised by that-- I was unable to do ANY backups until I fastboot flashed the disable dm verity kernel). Restoring system image didn't work either. Still got a "hello moto" bootloop.

I flashed the boot.img extracted from here for the -2 variant, and now it just hangs on the Motorola screen (still have "bad key" message on startup).

What do you think?
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] nicknc:
Flashing the latest RR img got me back into a working state albeit with encryption re-enabled. Also noticed that the baseband line in my bootloader was no longer blank. I've flashed the disable dm verity kernel and push the fstab.qcom fix to disable forced encryption again...and lost my TWRP backups. Oh well.

RR is booting after flashing Magisk, so there may be some progress.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] nicknc:
Have a LOT of issues with RR (wifi doesn't work, phone doesn't sleep, etc.), so attempted to go back to stock using the XT1921-2 firmware from the firmware thread. No dice-- I get the message "(bootloader) security version downgrade". I did not take any OTA's prior to rooting, so my phone (bought yesterday) must have come with a newer version installed.

At this point, I'm close to looking at letting this phone go. I have no clue why the unlocked version of this phone, sold through Best Buy here, is the same as the Cricket variant, why it does not appear to have a fingerprint reader, why it is sold as an E5 Play (not an E5 Cruise), and why it is so problematic.

For what it's worth, the full Product/Variant listed in the bootloader is "james XT1921-2 16 GB P3", and it is the unlocked Moto E5 Play sold through Best Buy.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] masoko182:
XT1944-3 Moto E5 (Nora)?

Are this instructrions compatible with XT1944-3 Moto E5 (Nora)?
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] LovetheROOT-S3:
Probably an ignorant question... But... Any possible way to flash TWRP without having to use fastboot or use of a PC?
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] MotoJunkie01:
Yes. You can install it directly from the Android OS using the Official TWRP App, or other on-device flashing apps such as Flashify, Rashr, and Flashfire. Of course, this type of install requires that your device be rooted.
[Moto E5 ROMs, Kernels, Recoveries, & Other Develop] LovetheROOT-S3:
Any suggestions to get temp root?