yashsingh1/xdaforums huggingface dataset:
[Moto E4 Guides, News, & Discussion] hitokage004:
Verizon let's you activate any compatible device on their approved list - from another carrier or not, as long as the IMEI/MEID/ESN isn't blacklisted/flagged. This is why their excuses about unlocking the bootloader on their phones make no sense.

Anyone who wants to unlock their bootloader and root, that researches first, knows not to buy the Verizon version. For example you can go buy the carrier unlocked e4, have it activated, use the Motorola website to unlock the bootloader, and root the phone with no problem.

Buying the phone at a discount from another carrier, but then using it immediately with Verizon may not actually work as the IMEI/MEID/ESN may be flagged as being under contract with another carrier.
[Moto E4 Guides, News, & Discussion] :
Yeah, that doesn't make any sense at all. I guess people need to stop buying Verizon devices if they want to unlock and root.
[Moto E4 Guides, News, & Discussion] zoofie666:
I'm back after having a lot of issues irl, I will be working on providing Boost related resources for this device. I had a computer failure as well I'm finally recovering from.
[Moto E4 Guides, News, & Discussion] CodyF86:
Even with basically the stock ramdisk it boots, but still sticks on the showing N/A text for no signature.

Honestly just need Motorola to release the source code; I'm using the correct tag but the source was from Code Aurora so obviously something is different / just need the source code. It's been out long enough I'm going to send them a GPL request for it here pretty soon if they don't put it on GitHub under their msm-kernels.

I may work on getting lineage to boot with an almost stock but modified kernel until we can get the source. Luckily the stock ROM I'd pretty slim so I actually don't mind it, but yeah want some Lineage lol.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Yeah Moto doesn't exactly do anything fast lol
[Moto E4 Guides, News, & Discussion] :
I can't get the kernel to boot either. I already requested the kernel source release on github over a month ago. Just left a message again yesterday politely asking for some kind of word on it.

---------- Post added at 08:19 PM ---------- Previous post was at 08:14 PM ----------

I also found a couple msm8937 kernels for cedric I'm trying to get to work with either los-14.1 or 15.
[Moto E4 Guides, News, & Discussion] KyleBryant:
YES!!!!!! Lineage here we come!
[Moto E4 Guides, News, & Discussion] :
That's a step, but don't get too happy yet. The hals are probably going to need some work since hardware_qcom_audio-caf, display-caf, and media-caf for msm8937 are like the only ones not updated to lineage-15.0 yet. I'm trying los14.1 again hoping to get something working and some kind of base for 15.0.
[Moto E4 Guides, News, & Discussion] SykkNyzz:
We should have a sub group for this >_>
[Moto E4 Guides, News, & Discussion] CodyF86:
When they do release the source code if you want a little help in cutting through the random config junk go ahead and remove the drivers/staging/prima directory from a fork, then link https://github.com/codyf86/vendor-qcom-opensource-wlan-prima/tree/LA.UM.5.6.r1 in roomservice to kernel/motorola/msm8937/drivers/staging/prima, then add

#
# Qualcomm Atheros Prima WLAN module
#
# CONFIG_PRIMA_WLAN is not set
CONFIG_PRONTO_WLAN=y
# CONFIG_PRIMA_WLAN_BTAMP is not set
CONFIG_PRIMA_WLAN_LFR=y
CONFIG_PRIMA_WLAN_OKC=y
CONFIG_PRIMA_WLAN_11AC_HIGH_TP=y
CONFIG_WLAN_FEATURE_11W=y
CONFIG_QCOM_TDLS=y
CONFIG_QCOM_VOWIFI_11R=y
CONFIG_ENABLE_LINUX_REG=y
CONFIG_WLAN_OFFLOAD_PACKETS=y
# CONFIG_WLAN_AUTOGEN_MACADDR_FEATURE is not set
# CONFIG_WLAN_FEATURE_RX_WAKELOCK is not set

to the defconfig when changing everything thats '=m' to '=y'.

