yashsingh1/xdaforums huggingface dataset:
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] RebelLion_:
Verizon E4 cannot be unlocked, so i doubt there's any way you can flash anything to it with any method
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] AeonFlux1603:
You can flash the official stock firmware for your variant which is signed by the OEM. The locked state of the bootloader will not permit the device to be flashed with any other firmware packages, signed or unsigned. Also, the locked bootloader will typically not permit downgrading to an earlier firmware version. The firmware package version you flash will need to be equal to or newer than the current version on your device. The Verizon variant of the Perry is extremely easy to brick in this regard, so use caution.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] TheDeveloperDude95:
Hey I wasn't trying to. It was simple question
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] b@dv3g3t@bl3s:
[MENTION=6485916]squid2[/MENTION] This is literally the best news ever to hear about this phone. Well this and [MENTION=220951]Rebellion[/MENTION]s new kernel for it.

????
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] GartimusPrime:
i found a build from a dev that got removed from xda, i found his build online via android file host but he has since taken it down and i dont have my copy anymore
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] smartech:
Not able to get any carrier work

Someone has issues carrier work? I have the

E4 Qualcomm version, is it an modem o radio file available?
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] AeonFlux1603:
Which E4 Qualcomm? There are several.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] zahidm:
I have some builds may be
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] AeonFlux1603:
Full firmwares can be found here for the xt1765, xt1767 & xt1768 Moto E4 Perry Qualcomm models. Available firmwares include RETAIL, RETCA, Amazon, T-Mobile, MetroPCS, US Cellular and Verizon. https://mirrors.lolinet.com/firmware/moto/perry/official/

For the xt1766 Moto E4 SPerry (also Qualcomm), including Sprint, Boost Mobile, Virgin Mobile, TextNow, FreedomPop, Ting & Republic Wireless, firmware packages are available here: https://mirrors.lolinet.com/firmware/moto/sperry/official/ The standard Sprint firmware package works for the Sprint MVNOs & subsidiaries I mentioned.

All packages available in the above links include radio firmware, bootloaders, recovery, partition tables (gpt.bin), boot images, boot logos, etc. But, saying you have the Qualcomm version is overly broad. As you can see there are several Qualcomm versions, as well as carrier-specific variants of those models. Use your model number or SKU (as well as your mobile provider) to determine the firmware package you need. If you need installation instructions, there are tons of guides and tutorials here on XDA which outline fastboot, m-fastboot and RSD-Lite firmware installation for Motorola and Lenovo devices.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] ThePhxRises:
Hi, been having an issue with my camera since I first installed this ROM. The first night I had it, the camera and flashlight worked fine, but when I woke up the next morning, any app that attempts to access the camera crashes immediately. Logs are attached, and any help is appreciated.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] smartech:
Thank you very much for your answer
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] AeonFlux1603:
I hope that helps you find the firmware you need to resolve your radio situation. Out of curiosity, did your cellular radio stop working, or is it something else?
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
Did you try a clean flash of the ROM?
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] ThePhxRises:
First install was a clean flash, however by the time it stopped working I'd already setup most my apps (though it worked after I was done setting them up and only stopped working the next morning, without so much as a reboot to trigger it) so I'm hoping to avoid having to do that all again.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] DB126:
Assume you rebooted after the problem manifested? Might try wiping caches in TWRP.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] ThePhxRises:
Absolutely, it's been weeks, I've rebooted countless times, and I've already cleared my caches in TWRP two or three times.

---------- Post added at 09:13 AM ---------- Previous post was at 08:38 AM ----------

So I was reading through older posts here and read that editing build.prop can cause the camera to stop working, well I didn't edit my build.prop since the whole reason I installed this rom was to go systemless and pass safetynet. Turns out the Magisk plugin I use to pass CTS Profile breaks the camera, presumably because it edits build.prop.

I thought to check because while I was digging through the logs I sent I came across a line which said permission was denied to build.prop.

Camera's fixed, but now I don't pass CTS Profile :(
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] DB126:
Yep - cat/mouse game with questionable tactics to get around safetynet. I have long since stepped away from this time wasting excercise. Good luck.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
Which module? Was it the props config module by Digeridoohan? Might not have spelled his name right...

But if so, you can ask for help in his thread by specifying the prop in question. He provides excellent support.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] ThePhxRises:
It was both that module and SafetyPatch by hackintosh5.

I can get by without passing CTS Profile, tbh
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] uwapalwa:
where?
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] GartimusPrime:
I did a build yesterday for CDMA devices that I am using right now. So far it works great, I get LTE and everything. I should point out that I am on US Cellular and have no idea if it will work on any other CDMA devices. Also I am not a dev, I can't fix things, I simply learned how to sync and build. I found some repos from [MENTION=220951]Rebellion[/MENTION] and decided to give it a go and it worked.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] GartimusPrime:
I've done another build today, just upstream changes, really just making sure it works, if anyone is interested
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] DB126:
Suggest spinning up a seperate thread if interested in sharing your work. I think it would be welcomed but keep in mind the inferred responsibilities should issues be found.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] GartimusPrime:
Yeah, that's the thing, not a Dev at all in the slightest, I got lucky. I can't fix things, so I will just stay in the shadows. I wont post anymore though as to not cause any issues. Thanks
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] DB126:
Kinda sad. Not that you are "not a Dev at all" (we are all skilled in different and valuable ways) but the realization that one can't easily post a one-off piece of work on XDA without fear of future criticism for not supporting the baby. Lots of demanding content consumers on these boards.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] GartimusPrime:
I honestly can't believe I got it to work. I mean, I really didn't, I just did some research and found the device and kernel trees that had the CDMA fix from the last guy that built.

I learned how to sync and build from a friend of mine, gave it a go and it worked. I am more than willing to share my AFH link if anyone wants it but I have yet to learn how to "fix" things so starting my own thread is not the best idea...
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
Completely understood. Been there bro. I don't share anymore either. Better off going to e4 telegram group

Official Moto E4 Perry Development

Official Moto E4 Qualcomm development group. Be respectful!

https://t.me/e4perry
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] b@dv3g3t@bl3s:
I'm interested in that link if you're still willing to share it?
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
https://xdaforums.com/moto-e4/how-to/e4-qualcomm-los-cdma-data-fix-discussion-t3690873/post79031856
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] LKJEFoi234:
Does this work for xt1766 on Sprint (CDMA)? I'm running this currently and it works fine, but prefer lineageOS.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] jeffhutch.412:
Can you post it on here for everybody :fingers-crossed:

Update: idk what caused it to begin with, but after reflashing, file transfers are all good ?

---------- Post added at 11:49 AM ---------- Previous post was at 10:53 AM ----------

im using it right now. lte, wifi hotspot, bt tether, mms, youtube, app dl, everthing using data that I could think of is now working perfect.

everything seems to be working awesome! :highfive:

EXTREMELY BUMMED that they took the theme engine out ?? (yeah, I've been out of the game for a bit LOL)

But now I'm stuck on root. I flashed the su zip from lineage for 14.1 but Im not rooted. Help!
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
[MENTION=4709686]jeffhutch.412[/MENTION]

Flash magisk 18.1
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] AeonFlux1603:
[MENTION=5752019]madbat99[/MENTION], I have searched diligently for a solid answer on a topic, but I'm not coming up with anything concrete. I was in hopes that maybe you knew. On the Sprint compatible xt1766, is there some type of security mechanism in place that actually prevents the baseband radio from being downgraded to an older version? For example, I am running the latest stock build (NCQS26.69-64-13) with the M8920_15000.280.06.05.07R baseband version. I have flashed the previous firmware build (NCQS26.69-64-11) with fastboot, and the baseband version indeed downgraded accordingly, to M8920_15000.280.06.05.06R. I have read on several of the device threads that downgrading the baseband version is somehow restricted, presumably by way of /aboot. So to my question: since I successfully reverted my baseband back to the previous version, downgrading is clearly not prohibited in its entirety. I'm assuming that downgrading back to the initial device release version of the baseband is prohibited due to that particular version allowing the device owner to enable full GSM functionality. (I do realize GSM support is not feasible unless the device was initially booted -- out of the box -- without the UICC card installed. Once booted up with the UICC installed, the device appears to be forever locked to the respective Sprint-affiliated network).

Am I correct in my reasoning as to baseband downgrading and, if so, do you know what mechanism was put into place to enable the restriction? Thanks for your time .
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
Well, to my memory, at a certain point it was no longer an option to downgrade modem or any other sensitive partition. Like bootloaders or gpt.bin. it has been assumed, and appears to be, the point where it happened. The same point in time that you have observed (update to firmware ending -10).

The current theory (supported by people who actually work or have worked at Motorola mobility) is that it is a qfuse (or something similar) that was already in place. But was either activated, or commandeered from another purpose, to serve this function.

At the time surrounding that update, no one was able to downgrade the modem below that point (or even if they did it was somehow incomplete), it has been a while and, since it didn't concern me, the memory is a bit fragmented.

I use my device on the intended network, so it wasn't critical information, or at least not important enough to leave a clear, solid, easily recallable memory. So it's missing bits. I apologise, but that's just how the human brain works.

So my theory is that either