It's literally what I've been doing to the surnia / msm8916 kernel to keep wifi up to date; I just switched it to it msms8937.

Turns out our friend the msm E4 at least uses pronto wifi as well (only ~1k-1.5k lines of code different at the most from updated surnia Code Aurora tag) and it compiles and all that happy stuff. They already had wifi in tip-top shape from the E3 and if it ain't broke don't fix it I'm assuming is what they figured when they started dev on the E4 hardware lol .:)
[Moto E4 Guides, News, & Discussion] KyleBryant:
I'm happy regardless, I love this simple little phone.
[Moto E4 Guides, News, & Discussion] :
Well, I'm 10% into an los-14.1 build with one of the cedric kernels I found. I know something is going to be broken, but we'll see if it finishes and boots. Luckily my builds go quick so we'll know shortly.
[Moto E4 Guides, News, & Discussion] :
Cross your fingers boys and girls...

Edit: #*&$+@%!!! Bootloop:(
[Moto E4 Guides, News, & Discussion] CodyF86:
Yeah it's the kernel, Try and flash the stock kernel (the version you extract after you root it and flash noverity) after you flash Lineage just to see what happens tho...
[Moto E4 Guides, News, & Discussion] :
Released. ?
[Moto E4 Guides, News, & Discussion] KyleBryant:
THE KERNEL HAS BEEN RELEASED ON GITHUB GUYS!

---------- Post added at 08:30 PM ---------- Previous post was at 08:29 PM ----------

Disregard for some reason labs didn't show me the newest post lol.

---------- Post added at 08:31 PM ---------- Previous post was at 08:30 PM ----------

When you guys need testers I'm using a metro variant and I'm down to ruin my phone for you lol
[Moto E4 Guides, News, & Discussion] CodyF86:
https://github.com/MotorolaMobilityLLC/kernel-msm/tree/nougat-7.1.1-release-perry

It's go time.

---------- Post added at 11:51 PM ---------- Previous post was at 11:40 PM ----------

@amarc78

Lol they excluded the def_config from the official source, so here for anyone that needs it.

perry_defconfig
[Moto E4 Guides, News, & Discussion] :
Yeah I saw that. It actually has a default config file, but it's named something different.
[Moto E4 Guides, News, & Discussion] CodyF86:
OK so,

I've gotten the kernel with the new kernel source released from Motorola to compile after a few tweaks...(aka add and/or fix a thing or two they either accidentally...or not left out....lol :) )

At the moment it still won't boot, but I'm working on it and have gone back to the basics. I'm building the kernel then repacking it with the stock ramdisk, which narrows it down very quickly.

I have a few more configurations try in terms of how the actual zimage is built, but hopefully, we'll at least be booting the stock kernel (That we have actual control of.) here shortly.....

...That or they are full of crap lol....just kidding though. <3 Motorola I'm sure i'll have it going here shortly.

[B]My Github / Sourxes:
{
[URL="https://github.com/codyf86/android_kernel_motorola_msm8937"]android_kernel_motorola_msm8937[/URL]
[URL="https://github.com/codyf86/vendor-qcom-opensource-wlan-prima/tree/LA.UM.5.6.r1"]vendor/qcom/opensource/wlan/prima - LA.UM.5.6.r1[/URL][/B]
}
[Moto E4 Guides, News, & Discussion] :
If you don't, I will one way or another, lol.

Made the news: http://www.androidpolice.com/2017/09/27/motorola-uploads-moto-e4-kernel-source-code-github/
[Moto E4 Guides, News, & Discussion] KyleBryant:
So is this still going to be based on nougat or oreo?

---------- Post added at 08:26 PM ---------- Previous post was at 08:18 PM ----------

Also how does lineage do with substratum?
[Moto E4 Guides, News, & Discussion] :
[MENTION=5337314]CodyF86[/MENTION] repo is for oreo but I've been working on both. I'd like to get a stable los14.1 build to use until 15.0 is a little more stable. It's not supported, but substratum has been working pretty good on los-15.0 for surnia, so maybe it will for this also. There is a repo to bring substratum support to los-14.1 though, so if I ever get it to boot I'll do a build with it. Stock oreo is supposed to get rootless theme support so hopefully it will eventually work good with los oreo also.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Sweet thanks man
[Moto E4 Guides, News, & Discussion] :
I think this kernel should work. https://github.com/Wzedlare/android...5295538#diff-e7b03b87c3d28d07adb57996a95f8392

I'm not so sure my bootloop problem is the kernel. I haven't been able to get logs yet though. Do you have all the necessary vendor blobs? I've been trying with stuff mainly extracted from stock but I'm missing something I think and it might be at least part of the problem.
[Moto E4 Guides, News, & Discussion] CodyF86:
If you're just flashing the kernel (boot.img) vendor blobs shouldn't matter as they will already be there., but for an entire rom they will of course. Think i'm getting close about to try something real fast will let ya know.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Just keep us posted lol, I'm down to beta test the bare minimum once it works, as long as calls and wifi work I'm fine lol
[Moto E4 Guides, News, & Discussion] CodyF86:
[MENTION=5768732]amarc78[/MENTION]

Ok, So I got the kernel to boot...and when I say boot I mean it display's N/A. The N/A actually goes away, which means it should be starting to run 'init', but then it reboots back to N/A.

So it's looping, but it actually does 'technically' boot instead of freezing or falling back to the bootloader. Can you try to flash this kernel over the lineage14.1 you built. I want to make sure the stock ROM isn't saying nope because the build system atm is adding userdebug to the kernel command line and I also put selinux in permissive mode.

Just want to rule those 2 things out.

http://test-it.us/boot.img.zip
[Moto E4 Guides, News, & Discussion] :
The link doesn't work.
[Moto E4 Guides, News, & Discussion] CodyF86:
Whoops sorry https got me.

https://test-it.us/boot.img.zip

actually That's weird it should have auto redirected you to https anyway.

107.212.34.52/boot.img.zip if that doesn't work.

If it complains about the SSL certificate not being valid / verifiable just bypass it I promise it is, or import the CA cert from https://www.cacert.org/. I didn't have $100+ dollars to spend on having one of the big name CAs sign my ssl cert, but cacert signs them for free and is already imported in a lot of distros / browsers.
[Moto E4 Guides, News, & Discussion] :
It does the same thing you say here. With the kernel I build los with it shows the n/a then loops with the screen just lighting up for a second then going blank over and over but not showing the n/a again. squid2 just posted a new twrp built with an msm8953 kernel source and says los is next. I think I'll try that kernel for the hell of it.

Edit: it wouldn't surprise me if something was missing from the stock kernel source. I hear they left some things out of other kernel sources.
[Moto E4 Guides, News, & Discussion] CodyF86:
Yeah I had to add F2FS back in; the source they posted just had symlinks, which now that I think about that again maybe I should check a few thinks with'ls -l' heh. :)
[Moto E4 Guides, News, & Discussion] CodyF86:
[MENTION=5768732]amarc78[/MENTION]

https://github.com/codyf86/android_kernel_motorola_msm8937

https://github.com/codyf86/android_device_motorola_perry

https://github.com/codyf86/vendor-qcom-opensource-wlan-prima/tree/LA.UM.5.6.r1

Dunno if it will boot, but thanks to Squid and Alberto and the twrp mention, I redid some things in the middle of the night lol.

You'll have to resync all 3. Will know in a minute.

---------- Post added at 04:40 AM ---------- Previous post was at 04:01 AM ----------

Well crap...lol

I went hard in the paint, but still won't boot even with the stock ramdisk. I followed the msm8953 commit path in terms of the moto F2FS and etc even.

How 8953 is booting but 8937 from motorola isn't has me stumped, but i'm sure we'll get there. At least I got a good base started for the future..