1. you were able to downgrade the modem the way the others could which is somehow incomplete (a previous member was quite obsessed and studied it thoroughly) or

2. The current update wasn't available then, and that point is as far back as you can successfully downgrade from then (-10) on.

Either way, I no longer have the device to test or hypothesize in a manner that would answer your question to absolute satisfaction.

The thread in which he laid out his journey (and frustration) the whole way through likely still exists.

also I don't really have the time or interest in digging into something that really has no benefit for me, only because this is the busy season for my work and my time is spread very thin.

Often times in the slow season when I have more time the prospect of being able to help someone else is good enough reason for me to go digging. that's at the heart of XDA that Drew many of us here and keeps many of us here beyond learning to mod our own devices.

Pretty sure I've answered to the best of my ability and wish you good luck in your search for an answer that will satisfy you.

I do have to admit that even with very little free time had you had a very important reason for wanting to know this it could have nudged me over the edge to start digging. but I'm a little glad that you didn't because it is late and I have to get up early.

Goodnight
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] AeonFlux1603:
Thanks much [MENTION=5752019]madbat99[/MENTION]. That's the best (and likely the most accurate) answer I've read on the subject. Yeah, my reason for asking is merely out of curiosity. I am trying to learn these Moto devices and how they click. I'm accustomed to working with LG devices and, similar to Motorola, LG commonly uses anti-rollback safeguards to prevent downgrading of firmware versions. Unlike Motorola devices, however, LG's anti-rollback is easily bypassed. Motorola seems serious about preventing firmware downgrading. Your answer as to being incomplete on the baseband downgrade is spot on. Just because my version appeared to revert back to the previous version, I assumed that it had successfully downgraded. But, upon further testing, I realized that the cell radio was not functioning properly.

In any event, thanks for your info and your theory. My time is likewise spread thin so I fully understand you there. So again, thank you very much for taking the time to address my curiosity on this topic.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] Eguy:
Funny you mention baseband, I have been running this rom for a while now (I have a factory unlocked retail XT1768) and just this last weekend all of a sudden my phone radio stopped working and I flashed the baseband again and lost my IMEI. I restored a stock nandroid and got my IMEI back and my SIM is recognized but now the phone radio is permanently powered off (as noted in the testing screen under *#*#4636#*#*). Not sure if it died or what is going on but it all happened out of the blue. Has this happened to anyone and is there a fix? I did a clean flash of this rom and the issue still remains.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] AeonFlux1603:
I haven't ran across any reports of issues that match what you are describing, but baseband problems in general are commonplace on the xt1766 model -- especially when a custom ROM is installed. Your issue is one of the first I have heard of involving the xt1768 model.

I would be almost willing to wager that your issue could be completely fixed by flashing a recent firmware package with fastboot or RSD Lite (taking care to wipe modemst1, modemst2, DDR, etc.). Have you tried clean flashing not just a stock ROM, but a complete firmware package?
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] Eguy:
Yeah, I recall seeing issues with the XT1766 model. I tried using RSD lite but no qcom port appears when I boot into the bootloader so RSD doesn't see my phone. I've tried multiple computers and the only port that appears is the ADB/fastboot one. Fastboot works perfectly fine (it's how I flashed the baseband). When I wiped modemst1&2 is when I lost my IMEI and I went back in and ran down the flow of the RSD package in fastboot which got my IMEI back as I mentioned. It's just weird to me that my SIM is recognized, I have my APN in the APNs and the phone radio refuses to power on. Just says no signal on the status bar.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
That radio off problem happens to everyone trying to use this ROM who is

1. Using a Sprint e4 (xt1766)

2. Has updated passed the firmware ending in -8

Edit: nevermind, just remembered you said xt1768

Brain blanked out and fed me bad information for a second, lol

Also, if your PC is windows 10 and having trouble with RSDlite, try the one on this page.

The one that says RSDlite 6.2.4

Also, the RSDlite XML to batch on that page is a great tool too. It converts the XML in the stock firmware to a .bat for easy one click flashing of firmware with fastboot. In case you just can't get RSDlite working. Trying to keep things easier for my fellow Moto users.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] Eguy:
That is the RSD lite I am using. When I plug the phone in I simply don't get more in my device manager than the ADB/fastboot interface. My Moto E2 works just fine. I'm just not sure how or if this can even be fixed anymore. The firmware I have is "XT1768_PERRY_RETAIL_7.1.1_NPQS26.69-41-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml"
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] kerdiaz:
I have a locked Sprint XT1766 and I'm using LOS14 for use the cellphone unlocked, I have two sim cards a none of two don't up LTE. any solution for that?
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] AeonFlux1603:
Please elaborate some on your issue. I understand your xt1766 is "locked," so I'm assuming you mean carrier/network locked. Your use of LOS 14.1 does not "unlock" your device for use on other carriers. Are you attempting to use a GSM SIM in your xt1766 running LOS 14.1? To my knowledge, there is no known exploit to unlock the xt1766 to GSM operability, regardless of what ROM you are using.