Maybe I'll try and build it with gcc 4.8 instead of 4.9, but that's all for tonight folks!
[Moto E4 Guides, News, & Discussion] KyleBryant:
Good job guys, any progress is better than no progress.
[Moto E4 Guides, News, & Discussion] CodyF86:
I just figured out that setting bootmode to userdebug in the kernel command line is why it was hanging with the stock ROM. Changing it back to user makes it fall through back to the bootloader if something is wrong...or boot if nothings wrong. Going to try something real fast to see if I can get the source built to boot in some shape way or form with the stock rom, but pretty confident now I can at least build los 14 and see what happens.

The build system adds userdebug to the kernel command line, so I've been using bootimg_tools to unpack the kernel and ramdisk and repacking it set back to user.
[Moto E4 Guides, News, & Discussion] KyleBryant:
I'm hoping one of these days I'll get on to find that it worked lol
[Moto E4 Guides, News, & Discussion] :
Your impatient comments every couple days isn't helping speed things up.
[Moto E4 Guides, News, & Discussion] KyleBryant:
They're not impatient comments grumpy, they're excitement and encouragement comments lol cheer up.
[Moto E4 Guides, News, & Discussion] carkev:
I have now removed my post to Q&A where perhaps it should have been in the first place - sorry.
[Moto E4 Guides, News, & Discussion] :
[MENTION=5337314]CodyF86[/MENTION] I switched to building aicp 12.1 since you and squid2 are doing los, so I don't get anybody mad at me and I already had the repo synced. Anyway, the kernel I've been building with will boot to the bootanimation with the stock rom, so I'm pretty sure it will boot aicp or los. I'm pretty sure my problem is at least mainly with the hals. I noticed throughout the while build I see no reference to any /hardware/qcom/display or media. All I see is /qcom/audio-caf/msm8996 and qcom/bt. I've tried adding lines to the BoardConfig.mk to no avail, I even added the direct paths to all the caf-msm8937 stuff. If I switch the board platform to 8920 it's looking for 8920 hals and it throws out a bunch of errors about this and that are missing. I'm a little confused. I've​ never had this problem building for other devices. Any ideas?

Edit: wait a minute, I just had a lightbulb suddenly appear above my head. Lol.
[Moto E4 Guides, News, & Discussion] SykkNyzz:
[MENTION=5768732]amarc78[/MENTION] totally jacked this post lmao jkjk
[Moto E4 Guides, News, & Discussion] carkev:
it says XT1766 on my Boost one ... and I believe it has Mediatek chipset

I bought it whilst on hols in the USA, and came to thread to hopefully find a way of sim unlocking it

so as to work back here in the UK (then root/twrp)

the ebay simlock sellers I have contacted say they cannot unlock it, so I'm stymied at present
[Moto E4 Guides, News, & Discussion] ATTACK:
The Boost Mobile E4 has a Snapdragon 427 not a Mediatek
[Moto E4 Guides, News, & Discussion] carkev:
I was going off what gsmarena say ...

How can I find out definitely as it would be important when I try to root it?

My problem is that I simply don't know enough!
[Moto E4 Guides, News, & Discussion] KyleBryant:
CpuZ in the playstore will tell you
[Moto E4 Guides, News, & Discussion] carkev:
:good:thank you - and for the root link,

I may be rated as a 'senior member' because I was once more active back on Windows PDA phones such as the Orange SPV M700. (not because I'm 73!)

my knowledge of Android Smartphones is not that great, which is why I appreciate good advice.
[Moto E4 Guides, News, & Discussion] carkev:
I tried Cpuz,

and it confirms what you say (ie: the Arm Cortex-A53 = Qualcom Snapdragon)

but is it any wonder that the likes of myself can get confused when 2 websites offer conflicting advice?

the one below is the one that I found yesterday - it says Mediatek for the XT1766 ...

http://www.phonemore.com/motorola-moto-e4-xt1766/specs/3428

yet this one says Qualcomm (without mentioning a model number)

https://www.phonearena.com/phones/Motorola-Moto-E4_id10485

so the moral of this post is that in future I'll do all my research at XDA:good:
[Moto E4 Guides, News, & Discussion] :
Did you guys see this? https://www.xda-developers.com/official-xposed-framework-android-nougat/
[Moto E4 Guides, News, & Discussion] KyleBryant:
yeah but i cant seem to get it to boot
[Moto E4 Guides, News, & Discussion] :
It took 5 or 10 mins to boot for me. But..

Make sure you wipe cache/dalvik after flashing.
[Moto E4 Guides, News, & Discussion] KyleBryant:
tried it again we'll see what happens, i used the arm sdk25 version which is the right one right?
[Moto E4 Guides, News, & Discussion] :
Yes.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Still not working for me hmmmm
[Moto E4 Guides, News, & Discussion] :
That's odd. I didn't do anything special. I had magisk 14.2 installed and a substratum theme. I had just made a backup before flashing a aicp build I tried and I just flashed it. Did you try the uninstaller?
[Moto E4 Guides, News, & Discussion] KyleBryant:
Yeah and after uninstaller my phone boots normally, i went in and removed every trace of xposed i could and im trying again

---------- Post added at 04:02 PM ---------- Previous post was at 03:51 PM ----------

nope still nothing
[Moto E4 Guides, News, & Discussion] :
Here's a wild guess. I had this in the build.prop set to false:

ro.mot.security.enable=true

Try changing that to false and reflash xposed and see what happens. I don't have any other ideas.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Nope, oh well. Thanks for the help I'll just wait til lineage and try again.
[Moto E4 Guides, News, & Discussion] SomethingiCy:
Hi everyone, brand new to the forums but long-time lurker. I recently bought the Boost E4 hoping to use it on the AT&T network. So far I have unlocked the phone through Motorola's website and flashed the 7.1.1 Sprint stock firmware on the phone - neither action allowed my AT&T sim to do anything other than produce an "Invalid Sim" notification.

The quoted post above caught my attention, but when I attempt to flash the retail firmware through RSD Lite I get a "Failed flashing process. 3/23 flash partition "gpt.bin" -> Phone returned FAIL." error. The fastboot log returns "Failed to verify hab image primary_gpt".

So, I have two questions. 1) Any advice any of you might have for connecting to the AT&T network, either through enabling band support in the Sprint firmware or successfully flashing the retail firmware? 2) I've also been watching the talk of Lineage development for this phone with a lot of anticipation. Were a functional Lineage rom to be released, do those typically enable all of the carriers the phone's hardware supports, or in this case since development is occurring on a Boost phone, would the Lineage rom likely only support a limited number of CDMA network?

Thanks in advance for any help!
[Moto E4 Guides, News, & Discussion] andMego:
Unlock the phone through boost Mobile or eBay......
[Moto E4 Guides, News, & Discussion] carkev:
I hope you get more joy than me mate - Boost simply won't answer my request and all the many, many ebayers (and internet unlocking services) I have tried say they cannot unlock CDMA phones or Boost E4's with an IMEI starting with 99
[Moto E4 Guides, News, & Discussion] KyleBryant:
I finally got it to work with the help of fx file explorer and an init.d file I made to force it to run selinux permissive on boot.
[Moto E4 Guides, News, & Discussion] :
Now I know why it worked for me but not you. I had an Arise audio mod installed which installs an selinux permissive script in su.d. I just realized that script was there yesterday and was going to mention that. Now that you got it working, this works pretty good https://www.google.com/amp/s/xdafor...tybox-v7-0-0-tweak-box-android-t3653953/amp/x

There aren't many compatible modules yet.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Did you have a problem with it absolutely swallowing ram for about 10 minutes after you powered your phone back on? I'm getting some horrible lag. After checking Xposed logs it's running through everything on my phone.

---------- Post added at 02:55 AM ---------- Previous post was at 02:55 AM ----------

Oh and I already have gravity box installed lol
[Moto E4 Guides, News, & Discussion] :
No, I hadn't noticed. I have noticed a little lag with chrome, but nothing else and my ram is about the same as it was before.