The only way I know to enable GSM support on the SPerry xt1766 is to remove the installed SIM out-of-the-box, before first boot. The phone must be booted initially without the Sprint affiliated SIM installed. Otherwise, the device becomes permanently locked to its respective CDMA network.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] kerdiaz:
I explain to you for parts:

1. I'm in Venezuela, and i have a Sprint E4 XT1766 wich is locked to Sprint. So I unlock bootloader, install TWRP and flash Lineage OS to use the cellphone Worldwide.

2. The problem is, I flash LOS, but my cellphone don't LTE up. So I don't know how because also I have a Moto X Pure, and both simcard work with LTE fine.

My question is: Is there any fix for that?

Thanks.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
Nope. E4 is newer, with new methods of carrier lockdown. As explained previously, phone must never be booted with original SIM installed. One time being booted to system with the original SIM, locks it to the carrier with no known way to work around.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] Eguy:
I just want to add in that for some reason my phone works on the stock rom only. I restored a nandroid of the stock rom and the phone radio works perfectly. I was curious and I did a clean flash of the latest LOS build and I had the same results - phone radio would not power on. Not sure why that is. I am relieved it's not a hardware problem and will struggle with the stock rom for now.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
Xposed with gravitybox is pretty close to a custom rom. Much more stable too.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] DB126:
100% agree - a statement which is applicable to *most* Moto devices. Alternatively, choose a reoccurring head dunk in boiling oil messing around with sketchy custom ROMs. Really depends if you prefer to manage your device or actually use it.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] Eguy:
I do miss the Bluetooth battery life in the status bar like on LOS, I don't think that can be added with gravitybox.
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] madbat99:
Nope. You can use the rom built for crma.if using the Sprint device on Sprint's network (or boost, Virgin, etc).

https://androidfilehost.com/?fid=1395089523397905823
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] cryochris:
MediaTek device

Hallo out there, I provide myself with a Moto e4 which I first set into developer mode and then I put into fastboot mode (connected with my PC via USB). From my Debian testing system I invoked fastboot device. The only entry was: Z**** fastboot.

So guess this is not the actual device?

However I checked dmesg to request what my kernel really discoverd:

[ 2960.620572] cdc_acm 3-2:1.0: Zero length descriptor references
[ 2960.620600] cdc_acm: probe of 3-2:1.0 failed with error -22
[ 2960.660818] cdc_acm 3-2:1.1: ttyACM3: USB ACM device
[ 2961.642983] usb 3-2: USB disconnect, device number 10
[ 2963.632489] usb 3-2: new high-speed USB device number 11 using xhci_hcd
[ 2963.780875] usb 3-2: New USB device found, idVendor=0bb4, idProduct=0c01, bcdDevice= 1.00
[ 2963.780881] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2963.780885] usb 3-2: Product: Android
[ 2963.780888] usb 3-2: Manufacturer: MediaTek
[ 2963.780891] usb 3-2: SerialNumber: Z****

So it is a MediaTek device, but I also recognized my serial number from the fastboot scan. So you mentioned that is not possible to install LineageOs on a MediaTek device? And indeed when I try to unlock the device with fastboot oem unlock Im asked from the phone gui to confirm this with volume up for yes. I did so but the phone dialog ended this by saying this is not allowed and the current status is "unlocked" on the shell it says:

(bootloader) Start unlock flow

FAILED (remote:

Unlock operation is not allowed

)

finished. total time: 6.912s

Is there anything I can to about it, or is it just locked?

Thank you in advance.

BR /chris
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] jamiedoe:
Have you enabled OEM unlocking
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] cryochris:
You already saved my day :) Thank you very much.

But is it possible to install LineageOs on such a MediaTek device anyways?

Thanks

BR Christian
[Moto E4 (Qualcomm) ROMs, Kernels, Recoveries, & Ot] jonjonmariah:
i need help =(

I am new here an i believe my problem got worsen..

I tried flashing roms and suddenly, my baseband is not found and wifi is disabled. I tried several downloads of stock roms but none of them is working. I can flash custom roms and i tried one stock rom (debloated) but still the baseband is not found and wifi is not working.

My first try was successful, then i got curious on flashing roms and i ended up breaking my phone. Can somebody help me please.. =(

I have the XT1766 Moto E4, Sprint variant from day oe. Thank you in advance!