Edit: I have quite a few apps installed too.
[Moto E4 Guides, News, & Discussion] KyleBryant:
Mine is going insane and I'm getting a lot of failed to load logs in xposed
[Moto E4 Guides, News, & Discussion] KyleBryant:
Look at that ram usage
[Moto E4 Guides, News, & Discussion] KyleBryant:
Wrong shot lol
[Moto E4 Guides, News, & Discussion] KyleBryant:
Went back to recovery and did another fresh cache clean and it fixed the problem.
[Moto E4 Guides, News, & Discussion] :
That's better than mine.
[Moto E4 Guides, News, & Discussion] KyleBryant:
I like to keep it below a gig if I'm not using anything lol
[Moto E4 Guides, News, & Discussion] KyleBryant:
Any updates on lineage progress?
[Moto E4 Guides, News, & Discussion] squid2:
I've been working on it for a few days. I'm working with my friends [MENTION=4480917]Alberto97[/MENTION] and [MENTION=1829889]vache[/MENTION] on setting up common repos for eight different Motorola devices to reduce duplicated code and effort for maintenance in the long term. It's a bit early right now and there's a lot of work to do, but give it a few weeks and it'll get there. You can see what we've been up to on GitHub. I'm working on LineageOS 14.1 first since it's easier to get things working on a stable base with known suitable blobs, then we can deal with 15 once the device repos are solid. I'm not really ready to accept pull requests at the moment since it's so early in development, but I'd welcome the involvement of others once we're ready.

And a screenshot from this weekend to keep you all excited:

[IMG="LineageOS 14.1 running on Moto E4 (perry)"]https://i.imgur.com/HoPNg9I.png[/IMG]
[Moto E4 Guides, News, & Discussion] :
Nice to see that screen shot. I think I figured out why I can't get my builds to boot as far as the bootanimation. It's the msm8937 stuff I was using. Like I mentioned to someone weeks ago, they need some work. It will be nice to ha e common repos. You work is very much appreciated.
[Moto E4 Guides, News, & Discussion] KyleBryant:
That's awesome man! I'm here when you need field tests.
[Moto E4 Guides, News, & Discussion] KyleBryant:
What happened to the TWRP thread?
[Moto E4 Guides, News, & Discussion] :
Moved to it's own Qualcomm development section. Things are being separated to avoid confusion between mediatek and qcom variants like it should be.

Edit: any Qualcomm discussion, guides etc will be moved to their own "MOTO E4 (QUALCOMM) GUIDES, NEWS, & DISCUSSION" section. Any new threads for qcom variants should be posted there. Also anything new for the development section should be here: https://xdaforums.com/moto-e4/moto-e4-qualcomm-roms-kernels-recoveries--other-development
[Moto E4 Guides, News, & Discussion] KyleBryant:
If my guide to rooting could be moved that would be awesome
[Moto E4 Guides, News, & Discussion] :
It's should be shortly. I'm really glad they honored my request. It was getting to be a mess around here. It's much easier for users to not have to sort through info about different devices in the same thread.
[Moto E4 Guides, News, & Discussion] KyleBryant:
95% of it is Qualcomm anyway lol
[Moto E4 Guides, News, & Discussion] :
Yup, and mediatek never gets as much love as qcom if any.
[Moto E4 Guides, News, & Discussion] :
It's on now!
[Moto E4 Guides, News, & Discussion] Shidell:
While your work is still early-going, I'm curious what your thoughts are about compiling images for the E4 (and other devices) as 64-bit.

The E4 ships with a 32-bit build of Android, despite having 64-bit capable hardware.

I ask because at least Google Camera, (possibly other applications), are being built for ARM64-only now, and if we can build for ARM64, then we could also (hypothetically) use these newer apps.

Any thoughts?
[Moto E4 Guides, News, & Discussion] SykkNyzz:
Awwww.... And I just finally figured out about running Xposed on stock.

Good job btw
[Moto E4 Guides, News, & Discussion] :
Don't worry, you can play with Xposed for a little bit longer. There's still work to be done. I don't have a signal on Boost. But it's pretty damn good so far. It'll get there. I just did this too: :)